DF 1-4 Manual Book

C32391.20--B0

DF1/4 Blade User Manual, v.2

DN70592449 Issue 2-0 en

Nokia Siemens Networks

1 (156)

DF1/4 Blade

2 (156) Nokia Siemens Networks

DN70592449Issue 2-0 en

The information in this document is subject to change without notice and describes only the product defined in the introduction of this documentation. This documentation is intended for the use of Nokia Siemens Networks customers only for the purposes of the agreement under which the document is submitted, and no part of it may be used, reproduced, modified or transmitted in any form or means without the prior written permission of Nokia Siemens Networks. The documentation has been prepared to be used by professional and properly trained personnel, and the customer assumes full responsibility when using it. Nokia Siemens Networks welcomes customer comments as part of the process of continuous development and improvement of the documentation. The information or statements given in this documentation concerning the suitability, capacity, or performance of the mentioned hardware or software products are given as is and all liability arising in connection with such hardware or software products shall be defined conclusively and finally in a separate agreement between Nokia Siemens Networks and the customer. However, Nokia Siemens Networks has made all reasonable efforts to ensure that the instructions contained in the document are adequate and free of material errors and omissions. Nokia Siemens Networks will, if deemed necessary by Nokia Siemens Networks, explain issues which may not be covered by the document. Nokia Siemens Networks will correct errors in this documentation as soon as possible. IN NO EVENT WILL NOKIA SIEMENS NETWORKS BE LIABLE FOR ERRORS IN THIS DOCUMENTATION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY OR DATA,THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATION IN IT. This documentation and the product it describes are considered protected by copyrights and other intellectual property rights according to the applicable laws. The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark of Nokia Corporation. Siemens is a registered trademark of Siemens AG. Other product names mentioned in this document may be trademarks of their respective owners, and they are mentioned for identification purposes only. Copyright Nokia Siemens Networks 2009. All rights reserved.

Contents

DN70592449 Issue 2-0 en


3 (156)

Contents

1 Introduction ............................................................................................5

2 Installation ..............................................................................................7 2.1 Site requirements .....................................................................................8 2.1.1 Mechanics and power ..............................................................................8 2.2 Site environment ......................................................................................8 2.3 Preventive site configuration: maintaining normal operation....................9 2.3.1 General precautions.................................................................................9 2.3.2 Power considerations.............................................................................10 2.4 Safety recommendations........................................................................10 2.5 Safety with electricity..............................................................................10 2.6 Preventing electrostatic discharge damage ...........................................11 2.7 Safety with laser radiation ......................................................................11 2.8 Dimensions ............................................................................................13 2.9 Product labelling.....................................................................................14

3 Setup and configuration......................................................................15 3.1 Connections ...........................................................................................15 3.1.1 Front panel .............................................................................................15 3.1.2 System Reset / System Boot..................................................................16 3.2 Interfaces ...............................................................................................18 3.3 Topologies..............................................................................................18 3.4 Implementation.......................................................................................20 3.4.1 Framing and tributary mapping ..............................................................20 3.4.2 Trunk protection .....................................................................................21 3.4.3 Trunks and tributaries.............................................................................21 3.5 Provisioning............................................................................................22 3.5.1 Multiservice Manager installation ...........................................................22 3.5.2 Physical setup ........................................................................................22 3.5.3 USB driver installation............................................................................25 3.5.4 Connecting to the DF1/4 Blade ..............................................................25 3.5.5 Command line options............................................................................27 3.5.6 User login ...............................................................................................28 3.5.7 Installation required information ..........................................................29 3.5.8 Multiservice Manager user interface ......................................................30 3.6 System setup .........................................................................................34 3.6.1 System ...................................................................................................34 3.6.2 Networking .............................................................................................35 3.6.3 Users Manager.......................................................................................54 3.6.4 System upgrade and backup..................................................................58 3.6.5 System downgrade.................................................................................59 3.6.6 General ..................................................................................................59 3.7 System Event Logging ...........................................................................60 3.7.1 Multiservice Manager Event Log............................................................61 3.7.2 Syslog ....................................................................................................63

DF1/4 Blade



3.8 SNMP .................................................................................................... 65 3.8.1 DF1/4 Blade SNMP MIB........................................................................ 65 3.8.2 SNMP communities ............................................................................... 65 3.8.3 Configure a DF1/4 Blade using SNMP.................................................. 66 3.8.4 DF1/4 Blade Traps ................................................................................ 67 3.9 System Alarms ...................................................................................... 69 3.9.1 Service LEDs......................................................................................... 69 3.10 Rack Alarms .......................................................................................... 70 3.11 V.11 Master slave serial data transmission (Q1 support)...................... 71 3.12 Example: A Managed Network .............................................................. 77 3.12.1 Local NTP server Windows XP/2000 .................................................... 77 3.12.2 RIP Listener Windows XP/2000 ............................................................ 77 3.12.3 IP Forwarding (Routing) Windows XP/2000 .......................................... 78 3.13 Configuring services .............................................................................. 80 3.13.1 Trunk ..................................................................................................... 80 3.13.2 Physical fibre connections ..................................................................... 82 3.13.3 Tributary interfaces................................................................................ 89 3.14 Trunk and Data Path Configuration ..................................................... 127 3.14.1 SDH Alarms......................................................................................... 127 3.14.2 Trail Trace Identifier............................................................................. 135 3.15 Network protection............................................................................... 136 3.15.1 MSP/1+1 Automatic Protection Switch ................................................ 137 3.15.2 UPSR/SNCP Automatic protection switch........................................... 139 3.16 Clock.................................................................................................... 140 3.16.1 Clock hierarchy.................................................................................... 143 3.16.2 Clock types .......................................................................................... 143 3.16.3 SSM..................................................................................................... 143 3.17 Troubleshooting................................................................................... 144 3.17.1 USB driver installation on Windows XP............................................... 144

4 International compliances ................................................................ 153

5 RoHS statements............................................................................... 155

Introduction

DN70592449 Issue 2-0 en


5 (156)

1 Introduction The Nokia Siemens Networks DF1/4 Blade is a single unit with 12 E1 ports, occupying two unit slots from the Dynanet subrack. DF1/4 Blade is used to increase the bandwidth capacity of the Dynanet customer networks, adapting to new Ethernet traffic demands while maintaining traditional services. The DF1/4 Blade allows customers to migrate to an SDH network from existing Dynanet installations. Requiring no additional rack space, the Blade can be installed in a majority of Dynanet products freely alongside other interface units.

The DF1/4 Blade has two multirate STM-1/STM-4 trunk interfaces and two fixed rate STM-1 interfaces that can operate as a trunk or tributary. In addition, the Blade supports 12 E1s and four gigabit Ethernet tributary interfaces. The DF1/4 Blade is based on an innovative software-driven architecture that protects customer investment by providing a direct upgrade path to feature and performance enhancements over the life of the product. Software updates are applied via an automated, fail-safe, one-step upgrade process that can be initiated from a central location to all sites in the network.

All configuration management and circuit provisioning is done via a user friendly graphical node management system, Multiservice Manager.

DF1/4 Blade



Installation

DN70592449 Issue 2-0 en


7 (156)

2 Installation This chapter describes the physical specifications and installation requirements for the Nokia Siemens Networks DF1/4 Blade.

Figure 1. DF1/4 Blade installed in NDM 8-slot Subrack

DF1/4 Blade



2.1 Site requirements

This chapter describes the site installation and safety requirements common to the DF1/4 Blade. Installers should reference the relevant chapter for the cabling specifications.

To ensure normal operation and avoid unnecessary maintenance, plan your site configuration and prepare your site before installation.

2.1.1 Mechanics and power

For instructions on installation and cabling of the rack, refer to NDM Installation document.

2.2 Site environment

Table Environmental site requirements lists the operating and non-operating environmental site requirements. The following ranges are those within which the DF1/4 Blade will continue to operate; however, a measurement that is approaching the minimum or maximum of a range indicates a potential problem. You can maintain normal operation by anticipating and correcting environmental anomalies before they approach a maximum operating range. The DF1/4 Blade products are designed for highly reliable operation and are cooled by a fan mounted inside the case. The fan openings at the rear of the chassis should be maintained clear of obstruction to allow airflow.

Table 1. Environmental site requirements

