Oms Fem

OTN Manual
OMS-FEM (OMS Front End Manager) v9.5

Doc. No.: BG-M370-E-8

COPYRIGHT AND TRADE SECRETS/LIABILITY
The present document and its contents remain the property of OTN Systems NV and
shall not, without prior written consent, be copied or transmitted or communicated to third
parties, nor be used for any other purpose than such as underlies their delivery to the
addressee.
The present document and its contents may change in the course of time or may not be
suitable in a specific situation. Consequently, they are recommended as suggested
guideline only.
OTN Systems NV hereby disclaims any liability for any damages that may result from the
use of the present document unless it is used with respect to the operation and mainte-
nance of equipment originally manufactured by OTN Systems NV and covered by its
standard warranty.
Open Transport Network OMS-FEM (OMS Front End Manager)
BG-M370-E-8 Page 3 of 189
Contents
1. INTRODUCTION .................................................................................................. 7
1.1 General ................................................................................................................ 7
1.2 Referenced Documents ..................................................................................... 7
2. PREREQUISITES ................................................................................................ 8
2.1 General ................................................................................................................ 8
2.2 Serial Key & License Pack ................................................................................ 8
2.2.1 Serial Key ............................................................................................................. 9
2.2.2 Voucher ................................................................................................................ 9
2.2.3 License Pack ........................................................................................................ 9
2.2.4 Licenses in a Live System ................................................................................... 9
3. GETTING STARTED ......................................................................................... 10
3.1 Installation ........................................................................................................ 10
3.2 Connection to the OTN Network .................................................................... 10
3.3 Start Up OMS-FEM Server ............................................................................... 10
3.4 Start Up OMS-FEM GUI ................................................................................... 12
4. TREEVIEW & FIELDS DESCRIPTON ............................................................... 13
4.1 LocalControl (LocCtrl) Field ........................................................................... 14
4.2 NetworkControl (NetCtrl) Field ....................................................................... 14
4.3 NetworkStatus (NetStat) Field ........................................................................ 15
4.4 NetworkStatusAlarm (NetStatAl) Field .......................................................... 15
5. OPERATION AND CONFIGURATION .............................................................. 16
5.1 Menu Structure ................................................................................................. 16
5.2 Functional Blocks ............................................................................................ 17
5.3 OMS GUI OMS-FEM GUI ............................................................................. 18
5.4 Node .................................................................................................................. 19
5.4.1 General .............................................................................................................. 19
5.4.2 Node Properties ................................................................................................. 19
5.4.3 Node Actions ...................................................................................................... 22
5.4.4 Node Info Example ............................................................................................ 25
5.4.5 Node View .......................................................................................................... 27
5.5 External/OTN Device ....................................................................................... 30
5.5.1 General .............................................................................................................. 30
5.5.2 Adding an External/OTN Device into OMS-FEM ............................................... 30
5.5.3 Device Properties............................................................................................... 31
5.5.4 Device Actions ................................................................................................... 33
5.6 Ports .................................................................................................................. 34
5.6.1 General .............................................................................................................. 34
5.6.2 Port Properties ................................................................................................... 34
5.6.3 Port Actions ........................................................................................................ 41
5.7 Link Aggregation ............................................................................................. 42
5.7.1 General .............................................................................................................. 42
5.7.2 Configuration ...................................................................................................... 42
5.8 External LAN .................................................................................................... 45
5.8.1 General .............................................................................................................. 45
5.8.2 Configuration ...................................................................................................... 45
5.9 VLAN Port/External LAN to Segment Mapping ........................................ 48
5.9.1 General .............................................................................................................. 48
5.9.2 Configuration ...................................................................................................... 48
5.10 Transparent Channel QinQ .......................................................................... 52
5.10.1 General .............................................................................................................. 52
5.10.2 Prerequisite ........................................................................................................ 52
OMS-FEM (OMS Front End Manager) Open Transport Network
Page 4 of 189 BG-M370-E-8
5.10.3 Configuration ...................................................................................................... 52
5.11 MSTP ................................................................................................................. 57
5.11.1 General .............................................................................................................. 57
5.11.2 Configuration (General) ..................................................................................... 57
5.11.3 Configuration (VLAN, Transparent Channel, Node) .......................................... 58
5.12 IGMP Snooping ................................................................................................ 63
5.12.1 General .............................................................................................................. 63
5.12.2 Configuration (General) ..................................................................................... 63
5.12.3 Configuration (VLAN, Node) .............................................................................. 64
5.13 Port Mirroring ................................................................................................... 70
5.13.1 General .............................................................................................................. 70
5.13.2 Configuration ...................................................................................................... 70
5.13.3 Remote Port Mirroring ....................................................................................... 72
5.14 MAC Access Control List (MAC ACL) ............................................................ 74
5.14.1 General .............................................................................................................. 74
5.14.2 Configuration ...................................................................................................... 74
5.15 IP Access Control List (IP ACL) ..................................................................... 77
5.15.1 General .............................................................................................................. 77
5.15.2 Configuration ...................................................................................................... 77
5.16 RADIUS (Remote Authentication Dial In User Service) ............................... 80
5.16.1 General .............................................................................................................. 80
5.16.2 Configuration ...................................................................................................... 80
5.17 Virtual Router ................................................................................................... 85
5.17.1 General .............................................................................................................. 85
5.17.2 Configuration ...................................................................................................... 85
5.18 Static Routing ................................................................................................... 89
5.18.1 General .............................................................................................................. 89
5.18.2 Configuration ...................................................................................................... 89
5.19 VRRP (=Virtual Router Redundancy Protocol) ............................................. 93
5.19.1 General .............................................................................................................. 93
5.19.2 Prerequisite ........................................................................................................ 93
5.19.3 Configuration ...................................................................................................... 94
5.20 DHCP Relay / Server ........................................................................................ 98
5.20.1 General .............................................................................................................. 98
5.20.2 Prerequisite ........................................................................................................ 98
5.20.3 Configuration ...................................................................................................... 99
5.21 IGMP (Internet Group Management Protocol) ............................................ 105
5.21.1 General ............................................................................................................ 105
5.21.2 Configuration .................................................................................................... 105
5.22 OSPF ............................................................................................................... 109
5.22.1 General ............................................................................................................ 109
5.22.2 Configuration .................................................................................................... 110
5.23 PIM-SM ............................................................................................................ 118
5.23.1 General ............................................................................................................ 118
5.23.2 Prerequisite ...................................................................................................... 118
5.23.3 Configuration .................................................................................................... 119
5.24 Front Port/External LAN/SLAN Mapping ..................................................... 124
5.25 Tagged/Untagged Ports ................................................................................ 124
5.26 802.1Q VLAN Trunking .................................................................................. 124
5.26.1 SLANs .............................................................................................................. 124
5.26.2 External LANs .................................................................................................. 125
5.27 ELAN/SLAN/VLAN (Trunking)/Tagged/Untagged Example ....................... 125
5.27.1 Introduction ...................................................................................................... 125
5.27.2 Learn the different Port Types ......................................................................... 126
5.27.3 Create SLAN (=service) Between Nodes ........................................................ 127
5.27.4 Modify SLAN: VLAN Trunking: Untagged Tagged ...................................... 128
5.27.5 Create External LANs (=ELANs) to External Switches ................................... 129
5.27.6 Glue it all together: Create VLANs ................................................................... 131
5.28 Full Feature Ready (=FFR) ............................................................................ 136
5.29 PoE in Detail ................................................................................................... 136
5.29.1 PoE Budgets .................................................................................................... 136
5.29.2 Calculation ....................................................................................................... 137
5.29.3 PoE Example1: No External Limitation, low voltage PSUs ............................. 137
5.29.4 PoE Example2: External Limitation, low voltage PSUs ................................... 137
5.29.5 PoE Example3: External Limitation, mix of low and high voltage PSUs ......... 138
5.29.6 PoE FAQ .......................................................................................................... 138
5.30 Media Redundancy Protocol (MRP) ............................................................. 139
5.30.1 General ............................................................................................................ 139
5.30.2 MRP Operation (short description) .................................................................. 139
5.30.3 Fetch the MRP license from the OTNnet ......................................................... 140
5.30.4 Install the MRP license on the node ................................................................ 140
5.30.5 Activate the MRP license on the Node ............................................................ 140
5.31 Loop-Free / Loop-Aware Mode: No STP Worries in Loop-Free mode (no Layer2
loops in design)! ............................................................................................ 141
5.31.1 General ............................................................................................................ 141
5.31.2 External Loops ................................................................................................. 141
5.31.3 Loop-Free / Loop-Aware Mode ........................................................................ 142
5.31.4 Tuning Parameters .......................................................................................... 142
5.31.5 VLAN-MSTi Mapping Table / Network Interruptions ........................................ 144
5.32 Layer3 View .................................................................................................... 145
5.32.1 General ............................................................................................................ 145
5.32.2 Example Network ............................................................................................. 145
5.33 Wizard Load Page/Load Into Live Network ................................................. 149
5.33.1 General ............................................................................................................ 149
5.33.2 Close Button .................................................................................................... 149
5.33.3 Get Load Scenarios Button .............................................................................. 149
5.33.4 Load Button ...................................................................................................... 150
5.34 Going Online Licenses Vouchers .......................................................... 151
5.34.1 Normal Situation .............................................................................................. 151
5.34.2 Error Situations ................................................................................................ 153
6. EXTERNAL DEVICES / OTN DEVICES / MIB-2 .............................................. 156
6.1 Monitoring and Alarming on a Device ......................................................... 156
6.2 Configure Alarm Rules via MIB-2 ................................................................. 156
6.3 Example MIB-2 Alarm: Alarm Rule in OMS-FEM Alarm in OMS GUI .... 158
6.3.1 How the Alarm Rule was created .................................................................... 158
6.3.2 The Monitoring and Alarm Generation in OMS GUI ........................................ 158
6.4 Disconnecting a Device / Clearing Alarms .................................................. 159
6.5 Configuring a Device ..................................................................................... 159
7. SERVER-CLIENT ENVIRONMENT, REMOTE OMS-FEM ............................... 160
8. SCRIPTING...................................................................................................... 161
8.1 General ............................................................................................................ 161
8.2 Components Identifiers or URLs .................................................................. 161
8.3 Command Examples ..................................................................................... 162
8.4 Writing a Scripting File .................................................................................. 162
8.5 Executing a Scripting File ............................................................................. 162
8.6 Full Command List......................................................................................... 163
9. LAYOUTING THE OMS-FEM .......................................................................... 164
9.1 Dropping Zones ............................................................................................. 164
9.1.1 Master Dropping Zones ................................................................................... 164
9.1.2 Global/Sub Dropping Zones ............................................................................ 164
9.2 Choose a Window/Tab and let it Float ......................................................... 165
9.3 Place Floating Window/Tab via Layout Navigator Tool ............................. 166
9.3.1 Place Window/Tab in Master Dropping Zones ................................................ 166
9.3.2 Place Window/Tab in Global/Sub Dropping Zones ......................................... 167
9.4 Change Order of Tabs within a Window ...................................................... 169
10. MONITORING .................................................................................................. 170
10.1 General ............................................................................................................ 170
10.2 MSTP Monitoring ........................................................................................... 170
10.3 Port Counters Monitoring ............................................................................. 172
10.4 VRRP Monitoring ........................................................................................... 175
10.5 IGMP Snooping Monitoring .......................................................................... 177
10.6 IGMP Monitoring ............................................................................................ 179
10.7 PIM-SM Monitoring ........................................................................................ 181
10.8 OSPF Monitoring............................................................................................ 184
11. TROUBLE SHOOTING .................................................................................... 188
11.1 My Traffic is Not Coming out of this Port? ................................................. 188
11.2 Port Counters ................................................................................................. 188
12. NODE/SERVICE RENAMING .......................................................................... 188
13. ABBREVIATIONS............................................................................................ 188

1. INTRODUCTION
1.1 General
The N50/N70 series nodes are non-modular nodes with a network card functionality and an extended
Layer2/Layer3 Ethernet interface.
The OMS Front End Manager or OMS-FEM is an OMS extension and necessary to configure that
extended Layer2/Layer3 Ethernet interface. The OMS-FEM is a Server/Client environment, where the
client provides a GUI environment.
More specifically, following elements/features/protocols can be configured via the OMS-FEM GUI:
front-end ports of the N50/N70 series nodes
LAG (Link Aggregation)
External LAN
VLAN
MSTP
Virtual Router (=License: Enhanced License Pack as of two or more virtual routers per node)
Static Routing
VRRP (Virtual Router Redundancy Protocol) (=License: Enhanced License Pack)
IGMP Snooping
IGMP (=License: Enhanced License Pack)
Access Control Lists, IP and MAC based
PoE (Power over Ethernet) (=License: PoE for 24 or 48 ports)
Port Mirroring
QoS (Packet Storm Control, Flow Control, Rate Control, SLAN and Congestion Control)
Jumbo Frames
Port Counters
DHCP Relay / Server
OSPF (=License: Enhanced License Pack)
PIM (=License: Enhanced License Pack)
MRP (=License: Media Redundancy Protocol)

1.2 Referenced Documents
The table below is an overview of the documents being referred to in this document, & refers to the
language code and * refers to the document issue.

Ref. Number Title
[1] AG-M330-&-* OMS (OTN Management System) User Manual
[2] BB-M412-&-* N50/N70 Series Node: N5024C/N5024CF/N5048C N7024C/N7024CF/N7048C
[2] BB-M413-&-* N50/N70 Series Node: N5224C, N7224C
[3] AF-M155-&-* OTN TRM Modules (OTRs, STRs, SFPs)
[4] AA-M205-&-* OTN Installation and Operation Manual
[5] EB-M770-&-* Industrial Ethernet Switch ETS-3GC7F, ETS-4GC24FP
[6] EB-M771-&-* ETS-3GC7F Integration in OTN
[7] AG-M425-&-* User Management Tool

2. PREREQUISITES
2.1 General
OMS-FEM GUI users are expected to have a reasonable amount of Ethernet technology knowledge,
including some Ethernet protocols such as MSTP, LACP, routing protocols,
Acting or configuring the OTN network without common sense or without the required Ethernet
knowledge may cause an instable or unreliable OTN network.
Using the OMS-FEM GUI requires at least that the OMS software has been installed. The OMS-FEM
GUI must be started from the OMS GUI. Furthermore, when using features like PoE24, Enhanced
Ethernetvouchers must be purchased first, see also next paragraph.
2.2 Serial Key & License Pack
If you need one of the following features on the N50/N70 nodes, licenses or vouchers must be
purchased:
PoE 24 Ports (Power over Ethernet)
PoE 48 Ports (Power over Ethernet)
Enhanced License Pack (L3 services: VRRP, Virtual Router, IGMP, OSPF, PIM-SM)
MRP (Media Redundancy Protocol)
Licenses must be purchased per node, so for example if the feature PoE24 Ports is necessary on
three nodes, and the Enhanced License Pack is necessary on five nodes, a total of 3+5=8 licenses
must be purchased.
The N50/N70 nodes licenses concept consists out of three parts:
Serial Key (see 6.1)
Vouchers (see 6.2)
License Pack (see 6.3)
All the processing on Serial Keys, Vouchers and License Packs must be done via the OTN OMS
Licenses Tool on OTNnet. If you dont have an OTNnet account yet, contact your sales manager.
If you have an OTNnet account, this tool can be started via https://extranet.otnsystems.com login, and
select OTN OMS Licenses in the Project Selection List.
A screenshot of the OTN OMS Licenses Tool can be found in Figure 26.

2.2.1 Serial Key
A Serial Key is necessary as of OMS v9.0 for your OMS installation and can be obtained completely
free at any time via the OTN Licenses tool on OTNnet.
Also if an upgrade is performed from an older OMS version (v3.x,4.x,5.x,6.x,7.x) to OMS v8.x or
higher, a Serial Key is required.
The Serial Key generated by this tool must only be used for one unique single OMS installation.
Furthermore, using OMS redundancy requires only one Serial Key. The Serial Key always starts with
N1 and looks as follows:
N1-aaaa-aaaa-aaaa-aaaa-aaaa-aaaa
This Serial Key is necessary to generate your License Pack.

2.2.2 Voucher
A Voucher is a unique number that identifies a specific feature (e.g. Power over Ethernet, Enhanced
License Pack) that can run on one N50/N70 node.
If you need a specific feature for 'n' N50/N70 nodes, an amount of 'n' vouchers of that feature must be
purchased.
Finally, OTN Systems will send you all the voucher(number)s in an email. These voucher(number)s
are necessary further on to get your License Pack. A voucher always starts with Vn and looks as
follows.
V1-aaaa-aaaa-aaaa-aaaa-aaaa-aaaa
V2-aaaa-aaaa-aaaa-aaaa-aaaa-aaaa
....
Vn-aaaa-aaaa-aaaa-aaaa-aaaa-aaaa
E.g V1 represents the PoE 24 ports feature, V2 represents the Enhanced License Pack....

2.2.3 License Pack
A License Pack unites or links your Serial Key with your ordered Vouchers into one encrypted License
Pack file. The License Pack file must be created via the OTN Licenses tool on OTNnet based on the
Serial Key and the obtained Vouchers.
The obtained License Pack file must be installed on your OMS PC (see 5.34) to activate the ordered
Vouchers (features) on the intended nodes.
License Pack file = *.dat file
If no specific features are necessary on any node, no vouchers must be ordered, and as a result, no
License (Pack file) is required.

2.2.4 Licenses in a Live System
See 5.34.

Page 10 of 189 BG-M370-E-8
3. GETTING STARTED
3.1 Installation
The OMS-FEM will be installed together and automatically with the OMS installation on the OMS PC,
see OMS manual Ref.[1]. Just make sure during the OMS installation that Yes is activated in the
screenshot below. As a result, the OMS-FEM processes are activated when starting the OMS
Console. If No was selected during installation, the parameter OMS Front End Manager
Enabled must be set to True later on in the OMS Console, see 3.3.

3.2 Connection to the OTN Network
In order to configure the OTN network, two distinct IP connections via RJ45 must be made from the
OMS PC to the OTN network first:
OMS Communication Channel to configure the OTN network infrastructure, create nodes,
services, SLANs This connection can be made to the OMS connector on any OTN-X3M
network card or N50/N70 series node in the OTN-X3M network. This connection provides
access to a virtual OMS communication channel along the OTN-X3M ring.
Management Channel to configure the Ethernet front ports on the N50/N70 series nodes in the
OTN-X3M network. This connection must be made to the MGT connector on one of the
N50/N70 series nodes in the OTN-X3M network or one of the ethernet front ports [1..12] on the
ET100DAE card, or one of the ethernet front ports [1..5] on the ET100AE card. This
connection provides access to a SNMP communication channel along the OTN-X3M ring.

3.3 Start Up OMS-FEM Server
1. In the OMS Console, make sure that the OMS Front End Manager Enabled = True via Edit
Options... General General. This is OK already if Yes was selected during installation
(see 3.1). See also Chapter Startup/OMS logon in the OMS Manual, see Ref. [1].

OMS
MGT
BG-M370-E-8 Page 11 of 189

2. As a result, an extra section OMS-FEM Server appears in the OMS Console.

3. Click Start Server(s) in the OMS Console.
4. Wait until the Server Output window in the OMS Console displays OMS Kernel was successfully
started.... Both the OMS Server and OMS-FEM Server window must turn green. From now on,
both servers are started successfully.

OMS Front End Manager:
Enabled = True
Selected database
OMS Kernel successfully started
Green = started up Green = started up
Page 12 of 189 BG-M370-E-8
3.4 Start Up OMS-FEM GUI
1. From the OMS GUI on the OMS PC, start the OMS-FEM via Tools Start OMS FEM. This is
only possible if:
the logged on user in the OMS GUI has the access right to start the OMS-FEM. If Tools
Start OMS FEM has been greyed out, contact your network administrator for further
processing. OMS users and their access profiles are configured as described in Ref. [7].
In the OMS Console, parameter : Edit Options... General General OMS Front
End Manager: Enabled = True.

2. Following window passes through:

3. The window below pops up. The network shown in the Network View is the network already
created via the OMS GUI. The lines that connect the nodes are a result of creating ethernet
services (GET, ET100HX4 or ET100) in the OMS GUI between the segment ports (or SLANs) of
the N50/N70 series nodes:

BG-M370-E-8 Page 13 of 189
4. TREEVIEW & FIELDS DESCRIPTON
Click in the Equipment treeview to expand/collapse the equipment objects or network elements. If you
select a network element, e.g. Port GE2, the Equipment Properties window automatically contains
the properties of the selected network element.

As an example, expand the State Information line in the Equipment Properties window to show the
available fields.

In the OMS-FEM, there are four field types possible regarding to the equipment objects (or network
elements):
Click to
Expand /
Collapse
Possible
Field
types
Page 14 of 189 BG-M370-E-8
1. LocalControl Field
2. NetworkControl Field
3. NetworkStatus Field
4. NetworkStatusAlarm Field

4.1 LocalControl (LocCtrl) Field
A LocalControl field is a single writeable field (=dark grey color, without a little square box at the end),
which is only used for local purposes, e.g. to define the name of the external LAN. The information of
the LocalControl field is never written into the live network. After entering the value, press the ENTER
key and click the Apply button to configure the value in the OMS-FEM.

4.2 NetworkControl (NetCtrl) Field
A NetworkControl field is used to configure a property in the live network. This field is a duo-field
(=first+second field), that is recognized by the little square box at the end. Clicking the little square box
opens up the second field of the duo-field. Clicking the little box again closes the second field.
First field: the configured value of this property, is a writeable field (=dark grey color) to enter
the value of the network property; After entering the value, press the ENTER key and click the
Apply button to configure the value in the live network. The change in the live network will
occur almost immediately.
Second field: the measured value of this property in the live network. If the measured value is
different from the configured value, an alarm is raised and sent to the OMS. The little box will
then be coloured according the alarm: orange, red.

Click to
show/hide
second field
First field:
Configured value
in the database
Second field:
Measured value
in the network
BG-M370-E-8 Page 15 of 189
4.3 NetworkStatus (NetStat) Field
A NetworkStatus field is a status field from the live network and represents the measured value. This
field is a single read-only field (=light grey color, without a little square box at the end).

4.4 NetworkStatusAlarm (NetStatAl) Field
A NetworkStatusAlarm field is a status field from the live network. This field is a duo-field
(=first+second field), that is recognized by the little square box at the end. Clicking the little square box
opens up the second field of the duo-field. Clicking the litte box again closes the second field.
First field: the measured value in the live network of this status property, is a read-only field
(=light grey color).
Second field: the expected value configured by the administrator, is a writeable field (=dark
grey color). If the measured value is different from the expected value, an alarm is raised and
sent to the OMS. The little box will then be coloured according the alarm: orange, red.
Example: If you want that the operational status of the port is up, configure the expected
value to up and click Apply. If the measured value is up, no alarm will be generated. If the
measured value is down, an alarm will be generated to the OMS.

Click to
show/hide
second field
First field:
Measured value
in the network
Second field:
Configured
expected value
Page 16 of 189 BG-M370-E-8
5. OPERATION AND CONFIGURATION
5.1 Menu Structure

Menu Item Description

Exit:
Exit/close the OMS-FEM.

If a specific view was closed for some reason, it can
be opened again via this menu. Specific views
cannot be deactivated or closed via this menu
though.
View Basic Windows:
(views of the configured database) These are the
windows that are opened by default when starting up
the OMS-FEM;
V the View is still open
(no V) the View was closed or hidden,
but can be opened again via clicking this
item.
View Views:
(views of the configured database) If some features
or protocols are viewed via right-clickView, a view
tab [V]<feat/protocol> will appear in the central body
of the OMS-FEM, all these tabs can be selected via
a listing under View Views;

View Monitors:
(views or monitoring of the live network); a
monitoring tab [M]<feat/protocol> will appear in the
central body of the OMS-FEM, all these tabs can be
selected via a listing under View Monitors;

View Properties:
(views of the configured database) If some
feature/port/nodeproperties are viewed via right-
clickView properties, a properties tab or window
will appear, all these properties windows can be
selected via a listing under View Properties;

Configuration of the Equipment, VLANs (and its L2
features), Transparent Channel, Virtual Routers
(and its L3 features).
Further Traffic Control including Security, Control
and Quality of Service (Qos) can be configured as
well.
Load Network:
Loads the configured/created settings from all the
nodes in the OMS-FEM into the live network.

BG-M370-E-8 Page 17 of 189

About:
Indicates the used OMS-FEM version.

License Information:
Indicates the used OMS Serial Key and the used
vouchers, e.g. PoE 24 ports, Enhanced License
Pack., see also 2.2 and 5.28.

5.2 Functional Blocks
The OMS-FEM has four big functional blocks which can be found in the figure below:

Equipment: This area shows the configured infrastructure hardware (nodes, ports created in the
OMS GUI) and LAGs (if anycreated in the OMS-FEM GUI). This information is visualized via a
treeview. The OMS-FEM GUI automatically synchronizes on the fly with the OMS GUI.
Nodes:
Create: via OMS;
Configure: via OMS;
View: via OMS and OMS-FEM;
Delete: via OMS and OMS-FEM if no SLANs, VLANs are configured on the node;
Equipment
(Hardware, nodes, ports, LAGs...)
Resources
(SLANs, Ext. LANs, VLANs, features...)
Network View
Event Log View
Page 18 of 189 BG-M370-E-8
Front Ports:
Created automatically via node creation in OMS;
Configure
View: via OMS-FEM;
Delete: not possible

Network View: This is a fixed view which cannot be closed or deleted, this view is always
available and shows in a graphic way the configured network so far. The dotted lines indicate the
configured External LANs, the solid lines indicate the configured SLANs (configured via services
in OMS). If an object (node, port, External LAN, SLAN, .) is selected in one of the Equipment or
Resources treeviews, it will be highlighted in blue accordingly in the Network View.
Resources: SLANs/External LANs/VLANs/L2 Features/Virtual Routers/L3 Features/Other:
This is a tabbed treeview and depending on the selected tab, the resource data is shown
accordingly.
Event Log View: Shows all the passed events.

5.3 OMS GUI OMS-FEM GUI
When nodes are created in the OMS GUI, they will be automatically taken over and visualized in the
OMS-FEM GUI.
SLANs (=Segmented LANs) for the N50/N70 series nodes must be created in the OMS GUI via
creating an ethernet service (GET, ET100HX4 or ET100). This SLAN will be taken over automatically,
synchronized on the fly and visualized in the OMS-FEM GUI.

OMS GUI:
Node Creation
OMS-FEM
OMS GUI:
GET Services
automatic
automatic
BG-M370-E-8 Page 19 of 189
5.4 Node
5.4.1 General
The network, subnetwork and nodes are created in the OMS GUI. The OMS-FEM automatically
synchronizes to the OMS GUI to display all the created nodes.
In the paragraphs further on, following information can be found:
Node Properties, see 5.4.2
Node Actions, see 5.4.3
Node Info Example, see 5.4.4
Node View, see 5.4.5

5.4.2 Node Properties

Page 20 of 189 BG-M370-E-8
Parameter Field
Type
Value Description
Generic Information
Name NetStat <text> Indicates the logical node name.
For N50/N70 Series Node, this is based on the
subnetwork and node name assigned in the OMS
GUI : <subnetwork name>-<node name>.
Location NetCtrl <text> Fill out a logic location for the node e.g. Node at
Brussels Station.
Type NetStat N5024C/N5048C
N5024CF/N5224C
N7024C/N7048C
N7024CF/N7224C
Indicates the node type that is configured in the
OMS GUI or the device type that is configured in
the OMS-FEM.
MGT IP Address LocCtrl <a.b.c.d> Indicates the ManaGemenT IP Address linked to:
the Front-End of the N50/N70 series node;

This IP address is factory set and cannot be
changed by the user. This IP address can also be
viewed via the OMS GUI and Interactive Display
on the N50/N70 series node.
MGT Netmask LocCtrl <a.b.c.d> Indicates the ManaGemenT IP Address Netmask.
This value is factory set and cannot be changed by
the user. This IP address can also be viewed via
the OMS GUI and Interactive Display on the
N50/N70 series node.
MAC Address NetStat Value Indicates the MAC Address of the node. This
address is factory set and cannot be changed by
the user.
PollInterval LocCtrl Value (milliseconds) Poll interval in milliseconds, for the OMS-FEM
polling the live network. Default value = 5 ms.
MAC Address Aging
Time
NetCtrl Value (seconds) Indicates the time-out value for the dynamic learnt
MAC address table. Default value = 300 s.
State Information
Line State NetStat Online
Offline
Indicates whether the OMS-FEM is Online or
Offline
Connection State NetStat Offline
Reachable
Unreachable
Measuring
Faulty
Offline: The OMS-FEM is offline, network element
cannot be measured.
Reachable: The network element is measured in
the live network.
Unreachable: The network element is configured
(changes are made to the database), but the con-
figuration is not yet loaded into the network.
Measuring: The OMS-FEM is measuring or dis-
covering this node.
Faulty: ***
Recovery State NetStat Ok
ClearInProgress
RollbackInProgress
Ok: The node is up and running, everything fine.
ClearInProgress: If a ClearFrontEnd action is
performed on the node, the Recovery State will
show ClearInProgress.
RollbackInProgress: rollback on a node is in
progress;
Alarm Status NetStat Unknown
In Service
OutOfServiceMajor
OutOfServiceCritical
Unknown: ***
In Service: Everything fine, no alarms;
OutOfServiceMajor: Alarm situation;
OutOfServiceCritical: Occurs when a rollback of
the node configuration is required.
BG-M370-E-8 Page 21 of 189
PoE Information (Node) (see also 5.29)
Oper Status NetStat On
Off
Faulty

On: PoE module is up and running
Off: PoE module is down
Faulty:
-PoE module is missing on the motherboard or on
the plug-on board, or no communication with one
of these PoE modules.
-PoE module has been shut down by the node
itself after 5 node reboots due to lack of available
PoE power. The node is still up and running but
no more PoE power delivered. Solve the problem
(remove some PoE devices or disable PoE on
some ports) and Re-enable PoE Module, see
further.
PSU 1 Max. Power NetStat Value (W)
500/1000
Indicates how much total power (in Watt) PSU1
can deliver to the node. This value has been read
out from and configured in the OMS GUI field
PSU Power (Watt). This value does not indicate
the PoE budget, but will be used to calculate the
PoE budget available for PoE delivery further on,
see parameters PoE budget. ATTENTION: when
there is only one PSU in the node, Critical and
High priority ports cannot be configured, only Low
priority ports can be configured.

By default, 1000 W is always configured in the
OMS GUI, it is assumed that the PSU operates in
the high-voltage range, either AC or DC, and
delivers 1000 W.

PSU 1 Max. Power:
220 VAC 1000 W
110 VAC 500 W
48 VDC 1000 W
24 VDC 500 W
PSU 2 Max. Power NetStat Value (W) Similar to PSU1 Max. Power, but for PSU2.
Ext. Max. Power NetCtrl Value (W) Default=0 (=no limit), value in the range[0,..,1000]

Configures the External Maximum Power. This
value indicates a power limit per PSU due to a
limited external power source connected to the
N50/N70 PSUs. E.g. an external battery is
connected to the N50/N70 PSU and can only
deliver 600W instead of the theoretical 1000W
that a PSU(s) can deliver in the high voltage
range.

One 600W battery connected to one PSU Ext.
Max. Power = 600

