Sei sulla pagina 1di 189

OTN Manual

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

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

OTN Manual OMS - FEM (OMS Front End Manager) v9.5 Doc. No.: BG - M370 -

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)

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

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

Open Transport Network

OMS-FEM (OMS Front End Manager)

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

OMS-FEM (OMS Front End Manager)

Open Transport Network

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

Open Transport Network

OMS-FEM (OMS Front End Manager)

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

OMS-FEM (OMS Front End Manager)

Open Transport Network

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 Ethernet…vouchers 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 don’t 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.

Project Selection List . A screenshot of the OTN OMS Licenses Tool can be found in

Open Transport Network

OMS-FEM (OMS Front End Manager)

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.

OMS-FEM (OMS Front End Manager)

Open Transport Network

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 Yesis 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 ManagerEnabled’ must be set to ‘True’ later on in the OMS Console, see §3.3.

set to ‘ True ’ later on in the OMS Console, see § 3.3. 3.2 Connection

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, SLANsThis 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

12] on the

N50/N70 series nodes in the OTN-X3M network or one of the ethernet front ports [1

ET100DAE card, or one of the ethernet front ports [1

connection provides access to a SNMP communication channel along the OTN-X3M ring.

5]

on the ET100AE card. This

OMS MGT
OMS
MGT

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

(see §3.1). See also Chapter ‘Startup/OMS logon’ in the OMS Manual, see Ref. [1].

General General. This is OK already if Yes’ was selected during installation

Open Transport Network

OMS-FEM (OMS Front End Manager)

Open Transport Network OMS-FEM (OMS Front End Manager) 2. As a result, an extra section OMS-FEM

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

OMS Front End Manager: Enabled = True
OMS Front End Manager:
Enabled = True

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

Both the OMS Server and OMS-FEM Server window must turn green. From now on,

started

both servers are started successfully.

.

Green = started up Green = started up Selected database OMS Kernel successfully started
Green = started up
Green = started up
Selected database
OMS Kernel successfully started

OMS-FEM (OMS Front End Manager)

Open Transport Network

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 End Manager: Enabled = True.

General General OMS Front

Enabled = True .  General  General  OMS Front 2. Following window passes through:

2. Following window passes through:

General  OMS Front 2. Following window passes through: 3. The window below pops up. The

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:

or ET100) in the OMS GUI between the segment ports (or SLANs) of the N50/N70 series

Open Transport Network

OMS-FEM (OMS Front End Manager)

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.

Click to Expand / Collapse
Click to
Expand /
Collapse

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

Possible Field types
Possible
Field
types

In the OMS-FEM, there are four field types possible regarding to the equipment objects (or network elements):

OMS-FEM (OMS Front End Manager)

Open Transport Network

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.

the Apply button to configure the value in the OMS-FEM. 4.2 NetworkControl (NetCtrl) Field A NetworkControl

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 Second field: Measured value in the network
Click to
show/hide
second field
Second field:
Measured value
in the network
second field Second field: Measured value in the network First field: Configured value in the database
First field: Configured value in the database
First field:
Configured value
in the database

Open Transport Network

OMS-FEM (OMS Front End Manager)

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).

(=light grey color, without a little square box at the end). 4.4 NetworkStatusAlarm (NetStatAl) Field A

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
Click to
show/hide
second field
be generated to the OMS. Click to show/hide second field Second field: First field: Configured Measured
be generated to the OMS. Click to show/hide second field Second field: First field: Configured Measured
Second field: First field: Configured Measured value expected value in the network
Second field:
First field:
Configured
Measured value
expected value
in the network

OMS-FEM (OMS Front End Manager)

Open Transport Network

5.

OPERATION AND CONFIGURATION

5.1

Menu Structure

Menu Item

Menu Item Description Exit: Exit/close the OMS-FEM. If a specific view was closed for some reason,
Menu Item Description Exit: Exit/close the OMS-FEM. If a specific view was closed for some reason,
Menu Item Description Exit: Exit/close the OMS-FEM. If a specific view was closed for some reason,
Menu Item Description Exit: Exit/close the OMS-FEM. If a specific view was closed for some reason,
Menu Item Description Exit: Exit/close the OMS-FEM. If a specific view was closed for some reason,
Menu Item Description Exit: Exit/close the OMS-FEM. If a specific view was closed for some reason,
Menu Item Description Exit: Exit/close the OMS-FEM. If a specific view was closed for some reason,

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/node…properties 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.

Open Transport Network