Min Max

Temperature, ambient operating

-5 degrees Celsius

+45 degrees Celsius

Temperature, ambient non-operating and storage

-25 degrees Celsius

70 degrees Celsius

Humidity, ambient (non-condensing) operating

10% 90%

Humidity, ambient (non-condensing) non-operating and

5% 95%

Installation

DN70592449 Issue 2-0 en


9 (156)

Min Max storage

Altitude, operating and nonoperating

Sea level 2,000 meters

Vibration, operating 5 to 200 Hz

0.5 g (1 oct./min.)

-

Vibration, nonoperating 5 to 200 Hz,

1 g (1 oct./min.)

200 to 500 Hz

2 g (1oct./min.)

DC power

(nominal -48 VDC)

-20 Volts DC -72 Volts DC

2.3 Preventive site configuration: maintaining normal operation

Planning a proper location for the subrack and designing the layout of your equipment rack or wiring closet is essential for successful system operation. Equipment placed too close together or inadequately ventilated can cause system over-temperature conditions.

Following are precautions that can help avoid problems during installation and ongoing operation.

2.3.1 General precautions

Follow these general precautions when planning your equipment locations and connections:

Nokia Siemens Networks recommends keeping equipment off the floor and out of any area that tends to collect dust, excessive condensation, or water.

Follow ESD prevention procedures to avoid damage to equipment. Damage from static discharge can cause immediate or intermittent equipment failure.

DF1/4 Blade



2.3.2 Power considerations

When planning power connections to the DF1/4 Blade, check the power at your site before installation and periodically after installation to ensure that you are receiving clean power.

2.4 Safety recommendations

The following guidelines will help to ensure your safety and protect the equipment. This list does not cover all potentially hazardous situations, so be alert.

The installation of your DF1/4 Blade should be in compliance with national and local electrical codes.

Always unplug the power cable before installing or removing a subrack.

Keep the subrack area clear and dust free during and after installation.

Keep tools and subrack components away from walk areas. Do not wear loose clothing, jewellery (including rings and chains),

or other items that could get caught in the subrack.

The DF1/4 Blade operates safely when it is used in accordance with its marked electrical ratings and product usage instructions.

Note Only trained and qualified personnel should be allowed to install or replace this equipment.

2.5 Safety with electricity

WARNING Refer servicing to qualified personnel

No User serviceable parts.

Installation

DN70592449 Issue 2-0 en


11 (156)

Tip Dispose of used components that contain batteries according to the manufacturer's instructions.

WARNING Do not work on the system or connect or disconnect cables during periods of lightning activity.

2.6 Preventing electrostatic discharge damage

Electrostatic discharge (ESD) damage, which occurs when electronic cards or components are improperly handled, can result in complete or intermittent system failures. Use an antistatic strap whenever handling the DF1/4 Blade assemblies.

Following are guidelines for preventing ESD damage:

Always use an ESD wrist strap or ankle strap and ensure that it makes good skin contact.

When handling a removed unit, make sure the equipment end of your ESD strap is attached to the ESD earth jack on the subrack.

Caution For safety, periodically check the resistance value of the antistatic strap. The measurement should be between 1 and 10 Mega Ohms (Mohm).

2.7 Safety with laser radiation

Up to six fibre optic interfaces in the form of hot swap SFP modules may be installed in the DF1/4 Blade, users must take suitable precautions, to protect against damage to eyes from Class 1 laser radiation.

The fibre optic SFP transmits invisible laser radiation. When not in use or connected to fibre optic cables, the fibre optic SFP connectors must have the dust caps fitted.

DF1/4 Blade



WARNING The fibre optic SFP transmits invisible laser radiation. Do not stare into beam or view directly with optical instruments.

This is a Class 1 laser product, operating at 1310nm or 1550nm, 0.5mW maximum.

Installation

DN70592449 Issue 2-0 en


13 (156)

2.8 Dimensions

Figure 2. DF1/4 Blade dimensions

DF1/4 Blade



Table 2. DF1/4 Blade dimensions

Max Mm

Height 233

Width 42

Depth 197

2.9 Product labelling

Each DF1/4 Blade unit has a label in the LED holder. The label contains the following information:

Model number Serial number

Setup and configuration

DN70592449 Issue 2-0 en


15 (156)

3 Setup and configuration The DF1/4 Blade is a fully software configurable device. Configurations can be made via Ethernet or USB.

3.1 Connections

3.1.1 Front panel

The DF1/4 Blade provides a total of 23 ports: 4 SDH, 12 E1, 2 10/100/1000 BaseT Ethernet, 2 GigEthernet, 2 V.11/Q1 and 1 USB.

DF1/4 Blade



Figure 3. DF1/4 Blade front panel

3.1.2 System Reset / System Boot

The DF1/4 Blade can be rebooted by removing and reinserting the unit to the subrack, by pressing the HW reset switch or by pressing the SW reset button of the Multiservice manager. Communication with the node will be lost and all traffic will be disrupted during the boot sequency.

3.1.2.1 Hardware Reset Switch


DN70592449 Issue 2-0 en


17 (156)

The DF1/4 provides a reset switch which is located between the USB console connector and the bottom SFP connector.

A straightened paper clip or any other small pointed object can be used to depress the button.

3.1.2.2 System Boot

Depressing the reset/boot button momentarily will cause the system to boot. Communication with the node will be lost and all traffic will be disrupted.

3.1.2.3 System Reset

Depressing and holding the reset button during the boot cycle will reset the node to the factory configuration. This will remove any configuration information supplied and will reset the node to the same configuration state as when the node was manufactured. Communication with the node will be lost and all traffic will be disrupted.

The 8 LEDs surrounding the E1 ports will turn red one after the other in a clockwise direction starting with the top left LED until a full circle is completed.

The reset button must be held depressed until the last of the 8 LEDs turns red, this takes approximately 30 seconds. Releasing the button before this will abort the reset process.

All 8 LEDs then flash green in sync 3 times indicating the system reset is now in progress.

DF1/4 Blade



3.2 Interfaces

The DF1/4 Blade product is fibre optic Customer Premises Equipment to deliver TDM and Packet based services.

The base models are equipped with the following fixed and flexible interfaces:

Flexible Interfaces SDH

2x 622Mbps/155Mbps SFP receptacles 2x 155Mbps SFP receptacles

Ethernet 2x Gigabit Ethernet SFP receptacles

Fixed Interfaces TDM

4xE1 RJ45 ports 8x E1 RJ45 ports. Refer to chapter 4 of this manual for

details.

Ethernet 2x 10/100/1000BaseT RJ45 ports

Flexible interfaces require the addition of SFP modules selected for interface bandwidth and transmission distance.

This manual is for the use of network administrators who need to configure the DF1/4 Blade for the delivery of tributary circuit and packet services from SDH fibre optic networks.

3.3 Topologies

The DF1/4 Blade has four fibre optic SDH interfaces which support a wide range of installation network topologies. The following figures illustrate several of the available topology solutions.


DN70592449 Issue 2-0 en


19 (156)

Figure 4. Terminal Mode and Protected Ring

Figure 5. Linear Midspan and Ring Ring

DF1/4 Blade



3.4 Implementation

3.4.1 Framing and tributary mapping

The DF1/4 Blade contains an extremely flexible digital cross connect and configurable trunk interfaces which support SDH framing and the most extensive support for multiple framing types within a micro MSPP device.

To fully exploit the feature-rich capabilities of the DF1/4 Blade requires that the network administrator be conversant with the SDH framing and tributary types. Conformance to accepted network design practises is encouraged, such that the network administrator should be mindful of the long term plans for network bandwidth allocation.

The following SDH mapping figure summarises the VC/VT mappings supported by the DF1/4 Blade.

140 T3-44.736 E3-34.368

E1-2.048

STM-1

STM-4

X1 X4

X3

AU-4

X1

X1

TUG-3

VC-4 VC-4

AU-4

Aligning Mapping Multiplexing Pointer processing

TUG-2

VC-12 C-12

X3

VC-3 C-3 X1

TU-12

TU-3

AUG-1

AUG-4

Figure 6. SDH mapping


DN70592449 Issue 2-0 en


21 (156)

3.4.2 Trunk protection

The SDH trunk can be configured with redundant protection interfaces.