One common 600W battery connected and
divided over two PSUs Ext. Max. Power = 300
Default Value = 0 indicates that there is no
External Maximum Power limit.
PoE Budget Crit. NetStat Value (W) Indicates how much power (in Watt) is available
for PoE delivery to Critical priority ports.
With one PSU configured, PoE Budget Crit.= 0
See 5.29 for the PoE Budget Calculation.
Page 22 of 189 BG-M370-E-8
PoE Budget High NetStat Value (W) Indicates how much power (in Watt) is available
for PoE delivery to Critical+High priority ports.
With one PSU configured, PoE Budget High= 0
See 5.29 for the PoE Budget Calculation.
PoE Budget Low NetStat Value (W) Indicates how much power (in Watt) is available
for PoE delivery to all the ports =
Critical+High+Low priority ports. See 5.29 for
the PoE Budget Calculation.
Total Consumed
Power
NetStat Value (W) Indicates the Total Consumed Power from all
ports together in one node, e.g if 4 cameras are
connected to 4 ports, each consuming 5 Watt,
then the Total Consumed Power will be 4*5W =
20W for this node.
Re-enable PoE
Module
LocCtrl Reset/No Must only be used when Oper Status (node-
level) is Faulty and Operation Status (port-level)
is OtherFault. If the offered power from the
PSU(s) to the node is not enough to deliver the
required PoE power to the PoE Clients, the node
will reboot. If after this reboot there is still
unsufficient power, the node will reboot again.
This behaviour can repeat itself a maximum of 5
reboots. After 5 reboots, the node will disable the
PoE board resulting in no more power being
delivered to the PoE Clients. Oper Status (node-
level) will turn into Faulty.
After a technician has solved the power problem
on-site, the PoE module must be re-enabled
again via selecting Reset and click the Apply
button. The connected PoE devices will get PoE
again.
MRP Information
MRP Protocol NetCtrl Enabled
Disabled

Enabled: Enable the MRP (=Media Redundancy
Protocol) on this node, refer to IEC 62439-2. A
purchased license is needed on every node
where this protocol must be enabled. See also
5.30.

Disabled: Disable the MRP on this node.

5.4.3 Node Actions
Right-click on a node to show a pop-up with possible actions on that node.

BG-M370-E-8 Page 23 of 189
Action Description
View Creates a new tab in the central body (where the network view tab is located) of the
OMS-FEM, with a detailed graphical view of the selected node. See 5.4.5.

View
properties
Generates a floating window with the Node properties.

Node Info See 5.4.4.
Add
Loopback
Interface
Creates or adds a Loopback Interface to the node. The loopback interface is a virtual
interface meant for management purposes. This interface can be added to a Virtual
Router. In the Virtual Router, an IP address must be assigned and can not be in the
range 127.x.x.x/24. Other IP addresses must always have subnetmask /32. (x.x.x.x/32).

This interface will be mainly used by the PIM-SM and the OSPF protocol. See PIM-SM
in 5.23 and OSPF in 5.22.
NOTE: This interface cannot be added to a VLAN.
NOTE: To remove the Loopback Interface, see 5.6.3.
Page 24 of 189 BG-M370-E-8

Load Loads the OMS-FEM database configuration of this individual node directly into the live
network.
Clear
Frontend
A Clear Frontend initiates a warm restart from the switch logic on the node (=restarting
the Front End control plane without rebooting the node, the node itself stays in service).
As a result, the settings, made by OMS-FEM, are cleared in the live network, and
loaded with default front-end values instead. This means clearing the:
- front port settings
- SLAN port settings
- Ethernet features (e.g MSTP),
- Ethernet protocols (e.g IGMP Snooping)

The programmed services in OMS are not cleared.
A Clear Frontend also influences the node property Recovery State. Its value turns
into ClearInProgress.
Rollback A rollback goes back to the previous valid situation for that node. A rollback action must
only be done when a specific configuration turns into an error situation for that node. A
pop-up with rollback required message will pop-up. If a rollback fails for some reason,
Clear FrontEnd followed by a Load in this node might be a solution.
Reboot
Front End
A Reboot Front End initiates a warm restart from the switch logic on the node
(=restarting the Front End control plane without rebooting the node, the node itself
stays in service). As a result, the settings made by OMS-FEM, are NOT cleared in the
live network. The switch on the node will be reloaded with the configured values after a
warm restart. The programmed services in OMS are not cleared.
Use this setting if you want to clear the switch logic on the node, e.g. clearing learned
ARP tables, MAC tables, etc. As a result, your virtual router has to learn everything
again from scratch. It initiates a fresh restart of the switch logic on the virtual router.

Result of
Add Loopback Interface
BG-M370-E-8 Page 25 of 189
5.4.4 Node Info Example
The Node Info tab can be opened via right-clicking a node and selecting Node Info. This tab is indicated by
[I]Node:<url> and shows more Node information based on selected CLI commands. See figure below:

Categories: Lists the available command categories, e.g: Equipment, VLAN, L2 -, L3-,

Commands: Lists the available commands, depending on the chosen category, as an example
the category VLAN has been chosen, see figure below.

Parameters: Depending on the chosen command, some required or optional parameters can be
filled out. Click first to check whether there are any and fill out the necessary values in the
shown parameters. In this example the VLAN ID must be filled out. After filling out a parameter,
make sure to press the Enter button on the keyboard to activate the Execute button. See figure
below:

Execute button: Click this button to execute the command with its required/optional parameters.
Output window: The result of the command execution is shown in this output window.
Node Info ([I]) tab
Page 26 of 189 BG-M370-E-8

Info button: Shows the port mapping info in the output window. These mappings are necessary
to interpret the output of the executed commands. The example below shows that SLAN port
SLAN9 is a member of VLAN 9.

Clear button: Clears the output window.
Save to File: If this checkbox has been checked, the command execution result is also written into
a log file located in <OMS install. path>/logging/Node Info/CLI_<subnetwork>-<node name>.txt.

History Repeat Button: this list shows a history of the executed commands so far. The most
recent commands are on top of the list. These listed commands can be executed again, with their
parameters already filled out, by selecting a command and clicking the Repeat button.

