Net Insight Nimbra One, Nimbra 300, Nimbra One 600 User Manual

Element Manager User’s Manual

Nimbra One Nimbra 300 series Nimbra 600 series

NimOS GX4.0.3

The specifications and information in this document are provided “as is” and are subject to change without notice. All statements, information, and recommendations in this document are provided without warranty of any kind, expressed or implied, including without limitation any warranty concerning the accuracy, adequacy, or completeness of such specifications and information or the result to be obtained from using such specifications or information. Net Insight AB shall not be responsible for any claims attributable to errors, omissions, or other inaccuracies in the specifications or information in this document, and in no event shall Net Insight AB be liable for direct, indirect, special, consequential or incidental damages arising out of the use or inability to use this document.

Net Insight and Nimbra are trademarks of Net Insight AB, Sweden. All other trademarks are the property of their respective owners.

Net Insight AB Box 42093 SE-126 14 Stockholm Sweden Phone: +46 8 685 04 00 Fax: +46 8 685 04 20 E-mail: info@netinsight.net

November, 2006

Stockholm, Sweden

Textpartnumber: NGP0017-0001/PJ20

(NID 601/PJ20)

Stockholm, Sweden

Element Manager User’s Manual Nimbra One Serie Contents • i

Contents

About This Manual 7

Overview..............................................................................................................................7

Intended reader ....................................................................................................................7

Support and assistance.........................................................................................................7

Organization of content .......................................................................................................7

Conventions in this manual..................................................................................................8

Information of specific importance .......................................................................8

Instructions............................................................................................................9

Terminal output and keyboard input......................................................................9

Web interface examples.........................................................................................9

Product Overview 10

Basics.................................................................................................................................10

About the Nimbra One.......................................................................................................10

About the Nimbra 300 series .............................................................................................12

About the Nimbra 600 series .............................................................................................13

The User Interface 15

Overview............................................................................................................................15

Connecting to the units ......................................................................................................15

Required software................................................................................................15

Command Line Interface ...................................................................................................16

Web interface.....................................................................................................................16

Frequently used terms..........................................................................................17

Logging in using the Telnet connection.............................................................................17

Terminal connection, Nimbra 340.......................................................................17

Logging in using a web browser........................................................................................17

Quick Start Guide 19

Overview............................................................................................................................19

Configuration.....................................................................................................................20

Set the System Parameters...................................................................................20

Set the DTM address ...........................................................................................20

Set the DTM routing parameters, dynamic routes...............................................21

Save the configuration.........................................................................................23

Restart the system................................................................................................23

Maintenance 25

Overview of maintenance ..................................................................................................25

Setting of system parameters .............................................................................................26

Restart the system................................................................................................27

Date and time setting .........................................................................................................27

Users..................................................................................................................................28

Add or modify users and access levels................................................................28

Preferences.........................................................................................................................28

Configuration handling......................................................................................................30

Backing up the current configuration ..................................................................31

ii • Contents Element Manager User’s Manual Nimbra One Serie

Modifying entries in the configuration ............................................................... 31

Uploading configurations ................................................................................... 32

Switching configurations.................................................................................... 33

Deleting configurations ...................................................................................... 33

Software maintenance....................................................................................................... 33

Swap images....................................................................................................... 36

Deleting images.................................................................................................. 36

Status Monitoring 37

Overview of status monitoring.......................................................................................... 37

Alarms............................................................................................................................... 38

The alarms page.................................................................................................. 38

Acknowledging an alarm.................................................................................... 39

Events ............................................................................................................................... 40

Syslog ............................................................................................................................... 41

Equipment......................................................................................................................... 42

Setting the administrative status of an installed board........................................ 43

Monitoring the installed interfaces ..................................................................... 43

Inventory........................................................................................................................... 44

Monitoring the logged in users ......................................................................................... 46

Control Network 47

General about In-band management ................................................................................. 47

Ethernet DLE...................................................................................................... 47

IP and routing ..................................................................................................... 48

DLE clients......................................................................................................... 48

DLE server.......................................................................................................... 49

Multiple DLE servers ......................................................................................... 49

Configuration.................................................................................................................... 49

Building networks with DLE............................................................................................ 50

IP routing .......................................................................................................................... 52

Overview of Control Network .......................................................................................... 52

Setting up In-band servers................................................................................................. 53

Peering DLE Server............................................................................................ 54

Setting up In-band clients ................................................................................................. 55

Setting up the In-band client............................................................................... 56

IP interfaces ...................................................................................................................... 57

IP routing conf .................................................................................................................. 57

Routes................................................................................................................. 58

Setting up IP routes............................................................................................. 58

Verifying and reconfiguring an IP route............................................................. 59

Deleting an IP route............................................................................................ 60

SNMP configuration......................................................................................................... 60

Adding a SNMP notification receiver ................................................................ 62

Editing or deleting a SNMP notification receiver............................................... 62

Access control and Advanced setup ................................................................... 62

SNMP page internal data.................................................................................... 64

Format of SNMP configuration.......................................................................... 65

Configuration Procedure..................................................................................... 66

Defining SNMPv3 Users.................................................................................... 67

Defining Community.......................................................................................... 68

Defining MIB Views .......................................................................................... 68

Defining Groups and Access Rights................................................................... 70

Assigning Users.................................................................................................. 71

DTM Configuration 72

Overview of DTM configuration ...................................................................................... 72

Interfaces........................................................................................................................... 73

Element Manager User’s Manual Nimbra One Serie Contents • iii

Editing a DTM interface......................................................................................73

Adding a new DTM interface..............................................................................75

Addresses...........................................................................................................................75

Adding a DTM address .......................................................................................76

Editing or deleting a DTM address......................................................................76

Host names.........................................................................................................................76

Adding a host.......................................................................................................77

Editing or deleting host names ............................................................................78

Links..................................................................................................................................78

Routes................................................................................................................................79

General ................................................................................................................79

Static route.........................................................................................................................82

Adding a static route............................................................................................82

Editing a static routing entry ...............................................................................83

Deleting a static routing entry .............................................................................83

Dynamic routing................................................................................................................83

Setting the dynamic routing parameters ..............................................................83

Adding a dynamic routing entry..........................................................................85

Editing a dynamic routing entry ..........................................................................87

Deleting a dynamic routing entry ........................................................................87

Sync...................................................................................................................................87

Trunks 89

Overview of Trunks...........................................................................................................89

Trunk Modules, Nimbra One...............................................................................89

Trunk Modules, Nimbra 300 ...............................................................................90

Trunk Modules, Nimbra 600 ...............................................................................90

Trunk interface configuration..............................................................................90

Editing the OC-48/ STM-16 X-ADM Module ..................................................................91

Editing the 2 x OC-12/STM-4 Trunk Module ...................................................................94

Editing the OC-12/STM-4 Trunk Module (DTM 622 Trunk Module).............................94

Editing the OC-3/STM-1 Trunk Module (DTM 150 Trunk Module)...............................97

Editing the 4 x DS3/E3 Trunk Module ..............................................................................99

Editing the 4 x OC-3/STM-1 Trunk Module ...................................................................101

Optional FEC version........................................................................................103

Editing the 1 Gbps Trunk Module ...................................................................................104

Nimbra 600 Series – Trunk interfaces .............................................................................106

Performance Monitoring 110

Overview..........................................................................................................................110

General about Perf. Monitoring .......................................................................................111

Set-up of Perf. Monitoring...............................................................................................112

Set-up Perf. monitoring for Trunks and Accesses.............................................112

Set-up of the connections ..................................................................................116

Access Modules 120

Overview of access modules............................................................................................120

Access Modules.................................................................................................120

Interface settings for Access Module...............................................................................122

4 x OC3 /STM-1 Access Module ......................................................................122

Ethernet Transport Service (ETS) 125

ETS Overview .................................................................................................................125

TTPs (Trail Termination Points)......................................................................................129

Setting up an Unicast TTP...............................................................................................130

Setting up a Multicast TTP ..............................................................................................131

Verifying and reconfiguring an ETS TTP .......................................................................133

iv • Contents Element Manager User’s Manual Nimbra One Serie

Deleting an ETS TTP ....................................................................................... 134

Advanced settings............................................................................................. 135

Devices............................................................................................................................ 135

Overview of ETS Device.................................................................................. 135

Devices............................................................................................................. 137

Setting up and editing a device......................................................................... 138

Adding VLANs for fast and gigabit Ethernet card (FEC and GEC)................. 139

Setting up and editing a device interface .......................................................... 140

Priority............................................................................................................................ 143

Diffserv and Ethernet user priority ................................................................... 143

Assignment of Traffic class.............................................................................. 144

Configure priority............................................................................................. 145

TTP statistics................................................................................................................... 147

Ethernet statistics ............................................................................................................ 148

Exampel of ETS Configuration....................................................................................... 150

Isochronous Transport Service, ITS (ASI, SDI, PDH & SONET/SDH)152

Overview......................................................................................................................... 152

Setting up an ITS tunnel ................................................................................................. 154

Required information........................................................................................ 154

Terminating Connection................................................................................... 155

Originating Unicast Connection ....................................................................... 157

Orginating Multicast Connection...................................................................... 159

Terminating Multicast Connection ................................................................... 162

Editing/deleting Connections............................................................................ 163

Advanced settings............................................................................................. 163

Channel Persistence 164

General............................................................................................................................ 164

Persistence Configuration ............................................................................................... 165

Link Class Normal............................................................................................ 165

Link Class Persistent ........................................................................................ 165

Link Class Nailed ............................................................................................. 165

Restart On Error ............................................................................................... 166

Redundant DLE Servers ................................................................................... 166

Handling an Error Situation............................................................................................ 166

The DTM->Links Page..................................................................................... 166

Node Status NoControl................................................................................................... 167

Restarting a node in NoControl ...................................................................................... 168

Restarting via Outband Management ............................................................... 168

Restarting via Serial Console............................................................................ 168

Restarting from a Neighboring Node................................................................ 168

Link Errors...................................................................................................................... 168

Channels with broken control-paths................................................................................ 168

Tearing down a unicast channel........................................................................ 169

Reestablishing a unicast channel ...................................................................... 169

Reestablishing a multicast channel................................................................... 169

DLE .................................................................................................................. 170

Source Routing 171

Overview......................................................................................................................... 171

Loose and strict source-routes .......................................................................... 172

Configuration.................................................................................................... 172

Example.......................................................................................................................... 172

Strict source-route............................................................................................. 172

Loose source-route ........................................................................................... 174

Specifying interfaces ........................................................................................ 174

Using a source-route in a TTP.......................................................................... 175

Element Manager User’s Manual Nimbra One Serie Contents • v

Updating a source-route.....................................................................................176

Deleting a source-route......................................................................................176

Scheduler 177

Scheduling of connections...............................................................................................177

Set-up of Scheduling .........................................................................................178

Create a new scheduling entry...........................................................................178

Automatic scheduling activities.........................................................................179

Upgrading 181

General.............................................................................................................................181

Upgrade from GXa.b.c.d to GXe.f.g.h ..............................................................181

Remote upgrade of Interface Modules.............................................................................182

Reference 183

Alarms .............................................................................................................................183

Date and time parameters ................................................................................................183

ETS statistics counters.....................................................................................................184

Ethconf statistics counters ...............................................................................................186

Ethconf MIB2 Statistics ....................................................................................186

Ethconf RMON Statistics..................................................................................186

Nimbra One CLI commands............................................................................................188

Glossary of Terms 190

Index 193

Element Manager User’s Manual Nimbra OneSerie About This Manual • 7

About This Manual

Overview

This manual includes information on how to configure, monitor and maintain network elements of a network, comprising the Nimbra series of multi-service switches, when being installed with the Nimbra Element Manager, system software provided by Net Insight. For further information on how to install and maintain the Nimbras please see Nimbra One / Nimbra300 series / Nimbra 600

series Installation and Maintenance Manuals.

Intended reader

This manual is intended for network managers and administrators involved in operation and maintenance of network elements that use Nimbra Element Manager as element management software platform.

Support and assistance

If you have any questions about how to use your equipment or software, and if you do not find the solution to your problem in this manual, please contact your local equipment and support supplier. If any question still remains, please consult Net Insight’s Technical Support Center.

Organization of content

The contents of this manual are organized as follows:

• About this manual includes information on how to use the manual.

• Product overview provides an overview of the technology and the

product concerned.

• The user interface describes how to establish communication with the

units and the additional equipment required. The log in procedure prior to software access is also shown.

• Quick start guide contains procedures to set up and run the unit after

initial installation.

• Maintenance covers software maintenance, such as backup routines and

software upgrades.

8 • About This Manual Element Manager User’s Manual Nimbra OneSerie

• Status refers to the functions for monitoring the operational status of the

unit.

• Control network contains information on how to set up in-band

management and configure the IP routes of a unit.

• DTM configuration covers information about the node administration for

the units.

• Trunks describe the trunk interfaces that are used to connect nodes into a

network.

• Performance Monitoring shows how to use the web interface to set up

performance monitoring.

• Access covers the access interfaces that are used to feed the network with

various kinds of traffic.

• Ethernet Tunneling Service (ETS) describes how to setup an Ethernet

tunnel and the configuration and maintenance of Ethernet interfaces.

• ITS handles the Isochonous Transport Services. Describes how ITS is

used and how to create a video tunnel, PDH tunnel or a Sonet/SDH tunnel through the DTM network.

• All connections describes Source routing, what it is and how to configure

it, how to specify the exact path that a channel shall take through the network. It also describes Scheduler how it works and how the planning and control of resources and utilization in the network is done.

• Reference contains information about alarms and events, date and time

parameters, statistics counters and CLI (Command Line Interface) commands.

• Glossary of terms contains glossary, including abbreviations.

Conventions in this manual

To enhance the readability of this manual, sections of special importance or interest are marked as follows:

Information of specific importance

Note:

Information for proper function of the equipment is contained in this kind of boxes, which includes the tip heading and symbol.

Tip:

Information for better understanding and utilization of the equipment is contained in this kind of box, which includes the tip heading and symbol.

Element Manager User’s Manual Nimbra OneSerie About This Manual • 9

Instructions

The instructions given in this manual are numbered in the sequence in which they should be performed, as follows

1. Initial measure

2. Next measure

3. …

Terminal output and keyboard input

Examples of text and commands appearing on a terminal screen are marked with a special font as follows.

Example of terminal text output

Example of command <optional parameters>; ... [Enter]

where the last word represents a specific keyboard key.

Web interface examples

The configurations shown in the example web pages in this manual are taken from generic systems. Therefore the parameters might differ from the users system configuration.

10 • Product Overview Element Manager User’s Manual Nimbra OneSerie

Product Overview

Basics

The Nimbra series of multi-service switches runs the DTM (Dynamic synchronous Transfer Mode) network protocol, standardized by ETSI, which is designed to increase the utilization of optical fibers and minimize the load of the network nodes. The protocol is also designed to support real-time broadband traffic, multicasting, and the ability to dynamically adapt to traffic variations in the network.

DTM combines the simple, non-blocking, real-time traffic capabilities of circuit switching with the dynamic resource handling of packet switching technology. This covers a gap in available techniques on the market and meets the demands of strict quality of service requirements for high-bandwidth communications.

About the Nimbra One

Nimbra One is a modular switch with hot-swap support for one control module and up to seven interface modules. The backplane provides up to 20 Gbps switching capacity, with an average non-blocking capacity of 5 Gbps, making it ideal for all cases of multi service access switching. A Nimbra One can be equipped with: One Control Module (mandatory in slot 1) and any combination of trunk and access modules, presented below:

Trunk modules: 4 x DS3/E3 Trunk Module OC-3/STM-1 Trunk Module (DTM150 Trunk Module) 4 x OC-3/STM-1 Trunk Module OC-12/ STM-4 Trunk Module (DTM 622 Trunk Module) 2 x OC-12/ STM-4 Trunk Module 1 Gbps Optical Trunk (DTM1000 Trunk Module) OC-48/ STM-16 X-ADM Module Access modules: Fast Ethernet Access Module Gigabit Ethernet Access Module T1 and E1 Access Modules SDI Video Access Module ASI Transport Access Module

Element Manager User’s Manual Nimbra OneSerie Product Overview • 11

8 x ASI Transport Access Module OC-3/STM-1 Access Module

Figure 1. The Nimbra One

12 • Product Overview Element Manager User’s Manual Nimbra OneSerie

About the Nimbra 300 series

The Nimbra 300 series is a set of multi-service access and switching devices for demanding video and data applications. With its 2U height form-factor it is ideally suited for use at the customer premises or in co-location POPs. Currently the Nimbra 300 series features three switches

• Nimbra 340

• Nimbra 340-HD

• Nimbra 360

All Nimbra 300 series switches are equipped with a fixed Gigabit Ethernet access interface and two slots for a wide selection of optional plug-in units for other services, or for transport over different media. In addition the different products have got integrated ports on the chassis for:

• DVB-ASI interfaces; 2 in, 2 out, 2 monitoring ports (Nimbra 340)

• HD-SDI interfaces; 1 in, 1 out, 1 monitoring port (Nimbra 340-HD)

• Multirate SDH/SONET trunk interfaces; 4 OC-3/STM-1 ports or 4

OC-12/STM-4 ports or 2 OC-48/STM-16 ports depending on installed firmware (Nimbra 360)

The Nimbra 300 series switches can be equipped with the following plug-in modules:

Trunk modules: 4 x DS3/E3 Trunk Module 4 x OC-3/STM-1 Trunk Module OC-12/ STM-4 Trunk Module (DTM 622 Trunk Module) 2 x OC-12/ STM-4 Trunk Module 1 Gbps Optical Trunk (DTM1000 Trunk Module) OC-48/ STM-16 X-ADM Module Access modules: Fast Ethernet Access Module Gigabit Ethernet Access Module T1 and E1 Access Modules SDI Video Access Module ASI Transport Access Module 8 x ASI Transport Access Module 4 x OC-3/STM-1 Access Module

Element Manager User’s Manual Nimbra OneSerie Product Overview • 13

Figure 2. Nimbra 340

About the Nimbra 600 series

Nimbra 600 series is a multi-service core switch for demanding video and data applications. Currently, there is only one switch in this series, the Nimbra 680.

Nimbra 680 features 40 Gbps switching capacity, redundant switch planes and control modules, and has 12 slots for plug-in units. The Nimbra 600 series switches can be equipped with the following interface modules:

Trunk modules: 1 x OC-192/STM-64 4 x OC-48/ STM-16 4 x OC-12/ STM-4 4 x OC-3/ STM-1

Figure 3. Nimbra 680 configuration example

Element Manager User’s Manual Nimbra OneSerie The User Interface • 15

The User Interface

Overview

The implemented software provides necessary functionality for node management, such as configuration and monitoring of the units.

Among the functions are:

• Network configuration changes

• Unit handling

• Software diagnostics and upgrade

The majority of the units handling procedures are carried out via a web browser. The functions are also available via a text-based terminal connection.

Connecting to the units

Communication with the units is done either locally through a terminal connected directly to the unit, or when the unit is in operation, remotely over the in-band management network.

Required software

• Terminal software: To utilize the terminal connection via the Serial

Control Port, a standard terminal emulation software (VT100) is required, e.g. Windows Terminal.

• FTP client: FTP is used to transfer the required configuration files to and

from the unit.

• Web interface: For the web interfaces a standard web-browser able to

handle Java-script and cookies should be used. Internet Explorer 5.5, Mozilla 1.4 Netscape 7, Firefox 1.0 or later versions are recommended web browsers.

16 • The User Interface Element Manager User’s Manual Nimbra OneSerie

Command Line Interface

A CLI (Command Line Interface) is a set of system commands used for management of the Nimbra nodes via a Terminal or a Telnet software. E.g. the CLI can be used when connecting to the unit via the Serial Control Port using a Terminal software, or when connecting via Telnet (TCP/IP) over the Ethernet Control Port or over the in- management network. Normally the web interface should be used. The CLI is intended mainly for initial configuration operations.

Web interface

The web interface is the easiest and most straightforward way to communicate with the units. It is designed to be easy to use, to navigate and to give a good overview of the configuration status of the unit and the parameters required in each configuration. All normal monitoring and configuration should be done using the web interface. The pages of the web interface automatically adapt to the information to be monitored or configured. Refer to Figure 4.

Figure 4. The web based user interface

• Alarm monitor: Shows the number of alarms indicated and their severity.

• Utility menu: Gives access to the unit’s home and log out pages and it

also gives quick access to the alarms page; refer to chapter Status monitoring, section Alarms.

• Title bar: In this space the name of the page is displayed.

• Main menu: Here is the entire pages regarding the unit’s configuration

and monitoring accessed. The menu is organized in a tree structure where the top row shows the main items and submenus are displayed below. Functions that are not available appear grayed out.

• Links to edit this object: Link to area for editing the object.

• Status information items: Here is the information about the status of the

configurable function displayed for monitoring purposes. These items can not be changed from this particular page.

There is also other configurable information items: These items consist of web-browser-style user dialogue boxes, e.g. pull-down menus, text input boxes and buttons. Any current configuration data is shown.

Main menu

Utility menu

Alarm monitor

Tile bar

Status information

Links to edit this object

Element Manager User’s Manual Nimbra OneSerie The User Interface • 17

Frequently used terms

The following terms and parameters are frequently used throughout the Element Manager:

Admin: The administrative status of the object (e.g. route, interface, server, card or function). The operator can either set the administrative status to Up if the object is to be activated, or to Down if it is to be deactivated.

Oper: The operational status of the object (e.g. route, interface, server, card or function). Up indicates that the object is active, while Down indicates that it is inactive. If the operational status shows Down while the administrative status is Up this is an indication of that an error has occurred.

Toggle Admin: Before any parameters can be changed, the administrative status of the interface must be set to down. To simplify this procedure, Toggle admin tells the node to set the administrative status of the interface to down, reconfigure all parameters and then set the administrative status to the configured value.

Local node: Is also mentioned as source and originating node. Remote node: Is also mentioned as destination, terminating and sink node.

Logging in using the Telnet connection

Terminal connection, Nimbra 340

1. Establish communication with a unit over a TCP/IP network. If the unit

has just been installed, you must first use the local serial connection according to the Nimbra 340 Installation and Maintenance Manual.

2. Start a Telnet client and enter connect (IP a ddress o f

the unit) and press [Enter].

When connection is established the following information appears on the terminal:

nimbra 340 login:_

3. Enter the user name and, when prompted for, the password.

Password:_ Nimbra pre -release 0.1

nimbra340: ~ #

The unit is now ready to receive commands. For a further description of commands, please see Reference chapter, section Nimbra 340 CLI commands.

Logging in using a web browser

1. Establish the connection, either locally or remotely, and start the browser.

2. Enter the name or the IP-address of the unit in the address field. A Web

interface start page, similar to Figure 5, will appear in the browser window.

18 • Element Manager User’s Manual Nimbra OneSerie

Figure 5. The start page

In the lower half of the page some unit information is given. This information is entered when the unit is installed and can be changed when required.

3. In the top half of the page a menu system appears. The only active menu

item is Log in, click on it to log in. The Login page, Figure 6, will appear.

Figure 6. The login page

4. Enter the user name in the Login field and then go to the Password field

and enter the password. The password will be hidden. Click OK.

If the user name and password are accepted a screen similar to the start page, Figure 5, will appear, with all the menu items enabled. If the user name or password is not accepted an error message is shown, and the login page, Figure 6, will reappear.

Element Manager User’s Manual Nimbra OneSerie Quick Start Guide • 19

Quick Start Guide

Overview

There are some initial configurations, which are needed before the nodes could be used in the network. The instructions in this chapter are intended to guide the operator that quickly needs to get a Nimbra One up and running in a network.

The operator needs to be familiar with technology in general and the chapter The user interface in this manual.

Note:

Before these procedures are performed, be sure that the unit is properly installed according to the relevant Installation and Maintenance Manual.

When following the quick start procedures, do not change other parameters than the ones instructed. Leave the other parameters blank or with default values.

This chapter shows the minimum of configuration which should be done in the node in order to get a Nimbra One up and running in a network and it describes how to use the web interface to configure the node.

The minimum configurations steps:

• Configuration of System information settings

• Adding of a DTM address

• Set up of the Routing parameters

• Back up the Configuration

• Restart the system

For more information about the functions, refer to the Maintenance, Configuration and Reference chapters in this manual.

20 • Quick Start Guide Element Manager User’s Manual Nimbra OneSerie

Configuration

These procedures will set the basic parameters of the Nimbras. For a basic configuration, keep the following information at hand:

Parameter name Description Type

System name The name of the unit, to be used instead

of the IP address, for easier recognition in the web page.

Opt

Location Description of the location of the unit. Opt

Contact person The name or e-mail address of the

contact person for the unit.

Opt

DTM address Shows the DTM address of the node. Man

Type definitions: Man – mandatory, Rec – recommended, Opt – optional

Set the System Parameters

1. Navigate to the Maintenance|System page, Figure 7 will appear.

Figure 7. The Maintenance, System page

2. Enter the System name, the name of the Contact person and the Location.

3. If Events should be logged tick the appropriate boxes and enter the Event

and Alarm log size.

4. To make parameters active without leaving the page, click Apply. Any

changes will then be made effective immediately. To return to the

Maintenance page, click OK.

Set the DTM address

1. Navigate to the web page DTM|Addresses and click on the Add address

button. The Add page, Figure 8, will appear.

Element Manager User’s Manual Nimbra OneSerie Quick Start Guide • 21

Figure 8. Add DTM address

2. Set the DTM address of the unit. Make sure that Primary address is set to

Yes. Click OK.

3. The DTM Addresses page, Figure 9, will appear. The DTM loopback

address 00.00.00.00.00.00.00.01, is always shown in the list.

Figure 9. DTM address

Note:

A change in the primary DTM address does not take effect until after the node has been restarted.

Set the DTM routing parameters, dynamic routes

Dynamic routing where a routing protocol (DRP) calculates the routing tables automatically.

1. Navigate to the web page DTM|Routing, the Routing page, Figure 10, will

appear.

Figure 10. Dynamic routing

2. Click on Dynamic routing config, Figure 11, will appear.

22 • Quick Start Guide Element Manager User’s Manual Nimbra OneSerie

Figure 11. Routing entries

• Node metric: The cost of switching a channel in this node.

• Enable: Decides if DRP should be enabled or not. If this is not enabled,

only the static routing entries will be used.

• Interface metric: The cost of setting up a channel out via this interface.

• Enable: Should this node communicate and exchange routing information

with a neighbor via this interface? This check box should normally be

enabled when using DRP. It can be disabled when DRP should not be used

via specific interface, e.g. if that interface connects to another operator and

you don’t want to exchange routing information automatically with that

operator.

Advanced settings

• Node is a:

Switch or End node:

If a node is attached to the rest of the network using a single point-to-point

link only, then the node doesn’ t need a complete routing table. The only

routing entry that is necessary is a default route that says that all other

addresses can be reached via the peer on the other side of the point-to-point

link. In DRP terminology, this type of node is called an end-node and all

other nodes are called switches.

• End node, in this case the node will get a default-route listing all the

available peers as possible next hops with no particular preference. This can

be useful if a node has two peers for redundancy purposes only and all other

destinations is the network can be reached at roughly the same cost via both

peers.

Note! If a node is configured as an end node, it can only originate and terminate channels; it will not allow a channel to be switched via itself.

If the node is configured as an end node:

• Default gateway: Calculates which way that should be default gw.

Element Manager User’s Manual Nimbra OneSerie Quick Start Guide • 23

• Area number: In a large network all the nodes can not belong to the same

area. Configure the area it should belong to.

• Detect from neighbors: The node will receive the area number from the

neighbor.

3. Enter the Node metric and select Enable.

4. If one of the interfaces is more critical to use than the other, enter a metric

for the DTM interface.

5. Select if the node should be a switch or an end node.

6. Click OK.

7. Save the new configuration.

Save the configuration

1. Navigate to web page Maintenance|Configurations and click on the Save

configuration button. The Save page, Figure 12, will appear.

Figure 12. Backup of the configuration

2. Enter a suitable name in the Name field, and a description of the

configuration in the Description field. Make sure that the Valid checkbox is ticked. Click OK.

Restart the system

1. Navigate to web page Maintenance|System. The System page, Figure 13,

will appear.

24 • Quick Start Guide Element Manager User’s Manual Nimbra OneSerie

Figure 13. The Initial config page

2. Click on restart or halt system at the top of page, Figure 14, will appear. In

the field type Restart. When the system is re-started the contact with the

browser is lost. After a short time, less than a minute, click on the “reload” button in the web browser to connect again.

Figure 14. The restart page

Tip:

The DTM, Links page can be used to check if the links to the surrounding nodes have been established properly.

Element Manager User’s Manual Nimbra OneSerie Maintenance • 25

Maintenance

Overview of maintenance

This chapter describes general maintenance of the unit. Functions and software using the web interface, such as supervision of status and configurations. How to backup and modify configurations.

The start web page for maintenance is shown in Figure 15 below.

Figure 15. The maintenance web page

The sub-sections are:

• System: A subset of the administration and log configuration.

• Date & time: Settings of the system clock.

• Users: List of logged in users.

• Preferences: Alarm and event logging preferences.

• Configurations: Handling of unit configurations and backup.

• Software: Handling of Operating System (OS) software.

26 • Maintenance Element Manager User’s Manual Nimbra OneSerie

Setting of system parameters

The System page contains system parameters and a control for software restart of the unit.

The configurable parameters are:

Parameter name Description Type Restart and halt of

system

Buttons and text box for halt or soft restart of the system.

Opt

System name

The name of the unit, to be used instead of the IP address, for easier recognition in the web page.

Opt

Contact E.g. the name or the e-mail address

of the contact person for the unit.

Rec

Location Optional description of the location

of the unit.

Rec

Name server

The IP address of the DNS (Domain Name Server) server. Translates the name to an IP-address.

Rec

NTP Server The IP address of the NTP (Network

Timing Protocol) server.

Rec

Event and Alarm log parameters

Settings for the parameters to be logged by the system.

The Event log in the network element should be large enough to hold event for at least a couple of minutes. A rule-of-thumb is 2.5 times the number of expected connections originating or terminating on the node, but not less than 50.

Rec

Type definitions: Man – mandatory, Rec – recommended, Opt – optional

1. Navigate to the Maintenance|System page, Figure 16, will appear.

Figure 16. The Maintenance, System page

2. Enter the System name, the name of the Contact person and the

Location. Enter the address of the NTP Server.

Element Manager User’s Manual Nimbra OneSerie Maintenance • 27

3. If Events should be logged tick the appropriate boxes and enter the Event

and Alarm log size.