In Linear topology networks, a switch to the protection trunk will switch the total payload, thereby inflicting a momentary service disruption to all circuits carried over the trunk.

Networks that use a ring topology, typically deploy a circuit path based protection, such that a protection switch impacts only the selected virtual circuits while maintaining service levels across the balance of the circuits.

The DF1/4 Blade enables the network administrator to configure trunk protection selectively to multiple sub-frame levels of the SDH trunk. This feature is utilised to provide path based protection for circuit based tributary interfaces. Switching path protection off for selected virtual circuits permit these circuits to be used in Ethernet VCAT groups, effectively doubling the available bandwidth for packet based tributary interfaces.

3.4.3 Trunks and tributaries

The DF1/4 Blade trunk interfaces have a maximum capacity of:

Lower order capacity of 30 VC-3s or 630 VC-12s Higher order capacity of 10 VC-4s The DF1/4 Blade tributary interfaces have a maximum capacity of:

4x E1 4 VC-12s

4x Ethernet Virtual Concatenation groups for flexible Ethernet transport

Lower order groups supporting a total of 9 VC-3s or 122 VC-12s

Higher order groups supporting a total of 8 VC-4s Cross connection between trunk interfaces can be made without restriction.

Cross connection from trunk to tributary is very flexible. Definition and distribution of TU types within the trunk payloads is totally within the control of the network administrator. The DF1/4 Blade can efficiently support a wide range of network implementations without restriction.

DF1/4 Blade



3.5 Provisioning

The following steps need to be taken before managing a new DF1/4 Blade:

Installing software Physical setup Installing USB drivers Connecting to the DF1/4 Blade

3.5.1 Multiservice Manager installation

There is a Setup.exe file on the CD that accompanies the DF1/4 Blade. This setup file will install Multiservice Manager, the software and USB driver files that is required to configure the DF1/4 Blade. The supported operating systems are Windows 2000 or XP.

To install Multiservice Manager, double click on the Setup.exe file and follow the installation wizard.

3.5.2 Physical setup

The DF1/4 Blade is connected to a PC through the serial USB 2.0 Type B port located at the front of the DF1/4 Blade.

There are several ways to provide a data connection between the PC and the DF1/4 Blade, this is described in the Figure USB and Ethernet console connections below.

Table 3. DF1/4 Blade console connections

Type Personal Computer DF1/4 Blade Comments

Serial USB USB host interface Front panel USB slave MSPP USB-to-Serial Port Device (COMxx)

Ethernet 10/100BaseT Front panel tributary port #2

Factory default IP

192.168.0.1


DN70592449 Issue 2-0 en


23 (156)

USB Type B Port

USB Type A Port

Management PCrunning Multiservice

Manager

Ethernet port #2

Ethernet interface

USB Type A toUSB Type B

Cable

Ethernet CAT5cross-over cable

Nokia DF 1/4 Blade

Figure 7. USB and Ethernet console connections

The DF1/4 Blade serial console connector complies with the Universal Serial Bus (USB) standard. To connect a PC to the DF1/4 Blade console, use a standard USB cable (Type A to Type B). These cables are commonly available from consumer electronics retailers.

DF1/4 Blade



The standard cable connects between the PC Type-A connector and the DF1/4 Blade console Type-B.

Table 4. USB pin-outs

Pin # Signal name

1 +5 volts

2 Data -

3 Data +

4 Ground

Figure 8. Type A connector found on PC

Figure 9. Type B connector used for DF1/4 Blade console

Connection via Ethernet supports management of the local node and management of remote network devices over the SDH Data Communication Channel (DCC) overhead bytes. The factory default IP address of the DF1/4 Blade is 192.168.0.1. Access to the DF1/4 Blade by IP is by Ethernet connection to port #2 which is the right hand side port of the two RJ45 Ethernet interfaces on the front panel. Use of this Ethernet port for management access does not preclude this interface also being configured for transport of Ethernet traffic over the WAN.


DN70592449 Issue 2-0 en


25 (156)

3.5.3 USB driver installation

The first time a USB connection is made to the DF1/4 Blade, Windows opens a dialog window indicating Found New Hardware. Proceed to install the DF1/4 Blade USB driver using the wizard by directing windows to Install from a list or specific location. Provide Windows with the search path \Multiservice Manager\Drivers\Win2k_XP. Windows will allocate a COM port to the USB console connection. The following versions of Multiservice Manager will not automatically bring up a list of available COM ports within the Setup window:

DLL Version: 2.10.6.7 (DF-CX) DLL Version: 3.2.6.2 (DF1/4 Blade) The DLL version is viewed as a splash window when the system starts or by clicking System Info from the Main Window.

If using older versions of Multiservice Manager, the COM port number can be found by examining the Device Manager. This can be accessed by going to:

Start Control Panel System Hardware Device Manager

Tip The allocated COM port is remembered by Windows for the DF1/4 Blade connection assuming the same USB port on the PC is always used.

If the USB driver fails to install during the installation process, see section 3.17.1 USB driver installation on Windows XP.

3.5.4 Connecting to the DF1/4 Blade

To start the Multiservice Manager application from Windows, use the mouse to select the following path:

Start Programs Nokia Siemens Networks Multiservice Manager

The following Multiservice Manager Main Window is displayed. Note the main window may contain further buttons and graphics depending on the configuration of the DF1/4 Blade.

DF1/4 Blade



Figure 10. Multiservice Manager Main Screen

Table 7 Multiservice Manager Menu Navigation illustrates menu navigation and shows all submenus.

Acknowledge the product information window that is displayed by clicking within the window.

Select the method of connection by clicking on the Setup button or Connection Connection Setup from the main menu then complete the Serial or TCP/IP details. Close this window and click on the Connect button.

The Serial port drop down box will list all available COM ports.

Select the COM# which has the description MSPP USB to Serial COM Port Device.

Current software is limited to a single USB session to a DF1/4 Blade from any single PC


DN70592449 Issue 2-0 en


27 (156)

Multiple DF1/4 Blade sessions can co-exist using the IP connection method. Each DF1/4 Blade can have only one management session at a

time.

Figure 11. Setup connection window

Tip The COM port selected for communication may vary with each PC. COM3 is used in the instance above, and may vary depending on the PC running Multiservice Manager.

ct control, if checked will immediately commence re of this window.

3.5.5 Com

F1/4 Blade will display all available command line options by using the llowing switch and invoking the application from the command shell.

C:\Program Files\Nokia Siemens Networks\ rvice /help

Table 5 lists DF1/4 Blades command line switches.

The Automatic Connea connection on closu

mand line options

Dfo

Multise Manager\MultiserviceManager

DF1/4 Blade



Table 5. DF 1/4 Blade e switches

d line switch

command lin

Comman Description

/NoLogo opens without the splash screen

/Mode Str where Str can be SDH, STM4_SDH, SONET, OC12_SONET, IA, OM, EM, OA or EV

/Cross Str where Str is the DACS cross connect file name

/SdhCross Str ile namewhere Str is the SDH/SONET cross connect f

/EVCross Str nnect file name where Str is the EV cross co

/IP Str where Str is the IP address

/COM Str where Str is the COM port

/Dir Str where Str is the forces default dir to launch from

/Platform Str where Str is 1600 or 800

/DF14B to start in the DF14B mode

/User UserName:UserPassword for auto login

/Backup ddressed node to auto backup from the a

/Help display this help screen

Note To use the /backup switch use the following syntax: C:\Program Files\Nokia Siemens Networks\

en set for a user on the DF1/4 Blade, omit from the command line.

Multiservice Manager\MultiserviceManager /ip 192.168.1.1 /user admin:my password /backup f a password has not beImypassword

3.5.6 User

me and password in order to connect to a Nokia Siemens Networks node for management and configuration. The login screen is shown below.

login

All users must log in with a userna


DN70592449 Issue 2-0 en


29 (156)

Figure 12. Multiservice Manager login dialogue

Factory default user logins are;

Level 4 (Network Admin) admin no-password

Level 0 (Guest) guest no-password

Refer to section Users manager for additional information on creating user accounts and associated access (privilege) levels.

3.5.7 Installation required information

After you install the unit, your system administrator must configure the individual and system interfaces before you connect your system to external networks.

Before you commence configuration, you will need information about the network. Following is some of the information you might need, depending on the services you plan to offer:

Node name and IP address for the DF1/4 Blade. Passwords to prevent unauthorized privileged-level access to the

configuration.

Optical interface standards. Operating speeds and required electrical standards for electrical

interfaces.

The source of the network clock reference.

DF1/4 Blade



3.5.8 Multiservice Manager user interface

Multiservice Manager provides a dockable windowed user interface. The appearance of the interface is configurable and can be set-up to display alarms and toolbars to the users choosing. The dockable interface operates in the same fashion as MS Office 2007 applications.

Figure 13. Multiservice Manager Main Screen (default layout)


DN70592449 Issue 2-0 en


31 (156)

Figure 13 Multiservice Manager Main Screen (default layout) shows the main window and describes the GUI layout.

Figure 14. Multiservice Manager Dockable Windows

Figure 14 Multiservice Manager Dockable Windows shows the main window and the dockable components available in Multiservice Manager. Table 7 Multiservice Manager Menu Navigation illustrates menu and sub menu navigation.

DF1/4 Blade



All items available in the menu are covered in the relevant sections of the document. The View menu is covered in the table below.

Table 6. View Menu Commands

View All items that control the look and feel of Multiservice Manager.

Toolbars Select tool bars to display.

Connection Display the Connection toolbar.

System Display the System toolbar.

Customise Customise and create tool bars.

Status Bar Toggle status bar on/off.

Panels Select Alarm windows to display

Alarms Toggle System Status Alarms on/off.

SDH/SONET Status Toggle SDH/SONET Status on/off.

SDH/SONET History Toggle SDH/SONET Status on/off.

Theme Change the current theme of Multiservice Manager

Office 2003 Select the colour scheme and window decorations of Office 2003.

Office 2007 Select the colour scheme and window decorations of Office 2007.

Layout Load Save or select the application layout.

Default Selecting the default as shown in the figure above.

Save to file Save the current layout to file.

Load From File Load a saved layout to file.

Table 7. Multiservice Manager Menu Navigation

Connection

Connect

Disconnect

Connection Setup

Exit

System

System Setup

Event Log

System Info

Backup

Restore

SDH

Trunk

Cross Connect

Clock

Section Alarms

Port A

View

Toolbars

Connection

System

Customise

Status Bar

Help

Help Index

About Multiservice Manager


DN70592449 Issue 2-0 en


33 (156)

Reboot Port B

Port C

Port D

HO Alarms

Port A

Port B

Port C

Port D

LO Alarms

Port A

Port B

Port C

Port B

Clear Alarm History

Reset Statistics

Clear APS History

Rack Alarm Cancellation

Panels

Alarms

SDH/SONET Status

SDH/SONET History

Layout

Default

Save to file

Load From File

The Connection menu provides commands to configure all connection details and to connect or disconnect from nodes in the network.

The System menu provides commands to configure all system parameters, not related to SDH/SONET. It provides access to system information and event logs. Configuration of TCP/IP services used by the node.

The SDH menu provides commands to configure all SDH parameters including:

Trunking options

Digital Cross Connect

SDH/SONET Alarms and history

Clock source and management.

The View menu provides commands to configure all parameters that control the look and feel of Multiservice Manager. Toolbars can be customised in the same fashion as MS Office applications.

The HELP menu provides commands to invoke the help system.

DF1/4 Blade



3.6 System setup

The System Setup button in the Multiservice Manager main window will open the system setup window. Each tab in this window is used to configure a set of system parameters.

Figure 15. System setup dialogue

3.6.1 System

This dialog allows the user to view system information of the node currently connected to the management system. The system dialog allows the operator to name the node, and add location and contact information. The name entered is displayed at the top right of the Main Window.

The name given appears in all Multiservice Manager dialogs after being saved.


DN70592449 Issue 2-0 en


35 (156)

3.6.2 Networking

The networking tab allows the user to configure settings for a number of network items.

The Table Network management functions lists the dialogs and provides a brief description of what each is used for. See each referenced section for further details.

When the system alarm is in a red (major alarm) state, then rack alarm A and service LED Yellow will be enabled.

When the system alarm is in a yellow (minor alarm) state, then rack alarm B and service LED Yellow will be enabled.

When the system alarm is in a green (normal) state, then no rack alarm or service LED is enabled

The user will then have to connect to the DF1/4 Blade in Multiservice Manager to find out which alarm is currently active.

The reason why no SDH specific alarms are included here is because there are four SDH trunks on the DF1/4. The System Alarm will cover any issues that may occur in the trunks, circuits or service ports.

Example: A Managed Network for an example on using these parameters.

TCP/IP Network configuration should be completed in the following order:

1. Create user logins and assign system privileges.

2. LAN IP address and network mask.

3. Enable Routing .

4. Routing specifics for the LAN interface.

5. Configure the WAN PPP, Link and routing specifics.

6. NTP client settings.

7. SNMP Communities.

8. SNMP trap targets.

9. Syslog.

Table 8. Network management functions

Config Item Description See Section

LAN The local Ethernet IP address of the 800. Used for physical and 3.6.2.1

DF1/4 Blade



Config Item Description See Section DCC connections. Provides IP connectivity for all of the 800s IP network features.

WAN Used to setup internetworking across the DCC between adjacent DF1/4 Blade nodes. 3.6.2.2

WAN Status A status window for DCC connections between adjacent nodes. 3.6.2.2

Routing Table A table displaying both static and dynamic route information held by the system. 3.6.2.3

Static Routes Static routes are entered in this dialog. 3.6.2.5

SNMP Communities

SNMP community strings (names) and associated read/write permissions are entered in this dialog. 3.6.2.6

SNMP Trap Targets

An IP address of a management console (computer configured to receive SNMP traps) is entered in this dialog. 3.6.2.8

Syslog An IP address of a management console (computer configured with a Syslog server) is entered in this dialog. 3.6.2.7

NTP Client An IP address of a NTP (computer configured with a NTP server) is entered in this dialog. 3.6.2.9

IP Routing IP routing is configured in this dialog. 3.6.2.10

3.6.2.1 Networking - LAN

An IP address is required to identify and manage a node via TCP/IP in Multiservice Manager. The IP address is also required if node is to be configured for Syslog or SNMP management, and is also required if the node is to be configured to have the system time synchronised using NTP.

Tip The IP address for the node is the IP address of the console Ethernet interface only.

The node management IP address and mask is used for local Ethernet and remote DCC connections. The new IP address is activated immediately after the Apply button is executed. This will cause a loss of connection if the current connection is over IP.

The factory default IP address is 192.168.0.1 mask 255.255.255.0

The LAN IP address is configured from the main menu:

System System Setup Networking Tab LAN


DN70592449 Issue 2-0 en


37 (156)

Enabling routing

The DF1/4 Blade supports two routing protocols, OSPF (Open Shortest Path First) and RIP (Routing Information Protocol) or can be configured to have no routing protocol running which is the default factory setting.

Multiservice Manager is used to manage all DF1/4 nodes in a network via TCP/IP. The PC communicates with all nodes via gateway node and all other nodes over the DCC (Data Communications Channel). As nodes are configured with different network addresses, routing information must be maintained in the management PC as well as all other nodes in the network.

Routing protocols ensure that if a protected network configuration changes due to a fault or some other condition, all nodes in a managed network are updated periodically with current routing information. This ensures nodes can communicate with one another providing a reliable management platform.

To configure routing on the DF1/4 Blade:

Configure Global Routing parameters

1. Select the Networking Tab from the System Setup dialog

2. Select IP Routing from the Network Item list

3. Select the protocol: None, RIP or OSPF from the routing protocol drop down list

4. Configure options for the selected protocol

5. Configure Interface Routing parameters

6. Enable routing for the LAN and WAN interfaces

7. Configure protocol interface options for the LAN and WAN interfaces. (This is covered in more detail below)

Tip On a managed network It is only necessary to enable a routing protocol on the LAN Ethernet interface on the gateway node. The gateway node connects to a management console, requiring only a one physical Ethernet connection to the DF1/4 Blade network. The management console can then manage any of the nodes in a DF1/4 network via the DCC (Data Communications Channel)

Static routes can be used in conjunction with RIP. The network administrator will likely enter static routes into a managed network to reach networks beyond that of the gateway.