Port labels used
in OMS-FEM
Port labels used
in Node Info
Commands
example
... ...
Port
mapping
BG-M370-E-8 Page 27 of 189
5.4.5 Node View
Right-click on a node in the equipment treeview and click View. A new Node View tab (e.g. tab:
NODE://X3M-2500-StationA) of this node will be created in the central body of the OMS-FEM. See
figure below.
By default, no resource selector is activated. The resource selector is a little toolbar, located in the
top right-hand corner of the Node View tab. By clicking a resource icon in this toolbar (e.g. LAG icon or
VLAN icon or..), the Node View will highlight these resource elements (e.g ports, paths, ) within
this node. See pictures further on. Via the mouse-scroll button, zooming in/out the Node view is
possible.

a. LAG View
In the figure below, click the LAG (Link Aggregation Group) icon in the resource selector to show all the ports of
that node that are involved in one or the other LAG. If there are multiple LAGs configured on that node, multiple
colors will be used.

The LAG ports of that node can also be viewed in the equipment treeview, by clicking the LAG icon and expand-
ing the treeview.

Right-click node
View
Resource
Selector
Node StationA,
no resources selected
SLAN (or segment) ports,
Loopback Interfaces
Ethernet front panel ports
Used front ports
have coloured LEDs
Node View Tab
Station A
LAG ports
Station A
LAG ports
Click LAG
icon to show
LAG ports
Page 28 of 189 BG-M370-E-8
b. VLAN/Transparent Channel View
In the figure below, click the VLAN icon in the resource selector to show all the front and SLAN ports
of that node that are involved in one or the other VLAN or Transparent Channel. The entire path from
front port up to the involved SLAN port is shown. If there are multiple VLANs or Transparent Channels
configured on that node, multiple colors will be used. The VLAN or Transparent Channel ports of that
node can also be viewed in the VLANs or Transparent Channels tab treeview, by clicking the VLAN
or Transparent Channel icon and expanding the treeview.

By clicking the ? icon, you can highlight the entire VLAN or Transparent Channel path. This is
especially handy when multiple VLANs or Transparent Channels are configured on the node and
when the paths are crossing inside the node view.
c. SLAN/External LAN View
In the figure below, click the External LAN icon in the resource selector to show all the External
LANs/SLANs ports of that node. If there are multiple External LANs/SLANs ports configured on that
node, multiple colors will be used. An External LAN indication symbol is also shown beyond the node.
The External LANs/SLANs ports of that node can also be viewed in the SLANs tab or treeview, by
clicking the SLAN/External LAN icon and expanding the treeview.

Station A
Station A
Front port
Click VLAN icon to show
VLAN and Transparent
Channel ports
VLANs
Station A
SLAN port
Entire VLAN or
Transparent
Channel path from
FrontSLAN
VLAN ID
Click ? to show
entire VLAN or
Transparent
Channel path
Transparent
Channels
VLAN ID
Station A
Station A
SLAN port
Station A
External LAN port
External LAN (=ELAN)
Indication Symbol
Click External LAN icon to
show external LAN/SLAN
ports
BG-M370-E-8 Page 29 of 189

d. Virtual Router View
In the figure below, click the Virtual Routers icon in the resource selector to show all the Virtual
Routers configured in that node. If there are multiple Virtual Routers configured on that node, multiple
colors will be used. An Virtual Router indication symbol is also shown within the node.
The Virtual Routers of that node can also be viewed in the Virtual Routers tab or treeview, by clicking
the Virtual Routers icon and expanding the treeview.

e. PoE View
In the figure below, click the Ports icon in the resource selector to show all the PoE information for the
entire node. This is only a View, nothing can be configured here.

Station A
Virtual Router
Indication
Virtual Router
External LANs
Click Virtual Router icon to
show Virtual Routers in
selected node
Numbers = VLAN ID
2 Virtual Routers configured
in StationA
2 Virtual Routers configured
in StationA
Virtual Router
VLANs
Station A
PoESettings on
Node Level
Click Ports icon to show
Poe Settings on this node
PoESettings on
Port Level
Page 30 of 189 BG-M370-E-8
5.5 External/OTN Device
5.5.1 General
External Device: is a network communication device of an external product supplier different from
OTN Systems.
OTN Device: is one of the industrial Ethernet Switches listed below.
ETS-3GC7F: 10 ports switch = 3 Gigabit Combo + 7 Fast Ethernet ports;
ETS-4GC24FP: 28 ports switch = 4 Gigabit Combo + 24 Fast Ethernet With PoE ports;
NOTE: The N50/N70 Series Nodes are nodes and are not considered as an OTN Device as
such. External Devices and OTN Devices are pure OMS-FEM configurations and or
not synchronized with the OMS GUI. The only interaction between these devices and the
OMS GUI are the configured alarm rules in the OMS-FEM via MIB-2 that can raise an
alarm in the OMS GUI Alarm window whenever the alarm rule is triggered.
Creation: via the OMS-FEM.
Configuration: via launching a web browser or telnet in the OMS-FEM;
Monitoring and alarming: via configuring MIB-2 alarm rules on these devices in the OMS-FEM,
see 6.
In the paragraphs below, following information can be found:
Adding or create an External/OTN Device, see 5.5.2;
Device Properties, see 5.5.3;
Device Actions, see 5.5.4;

5.5.2 Adding an External/OTN Device into OMS-FEM
Before an External/OTN Device can be monitored via alarming, it must be added in the OMS-FEM
first.
1. In the OMS-FEM, click Configuration Equipment External Device / OTN Device: The left-
hand window below pops up for an External Device and the right-hand window for an OTN Device.
Fill out a Name and the MGT IP Address of the device. For an OTN Device, indicate the Type of
the device as well, either ETS-3GC7F or ETS-4GC24FP.

2. Click the Add button to add the device to the Equipment window in the OMS-FEM. After clicking
this button, indicates an External Device whereas indicates the OTN Device.

External
Device
OTN
Device
External
Device
OTN
Device
OTN
Device
Visual links after
adding the device
ports to an ELAN
BG-M370-E-8 Page 31 of 189

3. Expanding the External Device in the Equipment treeview will always show 4 ports for any
external device, even if the device has more than 4 ports. The OTN Device will show 10 ( ETS-
3GC7F) or 28 ( ETS-4GC24FP) ports depending on the selected type.These ports in the OMS-
FEM are only meant for configuring ELANs on and visualising them in possible network drawings
in the Network View. No further protocols can be configured on these ports. ELANs can be
configured as described in 5.8.

5.5.3 Device Properties

Parameter Field
Type
Value Description
Generic Information
Name NetStat <text> Indicates the logical node or device name.
For N50/N70 Series Node, this is based on the
subnetwork and node name assigned in the
OMS GUI : <subnetwork name>-<node name>.
Type NetStat ETS-3GC7F
ETS-4GC24FP
Indicates the device type that is configured in
the OMS-FEM; ETS-3GC7F and ETS-4GC24FP
External Device:
Supplier xyz
OTN Device:
ETS-3GC7F
OTN Device:
ETS-4GC24FP
7 Fast Ethernet
ports
3 Gibabit
Combo ports
4 Gibabit Combo
ports
24 Fast Ethernet
with PoE ports
4 Fast Ethernet
ports
External Device:
Supplier xyz
OTN Device:
ETS-3GC7F
OTN Device:
ETS-4GC24FP
Page 32 of 189 BG-M370-E-8
External Device indicate the OTN Devices.
MGT IP Address LocCtrl <a.b.c.d> Indicates the ManaGemenT IP Address linked
to:
- OTN Device;
- External Device

This IP address is used by the OMS-FEM to
connect to the device and to open the web
browser on the device for further configuration.
The MGT IP address of the device can be
changed by the user. See Ref. [5].
PollInterval LocCtrl Value (milliseconds) Poll interval in milliseconds, for the OMS-FEM
polling the live network. Default value = 5 ms.
State Information
Line State NetStat Online
Offline
Indicates whether the OMS-FEM is Online or
Offline.
Connection State NetStat Offline
Reachable
Unreachable
Measuring
Faulty
Offline: The OMS-FEM is offline, network ele-
ment cannot be measured.
Reachable: The network element is measured
in the live network.
Unreachable: The network element is config-
ured (changes are made to the database), but
the configuration is not yet loaded into the net-
work.
Measuring: The OMS-FEM is measuring or dis-
covering this device.
Faulty: ***
Recovery State NetStat Ok Ok: The device is up and running, everything
fine.
In Service
Unknown: Probably no connection between
OMS-FEM and this device**
In Service: Everything fine, no alarms;
SNMP Credentials (only for External Devices)
SNMP Version LocCtrl 2
3

Configure which SNMP version is used by the
External Device, either 2 (=SNMPv2) or 3
(=SNMPv3).
Community (v2) LocCtrl Public
(or see in manual of
External Device)
If SNMP Version = 2, fill out the userid needed
to authenticate to SNMP v2 on the external
device. A valid authentication gives the OMS-
FEM the rights to read out the external device.
SNMP User (v3) LocCtrl (see in manual of
External Device)
Fill out the userid needed to authenticate
(together with v3 Auth. Password) to SNMP v3
on the external device. A valid authentication
gives the OMS-FEM the rights to read out the
external device.
Auth. Password (v3) LocCtrl (see in manual of
External Device)
Fill out the password needed to authenticate
(together with v3 SNMP User) to SNMP v3 on
the external device. A valid authentication gives
the OMS-FEM the rights to read out the external
device.
Privacy Password (v3) LocCtrl (see in manual of
External Device)
Filling out this password makes sure to encrypt
the SNMP v3 commands. Not filling it out or
filling out a wrong password transmits plain text
commands without encryption.

BG-M370-E-8 Page 33 of 189
5.5.4 Device Actions
Right-click on a device to show a pop-up with possible actions on that device. The possible actions for
an External Device and OTN Device are the same, see figure below:

Action Description
View
properties
Generates a floating window with the device properties, see 5.5.3.
Delete Deletes the device from the OMS-FEM.
MIB
Browser
Opens the MIB-2 browser in the OMS-FEM which allows to configure alarm rules on
External and/or OTN Devices. When the configured alarm rule becomes active, it will
raise an alarm in the Alarm Window in the OMS GUI. For more information on
configuring alarms in MIB-2, see 6.
Launch
Web
Browser
Opens a web browser with URL http://<MGT_IP_Address>, e.g. http://192.168.1.4. Via
this website, it will be possible to further configure the External or OTN Device.
Launch
telnet
Opens a Windows telnet client and connects to <MGT_IP_Address>, e.g. 192.168.1.4.
Make sure that a Windows telnet client has been installed and activated as indicated in
the window below:

Connect Makes a connection between the OMS-FEM and this device. Connecting is necessary
to monitor or read out the MIB-2 on the device. Connecting all devices at once can be
done as well via the OMS-FEM menu Configuration Connect All Devices.
Disconnect Disconnects the OMS-FEM from this device. After disconnecting, monitoring will not be
possible anymore and all the device alarms will be cleared in the OMS GUI.
Disconnecting all devices at once can be done as well via the OMS-FEM menu
Configuration Disconnect All Devices.

Page 34 of 189 BG-M370-E-8
5.6 Ports
5.6.1 General
Following list shows the possible N50/N70 Port types:
ComboPort
PowerOverEthernetPort
LAG
PowerOverEthernetLAGPort
ComboLAGPort
SLANPort
Loopback Interface
All these ports with their properties are described in paragraph 5.6.2.
5.6.2 Port Properties
Front ports are located in the Equipment treeview (by default on the left-hand side) as part of a
node. Its properties can be viewed via clicking a port. Right-clicking a port and selecting View
Properties shows the properties in a separate window.
SLAN ports are located in the SLANs tab (by default on the right-hand side) as part of an SLAN.

Their properties can be viewed via clicking a port. Right-click a port and select View Properties to
show them in a separate window. Control fields or properties can also be configured via this window.

N50/N70ComboPort N50/N70PowerOverEthernetPort
PoE Available
N50/N70LAG N50/N70SLANPort
PoE Available
N50/N70ComboLAGPort N50/N70PowerOverEthernetLAGPort
SFP Info
N50/N70 Loopback Interface
BG-M370-E-8 Page 35 of 189
Parameter Field
Type
Value Description
Generic Information
Type NetStat <x>=N50/N70
<x>ComboPort
<x>PowerOverEthernet-
Port
<x>LAG
<x>ComboLAGPort
<x>PowerOverEthernet-
LAGPort
<x>SLANPort
<x>VirtualPort
<x>ComboPort: Front port, these ports
have both the RJ45 and SFP port. These
RJ45 ports also support PoE. All ports of
the N5024CF/ N7024CF node are
<x>ComboPorts. The SFP port always
has priority over the RJ45 port. If for
example no SFP module is plugged in,
and the RJ45 brings up the link first, the
RJ45 port will become active. If the SFP
port is plugged in as well later on, the
SFP port will be activated and the RJ45
port deactivated.
<x>PowerOverEthernetPort: Front port,
these ports are RJ45 ports that support
PoE. These ports do not have an SFP
port. All ports of the N50xxC / N70xxC
node are <x>PowerOverEthernetPorts.
See also see also 5.29.
<x>LAG: Combined Front port, these
ports are the result of bundling one or
more physical front ports into one logical
LAG port via the LAG Wizard.
<x>ComboLAGPort: <x>ComboPort
which is a member of a LAG port.
<x>PowerOverEthernetLAGPort:
<x>PowerOverEthernetPort which is a
member of a LAG port
<x>SLANPort: Segment port, these ports
are the N50/N70 node logic segment
ports, which provide access to the OTN
ring. These ports are also visible in the
OMS GUI.
<x>VirtualPort: Loopback Interface. See
Add Loopback Interrface in 5.4.3.
Number NetStat Value <x>=N50/N70
For an <x>ComboPort or
<x>PowerOverEthernetPort, this number
indicates the number of the front port on
the front panel.
For an <x>LAG, <x>SLANPort or
<x>VirtualPort, this number indicates an
internal identity number of this object.
Name NetStat Value <x>=N50/N70
Indicates the name of the port, eg GE5
indicates Gigabit Ethernet port 5. The Port
naming is as follows:
Page 36 of 189 BG-M370-E-8
<x>Combo(LAG)Port GE<n>
<x>PowerOverEthernet(LAG)Port
GE<n>
<x>LAG is LAG<n>
<x>SLANPort SLAN<n>
<x>VirtualPort LOOPBACK<n>
Description NetStat Value <x>=N50/N70
Indicates the description of the <x>LAG
port. This parameter can be configured via
the Link Aggregation Group wizard.
LACP NetStat Value <x>=N50/N70
Indicates whether LACP is
Disabled/Enabled in case of an <x>LAG.
LACP can be configured via the Link
Aggregation Group wizard.
State Information
In Service
OutOfServiceMajor
Unknown: ***
In Service: Everything fine, no alarms
OutOfServiceMajor: Alarm situation
Admin Status NetCtrl Down
Up
This field configures the administrative
state of the port.

Down: Set this value when you want to
disable or block the port.

Up: Set this value when you want to
enable or open the port.
Operation Status NetStatAl Up
Down
Testing
Unknown
Dormant
Not Present
Lower Layer Down
Indicates the operational status of the
port. E.g. if the port cable is missing or the
destination party is down, the operational
state will be Down, although the
administrative state is up. If the
administrative state is down, the
operational state will also be down.
After clicking the little square behind the
field, it is possible to configure one of the
expected values for the operational state:

Up
Down
Testing (future)
Unknown
Dormant (future)
Not Present (future)
Lower Layer Down (future)
If you set this expected value to Up, and
the measured value is Down, an alarm
will be generated.

BG-M370-E-8 Page 37 of 189
Specific Information
MTU
(Maximum
Transmission
Unit)
NetCtrl 1..9216 bytes Indicates the maximum frame size in
bytes, allowed to transmit by that specific
port.
For normal sized frames, the value 1500
is used. This represents in total 1518
bytes = 1500 bytes payload and 18 bytes
header.
For jumbo frames, set this value higher
than 1500 with a maximum of 9216.
Negotiation NetCtrl Auto
No Negotation
Auto: AutoNegotiation is used, and the
speed and duplex mode(s) are advertised
and negotiated with remote Ethernet
parties. Configured speed and duplex
mode in OMS-FEM are ignored.
No Negotiation: the duplex and speed
settings are not negotiated, but used as
configured in these parameters below.
Duplex Setting NetCtrl
(with No
Negotiation)
Full Duplex
Half Duplex
With No Negotiation, this setting
configures the port in Full Duplex or Half
Duplex.
Speed Setting NetCtrl
(with No
Negotiation)
10 Mbps
100 Mbps
1 Gbps
10 Gbps
With No Negotiation, this setting
configures the port in the assigned speed.
Flow Control NetCtrl Disable
Symmetric
Disable: Disable flow control, no pause
packets will be sent.

Symmetric: Enable flow control. In full-
duplex mode flow control is realized with
pause frames in accordance with
IEEE802.3x; in half-duplex mode flow
control is realized by forcing collisions
(back pressure).
ATTENTION: it is strongly advised not to
use Flow Control and Storm Control (see
below) together.
Total Storm
Control Level
NetCtrl Level Off
[Level117]
Level Off: disable Storm Control. All
incoming packets are processed, nothing
is thrown away.

Total refers to a sum of possible DLF, BC
and MC packets.
Level117: enable Total Storm Control.
Level1: only a minimum of packets
allowed, strong limitation of packets.
Level17: lots of packets allowed, weak
limitation of packets.
The stepsize between two levels depend
on the actual speed value (configured or
Page 38 of 189 BG-M370-E-8
negotiated):
10/100 Mbps:
step = 500 packets/s

1 Gbps:
step = 4000 packets/s

Example:
DLF Storm Control enabled
BC Storm Control enabled
MC Storm Control disabled
Level3
speed 100 Mbps

Result: Storm Control = 3*500 packets/s
= 1500 packets/s
Sum of (DLF + BC) packets is limited to
1500 packets/s.

ATTENTION: it is strongly advised not to
use Flow Control and Storm Control
together.
DLF Storm
Control Enable
BC Storm
Control Enable
MC Storm
Control Enable
NetCtrl Enable/Disable DLF: incoming unicast traffic with an
unknown destination
BC: incoming Broadcast traffic
MC: incoming Multicast traffic
If <x> Storm Control Enable is enabled,
<x> Storm Control will be part of the Total
Storm Control Level.

If <x> Storm Control Enable is disabled,
no <x> Storm Control will be done and all
<x> packets are allowed and passing
through.
Output Rate Limit NetCtrl 10..1000 Mbps 10, 20...1000: Limit the outgoing traffic
according the configured value.
Value 1000 allows the full traffic or
bandwidth, so nothing is limited.
Burst Size NetCtrl 4..16000 Kbytes The shaping is implemented by using a
token bucket principle. In the OMS-FEM
GUI, the bucket size is referred to as Burst
Size. The (maximum) number of tokens
that can exist in the bucket is 4-16000
Kbytes in steps of 4 Kbytes.
Default Priority NetCtrl 0..7 Set the default priority for incoming
frames.
PoE Settings (see also 5.4.5e, 5.29)
(These are configured settings by the Administrator)
Admin Status NetCtrl On
Off
On: Enable PoE on this port. When this is
done online, this will only succeed if you
still have PoE licenses available. If not,
Admin Status will stay Off. It still depends
on the Power Priority, Classes and
Budgets whether power will be delivered
effectively.
Off: Disable PoE on this port
BG-M370-E-8 Page 39 of 189
Description NetCtrl <text> Port description e.g. Camera train station
2
Power Priority NetCtrl Low
High
Critical
Assigns a Power Priority for PoE to the
port. Critical priority ports will always get
power first, Low priority ports will always
get power as last. High priority is in
between. Depending on the situation,
Power management is performed, See
5.29.
Power Class NetCtrl Unlimited
Class 1
Class 2
Class 3/0
Class 4
Configure the desired power class for this
PoE port. A connected PoE device to this
port will never get more power than the
Power Class for which the port was
configured. Use Unlimited (=40W) when
you dont know yet the Power Class of the
connected device (=Detected Class). As a
result, the device will always get power,
and its power class can be detected.
When it has been detected, the
administrator can change Unlimited into
the same class as the Detected Class.
Always keep in mind the maximum PoE
budget of 1612 Watt for the entire node.
According the configured Power Class,
following power levels are delivered at the
PoE ports by the node (=PSE side) :
Class 0: 15.4 Watt
Class 1: 4.0 Watt
Class 2: 7.0 Watt
Class 3: 15.4 Watt
Class 4: 32.0 Watt
Current Status NetStat Disabled
Searching
DeliveringPower
Fault
OtherFault
Testing
Indicates the operational PoE port status.
Find below the possible values:

Disabled:
- the port was disabled for PoE by admin
Admin Status = Off
- the port was enabled for PoE by admin
Admin Status = On
The port is disabled later on at run-time by
power management, e.g. due to a power
dip,.... The Admin Status stays On
though.

Searching: The Node is checking the
connected Power Device (PD) before
power delivery. The node negotiating the
class, priority... No power is delivered yet
to the PD.

DeliveringPower: There is enough power
budget left to deliver power to this PD, the
node is really delivering power to the PD.

Fault: There is an external problem on the
PoE line or port, e.g. the PD requests
power beyond its allowed power range.
No power is delivered to the PD.
Page 40 of 189 BG-M370-E-8

OtherFault: PoE chip has been disabled
due to external power problem having
already caused five reboots of the node.
See parameter Re-enable PoE Module
on node-level for more information.

Testing: Port in testmode.
Detected Class NetStat Class 0
Class 1
Class 2
Class 3
Class 4
Indicates the measured or detected power
class of the connected PoE device. By
default, when no PoE device is connected
yet, Class 0 is indicated. When the PoE
device (e.g. Class 2) is connected
afterwards, its Power Class (Class 2) will
be indicated. Afterwards, when the PoE
device has been removed, the last
remembered Power Class (Class 2) is still
displayed, although no device is
connected at that time.
PoE Diagnostics (see also 5.4.5e, 5.29)
(These are measured values from the live network.)
Consumed
Power
NetStat <value>W Indicates the consumed power that power
device (PD) currently is consuming.
Overload # NetStat <value> Indicates the number of overload
conditions so far. Each time the PD on this
port asks more power than its configured
class allows, the counter increases with
one.
Short # NetStat <value> Indicates the number of shortcut
conditions on this port so far.
Power Denied # NetStat <value> Indicates the number of times that power
delivery has been denied on this port.
Device Absent # NetStat <value> Indicates the number of times that power
has been removed because a powered
device dropout was detected.
Invalid Sig. # NetStat <value> Indicates the number of times that an
invalid signature on PD has been
detected. A signature indicates that a PD
is a valid PD or not.
SFP Information
Laser
WaveLength
NetStat 0 nm
850 nm
1310 nm
Indicates the laser wavelength in nm:
0 = default value, no SFP connected
850 = GBit_SX
1310 = GBit_LX
SFP Name NetStatAl EMPTY
UNKNOWN
CODE ERROR
<values>
Indicates the used SFP Name, e.g.
1000Base_SX. An overview of all the
valid SFPs or <values> can be found in
Ref. [3] .
Signal Status NetStat Optical signal OK
Loss of signal
Optical Signal Ok: everything fine
Loss of signal: SFP loss of signal
Optics NetStat Ok
Not Ok
Ok: the SFP hardware is OK
Not Ok: indicates a hardware failure in the
SFP, please replace the SFP
Optical
Transmitter Fault
NetStat Yes
No
Yes: SFP module indicates at least one
transmit fault
No: SFP module indicates no transmit
BG-M370-E-8 Page 41 of 189
faults
Temperature NetStat Value (C) Indicates the SFP temperature
Optical Transmit
Power (+/- 3dB)
NetStat Value (dBm) Indicates the optical transmitted TRM
output power in dBm; Check the
measured value with the Pout values in
the manual OTN TRM Modules (AF-
M155-&-*). Signal accuracy is only
guaranteed within the normal working
range, i.e. when Optical transmit power is
between Pout min and Pout max.
Optical Receive
Power (+/- 3dB)
NetStat Value (dBm) Indicates the optical received TRM input
power in dBm; Check the measured value
with the Pin values in the manual OTN
TRM Modules (AF-M155-&-*). Signal
accuracy is only guaranteed within the
normal working range, i.e. when Optical
receive power is between Pin min and Pin
max.

5.6.3 Port Actions
Right-click on a port to show a pop-up with possible actions on that port.

Action Description
View Properties Click to view all the properties from this port.
Remove Loopback Interface This action is only available on loopback interfaces. This interface can
only be removed when this interface is not in use anymore by other
protocols or virtual routers. Click this action to remove the loopback
interface from the node.

NOTE: To add a Loopback Interface see 5.4.3.

Page 42 of 189 BG-M370-E-8
5.7 Link Aggregation
5.7.1 General
The symbol below is used in the OMS-FEM menu and treeviews to indicate Link Aggregation.

A LAG (=Link Aggregation Group) is the bundling of different front ports (GE ports = Gigabit Ethernet
ports) of the same node into one logical port group. All the front ports of the source and destination
LAG must have the same speed, duplex mode and/or negotiation setting.
This LAG combines the bandwidth of two or more Ethernet/Combo physical links into one single logic
link. This solution also increases redundancy and availability of the link between the two parties.
The Link Aggregation is the communication between two or more LAGs. One LAG for example of an
N50/N70 series node, and another LAG for example of another N50/N70 series node/switch/
application
Licenses: No license is required for LAG.
5.7.2 Configuration
ATTENTION: Before opening the LAG wizard, make sure that all the front ports of the source and
destination LAG have the same speed, duplex mode and/or negotiation setting. If the settings are not
the same, the LAG will not work or the LAG wizard can block the creation of the LAG.
ATTENTION: A maximum of 8 LAGs can be created per node. A maximum of 8 ports can be added to
a LAG.
1. In the OMS-FEM, go via Configuration Equipment Link Aggregation Group. The LAG
creation wizard opens.
2. In the general information window below, click the Next >> button.

BG-M370-E-8 Page 43 of 189
3. In the window below, fill out or configure following fields:
Description: a short description for this LAG instance;
LACP (=Link Aggregation Control Protocol): Enable to activate LACP. LACP provides a
method to control the bundling of several physical ports together to form a single logical
channel. LACP allows a network device to negotiate an automatic bundling of links by sending
LACP packets to the peer (directly connected device that also implements LACP). If LACP is
disabled (=default), the LAG will still perform some kind of basic bundle negotiaton with the
other side.
Negotiation, Duplex Setting, Speed Setting, Flow Control: All the ports in the LAG will be
configured with the same negotiation, duplex, speed and flow control setting. See port
properties table in 5.6.2 (Port Properties) for a description of these parameters.

4. Select the desired node (via Node Selection, only one node can be selected) and its ports (via
Port Selection) that must be bundled into one LAG. A maximum of 8 ports can be inserted into
one LAG. Click the Next >> button to review the information.

5. The review page highlights the intentional front ports that are going to be configured in a LAG.
Click the Finish button to create and store the LAG in the database/OMS-FEM or click << Prev to
change the configured information.

Page 44 of 189 BG-M370-E-8

6. The wizard runs into its final page: the Load page, see 5.33 for all the options.

7. After a Close action, whether loaded or not, the created LAG and its properties are visible in the
Equipment and Equipment properties window on the lefthand side. In this example, the URL is
LAG://e-Node 36/LAG1. LAG1 is due to automatic numbering of the created LAGs per node.
LAG1 indicates the first created LAG for that node, LAG2 the second etc...

NOTE: It is possible that during the Port Selection, some or all other ports of that node cannot be
selected anymore (=disappear from the port selection list) after clicking a specific port. This
is because that node is part of one or more VLANs. If your selected port is part of a VLAN on
that node, only other ports from that same VLAN can be selected for this LAG, other ports
disappear from the selection list. If your selected port is an unused (configured) port on that
node, only other unused (configured) ports of that node can be selected, other ports
disappear from the selection list.

NOTE: The created LAGs on a node are also visible in the Node View (right-click Node View)
and then selecting the LAG icon in Select a View, see also 5.4.5a

LAG(part of a VLAN)
BG-M370-E-8 Page 45 of 189
5.8 External LAN
5.8.1 General
The symbol below is used in the OMS-FEM menu and treeviews to indicate External LAN.

An external LAN is a physical connection created between two or more front ports of an N50/N70
series node or a third party switch. The front ports that are part of this external LAN must be
programmed in the OMS-FEM.

Licenses: No license is required for External LAN.

5.8.2 Configuration
1. In the OMS-FEM, go via Configuration Equipment External LAN. The External LAN

Page 46 of 189 BG-M370-E-8
3. Fill out an External LAN Name.
4. Configure 802.1Q VLAN Trunking with one of the following values below and click Next >>
button to review the information:
All (=default): all incoming frametypes are allowed, no frames are thrown away based on the
frame type.
Tagged: only incoming frames with a VLAN ID (=tagged) are allowed, other frames are
thrown away based on the frame type.
Untagged/PriorityTagged: only incoming frames without a VLAN ID (=untagged) or with a
Priority tag are allowed, other frames are thrown away based on the frame type.

5. The review page shows the line connecting the selected nodes, which is the intentional External
LAN. Click the Finish button to create and store the External LAN in the database/OMS-FEM or
click << Prev to change the configured information.

BG-M370-E-8 Page 47 of 189

7. After a Close action, whether loaded or not, the created External LAN and its properties are now
visible in the SLANs tab and properties window on the right-hand side. In this example, the URL is
ELAN://ExtLAN1/.

NOTE: The created External LANs on a node are also visible in the Node View (right-click Node
View) and then selecting the External LAN icon in Select a View, see 5.4.5c.
Page 48 of 189 BG-M370-E-8
5.9 VLAN Port/External LAN to Segment Mapping
5.9.1 General
The symbol below is used in the OMS-FEM menu and treeviews to indicate VLAN.

A VLAN, is a group of hosts with a common set of requirements that communicate as if they were
attached to the same broadcast domain, regardless of their physical location. A VLAN has the same
attributes as a physical LAN, but it allows for end stations to be grouped together even if they are not
located on the same network switch. Network reconfiguration can be done through software instead of
physically relocating devices.
To physically replicate the functions of a VLAN, it would be necessary to install a separate, parallel
collection of network cables and switches/hubs which are kept separate from the primary network.
However unlike a physically separate network, VLANs must share bandwidth; two separate one-
gigabit VLANs using a single one-gigabit interconnection can both suffer reduced throughput and
congestion. It virtualizes VLAN behaviors (configuring switch ports, tagging frames when entering
VLAN, lookup MAC table to switch/flood frames to trunk links, and untagging when exit from VLAN.)
Licenses: No license is required for VLANs.

5.9.2 Configuration
1. In the OMS-FEM, go via Configuration VLAN. The VLAN creation wizard opens.

3. In the figure below, fill out a VLAN Name.
4. Assign a VLAN Id to the VLAN by filling it out or selecting it. The chosen VLAN Id can be verified
later on in the VLAN Properties window on the right-hand side in the OMS-FEM. VLAN ID '1' is not
BG-M370-E-8 Page 49 of 189
permitted, because it is the preconfigured VLAN that contains all unused (unconfigured) ports;
Maximum VLAN Id is 4095.
5. Select the front ports and/or LAGs that must be part of the VLAN and Click Next >>.

6. Select (=Add to VLAN) the External LANs (ELANs) and SLANs that must be part of this VLAN (id).
This is the step in which the front ports are mapped to the segment (or SLAN) or External LAN.
The untagged checkbox is also related to the configured 802.1Q VLAN Trunking feature on the
External LAN in 5.8.2. E.g. if Tagged is selected in the 802.1Q VLAN Trunking feature for a
specific External LAN, then the Untagged checkbox in this wizard will be greyed out and
disabled for this specific External LAN. Furthermore, if more than one ELAN is selected for the
same VLAN, only one of the ELANs can have untagged frames that are linked to that specific
VLAN. An SLAN can be part of only one VLAN which means that each VLAN can have its own
dedicated SLAN with guaranteed bandwidth.

Page 50 of 189 BG-M370-E-8
7. ATTENTION: In this page, the OMS-FEM will detect whether a Layer2 VLAN Loop is introduced
or not, see figures below (first figure: no loop detected = Loop-Free mode; second figure: VLAN
loop detected = Loop-Aware mode). More detailed information on Loop-Free/Loop-Aware mode
can be found in 5.31.

8. loop detected: Click the Ok button of the VLAN Loop Detected window.
9. Click the Next >> button to review the information.

10. The review page shows the intentional VLAN.

11. no loop detected (=Loop-Free Mode): Click the Finish button to create and store the VLAN in
the database/OMS-FEM or click << Prev to change the configured information.

No VLAN Loop
LOOP-FREE mode
Detected VLAN Loop by OMS-FEM
LOOP-AWARE Mode
BG-M370-E-8 Page 51 of 189
12. loop detected (=Loop-Aware Mode): Click the Start MSTP Wizard button to start the MSTP
wizard for the configured VLAN (MSTP wizard see 5.11). The OMS-FEM forces the operator
to create an MSTi for the configured VLAN. The operator can still cancel or close the MSTP
wizard, and the VLAN will still be created in the database, but the VLAN will not load into the live
network before and MSTi had has been created for the Looped VLAN.

13. no loop detected (=Loop-Free Mode): The wizard runs into its final page: the Load page, see
5.33 for all the options.

14. After a Close action, whether loaded or not, the created VLAN and its properties are now visible in
the VLANs tab and on the right-hand side. In this example, the URL is VLAN://VLAN2/.

NOTE: The created VLANs on a node are also visible in the Node View (right-click Node View)
and then selecting the VLAN icon in Select a View, see 5.4.5b.

LOOP-FREE mode
LOOP-AWARE mode
MSTP Wizard
Page 52 of 189 BG-M370-E-8
5.10 Transparent Channel QinQ
5.10.1 General
The symbol below is used in the OMS-FEM menu and treeviews to indicate Transparent Channel.

With Transparent Channel or QinQ, it is possible that a transmitted frame within a network can carry
multiple VLAN ids instead of just one. This means for example that a subnetwork A in city A can
communicate with subnetwork B in city B via a Transparent Channel over the common core network,
without disturbing configured VLAN ids in the core network.
For example:
Subnetwork A and B communicate in the same VLANs: eg via VLAN id 3,5,105
The core network has for example also VLAN id 5 configured.
Without the use of a Transparent Channel, VLAN 5 of Subnet A+B, would interfere with VLAN 5
of the core network, which is undesired.
With the use of a Transparent Channel, VLAN 5 of Subnet A+B, would not interfere with VLAN
5 of the core network.
Licenses: No license is required for Transparent Channel.

5.10.2 Prerequisite
Make sure that the SLAN that is going to be used as Transparent Channel, has the VLAN Trunking
field set to Tagged or All. Modifying this setting can be done as described in 5.27.4.

5.10.3 Configuration
1. In the OMS-FEM, go via Configuration Transparent Channel. The Transparent Channel

BG-M370-E-8 Page 53 of 189
3. In the figure below, fill out a Transparent Channel Name.
4. Assign a Channel ID to theTransparent Channel by filling it out or selecting it. The chosen
Channel ID can be verified later on in the Transparent Channel Properties window on the right-
hand side in the OMS-FEM. The Channel ID must be in the range [1..4082].
5. Select the front ports and LAGs that must be part of the Transparent Channel and Click Next >>.

6. Select (=Add to Transparent Channel) the External LANs (ELANs) and SLANs that must be part of
this Transparent Channel. This is the step in which the front ports are mapped to the segment (or
SLAN) or External LAN. The untagged checkbox is also related to the configured 802.1Q VLAN
Trunking feature on the External LAN in 5.8.2. E.g. if Tagged is selected in the 802.1Q VLAN
Trunking feature for a specific External LAN, then the Untagged checkbox in this wizard will be
greyed out and disabled for this specific External LAN. Furthermore, if more than one ELAN is
selected for the same Transparent Channel, only one of the ELANs can have untagged frames
that are linked to that specific Transparent Channel. An SLAN can be part of only one Transparent
Channel which means that each Transparent Channel can have its own dedicated SLAN with
guaranteed bandwidth. For a Transparent Channel SLAN, the Untagged checkbox will always be
unchecked.

Page 54 of 189 BG-M370-E-8

7. ATTENTION: In this page, the OMS-FEM will detect whether a Transparent Channel loop is
introduced or not, see figures below (first figure: no loop detected = Loop-Free mode; second
figure: Transparent Channel loop detected = Loop-Aware mode). More detailed information on
Loop-Free/Loop-Aware mode can be found in 5.31.

No Transparent Channel Loop
LOOP-FREE mode
Detected Transparent Channel Loop by OMS-FEM
LOOP-AWARE Mode
BG-M370-E-8 Page 55 of 189
8. Transparent Channel loop detected: Click the Ok button of the Transparent Channel Loop
Detected window.

9. Click the Next >> button. In the window below, select how Layer2 protocols (LACP, STP, GVRP,
GMRP, MVRP, MMRP) must be processed over the Transparent Channel. Each of these
protocols can be processed as follows:
Peer: The corresponding protocol is not limited to the transparent channel only, but can
interact with both the customer and OTN network.
Tunnel (=default): The corresponding protocol packets get transferred transparently through
the OTN network and will as a result not interact with this OTN network.
Discard: Block and/or discard packets of the selected protocol. Packets of the selected
protocol will not pass the Transparent Channel.


11. The review page shows the intentional Transparent Channel.

12. no loop detected (=Loop-Free Mode): Click the Finish button to create and store the
Transparent Channel in the database/OMS-FEM or click << Prev to change the configured
information.

13. loop detected (=Loop-Aware Mode): Click the Start MSTP Wizard button to start the MSTP
wizard for the configured Transparent Channel (MSTP wizard see 5.11). The OMS-FEM
forces the operator to create an MSTi for the configured Transparent Channel. The operator can
still cancel or close the MSTP wizard, and the Transparent Channel will still be created in the
database, but the Transparent Channel will not load into the live network before an MSTi has been
created for the Looped Transparent Channel.

14. no loop detected (=Loop-Free Mode): The wizard runs into its final page: the Load page, see
5.33 for all the options.

LOOP-AWARE mode
MSTP Wizard
LOOP-FREE mode
Page 56 of 189 BG-M370-E-8
15. After a Close action, whether loaded or not, the created Transparent Channel and its properties
are now visible in the Transparent Channels tab and on the right-hand side. In this example, the
URL is CHANNEL://TransChannel1/

NOTE: The created Transparent Channels on a node are also visible in the Node View (right-click
Node View) and then selecting the VLAN icon in Select a View, see 5.4.5b.

BG-M370-E-8 Page 57 of 189
5.11 MSTP
5.11.1 General
The symbol below is used in the OMS-FEM menu and treeviews to indicate MSTP (Multiple Spanning
Tree Protocol). By default, a common and internal spanning tree (=CIST, =not VLAN aware) is always
running on the N50/N70 series nodes, so if no specific MSTP is configured on a specific VLAN or
Transparent Channel, the rings are always protected against broadcast storms.

MSTP originally defined in IEEE 802.1s and later merged into IEEE 802.1Q-2003, defines an
extension to RSTP to further develop the usefulness of VLANs. This "Per-VLAN" MSTP configures a
separate Spanning Tree for each VLAN or Tansparent Channel group and blocks all but one of the
possible alternate paths within each Spanning Tree.
If there is only one VLAN or Transparent Channel in the network, single (traditional) STP works
appropriately. If the network contains more than one VLAN, the logical network configured by single
STP would work, but it is possible to make better use of the alternate paths available by using an
alternate spanning tree for different VLANs/Transparent Channels or groups of VLANs/Transparent
Channels. Within N50/N70 networks, there is only one MST region operational.
More than one VLAN can be assigned to one MST instance.
Licenses: No license is required for MSTP.
NOTE: MSTP Monitoring from the live network is also possible, see 10.1.

MSTP configuration must be done on general level (see 5.11.2) and on VLAN or Transparent
Channel /Node level (see 5.11.3).

5.11.2 Configuration (General)
Following general MSTP parameters can be configured and are valid MSTP instances:
Forward Time: (default value = 15 s, min. 4 s, max. 30 s) Controls how fast a port changes its
spanning tree state from blocking state to forwarding state;
Max Aging: (default value = 20 s, min. 6 s, max. 40 s) The maximum age allowed for the STP
information learned from the network on any port before it is discarded;
Compatibility: Indicates the compatibility version for the spanning tree protocol;
Region: Sets the configuration name for the MST region;
Revision: (default value = 1, min. 0, max. 65535) Sets the configuration revision number for the
MST region; All nodes in an MST region must have the same revision level;
Page 58 of 189 BG-M370-E-8

5.11.3 Configuration (VLAN, Transparent Channel, Node)
1. In the OMS-FEM, go via Configuration L2 Features Spanning Tree. The Spanning Tree
configuration wizard opens.

3. In the window below, Fill out an STP name and an MSTP Instance Id. This Id a unique number
for the MSTP instance. The Instance Id must be in the range [1,..,63].
4. Select one or more VLANs/Transparent Channels on which this spanning tree instance must run.
Click Next >>.

BG-M370-E-8 Page 59 of 189

5. ATTENTION: Most of the parameters below are parameters for EXPERTS ONLY. Before
changing any parameter, read carefully 5.31 first ! In the page below, it is possible to change (or
keep the default) values of the parameters described below. Only ports that are part of a VLAN or
Transparent Channel are shown. Click the Next >> button to review the information.

Node: Bridge Priority (0-61440): A lower priority value has more priority than a higher priority
value. MSTP uses the bridge ID to determine the root bridge, the bridge with the lowest bridge
ID becomes the root bridge. The bridge ID is composed of the bridge priority and the bridge
MAC address. The bridge with the lowest priority value (=highest priority) becomes the lowest
bridge ID. If all the bridge IDs have the same priority, the bridge with the lowest MAC address
will then become the root bridge. NOTE: The bridge priority value must be in multiples of 4096.
Node:Loop-Aware
Checked: It means that the node is running in Loop-Aware mode, see 5.31; If there are
Layer2 loops detected in the configuration, the checkbox will be read-only and cannot be
unchecked. If there are no Layer2 loops detected, the checkbox can be unchecked
manually if desired.
Unchecked: It means that the node is running in Loop-Free mode, see 5.31. In this case,
the checkbox can be checked manually to go into Loop-Aware mode. Only check it
manually when you are going to create Layer2 loops by design. The OMS-FEM will check
it automatically anyway after detecting such a loop.
Link: ELAN/SLAN: Link Cost: The default value in this field is already calculated based on
the assigned bandwidth (SLANs) or link speed (ELANs). The value can be modified between
1 and 200000000 can be entered. This value represents the cost of the path to the other
bridge from the transmitting bridge at the specified External LAN/SLAN. If there is more than
one path from node A to node B, the path with the lowest path cost will be the selected path for
data transmittal, the other paths will be blocked via blocking the connected ports.
Port: Priority: Enter a value between 0 and 240, using multiples of 16. This is the value that
decides which port should be blocked by priority in a LAN if all Link Costs are the same.
Default value = 128.
Port: Link Type: Enter one of the values Auto/Point-to-Point/Shared
Point-to-point: The link is a point-to-point link to another device; Access ports and ELAN
ports are by default set to Point-to-Point. Point-to-point links make the node reconfigure
quicker (e.g. due to a loop reconfiguration) than a shared link.
Shared: The link is a shared segment and can contain more than one device; SLAN ports
are by default set to Shared. Shared links make the node reconfigure slower (e.g. due to
a loop reconfiguration) than a point-to-point link. E.g when your shared link only contains
two parties, the Link Type could be set to point-to-point.
Auto: (=default value) The N50/N70 series node will autodetect the Link Type for MST;
Page 60 of 189 BG-M370-E-8
Port: PortFast (ATTENTION: use only for Access Ports):
Checked (=default for Access Ports and ELAN ports): immediately puts the port into
STP forwarding mode upon linkup. The MSTP listening and learning phase is omitted. The
port still participates in STP. So if the port is to be a part of the loop, the port eventually
transitions into STP blocking mode. This setting is only allowed on access ports, which are
connected to a single server/workstation/end device where no loops are expected. When
this parameter is checked, also check the parameter BPDU Guard and Root Guard.
Unchecked (=default for SLAN Ports): puts the port first into STP blocking mode upon
linkup. The MSTP listening and learning phase is active. Based upon these results, MSTP
will keep the port in blocking mode or set in it in forwarding mode. Ports that are connected
to switches or routers must use this setting.
Port: Root Guard: This setting manages the root bridge protection:
Checked: prevents this port to become a root port. As a result, it prevents the switch
connected to this port to become the root bridge.
Unchecked (=default): allows this port to become a root. As a result, it allows the switch
connected to it to become the root bridge.
Port: BPDU Guard:
Checked (=default for Access Ports): The BPDU guard is enabled. If an MSTP BPDU
packet enters the port, the node will detect this immediately and disable the port if the port
has PortFast enabled or checked. (The port can be re-enabled by setting the Admin
Status of the port (via port properties) Down and click Apply and setting it back Up and
click Apply.) Checking BPDU Guard makes sure that external devices connected to this
port are not able to influence the MSTP topology within the network borders. As a result,
the network will be a lot more reliable.
Unchecked (=default for SLAN/ELAN Ports): The BPDU guard is disabled. The port will
not be disabled when an MSTP BPDU packet enters the port. A connected device to this
port is able to participate in the MSTP protocol and topology within the network. As a
result, this connected device can also become the root bridge (see also Root Guard
parameter for more information) of the network, resulting in possible major changes within
the MSTP network or domain.
Port: BPDU Transmit:
Checked: The N50/N70 node can transmit (MSTP) BPDU packets on this port.
Unchecked: The N50/N70 node does not transmit (MSTP) BPDU packets on this port.
This setting must for example be used when ETS-3GC7F/ETS-4GC24FP switches are
connected to the N50/N70 nodes, and RGERP (and not MSTP) is active on these ETS-
3GC7F/ETS-4GC24FP switches. See Ref. [5], [6].
Port: BPDU Receive:
Checked: The N50/N70 node can receive and process (MSTP) BPDU packets on this
port.
Unchecked: The N50/N70 node ignores incoming (MSTP) BPDU packets on this port.
This setting must for example be used when ETS-3GC7F/ETS-4GC24FP switches are
connected to the N50/N70 nodes, and RGERP (and not MSTP) is active on these ETS-
3GC7F/ETS-4GC24FP switches. See Ref. [5], [6].
Port: Hello Time (sec): (default=2 s, range [1,2]) This value configures the interval between
the MSTP hello packets, called BPDUs, sent by the root switch. Each MSTP node expects to
receive a BPDU packet within three hello times.

BG-M370-E-8 Page 61 of 189

6. The review page shows the intentional MST Instance (SLANs/External LANs, ports). Zooming in
via the mouse-scroll wheel (or using the built-in zoom toolbar) shows more MST details in the
node, see figures below. The PortFast feature and (Port) Priority are not shown on the nodes,
but zooming in even more, will show these properties as well. Click the Finish button to create
and store the MST Instance in the database/OMS-FEM or click << Prev to change the configured
information.


8. After a Close action, whether loaded or not, the created MST Instance and its properties are now
visible via right-click view on STP1 in the L2 Features tab on the right-hand side. In this
example, the URL is PROTOCOL://MstpProtocol STP1.
Page 62 of 189 BG-M370-E-8

BG-M370-E-8 Page 63 of 189
5.12 IGMP Snooping
5.12.1 General
The symbol below is used in the OMS-FEM menu and treeviews to indicate IGMP Snooping.

IGMP snooping is designed to prevent hosts on a local network from receiving traffic for a multicast
group they have not explicitly joined. It provides the N50/N70 series nodes with a mechanism to
diminish multicast traffic from links that do not contain a multicast listener (an IGMP client). The
N50/N70 series node will, by default, flood multicast traffic to all the ports in a broadcast domain (or
the VLAN equivalent). Multicast can cause unnecessary load on host devices by requiring them to
process packets they have not solicited.
IGMP snooping allows the N50/N70 series node to only forward multicast traffic to the ports that have
solicited them. IGMP snooping is not a protocol but a layer 2 optimization for the layer 3 IGMP
protocol (see 5.21). IGMP Snooping takes place internally on the N50/N70 series node. Snooping is
therefore especially useful for bandwidth-intensive IP multicast applications such as IPTV.
Licenses: No license is required for IGMP Snooping.
NOTE: IGMP Snooping Monitoring from the live network is also possible, see 1.1.

IGMP Snooping configuration must be done on general level (see 5.12.2) and on VLAN/Node level
(see 5.12.3).
5.12.2 Configuration (General)
ATTENTION: All related Router Port terminology in IGMP Snooping (see 5.12) is not related to
Virtual Routers (see 5.17), Static Routing (see 5.18) and VRRP (see 5.19).
Following general IGMP Snooping parameters can be configured in the L2 Features tab on the right-
hand side and are valid for all IGMP Snooping instances:
Port Purge Interval: (default value = 260 s, min. 130 s, max. 1225 s) The expiry of the Port
Purge Timer on the port for a particular multicast group results in the port being removed from the
forwarding list of the corresponding multicast entry in the Multicast Forwarding Table.
Report Forward Interval: (default value = 5 s, min. 1 s, max. 25 s) In order to keep the traffic low,
the response to general query messages must be done by only one host for a given group. How
can be made sure that only one host answers the query, while the others which have to report
(=Membership Report) the same group, or groups are not? This is achieved with delayed
response via the Report Forward Interval: When a host1 receives general query message, it
delays the response (= it sets a timer for each group to a different random value between 0 and
the Report Forward Interval second, then broadcasts the response(s) according to the timers. If
host1 receives a response from another host2, whose timer for that group has expired earlier,
host1 cancels the corresponding timer and doesnt send the duplicate response for the group.
Router Port Purge Interval: (default value = 125 s, min. 60 s, max. 600 s) Configuring Multicast
Router Port Time-Out sets the IGMP snooping router port purge time-out after which the port gets
deleted if no IGMP router control packets are received.
Page 64 of 189 BG-M370-E-8
Group Specific Query Interval: (default value = 2 s, min. 2 s, max. 5 s) Configuring group
specific query interval sets the time interval after which the N50/N70 node sends a group specific
query on a port.
Group Specific Retry Count: (default value = 2, min. 1, max. 5) Configuring group specific retry
count sets the maximum number of group specific queries sent on a port on reception of a leave
message.
Multicast Forward Mode: (default value =MAC) Configuring Multicast Forward Mode sets the
address type , MAC or IP, on which addresses the multicast forwarding is based. ATTENTION:
Note that changing this mode will remove all existing IGMP Snooping instances.

5.12.3 Configuration (VLAN, Node)
1. In the OMS-FEM, go via Configuration L2 Features IGMP Snooping. The IGMP Snooping
wizard opens.

IGMP Snooping Properties valid
for ALL nodes and VLANs
(not VLAN specific)
BG-M370-E-8 Page 65 of 189
3. In the window below, select the VLAN on which IGMP Snooping must be configured, only one
VLAN can be selected per IGMP Snooping instance. Multicast forwarding mode is MAC based*
(*= this mode can be changed in the IGMP Snooping Generic Properties into IP based. Note that
changing this mode will remove all existing IGMP Snooping instances.). Click the Next >> button.

4. In the window below, the IGMP Snooping instance can be configured for all the ports (per node)
belonging to that selected VLAN. IGMP Snooping can be enabled/disabled per node, some
parameters can be configured on Node level, some on Port level and further on, some on VLAN
level.

5. ATTENTION: An advised configuration for OTN solutions is shown further on.

6. Via right-clicking the red triangle, the extra (expert) parameters Report Process, Report
Forward, Query Forward can be configured after selecting them in the selection list. These
parameters have default values which are fine for the advised OTN Solution, but can be fine-tuned
if desired.

7. An example in the figure below: the parameters Report Process and Report Forward have been
selected in the drop-downlist. These parameters are configurable now and can be unselected as
well (via right-clicking the red triangle) to hide them again.

Page 66 of 189 BG-M370-E-8
Node Level:

Enabled:
checked (=default): IGMP Snooping is enabled on that specific node, and operates
according all the other configured parameters.
unchecked: IGMP Snooping is disabled on that specific node.
Snooping Mode:
Passive: All IGMP messages (membership queries, membership reports, leave group,
group specific queries...) through the N50/N70 series node are always passed without
interaction of the N50/N70 series node itself.
Proxy (=default): The N50/N70 series node itself is Proxy and queries all its non-router
ports. Proxy means that the N50/N70 series node tries to handle the IGMP flow as efficient
as possible...it only sends out IGMP messages on the OTN ring if really necessary. The
proxy only passes through a stream if a port asks for it.
Reporting without querier: Has reporting functionality but does not send out any query
over any of its ports.
Reporting with querier: Has reporting functionality but sends out queries over all the
ports, router and non-router ports.
Report Process: relevant in all modes
Non Router Ports (=default): Most of the time, router ports are SLAN ports, non-router
ports are front ports. As a result, setting this value makes sure that Reports are only
processed from non-router ports.
All Ports:Setting this value makes sure that Reports from all ports are processed.
Report Forward: only relevant in Passive mode
Router Ports (=default): Most of the time, router ports are SLAN ports, non-router ports
are front ports. As a result, setting this value makes sure that Reports mainly travel
towards to the OTN-X3M ring and not towards other front ports.
All Ports: Reports are forwarded to all ports.
Query Forward: not relevant in Passive mode
Non Router Ports (=default): Most of the time, router ports are SLAN ports, non-router
ports are front ports. As a result, setting this value makes sure that queries mainly travel
towards the front ports and not on the OTN-X3M ring.
All Ports: Setting this value results in queries on all ports, as a result probably also on the
OTN-X3M ring.
Remark (see figure below): only relevant when configuring multipIe IGMP Snooping instances
(=one instance per VLAN) within a node. This also means that multiple VLANs are configured
within that node.
It notifies that changing these Node Level properties, except for the enabled property,
automatically changes the Node Level properties on other instances already configured
within this node. Eg, if instance1 in VLAN10 has snooping mode configured as passive,
and later on, instance2 in VLAN20 within that same node configures snooping mode as
proxy, snooping mode in instance1 will automatically be configured as proxy as well.

BG-M370-E-8 Page 67 of 189
8. In the figure below, Port Level properties can be set. As an example, some settings were done:

Port Level:

Block Multicast:
checked: No multicast traffic is outputted on this port;
unchecked (=default): Multicast traffic is allowed on this port;
Static Router Port:
checked: This port is assigned as a fixed (or static) router port, this router port is always
there, and is not the result of a dynamic learning process;
unchecked (=default): If no queries are received on this port, this port will be a non-router
port. If queries are received after some time on this port, this port will turn into a
dynamically learnt router port.
Leave Mode: relevant in all modes;
Fast: the port is immediately removed from the multicast group when a leave message is
detected on that port.
Normal (=default): the port is not immediately removed from the multicast group when a
leave message is detected on that port. First some group specific queries are sent on that
port, and if no membership report is received within a time interval on that port for that
multicast group, the port will be removed from that multicast group.

Advised configuration for OTN solutions:
Starting from the default values for IGMP Snooping, the only thing extra that must be configured is
to enable the Static Router Port field for all the SLAN ports. As a result, following properties must
have the values as described below. Further on, find some graphic flows for the advised solution.

Node Level:
Enabled: checked on all nodes
Snooping mode: Proxy on all nodes
Report Process: Non Router Ports on all nodes
Report Forward: not relevant because Snooping mode Proxy is used
Query Forward: Non Router Ports on all nodes

Port Level:
Block Multicast: unchecked on all ports
Static Router Port: check the SLAN ports, leave the front ports unchecked
Leave Mode: normal on all ports

Click the Next >> button.
Page 68 of 189 BG-M370-E-8

OTN-X3M Ring
c1 c2 c3
c4 c5 c6
c7 c8
host2
host1
Router port
Proxy Mode
N50xx node
c1 c2 c3
c4 c5 c6
c7 c8
host2
host1
C4
C5
C6
C7
C8
C1
C2
C3
All streams via router port
automatically on the ring
c1 c2 c3
c4 c5 c6
c7 c8
host2
host1
C1, C2, C3, C4, C5, C6, C7, C8
Proxy
Proxy
Proxy
Proxy
All streams available
on the ring
All the Proxies know all the
available streams of all nodes
c1 c2 c3
c4 c5 c6
c7 c8
host2
host1
C1, C2, C3, C4, C5, C6, C7, C8
Proxy queries
only local Non-
Router Ports
I want to see
(join) stream C2
c1 c2 c3
c4 c5 c6
c7 c8
host2
C1, C2, C3, C4, C5, C6, C7, C8
C2
BG-M370-E-8 Page 69 of 189
9. In the window below, VLAN level properties can be configured specific for the chosen VLAN.
Click the Next >> button to review the information.
Max Response Time: Specifies the period in tenths of a second during which the host is
expected to respond to an IGMP query. Default value is 100 1/10 seconds = 10 seconds.
Query Interval: is the amount of time in seconds between IGMP General Query messages
sent by the querier, if this node is the querier. Default value is 125 seconds.
IGMP Version: Indicates the used IGMP version: V1, V2, V3 (=default).

10. The review page shows an overview of the IGMP Snooping instance. After zooming in via the
mouse-scroll wheel (or using the built-in zoom toolbar), the figure shows more IGMP Snooping
details in the node itself. Click the Finish button to create and store the IGMP Snooping Instance
for this specific VLAN in the database/OMS-FEM or click << Prev to change the configured
information.


12. After a Close action, whether loaded or not, the created IGMP Snooping and its properties are
now visible via right-click view on VLAN2 in the L2 Features tab on the right-hand. In this
example, only one instance for VLAN2 has been configured so far. In this example, the URL is
PROTOCOL://IGMPSnooping/ VLAN2. Zooming in shows more details in the node picture.

Page 70 of 189 BG-M370-E-8
5.13 Port Mirroring
5.13.1 General
The symbol below is used in the OMS-FEM menu and treeviews to indicate Port Mirroring.

Port Mirroring is used on a network switch to send a copy of network packets seen on one switch port
(or an entire VLAN) to a network monitoring connection on another switch port. This is commonly used
for network appliances that require monitoring of network traffic, such as an intrusion-detection
system.
Port mirroring can be configured per node. It means that the source port (=ingress/egress traffic) and
the destination port (=Mirroring port) reside on the same node. The mirroring occurs on a front port or
an SLAN (=segment) port. Remote Port Mirroring (mirroring between two or more nodes) is possible
via the SLAN Ports, see 5.13.3.
Licenses: No license is required for Port Mirroring.

NOTE: Additional monitoring is possible via Port Counters, see 11.2.

13. In the OMS-FEM, go via Configuration Traffic Control Control Port Mirroring. The Port
Mirroring wizard opens.

BG-M370-E-8 Page 71 of 189
15. In the window below, select the node (only one) and destination port (only one) on which the
chosen source traffic further on must be mirrored. Click the Next >> button advance to the source
port selection.

16. In the window below, select the source port(s) (one or more ingress and/or egress ports can be
selected) which traffic must be mirrored onto the already chosen destination port. Click the Next
>> button to review the configured information.

17. The review page shows intentional source and destination ports for mirroring. Click the Finish
button to configure and store the Port Mirroring in the database/OMS-FEM or click << Prev to

Page 72 of 189 BG-M370-E-8

19. After a Close action, whether loaded or not, the configured Port Mirroring and its properties are
now visible via right-click view on OTN-X3M-Node 36 in the Traffic Control on the right-hand
side. In this example, the URL is PROTOCOL://PortMirroring/OTN-X3M-Node 36.

5.13.3 Remote Port Mirroring
a. General
Remote Port Mirroring is the mirroring of traffic in one node or more nodes to a destination port in
another node (one-to-one or multi-to-one). If you want to Mirror the ingress/egress traffic on a front
port in Node X to another front port in Node Y, the data must be mirrored via a segment (or SLAN)
port and Mirroring must be configured on both Node X and Node Y. Remote Port Mirroring is not a
setting on itself but is the result of configuring indivual Mirroring instances on the required nodes.

b. Mirroring Example

Segment
Port
Mirroring SLAN
Segment
Port
OTN-X3M
Remote
Mirroring
Source
Node A
Configure
Mirroring
Front
Port
Front
Port
Destination
Node B
Configure
Mirroring
Mirroring
Port
Mirrored
Port
13
Node 10
S5
S6
SLAN5 (=Normal Data SLAN)
SLAN6 (=Remote Mirroring SLAN)
14 15
S6
OTN-X3M
Disable Destination
Removal Mechanism
for Mirroring!
Mirroring Instance10:
from source 13,14
to destination S6
24
13 14 15
Node 15
S5
VID
100
VID
100
Node 20
Mirroring Instance20:
from source S6
to destination 24
BG-M370-E-8 Page 73 of 189
c. Configure the Example
Front port 13 and 14 in Node 10 must be mirrored to front port 24 in Node 20. Follow the steps below
to configure Remote Port Mirroring on Node A (10) and B (20):
It is assumed that there is already a normal data SLAN e.g. SLAN5. Front ports 13, 14, 15 and
segment port 5 in both nodes 10 and 15 belong to VLAN ID (=VID) 100. It is not a prerequisite
but it is just an example.
Purpose: Mirror all the ingress/egress traffic on front port 13 and 14 in Node to front port 24 in
node 24. Create/Configure a Remote Mirroring SLAN (= ethernet service, e.g GET) between
Node 10 en 20 = SLAN6. (DO NOT LOAD YET! MSTP could select SLAN6 and close SLAN5
in some scenarios!) SLAN6 must only be used for mirroring. ATTENTION: Do not use
Mirroring and normal data traffic within the same SLAN !
Mirrored port: front port 13 and 14 in Node 10;
(Remote) Mirroring port: front port 24 in Node 20;
No VID is required to configure Remote Mirroring, not in the source node and not in the
destination node. VID100 was already present for normal data traffic and has nothing to do
with Remote Mirroring as such.
Disable Destination Removal Mechanism on the segment port on the destination node (S6
Node 20) in the OMS GUI. This setting is only allowed on segment ports that terminate the
Mirroring SLANs in the destination node (Node 20). It makes sure that the mirrored traffic with
unknown destination IP addresses in the destination node (Node 20), will not be removed, but
passed to the destination mirroring port. In the OMS GUI, set the following segment port
setting of the N50/N70 Series Node:
Set S6 Node 20 : BORA<N50/N70>Segment Port: Destination Removal Mechanism = Off

Note: MSTP BPDUs could be part of the mirrored traffic, but could be unwanted. This MSTP
traffic could be filtered out via your Ethernet traffic tracing tools. This MSTP traffic could be
filtered out as well via the OMS-FEM (not shown in this example) after sending the mirrored
traffic via another VLAN (e.g. VLAN200) and uncheck BPDU Receive/BPDU Transmit in the
default MSTP Instance for the ports listed below:
S6 on Node10 (source node, mirroring SLAN in VLAN200)
S6 on Node20 (destination node, mirroring SLAN in VLAN200)
24 on Node20 (destination node, mirroring front port in VLAN200)
Configure Port Mirroring on Node 10
source port = front port 13 and 14
destination port = segment port 6
Configure Port Mirroring on Node 20
source port = segment port 6 (has the special allow unknown destination traffic setting)
destination port = front port 24 (has the special block MSTP setting)
Load the configured service Remote Mirroring SLAN6.
Page 74 of 189 BG-M370-E-8
5.14 MAC Access Control List (MAC ACL)
5.14.1 General
The symbol below is used in the OMS-FEM menu and treeviews to indicate the MAC ACL feature. The
M Refers to MAC addresses.

An Access Control List will allow you to restrict the communication through the ports of this VLAN to a
limited number of devices. The MAC addresses of these allowed devices have to be specified in the
Access Control List (White (MAC) List).
Within the N50/N70 series node, Access Control lists with MAC addresses can be created per node
per VLAN. Furthermore, that created ACL for that specific VLAN on that specific node, can be
enabled/disabled per port on that node.
ACL enabled (checked) on a port, either access or SLAN port, means that only packets from MAC
addresses included in the ACL, have access to that port. MAC ACL disabled (unchecked) means that
all packets from all MAC addresses have access to that port. By default, SLAN ports have the created
ACL disabled (=all packets have access) and access ports (=ports connected to end-device) have the
created ACL enabled.
Licenses: No license is required for MAC Access Control List.
1. In the OMS-FEM, go via Configuration Traffic Control Security MAC Access Control List.
The Access Control List wizard opens.


3. Select the VLAN for which an ACL must be created. Only one VLAN can be selected at the time.
Click the Next >> button.
M
BG-M370-E-8 Page 75 of 189

4. In the window below, select the Nodes for which you want to configure MAC ACL. Only one node
can be selected at the time. E.g first select node 32.
5. Next, check the node ports on which the MAC ACL must be active (checked: only data from the
listed MAC addresses is allowed on this port; unchecked: data from all MAC addresses is
allowed). MAC ACLs on access ports (network edge, end station) are by default checked
whereas MAC ACLs on SLAN ports are by default unchecked.

6. In the MAC List, click the empty area and fill out the allowed MAC addresses (possible syntax:
ab-cd-ef-gh-ij-kl or ab:cd:ef:gh:ij:kl or abcdefghijkl) for the checked ports on this specific node.
After each filled out MAC address, press ENTER first before entering a new MAC address.
7. Repeat previous steps in this Node Configuration window for the other nodes.

Node 32
(VLAN3)
Node 10
(VLAN3)
Node 32
(VLAN3)
Node 10
(VLAN3)
Node 32
Enter MAC addresses
here e.g:
Node 10
Enter MAC addresses
here e.g:
ACL on access ports by
default checked
ACL on SLAN ports by
default unchecked
Page 76 of 189 BG-M370-E-8
9. The review page shows the intentional MAC ACL configuration. Click the Finish button to
configure and store the MAC ACL in the database/OMS-FEM or click << Prev to change the
configured information.
? indicates that a MAC ACL is configured for that specific node, and clicking the ? shows
the configured MAC ACL for that specific node.
green + on a port indicates that this port has a MAC ACL configured; this port only allows
traffic from MAC addresses configured in the MAC List;
no + on a port indicates that this port has no ACL configured; this port allows all traffic
from all MAC addresses, no restrictions.


11. After a Close action, whether loaded or not, the created MAC ACL and its properties are now
visible via right-click view on VLAN3 in the Traffic Control tab on the right-hand side. In this
example, the URL is PROTOCOL://MACACL/ VLAN3.

Green + =
ACL configured
Show MAC List
No + =
no ACL configured =
All traffic allowed
BG-M370-E-8 Page 77 of 189
5.15 IP Access Control List (IP ACL)
5.15.1 General
The symbol below is used in the OMS-FEM menu and treeviews to indicate the IP ACL feature. The I
Refers to IP addresses.

Within the N50/N70 series node, Access Control lists with IP addresses can be created per port.
An IP Access Control List will allow you to restrict the communication through access, ELAN or SLAN
ports according to the configured filter rules. The IP ACL rules (permit or deny) will be activated for the
incoming IP packets of the configured ports.
If no IP ACL is configured at all, all packets are allowed.
Licenses: No license is required for IP Access Control List.

1. In the OMS-FEM, go via Configuration Traffic Control IP Access Control List. The
IP ACL wizard opens.


3. Configuration: In the figure below, following parameters can be configured:
Filter: Permit/Deny: the type of rule that must be configured. Permit/Deny means that
incoming messages will be allowed/blocked on the configured port according to the
configured IP Addresses and Priority.
Source IP Address / Subnet Mask: the source IP address and subnet mask for which this
rule is valid. If these fields are left empty (indicated as Any IP Address further on), all
messages from any Source IP Address will be permitted or denied (according the filter value)
for the selected port further on.
I
Page 78 of 189 BG-M370-E-8
Destination IP Address / Subnet Mask: the destination IP address and subnet mask for
which this rule is valid. If these fields are left empty (indicated as Any IP Address further on),
all messages from any Destination IP Address will be permitted or denied (according the filter
value) for the selected port further on.
Priority: Indicates the priority in which this configured rule on a specific port of a node will be
processed. The field can be left empty or can have a value in the range [1..255]. Value 1 has
the lowest priority, value 255 has the highest priority. Rules with the highest priority are
processed first. If the priority of multiple rules is the same, the rule that was created first will be
processed first.

4. Ports Selection: In the figure below, select the node(s) and the port(s), via clicking the
checkboxes, for which the configured rule(s) must be activated. If VLANs are defined, it is possible
to show the selected ports for a specific VLAN via the VLAN-ports filter.

5. Click the Add button to add this rule in the rules list. Click the + to expand the rule or show more
info about this rule. Click the - to collapse the rule again. If a single or all rules must be deleted, it
can be done via selecting a single or all rule(s) as indicated in the figure below, and clicking the
Delete button.

VLAN-ports Filter
BG-M370-E-8 Page 79 of 189

7. The review page shows the intentional IP ACL configuration. Attention: the rules are listed now in
the order they will be processed by priority and creation time. The first rule will be processed first,
the second rule will be processed second ... If an incoming message matches multiple rules, only
the first matching rule in the list will be applied to the message, the other matching rules will be
ignored. Click the Finish button to configure and store the IP ACL in the database/OMS-FEM or
click << Prev to change the configured information.


9. After a Close action, whether loaded or not, the created IP ACL and its properties are now visible
via right-click view on IPACL in the Traffic Control tab on the right-hand side. In this
example, the URL is PROTOCOL://IPACL/ IPACL.

Click here to
select all rules
Click here to
select single rule
Click here to deselect
single/all rule(s)
Rules
processing
order
Highest
priority
Lowest
priority
Last
processed
First
processed
Page 80 of 189 BG-M370-E-8
5.16 RADIUS (Remote Authentication Dial In User Service)
5.16.1 General
The symbol below is used in the OMS-FEM menu and treeviews to indicate the RADIUS feature.

The RADIUS feature allows that external clients connected to the nodes must authenticate before
accessing the network. If the authentication mechanism is desired, the N50/N70 series node act as a
NAS (=Network Access Server) that forwards the authentication request to an external RADIUS
Server. The external RADIUS Server decides, based on the MAC/IP address, hostname of the client,
whenever that client is allowed to access the network.
For each node that must act a NAS, the RADIUS feature must be configured on that node.
An IP Access Control List will allow you to restrict the communication through access, ELAN or SLAN
ports according to the configured filter rules. The IP ACL rules (permit or deny) will be activated for the
incoming IP packets of the configured ports.
If no RADIUS is configured on a node, all packets are allowed on that node and no
authentication will be done.
NOTE: If both authentication mechanisms RADIUS and ACL (ACL see 5.14/5.15) are active on
the same port, both RADIUS and ACL have equal priority. It means that the port will be
blocked whenever one of the two mechanisms blocks that port or the port will be open when
both mechanisms allow the port to be open.
Licenses: No license is required for RADIUS.

1. In the OMS-FEM, go via Configuration Traffic Control Security RADIUS. The RADIUS
wizard opens.


BG-M370-E-8 Page 81 of 189
3. Configuration: In the figure below, configure the RADIUS feature on one specific node.
Fill out a Name for your RADIUS feature instance.
Authenticator Node Selection: Select one node in the node list on which you want to create
the RADIUS feature; This node will act as the Authenticator Node. A node will only appear in
this list if a Virtual Router (see 5.17) has been created on this node and no RADIUS instance
has been configured on the node yet. Only one node can be selected in the list. ATTENTION:
make sure that a router which can reach the configured RADIUS server(s), will be configured
on the selected node. This step can be done before or after the RADIUS configuration.

4. Configuration: In the figure below, fill out the following parameters to add a known external
RADIUS server. This Authenticator node will use this (or these) RADIUS server(s) for
authentication. If more than one RADIUS server is added, the node will always use the first-one in
the list.
Server IP Address: Fill out the IP Address of the external RADIUS Server.
Preshared Key: Indicates the Per-server encryption key which specifies the authentication
and encryption key for all RADIUS communications between the node (=authenticator) and the
RADIUS server. The maximum length of the secret key string is 46.
Additional Properties:
Authentication Port Number: value in the range [1,.., 65535], default value=1812:
indicates a specific UDP (=User Datagram Protocol) destination port on this RADIUS
server to be used solely for the authentication requests.
Accounting Port Number: value in the range [1,.., 65535], default value=1813: indicates
a specific UDP (=User Datagram Protocol) destination port on this RADIUS server to be
used solely for the accounting requests.
Timeout: value in the range [1,.., 120] seconds, default value=3 s: Indicates the time
period in seconds for which the node waits for a response from the RADIUS server before
retransmitting the request from the node to the RADIUS server.
Retransmit: value in the range [1,.., 254], default value=3: Indicates the maximum number
of attempts that the node undertakes to contact the RADIUS server.

Page 82 of 189 BG-M370-E-8

5. Click the Add button to add this RADIUS Server to the RADIUS Servers list. If a single or all
RADIUS Servers must be deleted, it can be done via selecting a single or all server(s) as indicated
in the figure below, and clicking the Delete button.

6. Default Port Settings: In the figure below, fill out the following parameters to add a known
external RADIUS server. This node will use this RADIUS server for authentication. If more than
one RADIUS server is added, the node will always use the first-one in the list.
Port-control:
Auto: Configures the 802.1x authentication process in this port. Causes the port to begin
the unauthorized state, allowing only EAPOL frames to be sent and received through the
port. The authentication process begins when the link state of the port transitions from
down to up or when an EAPOL-start frame is received. The switch requests the identity of
the client and begins relaying authentication messages between the client and the
authentication server. The switch can uniquely identify each client attempting to access the
network by the client's MAC address.
Force Authorized: Configures the port to allow all the traffic through this port. Disables
802.1X authentication and causes the port to transit to the authorized state without
requiring authentication exchange. The port transmits and receives normal traffic without
802.1X-based authentication of the client.
Force Unauthorized: Configures the port to block all the traffic through this port. Causes
the port to remain in the unauthorized state, ignoring all attempts by the client to
authenticate. The switch cannot provide authentication services to the client through the
interface.
Authentication Mode:
Multi Host: Configures the port to multi host authentication mode and performs port-based
authentication. More than one (=multi) host can be connected to the port using an Ethernet
hub connected to the port.
- Fill out parameters and click Add
- Repeat for every Radius Server
Click here to select
all RADIUS Servers
all RADIUS Servers
single RADIUS Server
BG-M370-E-8 Page 83 of 189
Single Host: Configures the port to single host authentication mode and performs MAC-
based authentication. Only one host can be connected to the port.
Control Direction:
Both:both incoming and outgoing traffic on this port is blocked until authentication was
succesful on this port.
In:only incoming traffic on this port is blocked until authentication was successful. Outgoing
traffic can travel out freely without authentication.
Max Request Count: value in the range [1,.., 10], default value = 2: sets the maximum
number of EAP (=Extensible Authentication Protocol) retries from the node to the client before
the node restarts the authentication process.
Max Start Count: value in the range [1,.., 65535], default value = 3: sets the maximum
number of EAPOL (=EAP over LAN) retries from the client to the node (=authenticator).
Reauthentication: default value = off:
On: will request the client to re-authenticate periodically (according Reauth-period) to the
node. The periodic reauthentication is requested to ensure that the same client (or
supplicant) is still accessing the network.
Off: the client must only authenticate once to the node, no periodic re-authentication
required.
Quiet Period(s): value in the range [0,.., 65535] seconds, default value=60s: Configures the
quiet-period, indicating the interval that the node remains in the quiet state following a failed
authentication exchange with the client.
Reauthorizaton Period(s): value in the range [1,.., 65535] seconds, default value=3600s:
Configures the reauthentication period which is used when the Reauthenticate has been
checked. It indicates the number of seconds between two re-authentication attempts.
Server Timeout(s): value in the range [1,.., 65535] seconds, default value=30s: Configures
the interval that the node waits for the retransmission of packets to the RADIUS server
(=authentication server).
Supplicant Timeout(s): value in the range [1,.., 65535] seconds, default value=30s:
Configures the interval that the node waits for the retransmission of packets to the client.
Transmit Period(s): value in the range [1,.., 65535] seconds, default value=30s: Configures
the interval that the node waits for a response from the client on an EAP-request/identity frame
that the node has sent to the client. After this interval, the node retransmits the EAP-request to
the client.
Start Period(s): value in the range [1,.., 65535] seconds, default value=30s: Configures the
interval that the client (=supplicant) waits between successive retries to the node
(=authenticator).
Held Period(s): value in the range [1,.., 65535] seconds, default value=60s: Configures the
interval in seconds that the client (=supplicant) waits before trying to acquire the node
(=authenticator).
Authentication Period(s): value in the range [1,.., 65535] seconds, default value=30s:
Configures the interval that the client (=supplicant) waits before timing-out the node
(=authenticator).
Page 84 of 189 BG-M370-E-8

8. The review page shows the intentional RADIUS configuration. Attention: The first RADIUS server
in the list will be used first. Click the Finish button to configure and store the RADIUS in the
database/OMS-FEM or click << Prev to change the configured information.


10. After a Close action, whether loaded or not, the created RADIUS and its properties are now
visible via right-click view on RADIUS in the Traffic Control tab on the right-hand side. In this
example, the URL is PROTOCOL://RADIUS/ RADIUS.

BG-M370-E-8 Page 85 of 189
5.17 Virtual Router
5.17.1 General
The symbol below is used in the OMS-FEM menu and treeviews to indicate a Virtual Router.

Virtual Router is a router (instance) created by the OMS-FEM within an N50/N70 Series node. Virtual
in this context refers to the fact that it is created programmatically and that multiple routers can be
created within the same node, with each Virtual Router having its own independent routing table.
Because the Virtual Routers are independent, the same or overlapping IP addresses can be used
without conflicting with each other. These routing tables initially only have IP addresses/masks (in
CIDR notation) of directly connected networks. Later on, these routing tables will be extended by using
Static Routing (see 5.18), OSPF (5.22), .Thus multiple Virtual Routers are possible in one
node. See the example figure below:

Licenses: An Enhanced License Pack is required on nodes that need at least two virtual routers.
NOTE: VLAN Routing is done via creating Virtual Routers on the nodes where the VLANs must be
routed. An additional Layer 3 View is possible as described in 5.32.

1. In the OMS-FEM, go via Configuration Virtual Router. The Virtual Router wizard opens.

Node
80
N50/N70
series node
Node
90
3 Virtual Routers
in one node
0 Virtual Routers
in one node
Page 86 of 189 BG-M370-E-8

3. In the figure below, create a virtual router that is located on one specific node:
Fill out a Name for your virtual router;
Node Selection: Select one node in the node list on which you want to create the router; After
selecting a node, the available candidate router ports pop up in the Router Ports Selection
window, and the VLANs on this node pop up in the VLAN selection window. The node cannot
be modified later on after finishing this Virtual Router creation.
Full Feature Ready: Check this checkbox if this Virtual Router must be Full Feature Ready,
see 5.28 for more information.
Router Ports Selection: This section shows the available SLAN, ELAN and Loopback ports
(not assigned to a VLAN) on the selected node. Select the ports that must be become router
ports.
VLAN Selection: This window shows the VLANs available on the selected node. Select the
VLAN(s) that must become router interfaces.

4. Click the Next >> button.

BG-M370-E-8 Page 87 of 189
5. Configuration: In the figure below, assign (or fill out) the IP addresses in CIDR (=Classless Inter-
Domain Routing) notation to the ports and interfaces of this virtual router:

7. Fill out the virtual router properties. In the figure below the default values are displayed. ICMP is
a protocol for sending control and test messages across the IP network.
Send ICMP redirects: (default=checked) An ICMP redirect message is used by a router to tell
a previous router that its better to use a different route next time. Sending these messages
can be turned off.
Send ICMP unreachables: (default=checked) An ICMP destination unreachable message
indicates that a destination is unreachable. Sending these messages can be turned off.
Send ICMP mask reply: (default=checked) If a station starts up, it will broadcast ICMP mask
request to learn the used subnet mask. The router will send back an ICMP mask reply.
Sending these messages can be turned off.
Send ICMP echo reply: (default=checked) An ICMP echo reply message is a reaction on an
ICMP echo request message, to tell that the receiver is alive and reachable. ICMP Echo
replies are used by the well-known ping command to test network connectivity. Sending these
messages can be turned off.
IP default TTL: (default=64, range [1,..,255] ) Time to live hop counter, indicates how long (or
how many hops) an IP message can survive in an IP network. Every hop, the TTL is
decreased with one. If TLL reaches 0, the IP message is removed from the network.
ARP timeout: (default=300 s, range [30,..,86400]) If an ARP entry is not used a specific
amount of time, called the ARP timeout, the entry is removed from the caching table.
ARP retries: (default=3, range [2,..,10]) indicates the number of times that the ARP cache
manager attempts to resolve an IP address.

Page 88 of 189 BG-M370-E-8
9. The Review page shows the intentional Virtual Router configuration with the IP address list and
an indication for Full Feature Ready or not (see 5.28 for more information). Click the Finish
button to configure and store the Virtual Router in the database/OMS-FEM or click << Prev to


11. After a Close action, whether loaded or not, the created Virtual Router and its properties are now
visible via right-click view on the created virtual router in the list e.g. VirtRout3 in the Virtual
Routers tab on the right-hand side. In this example, the URL is PROTOCOL://VirtualRouter/
VirtRout3.

NOTE: The Virtual Routers on a node are also visible in the Node View (right-click Node View)
and then selecting the Virtual Routers icon in Select a View, see 5.4.5d.

Indicates:
Full Feature Ready
Not Full Feature Ready
BG-M370-E-8 Page 89 of 189
5.18 Static Routing
5.18.1 General
The symbol below is used in the OMS-FEM menu and treeviews to indicate the Static Routing feature.

At least one virtual router must be configured before a static route can be configured.
This static routing wizard configures or creates static routes (on the virtual routers) throughout the
network. A route is a path from a source towards a destination via which the message has to travel to
reach the destination IP network.
There can exist multiple paths from source to destination, but only one path will be the most efficient
one. Routes (with a same destination) can be favored via a distance parameter.
Licenses: No license is required for Static Routing.
NOTE: VLAN Routing is done via creating Virtual Routers (see 5.17) on the nodes where the
VLANs must be routed. Static Routing can be done an any Virtual Router, see 5.28 for
more information on Full Feature Ready.
1. In the OMS-FEM, go via Configuration L3 Features Static Routing. The Static Routing
wizard opens.


3. In the figure below, select a virtual router, on which the static routing table must be created:
X
Page 90 of 189 BG-M370-E-8


5. In the figure below, one or more static routes can be defined. As a general example, consider that
the message has to travel from point A to point E via the path: A B C D E.
Default route: A default route is the route of the last chance. It is the last route tried by a
router, after trying and mismatching all the other routes or if no other route is available. The
destination of the default route is always 0.0.0.0/0. Check the checkbox if the configured static
route must be the default route; In the listings later on, the default route can always be
recognized as the route with 0.0.0.0/0.
Destination: This must be a network address. In our general example, the source would be
point A and the destination could be C, D or E. The destination could not be B, because
B is directly connected to this router. If default route is checked, a destination cannot be filled
out or selected as it will always be 0.0.0.0/0.
Network IP-address field: A network IP address (a network IP address covers the entire
network, an single IP address covers one host) must be filled out as destination, e.g.
192.168.100.0/24.
Network IP-address list: A list is shown of all available not directly connected networks
for the selected virtual router. Select one or more of the listed destinations that must be
reached. Selecting multiple destinations at once in this list is only interesting when the
static routes go via the same Via point, see paragraph below.
Via: The Via is a single IP-address of the next hop starting from the source (= point A) to
reach the final destination (=point E). The Via is part of a directly connected network (=point
B, =directly connected).
IP-address field: An external IP address can be filled out as Via point, e.g.
192.169.100.2.
IP-address (filtered) list: A list is shown of all available IP addresses for the selected
(filtered) virtual router in a specific node. Select one of the IP addresses that must act as a
Via point. Make sure to select an IP address that is part of the directly connected
network.
Distance: (value [1,..,254]) When there are multiple static routes with the same destination,
the static route with the lowest Distance value will be taken/favored.

BG-M370-E-8 Page 91 of 189

6. Click the Add button to add this static route in the routes list. If a single or all routes must be
deleted, it can be done via selecting a single or all route(s) as indicated in the figure below, and
clicking the Delete button.

8. The review page shows the intentional Static Route(s) configuration. Click the Finish button to
configure and store the Static Routes in the database/OMS-FEM or click << Prev to change the

Filter to show list of
possible Via points
Automatically
filled out
Click here to
select all routes
single route
single/all route(s)
Page 92 of 189 BG-M370-E-8


10. After a Close action, whether loaded or not, the created Static Routes on a Virtual Router are
now visible via right-click view on the Virtual Router in the Static Routing list e.g. VirtRout1 in
the L3 Features tab on the right-hand side. In this example, the URL is
PROTOCOL://StaticRouting/ VirtRout1. Default routes are indicated by 0.0.0.0/0.

BG-M370-E-8 Page 93 of 189
5.19 VRRP (=Virtual Router Redundancy Protocol)
5.19.1 General
The symbol below is used in the OMS-FEM menu and treeviews to indicate the VRRP Layer3 feature.

VRRP (=Virtual Router Redundancy Protocol) is a protocol which increases the availability of the
router of a subnet. This redundancy technology is based upon the sharing of a virtual IP Address
amongst all the router interfaces being part of the same VRRP Group. This is achieved by combining
a master and one or more backup router interfaces into one Group. The actual routing within the
Group is done by the master (=active) router interface whereas the others act as backup. A router
interface becomes master after a master election process.
All the router interfaces within a Group use a same unique virtual IP address, e.g 10.10.10.1. The
virtual IP address and router interfaces must be in the same subnet. The virtual IP address will be the
default gateway for its associated VLAN e.g. VLAN with VID 150.
This VRRP wizard can create one or more VRRP instances. Each VRRP instance can be configured
between two or more routers. As a result, a Group will always have one or more backup router
interfaces whenever its active router goes down.

Licenses: An Enhanced License Pack is required on the nodes that participate in the VRRP
instance.
NOTE: VRRP Monitoring can be done as described in 10.4.

5.19.2 Prerequisite
The router interfaces must be part of the same subnet. Furthermore, it is strongly advised that the
redundant routers have similar configurations, to easily backup each other. See figure below:
10.10.10.4
Node 80
Master
Master
10.10.10.5
Node 85
Backup
10.10.10.x/24
Node 90
Group of routing interfaces
sharing one IP address:
e.g. 10.10.10.1
Backup
VID 150
SLAN
Router2
Access
Node
Router1
VID 150
VID 150
Page 94 of 189 BG-M370-E-8

1. In the OMS-FEM, go via Configuration L3 Features VRRP. The VRRP wizard opens.


Router1
Similar
Configurations
Router1
Router2
Router2
BG-M370-E-8 Page 95 of 189
3. In the figure below, fill out a VRRP Instance Name.
4. Assign an Id to this VRRP instance in the range of [1,...,255] by filling it out or selecting it.
5. Expand the Virtual Router Selection treeview to select the router interfaces that must participate
in this VRRP instance. Select the router interfaces that must backup each other and click the Add
button to group the backup ports into one Group. The Group will be added to the list. For
example, each line below has two interfaces that backup each other:
SLAN 4 interface node 32 backups SLAN 4 interface node 23 (select, click Add)
VLAN 2 interface node 32 backups VLAN 2 interface node 23 (select, click Add)
VLAN 3 interface node 32 backups VLAN 3 interface node 23 (select, click Add)
NOTE: This example has only two routers that backup each other, but if you have for example
three (or multipe) redundant routers, each Group will probably have three (or multipe)
router interfaces.
NOTE: A maximum of 24 IP interfaces (External LAN, SLAN or VLAN) per Node can participate
in VRRP.

6. Once a router interface is part of a Group, it cannot be selected anymore to add it to another
Group. If a port has been added to the wrong Group, the port can be selected again after
deleting the wrong Group first. If a single or all Groups must be deleted, it can be done via
selecting a single or all Groups as indicated in the figure below and clicking the Delete button.

Each other backup,
in one Group
- Select and Add
- Repeat for every Group
3 times select and Add =
three Groups
1 time select and Add =
one Group
Page 96 of 189 BG-M370-E-8


8. In the figure below, the VRRP behaviour of each Group must be configured.

Virtual IP Addresses (group): Fill out an available unique virtual IP address for each Group.
Each router interface of the same Group will always be mapped to the same virtual IP
address. If one router fails, the other redundant routers take over and will still process the
same virtual IP and MAC address. In this way, redundancy is created.
Priority (individual): value in the range [1,..,254], default value=100; Configures the Priority of
each individual router interface within the Group. The higher value, the higher the priority; In
case the router interfaces have the same priority value, the higher IP address is favored as
master. The Priority and Preempt fields depend on each other:
Preempt Checked (=default): Inside a Group, the router interface with the highest
priority value always becomes the master, also when another router interface inside that
group with lower priority is already master (e.g after original master failure). If a failing
orignal master with the highest priority returns into the network again after recovery, it will
automatically take over the mastership from the backup router interface that is also still
alive.
Preempt Unckecked: Inside a Group, the router interface that becomes master stays
master until it fails. E.g, when a backup router interface becomes master after the original
master fails, this backup router interface stays master, even if the original master with the
highest priority value is up and running again (e.g. after failure recovery).
Advertisement Interval, msec (group): default value = 1000 msec, value [100,..,10000],
stepsize = 100; the master router interface within the VRRP instance communicates its state
and priority via advertisements towards the other backup router interface. This advertising
occurs according the filled out Advertisement Interval (configured on Group level).
Preempt (group): default checked, see also Priority field;
Authentication (group): optional string field, maximum eight characters, allowed characters:
09, az, AZ, !, @, #, $, %, ^, &, *. An optional textual authentication string can be used to
communicate within the Group of that VRRP instance, e.g. pwd2. A router ignores incoming
VRRP packets for a specific Group, if the authentication string of the packets mismatches the
Authentication (group) string configured for the Group.

all Groups
single Group
single/all Groups
BG-M370-E-8 Page 97 of 189

10. The review page shows the intentional VRRP instance configuration. Click the Finish button to
configure and store the VRRP instance in the database/OMS-FEM or click << Prev to change the


12. After a Close action, whether loaded or not, the created VRRP instance is now visible via right-
click view on the VRRP instance in the VRRP list e.g. VRRP1 in the L3 Features tab on the
right-hand side. In this example, the URL is PROTOCOL://VRRP/ VRRP1.

One Group
group individual group group group
Page 98 of 189 BG-M370-E-8
5.20 DHCP Relay / Server
5.20.1 General
The symbol below is used in the OMS-FEM menu and treeviews to indicate the DHCP feature.

DHCP is a network configuration protocol in IP networks which allows that IP clients at start-up
automatically request IP configuration data from a DHCP Server. This data is necessary for the client
to be able to communicate with other IP clients within the IP network.
The most import IP configuration data for the IP client is:
Own IP Address
Subnet Mask
Default Gateway IP Address
DNS Server IP Address(es)
Domain Name
Lease Time (amount of time that the IP configuration data is valid for this IP client)
The DHCP Server assigns IP addresses from an administrated IP address pool, to its clients. Multiple
DHCP servers in the IP network are possible. All DHCP servers are stand-alone and do not know
each other. The DHCP makes sure that only one DHCP server finally supplies an IP address (and
other data) to the client.
More information can be requested from the DHCP server via the Options parameter.
When using multiple subnets, it is possible that there is no DHCP server available in the client subnet
but only a DHCP Relay function. This DHCP Relay forwards or relays the DHCP messages from
clients to the DHCP Server in another subnet and vice versa.
The N50/N70 Series node can either act as a DHCP Server or as a DHCP Relay, but never both
together.
ATTENTION: A DHCP Server/Relay can only be configured on a Full Feature Ready virtual router in
an N50/N70 series node (see 5.17, 5.28).
This DHCP wizard can create one or more DHCP instances.
Licenses: No license is required for the DHCP Server/Relay function.

5.20.2 Prerequisite
At least one Full Feature Ready virtual router that has not DCHP configured yet, must have been
created.

BG-M370-E-8 Page 99 of 189
1. In the OMS-FEM, go via Configuration L3 Features DHCP. The DHCP wizard opens.


3. In the figure below:
Fill out a DHCP Instance Name;
Make a DHCP Type Selection: DHCP Relay or DHCP Server. Note: It is advised to always
create the DHCP Relays first and then the DHCP Servers.
Make a Node Selection on which the DHCP instance must run. Only one node can be
selected. The listed nodes are nodes with a Full Feature Ready Virtual Router on board.

Page 100 of 189 BG-M370-E-8

5. Depending on the Type Selection:
for DHCP Relay, go to 5.20.3a.
for DHCP Server, go to 5.20.3b.

a. Type Selection = DHCP Relay

1. Fill out the fields below:
Configuration: DHCP Server IP Address: Fill out the IP address of the DHCP Server where
the DHCP messages are relayed to and click the Add button. The DHCP Server will be added
to the list. Repeat this step for all your DHCP Servers.
Information Option (=Option 82): Checking the Information Option results in:
Insertion of the DHCP Relay information option in DHCP request messages forwarded to a
DHCP Server from a DHCP client.
Examining/removing of the DHCP Relay information option from DHCP response
messages forwarded to the DHCP client from the DHCP server.

3. The review page shows the intentional DHCP Relay instance configuration. Click the Finish
button to configure and store this DHCP Relay instance in the database/OMS-FEM or click <<
Prev to change the configured information.

BG-M370-E-8 Page 101 of 189

5. After a Close action, whether loaded or not, the created DHCP Relay instance is now visible via
right-click view on the DHCP instance in the DHCP list e.g. DHCP1 in the L3 Features tab on
the right-hand side. In this example, the URL is PROTOCOL://DHCP/ DHCPRelay1.

b. Type Selection = DHCP Server
1. Fill out the fields below:
Discovered IP Ranges: Click this drop-down list to show the discovered IP ranges that are
available through the created Virtual Router on the selected node. Both Virtual Router VLAN
and front ports are shown. Also the directly connected VLAN and front ports of the DHCP
Relay, which refers to this DHCP Server, are shown here. Select a range from the list that
must be used as a base for the IP address pool managed by the DHCP server. Selecting a
range will also pre-fill out Start/End/Default Gateway IP Address. These IP addresses can still
be changed. Not selecting a range will leave these fields empty.
Start IP Address (required): Fill out (or verify/change if already pre-filled out) the first IP
address (with subnet mask) of the IP address pool from which the DHCP server will offer IP
addresses to the DHCP clients. Network addresses and broadcast addresses are not allowed
e.g. when subnet mask 16 is used, 10.10.0.0 and 10.10.255.255 are not allowed.
End IP Address (required): Fill out (or verify/change if already pre-filled out) the last IP
address of the IP address pool from which the DHCP server will offer IP addresses to the
DHCP clients. Network addresses and broadcast addresses are not allowed e.g. when subnet
mask 16 is used, 10.10.0.0 and 10.10.255.255 are not allowed.
Default Gateway IP Address (required): Fill out (or verify/change if already pre-filled out) the
Default Gateway IP address that must be used by the DHCP clients. If this address is part of
the configured IP address pool ([StartEnd]), this address will not be used to assign to a
DHCP client.

Page 102 of 189 BG-M370-E-8
DNS IP Address (optional): Configures the DNS IP address that must be used by the DHCP
clients. If this address is part of the configured IP address pool ([StartEnd]), this IP address
must be excluded additionally further on via Exclude IP Ranges.
Domain Name (optional): Configures the Domain Name that must be used by the DHCP
clients e.g. company.research.
Lease Time (optional): Configures the amount of time in days-hours-minutes (default value =
1 hour) that the assigned IP address to the DHCP client is valid. During this time period, the IP
address is reserved for the DHCP client and will not be assigned to other DHCP clients. During
this lease time, the DHCP client must renew its DHCP request to (possibly, if client does not
suggest another IP address itself) extend the usage of the same IP address. If the lease time
expires without renewal, the IP address might be assigned to another DHCP client.

Utilization Threshhold: future.
Netbios Server IP Address (optional): Configures the IP address of a NetBIOS and WINS
name server that is available to Microsoft DHCP. If this address is part of the configured IP
address pool ([StartEnd]), this IP address must be excluded additionally further on via
Exclude IP Ranges.
Netbios Node Type (optional): Configures the NetBIOS node type for Microsoft DHCP
clients, for the corresponding DHCP server address pool. The Netbios Node Type indicates
the method used to register and resolve NetBIOS names to IP addresses.
None: Netbios is not configured.
1: b-node: Configures the DHCP server address pool to broadcast IP messages for
registering and resolving NetBIOS names to IP addresses.
2: p-node: Configures the DHCP server address pool to have point-to-point
communication with a NetBIOS name server for registering and resolving NetBIOS names
to IP addresses.
4: m-node: Configures the DHCP server address pool to initially broadcast IP message
and then query name server for registering and resolving NetBIOS names to IP addresses.
8: h-node: Configures the DHCP server address pool to initially query name server and
subsequently broadcast IP messages for registering and resolving NetBIOS names to IP
addresses. This node type is the best option for all conditions.
TFTP Server Name (optional, =DHCP option 66, maximum 63 characters): fill out the DNS
name or IP address of the Trivial File Transfer Protocol (=TFTP) server.

Exclude IP Ranges (optional): Fill out one or more IP ranges ([Start IP Address-End IP
Address]) that must be excluded from the IP address pool that the DHCP server uses to
assign IP addresses to DHCP clients. E.g. if the available IP address pool is [10.10.10.1-
10.10.10.254] and the exclude IP address pool is [10.10.10.17-10.10.10.20], then 10.10.10.17
will for example never be assigned to a DHCP client. Click the Add button for each IP range
that must be excluded. As a result, the Exclude IP Range will appear in the exclude list and
can still be deleted later on if required.

BG-M370-E-8 Page 103 of 189

Add button: Click the Add button below to add the DHCP Server Pool Configuration to the
overview list. Expanding/Collapsing the line by clicking +/- will show/hide the excluded IP
address Range will appear in the exclude list and can still be deleted later on if required.

2. Click the Next >> button to fill out the DHCP Server Parameters. Fill out the fields below:
Ping Test Before Offer: Check this checkbox if the DHCP Server must ping (or ARP if the IP
address is not yet known) in advance the IP address that the DHCP server wants to offer to a
DHCP client. If a DHCP client answers this ping command, it means that the IP address is
already in use by a client, and that the DHCP server has to offer another IP address. An
unchecked checkbox will not ping the IP address, the IP address will be offered to the client
anyway.
Boot Server IP Address (optional): A Boot Server is a server that serves the initial boot file
that a DHCP client might need to start up. If there is a Boot Server available, its IP address
can be filled out in this field.
Boot File: The boot file contains the boot image that is used as the operating system for the
DHCP client. If there is a Boot Server, fill out the name of the initial boot file to be loaded in a
DHCP client. The file name is a text string with a maximum size of 63 characters.
Offer Reuse TimeOut: Configures the amount of time (default value = 5 s, value [1..120 s]) in
seconds, that the DHCP server must wait for the DHCP Request from the DHCP client after
sending an DHCP Offer. If no DHCP Request is received within this interval, the DHCP Server
will reuse the lease offer for another DHCP client.
DHCP Server Pool Config List
after clicking the Add button
Show/Hide
Exclude IP
address ranges
Exclude IP address ranges
Page 104 of 189 BG-M370-E-8

4. The review page shows the intentional DHCP Server instance configuration. Click the Finish
button to configure and store this DHCP Server instance in the database/OMS-FEM or click
<< Prev to change the configured information.


6. After a Close action, whether loaded or not, the created DHCP Server instance is now visible via
right-click view on the DHCP instance in the DHCP list e.g. DHCP Server in the L3 Features
tab on the right-hand side. In this example, the URL is PROTOCOL://DHCP/ DHCPServer1.

BG-M370-E-8 Page 105 of 189
5.21 IGMP (Internet Group Management Protocol)
5.21.1 General
The symbol below is used in the OMS-FEM menu and treeviews to indicate the IGMP Layer3 feature.

IGMP is a protocol used between hosts and neighbouring local multicast routers. This protocol
manages multicast-group memberships. If a host wants to receive a multicast stream, the host must
be member of the multicast group. IGMP can be used to manage/distribute multicast streaming video
and allows more efficient use of the available bandwidth and resources.
Membership queries: The local multicast router sends out membership queries to check if any of the
hosts is interested in an available multicast stream. The host can join a multicast group via sending
membership reports to the membership querier.
Join a multicast-group: The hosts or clients request membership for a specific multicast stream
(=multicast-group with specific multicast IP address) via membership reports.
Leave a multicast-group: The hosts can leave (or disconnect from) a multicast stream via a time-out
(IGMPv1), Leave group requests (IGMPv2), or membership reports (IGMPv3).
ATTENTION: IGMP can only be configured on a VLAN that is connected to a Full Feature Ready
Virtual Router (see 5.28 for more information on Full Feature Ready).
IGMP is VLAN based and runs between the router itself and the VLANs connected to its router
interfaces.
As a result, if a host that is part of a VLAN joins a multicast stream, all the other members of the VLAN
will receive the multicast-stream as well. To prevent this, configure IGMP snooping (see 5.12) on
this router interface to make sure that only the stream requester(s) is(are) receiving the stream, and
not all the other uninterested members of the VLAN.
Depending on the used IGMP version (V1, V2 or V3), querying/joining/leaving a group may differ. Find
an overview in the table below:
Query Join a group Leave a group
IGMP V1 General Query Membership Report via time-out mechanism
IGMP V2 General Query
Group Specific Query
Membership Report via Leave Group messages
IGMP V3 General Query
Group Specific Query
Membership Report (join), SSM
(=source specific multicast) =
only want to receive streams
from a defined set of source IP
addresses.
Membership Report (leave)

Licenses: An Enhanced License Pack is required on the nodes that participate in IGMP.
NOTE: IGMP Monitoring from the live network is also possible, see 10.6.

1. In the OMS-FEM, go via Configuration L3 Features IGMP. The IGMP wizard opens.


Page 106 of 189 BG-M370-E-8

3. In the figure below, select one of the available VLANs on which you want to configure IGMP. Only
one VLAN can be selected per IGMP instance and (*) only VLANs are shown that are configured
in a Full Feature Ready Virtual Router (see also 5.28).


5. In the figure below, select one or more Virtual Routers on which you want to configure IGMP.


7. In the window below, VLAN properties can be configured specific for the chosen VLAN. Click the
Next >> button to review the information.
Leave Mode: configures the Leave Mode, Normal or Fast.
BG-M370-E-8 Page 107 of 189
Normal (=default): the port is not immediately removed from the multicast group when a
leave message is detected on that port. First some group specific queries are sent on that
port, and if no membership report is received within a time interval on that port for that
multicast group, the port will be removed from that multicast group.
Fast: the port is immediately removed from the multicast group when a leave message is
detected on that port.
Group Specific Query Interval: (default value = 10 s, min. 1 s, max. 255 s) Configures the
time interval after which the N50/N70 node sends a group specific query on a port.
Query Interval: (default value = 125 s, min. 11 s, max. 65535 s) is the amount of time in
seconds between IGMP General Query messages sent by the querier, if this node is the
querier.
Max Response Time: (default value = 100 1/10 s= 10 seconds, min. 1 1/10 s, max. 255
1/10 s) Specifies the period in tenths of a second during which the host is expected to
respond to an IGMP query.
Robustness: (default value = 2, min. 2, max. 255) Configure this parameter to indicate how
well your network can recover from lost IGMP packets. If you have a very stable network, the
Robustness value will be very low. For less stable networks, the Robustness value must be
set higher or high. E.g. if the Robustness value = 3, your network can recover from
(robustness-1) IGMP packets = (3-1) = 2 IGMP Packets. Changing the Robustness variable
automatically modifies certain IGMP message intervals for IGMPv2 and IGMPv3. Increasing
this value allows for more packet loss but increases the leave latency of the subnetwork.
IGMP Version: Indicates the used IGMP version: V1, V2 (=default), V3

9. The review page shows the intentional IGMP instance configuration. Click the Finish button to
configure and store the IGMP instance in the database/OMS-FEM or click << Prev to change the

Page 108 of 189 BG-M370-E-8
11. After a Close action, whether loaded or not, the created IGMP instance is now visible via right-
click view on the VLAN in the IGMP list e.g. VLAN2 in the L3 Features tab on the right-hand
side. In this example, the URL is PROTOCOL://IGMP/ VLAN2.

BG-M370-E-8 Page 109 of 189
5.22 OSPF
5.22.1 General
The symbol below is used in the OMS-FEM menu and treeviews to indicate the OSPF Layer3 feature.

OSPF is a dynamic routing protocol for IP networks. A dynamic routing protocol always determines the
best possible routing path. For example, determined routes may dynamically change because a
specific route becomes less or more preferred than before.
The concept of OSPF is that routers advertise updates of their link states to neighbouring routers.
And the neighbouring router does the same to its neighbouring router and so on. In other words,
each router learns from the other routers based on link state advertisements (=LSA). OSPF is a fast
protocol because only updates are advertised.
OSPF checks the availability of others routers in the network by sending Hello packets. If the other
router does not respond then it is assumed to be a dead router.
Some definitions:
Autonomous System (AS): largest entity within the OSPF routing hierarchy, a logical unit used in
OSPF to segment a large network into smaller parts, a collection of networks that share the same
OSPF routing instance.
Area: a group of routers and hosts which is a subset of the entire AS, an AS can be organized in a
number of Areas. Each Area has its own routing topology, resulting in reduced routing table sizes
and processor load. It also limits the amount of flooding of link state updates over the enitre
network.
Backbone Area: it is the central Area that distributes routing information between other Areas,
there is only one backbone Area within an AS.
Stub Area: is only connected to the Backbone Area. Stub Areas only receive routes from
within the AS (not from outside the AS).
Totally Stub Area: is only connected to the Backbone Area. Totally Stub Areas do not
advertise routes from outside its Area. The only route that is advertised is the default route to
the ABR (=Area Border Router). The Totally Stub Area communicates with the rest of the
network via this default route.
Virtual Links: Not supported.
Area Border Router (ABR): an ABR connects one or more Stub or Totally Stub Areas to the
Backbone Area. An ABR has multiple copies of the link-state database in memory, one copy for
each area to which that ABR is connected. Routers in areas use ABR as next hop to access
external addresses. ABR forwards packets to the ASBR that announces the external addresses.
Autonomous System Boundary Router (ASBR): an ASBR must be part of the Backbone Area
and connects the AS to another non OSPF AS. An ASBR can interconnect different routing
protocols and exchange routing information between them. ASBRs typically run an exterior routing
protocol or use static routes or a mix of them. An ASBR is used to distribute routes received from
other, external ASes throughout its own OSPF AS.
Page 110 of 189 BG-M370-E-8

This OSPF wizard can create Autonomous Systems, Areas and configure its OSPF instances
accordingly.
ATTENTION:
OSPF can run on any virtual router, not only on a Full Feature Ready (see 5.28) Virtual
Router.
If Loopback Interfaces (see Add Loopback Interface in 5.4.3) are used on a virtual router,
make sure to enable the Redistribute option for that virtual router or node. This is necessary
for PIM-SM, to make sure that this loopback interface is known within the entire PIM-SM
component.
Licenses: An Enhanced License Pack is required on the nodes that participate in the OSPF
instance.
NOTE: OSPF Monitoring from the live network is also possible, see 10.8.
1. In the OMS-FEM, go via Configuration L3 Features OSPF. The OSPF wizard opens.

3. New or existing Autonomous System (AS)?
Create AS see paragraph 5.22.2a below;
Select Existing AS see paragraph 5.22.2b below;
ASBR ABR
Backbone Area Stub Area
BG-M370-E-8 Page 111 of 189

a. Create Autonomous System
1. In the figure below, select Create Autonomous System and fill out the name of the Autonomous
System (=AS) e.g. AS1.
2. Click the Enter button on your keyboard and click the Next >> button in the wizard.

3. In the figure below, an Area can be configured within the AS.
NOTE: It is possible that in the OMS-FEM only a (Totally) Stub Area is created and not a
Backbone Area, because a Backbone Area could be configured in another third-party
network.

4. Following fields must be configured:
Area Name: The name of the Area.
Area Type: Select one of the possible Area types:
Backbone: This area has always Area Number 0.0.0.0. All other Stub or Totally Stub
Areas will always be directly connected to this Backbone Area. A Backbone Area can
receive routes from outside and inside the AS.
Stub: This Area is only connected to the Backbone Area and only receives routes from
inside the AS. It also receives the default route from the ABR.
Totally Stub: This Area is only connected to the Backbone Area and only receives the
default route (which gives access to the rest of the network) from the Backbone Area.
Area Number: is a unique number that identifies the Area. This number is 0.0.0.0 for the
Backbone Area and is different from 0.0.0.0 for any other Area.
Compatible RFC 1583: (default = checked) If checked, the Summary Route route costs are
calculated according standard RFC 1583.
Checked (=compatible): the Summary Route cost is based on the lowest cost (=best
cost) among the summarized routes. E.g. if the costs of three individual routes are 50, 100
and 200, the cost of the summarized route will be 50.
Page 112 of 189 BG-M370-E-8
Unchecked (=not compatible): the Summary Route cost is based on the highest cost
(=worst cost) among the summarized routes. E.g. if the costs of three individual routes are
50, 100 and 200, the cost of the summarized route will be 200.
NOTE: Make sure to set Compatible RFC 1583 identically in the entire AS to minimize the
chance of routing loops.

5. In the figure below, select the interfaces (VLAN, SLAN or ELAN ports) on the virtual routers that
will be part of the configured Area.
NOTE: A Virtual Router can only be part of one OSPF AS, thus it cannot be split over two or
more ASes, even if the Virtual Router would be configured as an ASBR.


7. In the figure below, configure the type of each virtual router in the Area. The virtual router can be
configured as an ASBR or an ABR. An ASBR can only be configured in the Backbone Area. Find
below all the parameters that can be configured according to the chosen router type:

BG-M370-E-8 Page 113 of 189

Router ID: This is a unique number that identifies the OSPF router. It is pre-filled out with the
IP address of the first listed router port of that Virtual Router. The Router Id field can be
adapted but is has to be unique throughout the AS.
ASBR Router: Check this checkbox if this Virtual Router must be configured as an ASBR. It
can only be checked if it concerns a Virtual Router in the Backbone Area (0.0.0.0). For other
areas, ASBR can not be configured. External Route (=route from outside the AS) redistribution
can only be performed by an ASBR. The fields listed below can be configured for an ASBR:
Redistr Conn: (default = unchecked) checking this parameter enables the redistribution of
the networks directly connected to the virtual router. If loopback interfaces (see Add
Loopback Interface in 5.4.3) are used on this virtual router, make sure to enable this
Redistr Conn checkbox. This is necessary for PIM-SM, to make sure that this loopback
interface is known within the entire PIM-SM component.
Redistr Stat: (default = unchecked) checking this parameter enables route redistribution of
the static routes into OSPF.
Def Info Orig Always: (default = unchecked) checking this parameter forces the ASBR to
propagate a default route into the OSPF routing domain.
NOTE: a default route still has to be created via Static Routing (see 5.18) in the ASBR to
route outside the AS.
Def Info Orig Always Cost: (default value = 0, range [0,..,254]) fill out this parameter to
assign a route cost to the default route (0.0.0.0/0).
Summ Ext Routes: Click this field to create summary reports. Such a summary report is
an aggregation of external routes or external Network Addresses (outside the AS). These
summary reports will be distributed within the Areas. In the figure below, fill out the
Network Address and click the Add button to add it into the Summ Ext Routes list.
E.g. if you have external addresses 10.0.1.0/24, 10.0.3.0/24, 10.0.3.0/24, 10.0.205.0/24, it
could be summarized (or added) in the Summ Ext Routes list as 10.0.0.0/16. Entries can
be removed by clicking the row-header-cell followed by clicking the Remove button. Click
the OK button to close the window for Summarising external routes.

ABR Router: Check this checkbox if this Virtual Router must be configured as an ABR. It can
always be configured in any Area. The fields listed below can be configured for an ABR:
ABR Type: Standard (=default), Cisco or IBM (refer to RFC 3509).
Default Route Cost: (default value = 1, range [0,..,30]) fill out this parameter to assign a
cost to the default route which is propagated into this Stub or Totally Stub Area.
Page 114 of 189 BG-M370-E-8
Summ Inter-area Routes: Click this field to create summary reports. Such a summary
report is an aggregation of external routes or external Network Addresses (outside the
Area, but inside the AS). These summary reports will be distributed within the Area, never
outside the Area. In the figure below, fill out the Network Address and click the Add button
to add it into the Summ Inter-area Routes list.
E.g. if you have external addresses 15.0.1.0/24, 15.0.3.0/24, 15.0.3.0/24, 15.0.205.0/24, it
could be summarized (or added) in the Summ Inter-area Routes list as 15.0.0.0/16.
Entries can be removed by clicking the row-header-cell followed by clicking the Remove
button. Click the OK button to close the Summ Inter-area Routes window.

8. Your resulting window could look as in the figure below. Click +/- to expand/collapse the list with
Summ Ext Routes and/or Summ Inter-area Routes:


10. In the figure below, the OSPF Interface parameters can be tuned:

Retransmit Interval (sec): (default=5 s, range [0,..,3600]) This value configures the time
interval between the retransmission of successive LSAs. Each new LSA must be
acknowledged. The LSA will be retransmitted by the originating router according the
Retransmit Interval until it has been acknowledged by the neighbour router.
Transmit Delay (sec): (default=1 s, range [0,..,3600]) This value configures the estimated time
required to transmit a link state update packet on the interface using this configuration. This
variable adds a specified time to the age field of an update. If the delay is not added before
transmission over a link, the time in which the link-state advertisement (LSA) propagates over
BG-M370-E-8 Page 115 of 189
the link is not considered. The default value is 1 second. This parameter has more significance
on very low-speed links.
Hello Interval (sec): (default=10 s, range [1,..,65535]) This value configures the (OSPFv2
Hello) interval between the hello packets sent on the interface. Hello Packets are sent between
two OSPF neighbours to maintain connectivity. The Hello Interval must be the same for all
(virtual) router interfaces attached to the same link. See also the Dead Interval parameter.
ATTENTION: OSPF neighbours must have the same Hello Interval value !
Dead Interval (sec): (default=40 s, range [1,..,65535]) The Dead Interval and Hello Interval
work together to maintain the operational link between two OSPF neighbours. If a virtual router
interface does not receive an Hello packet within the configured Dead Interval, the (virtual)
router decides that the neigbouring (virtual) router is dead or down. By default, the Dead
Interval is four times the Hello Interval. ATTENTION: OSPF neighbours must have the same
Dead Interval value !
Priority: (default=1, range [1,..,255]) This value configures the interface priority to determine
the Designated Router (DR) for the link connected to the interface. In the DR election process
the highest Priority wins and becomes DR. If the two DR candidates have the same Priority,
the highest Router Id (RID) wins.
Cost: (default=10, range [1,..,65535]) This value configures the cost metric value added to a
route on this interface. Following formula can be used as a rule of thumb to define the Cost for
a specific route. Cost = 1000 / Link Speed in Mbps, e.g. if your link speed = 100 Mbps, then
you could set your Cost to 1000/100 = 10. This formula works fine if your highest link speed in
the OSPF domain is 1 Gbps (=1000 Mbps) Cost = 1000 / 1000 = 1. With 1 being the
lowest possible Cost, a link speed of 10 Gbps would result in a Cost = 1000 / 10000 = 0.1
which is not valid. Therefore, if your network has link speeds higher than 1Gbps, other
customized finetuning formulas can be used to fill out the Cost parameter.
Auth Type: OSPF authentication can be done via selecting one of the following authentication
types listed below. ATTENTION: Make sure that neighbouring routers (or virtual router
interfaces) use the same Auth Type and Auth Field.
None: There is no OSPF authentication at all on this virtual router interface.
Auth Text: Authentication on this virtual router interface is done based on Simple
Password Authentication, a password must be specified in the Auth Field (alphanumeric
input) which is to be used by the neighboring routers that are using the OSPF simple
password authentication.
Message Digest: Authentication on this virtual router interface is done via md5
cryptographic authentication. A password must be specified in the Auth Field
(alphanumeric input) which is to be used by the neighboring routers that are using the
OSPF Message Digest authentication.
Auth Field: (alphanumeric input) Fill out a password or an authentication key that must be
used for authentication when Auth Type is Auth Text or Message Digest. ATTENTION: Make
sure that neighbouring routers (or virtual router interfaces) use the same Auth Type and Auth
Field.
Passive: Check the checkbox to make this virtual router interface passive. A passive virtual
router interface ignores routing updates on this interface and does not send Hello packets. A
passive interface could be set for interfaces that do not have neighbours. This parameter can
also be used for testing or troubleshooting purposes.
Page 116 of 189 BG-M370-E-8

12. The review page shows the intentional OSPF instance configuration. Click the Finish button to
configure and store the OSPF instance in the database/OMS-FEM or click << Prev to change the


14. After a Close action, whether loaded or not, the created OSPF instance for an Area is now visible
via right-click view on the Area in the OSPF-Area list e.g. BackboneArea in the L3 Features
tab on the right-hand side. In this example, the URL is PROTOCOL://OSPF/ BackboneArea.

b. Select Existing Autonomous System

1. In the figure below, select Select Existing Autonomous System and select the existing AS out
of the AS drop-down list. e.g. AS1.

Neighbouring routers
same Authentication
BG-M370-E-8 Page 117 of 189

2. Click the Next >> button in the wizard.

3. From now on, all the wizard pages are the same as in 5.22.2a (Create Autonomous System)
starting from the Area Configuration page. Configure the new Area accordingly.

4. As a result, two or more Areas (e.g. BackboneArea and StubArea1) will be created in the
Autonomous System AS1. These two or more Areas are listed in the figure below.

Page 118 of 189 BG-M370-E-8
5.23 PIM-SM
5.23.1 General
The symbol below is used in the OMS-FEM menu and treeviews to indicate the PIM-SM Layer3
feature.

PIM (Protocol-Independent Multicast) is a multicast routing protocol. It is protocol-independent
because PIM does not have a network topology discovery mechanism like other routing protocols
have. PIM uses routing information supplied by other routing protocols. PIM builds up Multicast
Distribution Trees for each IP Multicast Group Address. As a result, data packets from senders to a
multicast group reach all receivers which have joined the group via IGMP.
Some important definitions:
First Hop Router (FHR): This is the router that connects the multicast source (e.g. video server)
to the PIM network.
Last Hop Router (LHR): This is the router that connects the multicast receiver or client (=host) to
the PIM network.
Bootstrap Router (BSR): A BSR is a router which is elected amongst BSR candidates. A BSR
can be considered as the master of the PIM-SM component within the network. BSR is also a
standard-based protocol in PIMv2. The Rendez-Vous Point (RP) candidates (see below) will report
their candidacy to the elected BSR. Out of these candidates, the BSR generates multicastgroup-
to-RP mappings and distributes these to all the routers in the PIM domain through Bootstrap
messages. As a result, each router knows via where it can get a specific multicast stream.
Rendez-Vous Point (RP):
An RP is a router acting as a central multicast stream collector for a specific multicast range.
Each new stream that enters the network via the FHR, must first be registered via unicast
traffic to one of the available RPs. During registration, the multicast stream is embedded in the
unicast traffic.
If a host wants to receive a multicast stream, it must first join the stream via the LHR that
forwards the join message to the RP. Once the LHR receives the stream, it knows the source
of the multicast stream. At that point, it is more efficient that the LHR bypasses the RP (for this
multicast stream) and communicates directly to the multicast source. As a result, the LHR will
send a prune message to the RP and a join message to the multicast source for this multicast
stream.
This wizards supports PIM-SM (PIM Sparse Mode). Other modes are not supported.
ATTENTION: PIM-SM can only be configured on a Full Feature Ready Virtual Router (see 5.28 for
more information on Full Feature Ready).
This PIM-SM wizard can create one or more PIM-SM instances.
Licenses: An Enhanced License Pack is required on the nodes that participate in the PIM instance.
NOTE: PIM-SM Monitoring from the live network is also possible, see 10.7.
5.23.2 Prerequisite
At least one virtual router with Full Feature Ready enabled must have been created.
Strong advise: Add a Loopback Interface (see Add Loopback Interface in 5.4.3) to each virtual
router that will be Bootstrap-Router candidate (BSR-c) and/or Rendez-vous Point candidate (RP-c)
in the PIM-SM protocol. As long as the node is up and running, these Loopback Interfaces will
always be reachable and make sure that a BSR-c and/or RP-c on these nodes will always be
available.
BG-M370-E-8 Page 119 of 189
1. In the OMS-FEM, go via Configuration L3 Features PIM. The PIM wizard opens.


3. In the figure below, fill out following fields:
Component Name: Assign a name to the PIM-SM component. A PIM-SM component
corresponds to the PIM domain and classifies it as Sparse mode. A PIM-SM domain is defined
as an area of the network over which bootstrap messages are forwarded. Typically, a PIM-SM
router will be a member of exactly one domain.
Virtual Router Selection: Select the Virtual Routers (=all VLANs on this Virtual Router) or
only some VLAN ports that must be part of this PIM-SM component. Expanding the Virtual
Router shows the available VLANs on this router. ATTENTION: VLANs that have IGMP
Snooping MAC based configured are not shown.

Page 120 of 189 BG-M370-E-8

4. Click the Next >> button
5. In the figure below, the PIM Interface is configured. Following parameters can be configured per
virtual router interface:
Query Interval: value in the range [0,..,65535] s, default value = 30s, sets the frequency in
seconds at which PIM Hello (=query) messages are transmitted on this interface. The query
message informs the presence of a PIM router on this interface to the neighboring PIM routers.
Message Interval: value in the range [0,.., 65535] s, default value = 60s, sets the frequency in
seconds at which Join messages are transmitted on this interface to keep the receival of a
joined multicast stream alive. The same Join message interval must be used on all the PIM
routers in the PIM domain. If all the routers do not use the same timer interval, the
performance of PIM-SM can be adversely affected.


7. In the figure below, out of the previously selected Virtual Router interfaces, indicate which one
must act as BootStrap Router Candidate (BSR-C). Later on, when PIM is up and running in the
network, the Bootstrap Router (BSR) will be elected dynamically by means of bootstrap messages
and the BSR-C Priority. The highest BSR-C priority wins, and will become the active BSR. The
other candidates become standby BSRs.

BG-M370-E-8 Page 121 of 189


9. In the figure below, set the Priority for each BSR-C. This value is in the range [0,.., 255], default
value=0. The Priority will be used for the BSR election process later on in the network. The
highest priority wins.


11. In the figure below, out of the previously selected Virtual Router interfaces, indicate which one
must act as Rendez-Vous Point Candidate (RP-C). Later on, when PIM is up and running in the
network, the RP-Cs will advertise themselves to the BSRs.

Page 122 of 189 BG-M370-E-8

13. In the figure below, fill out the following fields:
Priority: Indicates the Priority for each RP-C. This value is in the range [1,.., 255], default
value=192. The Priority will be used later on for electing a specific RP for a specific Multicast
address group or range. For the same multicast address ranges, the lowest Priority wins and
becomes the RP for that multicast address range. The other interfaces become standby RPs.
Multicast Address Ranges: After clicking the Set... button, the multicast address Range(s) for
which the RP will be responsible can be filled out.
Start Group Address: Fill out the start group address (which is a valid multicast address
range e.g. 224.100.100.3/24) for which this RP is responsible. Click the Add button to add
this address to the RP Start Group Address list. Repeat this step until all the multicast
address ranges are configured for this RP. Click the OK button to close this window.
Hold Time: The RP candidate Hold Time defines the time interval (in seconds) till which the
RP candidate advertisement is valid, when the router is a RP candidate in the local domain.
The hold time defines the age for the RP advertisement. This value is in the range [65,.., 255],
default value = 80.

14. After adding your Start Group Addresses, the Rendez-vous Point Configuration window could
look as follows (click +/- to expand/collapse the Start Group Addresses list):

BG-M370-E-8 Page 123 of 189

16. The review page shows the intentional PIM instance configuration. Click the Finish button to
configure and store the PIM instance in the database/OMS-FEM or click << Prev to change the


18. After a Close action, whether loaded or not, the created PIM instance is now visible via right-
click view on the PIM instance in the PIM list e.g. PIMCom1 in the L3 Features tab on the
right-hand side. In this example, the URL is PROTOCOL://PIM/ PIMComp1.

Page 124 of 189 BG-M370-E-8
5.24 Front Port/External LAN/SLAN Mapping
N50/N70 series node front ports and External LANs can be mapped to segments (or SLANs) via
creating a VLAN in the OMS-FEM. See also chapter 5.9.

5.25 Tagged/Untagged Ports
Access ports (=front port connected to end-device, e.g. camera, laptop) are always untagged.
This means that this port does not expect or sends out messages with a VLAN ID. Tagged
messages are discarded. See also chapter 5.9.
SLAN Ports/External LAN ports, with 802.1Q VLAN Trunking = Tagged are always tagged ports.
This means that this port only expects or sends out messages with a VLAN ID. Untagged
messages are discarded. See also chapter 5.9.

5.26 802.1Q VLAN Trunking
This feature allows multiple VLANs to use the same physical link. This feature is possible on External
LANs and SLANs.
If you want to send out packets over a trunked VLAN into the outside world, you need an External LAN
with 802.1Q VLAN Trunking = Tagged or All. This behaviour is not possible via access ports. The
front port must have been configured as External LAN to reach this goal. See also chapter 5.8.

5.26.1 SLANs
Although SLANs are created and configured in the OMS GUI, the 802.1Q VLAN Trunking feature
which is by default set to Untagged/Priority Tagged, must be modified via the OMS-FEM. This
setting can be changed via right-clicking the desired SLAN in the SLANs treeview and select Modify.
As a result, the SLAN wizard (= Reused External LAN wizard) will be opened. For further steps in the
(Reused) External LAN wizard, see chapter 5.8.

SLAN wizard =
Reused External
LAN wizard
BG-M370-E-8 Page 125 of 189
5.26.2 External LANs
When an External LAN is created in the OMS-FEM, the 802.1Q VLAN Trunking is by default set to
All. This setting can be changed via right-clicking the desired ELAN in the SLANs treeview and
select Modify. As a result, the External LAN wizard will be opened. For further steps in the External
LAN wizard, see chapter 5.8.

5.27 ELAN/SLAN/VLAN (Trunking)/Tagged/Untagged Example
5.27.1 Introduction
Prerequisite: your N50/N70 nodes have been created in the OMS GUI and OMS-FEM.
Example: End-devices (e.g cameras, laptops) and external switches are connected to your
N50/N70 nodes. Interconnect two N50/N70 nodes via an SLAN (=OTN-X3M ring). The N50/N70
nodes must process messages in two different VLANs (VLAN10 and VLAN20). Possible untagged
packets from the External LAN are processed via a separate third VLAN (VLAN5). Only tagged
packets travel over the created SLAN between the two nodes. See the final scenario in the figure
example below. In the following pages, it is explained how to build up this scenario via the OMS-FEM:

2-A 5-A 3-E
U
T20
T10
U
U
T20 T10
2-S
U
U U
VID
20
VID
10
VID
5
T5
T5
2-A 5-A 3-E
U
U
2-S
U
U U
VID
20
VID
10
VID
5
T5
U
T20
T10
Node 17
X3M-Station A
Node 18
X3M-Station B
SLAN
ACCESS
ELAN
Page 126 of 189 BG-M370-E-8
Attention: The picture above is just an example to show what is possible, but the advised solution for
OTN applications is that each application can have its own SLAN. As a result and by default, each
SLAN will only allow untagged frames.
Attention: In the following pages below, obvious OMS GUI and OMS-FEM screenshots (e.g. Load
screenshots etc) are not shown, only relevant screenshots for the scenario set-up are displayed.
To set up an entire VLAN/SLAN/ELAN scenario, with the possibility of VLAN trunking and
tagged/untagged frames, basically following steps must be followed:
a. Learn the different port types;
b. Create an SLAN (=service) between the nodes;
c. (eventually) Modify SLAN: VLAN Trunking: (All/Untagged/Tagged);
d. Create external LANs (=ELANs) to connect to external switches;
- Define ELAN name;
- Consider VLAN trunking (all/tagged/untagged);
- Select the front port(s) that must be part of the ELAN;
e. Glue it all together: Create the VLANs
- Define VLAN name and ID;
- Assign or map the access ports to the correct VLAN;
- Assign or map the ELAN ports to the correct VLAN;
- Assign or map the SLAN ports to the correct VLAN;
- Consider tagged/untagged frames for this VLAN, valid for both VLAN ingress and egress;

5.27.2 Learn the different Port Types
In this example, two nodes (Node 17 and 18) have been created in the OMS GUI. Following different
port types must be considered.
a. Access ports (x-A)
An access port is a front port connected to an end-device. Two cameras are connected to front ports
2 and 5 in node 17 and two laptops to front ports 2 and 5 in node 18; Access ports are always
untagged ports, for both ingress and egress;
b. ELAN ports (y-E)
An ELAN port is a front port connected to external switch. In each node, an external switch has been
connected to front port 3. A front port turns into an ELAN port after it has been configured as such
(see further on). ELAN ports can be configured as tagged, untagged or all.
c. SLAN ports (z-S)
An SLAN port is an internal N50/N70 port that can interconnect to one or more N50/N70 nodes via the
OTN-X3M ring. This can be performed by creating an ethernet service (GET, ET100HX4 or ET100) in
the OMS GUI. In this example SLAN port 2 is used in both nodes.

X3M-StationB X3M-StationA
Node 17 Node 18
Access Port x-A =
port to end device
ELAN Port y-E =
port to switch or
external LAN
SLAN Port z-S =
port to OTN-X3M
ring or SLAN
2-A 5-A 3-E 2-A 5-A 3-E
2-S 2-S
BG-M370-E-8 Page 127 of 189

These nodes are created in the OMS GUI and are also visible in the OMS-FEM, see picture below.

5.27.3 Create SLAN (=service) Between Nodes

In the OMS GUI, create an ethernet service (GET, ET100HX4 or ET100) via Configuration Create
Service and make sure that SLAN port 2 in both node 17 and 18 are added to this service.
NOTE: SLAN port = BORA-N50/N70 Segment port

2-A 5-A 3-E
2-S
2-A 5-A 3-E
2-S
Node 17 Node 18
Create an SLAN
(=GET Service) in
OMS Gui
Page 128 of 189 BG-M370-E-8

After completing the service creation wizard, the OMS-FEM could look as in the figure below:

5.27.4 Modify SLAN: VLAN Trunking: Untagged Tagged
By default, the SLAN is programmed as an untagged link. In this example, we need a tagged link on
the SLAN. Therefore, the configured value on the 802.1Q VLAN Trunking feature must be modified
from untagged to tagged.
In the OMS-FEM, right-click the available SLAN and click Modify.

BG-M370-E-8 Page 129 of 189
In the modify wizard below, change the 802.Q VLAN Trunking value from Untagged/Priority
Tagged into Tagged.

5.27.5 Create External LANs (=ELANs) to External Switches

An external switch can be connected to an N50/N70 node via an ELAN port. Therefore an External
LAN (or ELAN port) must be created in each node. This means that each node will have its own
individual External LAN (or ELAN port) for each external switch, e.g. ELAN_A in Node 17 en ELAN_B
in Node 18.
In the OMS-FEM, create an External LAN via Configuration Equipment External LAN.
2-A 5-A 3-E
2-S
2-A 5-A 3-E
2-S
Node 17 Node 18
Create an open
ELANin OMS-FEM
Create another open
ELANin OMS-FEM External Switch
Page 130 of 189 BG-M370-E-8

Set the 802.1Q VLAN Trunking to All (All = default). This means that both tagged (=multiple
VLANs possible) and untagged frames can enter or ingress the ELAN (front) port. Select only front
port 3 of node X3M-StationA (=Node 17).

Repeat the two previous steps for another ELAN (e.g. ELAN_B) in front port 3 of node X3M-StationB
(=Node 18).
After the ELANs creation, both ELANs are visible in the OMS-FEM:

ELAN Port
Ingress rule
Open ELAN_A Open ELAN_B
BG-M370-E-8 Page 131 of 189
5.27.6 Glue it all together: Create VLANs
Following steps have to be done:
- Define VLAN names and IDs;
- Assign or map the access ports to the correct VLAN: 10 or 20;
- Assign or map the ELAN ports to the correct VLAN: 5, 10 or 20;
- Assign or map the SLAN ports to the correct VLAN: 5, 10 or 20;
- Consider tagged/untagged frames for this VLAN, valid for both VLAN ingress and egress;
In the OMS-FEM, create VLANs via Configuration VLAN

Define VLAN10, assign Access Ports to VLAN10:
Click Next >>. In the window below, define a VLAN name e.g. VLAN10 and assign VLAN ID 10 to it.
Furthermore, assign access port 2 from X3M-StationA and X3M-StationB to this VLAN10.

2-A 5-A 3-E
2-S
VID
10
2-S
Node 17
X3M-Station A
Node 18
X3M-Station B
2-A 5-A 3-E
VID
10
Define VLAN 10
in OMS-FEM
Assign Access
Ports to VLAN
2-A 5-A 3-E
2-S 2-S
Node 17
X3M-Station A
Node 18
X3M-Station B
2-A 5-A 3-E
Assign
Access Ports
to VLAN 10
VID
10
VID
10
Page 132 of 189 BG-M370-E-8
Assign ELANs to VLAN10, assign SLAN to VLAN10:
Click Next >>. In the window below, assign ELAN_A (=X3M-StationA), ELAN_B (=X3M-StationB) and
GET1 (=SLAN) to VLAN10 by checking the Add to VLAN checkboxes.

Consider tagged/untagged frames for VLAN10
For both ELANs: uncheck the untagged checkbox
For the SLAN: untagged checkbox stays unchecked
ELAN/SLAN Ports:
the untagged checkbox both influences the ingress and egress behaviour for that specific ELAN/SLAN
port within that specific VLAN.
Tagged frames:
If the untagged checkbox is unchecked for a specific ELAN/SLAN in a specific VLAN:
- incoming (=ingress) untagged frames (if any) on an ELAN/SLAN port will be ignored for this
specific VLAN;
- this specific VLAN will always send out (=egress) tagged packets on this specific ELAN/SLAN
port.

Untagged frames:
If the untagged checkbox is checked for a specific ELAN/SLAN in a specific VLAN:
- incoming (=ingress) untagged frames (if any) on an ELAN/SLAN port will be assigned or mapped
to this specific VLAN;
- this specific VLAN will always send out (=egress) untagged packets on this specific ELAN/SLAN
port.
- Checking the untagged checkbox can only be done for one VLAN for this specific ELAN/SLAN.

Example: if you leave the untagged checkbox unchecked for ELAN_A in VLAN10, incoming
untagged packets on ELAN_A will never be assigned to VLAN10. Furthermore, VLAN10 will always
send out tagged packets on ELAN_A.

2-A 5-A 3-E
2-S 2-S
Node 17
X3M-Station A
Node 18
X3M-Station B
2-A 5-A 3-E
VID
10
2-A 5-A 3-E
2-S 2-S
Node 17
X3M-Station A
Node 18
X3M-Station B
2-A 5-A 3-E
VID
10
Assign
SLAN
to VLANs
Assign
ELANs to
VLANs
Assign ELANs
to VLAN
Assign SLAN
to VLAN
VID
10
VID
10
BG-M370-E-8 Page 133 of 189

The final flow for VLAN10:

Repeat previous steps for VLAN20 (access port 5), resulting in the flow below:

2-A 5-A 3-E
2-S 2-S
Node 17
X3M-Station A
Node 18
X3M-Station B
2-A 5-A 3-E
VID
10
2-A 5-A 3-E
2-S 2-S
Node 17
X3M-Station A
Node 18
X3M-Station B
2-A 5-A 3-E
VID
10
VID
10
VID
10
T10
U
T20
T10
U
T20
T10
Only
tagged
frames
fromELAN
allowed on
VLAN 10
ELAN Ports: tagged/untagged behaviour:
Checked:
Ingress: all incoming untagged traf f ic f rom external on this ELAN port is assigned to VLAN 10
Egress: VLAN 10 will always send out untagged traf f ic on these ELAN ports
SLAN Ports: tagged/untagged behaviour (Read-only,
can only be changed via Modify SLAN in SLANs tab):
Unchecked:
Ingress: all incoming untagged traf f ic on this SLAN port is dropped or lost
Egress: VLAN 10 will always send out tagged traf f ic on these SLAN ports
Only
tagged
frames
allowed
on SLAN
2-A 5-A 3-E
U
T20
T10
U
T10
2-S
U
U
VID
10
2-A 5-A 3-E
U
2-S
U
U
VID
10
U
T20
T10
Node 17
X3M-Station A
Node 18
X3M-Station B
2-A 5-A 3-E
U
T20
T10
U
U
T20 T10
2-S
U
U
VID
20
VID
10
2-A 5-A 3-E
U
U
2-S
U
U
VID
20
VID
10
U
T20
T10
Node 17
X3M-Station A
Node 18
X3M-Station B
Page 134 of 189 BG-M370-E-8
Map the untagged packets to VLAN5:
Define VLAN5, No Access Ports must be assigned to VLAN5

Assign ELANs to VLAN5, assign SLAN to VLAN5

Consider tagged (SLAN) / untagged (ELAN) frames for VLAN5
For both ELANs: check the untagged checkbox to map untagged packets from these
ELANs to VLAN5
For the SLAN: untagged checkbox stays unchecked. In this example, no untagged
packets allowed on the SLAN
NOTE: Untagged packets from a specific ELAN can only be mapped to one VLAN
2-A 5-A 3-E
U
T20
T10
2-S
2-A 5-A 3-E
2-S
U
T20
T10
Node 17
X3M-Station A
Node 18
X3M-Station B
VID
5
VID
5
Define VLAN5
in OMS-FEM
No access ports
must be selected
2-A 5-A 3-E
U
T20
T10
T20 T10
2-S
2-A 3-E
2-S
U
T20
T10
Node 17
X3M-Station A
Node 18
X3M-Station B
VID
5
VID
5
2-A 5-A 3-E
U
T20
T10
T20 T10
2-S
2-A 5-A 3-E
2-S
U
T20
T10
Node 17
X3M-Station A
Node 18
X3M-Station B
Assign ELANs
to VLAN
Assign SLAN
to VLAN
VID
5
VID
5
Assign
SLAN
to VLAN5
Assign
ELANs to
VLAN5
5-A
BG-M370-E-8 Page 135 of 189

All together and final result:

2-A 5-A 3-E
U
T20
T10
T20 T10
2-S
2-A 5-A 3-E
2-S
U
T20
T10
Node 17
X3M-Station A
Node 18
X3M-Station B
VID
5
VID
5
2-A 5-A 3-E
U
T20
T10
T20 T10
2-S
2-A 5-A 3-E
2-S
U
T20
T10
Node 17
X3M-Station A
Node 18
X3M-Station B
VID
5
VID
5
Only Untagged
frames from ELAN
allowed on VLAN5
ELAN Ports: tagged/untagged behaviour:
Checked:
Ingress: all incoming untagged traf f ic f rom external on this ELAN port is assigned to VLAN5
Egress: VLAN5will always send out untagged traf f ic on these ELAN ports
SLAN Ports: tagged/untagged behaviour (Read-only,
can only be changed via Modify SLAN in SLANs tab):
Unchecked:
Ingress: all incoming untagged traf f ic on this SLAN port is dropped or lost
Egress: VLAN5 will always send out tagged traf f ic on these SLAN ports
Only tagged
frames allowed
on SLAN
U
U
U
T5
U
T5
T5
2-A 5-A 3-E
U
T20
T10
U
U
T20 T10
2-S
U
U
U
VID
20
VID
10
VID
5
T5
T5
2-A 5-A 3-E
U
U
2-S
U
U
U
VID
20
VID
10
VID
5
T5
U
T20
T10
Node 17
X3M-Station A
Node 18
X3M-Station B
Page 136 of 189 BG-M370-E-8
5.28 Full Feature Ready (=FFR)
Full Feature Ready is a checkbox that can be checked when creating a Virtual Router in a node. See
Figure below. If the checkbox is checked, it is called an FFR Virtual Router, if the checkbox stays
unchecked, it is called an non-FFR Virtual Router.

Some L3 features can only run on a FFR Virtual Router (5.17, 5.28), other L3 features can run on
any Virtual Router. Per node, it is possible to configure only one FFR Virtual Router. The table below
shows an overview of the available L3 features and where they can run.

Feature
Runs on FFR
Virtual Router
Runs on Non-FFR
Virtual Router
OMS v9.3 >= OMS v9.4
Static Routing Yes Yes Yes
OSPF Yes Yes Yes
VRRP Yes No Yes
DHCP Yes Yes Yes
IGMP Yes No No
PIM-SM Yes No No
RADIUS Yes --- No

FFR does not mean that all the features itself are already configured. It does mean that the Virtual
Router is ready to run them. The features themselves still have to be configured via the individual
feature wizards.
Once a Virtual Router has been created and configured, its FFR property cannot be modified
anymore. An existing FFR Virtual Router can only become a non-FFR Virtual Router by deleting the
Virtual Router and creating it again and vice versa.
See also 5.17 for the creation of a Virtual Router.

5.29 PoE in Detail
5.29.1 PoE Budgets
There are three types of PoE Budget:
PoE Budget Critical: the maximum power available for Critical Priority Ports;
PoE Budget High: the maximum power available for Critical + High Priority Ports;
PoE Budget Low: the maximum power available for all ports together: Critical + High + Low
Priority Ports;
BG-M370-E-8 Page 137 of 189
5.29.2 Calculation
Following definitions are used during the PoE budget calculation:
Pcrit: PoE Budget Critical;
Phigh: PoE Budget High;
Plow: PoE Budget Low;
Ppsu1: theoretical power that PSU1 can deliver (optionally filled out in the OMS GUI);
Ppsu2: theoretical power that PSU2 can deliver (optionally filled out in the OMS GUI);
Pext: External Maximum Power (filled out in OMS-FEM Ext. Max. Power);
Preal1 = minimum (Ppsu1, Pext with Pext greater than 0);
Preal2 = minimum (Ppsu2, Pext with Pext greater than 0);
Pint: internal consumed power from the node itself = 125W;
Pcrit = minimum(Preal1, Preal2) Pint
This formula only counts with two configured PSUs, with only one configured PSU, Pcrit = 0;
Phigh = maximum(Preal1, Preal2) Pint
This formula only counts with two configured PSUs, with only one configured PSU, Phigh = 0;
Plow = Preal1 + Preal2 Pint
5.29.3 PoE Example1: No External Limitation, low voltage PSUs
Purpose: how many 10W PoE cameras can be connected to a Node with the PoE specifications
below?
PSU1: VAC, low voltage range:110V Ppsu1 = 500W (Select in OMS GUI)
No external Power limitations Pext = 0W (already filled out in OMS-FEM)
Preal1 = minimum (Ppsu1, Pext (>0)) 500W;
Pint 125W;
Pcrit = minimum(Preal1, Preal2) Pint 500-125 = 375W 375 /10 = 37 cameras
Phigh = maximum(Preal1, Preal2) Pint 500-125 = 375W 375 /10 = 37 cameras
Plow = Preal1 + Preal2 Pint 500+500-125 = 875W 875 /10 = 87 cameras
RESULT: If the cameras must be connected to only Critical or High priority ports, 37 cameras
can be connected. If the cameras must be connected to only Low priority ports, 87 cameras
can be connected. Any other case connects between 37 and 87 cameras.
5.29.4 PoE Example2: External Limitation, low voltage PSUs
below?
PSU1 : VAC, low voltage range:110V Ppsu1 = 500W (Select in OMS GUI)
External Power limitation Pext = 300W (filled out in OMS-FEM)
Pint 125W;
RESULT: If the cameras must be connected to only Critical or High priority ports, 17 cameras
can be connected. If the cameras must be connected to only Low priority ports, 47 cameras
can be connected. Any other case connects between 17 and 47 cameras.
Page 138 of 189 BG-M370-E-8
5.29.5 PoE Example3: External Limitation, mix of low and high voltage PSUs
below?
PSU1 : VAC, low voltage range:110V Ppsu1 = 500W (Select in OMS GUI)
PSU2: VDC, high voltage range:48V Ppsu2 = 1000W (Select in OMS GUI)
External Power limitation Pext = 700W (filled out in OMS-FEM)
Pint 125W;
RESULT: If the cameras must be connected to only Critical priority ports, 37 cameras can be
connected. If the cameras must be connected to only High priority ports, 57 cameras can be
connected. If the cameras must be connected to only Low priority ports, 107 cameras can be
connected. Any other case connects between 37 and 107 cameras.
5.29.6 PoE FAQ
a. At Node Start-Up
Question1: in which order will connected PoE devices be powered up at start-up?
Answer1: According to the available power budget, the PoE ports and its connected devices
are powered according the power priority of the port. As long as there is power budget left, the
node keeps on powering up PoE ports. The node will first power up Critical then High and then
Low power priority ports. Within the same power priority group, ports are powered up
randomly.

In normal circumstances all configured and enabled (PoE Port: Admin Status = on) ports
should get power at start-up. It is possible for example that one of the two PSUs has been
removed for maintenance reasons. In that case, there might be more PoE configured in the
OMS-FEM than possibly can be delivered by one PSU in the live node. As a result, some PoE
ports might not get PoE power and this according the rules described above.

b. Node Up and Running
Question2: What happens if the external power source that feeds the PSU(s), fades away or
degrades?
Answer2: The PSU(s) will try to deliver the necessary PoE power as long as possible for all
the configured PoE ports (Critical, High and Low). After further degradation, at a specific time,
the PSU(s) cannot deliver anymore the necessary power and the node will reboot. The node
will not sequentially power down the low, high and critical power priority ports to keep for
example the criticals longer alive. If the node cannot power all the PoE ports, it will reboot and
power up all the PoE ports again.

If this degradation error situation repeats itself five times, the node will reboot five times
accordingly. After the fifth reboot:
The node disables its PoE module, which results in not delivering PoE anymore to the
connected PoE devices;
The node sets the field Oper Status (node-level) to Faulty in the OMS-FEM;
The node sets the field Operation Status (port-level) to OtherFault in the OMS-FEM;
A technician has to solve the PSU/external source problem first. Next Re-enable PoE
module via the OMS-FEM.

Question3: In which order do I connect my PoE devices to an up and running node which has
already PoE configured?
BG-M370-E-8 Page 139 of 189
Answer3: Connect your PoE devices first to the Critical then High and then Low power priority
ports. This is also the order in which the node powers up the connected PoE devices after a
reboot.

Question4: In a double PSU configuration, what happens if I pull out one PSU?
Answer4: The available PoE budget drops back to the PoE budget of one PSU. If the
remaining available PoE budget of the remaining PSU
is still enough to power all the configured PoE ports, all PoE ports will still be powered,
no disruptions occur.
is not enough to power all the configured PoE ports, some PoE ports will be disabled
according following order: First Low then High and then Critical power priority ports. Within
the same power priority group, ports are disabled or powered down randomly. Additional
ports will be powered down until the available PoE budget can power the remaining
enabled PoE ports. In normal circumstances, one PSU must be able to power up all the
Critical PoE ports.

Question5: In a single PSU configuration, what happens if I plug in an extra PSU?
Answer5: Nothing should really happen, everything keeps running normally. The available
PoE budget will increase which allows the network administrator to configure extra PoE ports,
and finally connect extra PoE devices to the extra configured PoE ports.

Question6: What happens if I connect a PoE device that requires more PoE power than the
maximum allowed power by the configured Power Class (Class 0, 1, 2, 3, 4) for that PoE port?
Answer6: E.g connect a power device to a PoE port that is configured with Power Class2
(Class 2 = 7 Watt). The connected device can consume a maximum of 7 Watt on that port. If it
wants to consume for example 10 Watt (greater than 7 Watt), then:
the PoE port will stop delivering power;
in OMS-FEM: counter power denied # increases with one;
in OMS-FEM: counter overload # increases with one;
in OMS-FEM: the field Current Status (port-level) is set to Fault; This fault conditions
disappears automatically after connecting a device that consumes power within the
configured power class range.
Question7: Why can I only configure Critical/High Priority ports when two PSUs are
configured?
Answer7: A Critical/High Priority port is a port that must stay up and running as long as
possible. This can only be achieved when there is PSU redundancy, which means two PSUs.
With one PSU, only Low Priority ports can be configured.

5.30 Media Redundancy Protocol (MRP)
5.30.1 General
The MRP is a protocol (IEC 62439-2) especially designed for industrial applications which need a
predictable fail-over time. This protocol can only be used in a ring-topology network and makes sure
that the ring network stays loop-free. MRP does in ring networks what spanning tree does in meshed
networks but with much faster convergence times.
5.30.2 MRP Operation (short description)
ring of MRP-compatible access switches connected to two N50/N70 series nodes;
ring consists of one selected MR Manager (MRM), and a number of MR Clients (MRC); Two
N50/N70 series nodes connected to this MRP access ring act as MRC; MRP ring protocol is
closed over the OTN ring via two N50 or N70 series nodes that have MRP activated.
MRP logically blocks one of its uplink ports, to prevent a layer2 loop;
when access ring is broken (cable break or device down) the MRM will detect it and open his
blocked uplink port;
convergence time depends on access switches, but is typically around 40ms;

Page 140 of 189 BG-M370-E-8
NOTE: Multiple Redundancy domains based on the VLAN tag are supported by the OTN ring.
This operation is only possible if the necessary MRP licenses (or vouchers) are purchased for the
N50/N70 series nodes that act as MRC. These license packs must be fetched from the OTNnet
(5.30.3), installed (see 5.30.4) and activated (see 5.30.5) on the intended N50/N70 series nodes.

5.30.3 Fetch the MRP license from the OTNnet
See 2.2.
5.30.4 Install the MRP license on the node
See 5.34 for an example how to install a license on the node. For activating the MRP license, see
next paragraph.
5.30.5 Activate the MRP license on the Node
1. Once the licenses are installed, navigate in the OMS-FEM in the node treeview to the node that
needs MRP, right-click the node and select View Properties.
2. In the MRP Information section, set MRP Protocol to Enabled and click the Apply button. From
now on, the MRP is activated on the node.

OTN-X3M-2500
N50xx
N50xx
N50xx
N50xx
Access switches
running MRP
MRP Access Ring
Enable MRP
Protocol via
OMS-FEM
MRP License!
MRP interrupting
the loop by
blocking the port
N50xx
N50xx
N50xx
N50xx
OTN-X3M-2500
Enable MRP
Protocol via
OMS-FEM
MRP License!
MRM
MRC
MRP Access Ring
MRC MRC
MRC MRC
MRP
Protocol
BG-M370-E-8 Page 141 of 189
5.31 Loop-Free / Loop-Aware Mode: No STP Worries in Loop-Free mode (no Layer2
loops in design)!
5.31.1 General
MSTi: Multiple Spanning Tree Instance.
In general, MSTP is a vital mechanism or protocol in a network that keeps the network loop-free (by
blocking specific ports) in order to avoid broadcast storms etc...
In fact, the OTN core network itself does not really need MSTP. Because of the double ring technology
within the OTN network, there will always be a redundant path.
Anyhow, MSTP must still be configured within the OTN network because of external applications that
could cause loops over the OTN network.
5.31.2 External Loops
unintended loops: accidental or to harm deliberately
via shortcut cables
via a third party Ethernet switch: this switch (=is an external switch beyond the control of the
network administrator) could become unintended root bridge of the running MSTP in the OTN
network. This switch could run RSTP or MSTP with conflicting parameters towards the MSTP
running in the OTN network;

loops by design:
external backup paths in case the OTN network is broken
redundant access networks e.g. ETS switches creating a subring between two OTN nodes

These external loops could influence the stability of your network if the network is not well protected
against them. The network could run into broadcast storms and undesired or unintended MSTP
topology changes that influence the stability of the network.
Therefore the OMS-FEM makes sure at configuration time that possible dangers listed above are by
default blocked resulting in a by default protected network. Depending on the configured VLANs,
SLANs, ELANs and its dependencies, the OMS-FEM will automatically configure the best optimized
MSTP configuration for the configured network.
Unintended Shortcut Cable
causing a loop
Unintended Ethernet Switch
causing a loop
OTN OTN
Unintended Loop Unintended Loop
OTN OTN
Intended Loop Intended Loop
LAN20
ETS Network
Page 142 of 189 BG-M370-E-8
Basically, the OMS-FEM can precheck at configuration time (before MSTP does loop detection at
runtime) if the configured network includes possible Layer2 loops (within a VLAN). These loops can
occur via the configured SLANs and/or ELANs.
When there are no loops by design, the OMS-FEM detects this during VLAN creation/modification
(see 5.9) and takes care of all the MSTP settings automatically. The administrator does not have to
worry about these settings anymore. The OMS-FEM will turn the network configuration into a fast and
efficient loop-free mode, taking care and protecting the network against unintended external loops.
When there are loops by design, the OMS-FEM detects this during VLAN creation/modification (see
5.9) and turns the network configuration automatically into loop-aware mode. The administrator has
to configure the necessary MSTis (MST instances) with the necessary parameters.
5.31.3 Loop-Free / Loop-Aware Mode
Loop-Free mode: If no possible Layer2 loops (within a VLAN) are detected by the OMS-FEM (see
figures below), the OMS-FEM will automatically configure the network into a much easier configurable
Loop-Free mode. The Loop-Free mode is always favoured against the Loop-Aware mode (see
further) and can be obtained initially by network design. Although no internal loops are detected by the
OMS-FEM, a default MSTP instance is still necessary to prevent accidental external loops. The default
MSTP instance will always run and cannot be disabled. In this mode, the OMS-FEM will automatically
configure the network (the default MSTP (=CIST) instance, port parameters, ) in such a way that the
possible listed dangers are blocked. In this mode, no other MSTi is needed beyond the default one.
However, the administrator could still configure the network manually into Loop-Aware mode (see
further) for later use.
Loop-Aware mode: The network is looped by design via ELANs, an external network or a second
OTN ring for redundancy reasons. In this mode, MSTP or RSTP is used to manage these loops or
backup paths. If one or more Layer2 loops (within a VLAN) are detected by the OMS-FEM (see figures
below), the default MSTi will not be able anymore to cover all the possible dangers. As a result, some
extra MSTis must be created. The amount of these instances depends on the amount of paths
between the different nodes in the network. Each path must be convered by an extra MSTi. After a
loop detect by the OMS-FEM, the OMS-FEM will force the network administrator into the MSTP wizard
to create a new MSTi. The administrator will not be able to load its configuration into the live
network until all candidate loop paths are covered by an individual MSTi. Furthermore, the
administrator will not be able to delete an MSTi on a VLAN which has a detected loop. Once the
network runs in Loop-Aware mode (because of predetected loops), the administrator cannot turn the
network back into Loop-Free mode.
NOTE: See also VLAN chapter 5.9 and MSTP chapter 5.11.
NOTE: A mix of both modes in the network is possible, e.g. some nodes can run in Loop-Free
mode, while the other nodes run in Loop-Aware mode.
5.31.4 Tuning Parameters
The OMS-FEM automatically configures some MSTP tuning parameters in an intelligent way to make
sure that both Loop-Free and Loop-Aware mode operate in the most efficient way. These parameters
are operational on different levels and can be configured and modified via the MSTP wizard. A list of
these parameters can be found below. A full explanation on these paramaters can be found in the
MSTP chapter 5.11):
Bridge Priority:
By default, each MSTi will elect its own Root Bridge automatically by the lowest Node Bridge ID (=
combination of Bridge Priority and Bridge MAC address). With the same Bridge Priority, the lowest
MAC address wins.

The root bridge selection can be influenced. Consider well which node you want to become the Root
Bridge for each MSTi at creation time. In this way, the root bridge can be configured on the more
central or important nodes.

Once you have decided which node must become Root Bridge, configure that node with the lowest
Bridge Priority. If you keep the default values for the Bridge Priority, your Root Bridge will become less
BG-M370-E-8 Page 143 of 189
predictable because the Root Bridge will be determined by the node with the lowest MAC Address.

When having multiple MSTis, try to distribute the Root Bridges in a well-considered way over the most
important or central nodes for better load sharing. This can be done by tuning the Bridge Priority
parameter per node per MSTi.

Link Cost:
If you have for example two redundant paths, the path with the lowest Link Cost will become the
favourite or primary path and the other the backup path. The default Link Cost per path in the OMS-
FEM is automatically calculated on the configured bandwidth (for SLANs)/link speed (for ELANs).
The higher the bandwidth or link speed, the lower the Link Cost. Finally, within MSTP, the primary
path will be the active path and the backup path will be blocked by MSTP to avoid loops.

It is always better to configure in OMS-FEM which path you want to be the primary and backup path
and not leave the election to the default values. If you a want a specific path to be the primary path,
overwrite its Link Cost with a lower value than the other Link Costs. If you want a specific path to be
the backup path, overwrite its Link Cost with a higher value than the other redundant paths.

Example: If you have two redundant paths, e.g an SLAN and an external link (ELAN), you probably
want the SLAN to be the primary path and the external link the backup path. To make the SLAN the
primary path, make sure to assign a lower Link Cost to the SLAN than to the external link.

Advise for other parameters:
Leave them as they are configured by the OMS-FEM automatically, unless you are an MSTP expert.
Level Parameter MSTi Dependent For which users?
Node Bridge Priority yes all
Loop-Aware mode no expert
Link Link Cost yes all
Port Priority yes expert
Link Type no expert
PortFast no expert
Root Guard no expert
BPDU Guard no expert
BPDU Transmit no expert
BPDU Receive no expert
Hello Time (sec) no expert

Node60
VID
10
Node70
VID
10
Node80
SLAN10
VID
10
Loop-Free Mode: 1 VLAN, 1 SLAN
Default MSTP
instance is
enough
Node60
VID
10
Node70
VID
10
Node80
SLAN10
SLAN20
VID
20
VID
20
VID
20
VID
10
Loop-Free Mode: 2 VLANs, 2 SLANs (completely separated)
Default MSTP
instance is
enough
Page 144 of 189 BG-M370-E-8

5.31.5 VLAN-MSTi Mapping Table / Network Interruptions
Using multiple MSTis introduces a mapping table that maps the VLANs to MSTis. This table has to be
synchronised between all OTN nodes (that are in 'Loop-Aware mode'). Changing this table, i.e.
creating a new VLAN or MSTi, will restart MSTP in all its nodes, hence introducing short network
interruptions.
This is native behavior of MSTP (IEEE 802.1s).
By using the 'Loop-Free' mode, no mapping table is created or altered (all VLANs are mapped to the
default instance), and no network interruption will take place when changing the network configuration.
The OTN Management System manages the alternate paths by configuring a series of BPDU port
settings. DO NOT ALTER THEM unless you are an MSTP expert user and are aware of the impact.

Node60 Node70 Node80
SLAN10
ELAN20
Loop-Aware Mode: 1 VLAN, 1 SLAN, 1 (closed) ELAN
At least one
extra MST
instance must
be configured
LAN20
VID
10
VID
10
VID
10
SLAN10
ELAN20
VID
10
VID
10
VID
10
LAN20
ELAN20
ELAN20
Predetected Loop
by OMS-FEM
This loop needs
an MST instance
SLAN10
ELAN20
VID
10
VID
10
VID
10
LAN20
ELAN20
Primary path:
higher Bandwidth or
lower Link Cost
Backup path:
Lower Bandwidth or
Higher Link Cost
blocked port
by MSTP to block
backup path
Root Bridge
BG-M370-E-8 Page 145 of 189
5.32 Layer3 View
5.32.1 General
The Virtual Routers on a node are already visible in the Node View (right-click Node View) and
then selecting the Virtual Routers icon in Select a View, see 5.4.5d.
On top of this view, the OMS-FEM offers an additional Layer3 View. This view shows the Layer3
interconnections of all the virtual routers within the network, also showing the IP addresses, connected
VLANs, SLANs and Loopback Interfaces.
Within this view, customizing the layout is possible but cannot be saved. Closing the Layer3 View tab
(=Layer3 [V]VirtualRouter/VirtualRouter tab) means loosing a customized layout.
5.32.2 Example Network
In the figure below (Network View tab), you can find a example network of which a Layer3 View will
be shown further on. This network has 5 nodes and each node has a Virtual Router configured.

Open the Layer3 View via Virtual Routers tab right-click PROTOCOL://VirtualRouter/ Layer3
View.

Right-click
Page 146 of 189 BG-M370-E-8
The figure below is shown. It is the Layer3 View showing the Layer3 interconnections of all the virtual
routers within the network, IP addresses, connected VLANs, SLANs and Loopback Interfaces.

The L3 View Navigation Toolbar has following buttons and functionalities:
Button Description
Follow Me

Click this button to activate the follow me window. This window shows a little
inner-window that indicates where your focus or location is (e.g. after zooming in
or out) within the entire network or Layer 3 View. This window also stays active
when using the other navigation buttons. This follow me window only disappears
after clicking this button again.
Fit to Graph

Click this button to set back the Layer 3 view to the default zoom or view. It will fit
the entire Layer 3 view within the entire Layer 3 view tab.
Select Mode

After clicking this button, it is possible to click a network element (virtual router,
VLAN, SLAN) to select it. Selecting multiple elements at once is possible via
CTRL+click. After having it/them selected, it is possible to drag the selected
network elements element into another location in your view to customize your
layout. The unselected network elements stay in place while dragging the others.
In this mode, it is is also possible to right-click a network element icon and view
the possible actions on this network element.
Information
Mode

In this mode, a grey information box will always be shown in the top-lefthand
corner on top of the Layer3 View. Clicking a network element (virtual router,
VLAN, SLAN, link) will show all the necessary information of this element in this
information box. In this mode, it is also possible to move the entire network
drawing in your layout by clicking a network element and drag/drop it.
Move Mode

In this mode, it is possible to move the entire network drawing in your layout by
clicking a network element and drag/drop it.
Zoom Mode

After clicking this button, zoom in via selecting the area of interest. Selecting this
area occurs via clicking and dragging, a light-blue selections area appears. Note:
Zooming in/out is also always possible via the mouse-scroll-wheel, irrespective of
the selected toolbar button; set back to the default zoom or default view via the Fit
to graph button.
Change Layout

ATTENTION: Clicking this button will change your layout immediately without any
further user confirmation. You will loose your previous layout. It sets another best
fit layout for the entire view.

Virtual Router
VLAN or SLAN
L3 View
Navigation Toolbar
BG-M370-E-8 Page 147 of 189
After zooming in (see Zoom Mode in the table above), your view could look as follows:

Hovering (=move over it with your mousepointer) the network element icons shows a temporary info
box of that network element, see some examples below:

Node identification
of the virtual router
Network IP
Address
VLAN identification
Temporary Info Box
after hovering
Virtual Router
Hovered Virtual
Router
Page 148 of 189 BG-M370-E-8

The figure below shows an example of the Layer3 View in Information Mode:

Temporary Info Box
after hovering
VLAN
Hovered VLAN
Temporary Info Box
after hovering
Link
Hovered Link
Information Mode:
Fixed Info Box showing info
of clicked network element
BG-M370-E-8 Page 149 of 189
5.33 Wizard Load Page/Load Into Live Network
5.33.1 General
The Load page is the final page of a feature wizard (e.g. LAG, VLAN, IGMP, .) and is reached after
clicking the Finish button in that wizard. This page allows to configure your features off-line into a
database without really loading them directly into the live network. Later on, it is possible to load all the
configurations at once into the live network which is much more time-efficient than loading all the
configurations individually.
An example of the Load page is found below, other Load pages from other feature wizards are similar
to this one:

Load or not Load (yet)? Thats the question.
Some definitions:
Load: transmit or load the feature configurations from the OMS-FEM database into the live
network. After a successful Load, the feature creations/configurations/modifications are up and
running in the live network.
Load Scenario: a list of actions that the OMS-FEM must perform to load the latest
creations/configurations/modifications of the specific feature into the live network.
Following buttons can be clicked in this Load page:
Close button (see 5.33.2)
Get Load Scenarios button (see 5.33.3)
Load button (see 5.33.4)

5.33.2 Close Button
This button closes the wizard. It does not matter if the configuration is loaded or not. The wizard
feature configuration stays stored in the database and can still be loaded later on via:
Configuration Load Network
Right-clicking a node and select Load
Right-clicking a feature or protocol and select Modify, this modify wizard finally turns into the Load
page
5.33.3 Get Load Scenarios Button
Clicking this button shows all the load scenarios and highlights the Load button. The load scenarios
are only shown, not loaded. The Load button is highlighted if further loading is desired.
Clicking this Get Load Scenarios button is:
Interesting just to verify what might change into the live network, it is still possible to Close the
wizard without really loading. The loading can be be postponed for later.
Necessary if you really want to load now.

Page 150 of 189 BG-M370-E-8

5.33.4 Load Button
The Load button is only activated after clicking the Get Load Scenarios button. Clicking the Load
button loads the listed and checked Load Scenarios into the live network. A progress bar indicates the
load progress. After a Load action, a green message bar with Load Success is displayed when the
action was successful. If not, a red message bar with Load Error is displayed. See the windows
below: before/during/after Load.

Load Scenarios
Before Click
After Click
Load Scenarios
Before Load
Only checked nodes
are loaded
Load progress bar
During Load
BG-M370-E-8 Page 151 of 189

5.34 Going Online Licenses Vouchers
5.34.1 Normal Situation
Once you have generated your license pack (*.dat file) online via the OTNnet
(https://extranet.otnsystems.com), following actions must be done to activate your purchased
vouchers (features) in your live network:
1. It might be interesting to save this *.dat file on a USB stick before going to your OMS PC;
2. Go to your OMS PC. In the OMS-FEM, verify your purchased and consumed licenses via Help
License Information.

3. Initially you will not have any licenses (or *.dat file). As a result, the window below pops up, with
only the OMS installation Serial Key displayed. Vouchers (=Purchased vouchers) and Used
Vouchers (=Consumed vouchers) are still empty. Click Ok to close the window.

4. Install the purchased licenses via copying the '*.dat' file onto your OMS PC:
For OMS v9.0 and v9.1: <oms path>\bin_fem\License.
For OMS versions higher than v9.1: OMS Console Help About License Path.
ATTENTION: make sure that there is only one *.dat file in this directory, other *.dat files must
be removed from this directory!

After Load
Load result
No license pack f ile
(*.dat) installed yet
Page 152 of 189 BG-M370-E-8

5. Stop and restart (via Stop Server(s)/Start Server(s) buttons) the servers via the OMS Console to
read out the purchased licenses and set them ready to use in the OMS-FEM;
6. Open the OMS GUI and the OMS-FEM;
7. In the OMS-FEM, verify your purchased and consumed licenses via Help License
Information. For example: the *.dat file included 2 PoE24 (=for two nodes) and 1 PoE48 (=for
one node) licenses. Click OK to close the window.

8. From now on, it is possible to activate PoE on two 24 port nodes (e.g. N5024C, N5024CF,
N5224C) and one 48 port node (e.g. N5048C). Activating PoE can be done on port level in the
PoE Settings section of the port properties, via setting the Admin Status = On.

9. After activating PoE, in the OMS-FEM, verify your purchased and consumed licenses via OMS-
FEM Help License Information. From the moment PoE is activated at least on one port
within any of the available nodes (does not matter which node), the PoE license for that node is
counted as Used Voucher or consumed. The Used Vouchers in the figure below are counted
on node level, not on port level. If PoE was activated first on a node, and deactivated later on on
all the ports of that same node, from then on and if desired, this PoE license can be used on
another node instead. Click OK to close the window

License pack f ile
(*.dat) installed
No f eatures activated
yet in OMS-FEM
BG-M370-E-8 Page 153 of 189

10. Verify whether your PoE features are operational.

5.34.2 Error Situations
a. Online environment: Activate features on more nodes than licenses available
Notification in OMS-FEM: yes;
Alarm in OMS: no;
If you try to activate (=set Admin Status on) in the OMS-FEM for example PoE on more nodes
(e.g. 3 nodes) than you have purchased licenses (e.g. for 2 nodes), the error message in the
window below pops up. The activation on the extra node will fail. No extra alarm to the OMS GUI is
generated.

b. Offline environment: Activate features on more nodes than licenses available
Alarm in OMS: yes (when OMS-FEM tries to go online);
If you activate (=set Admin Status on) in the OMS-FEM for example PoE on more nodes (e.g.
2 nodes) than you have purchased licenses (e.g. for 1 node), the error message in the window
below pops up. As a result, the OMS-FEM cannot go online (alarm in OMS Gui, see screenshot
below). This problem can be solved by deactiving (=set Admin Status off) features, e.g. on port
level for PoE until the feature has been deactivated on the entire node. Repeat this step on
enough nodes, until the problem is solved. Next, make a disconnect subnetwork followed by a
connect subnetwork in the OMS GUI.
Activate PoE24
on Node 24
(=24 ports Node)
Activate PoE48
on Node 17
(=48 ports Node)
Page 154 of 189 BG-M370-E-8

When the OMS-FEM tries to go online, the alarm below is generated in the OMS Gui:

c. Inconsistent *.dat files, before and after
Alarm in OMS: yes (when the OMS-FEM tries to go online);
If a specific amount of features, for example PoE, is activated in your network via *.dat file1, and
this file is removed later on and replaced by another *.dat file2 with less licenses than *.dat
file1 then the alarm in the figure below is generated towards the OMS GUI. It means that more
vouchers or features are activated in the live network than allowed in *.dat file2. As a result, the
OMS-FEM cannot go online.

*.dat f ile inconsistent
with f eatures activated in
the network
the network
BG-M370-E-8 Page 155 of 189
d. Inconsistent Serial Keys
Alarm in OMS: yes (when the OMS-FEM tries to go online);
If a *.dat file is used that is linked to another Serial Key (e.g. N1-9876-5432-1098-7654-3210-
9876) than the Serial Key used during installation (e.g. N1-1234-5678-9012-3456-7890-1234),
then the error message below pops up in the OMS-FEM when activating/deactivating a feature,
e.g PoE.

As a result, the OMS-FEM cannot go online. When the OMS-FEM tries to go online, the alarm
below is generated in the OMS Gui:

N1-1234-5678-9012-3456-7890-1234 N1-9876-5432-1098-7654-3210-9876.
the network
Page 156 of 189 BG-M370-E-8
6. EXTERNAL DEVICES / OTN DEVICES / MIB-2
6.1 Monitoring and Alarming on a Device
General information on External Devices and OTN Devices can be found in 5.5. After the External /
OTN device has been added (see 5.5) and assuming that this device has MIB-2 onboard, the OMS-
FEM can connect to this device and read out the entire MIB-2 structure. Next, the OMS-FEM can
configure alarm rules on any property in that MIB-2 structure (see IETF RFC1213).
A MIB (=Management Information Base) is a standardized database structure holding a set of data or
network objects. MIB-1 refers to the intial MIB structure whereas MIB-2 refers to the latest structure.
Parameters and properties in this read-only and tree-structured MIB-2 are accessed through its unique
OID (=Object Identifier). If the alarm rule is triggered, a customized alarm will be raised in the OMS
GUI.
6.2 Configure Alarm Rules via MIB-2
Follow the steps below to configure alarm rules:
1. Once the device has been added in the OMS-FEM, its MIB can be accessed via a MIB Browser.
Right-click the device in the Equipment window, first connect to the device via selecting Connect.
Next, select MIB Browser to open the MIB-2 structure on the device.

2. The MIB browser of the selected device opens and shows the window below in which four
different sections can be noticed.

1) MIB-2 Tree: Use this tree to navigate to the desired parameter, on which an Alarm Rule
must be configured. Clicking a parameter pre-fills out the Alarm Rule Configuration window
and measures the live data from the device. The measured data is shown in the Measured
Data section. Some parameters are table parameters e.g. ifTable. Clicking on such a
parameter will fill out an entire table with live data in the Measured Data section.
4) Alarm Rule List
2) Measured Data
Output
3) Alarm Rule
Configuration
1) MIB-2 Tree
BG-M370-E-8 Page 157 of 189
2) Measured Data: Based on the clicked parameter in the MIB-2 tree, this section is filled out
with live measured data from the device. Clicking a cell in this section pre-fills out the Alarm
Rule Configuration window further than it was already done after clicking in the MIB-2 tree.
3) Alarm Rule Configuration: This section is used to configure an alarm rule on a specific
OID. The fields can be pre-filled out by clicking a parameter in the MIB-2 Tree or by clicking a
cell in the Measured Data section. The fields can also be filled out manually. Find below a
description of the fields in this section. The fields below will be used in the Alarm Log View
and Alarm Details window in the OMS GUI when raising an alarm.
NOTE: It is possible to configure multiple alarm rules on the the same OID, e.g. rule1: raise
a minor alarm when temperature is between 50 and 60 degrees; rule2: raise a major
alarm when temperature is above 60 degrees etc.
OID: The object identifier that identifies the parameter on which an alarm rule must be
configured; The OID is the one and only link of the parameter to the defined parameter in
the MIB-2 tree, e.g. modifying the Property Name name below will still refer to the initial
intended parameter as long as the OID remains the same.
Property Name: The name of the MIB-2 property on which an alarm rule must be
configured. This name can be modified, it will only modify the property name in the alarm
rule, not in the MIB-2 tree.
Alarm Name: Fill out an appropriate value to identify the alarm, e.g. Door is open or ETS
interface is down, or.
Condition: Fill out the normal condition of the parameter in which no alarm must be raised.
The measured value from the live network will be compared to the configured value in
the alarm rule. If this condition is violated, not met or false, an alarm will be raised in the
OMS GUI. Depending on the Configured value type, the condition list is =,,<,>,<=,>=
for number and =, , starts with, starts not with, ends with, ends not with, contains, not
contains for text parameters. See also examples below.
Configured value: fill out the value that you consider as a normal situation for this
parameter. This value will be compared against in the condition. For example, if you want
an alarm when the temperature exceeds 50 degrees, your configured value would be 50
and your condition would be <.
It should look like:
measured value < configured value
ex1. 27 degrees: measured value (=27) < configured value (=50) true no alarm
ex2. 57 degrees: measured value (=57) < configured value (=50) false alarm
Configured value type: fill out the data type of the configured value: number or text. E.g.
with number, mathematical comparisons (e.g. <, >, ) are possible.
Severity: Fill out the severity of the alarm. Each severity results in a dedicated color, e.g.
major results in a red color. Possible values: none, indeterminate, warning, minor, major,
critical.
Add button: adds or creates a new configured alarm rule.
Delete button: deletes a selected alarm from the Alarm Rule List.
Update button: an alarm rule selected from the Alarm Rule List can be modified just by
modifying its fields in the Alarm Rule Configuration and clicking the Update button.
4) Alarm Rule List: lists all the configured alarm rules so far. Sorting and filtering can be done
via clicking the header cells of this list.
3. From the moment the alarm rule is configured and listed in the Alarm Rule List, and the device is
still connected, the OMS-FEM starts to poll the device to read out the MIB. It will first be checked
if the measured and configured value from the parameter (ref. OID in the alarm rule) is Valid or
Invalid (see figure below). Invalid means that there might be problem with the OID, syntax, data
typeand that you have to verify this and adapt or update when possible. If Invalid occurs in the
Alarm Rule List, no alarms on this rule will be raised in the OMS GUI before this issue has been
solved.
Page 158 of 189 BG-M370-E-8