4. To make parameters active without leaving the page, click Apply. Any

changes will then be made effective immediately. To return to the Maintenance page, click OK.

Restart the system

Note:

Save the configuration before restarting. Otherwise the parameter changes will be lost! Refer to Configuration handling.

1. Navigate to web page Maintenance|System. The System page, Click on

restart or halt system at the top of page, Figure 17, will appear. Type Restart.

When the system is re-started the contact with the browser is lost. After a short

time, less than a minute, click on the “reload” button in the web browser to connect again.

Figure 17. The Restart page

Date and time setting

This section is intended to set and re-set the internal date and time clock of the unit.

1. Navigate to the Maintenance|Date & Time page, Figure 18, will appear.

28 • Maintenance Element Manager User’s Manual Nimbra OneSerie

Figure 18. Date & time page

2. Enter the revised date and time info in the entry fields.

For the time, use the hh:mm:ss format. To avoid involuntary change of the parameters the Update date & time checkbox must be ticked for any changes to take effect when the OK or Apply button is clicked.

For a further description of terms and parameters found on the Date & Time page, please see Reference chapter, section Date and Time parameters.

Note:

If the internal clock is set to a time or date in the future, all user will automatically be logged out by the system.

Users

The user menu lists the logged in users. Users can be added and the access level can be modified, according to the procedure below.

Add or modify users and access levels

1. Navigate to the Maintenance|Users. The Users page, Figure 18, will

appear.

Figure 19. The User page

2. Click on the Add users. The Users page, Figure 20, will appear.

3. Enter the User name, Access Mode and Passwords.

Click on OK

Figure 20. Date & time page

Preferences

The unit contains one set of preferences for event and alarm presentation for each authorized user controlled through the Preferences page. Here, the

Element Manager User’s Manual Nimbra OneSerie Maintenance • 29

contents and size of the event and alarm log can be configured, according the procedure below.

The configurable parameters are:

Parameter name Description Type Visible events The types of events that the user chooses to

view. The events can be: performance: reset: info: config: debug: Not applicable alarm:

Rec

Visible alarms

The categories of alarms. Acknowledged: The severity acknowledged

indicates that the alarm is taken care of. Warning: The warning severity level indicates

the detection of a potential or impending service affection fault, before any significant effects have been felt.

Major: The major severity level indicates that a service affecting condition has developed and an urgent corrective action is required.

Minor: The Minor severity level indicates the existence of a non-service affecting fault condition and that corrective action should be taken in order to prevent a more serious fault.

Critical: The critical severity level indicates that a service affecting condition has occurred and an immediate corrective action is required.

Rec

Event log size

The number of events to keep in the log and presented for the operator. Note! The log cannot contain more events than set in the Systems page.

Rec

Auto refresh

The refresh interval of the alarm list information.

Rec

Type definitions: Man – mandatory, Rec – recommended, Opt – optional

Note:

The event log can not contain more events than what is set in the System page, Refer to section Setting of system parameters.

30 • Maintenance Element Manager User’s Manual Nimbra OneSerie

1. Click on the Maintenance|Preferences. The Preferences page, Figure 21,

will appear.

Figure 21. Maintenance, Preferences page

2. Enter the desired information for the currently logged in user.

3. Click OK and return to the Maintenance main page.

4. If required, back up the configuration changes. Refer to chapter

Maintenance, section Configuration handling.

Configuration handling

Changes made to the configuration become immediately active, but they are stored in volatile RAM memory. When the unit is powered off, and then powered on again, it reverts to the latest backed up configuration.

In order not to risk losing the configuration when changes have been verified and approved, the configuration should be backed up according to the procedure below.

1. Click on the Maintenance menu item. and then click on Configurations.

The Configurations page, Figure 22, will appear.

Figure 22. Configurations page

The table shows the active and previous configurations stored in the flash memory. The active configuration is at the top of the table. Maximum number of stored configuration for the Nimbra One is 3. To leave room for a new configuration, an older one must be deleted. To delete a configuration, refer to, section Delete a configuration.

Element Manager User’s Manual Nimbra OneSerie Maintenance • 31

The table shows the following information:

• Id: The index number of the configuration.

• Name: A user-defined name of the configuration.

• Description: An optional user-defined description of the configuration.

• Valid: Only a configuration with a Yes in this column can become active

(after restart).

• Date: Date and time when the configuration was saved to flash memory.

Tip:

If Valid is set to “Yes” for more than one configuration the first configuration with set to “Yes” is the current configuration.

The previous configurations are retained in the unit until they are deleted. To make any previous configuration in the list active, set the Valid option to No for the configurations that are above the wanted one in the list and restart.

The term “active” is used for the configuration, among the valid ones, with the lowest index number.

Backing up the current configuration

1. Navigate to the Maintenance|Configurations page according to the

previous section.

2. Click on the Backup current button. The Backup page, Figure 23, will

appear.

Figure 23. Backup configuration

4. Enter a name for the configuration in the Name entry field, and a suitable

description in the Description field. The Valid checkbox must be ticked.

5. Click OK.

A dialogue box pops up, indicating that the operation may take a while, and the Maintenance, Configurations page, Figure 22, will reappear with the new configuration active at the top of table.

Modifying entries in the configuration

Note:

Any changes of a configuration in valid status will occur when the unit is restarted. Only one configuration can be active.

If the active configuration is made inactive or deleted the entire system can be affected on restart, as another configuration will become active.

32 • Maintenance Element Manager User’s Manual Nimbra OneSerie

1. Navigate to the Maintenance|Configurations page according to the

previous section. The Configurations page, Figure 22, will appear.

2. Click on the name of the configuration to be modified in the Name

column. Figure 24, will appear.

Figure 24. Edit page

Information regarding the configuration, such as name, when it was created, a description and the size of it, is shown. The only parameter that can be altered here is whether the configuration should be Valid or not.

3. Click on Download file will download the configuration. A standard save

dialog will appear. Open the file and modify it. To upload the new configuration, please refer to section Uploading configurations.

4. Click OK. The Maintenance|Configurations page, Figure 22, will

appear, reflecting the modification.

Uploading configurations

To upload a prepared configuration file to the unit, use the following procedure:

1. Navigate to the Maintenance|Configurations page according to the

previous section and click on the Upload configuration button. The Upload page, Figure 25, will appear.

Figure 25. Upload configuration page

2. Click on the Browse button. A standard File Open dialogue box appears.

Select the desired filename and click the OK button.

3. The Confirm uploaded configuration page, Figure 26, appears.

Figure 26. Confirmation page

Element Manager User’s Manual Nimbra OneSerie Maintenance • 33

4. Enter an appropriate name and a description for the configuration in the

Name entry field. The Valid checkbox should be ticked.

5. Click the OK button. The Maintenance|Configurations page, Figure 22,

will reappear with the new configuration active at the top of table.

Switching configurations

To make a previous configuration active, the Valid option has to be set to No for the other configurations that are above the wanted one in the list. This is done by following these steps:

1. Enter the Maintenance|Configuration page according to the previous

section. The Maintenance|Configurations page, Figure 22, will appear.

2. Click on the name of the configuration to be modified in the Name

column. The Edit configuration page, Figure 24, will appear.

3. Make the configuration inactive by clearing the Valid checkbox.

4. If necessary, repeat steps 2 and 3 to make other configurations inactive,

then restart.

Deleting configurations

Note:

If the active configuration is deleted the entire system will be affected after that the unit restarts as another configuration will become active.

1. Enter the Maintenance|Configuration page according to the previous

section. The Maintenance|Configurations page, Figure 22, will appear.

2. Click on the name of the configuration to be modified in the Name

column. The Edit configuration page, Figure 24, will appear.

3. To delete the configuration, click on the Delete button. The Maintenance,

Configurations page, Figure 27, will appear.

Figure 27. Delete the configuration

Software maintenance

The Nimbra One can store two alternative images in non-volatile flash memory. One image can be set as primary (present in the volatile RAM memory) and one as secondary (stored in the flash memory). The choice of the primary or secondary image can be selected in the web interface. When the unit is restarted, it reads the primary image from the flash memory.

34 • Maintenance Element Manager User’s Manual Nimbra OneSerie

New versions of the software can also be uploaded, refer to section Uploading images.

Element Manager User’s Manual Nimbra OneSerie Maintenance • 35

1. Click on the Maintenance menu item. Then click on Software. The

Maintenance|Software, Figure 28 will appear.

Figure 28. Maintenance, Software page

The table shows both of the software images stored in the unit. When powering up the unit the primary image is loaded and will appear as running. The following information is shown:

• Image: Displays the images as. The marker shows the image that will boot

next time the unit restarts.

• Name: Shows the name of the image.

• Version: Shows the version of the software.

Uploading images:

If a new image should be uploaded and there’ s already two images, one of them must be deleted, refer to section Deleting images. To upload an image file to the unit, use the following procedure:

1. Click on the Upload image button. A standard File Open dialogue box

appears. Select the desired filename and click on the OK button.

2. The Confirm uploaded image page, Figure 29, appears.

Figure 29. Confirm uploaded image page

3. If the image is to be installed as the active image, tick the Default

checkbox. The recommendation is to not install the image as default instead swap the images after a successful installation of the new image.

Figure 30. Confirm uploaded image page

4. Click OK. The Maintenance|Software page, Figure 28, will reappear

with the new image displayed in the table.

36 • Maintenance Element Manager User’s Manual Nimbra OneSerie

Swap images

1. Click on the Maintenance menu item. Then click on Software. The

Maintenance|Software, Figure 28 will appear.

Figure 31. Maintenance, Software page

The table shows both of the software images stored in the unit. When powering up the unit the primary image is loaded and will appear as running. The following information is shown:

• Image: Displays the images as. The marker shows the image that will boot

next time the unit restarts.

• Name: Shows the name of the image.

• Version: Shows the version of the software.

Swap images:

2. Click on the Swap images button and the images are swapped.

Deleting images

Note:

If the primary image is deleted, the next image (the secondary image) in the flash memory will become the new primary image. Note that the running image will not be affected until the unit is restarted.

1. Enter the Maintenance|Software page according to the previous section.

The Maintenance|Software page will appear.

2. Click on the name of the image to be deleted in the Name column. The

Software Edit page,

3. Figure 32, will appear.

Figure 32. Software Edit page

4. Click on the Delete button. The Maintenance|Software page, Figure 28,

Element Manager User’s Manual Nimbra OneSerie Status Monitoring • 37

Status Monitoring

Overview of status monitoring

This chapter describes how general supervision of status and configuration is performed over the web interface.

The start web page for status monitoring is shown as below.

Figure 33. The start web page for Status

The sub-sections are:

• Alarms: present the alarms in the unit.

• Events: present the events in the node.

• Syslog: presents a log of the system.

• Equipment: lists the installed equipment in the unit.

• Inventory: presents the cards in the node including all the information

about it such as: Art no, Rev and serial number.

• Who: shows the users that are logged in to the unit.

38 • Status Monitoring Element Manager User’s Manual Nimbra OneSerie

Alarms

An alarm is the reporting of a fault or a condition in the system. The alarm is always active or cleared, meaning that an alarm is indicating an actual status. It should always be possible to examine the fault condition, and from this determine whether an alarm exists or not.

Note! The alarm list will present the alarms which are defined under Maintenance|Preferences.

The alarms page

1. Click on the Status|Alarms. The Alarms page, Figure 34, will appear.

Figure 34. Alarms page

The table shows the Active and Cleared alarms in lists and it shows the alarms in the lists as follows.

• Cause:

Indicates the cause of alarm in plain text.

• Sev:

Shows the severity of the alarm. The following values are possible:

Cr Critical (red). The critical severity level indicates that a service affecting condition has occurred and an immediate corrective action is required.

Ma Major (orange). The major severity level indicates that a service affecting condition has developed and an urgent corrective action is required.

Mi Minor (yellow). The Minor severity level indicates the existence of a non-service affecting fault condition and that corrective action should be taken in order to prevent a more serious fault.

Wa Warning (blue). The warning severity level indicates the detection of a potential or impending

Element Manager User’s Manual Nimbra OneSerie Status Monitoring • 39

service affection fault, before any significant effects have been felt.

Information Cl Cleared (green). The cleared severity level

indicates the clearing of one or more previously reported alarms.

• Object

The function in the unit that the event concerns.

• Text:

More detailed text about the alarm.

• Time:

When the alarm was issued.

• Ack:

Shows if the alarm has been acknowledged or not.

For a further description of the different alarms, see the Reference chapter, section Alarms and Events.

Acknowledging an alarm

The alarms remain in the Alarm monitor field at the top of the web page until the alarm has been acknowledged. To acknowledge an alarm, do the following:

1. Enter the Alarms page according to the previous section. Click on the

alarm event to be acknowledged in the Cause column. The Edit page, Figure 35, will appear.

Figure 35. Acknowledge alarm page

This page shows the same information as the alarm list. With the addition of an editable Comment field and an Acknowledged drop-down menu.

2. Enter any desired comment, set the Acknowledged drop-down menu to

Yes and click Apply or OK.

40 • Status Monitoring Element Manager User’s Manual Nimbra OneSerie

3. The Alarms page, Figure 34, appears with Ackn. set to “yes” and the

alarm is no longer shown in the Alarm monitor.

Note:

In some circumstances the cause of the alarm can not be remedied or the alarm should not be acknowledged until later. In this case, use the Comments field to pass on any comment regarding the alarm event.

Events

Note! The event list will present the events which are defined under Maintenance|Preferences.

1. Click on the Status menu item and then click on Events. The Events

page, Figure 36, will appear.

Figure 36. Events page

The table shows the last events logged by the unit, such as configuration changes, alarms and other system related events, as follows:

• Id:

Index number of the event.

• Sev:

Indication of the severity of the event. The following values are possible:

Cr Critical (red). The critical severity level indicates that a service affecting condition has occurred and an immediate corrective action is required.

Ma Major (orange). The major severity level indicates that a service affecting condition has developed and an urgent corrective action is required.

Mi Minor (yellow). The Minor severity level indicates the existence of a non-service affecting fault condition and that corrective action should be taken in order to prevent a more serious fault.

Wa Warning (blue). The warning severity level indicates the detection of a potential or impending

Element Manager User’s Manual Nimbra OneSerie Status Monitoring • 41

service affection fault, before any significant effects have been felt.

Information Cl Cleared (green). The cleared severity level

indicates the clearing of one or more previously reported alarms.

• Object:

The function in the unit that the event concerns.

• Text:

Specification of the event.

• Time:

Shows when the event occurred.

Syslog

The Syslog page lists a log of the system. To access the page, proceed as follows:

1. Click on the Status menu item and then click on Syslog. The Syslog page,

Figure 38, will appear. The syslog in this example is only showing some entries of the log.

Figure 37. The Syslog page

42 • Status Monitoring Element Manager User’s Manual Nimbra OneSerie

Equipment

The Equipment page lists the software drivers and hardware devices installed in the unit. To access the page, proceed as follows:

1. Click on the Status|Equipment. The Equipment page, Figure 38, will

appear.

Figure 38. Equipment page

The following information is shown: Power/Fans

• Temperature states the temp of the unit.

• Fan states, which fan that is operating.

• Power supply states which power supply that is operating.

Installed boards

• Pos states the position of the board in the chassis.

• Name presents the type of board installed.

• Admin shows the administrative status of the board.

• Oper: shows the operational status of the board.

Installed Interfaces

• Name shows the name of the interface.

• MAC address states the MAC address of the interface.