DF1/4 Blade



RIP global settings

The RIP global settings figure displays RIP as the selected protocol. This dialog displays the global configuration parameters that RIP will use on either the LAN or WAN interfaces. Note that this figure is showing the default and recommended parameters. These parameters can be changed to interoperate with other manufacturers equipment.

For further reading on RIP please consult RFCs 1058 and 2453.

Tip RIP can only be used as the routing protocol for a maximum of 15 hops (nodes). If the size of the network exceeds 15 hops then OSPF should be used.


DN70592449 Issue 2-0 en


39 (156)

Figure 16. RIP global settings

Table 9. RIP global configurable parameters

Propagate Static Routes

Static routes created in the Static Routes panel will be propagated via RIP if enabled.

Broadcast Interval The frequency of RIP announcements.

DF1/4 Blade



Default TTL This setting specifies the time-to-live (TTL) for routes that are learned from other routers through RIP. Routes that do not update before they exceed the specified TTL are marked as invalid.

Deletion Interval Specifies the amount of time a route will remain in the routing table before it expires and is removed

OSPF global settings

The Figure OSPF global settings displays OSPF as the selected protocol. This dialog displays the global configuration parameters that OSPF will use on either the LAN or WAN interfaces. Note that this figure is showing the default and recommended parameters. These parameters can be changed to interoperate with other manufacturers equipment. For further reading on OSPF please consult RFC 2328.


DN70592449 Issue 2-0 en


41 (156)

Figure 17. OSPF global settings

Table 10. OSPF global configurable parameters

Propagate Static Routes Static routes created in the Static Routes panel will be propagated via OSPF if enabled.

Router ID A 32-bit number that uniquely identifies this router in the AS (Antonymous System). This field is automatically populated with an ID derived from the system motherboard serial number and is therefore unique for the DF1/4. This can be changed to any 32 bit number but

DF1/4 Blade



must be unique within the network.

Area ID The Area ID of the area to which the attached network belongs. All routing protocol packets originating from the interface are labelled with this Area ID.

Router Priority An 8-bit unsigned integer. When two routers attached to a network both attempt to become Designated Router, the one with the highest Router Priority takes precedence. A router whose Router Priority is set to 0 is ineligible to become Designated Router on the attached network. Advertised in Hello packets sent out this interface.

Transmit Delay

The estimated number of seconds it takes to transmit a Link State Update Packet over this interface. LSAs (Link State Advertisements) contained in the Link State Update packet will have their age incremented by this amount before transmission. This value should take into account transmission and propagation delays; it must be greater than zero.

Retransmit Interval

The number of seconds between LSA retransmissions, for adjacencies belonging to this interface. Also used when retransmitting Database Description and Link State Request Packets. This parameter must have the same value set for all nodes in the network.

Hello Interval The length of time, in seconds, between the Hello packets that the router sends over the interface. This parameter must have the same value set for all nodes in the network.

Dead Interval The number of seconds before the router's neighbours will declare it down, when they stop hearing the router's Hello Packets. This parameter must have the same value set for all nodes in the network.

Configuring LAN RIP

When a LAN IP address has been entered and a connection is re-established with the node, RIP can be enabled as follows.

Send Type. Disabled, RIPv1 or RIPv2. Receive Type. RIPv1 Broadcast, RIPv2 Broadcast, RIPv2

Multicast.


DN70592449 Issue 2-0 en


43 (156)

Figure 18. System setup Networking

Enable Enable the RIP protocol for the Ethernet 2 interface.

Send Type Disabled, RIP version1 or RIP version 2.

Receive Type RIPv1 Broadcast, RIPv2 Broadcast, RIPv2 Multicast.

Configuring LAN OSPF

When a LAN IP address has been entered and a connection is reestablished with the node, OSPF can be enabled as follows.

DF1/4 Blade



Figure 19. System setup LAN

Mode Default: Passive

Set the Mode to Active if OSPF packets are required to be sent from this Interface. If the DF1/4 is required to exchange routes with another OSPF Speaker directly connected to this Interface, then Active should be selected. Otherwise, select Passive.

Cost A default Cost of 0 implies that the OSPF Shortest Path Calculations will be based on the bandwidth of the link connected to the Interface. Otherwise, the Shortest Path Calculations will be based on the face-value of the non-zero Cost. The default of 0 is


DN70592449 Issue 2-0 en


45 (156)

recommended.

Authentication Specify that simple password authentication should be used for the given area.

3.6.2.2 Networking WAN

A WAN (Wide Area Network) is a network of DF1/4 Blades connected together in one of the topologies as described in section 2.3 Topologies.

A WAN is configured so a network operator can manage DF1/4 Blade nodes over the DCC (Data Communications Channel) or via In band management alleviating the need for a separate management network.

The WAN can be configured to use static or dynamic routing. Dynamic routing is implemented using RIP (Routing Information Protocol) or OSPF.

Tip If RIP is used to provide dynamic routing, Numbered PPP links must be used.

Configuring WAN

1. Enable the interface and configure the PPP link.

PPP links are configured between adjacent 800 nodes. If static routing is used, the WAN PPP link can be configured as Unnumbered. If dynamic routing is used, then Numbered PPP interfaces must be used for RIP, numbered and unnumbered links are supported by OSPF.

Authentication is not implemented but has been included in the Multiservice Manager GUI and is reserved for future use.

DF1/4 Blade



Figure 20. DCC PPP configuration

Tip If 1+1 Protection is configured for either Linear Midspan or Terminal Mux trunking, then only DCC A and DCC C interfaces are used.

2. Configure the Link to use the DCC

The DCC link is configured to transmit management traffic in either the RSOH (Regenerator Section Overhead) or the MSOH (Multiplex Section Overhead).

RSOH and MSOH overheads are independent of the SDH payload.

It is recommended to use the MSOH for DCC links as the transmission rate is 576 Kbps, whereas the RSOH only provides 192 Kbps of capacity.

Configure the link to use an In-band communication channels.


DN70592449 Issue 2-0 en


47 (156)

The PPP links can be carried as payload rather than using the DCC if In-band is selected.

The HDLC terminations can be connected to a TU-12 (2Mb/s) for SDH.

For a TU-12 only timeslots 1-15 and 17-31 are used.

Figure 21. In-band Management Cross-connect

DF1/4 Blade



Figure 22. DCC Link configuration

3. Enable routing for the PPP interfaces

Press the Routing tab.

Global Routing options are selected and described in section Enable Routing.

OSPF or RIP will have been selected.

Routing parameters for the PPP interfaces are selected and configured as in section Configure LAN RIP and section Configure LAN OSPF.

4. Check the WAN status

When the WAN links have been configured, you can check the status in the dialog below.

Note that the DCC is reported as being up for both the A and B trunks in this example.


DN70592449 Issue 2-0 en


49 (156)

Figure 23. DCC WAN status

Troubleshooting DCC links

If you encounter problems getting the DCC links up you should try the following.

1. Check for mistakes with the IP addressing. If you have used numbered links and you have many nodes in the network, mistakes can easily be made.

2. Check that you have the correct Netmasks.

3. Configure the fist node (node A), configure the adjacent node (node B), disable and enable the DCC interface. See Configuring WAN (under Networking WAN), then disable and enable the interface on node A.

4. Check that all router IDs of the network are unique. Systen Setup -> Networking -> IP Routing

5. Reboot both the nodes.

3.6.2.3 Routing Table

The routing table is a diagnostic tool that allows a network administrator to check what routes are held by the system.

DF1/4 Blade



This tool is useful when entering static routes. If a syntactically or logically incorrect route is entered into the node, the route will not show in the routing table.

The routing table can be sorted on any of the columns by clicking the column heading.

Tip The routing table has to be manually refreshed.

Figure 24. Routing table

3.6.2.4 Routing Table Flags

Table 11. Routing table flags


DN70592449 Issue 2-0 en


51 (156)

3.6.2.5 Static Routes

Static routes are entered through the Static Routes dialog below.

A managed network of DF1/4 Blades can be configured using static routes, however, if the network topology is protected, the network will not converge in the advent of network failure and a connection to one or many nodes will be lost.

Static routes can be used in conjunction with RIP or OSPF. The network administrator will likely enter static routes into a managed network to reach networks beyond that of the gateway.