OMS-FEM (OMS Front End Manager)

About: Indicates the used OMS-FEM version. License Information: Indicates the used ‘OMS Serial Key’ and
About: Indicates the used OMS-FEM version. License Information: Indicates the used ‘OMS Serial Key’ and
About: Indicates the used OMS-FEM version. License Information: Indicates the used ‘OMS Serial Key’ and
About: Indicates the used OMS-FEM version. License Information: Indicates the used ‘OMS Serial Key’ and
About: Indicates the used OMS-FEM version. License Information: Indicates the used ‘OMS Serial Key’ and
About: Indicates the used OMS-FEM version. License Information: Indicates the used ‘OMS Serial Key’ and

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:

Resources Equipment Network View (SLANs, Ext. LANs, VLANs, features ) (Hardware, nodes, ports, LAGs )
Resources
Equipment
Network View
(SLANs, Ext. LANs, VLANs, features
)
(Hardware, nodes, ports, LAGs
)
Event Log View

Equipment: This area shows the configured infrastructure hardware (nodes, ports… created in the OMS GUI) and LAGs (if any…created 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;

OMS-FEM (OMS Front End Manager)

Open Transport Network

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: OMS GUI: OMS-FEM GET Services Node Creation automatic automatic
OMS GUI:
OMS GUI:
OMS-FEM
GET Services
Node Creation
automatic
automatic

Open Transport Network

OMS-FEM (OMS Front End Manager)

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

§5.4.3  Node Info Example, see §5.4.4  Node View, see §5.4.5 5.4.2 Node Properties BG-M370-E-8

OMS-FEM (OMS Front End Manager)

Open Transport Network

Parameter

Field

Value

Description

 

Type

   

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

Indicates the node type that is configured in the OMS GUI or the device type that is configured in the OMS-FEM.

N5024CF/N5224C

N7024C/N7048C

N7024CF/N7224C

 

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

Indicates whether the OMS-FEM is ‘Online’ or ‘Offline

Offline

Connection State

NetStat

Offline

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: ***

Reachable

Unreachable

Measuring

Faulty

Recovery State

NetStat

Ok

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;

ClearInProgress

RollbackInProgress

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.

Open Transport Network

OMS-FEM (OMS Front End Manager)

PoE Information (Node) (see also §5.29)

 

Oper Status

NetStat

On

On: PoE module is up and running Off: PoE module is down Faulty:

Off

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)

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.

500/1000

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.

OMS-FEM (OMS Front End Manager)

Open Transport Network

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

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.

Power

Re-enable PoE

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.

Module

MRP Information

MRP Protocol

NetCtrl

Enabled

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

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.

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

Open Transport Network

OMS-FEM (OMS Front End Manager)

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.

a detailed graphical view of the selected node. See §5.4.5. View Generates a floating window with

View

Generates a floating window with the Node properties.

properties

a floating window with the Node properties. properties Node Info See §5.4.4. Add Creates or adds

Node Info

See §5.4.4.

Add

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.

Loopback

Interface

NOTE: This interface cannot be added to a VLAN. NOTE: To remove the Loopback Interface, see §5.6.3.

OMS-FEM (OMS Front End Manager)

Open Transport Network

 
Result of ‘Add Loopback Interface’
Result of ‘Add Loopback Interface’
Result of
‘Add Loopback Interface’

Load

Loads the OMS-FEM database configuration of this individual node directly into the live network.

Clear

A