• Oper shows the operational status of the board.

Element Manager User’s Manual Nimbra OneSerie Status Monitoring • 43

Setting the administrative status of an installed board

To set the administrative status to a board proceed as follows:

1. Navigate to the Status|Equipment page and click on the position of one

of the boards. The Edit Board page, Figure 39, will appear.

Figure 39. Edit board page

• Board pos which position (1-8) of the cards in the chassis.

• Administrative status can be set to Up or OFF.

• Operative status shows the operational status of the card.

• Name shows the name of the board.

2. Set the Administrative status to Up/OFF, using the drop-down menu and

click OK. To apply the setting without leaving the Edit board page, click Apply.

The status of the card can be verified in the administrative status and operative status columns of the Status|Equipment page.

Monitoring the installed interfaces

1. Navigate to the Status|Equipment page and click on the index number in

the Name column. The Interface page, Figure 40, will appear.

Figure 40. The interface page

• Id presents the id of the card in the chassi.

44 • Status Monitoring Element Manager User’s Manual Nimbra OneSerie

• Name shows the name of the interface.

• Operational status shows the operational status of the card.

• Board position which position (0-7) of the cards in the chassis.

• Class presents the class e.g. DTM.

• Interface MAC address: A globally unique hardware identifier for this

interface card.

• First available Rx slot shows the first available slot.

• Number of available RX slots shows the number of slots from the

peering node to this node.

• First available Tx slot shows the first available slot.

• Number of available TX slots shows the number of slots available for

transmission on this interface.

2. The page shows the above parameters regarding the installed interface.

Click OK to return to the Equipment page.

Inventory

The Inventory function describes the physical entities installed in the system. A Physical entity or Physical component represents an identifiable physical

resource within a managed system. Typically, physical entities are physical resources e.g. communications ports, backplanes, sensors, daughter-cards, power supplies, software images, and the overall chassis which can be managed.

A Containment tree describes which entities that are contained within another entity. Typically, a board is contained in a board slot (position), which is contained within the chassis. Or, a software image is contained in a software storage position, which is contained on a board. The use of the position entity allows modeling where a resource is absent, i.e. a board slot position may be empty, which is modeled as a position (board slot) that does not contain a board.

In the Inventory table, the Type column describes the type of entity, and the entity containment tree. The entity tree is displayed with the children (i.e. contained entities) of an entity indented relative to the parent. The Properties column describes data about the entity, e.g. the name, revision, article number, etc.

Element Manager User’s Manual Nimbra OneSerie Status Monitoring • 45

To access the Invetory page, proceed as follows: Click on the Status|Inventory. The Inventory page, Figure 41, will appear.

Figure 41. The Inventory page, first part

The top of the Inventory table lists:

Printer friendly format: The format is presented in text-only format. System name: the name of the node. Location: the location of the node. Contact: the contact person. DTM address: the dtm address of the node. The second part of the Inventory page, Figure 42, presents the Type and

Properties of the installed entities. The picture presents the entities and its

relations in a tree structure. Where for instance, which boards that are installed and which software that is running.

46 • Status Monitoring Element Manager User’s Manual Nimbra OneSerie

Figure 42. The Inventory page, second part

For Boards-position on which more than two FW-images could be stored, i.e. Control Module, Gigabit/Fast Ethernet, STM-1 access, for those boards the image that is running will be indicated as follows:

Primary: Image stored as primary Secondary: Image stored as secondary Running: Image that is running could be either the primary or secondary For boards on which only one FW-image could be stored, only the primary

image will be presented and that one is thus the same as the running.

Monitoring the logged in users

This function is used to check if any other users are logged in to the unit over web GUI (Graphical User Interface), to make sure that no other user attempt to configure the unit at the same time.

1. Click on the Status|Who. The Who page, Figure 43, will appear.

Figure 43. The who page

The table shows information about other logged in users, as follows:

• User name lists all the logged in users in the unit.

• Tty shows the type of terminal used.

• From shows the IP address of the logged in users.

• Login shows the time when the user logged in.

• Expire shows the time when the user’ s session will expire.

Element Manager User’s Manual Nimbra OneSerie Control Network • 47

Control Network

General about In-band management

The management network is used for managing the nodes in the Nimbra network. It is used when an operator or application accesses the nodes using e.g. telnet, HTTP or SNMP. The network is also used by some other protocols, such as NTP (Network Time Protocol).

Typically, the type of traffic on a management network is from one of a few management stations located on a network outside the Nimbra network. The management stations accesses the nodes when e.g. provisioning connections, collecting network statistics, or when checking on the status of the nodes. Alarm messages are usually sent from the managed nodes to a limited number of management stations.

When managing the nodes, there is rarely any communication between the nodes. Communication is done with the network management stations, either from a network management system such as Nimbra Vision, or from a web browser or telnet session. This traffic is routed via the gateway. Typically, only a limited number of nodes in the Nimbra network reached are simultaneously from a management station.

Ethernet DLE

DLE (DTM LAN Emulation) emulates a LAN (Local Area Network) as an Ethernet segment on top of Net Insights network. It is implemented using channels through the network. Seen from DLE, each node in the segment has direct connectivity to all other nodes, as on an Ethernet segment. The underlying physical topology of the DTM network is not related to the topology of the segment, e.g. two nodes on the same DLE segment may be located far away from each other.

D T M

Nimbra

DLE

client

DLE

client

DLE

client

DLE

client

DLE

server

DLE

server

DLE Segment 1

DLE Segment 2

Figure 44. Two DLE segments. These can represent one in-band mgmt network using IP routes in order to connect the two segments, or as two independent in-band mgmt networks, where each control part of the network.

48 • Control Network Element Manager User’s Manual Nimbra OneSerie

Note:

Note! that the DLE segment is a logical segment. The physical topology exists only on the DTM level.

IP and routing

Each node that is connected to the DLE segment has, an virtual IP interface assignied, allowing the node to communicate with other nodes on the segment using IP. A gateway routes the IP packets to and from the segment. This means that each segment has its own IP network address. Routing can be to other networks, i.e. DLE segments, or to an out-band IP network.

Routing will load the Control Module CPU of the gateway node. The number of packets that can be routed will therefore be limited by the capacity of the Control Module.

DLE clients

Each virtual Ethernet interface is implemented by the DLE client, one client per virtual interface. When Ethernet packets are sent from one node to another within the segment, the client will establish a channel to the remote node. The remote node would establish a return channel for any reply. This means that from each node, there will be a channel established to every other node in the segment to which packets have been sent. To reduce the number of channels in a segment, channels can be torn down automatically or manually when they are no longer used. It is possible to have multiple clients on a single node, implementing multiple virtual Ethernet interfaces.

Gateway

Figure 45. A DLE segment with channels between DLE clients

In Figure 45, it is assumed that all nodes has communicated via the gateway. So the gateway (A) has channels connected to and from all the nodes. Communications has also occurred between node (E) and (F) resulting in a channels between these two nodes. Channels that are not used has been torn down, hence no channels exists between any other nodes.

Note:

Figure 45, shows the DTM channels. The physical topology is not presented.

Element Manager User’s Manual Nimbra OneSerie Control Network • 49

Client to Server Channels and Server to Client Channels are used for broadcast packets, and for DLE signaling.

Client to Client Channels are used for peer-to-peer communication.

Note:

To change the IP address on the physical interface, refer to the Nimbra Installation and Maintenance Manual, Section Setting Initial Parameters.

DLE server

Each DLE segment has a DLE server. The responsibility of the server is to provide information to the clients about the other nodes in the segment, and thus aid the clients in establishing their connections. Because the client and server must be able to at all time communicate, permanent channels are established between client and the server. One channel is established from each client to the server, and one multicast channel is established from the server to all the clients.

The channels between server and clients are also used when distributing broadcast packets. The broadcast packets from a client are sent to the server, which distributes it to all the other clients on the segment using the multicast channel from the server to the clients. I.e. broadcast packets will not result in establishment of new channels between two clients. Packets are also distributed in the same way if the channel from one client to the other client is not established. Typically, this would be during the period when a channel is being established.

Multiple DLE servers

It is possible to use multiple servers for a single segment. The servers cooperate and allows for redundancy.

At all time, a client is connected to only one server. When multiple servers are used, the servers are interconnected using multicast channels, one in each direction. Client packets that would be sent via the server to other clients are also replicated by the server and sent to the peering servers for distribution to their connected clients.

Setting up a segment with multiple servers, and where sets of clients are connected to different servers implements redundancy between servers.

Multiple servers can be used as alternative servers for the client. For each client, it is possible to configure alternative servers, where the alternative servers must serve the same segment. When a client establishes a channel to a server, it will try the servers in order until successful. If a server would go down, the client establishes a new channel to a server, trying them in order until successful. This implements redundant servers.

Configuration

The management traffic requires only moderate bandwidth. It is therefore adequate to use 512 kbps (equals one DTM slot) per channel. As the DLE

50 • Control Network Element Manager User’s Manual Nimbra OneSerie

client-to-server communication is only used for signaling and broadcasting, 512 kbps is sufficient on these channels as well.

The recommendations in this document are for an in-band management network that is used exclusively for management of the Nimbra nodes. No consideration has been taken for allowing other traffic.

To limit the load on the DLE server, there is a recommended maximum of DLE clients in one segment per server.

To limit the load on the gateway, there is recommended maximum number of nodes that shall have its traffic routed through the gateway.

For availability reasons, when a single DLE server is used, it is recommended that the gateway for a DLE segment is located on the same node as the DLE server.

Nimbra One Nimbra 300 Nimbra 290/291

Maximum recommended number of DLE clients for one DLE server

16 16 16

When working as gateway: maximum recommended number of nodes to route traffic for

255 255 255

Maximum recommended number of DLE clients on a gateway

3 3 2

Table 1. Configuration recommendations of the DLE in-band network used for managing the nodes from external management stations

Nimbra One/300 Nimbra 290/291

Client-to-client channel capacity.

512 kbps (1 slot) 512 kbps (1 slot)

Cannot be configured. Client-to-server channel capacity.

512 kbps (1 slot) 512 kbps (1 slot)

Cannot be configured. Server-to-client channel capacity.

512 kbps (1 slot) 512 kbps (1 slot)

Cannot be configured. Server-to-server channel capacity.

512 kbps (1 slot) Not supported

Time out before tearing down unused channels

Default is infinite, but can be configured

Default is infinite, but

can be configured

Table 2. Communication specifications of the DLE in-band network

Building networks with DLE

When building in-band management networks using DLE, use the recommendations listed in Table 1 and Table 2.

Element Manager User’s Manual Nimbra OneSerie Control Network • 51

Nimbra 290 and 291 only supports 512 kbps channels. Also, Nimbra 290 and 291 do not support multiple servers.

On Nimbra One prior system release GX3.3 only 512 kbps channels are supported. Also, multiple servers are not supported.

For networks larger than the number of nodes that are recommended within one DLE segment, build a tree of segments where intermediate nodes acts as gateways between the segments. Note that the root of the tree will have to route traffic to and from all of nodes to the external network.

Gateway

DLE segment

192.168.100.64/27

External network

192.168.1.0/24

192.168.100.33

DLE segment

192.168.100.00/27

192.168.100.66

DLE segment

192.168.100.32/27

192.168.100.34 …35 …36

…67 …68

192.168.100.1

192.168.100.65

Gateway

…2

…3

192.168.1.1

Figure 46. Example of a network with three DLE segments built as a tree, and one external network

In The DLE segments have a netmask of 255.255.255.224 meaning that there can be 30 nodes on each network (one address is the network, and one is the broadcast address). The gateways route packets between the DLE segments and the external network.

If the Nimbra network consists of more nodes than what is recommended as the maximum for one gateway, it is recommended to split the network into separate in-band management networks and route their traffic to an external network using another node as the gateway. See Figure 47.

Gateway

Tree of nodes

and DLE

segments

Tree of nodes

and DLE

segments

Gateway

External management network

Figure 47. Large networks are divided into smaller networks, each with its gateway to the external management network

52 • Control Network Element Manager User’s Manual Nimbra OneSerie

IP routing

Setting up DLE only configures the individual DLE segments. As with all IP networks, routing must be configured in each node to be able to route the traffic in and out of the DLE segment. Setting up IP routing for a DLE segment is not different from setting up IP routing in general.

A routing entry consists of a destination, a netmask and a gateway. When a packet is sent to a node outside the network, the IP address to the node is masked with the netmask of a route. If the masked IP address matches the destination of the route, the packet is forwarded to the gateway specified in the route. The gateway must be located on the local IP sub-network.

On each node in the DLE segment, a default gateway routing entry should be specified, or routes must be specified to all remote destinations. This is used to determine where to forward packets to nodes outside the DLE segment. The default route is specified as destination 0.0.0.0 with netmask 0.0.0.0. This entry will match all IP addresses. The gateway shall be the IP address of the gateway on the DLE segment.

Node a

Destination: 0.0.0.0 Netmask: 0.0.0.0 Gateway: 192.168.100.33

Node b

Destination: 0.0.0.0 Netmask: 0.0.0.0 Gateway: 192.168.100.1

Destination: 192.168.100.64 Netmask: 255.255.255.224 Gateway: 192.168.100.3

Node c

Destination: 0.0.0.0 Netmask: 0.0.0.0 Gateway: 192.168.1.222

Destination: 192.168.100.32 Netmask: 255.255.255.224 Gateway: 192.168.100.2

Destination: 192.168.100.64 Netmask: 255.255.255.224 Gateway: 192.168.100.3

External node

Destination: 192.168.100.0 Netmask: 255.255.255.0 Gateway: 192.168.1.1

Default route

Default route. The gateway is the node on the external network that acts as gateway to other networks. This might not be any node, in which case this entry does not exist. In this example, it is assumed that the gateway is …222, which is not shown in the figure.

This route is only necessary if you

want to be able to send packets from

network 192.168.100.32 to network

192.168.100.64.

Figure 48. Routing tables for a network as shown in Figure 46

Note:

The node (c) must have two routing entries, in addition to the default route; one to each network (DLE segments).

Element Manager User’s Manual Nimbra OneSerie Control Network • 53

Overview of Control Network

This section describes how to use the web interface to set up IP and SNMP parameters for in- and out-band management. The start web page for Control network is shown in the, Figure 49, below.

Figure 49. The Access web page

The sub-sections are:

• In-band servers presents how to set up the dle servers used in In-band

management.

• In-band clients describes how to create clients used in In-band.

• IP interfaces states the physical and logical address of the interfaces.

• IP routing conf describes how to set the routing parameters.

• IP routing table presents all routing entries in the unit.

• SNMP describes the SNMP (Simple Network Management Protocol)

configurations for the unit.

Setting up In-band servers

DLE servers use one single multicast channel for connecting to all peering DLE servers. Each server is responsible for re-establishing its originating multicast channel in case (parts of) it goes down, after verifying that the peering server still is configured as a peer.

A DLE server must be configured in one of the units of the network, according to the following procedure.

To set up the in-band server, keep the following information at hand:

Parameter name Description Type Administrative

status

To activate the DLE server set the Administrative status in the drop-down menu to Up.

Man

DSTI

Index, DTM service type instance. Should be 32769 when using GX 3.2 or older.

Man

Server - Client connection capacity

The capacity between the server and the client. 0,400 Mbps = 1 slot.

Man

Server - Server connection capacity

The capacity between the servers. 0,400 Mbps = 1 slot.

Man