Flag Definition Description

C Connected Route A directly connected route, route to an adjacent node.

G Gateway Route Indirect route via Gateway Route via a distant node

I ICMP Route ICMP redirect dynamic route. An IP router (or other node) has updated this nodes route table with information contained in an ICMP packet for a direct route

N SNMP Route Entry via SNMP MIB II. An IP router has updated this nodes route table with information contained in an SNMP packet

O OSPF Route Route learned from OSPF. An IP router (or other node) has updated this nodes route table with information contained in an OSPF routing protocol update

P Private Route This is a route private to this node and will not be exchanged with other nodes

R RIP Route Route learned from RIP. An IP router (or other node) has updated this nodes route table with information contained in an RIP routing protocol update

S Static Route This is a route that has been manually generated or as part of the node boot sequence

T Temporary route This is a temporary route

Z Zombie route The interface that this route relates to is no longer active

? Unknown Route Route of unknown origin

DF1/4 Blade



Figure 25. Static routes dialogue

3.6.2.6 SNMP communities

SNMP see section 3.8.

3.6.2.7 Syslog

Syslog see section 3.7.2.

3.6.2.8 SNMP Trap Targets

SNMP see section 3.8.

3.6.2.9 NTP Client

The DF1/4 Blade internal time clock is derived from internal oscillators, and not from a real time clock.

While the DF1/4 Blade keeps very accurate Terrestrial time, Terrestrial time will be set to zero if powered down or the system is rebooted.

To overcome this, the node can be configured to synchronise time with a NTP (Network Time Protocol) Server.


DN70592449 Issue 2-0 en


53 (156)

Figure 26. Enabling NTP

NTP Synchronisation

If NTP is enabled, the DF1/4 Blade will attempt synchronization with a NTP server as follows.

2 minutes after application launch (about 2-1/2 minutes after power on).

Until successful, the node will reattempt synchronization at 5 minute intervals.

Once successful, synchronisation will be attempted every 24 hours.

The DF1/4 Blade will also attempt to synchronize with a NTP server when first enabled or when the IP address for the server is changed, or the Force Update button is pressed.

DF1/4 Blade



3.6.2.10 IP Routing

Figure 27. IP Routing

IP routing is configured by selecting IP Routing in the Networking tab of the System Setup dialog.

3.6.3 Users Manager

The Users Manager tab allows a network administrator to add/delete/change user profiles. The login name, level, and days remaining of all current user profiles are displayed.


DN70592449 Issue 2-0 en


55 (156)

Figure 28. Users Manager

DF1/4 Blade



Figure 29. Add User Dialogue

The factory default profile is username admin and no password. Logging in with the default admin profile will then allow the user to define a number of other profiles.

The Add User button in the Users Manager tab will allow any user logged in as a level 4 or network administrator user to create a new profile. The Add User dialog is shown in the figure above. The administrator may enter the name, password and user level of each profile.

There are six operator profiles. The Table 12 Operator profile summary displays read or access to various parts of the application.


DN70592449 Issue 2-0 en


57 (156)

Table 12. Operator profile summary

Suggested Application Guest Executive Technician

Local administrator

Network administrator Upgrade

Level 0 Level 1 Level 2 Level 3 Level 4 Level 5 ACTIVITY

R W R W R W R W R W R W

Main Multiservice Manager summary

a a a a a a a

IM configurations a a a a a a SS cross connect VC/VT a a a a a a Small DACS a a a a a a Event Log a a a a a a Trunk, APS and clock a a a a a a Initiate diagnostics a a a a a a a Set Window (IP/SNMP/time) a a a a a Reboot IM a a a a User accounts Management a a Upgrade a a aDevice List a a a aReboot Node a a a a

Tip Guest is a special profile that might be used by a non employee such as a contractor. In addition, this profile has a hard coded 10 second timeout after use.

DF1/4 Blade



3.6.4 System upgrade and backup

The Utilities tab allows administrations to execute software system reboots, backup and restore of system configuration and the ability to reset the node to Factory Default.

Figure 30. System setup Utilities

Pressing the Upgrade Node button will bring up a window that allows users to select an upgrade package (Service Pack) file (*.HPK) to run a software upgrade on the DF1/4 Blade. A reboot of the node will be required after the new software is installed.


DN70592449 Issue 2-0 en


59 (156)

Caution Uninstalling old service packs will prevent the management of DF1/4 Blade units with the old service pack.

Tip You must be logged onto the node with Level 5 (Upgrade) privileges. See section Users Manager.

The Backup button allows the user to backup by saving the complete network configuration.

The Restore button allows a previously saved node configuration to be loaded and will replace the current configuration. After loading a reboot is requested by the GUI. The restore feature can simplify the roll out of a large network as a configuration template can be created and imported into each node. Minor node specific address changes will need to be made to each node prior to activation.

The Factory Default button will remove any configuration information supplied and reset the node to the same configuration state as when the node was manufactured.

3.6.5 System downgrade

The node can be downgraded by installing an earlier or previous service pack. The procedure is exactly the same as upgrading a node. See section System upgrade and backup.

3.6.6 General

The general property of the system setup allows the user to Save Position on Exit and Display Tooltips. Refer to the figure below.

DF1/4 Blade



Figure 31. System setup General dialogue

Save Position on Exit: The user has the ability to alter the size and the position of the main window of Multiservice Manager. Save Position on Exit allows the user to save the size and placement of the main window therefore after exiting and re-opening Multiservice Manager, the position and size has not changed.

Display Tooltips: Enables and disables mouse over Tooltips. Usually found on interface ports and the Cross Connect window.

Default Button: Enables both properties, Save Position on Exit and Display Tooltips.

3.7 System Event Logging

System Event logging is implemented in the DF1/4 Blade via the following methods:

Multiservice Manager Event Log (see section 3.7.1) Syslog (see section 3.7.2) SNMP traps (see section 3.8) All events generated by the DF1/4 Blade, are shown in the Event

Log and are sent as Syslog messages. See Syslog below.


DN70592449 Issue 2-0 en


61 (156)

The Event Log acts as a FIFO (First In First Out) buffer. As the buffer has a finite amount of capacity to save event notifications, old events will be dropped to make way for new events. If the network operator wishes to save a history of events, this is best achieved with the use of Syslog.

3.7.1 Multiservice Manager Event Log

Multiservice Manager includes an Event Log that reports all system events and alarms generated by the connected node. See Figure Multiservice Manager Event Log All Events.

To view the event log: Log into a DF1/4 Blade and press the Event Log button at the top left of the main screen.

Refresh the event log: When the Event Log is first opened, the contents of the event list will be empty until the log is refreshed. The log is refreshed by clicking the refresh button in the top right hand side of the dialog.

3.7.1.1 Event categories

The event log can display all events in a single list, or can display system events/alarms in predefined categories by selection of the appropriate tab in the Event Log dialog.

The Event Log categories are shown in the Alarm categories table.

Table 13. Alarm categories

Port Alarms Alarms that occur on any interface port.

System Alarms Any alarm generated by the DF1/4 Blade internal system.

SDH Alarms Alarms that correspond to any SDH specific event, excluding Protection switching and SDH clock alarms.

Clock Alarms Alarms that relate to SDH clock source (synchronisation clock)

APS Alarms Alarms that report SDH Protection Switching events.

Users Any user event recorded by the system. Example: Logging in or out of the system.

DF1/4 Blade



3.7.1.2 Interpreting the Event Log

Multiservice Manager uses the icons in shown in the table below to easily convey the meaning and severity of system events and alarms.

Table 14. Multiservice Manager Event Log Icons

ICON Colour Description

Red Alarm severity - Critical

Yellow Alarm severity - Minor

Green Alarm severity - Normal (no alarm)

Gray Alarm severity - Disabled or alarms masked by other alarms.

White Alarm severity - Informational

Interface Module Event - Information

Information - General

Root event - First line of the event log (root of the tree).

Scripting Event

Session (communications) event

System generated

Time stamp

User log in

User log out


DN70592449 Issue 2-0 en


63 (156)

Figure 32. Multiservice Manager Event Log All Events

The Event Log can also be saved as a text file for analysis at a later date.

3.7.2 Syslog

The DF1/4 Blade can be configured as a Syslog client to send Syslog messages to a Syslog server. The Syslog server would under most circumstances be a management console used to perform network and element management for a network of DF1/4 Blades.