6.3 Example MIB-2 Alarm: Alarm Rule in OMS-FEM Alarm in OMS GUI
6.3.1 How the Alarm Rule was created
This example has alarm rules configured to monitor port 1, 2 and 3 of device ETS28p. The alarm rules
were configured via navigating to the ifTable (1.3.6.1.2.1.2.2.) (=InterfacesTable) parameter from the
ETS28p MIB-2 tree. Clicking this parameter loaded the interfaces table into the Measured Data
section on the right-hand side.
Clicking the ifOperStatus cell of the specific port (e.g. ifIndex 3 refers to port 3, ifOperStatus_3
refers to the linkstatus of port3) pre-filled out the Alarm Rule Configuration section. Monitoring the
port status can be done based on the IfOperStatus values below:
IfOperStatus = 1 Link = Up on this port;
IfOperStatus = 2 Link = Down on this port;
Based on these values the alarm rule condition could be defined as follows:
Measured value = Configured value with the Configured value = 1 (=Link Up)

6.3.2 The Monitoring and Alarm Generation in OMS GUI
Step1: everything fine, no alarms, link is still up on port 3 of ETS28p, ifOperStatus_3 is still 1 see
figure below.

4) Alarm Rule List
Valid /
Invalid
Valid /
Invalid
OMS-FEM
OMS GUI
1 = link up
2 = link down
Cable plugged in ETS interface 3 link up measured value = 1 OK
Condition = true no alarm raised in OMS GUI
Step1:
- Alarm rule configured
- Everything Fine: Link Up
- No Alarms
BG-M370-E-8 Page 159 of 189