Type definitions: Man – mandatory, Rec – recommended, Opt – optional

• Advanced

54 • Control Network Element Manager User’s Manual Nimbra OneSerie

Controls the parameters of the exponential back-off algorithm. Controls the reconnect time out.

Minimum interval: 10 ms. The start value of the algorithm. After a tear down of the connection, it will try immediately to re-establish the connection, if it fails it will wait 10 ms and then retry.

Maximum interval: 50000 ms. The end value of the algorithm. The reestablish mechanism will wait not longer then 50000 ms to re-establish a channel.

• Destinations to peering dle servers. DLE servers on the same level, used

for multiple servers for redundancy and load balance.

• Statistics presents statistics of dle servers. Refer to chapter All connections

and section Statistics.

1. Navigate to web page Control Networks|In-band servers and click on

Add server, Figure 50, will appear.

Figure 50. In-band Servers page

2. To activate the DLE server set the Administrative status in the drop-

down menu to Up and enter the DSTI and the capacity of the server to client. Also enter the capacity between server to server. Click Applay and then OK.

Peering DLE Server

3. Click on Destinations, refer to Figure 50, in order to add one or more

destinations.

Element Manager User’s Manual Nimbra OneSerie Control Network • 55

Figure 51. In-band Servers page

Re-connect checked: if secondary path is used it will re-connect to primary. Delete checked: deletes the checked destinations.

4. Click on Add destination.

Figure 52. In-band Servers page

5. Enter Destination DTM node address, Destination DSTI and select if

sourse routes should be used. Click on OK.

6. Add the servers in the peering nodes.

Setting up In-band clients

An In-band client must be configured on every node in the segment, including the nodes with the In-band server.

To set up the in-band management, keep the following information at hand:

Parameter name Description Type DSTI Index, DTM service type instance. Man Client - Client

connection capacity

The capacity between the clients. Man

Tear down unused channels after

Channels are torn down when they are no longer used. The times in seconds before the channels are torn down.

0 sec = channels are never torn down 600 sec = 10 minutes which is recommended

Man

Server DTM node

The DTM host name or the address of the DLE server.

Man

Server DSTI Index of the server. DTM Service Type Instance. Man

56 • Control Network Element Manager User’s Manual Nimbra OneSerie

Alternative server DTM node

DTM address to the secondary server node. Opt

Alternative server DSTI

Index of the server. DTM Service Type Instance. DSTI of server node.

Opt

Client to Server connection capacity

The capacity between the server and the client. 0,400 Mbps = 1 slot.

Man

Type definitions: Man – mandatory, Rec – recommended, Opt – optional

• Advanced refer to section Setting up In-band servers.

• Statistics presents statistics of all dle clients. Refer to chapter All

connections and section Statistics.

Setting up the In-band client

1. Navigate to Control Networks|In band Clients web page, and click on

the Add client button. The Edit page, Figure 53, will appear.

Figure 53. Edit client page

Element Manager User’s Manual Nimbra OneSerie Control Network • 57

2. Set the Administrative status drop-down menu to Up.

3. Enter the values of the client and the server in the fields.

4. Click OK.

Note:

It may take several seconds before the page reloads with Operational status Up. This is due to the communication time between server and client.

IP interfaces

IP interface menu presents the physical and logical Ethernet address of the interface. This section describes how to change the address of the physical and logical Ethernet interface and also how to change the netmask of the subnet.

Navigate to Control Networks|IP interfaces web page, Figure 54, will appear.

Figure 54. IP interfaces page

eth0: The physical address of the Ethernet interface. dlec0: The logical address of the Ethernet interface.

1. Click on the Id of the interface that should be changed, Figure 55, will

appear.

Figure 55. IP address page

2. Click on the IP address and make the changes to the address and the

netmask. Or click on Add address... in order to add a n IP-address.

3. Click OK.

IP routing conf

Generic IP services may need to be configured. This is described below.

58 • Control Network Element Manager User’s Manual Nimbra OneSerie

Routes

In order to enable routing outside an In-band segment, routes have to be configured. Some default routes are always configured in a node, e.g. to the subnet of a configured Ethernet interface, and to the loopback interface.

Note:

An IP route must be configured on every node in the DLE segment. It will tell the node where to send IP traffic to a node outside the DLE segment.

Make sure to have at hand all the information that the operation requires.

Click on the Control Networks|IP routing table an overview of the IP routes are listed.

U means that the routing entry is up, in other words active. G means that in order to reach the destination you should use the gateway that

is “pointed out” by the routing entry. Example:

sw042:/flash/root # netstat -rn Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface

192.168.103.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0

192.168.148.0 0.0.0.0 255.255.254.0 U 0 0 0 dlec1

127.0.0.0 127.0.0.1 255.0.0.0 UG 0 0 0 lo

0.0.0.0 192.168.103.1 0.0.0.0 UG 0 0 0 eth0

The first entry says that you can reach 192.168.103.0/24 directly, without passing a gateway (no “G”). The same counts for the second entry. The third entry is for a local host, that entry will always be there. The fourth entry says that all the other nodes (0.0.0.0/0) could be reached via the gateway

192.168.103.1.

Setting up IP routes

The configurable parameters for a route are:

Parameter name

Description Type

Destination

The destination IP network that the route will use.

Enter Default for a default (0.0.0.0) route.

Man

Netmask

The network mask to apply for the destination network. E.g. netmask 255.255.255.0

Man

Gateway

The IP address of the node that is connected to the other network.

Man

Element Manager User’s Manual Nimbra OneSerie Control Network • 59

Type definitions: Man – mandatory, Rec – recommended, Opt – optional

1. Click on the Control Networks|IP Routing Conf. The Routing conf.

page, Figure 56, will appear. This page contains the configured routes on the subject node.

Figure 56. IP routing configuration page

2. Click on the Add route button, the Add page, Figure 57, will appear.

Figure 57. Add IP route

3. Set the Administrative status to Up and enter the Destination IP address

and the Netmask.

4. Enter the IP address of the Gateway.

5. Click OK. The Routing configuration page will appear, with the new

route in the table.

Verifying and reconfiguring an IP route

To verify and reconfigure an IP route, follow the steps below:

1. Navigate to web page Control Networks|IP Routing conf. and click on

the route to be verified or reconfigured. The Edit page, Figure 58, will appear.

Figure 58. Edit IP route

2. Set the Administrative status drop-down menu to Up. Enter new values

in the different fields.

60 • Control Network Element Manager User’s Manual Nimbra OneSerie

3. Click Ok. The Routing configuration page, Figure 56, will appear, with

the changes made to the route reflected in the table.

4. If required, back up the configuration changes to the. Refer to chapter

Maintenance, section Configuration handling.

Note that assymetric routing may cause problem with snmp/telnet/ftp.

Deleting an IP route

To delete an IP route, follow the steps below:

1. Enter the Control Networks|IP Routing conf|Edit page according to the

previous section.

2. Click on the route to be deleted. The Edit IP Route page, Figure 58, will

appear.

3. Click on the Delete button.

4. The Control Networks|IP Routing conf page will reappear without the

removed IP route.

SNMP configuration

This chapter describes the SNMP (Simple Network Management Protocol) configuration for the network element. It describes setting up of community names, SNMPv3 user, and notification receivers.

1. Click on the Control Networks menu item. Then click on SNMP. The

SNMP configuration page, Figure 59, will appear.

Figure 59. SNMP configuration page

Element Manager User’s Manual Nimbra OneSerie Control Network • 61

The page shows information about the SNMP community names and user configuration. The SNMP agent is a full SNMPv1/v2c/v3 agent that supports SNMPv3 security levels noAuthNoPriv, authNoPriv and authPriv. It also shows the configured notification receivers.

• Read-only community name is the community name for SNMPv1/v2c

read (i.e. get) operations. If set, then get operations using this community is accepted, while write (i.e. set) operations are not accepted using this community.

• Read-write community name is the community name for SNMPv1/v2c

read (i.e. get) and write (i.e. set) operations. If set, then SNMPv1/v2c read and write operations using this community are accepted.

• Notification (trap) community name is the community used when

sending notification. If set, notifications are sent as SNMPv2 traps with this community.

• SNMPv3 user is a user name used in SNMPv3 communication with the

node. If set, SNMPv3 operations using this USM user are accepted using a security level that depends on the Authentication key and the Privacy key, as described below.

• Authentication key is the passphrase used for SNMPv3 authentication of

the SNMPv3 user. If empty, then the authentication check is disabled, e.g. security level is noAuthNoPriv. If set, but the Privacy key (see below) is not set, then only authentication check is done, e.g. security level is authNoPriv, If set, and the Privacy key is set, then authentication check is done, and the data is encrypted, e.g. security level is authPriv.

If authentication check is disabled, then the user has read-only permission, just as if using SNMPv1/v2c with the Read-only community name. If authentication check is enabled, then the user has read and write permission, just as if using SNMPv1/v2c with the Read-write community name.

• Privacy key is the passphrase used for SNMPv3 encryption. If set,

SNMPv3 operations are also encrypted, e.g. security level is authPriv. To use encryption, then the Authentication key must also be set.

The page also shows information about the SNMP notification receiver configuration as follows. A notification receiver is the management station that will process notifications (SNMP traps) sent from the network elements. You may send notifications for multiple management stations.

• IP address shows the IP addresses of the configured SNMP notification

receivers (management station).

• UDP port number shows the UDP (user data protocol) port number for

the notification receivers, normally 162, which is the standard port.

The link Access control configurations opens a page that allows for advanced configuration of the SNMP agent, including setting up of detailed access control.

The link MIB specifications opens window from where it is possible to download the Net Insight enterprise MIB specifications supported by the network element.

62 • Control Network Element Manager User’s Manual Nimbra OneSerie

Adding a SNMP notification receiver

1. Navigate to the Control Networks|SNMP page and click on the button

Add SNMP notification receiver. The Add SNMP notification receiver

page, Figure 60, will appear.

Figure 60. Add SNMP notification page

The web page shows information as follows:

• IP address: The IP address of the configured SNMP notification receiver

(management station).

• UDP port number: The UDP (user data protocol) port number for the

notification receivers. The standard port number is 162.

2. Add the IP address and UDP port number for the management station.

3. Click OK to add the new notification receiver. The Control

Networks|SNMP configuration page will be loaded updated with the new notification receiver.

Editing or deleting a SNMP notification receiver

1. Navigate to the Control Networks|SNMP page and click on the IP

address of the notification receiver that should be edited or deleted. The SNMP notification receiver page, Figure 61, will appear.

Figure 61. Edit SNMP notification page

2. On this page, the IP address and UDP port number can be changed. To

change the values, edit the IP address and UDP port number for the management station. The change will be effectuated when the OK or Apply button is clicked.

3. To delete the notification receiver, click the Delete button. The Control

Networks|SNMP page will be loaded with the notification receiver removed.

Element Manager User’s Manual Nimbra OneSerie Control Network • 63

Access control and Advanced setup

Advanced configuration of the SNMP agent is done using the Access control configurations page. Using this page requires good knowledge of SNMP agent

configuration as specified in relevant RFC’ s. Generally, this page is used for setting up the Local Configuration Datastore

(LCD) of the SNMP agent. The LCD describes the configuration of the SNMP agent. All of the SNMP agent configuration can be done using this page. But because the most common configuration of the agent is the setting of community names, the SNMPv3 user, and the notification receivers, the setting up of that data is preferably done using the SNMP page instead. However, the configuration done on the SNMP page is internally processed as if entered directly into the LCD.

Please refer to section SNMP page internal data below for a description on how the form on the SNMP page is internally represented and related to the LCD.

Please refer to section Access control and Advanced setup below for a description of the format on the LCD.

The default configuration of the LCD adds configurations to the SNMP agent which are used by the community names, SNMPv3 user, and the notification receivers configured on the SNMP page. Modifications and additions to the configuration can be done here.

The following is the default configuration:

• Access entries for the notifiers, readers, writers, authUsers and privUsers

principals that are configured using the SNMP page. These define the permissions for the different principals. You can modify these entries to change the permissions of these community names and SNMPv3 users.

• A view family tree All that includes all the OID’s. This is used when

setting up the access entries.

• Entries that define how notifications (traps) are sent.

The configuration is done using entries in a text box. To edit the SNMP agent configuration:

1. Navigate to The Control Networks|SNMP and select the link Access

control configuration. The Access control configurations page, Figure 62, will appear.

64 • Control Network Element Manager User’s Manual Nimbra OneSerie

Figure 62. Access control configurations page

2. Modify the configuration in the Local Configuration Datastore text box.

The button Restore to defaults loads the default configuration into the text box.

3. To apply a new configuration, click the Apply (or OK) button.

4. When the configuration is applied, it will pass a syntax control. If the

configuration contains syntax errors, the page will be reloaded with errors shown.

The link AuthKey Generator opens a window where an authentication key or privacy key can be encoded for use in the LCD.

SNMP page internal data

Setting up data on the SNMP page is equivalent to setting up data on the Access control configuration page. This section describes how the equivalent

setup on this page corresponds to the form on the SNMP page. Note that the entries here assumes at least the default configuration in the LCD,

as the definitions in the LCD are referred to from the internal entries. Setting of a Read-only community name with the value public on the SNMP

page is equivalent to:

snmpCommunityEntry 1 public standardReader localSnmpID \

- - nonvolatile vacmSecurityToGroupEntry snmpv1 standardReader readers nonvolatile vacmSecurityToGroupEntry snmpv2c standardReader readers nonVolatile

Setting of Read-write community name with the value private on the SNMP page is equivalent to:

Element Manager User’s Manual Nimbra OneSerie Control Network • 65

snmpCommunityEntry 2 private standardWriter localSnmpID \

- - nonvolatile vacmSecurityToGroupEntry snmpv1 standardWriter writers nonvolatile vacmSecurityToGroupEntry snmpv2c standardWriter writers nonVolatile

Setting of Notification community name with the value public on the SNMP page is equivalent to:

snmpCommunityEntry 3 public standardNotifier localSnmpID \

- - nonvolatile vacmSecurityToGroupEntry snmpv2c standardNotifier \ notifiers nonVolatile

Setting of SNMPv3 user name, authentication key and privacy key on the SNMP page is equivalent to one of the following entries, depending on the entered data. When entering user name root only:

usmUserEntry localSnmpID root usmNoAuthProtocol \ usmNoPrivProtocol nonVolatile - - vacmSecurityToGroupEntry usm root readers nonVolatile

or, when entering authentication key public:

usmUserEntry localSnmpID root usmHMACMD5AuthProtocol \ usmNoPrivProtocol nonVolatile - public vacmSecurityToGroupEntry usm root authUsers nonVolatile

or, when also entering privacy key secret:

usmUserEntry localSnmpID root usmHMACMD5AuthProtocol \ usmDESPrivProtocol nonVolatile - public secret vacmSecurityToGroupEntry usm root privUsers nonVolatile

Setting of Notification receiver with IP address 192.168.0.1 and port 162 adds the following per added notification receiver. The index will always be an integer value unique per entry.

snmpTargetAddrEntry index snmpUDPDomain 192.168.0.1:162 1500 3 \ standardTrapSink standardParams nonVolatile 255.255.255.255:0 2048

Format of SNMP configuration

The Local Configuration Datastore (LCD) is represented by a text format, where each line represents an entry. Actually, an entry in the LCD is representing an entry in an SNMP table. The different field for an entry represents columnar objects in the tables. The format of an entry is in general:

keyword value… The keyword represents the type of entry, and the value is a list of fields in the