DF1/4 Blade



Configuring Syslog

Syslog is configured from the main screen via:

System Setup Networking Tab Syslog 1. Enter the IP Address of the Syslog server to receive the messages.

2. Choose a Facility Code to append and categorise your messages.

3.7.2.1 Syslog server

Below is a screen shot of a free Syslog server configured to receive Syslog messages from a DF1/4 Blade. The server, Kiwi Syslog Daemon, is freely available over the internet.

For further information on the workings of Syslog please consult RFCs 3164, 3195.

Figure 33. Syslog message capture


DN70592449 Issue 2-0 en


65 (156)

3.8 SNMP

SNMP (Simple Network Management Protocol) Version 1 is implemented in the DF1/4 Blade to execute system configuration (gets and sets), and to receive status information about the nodes as alarms (traps).

3.8.1 DF1/4 Blade SNMP MIB

DF1/4 Blades ship with an accompanying MIB (Management Information Base) which describes all SNMP objects.

The MIB, is an ASCII text file that describes SNMP network elements (DF1/4 Blade nodes) as a list of data objects, using Descriptors and Identifiers. Think of it as a dictionary of the SNMP language, every object referred to in an SNMP message must be listed in the MIB.

The fundamental purpose of the MIB is to translate numerical strings into human-readable text. When an SNMP device sends a Trap or other message, it identifies each data object in the message with a number string called an object identifier, or OID. The MIB provides a text label for each OID. Your SNMP manager uses the MIB as a codebook for translating the OID numbers into a human-readable display.

DF1/4 Blade MIB can be downloaded from NOLS.

3.8.2 SNMP communities

SNMP communities are used to define and set system access privileges.

SNMP communities are created and assigned read, write or read/write privileges.

The DF1/4 Blade factory default community name is: public with read access.

Configuring SNMP communities

System Setup Networking Tab SNMP Communities 1. Enter a Community name.

2. Assign read, write or read/write access.

DF1/4 Blade



Figure 34. SNMP communities

3.8.3 Configure a DF1/4 Blade using SNMP

DF1/4 Blades can be fully configured via SNMP Version 1. All system options (configuration items) that are set using Multiservice Manager can also be set via SNMP.

To configure a DF1/4 Blade via SNMP, a copy of the DF1/4 Blade MIB must loaded or compiled into a SNMP manager. The manager will display a list of MIB objects graphically as an inverted spanning tree.

It is beyond the scope of this manual to cover all MIB objects in detail. If you require further information, compile or load the MIB into a SNMP manager. Or you can read the object descriptions and identifiers directly by opening the MIB with a text editor/viewer.


DN70592449 Issue 2-0 en


67 (156)

Tip DF1/4 Blades can only be configured via SNMP if a community name created and is assigned write access. The SNMP manager communicates with the node using the same community name. Read access is also required to be able to validate any configuration changes made.

3.8.4 DF1/4 Blade Traps

The DF1/4 Blade sends some alarm notifications as SNMP Traps. In a managed network, traps are sent from many nodes to a single management console. This allows the network operator to manage one to many networks from a centralised location.

Intelligence can also be built into a managed network with the use of SNMP management software. The software can be configured to create relationships between network elements providing a network centric view which will identify running services, and not isolated nodes.

Traps are more likely to be of interest to network operators, so a description of DF1/4 Blades traps is included in this manual. These descriptions can also be read directly from the MIB.

Table 15. DF1/4 Blade SNMP Trap descriptions

SNMP Trap Description

hpx800SystemAlarmNotification Indicates a state change in the systemAlarmStatus object.

hpx800SdhSonetClockSwitch Indicates SDH clocking has switched to a different source.

hpx800SwitchActiveLine Indicates the receiving line switched over to another line.

hpx800SwitchActivePath Indicates the receiving path has switched over to another channel

hpx800SectionAlarmNotification Indicates a state change in the value of the sectionCurrentAlarmStatus object, caused by a bit changing from 0 to 1 (alarm triggered) or 1 to 0 (alarm cleared).

hpx800LineAlarmNotification Indicates a state change in the value of the lineCurrentAlarmStatus object, caused by a bit changing from 0 to 1 (alarm triggered) or 1 to 0 (alarm cleared).

hpx800PathAlarmNotification Indicates a state change in the value of the pathCurrentAlarmStatus object, caused by a bit changing from 0 to 1 (alarm triggered) or 1 to 0 (alarm cleared).

hpx800VtAlarmNotification Indicates a state change in the value of the vtCurrentAlarmStatus object, caused by a bit changing from 0 to 1 (alarm triggered) or 1

DF1/4 Blade



SNMP Trap Description to 0 (alarm cleared).

hpx800E1AlarmNotification Indicates a change in the value of any E1 alarm.

hpx800EthernetAlarmNotification Indicates a change in the value of any Ethernet alarm.

hpx800Ds3AlarmNotification Indicates a change in the value of any DS3 alarm.

hpx800E1BitsAlarmNotification Indicates a change of the E1 Bits alarm.

hpx800StmAlarmNotification Indicates a change of STM-n/OC-n alarm.

hpx800FanSpeedChangeNotification Indicates a change of fan speed.

3.8.4.1 Setting SNMP trap targets

To receive SNMP Traps the DF1/4 Blade must be configured with one or more IP addresses of a SNMP manager (or other trap receiving software) running on a computer that is reachable via TCP/IP. See the figure below.

Figure 35. SNMP trap targets


DN70592449 Issue 2-0 en


69 (156)

3.8.4.2 Receiving DF1/4 Blade traps

For smaller networks, a functionally rich and expensive management system may not be necessary, or may not be cost effective.

Many free trap receivers are available over the internet and may be used to receive alarm notifications. Most free trap receivers will load or compile the DF1/4 Blade MIB and will produce human readable notifications.

3.9 System Alarms

3.9.1 Service LEDs

Three LEDs are provided for on the front panel (in the handle) of the unit. There is one each of a red LED, a yellow Led and a green LED. The activation of these LEDs is based on the alarm conditions listed in the previous section.

LED Function

Green When the unit is being accessed by a management session or command line interface (CLI).

Yellow When the unit has detected a fault outside the equipment (the incoming signal may be faulty, for example). Some of the services may still be functioning quite normally and further actions are needed for locating the fault.

Red When the unit has detected a serious problem such as an incorrect supply voltage, over temperature alarm or if the unit has failed to boot completely. (The red LED activates by default when the unit is powered on and is extinguished once the system has booted successfully).

DF1/4 Blade



3.10 Rack Alarms

Rack alarm A: indicates that the equipment performance does not fulfill the specifications and that the equipment requires immediate service activities. Prompt alarm, faults preventing the use of the equipment.

Rack alarm B: indicates that the system performance has weakened; however, the equipment is still able to transmit information. Deferred alarm, faults that impair the performance of the equipment but do not prevent the operation of the equipment.

Rack alarm D: When activated, rack alarm D inhibits rack alarms A and B from being placed on the backplane.

Rack alarm D is controlled from a button on the front panel of the GUI.

The following logic statements apply:

Rack A alarm appears on the backplane when the condition to activate Alarm A exists AND Rack Alarm D is NOT activated

Rack B alarm appears on the backplane when the condition to activate Alarm B exists AND Rack Alarm D is NOT activated

When rack alarm A or B is active and rack alarm D is not active, the respective signal is passed to the backplane and indicates that there is a fault on a card in the subrack that requires attention.

Note that just because Alarm D is activated, it does not necessarily mean that Alarm A or Alarm B condition exists.

When rack alarm D is active, it indicates that a user has placed a temporary cancellation on rack A and B alarm. This means that no matter what fault is currently on the card or subsequently occurs on the card that enabled the alarm cancellation, the card will not cause rack A or B alarms to activate. In this state, Service LEDs are still active and function as normal.

Temporary cancellation means that if the card is reset, then rack alarm D returns to its off state Alarms A and B are propagated through to the backplane as normal.

Rack alarms A and B do not activate unless the alarm condition remains for more than 3 seconds.

Conversely, Rack alarms A and B will not clear down until the relevant alarm condition remains clear for more than 3 seconds.

The following rack alarms are represented.

Table 16. Rack alarms