Step2: Cable in port 3 of ETS28p has been pulled out, ifOperStatus_3 changes from 1 into 2, alarm
rule condition has been violated and an alarm is raised in the OMS GUI, See figure below.

6.4 Disconnecting a Device / Clearing Alarms
Disconnecting the device will clear all the device alarms in the OMS GUI. A device can be
disconnected via right-clicking the device in the Equipment window and select disconnect.
6.5 Configuring a Device
Once the external/OTN device has been added in the OMS-FEM, it can be configured via the devices
web browser or via the Windows Telnet client. Its web browser can be started via right-clicking the
device in the Equipment window and selecting Launch Web Browser. A telnet session to this device
can be started via right-clicking the device and selecting Launch Telnet. Make sure the Telnet client
has been activated, see 5.5.4.

OMS-FEM
1 = link up
2 = link down
Step2:
- Broken link
- ERROR: Link Down
- Alarm Raised in OMS GUI
OMS GUI
Cable pulled out of ETS interface 3 link down measured value = 2 NOK
Condition = false alarm raised in OMS GUI
Alarm Details
Page 160 of 189 BG-M370-E-8
7. SERVER-CLIENT ENVIRONMENT, REMOTE OMS-FEM
Using a remote OMS-FEM Client is possible when it is connected via a LAN to the OMS Server. As a
result the OMS Server PC needs 3 network interface cards (NIC) as indicated in the figure below.