entry separated by spaces. The keyword is actually describing what SNMP table to configure, and the field values are the columnar objects.

Entries may span multiple lines by using a backslash (\) at the end of the entry's lines.

White-space is ignored.

66 • Control Network Element Manager User’s Manual Nimbra OneSerie

String values that contains white space must be delimited by quotation marks (").

A line is considered a comment and ignored if it starts with a hash (#). Some fields shall have an OBJECT IDENTIFIER as the value. An OBJECT

IDENTIFIER is the complete OID from the root or the MIB tree, written as numbers separated by dots. E.g. an OBJECT IDENTIFIER for the sysName object defined in the MIB-2 systems group would be 1.3.6.1.2.1.1.5.

If the OBJECT IDENTIFIER is not part of an enterprise specific object, the OBJECT IDENTIFIER may be substituted by its name. The sysName object would thus be sysName. It is possible to start the OBJECT IDENTIFIER with a substituted name, and continue with the remaining fields. The sysName could be written as system.5 because system represents 1.3.6.1.2.1.1, or as mib-

2.1.5. Similar, all the enterprise MIB objects can start with enterprises,

as this represents 1.3.6.1.4.1. The following entry keywords are supported. For full description on the

meaning of the entry, please refer to the description in the corresponding RFC.

Keyword See also

snmpCommunityEntry RFC3584 usmUserEntry RFC3414 vacmViewTreeFamilyEntry RFC3415 vacmAccessEntry RFC3415 vacmSecurityToGroupEntry RFC3415 snmpNotifyEntry RFC3413 snmpTargetAddrEntry RFC3413 snmpTargetParamsEntry RFC3413 snmpNotifyFilterEntry RFC3413 snmpNotifyFilterProfileEntry RFC3413

Table 3. SNMP table entries as keywords

Configuration Procedure

The configuration procedure involves the following steps:

1. Define an SNMPv3 user or community.

2. Define a family of view sub-trees, MIB views. The MIB view defines a set

of managed information that may be accessed.

3. Define a group and its associated access rights. The group is assigned the

MIB views for read, write and notification access.

4. Assign SNMPv3 user or SNMPv1/v2c community names to the group. The associations between the MIB views, the groups and the principals

(users/community names) are shown in the figure below.

Element Manager User’s Manual Nimbra OneSerie Control Network • 67

vacmGroupName (group)

vacmGroupName (name)

vacmAccessReadViewName… (read/write/notify)

vacmViewTreeFamilyViewName (name)

vacmSecurityName (principal)

usmUserName (name)

user

usmUserEntry

group

vacmAccessEntry

MIB view

vacmViewTreeFamilyEntry

user



group

vacmSecurityToGroupEntry

community name

snmpCommunityEntry

snmpCommunitySecurityName (name)

vacmSecurityName (principal)

or -

Figure 63. MIB views, groups and users or community names

Defining SNMPv3 Users

At least one SNMPv3 user must be configured for the SNMP agent to send and receive SNMP messages using the SNMPv3 protocol. (SNMPv1 and SNMPv2c do not have users. Instead they have community names, see section Defining Community.) The preferred way to define a user is to use the SNMP page.

A user is defined in the User-based Security Model, USM. Note that an USM user is not the same as the element manager users used for

the CLI or web access of the Nimbra network element. Hence, the users defined for the element manager is not known by the SNMP agent, and the element manger does not know about the USM users.

A user entry is represented by the tag usmUserEntry. The format of the entry is:

usmUserEntry engineID name authProtocol privProtocol storage target authKey

68 • Control Network Element Manager User’s Manual Nimbra OneSerie

engineID is always localSnmpID, which represents the SNMP agent’s administratively-unique identifier.

name is the user name, as a human readable string of up to 32 characters. authProtocol is the authentication protocol which must be used when sending

and receiving messages for this user. The authentication protocol is used to authenticate the user. The value is usmNoAuthProtocol if no authentication protocol shall be used, usmHMACMD5AuthProtocol if HMAC-MD5 protocol shall be used, or usmHMACSHAAuthProtocol if HMAC-SHA shall be used. (This value is actually an OBJECT IDENTIFIER that represents the authentication protocol.)

privProtocol is the privacy protocol which must be used when sending and receiving messages for this user. The privacy protects the messages from disclosure. The value is usmNoPrivProtocol if no privacy protocol shall be used, or usmNDESPrivProtocol if CBC-DES shall be used. (This value is actually an OBJECT IDENTIFIER that represents the privacy protocol.)

storage describes how the entry is stored. This is always nonVolatile. target is always a dash (-). authKey is the user’s authentication password. If no authentication protocol is

used, the value shall be a dash (-). (The password is converted to a key at runtime.) The password can be given in clear text , or as an encrypted string. To encrypt the password, use the Auth Key Generator on the Edit Access Control page, see Figure 62.

Defining Community

At least one SNMPv2 community must be defined for the SNMP agent to send and receive SNMP messages using the SNMPv1/v2c protocols. The preferred method to define community names is using the SNMP page.

snmpCommunityEntry index community name engineID conext target \ storageType

index is a unique index string. It does not mean anything, but must be unique. community is the community name string that will be used. name is the name of this entry, and will be used as the principal to refer to the

entry when setting up the security, see Defining Groups and Access Rights. engineID is always localSnmpID, which represents the SNMP agent’s

administratively-unique identifier. context is the name of the context to which the group is part of. To gain access

by this entry, the specified context must be in use. On the Nimbra network elements, the context is always the default context, which is represented by a dash (-).

target is always a dash (-). storage describes how the entry is stored. This is always nonVolatile.

Defining MIB Views

A family of view sub-trees is a definition that includes or excludes managed information forms a MIB view. A MIB view is used for defining a set of managed information that may be accessed. The definition of the family view of sub-trees may include wildcards. If no wildcards are used, the family of view sub-trees becomes a single sub-tree.

Element Manager User’s Manual Nimbra OneSerie Control Network • 69

If there are multiple sub-trees defined, then the one with most sub-identifies in its OID is used. If multiple sub-trees are defined with the same number of subidentifiers, then the lexographically greatest is used.

A MIB view represented by one or multiple. An entry is represented by the tag

vacmViewTreeFamilyEntry. The format of the entry is:

vacmViewTreeFamilyEntry name subtree

mask type storageType

name is the human readable name for a family of view sub-trees, i.e. the name for the MIB view. This is a printable string of no more than 32 characters. Multiple entries may define one MIB view, which in this case all must have the same name. The name is used when defining groups (see Defining Groups and

Access Rights). subtree is an OBJECT IDENTIFIER that identifies a sub-tree of the MIB, i.e.

what managed objects to include or exclude from the MIB view. The sub-tree is combined with the mask.

mask is a bit mask which, in combination with the subtree defines a family of view sub-trees. The bit mask is represented as a sequence of hexadecimal bytes separated by colons. Each byte is within the range 0x00 to 0xff. A zero-length string is represented by a dash (-).

The bit mask is a series of zeros and ones, where the zeros represent wildcards, and the ones represent an exact match. The bit mask is applied on the subtree, where the first bit masks the first sub-identifier, and so on. The bits are grouped to bytes, which are represented by the substring 00 through ff, and are all

separated by colons (:). The last byte is padded with ones at the end to fill out to a complete byte.

type indicates whether the entry shall define a family of sub-trees that shall be included or excluded from the MIB view. The value of this field is included or excluded.

storageType describes how the entry is stored. This is always nonVolatile.

Example 1

The example defines a view names "All" that allows access to everything (actually, everything under the 1 branch in the MIB tree).

vacmViewTreeFamilyEntry All iso - included nonvolatile

Example 2

The example defines a view named "noIfTable", that allows access to everything except to the ifTable.

vacmViewTreeFamilyEntry noIfTable iso - included nonvolatile vacmViewTreeFamilyEntry noIfTable 1.3.6.1.2.1.2.2 - exluded \ nonVolatile

Example 3

The example shows how to define a family of view subtrees that only allows access to row 9 in the ifTable. The 10th bit is a zero, which makes the 10th subidentifier in the subtree a wildcard (don’t care). This is the columnar object.

Byte 1 Byte 2

full subtree (OID)

1.3.6.1.2.1.2.2.1.0.9

subtree (OID)

1.3.6.1 2.1.2.2 1.0.9

mask

1111 1111 101

70 • Control Network Element Manager User’s Manual Nimbra OneSerie

padded mask

1111 1111 1011 1111

mask in hexadecimal

0xff 0xbf

mask as value

ff:bf

vacmViewTreeFamilyEntry if9 1.3.6.1.2.1.2.2.1.0.9 ff:bf included nonVolatile

Defining Groups and Access Rights

A group is a associating the MIB views with access rights. A group is represented by one or multiple entries, for different accesses. An entry is represented by the tag vacmGroupName.

vacmAccessEntry name prefix

model level match read write notify

storageType

name is the name of the group. The name is a string of up to 32 characters. The is used when associating access rights to users (see Assigning Users).

prefix is the name of the context to which the group is part of. To gain access by this entry, the specified context must be in use. On the Nimbra network elements, the context is always the default context, which is represented by a dash (-). (The prefix could be the complete name of the context, or the prefix of a context, as defined by match, see below.)

model is the security model to which the group belongs. In order to gain access by this entry, the specified security model must be in use. The security model can be snmpv1, snmpv2c or usm for SNMPv3 using the USM.

level is the minimal security level. In order to gain access by this entry, the security level in use must at least be the specified security level. The value is

noAuthNoPriv if no authentication shall be required, and authNoPriv if

authentication using HMAC-MD5 is required. If multiple entries are equally indexed, except for this value, then the one with the highest security level is applied.

match specifies how the prefix shall be matched. For the Nimbra network elements, it does not make sense to set the value to anything except exact. The value can be exact of prefix.

read is the name of the MIB view (see Defining MIB Views) that shall be used to control what management information can be read. In order to gain read access by this entry, the MIB view must allow access of the management information.

write is the name of the MIB view (see Defining MIB Views) that shall be used to control what management information can be written. In order to gain write access by this entry, the MIB view must allow access of the management information.

notify is the name of the MIB view (see Defining MIB Views) that shall be used to control what management information can be included in a notification. In order to gain read access for notifications by this entry, the MIB view must allow access of the management information.

storageType describes how the entry is stored. This is always nonVolatile.

Example

vacmAccessEntry FullAccessUser - usm authNoPriv exact All All All onVolatile

Element Manager User’s Manual Nimbra OneSerie Control Network • 71

The example defines a group named "FullAccessUser" that requires the user to have at least the security level "authNoPriv" (authenticated, but not encrypted). The group permits access to the MIB view "All" for read (responding to snmpget operations), write (accept snmp-set operationrs) and for notifications.

Assigning Users

A user must be associated with a group, where the group defines the access rights for the user. For SNMPv1 and SNMPv2c, which do not have the user concept, the community name is used instead.

An entry maps a security model and its user or community name to a group. An entry is represented by the tag vacmSecurityToGroupEntry.

vacmSecurityToGroupEntry model principal

group storage

model defines if the security model for the entry. The model is snmpv1,

snmpv2c or usm.

principal is the user name for the security model USM (see Defining SNMPv3 Users), or the security name that represents the community name for

SNMPv1/v2c. A default security name is public. The community name for the public security name is modified from the web page Status | SNMP config.

group is the name of the group (see Defining Groups and Access Rights) to which the user or community name shall be associated.

storage describes how the entry is stored. This is always nonVolatile.

Example 1

The example associates the USM user "root" with the group "FullAccessUser".

vacmSecurityToGroupEntry usm root FullAccessUser nonVolatile

Example 2

The example associates the community name "public" for SNMPv2 access to the group "ReadOnlyUser".

vacmSecurityToGroupEntry snmpv2c public ReadOnlyUser nonvolatile

72 • DTM Configuration Element Manager User’s Manual Nimbra OneSerie

DTM Configuration

Overview of DTM configuration

This chapter describes how to use the web interface to configure monitor the DTM-layer. The start web page for DTM is shown in the, Figure 64, below.

Figure 64. The start web page for DTM

The sub-sections are:

• Interfaces: monitor the state of the DTM interfaces and configure the

interfaces present in the unit.

• Addresses: configure the DTM addresses of the unit.

• Host names: configure mapping between the host names and the DTM

addresses.

• Links: show the state of the DTM links to other units. The page can be

used to check if the links to the surrounding nodes have been properly established.

• Routing: monitors and configures the DTM routing.

• Sync: monitor the synchronization status of the node and modify the

external clock.

Note:

Make sure to have all the information that the operation requires, before starting any configuration operationThis will help you to minimize any downtime of the system.

Element Manager User’s Manual Nimbra OneSerie DTM Configuration • 73

Interfaces

The start web page for Interfaces, is presented in Figure 65.

Figure 65. DTM interfaces page

The table lists the DTM interfaces that are present in the unit. For each interface the following is presented:

Name presents the name of the interface. The interface name, written as

“dtmX:Y”, where X is position of the card and Y position of the port, on the card.

Capacity presents the total number of slots, which can be used. Free shows the number of unused for transmit slots. TX slots show the used slots i.e. from this node to the peering node. TX capacity % column indicates the percentage of used slots in the transmit

direction. Each block is shown both as numbers and as a bar graph, representing increments of 10%.

RX slots show the used slots for receive. The RX capacity % column indicates the percentage of used slots for receive.

Each block is shown both as numbers and as a bar graph, representing increments of 10%.

Editing a DTM interface

Access the DTM|Interfaces page. In the interface table, click on the Id of the interface that should be edited. The Edit page, Figure 66, will appear.

74 • DTM Configuration Element Manager User’s Manual Nimbra OneSerie

Figure 66. DTM Interface, Edit page

The configurable parameters are:

Parameter name

Description Type

Admin. status The admin. status of the board. Man Toggle Admin The Toggle Admin option automatically sets the

Administrative status to Down momentarily and then to Up again.

Opt

Metric for dynamic routing

The cost of using this interface when dynamic routing is used.

Man

Enable

Mark Enable, if dynamic routing should be used.

Man

Type definitions: Man – mandatory, Rec – recommended, Opt – optional

Read-only parameters are:

Parameter name

Description Type

Interface name The interface id, written as “dtmX:Y” (where X is

position of the card and Y position of the port).

Readonly

Oper. status The operational status of the board.

Readonly

Transmit capacity

The total number of time slots available for transmission on this interface.

Readonly

Used TX capacity

The number of used time slots from this node to the peering node.

Readonly

Used RX capacity

The number of used time slots from the peering node to this node.

Readonly

Interface MAC address

A globally unique hardware identifier for this interface card.

Readonly

Failure on underlying interface alarm

An error reported by the underlying trunk interface. (LOF loss of frame.)

Readonly

Reduced control capacity alarm

The node is not able to signal the remote node. This usually indicates a problem in the TX direction for the link.

Readonly

Element Manager User’s Manual Nimbra OneSerie DTM Configuration • 75

Adding a new DTM interface

It is possible to configure an interface that is currently not present in the unit. This is done for example when pre-configuring an interface that will be added to the unit later.

1. To add a DTM interface, access the DTM|Interfaces page. Click on the

Add interface link. The Add page, Figure 67, will appear.

Figure 67. Add DTM interface

See the Edit Interface in previous section for definitions.

2. Enter the Interface name, for the new interface, set the Admin status to

Up in the drop down list.

3. Enter 1 for the Control channel capacity.

4. Click OK.

5. The DTM|Interfaces page will reappear with the new interface listed.

6. If required, back up the configuration changes; refer to chapter

Maintenance, section Configuration handling.

Addresses

This chapter describes how to configure the DTM addresses of the unit. The DTM address must be configured before any configuration of services can be done!

Each node can have one primary DTM address and several alias addresses. The

primary address (marked with a symbol in the “ Primary address” column), in the table below, is always used as the source address when the node establishes a channel. In addition to the primary address a node also accepts channels to all its alias addresses.

The address “ 00.00.00.00.00.00.00.01” is a loop back address that all nodes listens to. It is equivalent to the address 127.0.0.1 in an IP-node.

1. Click on the DTM menu item and then click on Addresses. The

Addresses page, Figure 68, will appear.

Figure 68. DTM address page

76 • DTM Configuration Element Manager User’s Manual Nimbra OneSerie

The table shows information of the configured addresses as follows:

• DTM address: The configured DTM address for the unit and one

loopback (always 00.00.00.00.00.00.00.01) address to the back plane.

• Primary address: Shows which address is the primary address for the

node. Note that a node can only have one primary address.

Adding a DTM address

1. Navigate to the DTM|Addresses page and click on the Add address

button. The Add page, Figure 69, will appear.

Figure 69. Add DTM address page

2. Enter the DTM address and whether the address is Primary or not and

click OK. The DTM addresses page will reappear with the new address listed in the table.

3. Back up the configuration changes; refer to chapter Maintenance, section

Configuration handling, and then restart the node; refer to chapter Maintenance section System.

Editing or deleting a DTM address

1. Navigate to the DTM|Addresses page and click on the address that is to

be revised or deleted. The Edit page, Figure 70, will appear.

Figure 70. Edit DTM address page

2. Change the parameters as desired and click Apply or OK.

Note! If the primary address of the node is changed, the configuration must be saved and the node must be restarted for the changes to take effect. Note also that address changes will not affect existing channels.

Host names

Nodes in a DTM network can be assigned names using the host names function. Host names are configured locally in each node and used as alias for a DTM address.

Element Manager User’s Manual Nimbra OneSerie DTM Configuration • 77

From the DTM main page, click on Host names. The Host names page, Figure 71, will appear.

Figure 71. Host names page

The Host names table shows the DTM hosts, as follows:

• DTM address: The DTM address of the node.

• Primary hostname: The primary name for the host.

Remember to include the list of the host names in every node, all the nodes in the network must know all the host names!

Adding a host

1. Navigate to the DTM|Host names page and click on the Add Entry

button. The Add page, Figure 72, will appear.

Figure 72. Add DTM host names page

2. Enter the desired DTM address and the Host names for that address.

Click OK. The DTM, Hosts names page will reappear with the address and host name added.

It is possible, but not recommended to specify several names per address, by entering each name on separate lines. Only the name on the first line will be shown on the hostname page, use several entries with the same DTM address instead.

78 • DTM Configuration Element Manager User’s Manual Nimbra OneSerie

Editing or deleting host names

1. Navigate to the DTM|Host names page and click on the address for the

host to be edited or deleted. The Edit DTM Host names page, Figure 73, will appear.

Figure 73. Editing DTM host names

1. Change the parameters as desired and click Apply or OK.

2. To delete a host, click the Delete button. The DTM|Host names page will

reappear with the host removed from the table.

Note:

The changes to a hostname will not affect channels that have already been established. The hostname table is only consulted when a channel is established.

Links

The Links page shows the DTM links that the node is connected to. The page can be used to check if links to surrounding nodes have been properly

established. For each link id there should be two addresses; it’s own node address and one address to the remote node.

The link-table lists all the links that this node is attached to along with all other nodes that are attached to these links. Each line in the table represents an interface and the node that the interface is located in.

Each link starts with an id, which is equal to the id of a local interface. It lists the other interface connected to that link before starting a new link with a new id.

Element Manager User’s Manual Nimbra OneSerie DTM Configuration • 79

1. Click on the DTM menu item. Then click on Links. The Links page,

Figure 74, will appear.

Figure 74. DTM links page

• Id: The local interface that is connected to the link.

• Type: Displays the type of links. “ looped” indicates a point-to-point link

and “open” indicates some type of link failure.

• I/F MAC addr: Lists the MAC address of the interface. The top one is the

local interface and the one below is to the remote node.

• Node MAC addr: Lists the MAC addresses of all nodes connected to the

link. The top one is the local node MAC and the one below is the interface in the remote node.

• Node addr: Shows the node address of all nodes connected to the link.

The top one is the local node address and the one below is the remote node.

In, Figure 74, a link is formed from the local interface dtm2:1 with interface MAC-address 00:10:5B:00:04:B5 to node iov065 and the interface MACaddress 00:10:5B:00:04:B8 and then back to the local interface dtm2:1, i.e. looped.

In, Figure 74, at the bottom of the list the type is open. This indicates some type of link failure, e.g. that the remote node is down.

Routes

General

To establish channels in a network, the switches must know where to find all other nodes in the network. The process of finding a path from node A to B in the network is called routing.

Routing in a network has a lot in common with routing in an IP network, Figure 75, lists the main differences between IP routing and DTM routing.

Parameter name IP DTM What is routed? packets

channel-setup requests

How do you specify how to reach a destination?

with one nexthop per destination

by specifying all possible nexthops that lead to the destination.

80 • DTM Configuration Element Manager User’s Manual Nimbra OneSerie

Address type IP addresses DTM addresses

Figure 75 Differences between routing in an IP network and a DTM network

This section describes how to configure routing. There are two different ways to configure routing:

Static routing where the routing tables are configured manually. Manual configuration of routing tables works fine in a small network.

Dynamic routing where a routing protocol calculates the routing tables automatically.

Note:

Do not mix dynamic routing with static routing since this can lead to errors that are hard to track down.

Static routing

To use static routing, it is necessary to configure each node in the network with information on how to reach each other node in the network. For nodes with a single interface and a single neighbour, this is as easy as instructing the node that all other nodes can be reached via that neighbour, but for nodes with multiple interfaces it is necessary to configure which neighbour to use to reach each destination or group of destinations.

Static routing is configured in the Routing Table. The routing table can be seen in the DTM|Routing page. The routing table consists of a number of routing entries. Each routing entry contains the fields shown in Figure 76.

Element Manager User’s Manual Nimbra OneSerie DTM Configuration • 81

Field Description

Destination The destination and prefix together specify which

destinations this routing entry is valid for; refer to section Addresses for a description of addressing. The destination must be a numeric DTM address.

Prefix

The number of significant bits in the destination address.

Next hop One possible next hop node that can be used to

reach the destination node(s). The next hop must be the DTM address of a neighboring node.

Type

Shall be set to “Static” for static routing entries. See the chapter on DRP for a description of “Link Prefix” and “Area Prefix”.

Metric The cost of using this route entry. If there are several

routes to the same destination, then routes with the lower metric are tried before routes with higher metric

Adm

Administrative status for the route. Routes with Adm set to down are ignored when making routing decisions.

Figure 76 The routing entries

When a node needs to find a nexthop for a destination it looks in the routing table for all entries that match the destination address. This gives the node a list of a number of different nexthops that it should try to reach the destination via.

Note:

If there are several routing entries with different prefix lengths that are valid for a destination, then only the entries with the longest prefix will be used. If there are several entries with the same prefix length, then they will all be tried in order of increasing metric.

Note:

If the routing is mis-configured in a node, the operation of the entire network can be affected.

Dynamic routing

Instead of configuring the routing tables manually in each node; a routing protocol can be used to populate the routing table automatically. This is called dynamic routing. In a DTM network, the routing protocol DRP can be used.

Dynamic routing has the following advantages over static routing: Less manual configuration required for large networks. Automatically updated routing tables when a new node is added to the network

or when the network topology changes. Static routing is error-prone. The DRP Protocol, is a routing protocol that is very similar to OSPF, but it has

been adapted to the unique characteristics of the Net Insight’s technology. It automatically calculates the routing tables in all nodes and updates them as changes are detected in the network.

82 • DTM Configuration Element Manager User’s Manual Nimbra OneSerie

To use DRP, all that is necessary is to enable DRP on all nodes in the network and then remove all the static routing entries that have been added to the nodes as shown in the section on Static Routing.

Static route

Adding a static route

1. Navigate to the DTM|Routing. The start web page for Routing

configuration is shown in, Figure 77.

Figure 77 Routing

2. Click on Add route, the Route page, Figure 78, will appear.

Figure 78. The add route page

• Route id: States the id of this routing entry.

• Administrative status: The Administrative status for this routing entry.

Down means that the route is ignored. Up means that the routing entry shall be used.

• Type: The type of routing entry. Set to static for static routes. (Link prefix

and Area prefix are for dynamic routing.)

• Destination: The address of the remote node or network.

• Prefix: The length of netmask for the remote subnet.

E.g. Prefix 64 = FF.FF.FF.FF.FF.FF.FF.FF E.g. Prefix 56 = FF.FF.FF.FF.FF.FF.FF.00 E.g. Prefix 48 = FF.FF.FF.FF.FF.FF.00.00

• Next hop: The DTM address of the neighboring node that can be used to

reach the destination.

• Metric: The cost associated with using this route. A route with a lower

metric will be tried before a route with a higher metric.

Element Manager User’s Manual Nimbra OneSerie DTM Configuration • 83

3. Set the Admin status to Up in the drop down list and mark the Toggle

admin. Enter the Destination network or node address. Enter the Prefix.

4. Enter the Next hop, and set the Type to static.

5. Enter the Metric parameter.

6. Click on the OK button.

7. The Routes page will reappear with a line for the new static route added in

the table.

Editing a static routing entry

1. To edit a routing entry, access the DTM|Routes page and click on the

address of the route to be edited. The Route page, Figure 79, will appear.

Figure 79. Edit route page

Via this page it is possible to temporarily disable the route by setting the Administrative status to Down, change the prefix or delete the route.

2. To make changes, enter the new values and then click Apply or OK.

Deleting a static routing entry

1. To delete a routing entry, access the DTM|Routing, Figure 77, will

appear. Click on the address of the route to be deleted. The Edit routes page, Figure 79, will appear.

2. Set the Administrative status drop-down menu to Down, click Apply.

3. Click on the Delete button.

4. The Routes page will reappear, without the deleted route.

Dynamic routing

Setting the dynamic routing parameters

1. Navigate to the web page DTM|Routing, the Routing page, Figure 80,

will appear.

84 • DTM Configuration Element Manager User’s Manual Nimbra OneSerie

Figure 80. Dynamic routing

2. Click on Dynamic routing config, Figure 81, will appear.

Figure 81. Routing entries

The goal of DRP is to find the lowest-cost path from source node to destination node. The cost of a path is defined as the sum of the cost of all switches and outgoing interfaces that the path uses. A good base-configuration for DRP is to set the cost of all outgoing interfaces to 1 and the cost for passing through all nodes to 0. This means that the lowest-cost path will always be the path that passes through the least number of links. In some circumstances, the operator might have a different opinion on what the lowest-cost path is. It is then

possible to classify some links or switches as “ more expensive” than other links. This is done via a set of configuration variables called “ metrics”.

Changes to the Metric settings in a node will be automatically propagated to all other nodes in the network and they will update their routing tables accordingly. This process can however take some time (on the order of seconds in smaller networks) before all nodes have received the new information. Changes to metrics do not affect channels that are already established.

• Node metric: The cost of switching a channel in this node.

• Interface metric: The cost of setting up a channel out via this interface.

Element Manager User’s Manual Nimbra OneSerie DTM Configuration • 85

• Enable: Should this node communicate and exchange routing information

with a neighbor via this interface? This check box should normally be enabled when using DRP. It can be disabled when DRP should not be used via specific interface, e.g. if that interface connects to another operator and

you don’t want to exchange routing information automatically with that operator.

Advanced settings

If a node is attached to the rest of the network using a single point-to-point link only, then the node doesn’ t need a complete routing table. The only routing entry that is necessary is a default route that says that all other addresses can be reached via the peer on the other side of the point-to-point link. In DRP terminology, this type of node is called an end-node and all other nodes are called switches.

• Node is a:

Switch: Build a complete routing table in this node.

End node: In this case the node will get a default-route listing all the

available peers as possible next hops with no particular preference. This can be useful if a node has two peers for redundancy purposes only and all other destinations is the network can be reached at roughly the same cost via both peers.

Note! If a node is configured as an end node, it can only originate and terminate channels; it will not allow a channel to be switched via itself.

• Detect default gateway: Calculate which neighbor that should be the

default gateway automatically. Only relevant for end-nodes.

• Area number: In a large network all the nodes can not belong to the same

area. Configure the area it should belong to.

• Detect from neighbors: The node will receive the area number

automaticallyfrom the neighbor.

3. Enter the Node metric and select Enable.

4. Enter a metric for the DTM interfaces.

5. Select if the node should be a switch or an end node and click OK.

Adding a dynamic routing entry

1. To add a dynamic route navigate to the web page DTM|Routing, the

Routing config page, Figure 82, will appear.

Figure 82. Dynamic routing

Click on Add route, Figure 85, will appear.

86 • DTM Configuration Element Manager User’s Manual Nimbra OneSerie

Figure 83. Dynamic routing

Enter the values and click OK. In the default configuration, DRP will make sure that all nodes in the network

contains a host route for each other node in the network. In a large network, it is sometimes desirable to lower the number of routing entries in a node. DRP provides a number of mechanisms to do this.

For dynamic routes the type could be set to:

• Link Prefix

If there are many end-nodes with addresses with a common prefix attached to a single switch, then it is possible to announce all the end-nodes as a single route instead of announcing them individually. This is done by configuring the endnodes as end node (in Dynamic routing config) and adding a link-prefix route in the switch.

n1X.17.01

X.17.03

X.17.02

Figure 84. Routing entries

Nodes n1, n2 and n3 are configured as end-nodes and they have DTM addresses that all fall in the range X.17.00/60 (i.e. from X.17.00 to X.17.0F). A linkprefix route can therefore be added to the node s1. This means that instead of announcing n1, n2 and n3 individually, s1 will announce only X.17.00/60. Instead of each node in the DTM network having three separate routes for n1, n2 and n3, they will only have a single route that covers all three of them.

• Area Prefix

A network can be divided into areas to increase the scalability of DRP. Each area is identified with an area number, that must be configured in each node belonging to the area. The default value of the area number is zero. A border node is a node that has at least one neighbour that resides in another area. Two

Element Manager User’s Manual Nimbra OneSerie DTM Configuration • 87

border nodes with different area numbers will not become adjacent and exchange topology state information.

Editing a dynamic routing entry

To edit a dynamic routing entry, access the DTM|Routes page and click on the address of the route to be edited. The Route page, Figure 85, will appear.

Figure 85. Edit route page

Enter the entries, which should be changed. Click Apply or OK.

Deleting a dynamic routing entry

To delete a routing entry, access the DTM|Routing web page. Click on the address of the route to be deleted.

Set the Administrative status drop-down menu to Down, click Apply. Click on the Delete button.

Figure 86. Delete a routing entry

Sync

Net Insight’s solution is a synchronous solution and all the nodes in the entire must be synchronized to the same clock source. The source node can either use its internal clock or use an external sync clock. The reference clock is distributed in a tree-structure throughout the whole network. The external sync source could either be a 2.048 MHz or a 1.544 MHz clock.

88 • DTM Configuration Element Manager User’s Manual Nimbra OneSerie

This chapter describes how to monitor the synchronisation status of the unit and to modify external clock settings.

Click on the DTM menu item. Then click on Sync. The Sync page, Figure 87, will appear.

Figure 87. The Sync page

The web page shows the sync sources and their status, as follows: Sync oper. state: Either Up (the unit is synchronized), Pending (the unit is

starting up), or Down (error in sync function). The error is shown in the Alarms list.

• External clock priority: Sets the priority of the external clock, attached to

this node.

• External clock admin. status: Sets the external clock to active when

status is set to up, if signal is present. Down forces the external clock to de inactive.

• Type: Specifies if the clock is internal,externalor timing is taken from

another node.

• Id: Shows interface id for all interfaces.

• Current source: Yes if the switch is synchronized to this source, No

otherwise.

• Back-up source: Yes if the clock is intended as backup, No if it isn’t.

• Prio: Priority, 0 to 14. 14 is the internal clock, 0 and up is used for any

external clocks. A low number indicates high priority, highest priority = 0. When using only internal sync, the node with the lowest Node Mac/If address will be the sync master.

Element Manager User’s Manual Nimbra OneSerie Trunks • 89

Trunks

Overview of Trunks

Trunk modules are used to connect nodes into a network. The trunk interface manager supports 8B10B, SONET/ SDH and PDH class of

interfaces. The main functional areas covered by the manager are: Trunk interface configuration, Trunk interface alarm administration and PMM (Performance Monitor Manager) support for trunk interfaces. For PMM refer to section Perf. Monitor.

Trunk Modules, Nimbra One

There are several different trunk modules. Some of the cards are turnable and some are available in type A and B versions. The recommendation is to use A for the Trunk Modules and B for Access Modules.

Trunk Modules Data rate

OC-48/STM-16 X-ADM Module 2 488 Mbps OC-12/STM-4 Trunk Module

(DTM 622 Trunk Module)

622 Mbps

2 x OC-12/STM-4 Trunk Module 2 x 622 Mbps 4 x OC-3/STM-1 Trunk Module 4 x 155 Mbps OC-3/STM-1 Trunk Module

(DTM 150 Trunk Module)

155 Mbps

4 x DS3/E3 Trunk Module DS3 45 Mbps

E3 34 Mbps

1 Gbps Optical Trunk Module DTM 1000 Trunk Module SH

1 000 Mbps

1 Gbps Optical Trunk Module DTM 1000 Trunk Module LH

1 000 Mbps

90 • Trunks Element Manager User’s Manual Nimbra OneSerie

Trunk Modules, Nimbra 300

There are several versions of trunk modules, according to the table below. From a web management point of view, all Nimbra 300 trunk modules have a Nimbra One mirror image and behaves identically in the GUI interface. Hence, no separate description is made of Nimbra 300 Series trunk modules.

Trunk Modules Data rate

OC-48/STM-16 X-ADM Module 2 488 Mbps OC-12/STM-4 Trunk Module 622 Mbps 2 x OC-12/STM-4 Trunk Module 622 Mbps 4 x OC-3/STM-1 Trunk Module 155 Mbps 4 x DS3/E3 Trunk Module DS3 45 Mbps

E3 34 Mbps 1 Gbps Optical Trunk Module, SH 1 000 Mbps 1 Gbps Optical Trunk Module, LH 1 000 Mbps

Nimbra 360 has also got integrated SDH/SONET trunk interfaces on the base unit. One interface type is installed among the options below.

Trunk Interfaces, Nimbra 360 Base Unit Data rate

OC-48/STM-16 X-ADM Interface (2 ports) 2 488 Mbps OC-12/STM-4 Trunk Interface (4 ports) 622 Mbps OC-3/STM-1 Trunk Interface (4 ports) 155 Mbps

Trunk Modules, Nimbra 600

There are several versions of trunk modules, according to the table below. These modules look different in the web interface than corresponding ones in Nimbra One/300.

Trunk Modules Data rate

1 x OC-192/STM-64 9 952 Mbps 4 x OC-48/STM-16 2 488 Mbps 4 x OC-12/STM-4 622 Mbps 4 x OC-3/STM-1 Trunk Module 155 Mbps

Trunk interface configuration

The start web page for Trunks is shown in, Figure 88.

Element Manager User’s Manual Nimbra OneSerie Trunks • 91

Figure 88. The start web page for Trunks

The sub-sections are:

• Interfaces present the various trunk modules and monitor the state of

them.

• Perf. Monitor. Performance monitoring (PM) is the process whereby

transported data in a tele- or data communication network is supervised for quality deterioration. With help of this process, service level agreement (SLA) reports can be produced and preventive maintenance work can be performed at an early stage before more severe faults occur in the network. Performance monitoring counters via SNMP. G.826-like performance counters on trunk, interface and connection. For further information please refer to section.

1. Navigate to the Trunks|Interface menu to enter the list of the trunks.

Select the trunk that should be configured or inspected, by clicking on the Name of the trunk.

Figure 89. Trunk Module

The table presents the following information:

• Name presents the name of the interface, 8b10b or Sonet/sdh.

• Mode: Shows the mode of the interface, 8b10b, sdh or sonet.

• Capacity: Shows the total capacity of the trunk interface in Mbps.

• Oper: Shows the operative status of the trunk interface.

Editing the OC-48/ STM-16 X-ADM Module

The Read-only parameters are:

Parameter name Description

Interface name The interface id, Sonet/sdh. Written as

“nameX:Y” Where X is position of the

card and Y position of the port. Oper. status The operational status of the board. Speed The capacity, 2488.320 Mbps. Transceiver temperature Presents the temperature of the card. Transceiver laser bits Presents the ampere of the laser.

92 • Trunks Element Manager User’s Manual Nimbra OneSerie

Transceiver power Presents the power. Receiver power Presents the power.

The configurable parameters for the OC-48/STM-16 interface are:

Parameter name Description

Suppress Alarms When the service is up and running as

intended, enable the alarms for the service by uncheck the Suppress alarms for;

All: When marked all the alarms are suppressed. AIS: Alarm indication signal.

RDI: Remote defect indicator.

Default is that the alarms are suppressed. I.e. you must uncheck the

boxes to receive the alarms!

The Advanced parameters for SONET/SDH OC-48/STM-16 interface are:

Parameter name

Description

Force DNU SSM transmission:

Do not use sync source master. Selects whether to retrieve the transmitting bit-clock or not.

H1 SS bits Differences between Sonet and SDH.

Selects value of the SS bits in the H1 byte in the Sonet/SDH section overhead. Older Sonet/SDH equipment may require other value than the default. 00 Sonet 10 SDH

POH C2 byte: Path over head

C2 = Unspecified (Type of network eg. ATM.)

Signal failure filter period

Delay time for 1+1, so the nodes will not switch over when the external products will.

Performance monitoring counters

B1 Section overhead B2 Line overhead

B3 Path overhead M1 Remote indication of B1

G1 Remote indication of B3 Overhead bytes: SS=2 C2=255

Pointer adjustment event, positive and negative

RXPJE+ RXPJETXPJE+ TXPJE-

The Alarms parameters are presented at the bottom of the table as:

Parameter name Description

Opto module Alarms from SFP. Unequipped (UNEQ) Unequipped, signal for no service

configured.

Los of signal (LOS) Loss of signal. No signal detected on

SONET/SDH network interface, no light in the fiber.

Los of frame (LOF)

Loss of frame. Unable to align SONET/SDH frame, no light in the fiber.

Los of pointer (LOP) Loss of pointer

No pointer for where payload is.

Alarm indication signal, line (AIS-L)

Alarm indication signal, line, defect detected by upstream SONET/SDH network interface.

Alarm indication signal, path (AIS-P)

Alarm indication signal, path, defect detected by upstream SONET/SDH network

Element Manager User’s Manual Nimbra OneSerie Trunks • 93

interface.

Remote defect indication, line (RDI-L)

Remote defect indication, line, defect detected by downstream SONET/SDH network interface.

Remote defect indication, path (RDI-P)

Remote defect indication, path, RDI-P, defect detected by downstream

SONET/SDH network interface. Payload mismatch (PLM) Payload mismatch. Degraded signal (DEG) Degraded signal . Loopback Loopback alarm, NA.

1. Navigate to the Trunks|Interface and then on the trunk interface that

should be edited, Figure 90, will appear.

Figure 90. Edit the Trunk parameters, OC-48/STM-16 X-ADM Module

94 • Trunks Element Manager User’s Manual Nimbra OneSerie

2. Select whether to receive the alarms or not by marking the Suppress

Alarms or not.

3. Enter the Signal failure filter time, and click OK.

Editing the 2 x OC-12/STM-4 Trunk Module

The 2 x OC-12/STM-4 Trunk Module is configured equivalently with the OC-48/STM-16 X-ADM Module.

Editing the OC-12/STM-4 Trunk Module (DTM 622 Trunk Module)

The Read-only parameters are:

Parameter name Description

Interface name The interface id, Sonet/sdh. Written as

“nameX:Y” Where X is position of the

card and Y position of the port. Oper. status The operational status of the board. Speed The capacity.

The configurable parameters for the OC-12/STM-4 Trunk Module are:

Parameter name Description

Suppress Alarms When the service is up and running as

intended, enable the alarms for the

service by uncheck the Suppress alarms

for;

All: When marked, all alarms are

suppressed.

AIS: Alarm indication signal is

suppressed.

RDI: Remote defect indicator.

Default is that the alarms are

suppressed. I.e. you must uncheck the

boxes to receive the alarms!

The Advanced parameters:

Parameter name Description

Transmit sync source Selects whether to retrieve the

transmitting bit-clock for the interface

from local oscillator, interface or from

the bit clock received from the remote

node, loop. This shouldn’t be confused

with the 8 kHz frame clock. H1 SS bits Differences between Sonet and SDH.

Selects value of the SS bits in the H1

byte in the Sonet/SDH section

overhead. Older Sonet/SDH equipment

may require other value than the default.

00 Sonet

10 SDH Signal failure filter period

Delay time for 1+1. The time that the

nodes waits for underlying network

(SDH/SONET/WDM) to re-establish

connection. In order to avoid a switch

over.

This parameter can also be used to

allow certain amount of errors without

Element Manager User’s Manual Nimbra OneSerie Trunks • 95

tearing down channels or a certain trunk.

Degraded defect (DEG) period Configuration parameters for the

“Degraded” alarm, according to ITU G.806 fir the interface.

Period, default 5 sec.

Degraded defect (DEG) threshold Configuration parameters for the

“Degraded” alarm, according to ITU G.806 fir the interface.

Number of block errors. Default 1200.

Performance monitoring counters B1 Section overhead

B2 Line overhead B3 Path overhead

M1 Remote indication of B1 G1 Remote indication of B3

Pointer adjustment event, positive and negative

RXPJE+ RXPJETXPJE+ TXPJE-

The Alarms parameters are presented at the bottom of the table as:

Parameter name Description

Opto module Alarms from SFP. Unequipped (UNEQ) Unequipped, signal for no service

configured.

Los of signal (LOS) Loss of signal. No signal detected on

SONET/SDH network interface, no light in the fiber.

Los of frame (LOF)

Loss of frame. Unable to align SONET/SDH frame, no light in the fiber.

Los of pointer (LOP) Loss of pointer

No pointer for where payload is.

Alarm indication signal, line (AIS-L)

Alarm indication signal, line, defect detected by upstream SONET/SDH network interface.

Alarm indication signal, path (AIS-P)

Alarm indication signal, path, defect detected by upstream SONET/SDH network interface.

Remote defect indication, line (RDI-L)

Remote defect indication, line, defect detected by downstream SONET/SDH network interface.

Remote defect indication, path (RDI-P)

Remote defect indication, path, RDI-P, defect detected by downstream

SONET/SDH network interface. Payload mismatch (PLM) Payload mismatch. Degraded signal (DEG) Degraded signal. Loopback Loopback alarm, NA.

1. Navigate to the Trunks|Interface and then on the trunk interface that

should be edited, Figure 91, will appear.

2. Select whether to receive the alarms or not by marking the Suppress

Alarms or not.

3. Enter the Signal failure filter time, and click OK.

96 • Trunks Element Manager User’s Manual Nimbra OneSerie

All

Figure 91. Edit the Trunk parameters OC-12/STM-4 Module

Element Manager User’s Manual Nimbra OneSerie Trunks • 97

Editing the OC-3/STM-1 Trunk Module (DTM 150 Trunk Module)

The Read-only parameters are:

Parameter name Description

Interface name The interface id, 8b10b or Sonet/sdh. Written

as “nameX:Y” Where X is position of the card

and Y position of the port. Oper. status The operational status of the board. Description

The number of slots available for

transmission on this interface. Speed The capacity.

The configurable parameters for the OC-3/STM-1 Trunk Module are:

Parameter name Description

Suppress Alarms When the service is up and running as

intended, enable the alarms for the service by

uncheck the Suppress alarms for;

All: When marked, all alarms are suppressed.

AIS: Alarm indication signal.

RDI: Remote defect indicator.

Default is that the alarms are suppressed.

I.e. you must uncheck the boxes to receive

the alarms!

The Advanced parameters:

Parameter name Description

Transmit sync source Selects whether to retrieve the transmitting

bit-clock for the interface from local oscillator

(interface) or from the bit clock received from

the remote node (loop). This shouldn’t be

confused with the 8 kHz frame clock. H1 SS bits

Differences between Sonet and SDH.

Sets value of the SS bits in the H1 byte in the

Sonet/SDH section overhead. Older

Sonet/SDH equipment may require other

value than the default.

00 Sonet

10 SDH Signal failure filter period Delay time for 1+1. The time that the nodes

waits for underlying network

(SDH/SONET/WDM) to re-establish

connection. In order to avoid a switch over.

This parameter can also be used to allow

certain amount of errors without tearing down

channels or a certain trunk.

The Alarms parameters are presented at the bottom of the table as:

Parameter name Description

Unequipped (UNEQ) Unequipped, signal for no service configured. Los of signal (LOS) Loss of signal. No signal detected on

SONET/SDH network interface, no light in the

fiber. Los of frame (LOF)

Loss of frame. Unable to align SONET/SDH

frame, no light in the fiber. Los of pointer (LOP) Loss of pointer

No pointer for where payload is. Alarm indication signal, line

(AIS-L)

Alarm indication signal, line, defect detected

by upstream SONET/SDH network interface.

98 • Trunks Element Manager User’s Manual Nimbra OneSerie

Alarm indication signal, path (AIS-P)

Alarm indication signal, path, defect detected by upstream SONET/SDH network interface.

Remote defect indication, line (RDI-L)

Remote defect indication, line, defect detected by downstream SONET/SDH network interface.

Remote defect indication, path (RDI-P)

Remote defect indication, path, RDI-P, defect detected by downstream SONET/SDH

network interface. Payload mismatch (PLM) Payload mismatch. Degraded signal (DEG) Degraded signal. Loopback Loopback alarm, NA.

1. Navigate to the Trunks|Interface and then on the trunk interface that

should be edited, Figure 92, will appear.

2. Select whether to receive the alarms or not by marking the Suppress

Alarms or not.

3. Enter the Signal failure filter time, and click OK.

All

Figure 92. Edit the Trunk parameters, OC-3/STM-1 Trunk Module

Net Insight Nimbra One, Nimbra 300, Nimbra One 600 User Manual

Specifications and Main Features

Frequently Asked Questions

User Manual