DN70592449 Issue 2-0 en


71 (156)

Fault Condition Rack alarm Service LEDs

Loss of power supply A Red

Equipment Reset A Red

Test mode (self test) No rack alarm Red

System Alarm (Red) A Yellow

System Alarm (Yellow) B Yellow

Fault Condition Explanation

Loss of power supply: self explanatory Equipment Reset: Node is booting up boot kernel Test mode (self test): Node is loading firmware or going through

self test on boot up

System Alarm: This is the alarm summary indicator located at the top left hand corner in Multiservice Manager. It changes state whenever there is any alarm present on the node.

When the system alarm is in a red (major alarm) state, then rack alarm A and service LED Yellow will be enabled.

When the system alarm is in a yellow (minor alarm) state, then rack alarm B and service LED Yellow will be enabled.

When the system alarm is in a green (normal) state, then no rack alarm or service LED is enabled

The user will then have to connect to the DF1/4 Blade in Multiservice Manager to find out which alarm is currently active.

The reason why no SDH specific alarms are included here is because there are four SDH trunks on the DF1/4. According to rack alarm and service LED usage it would be too complex and time consuming to write up alarm outputs for variations of when which rack alarm should be active under different trunk and circuit circumstances. Using the System Alarm will cover any issues that may occur in the trunk, circuit or service ports.

3.11 V.11 Master slave serial data transmission (Q1 support)

The DF1/4 Blade supports the transparent transmission of serial data via 2 V.11 interfaces in a master slave topology. The serial data is

DF1/4 Blade



transmitted over the DCC and can be broken out in any or all nodes in a DF1/4 Blade network.

The DF1/4 Blade does not implement a master slave or SCADA like protocol, it implements the broadcasting of serial data from a master to one to many slaves. A higher level protocol running over the master slave topology will provide the means by which each slave will know when to respond to the master.

V.11 Port specifications

Pin 2 Receive A (+) (output)

Pin 3 Transmit A (+) (input)

Pin 4 Transmit B (-) (input)

Pin 5 Receive B (-) (output)

Figure 36 V.11 Port specifications

V.11 Port configuration

The two V.11 ports are pre-configured as:

Even Parity 8 Data bits 1 Stop Bit The following data transmission rates are supported: 75, 150, 300, 600, 1200, 2400, 4800, 9600 bit/s.

V.11 Master slave configuration

Each of the 2 V.11 ports can be configured as a master or a slave. This is achieved by clicking either 1 or 2 to configure the V.11 ports. See Figure V.11 Master slave configuration.


DN70592449 Issue 2-0 en


73 (156)

Figure 37. V.11 Master slave configuration

V.11 Port configuration dialog

Tip Always configure the master port before configuring any slaves.

Configure port as a master

1. Select Master from the drop down list

2. Select Serial Baud rate

DF1/4 Blade



3. Create a Group ID. The group ID is created for administration purposes and allows the network administrator to create logical groups.

4. Add the IP address for the Slave IPs the master will broadcast to.

Figure 38. Configuring master

Configure port as a slave

1. Select Slave from the drop down list


DN70592449 Issue 2-0 en


75 (156)

2. Select Serial Baud rate

3. Create a Group ID. The Group ID is created for administration purposes and allows the network administrator to create logical groups.

Figure 39. Configuring slave

DF1/4 Blade



Master Slave Example

Figure 40. Master slave example

Table 17. Master slave example

Parameter Master Slave 1 Slave 2 Slave 3

LAN IP 10.200.1.1 10.201.22.1 10.201.23.1 10.201.24.1

Mode Master Slave Slave Slave

Group ID 111 111 111 111

Serial Baud 9600 9600 9600 9600

Slave IPs 10.201.22.1

10.201.23.1

10.201.24.1

N/A N/A N/A


DN70592449 Issue 2-0 en


77 (156)

3.12 Example: A Managed Network

The Figure Example Network shows how to configure the DCC PPP links and demonstrates a numbering scheme.

Trunks must be configured before configuring the network. See section Configuring services for a detailed description.

The example uses /30 subnets (netmask = 255.255.255.252) to demonstrate efficient use of network addresses.

The management console (PC) connected to the gateway node will need to be on the same class C network in order to communicate with the DF1/4 Blade ring: For this example 10.10.10.0

The following network functions can be added to Windows XP/2000 to enhance their capabilities as a management console.

NTP Local Server RIP Listener IP Forwarding (Routing)

3.12.1 Local NTP server Windows XP/2000

NTP server is enabled so each node in the network can synchronise time.

1. Open your registry

2. Edit the key [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters]

3. Create a new DWORD value, or modify the existing value, called "LocalNTP" and set it to:

0 = disabled, 1 = enabled.

4. Exit your registry; reboot Windows for the change to take effect.

3.12.2 RIP Listener Windows XP/2000

RIP listener is enabled so the management console is able to learn the routes of the DF1/4 Blade network.

1. In control panel, select Add or Remove Programs.

2. Choose Add/Remove Windows Components.

3. In the Windows Components Wizard, select Networking Services.

DF1/4 Blade



4. Go to Details.

5. Click the RIP Listener check box.

6. Click OK, then click Next.

3.12.3 IP Forwarding (Routing) Windows XP/2000

Routing may be enabled so the management console can forward packets to other networks.

1. Open your registry.

2. Edit the key [HKEY_LOCAL_MACHINE\SYSTEM\ CurrentControlSet\Services\Tcpip\Parameters ]

3. Create a new DWORD value, or modify the existing value, called "IpEnableRouter" and set it to:

0 = disabled, 1 = enabled.

4. Exit your registry; you may need to restart or log out of Windows for the change to take effect.


DN70592449 Issue 2-0 en


79 (156)

DF1/4 Blade



Figure 41. Example Network

3.13 Configuring services

The configuration of DF1/4 Blade services can be completed in three steps;

Trunk Tributaries Cross connect

3.13.1 Trunk

Configuration of the trunk interfaces sets the parameters for trunk ports A, B, C and D.

From the Multiservice Manager main screen select the Trunk button and select the required trunk parameters:

Type - Framing Protocol Setting the framing to SDH also sets the circuit interfaces to

E1

Data Rate Ports A and B operate at 155Mbps only Ports C and D operate at 155Mbps or 622Mbps

Topology Terminal mode ports can be set independently Terminal mode, protected ports are grouped in

Working/Protection pairs A + B and C + D

Ring mode, protected ports are grouped in West/East pairs A + B and C + D

Linear mid-span groups all four protected ports and limits data rate to 155Mbps

Protection In terminal or mid-span, protection is 1+1 Multiplexer or Line

switched


DN70592449 Issue 2-0 en


81 (156)

In ring mode, protection is path based SNCP or UPSR and requires additional configuration at each High Order or Low order path level as the network architecture demands.

Figure 42. Trunk dialogue

DF1/4 Blade



3.13.2 Physical fibre connections

3.13.2.1 SFP information

The optical trunks consist of SFP (Small Form-Factor Pluggable-Transceiver) modules that have Transmitters on the left and a Receiver on the right.

Figure 43. Front panel


DN70592449 Issue 2-0 en


83 (156)

The SFPs can be interrogated to display generalised static information such as vendor, or Digital Diagnostic Monitoring Interface (DDMI) such as receive power level in real time.

General Information is available by hovering over Ethernet 3 &4 or Trunk A, B, C, and D port configuration dialog button, or by clicking the button and opening the port configuration dialog. It can also be viewed via the main menu. See Table 18 SFP General Information for a list of the fields displayed. The hexadecimal form (raw form) and textual form of General Information is also available in the System Info dialog of the main menu. Select System System Info.

Table 18. SFP General Information

Label Description

Identifier Type of Transceiver

Connector type The external connector type for the media interface on the transceiver

Encoding Serial encoding algorithm used by transceiver

Nominal Nominal signalling rate

Vendor name Vendor name

Vendor OUI Vendors IEEE company ID

Vendor PN Part number provided by Vendor

Vendor rev Revision level for part number provided by vendor

Wavelength Laser wavelength

Vendor SN Serial number provided by vendor

Date Code Vendors manufacturing date code

Supported Link Lengths Link length supported for different mediums

NSN supported DDMI SFPs

NSN

Documents

DF 1-4 Manual Book