Further more, start the OMS Console on the remote OMS-FEM Client (if not already started) via Start
Programs OTN OMS OMS Console. To make remote operation possible, perform
following actions in the remote OMS Console:
open Edit Options OMS-FEM GUI
Set the field Connect to remote OMS-FEM server = True
Replace localhost with the IP address of the OMS-FEM server, e.g. 192.168.10.10
Click on the Database Selector and select the OMS-FEM SQL database, most likely situated
on the OMS-FEM server.
Click Apply and OK,
See figure below:

OTN-X3M-2500
N50xx
N50xx
N415
OMS Server
OMS-FEM Server
NIC2
NIC1
N50xx
OMS Port
MGT Port
LAN
NIC3
Remote OMS-FEM Client
192.168.10.10
Local
Remote
Database
Selector
BG-M370-E-8 Page 161 of 189
8. SCRIPTING
8.1 General
ATTENTION: It is strongly advised that scripting is only used by advanced and trained OTN users.
Make sure to start the OMS server first. Next, the OMS Scripting tool can be started via clicking
Start Programs OTN OMS OMS Scripting or via the OMS Console Tools OMS
Scripting Console. The window below pops up:

Fill out the command from OmseScript import * and press enter.

All configuration actions that can be performed on the OMS database through the OMS-FEM, can also
be performed by executing script commands. After filling out from OmseScript import * and
authenticating via Authenticate("oms") it is possible to enter scripting commands. A list with all
the possible OMS-FEM Scripting commands is displayed in 8.6. All the commands are
CaseSenSitive.
Some commands will start scripting an ethernet feature/protocol wizard. These commands must be
followed by another set of commands. In the full command list in 8.6, the command CreateACL
is followed by the commands SetPortACLEnabled, AddMACAddress, RemoveMACAddress,
Finish. This means that if you use CreateACL, you can also use SetPortACLEnabled,
AddMACAddress, RemoveMACAddress, in the same order as indicated in the full command list. The
wizard command set must always end with the Finish command.
8.2 Components Identifiers or URLs
If a script command operates on a single OMS component, its first parameter identifies an OMS
component as a Uniform Resource Locator (URL).
A URL is the unique hierarchical address of an OMS-FEM component. In its most general form it is a
concatenation of keywords separated by slashes, and followed by the components name or number.
Examples of URLs, needed when writing scripting commands, can be found in the treeview (see figure
below) in the OMS-FEM. For example, the URL of a node has following syntax:
NODE://<subnetwork name>-<node name> e.g: NODE://X3M-2500-Node 15.