‘Clear Frontend’ initiates a warm restart from the switch logic on the node (=restarting

Frontend

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

A

Reboot Front End’ initiates a warm restart from the switch logic on the node

Front End

(=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.

Open Transport Network

OMS-FEM (OMS Front End Manager)

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:

Node Info ([I]) tab
Node Info ([I]) tab

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

categories, e.g: Equipment, VLAN, L2 - …, L3 - , …  Commands : Lists the

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

the category ‘VLAN’ has been chosen, see figure below.  Parameters : Depending on the chosen

Parameters: Depending on the chosen command, some required or optional parameters can be

’ 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

filled out. Click ‘

the Execute button. See figure filled out. Click ‘ below:  Execute button : Click this

below:

Execute button. See figure filled out. Click ‘ below:  Execute button : Click this button

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.

OMS-FEM (OMS Front End Manager)

Open Transport Network

OMS-FEM (OMS Front End Manager) Open Transport Network  Info button : Shows the port mapping

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.

Port mapping Port labels used Port labels used in OMS-FEM in Node Info Commands example
Port
mapping
Port labels used
Port labels used
in OMS-FEM
in Node Info
Commands
example

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’.

Info/CLI_<subnetwork>-<node name>.txt ’.  History – Repeat Button : this list shows a history

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.

their parameters already filled out, by selecting a command and clicking the Repeat button. Page 26

Open Transport Network

OMS-FEM (OMS Front End Manager)

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

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.

VLAN icon or…

),

SLAN (or segment) ports, Right-click node Resource Node View Tab Loopback Interfaces  View Selector
SLAN (or segment) ports,
Right-click node
Resource
Node View Tab
Loopback Interfaces
 View
Selector
Node StationA,
no resources selected
Used front ports
have coloured LEDs
Ethernet front panel ports

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.

Click LAG Station A Station A icon to show LAG ports LAG ports LAG ports
Click LAG
Station A
Station A
icon to show
LAG ports
LAG ports
LAG ports

OMS-FEM (OMS Front End Manager)

Open Transport Network

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.

Station A Station A Click VLAN icon to show Transparent Station A VLANs SLAN port
Station A
Station A
Click VLAN icon to show
Transparent
Station A
VLANs
SLAN port
Front port
VLAN and Transparent
Channels
Channel ports
Entire VLAN or
VLAN ID
Transparent
Channel path from
Front SLAN
Click “?” to show
VLAN ID
entire VLAN or
Transparent
Channel path

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.

Click External LAN icon to Station A Station A Station A show external LAN/SLAN SLAN
Click External LAN icon to
Station A
Station A
Station A
show external LAN/SLAN
SLAN port
External LAN port
ports
External LAN (=ELAN)
Indication Symbol

Open Transport Network

OMS-FEM (OMS Front End Manager)

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.

Virtual Router Click Virtual Router icon to 2 Virtual Routers configured Station A Indication show
Virtual Router
Click Virtual Router icon to
2 Virtual Routers configured
Station A
Indication
show Virtual Routers in
in StationA
selected node
Virtual Router
VLANs
2 Virtual Routers configured
Numbers = VLAN ID
in StationA
Virtual Router
External LANs

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.

Click Ports icon to show Station A Poe Settings on this node PoE Settings on
Click Ports icon to show
Station A
Poe Settings on this node
PoE Settings on
Node Level
PoE Settings on
Port Level

OMS-FEM (OMS Front End Manager)

Open Transport Network

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.

Type of the device as well, either ETS-3GC7F or ETS-4GC24FP. 2. Click the Add button to
Type of the device as well, either ETS-3GC7F or ETS-4GC24FP. 2. Click the Add button to

2. Click the Add button to add the device to the Equipment window in the OMS-FEM. After clicking

this button,

window in the OMS-FEM. After clicking this button, indicates an External Device whereas indicates the OTN

indicates an External Device whereas

clicking this button, indicates an External Device whereas indicates the OTN Device. OTN Device Visual links

indicates the OTN Device.

OTN Device Visual links after adding the device ports to an ELAN OTN OTN External
OTN
Device
Visual links after
adding the device
ports to an ELAN
OTN
OTN
External
External
Device
Device
Device
Device

Open Transport Network

OMS-FEM (OMS Front End Manager)

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.

OTN Device: OTN Device: ETS-3GC7F ETS-4GC24FP 7 Fast Ethernet ports 3 Gibabit Combo ports 24
OTN Device:
OTN Device:
ETS-3GC7F
ETS-4GC24FP
7 Fast Ethernet
ports
3 Gibabit
Combo ports
24 Fast Ethernet
with PoE ports
4 Gibabit Combo
ports
External Device: Supplier xyz 4 Fast Ethernet ports
External Device:
Supplier xyz
4 Fast Ethernet
ports

5.5.3 Device Properties

OTN Device: ETS-3GC7F
OTN Device:
ETS-3GC7F
OTN Device: ETS-4GC24FP
OTN Device:
ETS-4GC24FP
External Device: Supplier xyz
External Device:
Supplier xyz

Parameter

Field

Value

Description

 

Type

   

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

Indicates the device type that is configured in the OMS-FEM; ETS-3GC7F and ETS-4GC24FP

ETS-4GC24FP

OMS-FEM (OMS Front End Manager)

Open Transport Network

   

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

Indicates whether the OMS-FEM is ‘Online’ or ‘Offline’.

Offline

Connection State

NetStat

Offline

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: ***

Reachable

Unreachable

Measuring

Faulty

Recovery State

NetStat

Ok

Ok: The device is up and running, everything fine.

Alarm Status

NetStat

Unknown

Unknown: Probably no connection between OMS-FEM and this device** In Service: Everything fine, no alarms;

In Service

SNMP Credentials (only for External Devices)

 

SNMP Version

LocCtrl

2

Configure which SNMP version is used by the

3

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.

Open Transport Network

OMS-FEM (OMS Front End Manager)

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:

Device and OTN Device are the same, see figure below: Action Description View Generates a floating
Action Description View Generates a floating window with the device properties, see §5.5.3. properties Delete
Action
Description
View
Generates a floating window with the device properties, see §5.5.3.
properties
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
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.
Browser
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.

OMS-FEM (OMS Front End Manager)

Open Transport Network

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/N70LAG N50/N70ComboLAGPort N50/N70PowerOverEthernetLAGPort
N50/N70LAG
N50/N70ComboLAGPort
N50/N70PowerOverEthernetLAGPort
N50/N70ComboPort N50/N70PowerOverEthernetPort
N50/N70ComboPort
N50/N70PowerOverEthernetPort
N50/N70SLANPort N50/N70 Loopback Interface
N50/N70SLANPort
N50/N70 Loopback Interface
PoE Available SFP Info PoE Available
PoE Available
SFP Info
PoE Available

Open Transport Network

OMS-FEM (OMS Front End Manager)

Parameter

Field

Value

Description

 

Type

   

Generic Information

 

Type

NetStat

<x>=N50/N70

<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

<x>ComboPort

<x>PowerOverEthernet-

Port

<x>LAG

<x>ComboLAGPort

<x>PowerOverEthernet-

LAGPort

<x>SLANPort

<x>VirtualPort

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:

OMS-FEM (OMS Front End Manager)

Open Transport Network

     

<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

Alarm Status

NetStat

Unknown In Service OutOfServiceMajor

Unknown: *** In Service: Everything fine, no alarms OutOfServiceMajor: Alarm situation

Admin Status

NetCtrl

Down

This field configures the administrative state of the port.

Up

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.

Open Transport Network

OMS-FEM (OMS Front End Manager)

Specific Information

 

MTU

NetCtrl

1

9216

bytes

Indicates the maximum frame size in bytes, allowed to transmit by that specific port.

(Maximum

 

Transmission

Unit)

 

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

 

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.

No Negotation

Duplex Setting

NetCtrl

Full Duplex

With ‘No Negotiation’, this setting configures the port in Full Duplex or Half Duplex.

(with No

Half Duplex

Negotiation)

Speed Setting

NetCtrl

10

Mbps

With ‘No Negotiation’, this setting configures the port in the assigned speed.

(with No

100 Mbps

 

Negotiation)

1 Gbps

 

10

Gbps

Flow Control

NetCtrl

Disable

 

Disable: Disable flow control, no pause packets will be sent.

Symmetric

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

NetCtrl

Level Off

 

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.

Control Level

[Level1…17]

Level1…17: 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

OMS-FEM (OMS Front End Manager)

Open Transport Network

     

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

NetCtrl

Enable/Disable

DLF: incoming unicast traffic with an unknown destination

Control Enable

BC

Storm

BC:

incoming Broadcast traffic

Control Enable

MC: incoming Multicast traffic

MC

Storm

Control Enable

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

On:

Enable PoE on this port. When this is

Off

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

Open Transport Network

OMS-FEM (OMS Front End Manager)

Description

NetCtrl

<text>

Port description e.g. ‘Camera train station

 

2’

Power Priority

NetCtrl

Low

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.

High

Critical

Power Class

NetCtrl

Unlimited

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 don’t 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,

Class 1

Class 2

Class 3/0

Class 4

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

Indicates the operational PoE port status. Find below the possible values:

Searching

DeliveringPower

 

Fault

Disabled:

OtherFault

-

the port was disabled for PoE by admin

Testing

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 to the PD.

No power is delivered yet

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.

OMS-FEM (OMS Front End Manager)

Open Transport Network

     

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

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.

Class 1

Class 2

Class 3

Class 4

PoE Diagnostics (see also §5.4.5e, §5.29) (These are measured values from the live network.)

 

Consumed

NetStat

<value>W

Indicates the consumed power that power device (PD) currently is consuming.

Power

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

NetStat

0 nm

Indicates the laser wavelength in nm:

WaveLength

850 nm

0 = default value, no SFP connected 850 = GBit_SX 1310 = GBit_LX

1310 nm