Node URL example
(no slash at the end)
Page 162 of 189 BG-M370-E-8
8.3 Command Examples
CreateNetwork("//My Net")
CreateSubNetwork("//My Net/My SubNet", "OTN_2500_X3M","30","Double Ring")
SetProperty("//My Net/My SubNet","Ring_CentralNodeAddress","30")
CreateNode("//My Net/My SubNet/10", "N22")
CreateNode("//My Net/My SubNet/20, "N22")
CreateNode("//My Net/My SubNet/110", "N5048C", "Brussels")
CreateNode("//My Net/My SubNet/120", "N5024C", "Antwerp")
CreateNode("//My Net/My SubNet/130", "N5024CF", "Bruges")
CreateNode("//My Net/My SubNet/140", "N5224C", "Gent")
CreateLink("//My Net/My SubNet/{10,20}")

8.4 Writing a Scripting File
Proceed as follows to write a script:
1. Open Notepad (or another text editor).
2. A script file has an OMS part and an OMS-FEM part. The OMS part must always start with
from OScript import * and the OMS-FEM part must always start with from OmseScript import *.
In both the OMS and OMS-FEM part, always authenticate first via Authenticate. Find below the
start of the two parts that have to be entered in your text-editor.

############################
# OMS part
############################
from OScript import * # required to import OMS scripting extension to python
Authenticate("oms") # required to authenticate before scripting can be done
############################

############################
# OMS-FEM part
############################
from OmseScript import * # required to import OMS FEM scripting extension to python
Authenticate("oms") # required to authenticate before scripting can be done
############################

3. See china_oms.py in the <oms path>/script directory for an entire scripting file example.
4. Write your entire scripting file and save it as a *.py file in the <oms path>/script directory.

8.5 Executing a Scripting File
1. Open a command prompt;
2. Change your directory path to the <oms path>/script directory;
3. If your scripting file is china_oms.py, execute your scripting file via entering the command
python china_oms.py. See in the screenshot below for an example:

BG-M370-E-8 Page 163 of 189
8.6 Full Command List
A full command list (command+description) can be displayed in the scripting tool by using the scripting
command help(OmseScript). This will result in the screen below. Pressing the spacebar will
navigate through all the listed command screens.

Right-clicking the window title-bar and selecting properties will pop-up the screen below. This window
and its tabs allow the user to finetune the scripting DOS-box for an optimized scripting command
listing.

Page 164 of 189 BG-M370-E-8
9. LAYOUTING THE OMS-FEM
The OMS-FEM has a very advanced layouting mechanism. The displayed network information in the
OMS-FEM can be managed and layouted according to a docking layout system. It supports floating
windows, tabbed documents etc
Once a window (with all tabs or a single tab) is floating, it can be dropped almost anywhere to optimize
your layout. A floating window can stay floating or it can be dropped in one of the defined dropping
zones with the help of the layout navigator.
It can be chosen to drag & drop a floating window into one of the defined dropping zones:
Master zones (see 9.1.1)
Sub zone, which is a part of a Global Zone (see 9.1.2)
The dropped window will then automatically fit in the available layout.
Generally, following steps are needed to change the layout:
1. Teach yourself the different dropping zones, see 9.1;
2. Choose a Window/Tab to layout and let it float, see 9.2;
3. Place floating Window/Tab via Layout Navigator Tool, see 9.3:
Drag & Drop into a locked position via dedicated dropping zones
Dock as tabbed document
4. Change Order of Tabs within a window if necessary, see 9.4

9.1 Dropping Zones
Floating windows can be dropped into dropping zones via the layout navigator tool.
The OMS-FEM has:
Master Dropping Zones, see 9.1.1
Global/Sub Dropping Zones, see 9.1.2

9.1.1 Master Dropping Zones
There are four Master Dropping Zones in the OMS-FEM: a top, bottom, left and right Master Zone.

9.1.2 Global/Sub Dropping Zones
Each window already present in the OMS-FEM layout, represents a Global dropping zone. Each
Global dropping zone can be devided in a top, bottom, left, right and center/tabbed Sub dropping
zone.

Top Master Zone
Bottom Master Zone
Left
Master
Zone
Right
Master
Zone
BG-M370-E-8 Page 165 of 189

9.2 Choose a Window/Tab and let it Float
You can let a window (with one or more tabs) float via clicking the Window title bar and dragging it
out of its locked position and just drop it (not dropping it into one of the dropping zones).
You can let the active single tab float via right-clicking the Window title bar/tab and click Float or
click and drag the single tab out of its locked position and just drop it (not dropping it into one of the
dropping zones).

After having clicked Float in the pop-up menu or dragged & dropped the window/tab, your figure
could look as follows:

The Floating window can be placed back into its previous position by double-clicking the window title
bar.
Global
Zone 1
Global
Zone 2
Global
Zone 3
Global
Zone 4
Global
Zone 5
Global
Zone 6
Sub
Zone
Left
Sub
Zone
Right
Sub Zone
Top
Sub Zone
Bottom
Sub
Zone
Center/
Tabbed
Right-click to show
tab options
Floating window
Page 166 of 189 BG-M370-E-8
9.3 Place Floating Window/Tab via Layout Navigator Tool
The layout navigator tool is necessary to finally drop the floating window into one of the described
dropping zones (9.1.1 and 9.1.2). To drop it will fit it within the layout already present.
9.3.1 Place Window/Tab in Master Dropping Zones
1. Click or Drag & Hold the Floating window to show the Master Zone selectors;

2. Drag the floating window including the mouse pointer over one of the Master Zone selectors to
highlight that Master dropping zone;

3. If this dropping zone is fine for you, drop the floating window. The window will automatically fit into
the layout. Or try another dropping zone (by repeating previous steps) if this layout does not suite
your needs.

Master Zone
selectors
Click here to show
master zone selectors
Active Master Zone Selector Highlighted Master Zone
BG-M370-E-8 Page 167 of 189

9.3.2 Place Window/Tab in Global/Sub Dropping Zones
If the floating window is dragged over a Global dropping zone, the layout navigator tool pops up in
the center of that Global dropping zone (see 9.1.2).
The Sub dropping zone and its selector highlight blue when the floating window including the mouse
pointer is dragged over it.

Find below an explored example with all the dropping possibilities concerning Global/Sub dropping
zones:
Window in layout after dropping
layout
navigator
Sub dropping
zone
selectors
global dropping zone
Page 168 of 189 BG-M370-E-8
Drag floating window over
this button to select
Left Sub dropping zone
Before
drop
After
drop
Select
Sub dropping zone
via layout
navigator
Right Sub dropping zone
Top Sub dropping zone
BottomSub dropping zone
Center/Tabbed Sub dropping zone
Result s in
new tab
BG-M370-E-8 Page 169 of 189
9.4 Change Order of Tabs within a Window
Click, drag & hold the tab horizontally between the dotted lines, for example the SLANs tab. As a
result, you can change the order of the tabs.

Drag horizontally
Click here
Drop
Page 170 of 189 BG-M370-E-8
10. MONITORING
10.1 General
Within the OMS-FEM, monitoring means supervising the status of the live network whereas viewing
means whatching the database configuration. Viewing could be done offline, while monitoring can only
be done online in the live network.
Following monitoring features are available:
MSTP Monitoring, see 10.2;
Port Counters Monitoring, see 10.3;
VRRP Monitoring, see 10.4;
IGMP Snooping Monitoring, see 10.5;
IGMP Monitoring, see 10.6;
PIM-SM Monitoring, see 10.7;
OSPF Monitoring, see 10.8;
10.2 MSTP Monitoring
MSTP Monitoring allows to monitor the status and roles of the ports within an MSTP domain in the live
network.
Monitoring an MSTP instance can be done via the L2 features tab right-click MSTP instance
Monitor. A new monitoring [M] tab (e.g. [M]MSTP/STP1) opens in the middle body view.
The monitoring tab offers both a graphical and a table view, see figures below.

Refreshing the monitoring view must be done via clicking the refresh buttons:
BG-M370-E-8 Page 171 of 189

After zooming in via the mouse-scroll button or the OMS-FEM zoom button, the graphical view shows
more detailsThe meaning of the colors and icons can be found in the legend.
Example: bridge role: MSTP uses the bridge ID to determine the root bridge, the bridge with the
lowest bridge ID becomes the root bridge. The bridge ID is composed of the bridge priority and the
bridge Role MAC address. The bridge with the lowest priority value (=highest priority) becomes the
lowest bridge ID. If all the bridge IDs have the same priority, the bridge with the lowest MAC address
will then become the root bridge or the Bridge rolein this example, node 70 becomes the bridge
role.

Port State Is port included in
active topology?
Is port learning
MAC addresses?
Disabled/ Blocking No No
Listening No No
Learning No Yes
Forwarding Yes Yes

Refresh
buttons
zoom
button
same priority, lowest
MAC address =
Bridge Role
Page 172 of 189 BG-M370-E-8
Icon Description
Node
Bridge Role Indicates which node is the Bridge Role or Root Bridge of the monitored MST
instance. The Root Bridge can differ from instance to instance.
Port State Indicates how the MSTP process has progressed
Disabled
/Blocking
This port would cause a switching loop. As a result, MSTP sets this port into
Disabled state to prevent the loop. In this state, the port discards the frames and
does not learn the MAC addresses. Also if the link is down (e.g. no cable connected)
are the port has been disabled by the administrator, the port will turn also into the
Disabled state. A port is blocked by MSTP if the Port State = disabled and the
Port Role is alternate or backup.
Listening A port enters this state after the Blocking state. The port enters this state when
spanning tree decides that the port must participate in frame forwarding.
Icon Description
Learning A port enters this state after the Listening state. In this state, the port gets ready to
participate in frame forwarding and learns MAC addresses from the received
packets.
Forwarding In this state, the port receives and forwards frames or forwards frames switched
from another port. This transition from Blocking to Forwarding state could take some
seconds, also depending on the amount of nodes. A port could be set in PortFast
mode (see 5.11.3) to transition directly from Blocking into Forwarding state at
LinkUp and to avoid having to wait a few seconds.
Port Role After the MSTP instance is up and running, the Port Role indicates how the ports
deal with the user data.
Disabled If the link is down (e.g. no cable connected), the port role will turn into the Disabled
state. The administrator could also configure the port as Disabled.
Root Which Bridge port will offer the Bridge the best path towards the Root Bridge? This
port will be the root port of that Bridge. Every bridge will have one root port.
(root alternate)
Alternate A blocked port providing an alternate path to the Root Bridge of the spanning tree.
It is an alternate root port. A port is blocked by MSTP if the Port State = disabled
and the Port Role is alternate or backup.
(root alternate)
Designated One forwarding port, with the lowest path cost, is elected for every segment
(SLAN/ELAN/Access network). This port will be the designated port for that
segment.
(designated backup)
Backup A blocked port that acts as a backup for the path provided by a Designated Port. A
port is blocked by MSTP if the Port State = disabled and the Port Role is
alternate or backup.
(designated backup)

10.3 Port Counters Monitoring
1. In the OMS-FEM, go via Configuration Traffic Control Control Port Counters. The
Port Counters section opens in the Port Counters tab, see figure below. The ports can be
selected for monitoring via the Node-Port Selector button. After selecting the ports (see figures
further on), the counter monitoring must be refreshed manually via the Counter Refresh button

BG-M370-E-8 Page 173 of 189

2. In the figure below, click the Node-Port Selector button to display the Node-Port treeview.
Furthermore, an empty table with the possible counters is displayed after clicking this button.

3. In the figure below, expand the Node-Port treeview and select one (LAG)port/more
(LAG)ports/entire node for monitoring. Selecting some ports immediately adds these ports in the
Counter overview. The last selected port is always added at the end (=last row) of the Counter
Overview. Selecting a LAG adds all the ports of the LAG in the Counter overview. Each counter
for each port always displays two values, refreshed by the Counter Refresh button:

Upper value: this is always the actual counter value (or most recent counter value) for the
selected port. Initial value, when nothing measured yet = actual
Bottom value: this is always the previous counter value selected port. Initial value, when
nothing measured yet = previous
Counter Refresh button: Clicking this button starts the measuring of the counters. Each click
on this button moves the old upper value towards the bottom value (upper value bottom
value) and refreshes the upper value for each counter on each port.

Node-Port
Selector
button
Indicates counter
configuration/
selection area
Counter
Refresh
button
Indicates counter
monitoring area
Node-Port
treeview
Counter
overview
Expand/
Collapse
treeview
Page 174 of 189 BG-M370-E-8

4. The counter refresh process is visualised in the figure below:

5. For an optimized view of all the counters, stretch the layout of the Port Counters tab or isolate
(=let float) the Port Counters tab (see also 9.2) into a stand-alone window, see figure below:

6. The table below lists all the monitored counters and their description.

Counter Name Description
Input
Octets In The total number of octets received on the interface, including framing characters.
Ucast In Packets The number of packets, delivered by this sub-layer to a higher (sub-) layer, which
were not addressed to a multicast or broadcast address at this sub-layer.
Disc In Packets The number of discarded inbound packets (even though no errors had been
detected in these packets) and not delivered to a higher-layer protocol. One
possible reason for discarding such a packet could be to free up buffer space.
Error In Packets For packet-oriented interfaces, the number of inbound packets that contained
errors preventing them from being deliverable to a higher-layer protocol.
For character-oriented or fixed-length interfaces, the number of inbound
transmission units that contained errors preventing them from being deliverable to
a higher-layer protocol.
two counter values:
upper value: actual (=most recent) value
bottom value: previous value
Not clicked yet,
measuring not started
Click Refresh button
Fresh values
Old values
moved
BG-M370-E-8 Page 175 of 189
Unkn Prot Disc
Packets
For packet-oriented interfaces, the number of packets received via the interface
which were discarded because of an unknown or unsupported protocol.
For character-oriented or fixed-length interfaces that support protocol
multiplexing the number of transmission units received via the interface which
were discarded because of an unknown or unsupported protocol. For any
interface that does not support protocol multiplexing, this counter will always be 0.
Output
Octets Out The total number of octets transmitted out of the interface, including framing
characters.
Counter Name Description
Ucast Out
Packets
The total number of packets that higher-level protocols requested to be
transmitted, and which were not addressed to a multicast or broadcast address at
this sub-layer, including those that were discarded or not sent.
Disc Out Packets The number of discarded or untransmitted outbound packets (even though no
errors had been detected). One possible reason for discarding such a packet
could be to free up buffer space.
Error Out Packets For packet-oriented interfaces, the number of outbound packets that could not
be transmitted because of errors.
For character-oriented or fixed-length interfaces, the number of outbound
transmission units that could not be transmitted because of errors.

10.4 VRRP Monitoring
(More info on VRRP can be found in 5.19)
VRRP is based upon the sharing of a virtual IP Address amongst all the router interfaces being part
of the same VRRP Group. This is achieved by combining a master and one or more backup router
interfaces into one Group.
Via VRRP Monitoring, it is possible to see which is the current Master and Backup router for a
specific VRRP Group, the current status or values of some VRRP related parameters.
VRRP monitoring can be done via the L3 features tab right-click VRRP instance Monitor. A
new monitoring [M] tab (e.g. [M]VRRP/<VRRP instance>) opens in the middle body view, see figure
below.
Refreshing the screen must be done via clicking the Refresh button. The Navigation Toolbar can be
used as described in 5.32.

Refresh
button
1
6
4
5
Navigation Toolbar
Virtual Router
with 4 Groups
Page 176 of 189 BG-M370-E-8
The table below shows the displayed parameters and their description.
Parameter Behaviour Description
Interface State Dynamic Master/ Slave: indicates whether this interface is the
Master or the Slave of the Group.
Interface Virtual-IP Address Static Indicates the virtual IP Address that was configured for
the Group in the VRRP configuration wizard. All the
router interfaces within a Group use a same unique
virtual IP address, e.g 10.10.10.1. The virtual IP
address and router interfaces must be in the same
subnet. The virtual IP address will be the default
gateway for its associated VLAN e.g. VLAN with VID
150.
Interface (Virtual) MAC Address Static Indicates the Virtual MAC Address of the node.
Interface Priority Static Indicates the configured Priority value for each
individual Router interface; The higher the value, the
higher the priority.
Become Master Dynamic Indicates how many times this router interface has
become master of the group since the node was
rebooted last time. Typically in a stable network when
no switch overs have occurred yet, this value = 1 for
the master and 0 for the backups of the group.
Advertise Received Dynamic Indicates how many advertisements this router
interface has received since the node was rebooted
last time. (A master router interface within the VRRP
instance communicates its state and priority via
advertisements towards the other backup router
interfaces. This advertising occurs according the filled
out Advertisement Interval (configured on Group
level).
Advertise Interval Errors Dynamic Indicates how many times this router interface has
received an advertisement for which the advertisement
interval was different than the one configured for the
local virtual router, since the node was rebooted last
time.
Authenticate Failures Dynamic Indicates how many times this router interface has
received advertisements with the wrong authentication
since the node was rebooted last time. If this counter is
different from 0, it might mean an intruder in your
network or a misconfiguration.
Authenticate Type Mismatch Dynamic Indicates how many times this router interface has
received advertisements with the wrong authentication
type since the node was rebooted last time. If this
counter is different from 0, it might mean an intruder in
your network or a misconfiguration.

BG-M370-E-8 Page 177 of 189
10.5 IGMP Snooping Monitoring
IGMP snooping is designed to prevent hosts on a local network from receiving traffic for a multicast
group they have not explicitly joined. It provides the N50/N70 series nodes with a mechanism to
diminish multicast traffic from links that do not contain a multicast listener (an IGMP client).
(More info on IGMP Snooping can be found in 5.12)
IGMP snooping monitoring can be done via the L2 features tab expand IGMP Snooping right-
click <VLANx> Monitor. A new monitoring [M] tab (e.g. [M]IGMP Snooping/<VLANx>) opens in
the middle body view, see figures below:

Refreshing the screen must be done via clicking the Refresh and/or Reload buttons.
Network Drawing:
Blocked Multicast Port: This port has been configured in the OMS-FEM (see 5.12.3) to
block outgoing multicast traffic. No multicast traffic will be outputted on this port.
Static Router Port: This port has been configured as a static router port (see 5.12.3). As a
result, this router port is always there and is not the result of a dynamic learning process; This
port will always stream out all the streams of the monitored VLAN.
Dynamic Router Port: a port will be marked as such when the following two conditions are
met:
The static router port checkbox has been unchecked for this port (see 5.12.3);
Refresh
button
Right-click:
Monitor
Available
Streams
Monitoring: IGMP Snooping
Counters
per Node
Reload
button
All nodes of this
selected VLAN 220
This record is listed here because Node4 port6 is streaming
out this stream (src IP: 192.168.15.11, grp IP: 226.0.0.4)
because the connected user has joined for it.
Page 178 of 189 BG-M370-E-8
This port has been dynamically selected as Querier port and IGMP Queries are entering
this port. As a result all the streams of this VLAN will be streamed out on this port. It could
turn into a non-router port later on when the situation changes in the network.
Regular Port (grey front/SLAN port): This port will stream out only when the connected user
joins for a stream;
The Navigation Toolbar can be used as described in 5.32.
Clicking the Refresh Button refreshes only the values in the tables (counters per node,
available streams). It will not refresh port colors in the network drawing. The layout of the
network drawing stays intact.
Clicking the Reload Button reloads and refreshes the entire page: the values in the tables
(counters per node, available streams), the port colors in the network drawing. It also sets
back the initial table design of the available streams (drag & dropped columns, e.g. for filtering
reasons, will be set back). The layout of the network drawing will be set back to the default
layout.
Tables:
Table left-hand side: counters per node: the screen shows per node (one column per node)
IGMP Snooping counters. The counter values can be resetted for <NODEx> by rebooting
<NODEx>. Sorting data can be done via clicking/toggling the header cells.
Table right-hand side: available streams: lists all the available streams. Some streams are
joined (regular port), other streams are always available (router port). The Streaming Out
Port is the port which streams out the stream, listed in that specific record. Sorting data can be
done via clicking/toggling the header cells.
Filtering Streams: filtering can be done by dragging and dropping one or more of the header
cells (e.g. Streaming Out Ports) into the section above the table. An example can be found in
the screenshot below.
Resetting the original table layout can be done via clicking the Reload Button.

The table below lists the stream parameters:
Available Streams
Parameter Description
Streaming Out Ports the port which streams out the available stream
VLAN ID the monitored VLAN
Source IP Address the IP Address of the stream transmitter
Group IP Address the destination or Group IP Address of the stream
Drag & Drop
Streams
grouped
per port
FILTERING Streams
BG-M370-E-8 Page 179 of 189
10.6 IGMP Monitoring
IGMP is a protocol used between hosts and neighbouring local multicast routers. This protocol
manages multicast-group memberships. If a host wants to receive a multicast stream, the host must
be member of the multicast group. IGMP can be used to manage/distribute multicast streaming video
and allows more efficient use of the available bandwidth and resources.
(More info on IGMP can be found in 5.21)
IGMP monitoring can be done in a VLAN in which the IGMP instance is active. This can be done via
the L3 features tab right-click VLAN within the IGMP instance Monitor. A new monitoring
[M] tab (e.g. [M]IGMP/<VLANx>) opens in the middle body view, see figure below.

Only nodes will be displayed that have a Virtual Router configured in the monitored VLAN.
Refreshing the screen must be done via clicking the Refresh buttons.
Network Drawing:
Used Virtual Router(s): The IGMP instance within the monitored VLAN has been configured
on this virtual router. All IGMP virtual routers will initially be marked as Used Virtual
Router(s). This means that these virtual routers are candidate Queriers and can turn into
Virtual Router as Active Querier if it gets selected in the Querier election process.
Not Used Virtual Router(s): The IGMP instance within the monitored VLAN has not been
configured on this virtual router. This means that these virtual routers will not participate in the
IGMP protocol and will not act as a Querier. This virtual router will just pass IGMP messages
(queries, .) transparently.
Virtual Router as Active Querier: The IGMP instance within the monitored VLAN has been
configured on this virtual router. Furthermore, this virtual router was elected in the Querier
election process to become the active Querier. This virtual router will generate the IGMP
queries.
Clicking Refresh Button1 refreshes only the values in the tables (counters per node, IGMP
properties). It will not refresh virtual router colors in the network drawing. The layout of the
network drawing stays intact.
Clicking Refresh Button2 refreshes all: the values in the tables (counters per node, IGMP
properties), the virtual routers colors in the network drawing.

Monitoring: IGMP
Right-click:
Monitor
Counters
per node
IGMP VLAN
Properties
All nodes of this
selected VLAN 220
Refresh
button1
Refresh
button2
Page 180 of 189 BG-M370-E-8
Tables:
Table left-hand side: counters per node: the screen shows per node (one column per node)
IGMP counters. The counter values can be resetted for <NODEx> by rebooting <NODEx>. If
the values for a specific node are empty, it means that IGMP has not been configured on this
virtual router or node (=Not Used Virtual Router). Sorting data can be done via
clicking/toggling the header cells.
Table right-hand side: IGMP VLAN Properties: these properties and settings are common
for the entire monitored VLAN, it means that the listed nodes will all have the same values or
no values at all. See 5.21 for a description of the IGMP VLAN Properties. If the values for a
specific node are empty, it means that IGMP has not been configured on this virtual router or
node (=Not Used Virtual Router). Sorting data can be done via clicking/toggling the header
cells.

BG-M370-E-8 Page 181 of 189
10.7 PIM-SM Monitoring
(More info on PIM-SM can be found in 5.23)
PIM (Protocol-Independent Multicast) is a multicast routing protocol. It is protocol-independent
because PIM does not have a network topology discovery mechanism like other routing protocols
have. PIM uses routing information supplied by other routing protocols. PIM builds up Multicast
Distribution Trees for each IP Multicast Group Address. As a result, data packets from senders to a
multicast group reach all receivers which have joined the group via IGMP. The senders announce their
streams via Rendez-vous Points (RPs)

PIM-SM monitoring can be done via the L3 features tab right-click PIM instance Monitor. A
new monitoring [M] tab (e.g. [M]PIM/<PIM instance>) opens in the middle body view, see figure below.

Refreshing the screen must be done via clicking the Refresh button.
RP: Router400
RP: Router300
Router100
announce
announce
JOIN
JOIN
Monitoring: PIM-SM
Right-click:
Monitor
Neighbors
Refresh
button
RPs
Statistics
Multicast
BSRs
Page 182 of 189 BG-M370-E-8

Network Drawing:
Router300 and Router400: Rendez-vous Point candidates.
Router100: router that processes joins and finally sends streams to the clients.
Tables:
Neighbor Table: the table shows all the neigbors (and its properties) of each Virtual Router in
the monitored PIM-SM component. Sorting data can be done via clicking/toggling the header
cells.
Rendez-vous Point (RP) Table: the table shows all the Rendez-vous Point candidates
available in the monitored PIM-SM component. Sorting data can be done via clicking/toggling
the header cells.
Node Statistics Table: the table shows some statistics about the virtual routers participating
in the PIM-SM component. Sorting data can be done via clicking/toggling the header cells.
Multicast Table: the table shows all the multicast streams available in the PIM-SM
component. Sorting data can be done via clicking/toggling the header cells.
Bootstrap (BSR) Table: the table shows all the Bootstrap candidates available in the
monitored PIM-SM component. Sorting data can be done via clicking/toggling the header
cells.
Filtering can be done by dragging and dropping one or more of the header cells (e.g. Virtual
Routers) into the section above the table. An example can be found in 10.5 and 10.8.
Resetting the original table layout (after filtering etc) can be done via clicking the Refresh
button.
Neighbor Table
Node ID the Node URL of the node on which a PIM neighbor was detected.
Neighbor IP Address the IP Address of the discovered PIM neighbor or neighbor router
interface.
VLAN the VLAN URL of the VLAN to which the neighbor router interfaces
belongs.
DR IP Address the IP Address of the Designated Router for that specific neighbor.
Rendez-vous Point (RP) Table
Virtual Router the name of the virtual router on which the RP candicate is located.
Interface Address the address or URL of the Virtual Router interface that is participating in
PIM-SM. This is a PIM-SM interface.
Interface IP Address the IP Address of the PIM-SM interface.
Active RP Active RP = X: this RP was elected out of the RP Candidates (RP-C) as
active RP.

Active RP = (empty): this RP Candidate is not active but standby.
Multicast Group the IP address of the multicast group for which this PIM-SM interface is the
RP.
Node Statistics Table
Number of (S,G)
Entries
Indicates the amount of announced multicast streams available on that
node, with S = Source IP Address and G = Group IP Address. A value
different from 0 indicates that this node is a First Hop Router (FHR).
BG-M370-E-8 Page 183 of 189
Number of (*,G)
Entries
Indicates the amount of joined multicast streams (G = Group IP Address).
Last Hop Count Indicates the amount of multicast streams that will be streamed out on this
node, to one or more local clients whenever the streams are available. A
value different from 0 indicates that this node is a Last Hop Router (LHR).
Multicast Table
Outgoing Interface field empty:
The stream has been registered on a node but has not been joined yet.

field not empty:
The stream has been registered on a node and has been joined. The field
indicates the VLAN in which the multicast stream is streamed out.
Source IP Address the IP Address of the multicast stream transmitter.
Group IP Address the destination or Group IP address of the multicast stream.
Bootstrap (BSR) Table
Node ID the URL of the node.
Interface Address the address or URL of the Virtual Router interface that is participating in
PIM-SM. This is a PIM-SM interface.
Interface IP Address the IP Address of the PIM-SM interface.
Active BSR Active BSR= X: this BSR was elected out of the BSR Candidates (BSR-
C) as active BSR.

Active BSR = (empty): this BSR Candidate is not active but standby.
Active means that this BSR was elected out of the BootstrapRouter
Candidates (BSR-C) to become the active BSR.

Page 184 of 189 BG-M370-E-8
10.8 OSPF Monitoring
(More info on OSPF can be found in 5.22)
Before OSPF monitoring is shown, take a look at the created Virtual Routers first. In the example
below, four Virtual Routers have been created, two (20-1 and 20-2) in node 20 and another two in
node 40 (40-1 and 40-2).

OSPF is a dynamic routing protocol for IP networks. A dynamic routing protocol always determines the
best possible routing path. For example, determined routes may dynamically change because a
specific route becomes less or more preferred than before.
OSPF monitoring can be done via the L3 features tab right-click OSPF Area instance
Monitor. A new monitoring [M] tab (e.g. [M]OSPF/<OSPF Autonomous System>) opens in the middle
body view, see figure below. All the Virtual Routers in that OSPF instance or Autonomous System will
be shown. Also the Areas are visible.

Virtual Router
40-1
Virtual Router
40-2
Virtual Router
20-1
Virtual Router
20-2
Monitoring: OSPF
Right-click:
Monitor
Neighbor
Table
OSPF Routing
Table
Refresh
button
The monitored
Autonomous
System
BG-M370-E-8 Page 185 of 189

Refreshing the screen must be done via clicking the Refresh button.
Clicking the Refresh Button refreshes the values and sets back the initial table design within the
screen. The table design could have been changed for filtering reasons.
The Navigation Toolbar and informational pop-ups can be used as described in 5.32.

Network Drawing:
ASBR: Indicates that the marked Virtual Router is an ASBR router.
ABR: Indicates that the marked Virtual Router is an ABR router.
Tables:
Table left-hand side: Neighbor Table: the table shows all the neigbors (and its properties) of
each Virtual Router in the monitored Autonomous System. Sorting data can be done via
clicking/toggling the header cells.
Table right-hand side: OSPF Routing Table: the table shows the dynamic learnt routes via
OSPF for each Virtual Router in the Autonomous System.
Filtering can be done by dragging and dropping one or more of the header cells (e.g. Virtual
Routers) into the section above the table. An example can be found in the screenshot below.
Resetting the original table layout (after filtering etc) can be done via clicking the Refresh
button.

Monitoring: OSPF
Area BB1
40-1:
Virtual
Router
Name
BB1
BB1
FILTERING Virtual Routers
Drag & Drop
Page 186 of 189 BG-M370-E-8
Neighbor Table
Virtual Router Indicates the name of the measured Virtual Router in the network.
Neighbor IP-Address Indicates the IP-Address of the neigbor of that Virtual Router. A Virtual
Router can have one or more neighbors.
Neighbor Router ID This is a unique ID that identifies the neighbor OSPF router. It is pre-filled
out with the IP address of the first listed router port of that Virtual Router
during OSPF configuration. The Router Id field is unique throughout the
Autonomous System.
State Indicates the different states of the neigbor during dynamic set-up of the
OSPF protocol and tables. Once the neighbor state is Full, both neighbors
are fully adjacent.

down: This is the initial state of a neighbor communication. It means that
this Virtual Router has received no recent information from the neighbor
yet.

attempt: This state is only valid for neighbors attached to NBMA (=Non
Broadcast Multiple Access) networks. It indicates that no recent
information has been received from the neighbor, but that a more
concerted effort should be made to contact the neighbor.

init: In this state, an Hello packet has recently been received from the
neighbor. However, a bidirectional conversation between this Virtual
Router and its neighbor has not been established yet.

twoWay: In this state, communication between the Virtual Router and its
neigbor is bidirectional. This is the result of the operation of the Hello
Protocol.

exchangeStart: This is the first step in creating an adjacency between the
two neighboring routers. The goal of this step is to decide which router is
the master, and to decide upon the initial DD sequence number. Neighbor
conversations in this state or greater are called adjacencies.
exchange:In this state the router is describing its entire link state database
by sending Database Description packets to the neighbor. Each Database
Description Packet has a DD sequence number, and is explicitly
acknowledged.
Loading: In this state, the Virtual Router has sent Link State Request
packets to its neighbor asking for the more recent LSAs (=Link State
Advertisement) that have been discovered (but not yet received) in the
exchange state.

Full: In this state, the Virtual Router and its neighbor are fully adjacent.
Prio This value indicates the Virtual Router interface priority. This value is used
to determine the Designated Router (DR) for the link connected to the
interface. In the DR election process the highest Priority wins and becomes
DR. If the two DR candidates have the same Priority, the highest Router Id
(RID) wins.
Routing Table
Virtual Router Indicates the name of the measured Virtual Router in the network.
Destination Indicates the destination IP address of the advertised route.
Subnet Mask Indicates the subnet mask of the destination of the advertised route.
Next Hop IP Address Indicates the IP address of the next hop via which you want the traffic to
travel to reach its final destination. The final destination is indicated in the
BG-M370-E-8 Page 187 of 189
Destination IP address.
Area Indicates the Area in which the destination of the route resides.
Route Type Indicates the Route Type, find below a list of the possible values:

intraArea: The destination of the route is located in the same Area as the
Area of the Virtual Router interface.

interArea: The destination of the route is located in an Area other than the
Area of the Virtual Router interface.

type1External: The destination of the route is located outside the
Autonomous System. External routes are redistributed into the
Autonomous System.
Type1: route cost = internal OSPF cost + external redistributed cost
type2External: The destination of the route is located outside the
Autonomous System. External routes are redistributed into the
Autonomous System.
Type2: route cost = external redistributed cost
Route Cost Indates the cost of the route. The lower the cost, the more favoured the
route will be.
TOS TOS = Type Of Service Future use.

Page 188 of 189 BG-M370-E-8
11. TROUBLE SHOOTING
11.1 My Traffic is Not Coming out of this Port?
Verify MSTP: If no specific MSTP per VLAN is configured, a common and internal spanning tree
(=CIST, =not VLAN aware) is active automatically. This CIST blocks ports independent of the VLAN
they are in. This means that if port1 resides in VLANa, and port2 resides in VLANb, and both ports are
part of a loop somehow, one of the ports is automatically blocked by this CIST, because the CIST is
not VLAN aware!
11.2 Port Counters
In addition to Port Mirroring (see 5.13), the Port Counters indicate all sorts amounts of incoming and
outgoing traffic on a selected port, for tracing and statistics purposes. See 10.3 how to monitor the
Port Counters.

12. NODE/SERVICE RENAMING
It is possible to rename the nodes and/or services of the N50/N70 Series Nodes. This is possible via
an integrated tool in the OMS Console via OMS Console Tools OMS Server Node/Service
Renaming...
In advance of using this tool, the servers must be stopped via clicking the Stop Server(s) button in the
OMS Console. A full description of this tool can be found in the OMS User Manual, see Ref. [1].

13. ABBREVIATIONS
ABR Area Border Router
ARP Address Resolution Protocol
ASBR Autonomous System Boundary Router
BC Broadcast
BPDU Bridge Protocol Data Unit
CIDR Classless Inter-Domain Routing
CIST Common and Internal Spanning Tree
CLI Command Line Interface
DLF Destination Lookup Failure
DNS Domain Name System
DR Designated Router
EAP Extensible Authentication Protocol
EAPOL EAP over LAN
FFR Full Feature Ready
FHR First Hop Router
GET Gigabit Ethernet
GMRP Generic Multicast Registration Protocol
GUI Graphical User Inteface
GVRP Group VLAN Reduction Protocol
ICMP Internet Control Message Protocol
IGMP Internet Group Management Protocol
IP Internet Protocol
IPTV Internet Protocol TeleVision
IP ACL IP (address) Access Control List
LACP Link Aggregation Control Protocol
BG-M370-E-8 Page 189 of 189
LAG Link Aggregation Group
LAN Local Access Network
LHR Last Hop Router
LSA Link State Advertisement
MAC ACL MAC (address) Access Control List
MC Multicast
MGT Management
MIB Management Information Base
MMRP Mobile Mesh Routing Protocol
MRM Media Redundancy Manager
MRC Media Redundancy Client
MRP Media Redundancy Protocol
MSTi Multiple Spanning Tree Instance
MSTP Multiple Spanning Tree Protocol
MTU Maximum Transmission Unit
MVRP Multicast VLAN Registration Protocol
OID Object Identifier
OMS OTN Management System
OMS-FEM OMS Front End Manager
OSPF Open Shortest Path First
OTN Open Transport Network
PoE Power over Ethernet
PD Powered Device
PSE Power Sourcing Equipment
PIM Protocol-Independent Multicast
PSU Power Supply Unit
PVID Port VLAN ID
QoS Quality of Service
RADIUS Remote Authentication Dial In User Service
RSTP Rapid Spanning Tree Protocol
RID Router ID
SFP Small form-factor pluggable
SSM
SLAN
Source Specific Multicast
Segmented LAN
SNMP Simple Network Management Protocol
STP Spanning Tree Protocol
TTL Time To Live
TFTP Trivial File Transfer Protocol
UDP User Datagram Protocol
VID VLAN ID
VLAN Virtual LAN
VRRP Virtual Router Redundancy Protocol

Oms Fem

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Oms Fem

Caricato da

Copyright:

Formati disponibili

OTN Manual

OMS-FEM (OMS Front End Manager) v9.5

Potrebbero piacerti anche