Vous êtes sur la page 1sur 156

C32391.

20--B0

DF1/4 Blade
User Manual, v.2

DN70592449
Issue 2-0 en

Nokia Siemens Networks

1 (156)

DF1/4 Blade

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.

2 (156)

Nokia Siemens Networks

DN70592449
Issue 2-0 en

Contents

Contents

DN70592449
Issue 2-0 en

Introduction ............................................................................................5

2
2.1
2.1.1
2.2
2.3
2.3.1
2.3.2
2.4
2.5
2.6
2.7
2.8
2.9

Installation ..............................................................................................7
Site requirements .....................................................................................8
Mechanics and power ..............................................................................8
Site environment ......................................................................................8
Preventive site configuration: maintaining normal operation....................9
General precautions .................................................................................9
Power considerations .............................................................................10
Safety recommendations........................................................................10
Safety with electricity..............................................................................10
Preventing electrostatic discharge damage ...........................................11
Safety with laser radiation ......................................................................11
Dimensions ............................................................................................13
Product labelling.....................................................................................14

3
3.1
3.1.1
3.1.2
3.2
3.3
3.4
3.4.1
3.4.2
3.4.3
3.5
3.5.1
3.5.2
3.5.3
3.5.4
3.5.5
3.5.6
3.5.7
3.5.8
3.6
3.6.1
3.6.2
3.6.3
3.6.4
3.6.5
3.6.6
3.7
3.7.1
3.7.2

Setup and configuration ......................................................................15


Connections ...........................................................................................15
Front panel .............................................................................................15
System Reset / System Boot..................................................................16
Interfaces ...............................................................................................18
Topologies..............................................................................................18
Implementation.......................................................................................20
Framing and tributary mapping ..............................................................20
Trunk protection .....................................................................................21
Trunks and tributaries.............................................................................21
Provisioning............................................................................................22
Multiservice Manager installation ...........................................................22
Physical setup ........................................................................................22
USB driver installation ............................................................................25
Connecting to the DF1/4 Blade ..............................................................25
Command line options............................................................................27
User login ...............................................................................................28
Installation required information ..........................................................29
Multiservice Manager user interface ......................................................30
System setup .........................................................................................34
System ...................................................................................................34
Networking .............................................................................................35
Users Manager.......................................................................................54
System upgrade and backup..................................................................58
System downgrade.................................................................................59
General ..................................................................................................59
System Event Logging ...........................................................................60
Multiservice Manager Event Log ............................................................61
Syslog ....................................................................................................63

Nokia Siemens Networks

3 (156)

DF1/4 Blade

4 (156)

3.8
3.8.1
3.8.2
3.8.3
3.8.4
3.9
3.9.1
3.10
3.11
3.12
3.12.1
3.12.2
3.12.3
3.13
3.13.1
3.13.2
3.13.3
3.14
3.14.1
3.14.2
3.15
3.15.1
3.15.2
3.16
3.16.1
3.16.2
3.16.3
3.17
3.17.1

SNMP .................................................................................................... 65
DF1/4 Blade SNMP MIB........................................................................ 65
SNMP communities ............................................................................... 65
Configure a DF1/4 Blade using SNMP .................................................. 66
DF1/4 Blade Traps ................................................................................ 67
System Alarms ...................................................................................... 69
Service LEDs......................................................................................... 69
Rack Alarms .......................................................................................... 70
V.11 Master slave serial data transmission (Q1 support)...................... 71
Example: A Managed Network .............................................................. 77
Local NTP server Windows XP/2000 .................................................... 77
RIP Listener Windows XP/2000 ............................................................ 77
IP Forwarding (Routing) Windows XP/2000 .......................................... 78
Configuring services .............................................................................. 80
Trunk ..................................................................................................... 80
Physical fibre connections ..................................................................... 82
Tributary interfaces................................................................................ 89
Trunk and Data Path Configuration ..................................................... 127
SDH Alarms......................................................................................... 127
Trail Trace Identifier............................................................................. 135
Network protection............................................................................... 136
MSP/1+1 Automatic Protection Switch ................................................ 137
UPSR/SNCP Automatic protection switch........................................... 139
Clock.................................................................................................... 140
Clock hierarchy.................................................................................... 143
Clock types .......................................................................................... 143
SSM..................................................................................................... 143
Troubleshooting................................................................................... 144
USB driver installation on Windows XP............................................... 144

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

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

Nokia Siemens Networks

DN70592449
Issue 2-0 en

Introduction

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.

DN70592449
Issue 2-0 en

Nokia Siemens Networks

5 (156)

DF1/4 Blade

6 (156)

Nokia Siemens Networks

DN70592449
Issue 2-0 en

Installation

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

Figure 1.

DN70592449
Issue 2-0 en

DF1/4 Blade installed in NDM 8-slot Subrack

Nokia Siemens Networks

7 (156)

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 nonoperating 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 nonoperating and storage

-25 degrees Celsius

70 degrees Celsius

Humidity, ambient (noncondensing) operating

10%

90%

Humidity, ambient (noncondensing) non-operating and

5%

95%

8 (156)

Nokia Siemens Networks

DN70592449
Issue 2-0 en

Installation

Min

Max

Altitude, operating and


nonoperating

Sea level

2,000 meters

Vibration, operating

5 to 200 Hz

storage

0.5 g (1 oct./min.)
Vibration, nonoperating
DC power

5 to 200 Hz,

200 to 500 Hz

1 g (1 oct./min.)

2 g (1oct./min.)

-20 Volts DC

-72 Volts DC

(nominal -48 VDC)

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:

DN70592449
Issue 2-0 en

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.

Nokia Siemens Networks

9 (156)

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.

10 (156)

Nokia Siemens Networks

DN70592449
Issue 2-0 en

Installation

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.

DN70592449
Issue 2-0 en

Nokia Siemens Networks

11 (156)

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.

12 (156)

Nokia Siemens Networks

DN70592449
Issue 2-0 en

Installation

2.8

Dimensions

Figure 2.

DN70592449
Issue 2-0 en

DF1/4 Blade dimensions

Nokia Siemens Networks

13 (156)

DF1/4 Blade

Table 2.

2.9

DF1/4 Blade dimensions

Max

Mm

Height

233

Width

42

Depth

197

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

14 (156)

Model number

Serial number

Nokia Siemens Networks

DN70592449
Issue 2-0 en

Setup and configuration

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.

DN70592449
Issue 2-0 en

Nokia Siemens Networks

15 (156)

DF1/4 Blade

Figure 3.

3.1.2

DF1/4 Blade front panel

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

16 (156)

Hardware Reset Switch

Nokia Siemens Networks

DN70592449
Issue 2-0 en

Setup and configuration

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.

DN70592449
Issue 2-0 en

Nokia Siemens Networks

17 (156)

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.

18 (156)

Nokia Siemens Networks

DN70592449
Issue 2-0 en

Setup and configuration

DN70592449
Issue 2-0 en

Figure 4.

Terminal Mode and Protected Ring

Figure 5.

Linear Midspan and Ring Ring

Nokia Siemens Networks

19 (156)

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.

STM-4

AUG-4
X1

STM-1

X4 X1
AUG-1

AU-4

VC-4

VC-4

TUG-3

140
T3-44.736
E3-34.368

X3

X1

X1

TU-3

VC-3

C-3

TUG-2

Aligning
Mapping
Multiplexing
AU-4

Figure 6.

20 (156)

E1-2.048

X3
TU-12

VC-12

C-12

Pointer processing

SDH mapping

Nokia Siemens Networks

DN70592449
Issue 2-0 en

Setup and configuration

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 VC12s

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.

DN70592449
Issue 2-0 en

Nokia Siemens Networks

21 (156)

DF1/4 Blade

3.5

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

3.5.1

Installing software

Physical setup

Installing USB drivers

Connecting to the DF1/4 Blade

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

22 (156)

Nokia Siemens Networks

192.168.0.1

DN70592449
Issue 2-0 en

Setup and configuration

Ethernet port #2

Nokia DF 1/4 Blade

USB Type B Port

USB Type A to
USB Type B
Cable

Ethernet CAT5
cross-over cable

Management PC
running Multiservice
Manager
USB Type A Port

Ethernet interface

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.

DN70592449
Issue 2-0 en

Nokia Siemens Networks

23 (156)

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

+5 volts

Data -

Data +

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.

24 (156)

Nokia Siemens Networks

DN70592449
Issue 2-0 en

Setup and configuration

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.

DN70592449
Issue 2-0 en

Nokia Siemens Networks

25 (156)

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

26 (156)

Nokia Siemens Networks

DN70592449
Issue 2-0 en

Setup and configuration

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.

The Automatic Connect control, if checked will immediately commence


a connection on closure of this window.

3.5.5

Command line options


DF1/4 Blade will display all available command line options by using the
following switch and invoking the application from the command shell.
C:\Program Files\Nokia Siemens Networks\
Multiservice Manager\MultiserviceManager /help

Table 5 lists DF1/4 Blades command line switches.

DN70592449
Issue 2-0 en

Nokia Siemens Networks

27 (156)

DF1/4 Blade

Table 5.

DF 1/4 Blade command line switches

Command line switch

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

where Str is the SDH/SONET cross connect file name

/EVCross Str

where Str is the EV cross connect file name

/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

to auto backup from the addressed node

/Help

display this help screen

Note
To use the /backup switch use the following syntax:
C:\Program Files\Nokia Siemens Networks\
Multiservice Manager\MultiserviceManager /ip
192.168.1.1 /user admin:my password /backup

If a password has not been set for a user on the DF1/4 Blade, omit
mypassword from the command line.

3.5.6

User login
All users must log in with a username and password in order to connect
to a Nokia Siemens Networks node for management and configuration.
The login screen is shown below.

28 (156)

Nokia Siemens Networks

DN70592449
Issue 2-0 en

Setup and configuration

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:

DN70592449
Issue 2-0 en

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.

Nokia Siemens Networks

29 (156)

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.

30 (156)

Multiservice Manager Main Screen (default layout)

Nokia Siemens Networks

DN70592449
Issue 2-0 en

Setup and configuration

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.

DN70592449
Issue 2-0 en

Nokia Siemens Networks

31 (156)

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

System

SDH

View

Help

Connect

System Setup

Trunk

Toolbars

Help Index

Disconnect

Event Log

Cross Connect

Connection

Connection Setup

System Info

Clock

System

About Multiservice
Manager

Exit

Backup

Section Alarms

Customise

Restore

Port A

Status Bar

32 (156)

Nokia Siemens Networks

DN70592449
Issue 2-0 en

Setup and configuration

Reboot

Port B

Panels

Port C

Alarms

Port D

SDH/SONET
Status

HO Alarms
Port A
Port B
Port C
Port D
LO Alarms

SDH/SONET
History
Layout
Default
Save to file
Load From File

Port A
Port B
Port C
Port B
Clear Alarm
History
Reset Statistics
Clear APS History
Rack Alarm
Cancellation
The Connection
menu provides
commands to
configure all
connection details
and to connect or
disconnect from
nodes in the
network.

DN70592449
Issue 2-0 en

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.

Nokia Siemens Networks

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.

33 (156)

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.

3.6.1

System setup dialogue

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.

34 (156)

Nokia Siemens Networks

DN70592449
Issue 2-0 en

Setup and configuration

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

DN70592449
Issue 2-0 en

Nokia Siemens Networks

35 (156)

DF1/4 Blade

Config Item

Description
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

See Section

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

36 (156)

Nokia Siemens Networks

DN70592449
Issue 2-0 en

Setup and configuration

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.

DN70592449
Issue 2-0 en

Nokia Siemens Networks

37 (156)

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.

38 (156)

Nokia Siemens Networks

DN70592449
Issue 2-0 en

Setup and configuration

DN70592449
Issue 2-0 en

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.

Nokia Siemens Networks

39 (156)

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.

40 (156)

Nokia Siemens Networks

DN70592449
Issue 2-0 en

Setup and configuration

DN70592449
Issue 2-0 en

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

Nokia Siemens Networks

41 (156)

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 reestablished with the node, RIP can be enabled as follows.

42 (156)

Send Type. Disabled, RIPv1 or RIPv2.

Receive Type. RIPv1 Broadcast, RIPv2 Broadcast, RIPv2


Multicast.

Nokia Siemens Networks

DN70592449
Issue 2-0 en

Setup and configuration

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.

DN70592449
Issue 2-0 en

Nokia Siemens Networks

43 (156)

DF1/4 Blade

Figure 19.

Mode

System setup LAN

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

44 (156)

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

Nokia Siemens Networks

DN70592449
Issue 2-0 en

Setup and configuration

recommended.
Authentication

3.6.2.2

Specify that simple password authentication should be used for


the given area.

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.

DN70592449
Issue 2-0 en

Nokia Siemens Networks

45 (156)

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.

46 (156)

Nokia Siemens Networks

DN70592449
Issue 2-0 en

Setup and configuration

The PPP links can be carried as payload rather than using the DCC if Inband 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.

DN70592449
Issue 2-0 en

In-band Management Cross-connect

Nokia Siemens Networks

47 (156)

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.

48 (156)

Nokia Siemens Networks

DN70592449
Issue 2-0 en

Setup and configuration

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.

DN70592449
Issue 2-0 en

Nokia Siemens Networks

49 (156)

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.

3.6.2.4

Routing Table Flags

Table 11.

50 (156)

Routing table

Routing table flags

Nokia Siemens Networks

DN70592449
Issue 2-0 en

Setup and configuration

Flag

Definition

Description

Connected Route

A directly connected route, route to an adjacent node.

Gateway Route

Indirect route via Gateway Route via a distant node

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

SNMP Route

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

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

Private Route

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

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

Static Route

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

Temporary route

This is a temporary route

Zombie route

The interface that this route relates to is no longer active

Unknown Route

Route of unknown origin

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.

DN70592449
Issue 2-0 en

Nokia Siemens Networks

51 (156)

DF1/4 Blade

Figure 25.

3.6.2.6

Static routes dialogue

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.

52 (156)

Nokia Siemens Networks

DN70592449
Issue 2-0 en

Setup and configuration

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.

DN70592449
Issue 2-0 en

Nokia Siemens Networks

53 (156)

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.

54 (156)

Nokia Siemens Networks

DN70592449
Issue 2-0 en

Setup and configuration

Figure 28.

DN70592449
Issue 2-0 en

Users Manager

Nokia Siemens Networks

55 (156)

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.

56 (156)

Nokia Siemens Networks

DN70592449
Issue 2-0 en

Setup and configuration

Table 12.

Suggested
Application
ACTIVITY
Main
Multiservice
Manager
summary

Operator profile summary

Guest

Executive

Technician

Local
administrator

Network
administrator

Upgrade

Level 0

Level 1

Level 2

Level 3

Level 4

Level 5

IM
configurations

SS cross
connect VC/VT

Small DACS

Event Log

Trunk, APS and


clock

Initiate
diagnostics

Set Window
(IP/SNMP/time)

User accounts
Management

Upgrade

a a

a a

a
a

Reboot IM

Device List

Reboot Node

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.

DN70592449
Issue 2-0 en

Nokia Siemens Networks

57 (156)

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.

58 (156)

Nokia Siemens Networks

DN70592449
Issue 2-0 en

Setup and configuration

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.

DN70592449
Issue 2-0 en

Nokia Siemens Networks

59 (156)

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:

60 (156)

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.

Nokia Siemens Networks

DN70592449
Issue 2-0 en

Setup and configuration

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.

DN70592449
Issue 2-0 en

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.

Nokia Siemens Networks

61 (156)

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.

ICON

Multiservice Manager Event Log Icons

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

62 (156)

Nokia Siemens Networks

DN70592449
Issue 2-0 en

Setup and configuration

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.

DN70592449
Issue 2-0 en

Nokia Siemens Networks

63 (156)

DF1/4 Blade

Configuring Syslog

Syslog is configured from the main screen via:


System Setup Networking Tab Syslog

3.7.2.1

1.

Enter the IP Address of the Syslog server to receive the messages.

2.

Choose a Facility Code to append and categorise your messages.

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.

64 (156)

Syslog message capture

Nokia Siemens Networks

DN70592449
Issue 2-0 en

Setup and configuration

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.

DN70592449
Issue 2-0 en

Nokia Siemens Networks

65 (156)

DF1/4 Blade

Figure 34.

3.8.3

SNMP communities

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.

66 (156)

Nokia Siemens Networks

DN70592449
Issue 2-0 en

Setup and configuration

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

DN70592449
Issue 2-0 en

Nokia Siemens Networks

67 (156)

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.

68 (156)

SNMP trap targets

Nokia Siemens Networks

DN70592449
Issue 2-0 en

Setup and configuration

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.

DN70592449
Issue 2-0 en

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

Nokia Siemens Networks

69 (156)

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.

70 (156)

Rack alarms

Nokia Siemens Networks

DN70592449
Issue 2-0 en

Setup and configuration

Fault Condition

Rack alarm

Service LEDs

Loss of power supply

Red

Equipment Reset

Red

Test mode (self test)

No rack alarm

Red

System Alarm (Red)

Yellow

System Alarm (Yellow)

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

DN70592449
Issue 2-0 en

Nokia Siemens Networks

71 (156)

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.

72 (156)

Nokia Siemens Networks

DN70592449
Issue 2-0 en

Setup and configuration

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

DN70592449
Issue 2-0 en

1.

Select Master from the drop down list

2.

Select Serial Baud rate

Nokia Siemens Networks

73 (156)

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.

74 (156)

Select Slave from the drop down list

Nokia Siemens Networks

DN70592449
Issue 2-0 en

Setup and configuration

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.

DN70592449
Issue 2-0 en

Configuring slave

Nokia Siemens Networks

75 (156)

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

N/A

N/A

N/A

10.201.23.1
10.201.24.1

76 (156)

Nokia Siemens Networks

DN70592449
Issue 2-0 en

Setup and configuration

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.

3.12.1

NTP Local Server

RIP Listener

IP Forwarding (Routing)

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\W
32Time\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.

DN70592449
Issue 2-0 en

Nokia Siemens Networks

77 (156)

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.

78 (156)

Nokia Siemens Networks

DN70592449
Issue 2-0 en

Setup and configuration

DN70592449
Issue 2-0 en

Nokia Siemens Networks

79 (156)

DF1/4 Blade

Figure 41.

3.13

Example Network

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

3.13.1

Trunk

Tributaries

Cross connect

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

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

80 (156)

Setting the framing to SDH also sets the circuit interfaces to


E1

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


switched

Nokia Siemens Networks

DN70592449
Issue 2-0 en

Setup and configuration

Figure 42.

DN70592449
Issue 2-0 en

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.

Trunk dialogue

Nokia Siemens Networks

81 (156)

DF1/4 Blade

3.13.2

Physical fibre connections

3.13.2.1

SFP information

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

Figure 43.

82 (156)

Front panel

Nokia Siemens Networks

DN70592449
Issue 2-0 en

Setup and configuration

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 supports and supplies a range of DDMI enabled SFPs. Please


contact NSN to obtain current pricing and availability. Contact
information is available at www.nsn.com.

DN70592449
Issue 2-0 en

Nokia Siemens Networks

83 (156)

DF1/4 Blade

Digital Diagnostic Monitoring Interface

DDMI is available by examining the SFP Diagnostics tab in the Port


Configuration dialog, if the SFP in use supports DDMI. Temperature,
Voltage, Tx Bias, Tx Power and Rx Power (average) can be set to raise
an alarm on warning, or set to raise an alarm on error. The current value
of each of these parameters is compared to the thresholds as displayed
in figure 41 below. Note that figure 41 is showing the Rx Power
threshold as higher than -6.00dbm, which is the maximum receive power
level for the SFP in use.
The thresholds are factory-set in the DDMI SFP and cannot be set with
Multiservice Manager.

84 (156)

Nokia Siemens Networks

DN70592449
Issue 2-0 en

Setup and configuration

Figure 44.

3.13.2.2

Port Configuration Dialog showing SFP DDMI

Point-to-Point MSP 1+1

The figure below shows trunk port A and B setup in Terminal Mux mode
(Point-to-Point) with MSP 1+1 protection. Trunk port C and D are setup
the same way if configured in Terminal Mux MSP 1+1 mode.
Working (Port A): Port A Transmit of the local node connects to port A
Receive of the remote node and vice versa.
Protection (Port B): Port B Transmit of the local node connects to port B
Receive of the remote node and vice versa.

DN70592449
Issue 2-0 en

Nokia Siemens Networks

85 (156)

DF1/4 Blade

Working (arrow indicates direction of Tx to Rx)


Protection

Local Node

Tx Rx

Remote Node

Figure 45.

MSP 1+1 Point to Point topology

A multi-drop linear network is a linear series of connected network nodes


that has a terminal node at each end and multiple midspan nodes in
between.
In a linear midspan configuration with MSP 1+1 protection the DF1/4
Blade is limited to STM-1 bandwidth.
DF1/4 Blade in MSP 1+1 protection mode:

86 (156)

Port A acts as the working WEST span, port B is the protection.

Port C acts as the working EAST span, port D is the protection.

Nokia Siemens Networks

DN70592449
Issue 2-0 en

Setup and configuration

Working (arrow indicates direction of Tx to Rx)


Protection

Tx Rx

Terminal Node

WEST

Linear Midspan Node

EAST

Terminal Node

Figure 46.

MSP 1+1 Protected multidrop linear topology

In a linear midspan configuration without protection the DF1/4 Blade can


be configured to be connected to two linear midspan networks:
Network 1: Port A is the WEST span and B is the EAST span at STM-1
Network 2: Port C is the WEST span and D is the EAST span at STM-1
or STM-4

DN70592449
Issue 2-0 en

Nokia Siemens Networks

87 (156)

DF1/4 Blade

Working (arrow indicates direction of Tx to Rx)

Port A
Terminal
Mode

Port C
Terminal
Mode

Tx Rx

155 Mbps STM-1/OC-3

622 Mbps STM-4/OC-12

WEST

WEST

Linear Midspan Node

EAST
Port D
Terminal
Mode

Port B
Terminal
Mode

Figure 47.

3.13.2.3

EAST

Two linear midspan networks

Ring SNCP/UPSR topology

Configured in a ring topology with SNCP/UPSR protection, the DF1/4


Blade nodes are connected to form a fibre optic ring. Data is transmitted
over two counter-rotating rings and the receiving DF1/4 Blade selects
one of the two data paths based on signal quality, overhead bytes and
management interface controls.
A DF1/4 Blade can support up to two protected rings, both operating at
155 Mbps or one operating at 155 Mbps and the other at 622 Mbps.
Only the rings connected at trunk port C and D can be upgraded from
155 Mbps to operate at 622 Mbps.
The ring with transmission in a clockwise direction is by convention
defined as the Working ring. The other ring which transmits in a
counter-clockwise direction is defined as the Protection Ring. There is
no logical limit to the number of nodes within the ring, although physical
distance limits exist for each section based on fibre optic plant and the
choice of SFP modules.

88 (156)

Nokia Siemens Networks

DN70592449
Issue 2-0 en

Setup and configuration

The terminology used to describe the relative direction to a DF1/4 Blade


is EAST or WEST.

Trunk port A and C are by convention nominated WEST

Trunk port B and D are by convention nominated EAST

Connecting up the fibre optic ring:

fibre optics on the WEST port always connects up to the EAST


port on the adjacent node

fibre optics on the EAST port always connects up to the WEST


port on the adjacent node
Working (arrow indicates direction of Tx to Rx)
Protection
Ring Mode
SNCP/UPSR

EAST

WEST

WEST

EAST

Ring Mode
SNCP/UPSR

Ring Mode
SNCP/UPSR

Ring Mode
SNCP/UPSR

Figure 48.

3.13.3

Ring SNCP/UPSR Topology

Tributary interfaces
The base system DF1/4 Blade contains two tributary interface types:

DN70592449
Issue 2-0 en

Packet 10/100/1000BaseX Ethernet

Nokia Siemens Networks

89 (156)

DF1/4 Blade

Circuit E1

There are two ways to access the tributary configuration window:

3.13.3.1

Left click select the port to be configured on the front main GUI
window

Right click on the port in the cross connect window and select
Properties

Ethernet

The Ethernet ports 1 and 2 are electrical interface 10/100/1000Mbit/s


ports that allow an Ethernet LAN to be extended over a trunk or WAN.
Access to the port is made via a standard RJ-45 connection. The port is
configured to appear as a Network Interface Card. The Ethernet ports
support automatic MDI/MDIx crossover at all data rates, so a through or
crossover cable can be used to connect to the ports.
The Ethernet ports 3 and 4 operate at 1000Mbps and have pluggable
interfaces that may be installed by the network administrator. Ethernet
SFP interface modules are available in a wide range of electrical and
fibre optic interfaces.
3.13.3.2

Ethernet configuration

The port configuration dialog has configuration tabs as discussed below.

Interface parameters

The Port Enable section is used to turn the port ON or OFF. When the
port is disabled, all front panel LED indicators are turned off. By default,
the port is set OFF. The On position enables port to become active and
all port operations perform as normal.
Enabling LCAS allows for the ability to increase and decrease Ethernet
bandwidth without incurring a data hit.
Encapsulation allows the network administrator to select the WAN
protocol LAPS, GFP or PPP.
The Scrambler section allows the user to select whether the scrambler
is enabled or not. If selected, a self-synchronous scrambler/descrambler
is used at both ends of the channel to randomise the data and ensure
there are always transitions. This reduces the likelihood that a stream of
all 1s or all 0s will be transmitted. Some lower data rates may not require
scrambling.
Frame Check Sequence enables detection of corrupted Ethernet
frames.

90 (156)

Nokia Siemens Networks

DN70592449
Issue 2-0 en

Setup and configuration

Figure 49.

Ethernet port configuration

The Connection can set to Auto Negotiate where the Ethernet port auto
senses the connected device or a fixed rate and mode to either 10Mbps
or 100Mbps half or full duplex.
Flow control enables the use of PAUSE frames for flow control. Default
value is off.
Setting the Watermark levels changes the data buffer full/empty
settings for pause frame generation. The default values are 30% and
70%.

DN70592449
Issue 2-0 en

Nokia Siemens Networks

91 (156)

DF1/4 Blade

Advanced - interoperability

The Advanced tab allows the network administrator to change control


fields to provide interoperability with other network providers.

Tip
It is recommended that these settings are not altered and that the
defaults as shown below are used.
The advanced tab will change according to Encapsulation scheme
selected.
Encapsulation scheme is selected from the Interface dialog as in Figure
Ethernet port configuration above.
LAPS

LAPS is a HDLC-like framing structure to encapsulate IEEE 802.3


Ethernet MAC frame to provide a point-to-point Full Duplex simultaneous
bidirectional operation. The LAPS protocol is specified in the following
standards: ITU-T X.85/Y.1321 and ITU-T X.86.

92 (156)

Nokia Siemens Networks

DN70592449
Issue 2-0 en

Setup and configuration

Figure 50.

LAPS control fields

Table 19.

Format of LAPS Frame with an Ethernet MAC Fame Payload

MSB

FLAG (0x7E)

LSB 1 octet

MSB

ADDRESS (0x04)

LSB 1 octet

MSB

CONTROL (0x03)

LSB 1 octet

MSB

First octet of SAPI (0xFE)

LSB 1 octet

MSB

Second octet of SAPI (0x01)

LSB 1 octet

DN70592449
Issue 2-0 en

Destination Address (DA)

6 octets

Source Address (SA)

6 octets

Nokia Siemens Networks

93 (156)

DF1/4 Blade

Length / Type

2 octets

MAC Client data

46 -1500
octets

PAD
FCS of MAC 4 octets
FCS of LAPS 4 octets
MSB

FLAG (0x7E)

MSB

Bit
8

Bit
7

Bit
6

LSB 1 octet
Bit
5

Bit
4

Bit
3

Bit
2

Bit
1

LSB

GFP

Generic Framing Procedure (GFP) is protocol for mapping packet data


into an octet-synchronous transport such as SDH. Unlike HDLC-based
protocols, GFP does not use any special characters for frame
delineation. Instead, it uses a cell delineation protocol, such as used by
ATM, to encapsulate variable length packets. A fixed amount of
overhead is required by the GFP encapsulation that is independent of
the contents of the packet. The GFP protocol is specified in the ITU-T
G.7041/Y.1303 standard.

94 (156)

Nokia Siemens Networks

DN70592449
Issue 2-0 en

Setup and configuration

Figure 51.

DN70592449
Issue 2-0 en

GFP control fields

Nokia Siemens Networks

95 (156)

DF1/4 Blade

Table 20.

Format of GFP Frame with an Ethernet MAC Frame Payload

Ethernet MAC Frame

GFP Frame
Octets
PLI Field

cHEC Field

Type Field

Octets

Preamble

tHEC Field

Start of Frame Delimiter

0-60

Extension Header

Destination Address (DA)

GFP

Source Address (SA)

MAC client data

Length/Type

Payload

MAC client data

Information

PAD

Pad Field

4
Bits

4 Frame Check Sequence


(FCS)
1

PPP

The Point-to-Point Protocol (PPP) is a HDLC-like framing structure and


provides a standard method for transporting multi-protocol datagrams
over point-to-point links. PPP can be used to encapsulate IEEE 802.3
Ethernet MAC frame to provide a point-to-point Full Duplex simultaneous
bidirectional operation. The PPP Bridging Control Protocol (BCP) is
specified in the following standards: RFC 1661, RFC 1662, RFC 2878,
RFC 2615 and RFC 3518.

96 (156)

Nokia Siemens Networks

DN70592449
Issue 2-0 en

Setup and configuration

Figure 52.

DN70592449
Issue 2-0 en

PPP control fields

Nokia Siemens Networks

97 (156)

DF1/4 Blade

Table 21.

FDDI Frame Format (IEEE 802 Un-tagged Frame) rfc 3518

0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
HDLC FLAG
Address and Control
F 0 Z B Pads

MAC Type

0x00

0x31

Pad Byte

Frame Control

Destination MAC Address


Destination MAC Address

Source MAC Address

Source MAC Address


LLC data
LAN FCS (optional)
optional Data Link Layer padding
Frame FCS

HDLC FLAG

Address and Control as defined by the framing in use.


PPP Protocol )x0031 for PPP Bridging

FLAGS

bit

F:

Set if the LAN FCS field is present

bit

0:

Reserved, must be zero

bit

Z:

Set if IEEE 802.3 Pad must be zero filled to minimum size

bit

B:

Set if the frame is a bridge control packet

Pads

Any PPP frame may have padding inserted in the optional Data Link
Layer Padding field. This number tells the receiving system how many
pads octets to strip off.

Status

The Status Dialog will change according to the Encapsulation Scheme


chosen.

98 (156)

Nokia Siemens Networks

DN70592449
Issue 2-0 en

Setup and configuration

If an alarm is any colour other than green, you may have to check these
configuration items at the remote end. This may also include checking
the status of the SDH parameters in the application section of the user
interface.

Figure 53.

Ethernet status alarms

Statistics

The Statistics section is used to monitor the traffic that has passed
through the port (Ethernet Bridge) and over the WAN. Only packets that
pass over the WAN will affect the statistics counters. The Transmit and
Receive flow is shown in byte and packet counts.
The payload held in each packet adds to a byte counter. The byte
counter does not include the Ethernet Frame overhead.
The Refresh button is used to get the current statistics from the port.
This feature presents a snap shot of the network statistics at the time
the button is pressed.

DN70592449
Issue 2-0 en

Nokia Siemens Networks

99 (156)

DF1/4 Blade

The Clear button is used to reset the traffic statistics, the counters are
set to zero. Both Transmit and Receive directions will be cleared for byte
and packet counters.
Both byte and packet counters are represented inside the Ethernet port
as a 32-bit number. This represents 232 bytes, and is equal to
4,294,967,296 bytes that can be counted before it rolls over to zero
again. Please note that a byte counter will roll over much faster than a
packet counter by orders of magnitude.

Figure 54.

100 (156)

Ethernet statistics

Nokia Siemens Networks

DN70592449
Issue 2-0 en

Setup and configuration

Ethernet alarms

The Ethernet port has alarms that can be configured and monitored via
the port alarm monitor setup window.

Figure 55.

Monitoring Ethernet alarms

LOL: A Loss of Link alarm indicates the presence of an Ethernet signal.


An Ethernet port will detect either a 10, 100 or 1000 Mbps connection to
another port configured as a switch.

Port indicators

Each Ethernet port has three alarm indication LEDs on the front panel.
The LED interpretations are summarised below.

DN70592449
Issue 2-0 en

Nokia Siemens Networks

101 (156)

DF1/4 Blade

Table 22.

RJ45 LED Display

Interpreting Ethernet Port LEDs

Fibre Optic

Interpretation

Port is off
All LEDs off

Or
LAN not connected

Left/Top LED
flashing
green

Receiving or Transmitting packet

LAN connected

Right/Lwr
LED - Green

Interface specificiations

Figure 56.

102 (156)

RJ45 Pin-outs

Nokia Siemens Networks

DN70592449
Issue 2-0 en

Setup and configuration

Table 23.

Ethernet cable straight through

RJ45 pin #

Signal name

Signal name

RJ45 pin #

Tx +

Rx +

Tx -

Rx -

Rx +

Tx +

Rx -

Tx -

Table 24.

Ethernet cross over path cable

RJ45 pin #

Signal name

Signal name

RJ45 pin #

Tx +

Rx +

Tx -

Rx -

Rx +

Tx +

Rx -

Tx -

Table 25.

Interface specifications

IM connector

RJ-45 connector configured as a NIC

Link Speed

10/100/1000 Mbps (Half or Full duplex auto-negotiation)

Alarm Monitoring

LOL: Loss of Link


TxFault (for Ethernet ports 3 & 4 only)

Indicator LEDs

LED INDICATORS SHOW THE LINK STATUS, WAN


STATUS, TX/RX,

Standards

IEEE802.3

WAN protocol

Complies with ITU-T X.86(LAPS), GFP, PPP

3.13.3.3

E1
E1 configuration

The port configuration dialog has configuration tabs as discussed below.

DN70592449
Issue 2-0 en

Nokia Siemens Networks

103 (156)

DF1/4 Blade

Interface parameters

The interface tab allows the user to select the frame monitoring, line
coding and line build out options.
The Port Enable section is used to turn the port ON or OFF. When the
port is disabled, all front panel LED indicators are turned off. By default,
the port is set disable.
The On position enables the port to become active and all port
operations perform as normal.
SSM Extraction can be enabled if one of the E1 ports is being used as
a network clock source.

In E1 defines the national bits used from timeslot zero that carry
the Synchronisation Status Message. One out of five national bits
can be chosen to do this.

The AIS Standards allows the user to select the standard to follow for
generating AIS alarms.
Impedance: The port can be set to 120 or 75 ohm when the trunk is
configured as SDH. The physical E1 interface is 4-wire interface.

104 (156)

Nokia Siemens Networks

DN70592449
Issue 2-0 en

Setup and configuration

Figure 57.

E1 port configuration dialog interface tab

E1 Ports 5 to 12 Configuration

E1 ports 5 to 12 of the DF1/4 have a different configuration dialog to that


of E1 ports 1 to 4. The difference is the Interface tab only. The Testing
and General tabs are identical.
Ports 1 to 4 provide Clock SSM (Synchronization Status Messaging)
extraction, if the port is selected as the clock source in the Clock
Configuration dialog.
Tip
If the network administrator has the need to extract SSM then E1 ports 1
to 4 should be selected. The clock can be extracted on ports 5 to 12,
SSM cannot be extracted.

DN70592449
Issue 2-0 en

Nokia Siemens Networks

105 (156)

DF1/4 Blade

Figure 58

E1 ports 5 to 12 configuration

Testing parameters

The testing tab allows the user to select a loopback mode for testing.
The available loopback modes are

106 (156)

None

Equipment

Line

Nokia Siemens Networks

DN70592449
Issue 2-0 en

Setup and configuration

Equipment: The signal is looped back internally to the node at the Line
Interface Unit. Signal that is normally transmitted is still transmitted. No
external signal is received.
Line: The signal is looped back externally to the line at the Line Interface
Unit. Signal that is normally received is still received. No external signal
is transmitted.
General allows a user comment to be entered.

Figure 59.

DN70592449
Issue 2-0 en

E1 port configuration dialog testing tab

Nokia Siemens Networks

107 (156)

DF1/4 Blade

IM alarms

Figure 60.

Monitoring E1 port alarms

LOS
The LOS alarm is set if the node identifies a loss of signal. On
occurrence of a LOS, all the other options are irrelevant.
RxAIS
An AIS alarm is triggered on the occurrence of a terminated network
connection at the other end of the network. It is triggered depending on
the AIS Standard selected in the E1 configuration window. See the
Figure LOS and RxAIS alarms below.

108 (156)

Nokia Siemens Networks

DN70592449
Issue 2-0 en

Setup and configuration

2.
LOS

4.
Rx AIS

3.
AIS

1.

PBX-A
Framed

Node A

Node B

PBX-B
Framed

Acts as a pipe where alarms set by either PBX are sent to the receiving PB

Figure 61.

LOS and RxAIS alarms

Cables

There are two types of cables to connect devices to the E1 port, one for
Network Interface mode and the other for Network Terminal mode of
operation. Each cable connects to the port with an 8 pin RJ45 connector.
Use shielded cables to ensure electromagnetic compatibility.

Tip
Unused pins are not connected at the port. The metal shell of the RJ45
socket may optionally be used as shielding.

DN70592449
Issue 2-0 en

Nokia Siemens Networks

109 (156)

DF1/4 Blade

Table 26.

DF1/4 Blade cable for Network Interface mode

DF1/4 Blade
Cable for Network Interface Mode
P1

Signal Name

RJ45

P2

Signal Name

RJ45

Tx Tip

Rx Tip

Tx Ring

Rx Ring

Rx Tip

Tx Tip

Rx Ring

Tx Ring

6
7
8

Table 27.

DF1/4 Blade cable for Network Terminal mode

DF1/4 Blade
Cable for Network Terminal Mode
P1

Signal Name

RJ45

Signal Name

RJ45

Tx Tip

Tx Tip

Tx Ring

Tx Ring

110 (156)

P2

Rx Tip

Rx Tip

Rx Ring

Rx Ring

Nokia Siemens Networks

DN70592449
Issue 2-0 en

Setup and configuration

Interface specifications

Table 28.

Interface specifications

Connector

Dual RJ-48,
E1/120 ohm

Trunk Speed

E1: 2048 Kbps

Signalling Monitoring

Unframed, D4, ESF, CAS, CCS

Loopbacks

Equipment, Line

Alarms

LOS: Loss of signal


RxAIS: Receive alarm indicator
signal

LED Indicators

Normal Data Transmission


Error AIS
Error LOF or LOS

All inter connections to unit via the E1 connectors are intra building only,
SELV, and not for outside plant connection. The E1 connections for the
unit are assumed to connect to a UL Listed PBX, NCTE (Network
Channel Terminal Equipment) or CSU/DSU (Channel Services Unit /
Digital Services Unit) unit, co-located with this equipment, or other
certified network equipment which provides the required protection for
outside plant lines which may be connected to this equipment.
3.13.3.4

Cross connect

The cross connect window can be reached by pressing the button


Cross Connect on the main GUI front window. Ensure that the trunk
settings are correct and configured before setting up the cross connect.
Subsequent changes to the trunk settings may be service affecting and
require reconfiguration of the cross connect.
The cross connect is used to groom the circuit and packet services over
the high speed trunks.
The graphical presentation of the cross connect window will vary
depending on the Trunk configuration settings. The fibre optic trunks are
shown as AU-4s (SDH). The figure below shows the cross connect with
trunk A and B setup in ring mode with protection, trunks C and D set up
terminal mux mode, no protection with a trunk speed of 155 Mbps.

DN70592449
Issue 2-0 en

Nokia Siemens Networks

111 (156)

DF1/4 Blade

Figure 62.

Digital cross connect

Configure the Trunk Framing Structure

The top section of the cross connect represents each enabled trunk and
trunk frame in order of A to D, from left to right. Hovering over the trunk
square highlights the trunk or frame it represents.
The trunk framing structure can be set to the following:
For SDH:

AU4

AU4-VC4

The Figure Changing frame structure shows how to change the trunk
framing structure. To change the trunk frame, right click on the square

112 (156)

Nokia Siemens Networks

DN70592449
Issue 2-0 en

Setup and configuration

representing the trunk, select AU Type and select the required framing
structure. The change will be immediately displayed graphically.

Figure 63.

DN70592449
Issue 2-0 en

Changing frame structure

Nokia Siemens Networks

113 (156)

DF1/4 Blade

Figure 64.

Trunk frame structure

Configure the TU Bandwidth

The DF1/4 Blade has default settings of tributary unit or virtual tributary
which are displayed in the cross connect window the first time a node
configuration is commenced. These are:
For SDH (AU4)

3x TU-3, (represented as a bar) each containing;

7x TU-2 (represented as frames) each containing;

3x TU-12 (represented as squares) each containing an


E1 payload

To change the VC bandwidth, Right-click on a white square that


represents a VC, select Tug Type, then select the required tributary
type. The change will be immediately displayed in the graphic.

114 (156)

Nokia Siemens Networks

DN70592449
Issue 2-0 en

Setup and configuration

Figure 65.

Changing TU type

SDH Cross Connect

To map a tributary such as a E1 simply left click on the E1 port icon and
drag to the destination tributary unit group of choice.
Tributary unit bandwidth should be configured before an interface
connection is dragged to it. To configure the tributary type refer to the
previous section.
Control buttons

The SDH Cross Connect window has these control buttons:

DN70592449
Issue 2-0 en

NEW

Deletes the current cross connects.

SAVE

Saves the current cross connect configuration to disk.

LOAD

Loads a previously saved cross connect configuration.

Nokia Siemens Networks

115 (156)

DF1/4 Blade

VALIDATE

Verifies that cross connections to IMs exist.

INSTALL

Installs the cross connect configuration to the DF-CX-SS.

REFRESH

Reloads the current DF-CX-SS configuration (from the node)

HELP
Close

Opens the help file in a SDH context.


Closes the Cross Connect window.

Control menu

A right click in the tributary unit of the SDH cross connect window,
displays the drop down menu as in the figure above.
This menu allows repetitive Undo and Redo of cross connects up to a
maximum of 40 actions.
To delete a specific cross-connect, right click directly on either end of a
link, then select Delete All Links from the menu. This will delete only the
selected link.
A complex cross connect window can be clarified by focusing on only
the components being addressed. The port or trunk can be faded or
focused from the drop down menu or by the left click on the trunk
representation at the top of the cross connect or by left clicking on the
trunk port identifier button on the left (A1, B1, C1..4, D1..4).

116 (156)

Nokia Siemens Networks

DN70592449
Issue 2-0 en

Setup and configuration

Figure 66.

Right-click tributary unit menu

Tailor the Screen appearance

The AU4s can be moved to any location of the window by dragging the
blue handles at the left edge of each frame. Clicking on the Install
button will save the new screen locations of these frames.

Figure 67.

DN70592449
Issue 2-0 en

Blue relocation handles

Nokia Siemens Networks

117 (156)

DF1/4 Blade

Ethernet VCG and LCAS cross connects

The DF1/4 Blade supports a range of flexible options for Ethernet over
concatenated SDH circuits.
The Ethernet uses Virtual Concatenation (VCAT) and Link Capacity
Adjusting Scheme (LCAS) to dynamically manage concatenated SDH
VCs to 10/100/100BaseT and Gig Ethernet interfaces. Up to four
Ethernet interfaces are supported.
Bandwidth granularity is supported as low as VC12 (E1) and as
multiples of STS-1 and VC3.
LCAS allows for the modification of the bandwidth of the system without
the disruption of traffic. If LCAS mode is not enabled, and there is an
adjustment in the circuit, for example an increase in bandwidth, the local
and remote nodes make the required changes whilst the changes take
place the already existing links are lost and the traffic is disrupted.
When both nodes are properly configured then the circuit connects
again.

Setting up a LCAS Group

1. Enable LCAS mode in the Ethernet port configuration window.


2. Connect the WAN Ethernet ports up to the VC/VT/STS-1.
3. Press Install button on the cross connect. By pressing Install, it
enables all the LCAS links in the group.

Adding and Removing LCAS Links Hitlessly

The statuses of an LCAS link can be examined by left then right click on
a VC/VT that is part of the LCAS group. This brings up a menu, select
Properties, the following window will be shown:

118 (156)

Nokia Siemens Networks

DN70592449
Issue 2-0 en

Setup and configuration

Figure 68.

Tributary properties: LCAS status

This window allows the user manage the LCAS member:

add a comment about the VC/VT/STS-1

view the status of the LCAS link under Tx/Rx State

enable or disable an LCAS group member without causing a hit on


the payload data.

Pressing the Refresh button will refresh the Tx/Rx State of the LCAS
link.
Removing a Link

When removing a link DO NOT simply delete the VC/VT link as this will
cause the link to go into Do Not Use state. Instead select Disable, then
press Install before deleting the VC/VT link in the cross connect
window.
Adding a Link

When adding a link, connect the WAN Ethernet port up to the VC/VT,
enter the Tributary Properties Window. Select Enable then press Install.
Tx/Rx State

Tx: Means the state message being transmitted by the local LCAS link
Rx: Means the received state message transmitted from the
corresponding remote LCAS link

DN70592449
Issue 2-0 en

Nokia Siemens Networks

119 (156)

DF1/4 Blade

States that are transmitted and received:

Table 29.

TX RX states

Normal

The link is in a normal state.

Add

The corresponding member on the remote side is still to be added.

Idle

The link has been disabled one end and is waiting enabling or removal.

EOS

End Of Segment. This status is transmitted by the last member that is added
to the LCAS group.

Unknown

There is no member on the remote end, or its status is unknown

DNU

Do Not Use. This status is transmitted by the local end to the remote end to
indicate that the remote end was not pulled down correctly.

The following sections detail just three of these variants possible over a
conventional path protected ring network.

EoS UPSR/SNCP protected ring

In a conventional SDH path protected network, the Ethernet traffic is


mapped into concatenated frames and transmitted onto both the working
and protected rings. The destination ADM selects one of these paths
and discards the other. This practice is entirely suitable for fixed
bandwidth TDM circuits such as E1, but Ethernet packet services
effectively discard half of what could be usable network bandwidth. In
the example depicted in the figure below, this network is an STM-1 ring,
then two thirds of the total network bandwidth is consumed to deliver a
100BaseT E-Line service between nodes A and C.
In the event of a single point ring failure the alternative path is
automatically selected and there is no change to the E-Line service
bandwidth.

120 (156)

Nokia Siemens Networks

DN70592449
Issue 2-0 en

Setup and configuration

Node
B

UPSR/SNCP
Path protected
Ring

VC

VC

Working
Ring

Protecting
Ring

Working Ring

Node
C

Node
A
VC

Protecting Ring

VC

VC

VC

VC

VC

Fast Ethernet
E-Line service

Figure 69.

EOS protected path ring

To configure this E-Line service, drag the cross connections from the
selected Ethernet port to the trunk VCAT group member circuits. Only
the A trunk port is connected as this is the default working ring port that
faces the West. The B port protection ring connections are
automatically configured but not shown in the connection window. Refer
to the Figure EOS Protected Path Ring Cross Connect below.

DN70592449
Issue 2-0 en

Nokia Siemens Networks

121 (156)

DF1/4 Blade

Figure 70.

EOS Protected Path Ring Cross Connect

EoS LCAS protected ring

This EoS configuration is also based on a conventional protected path


ring network. The 100BaseT E-line service between nodes A and C
uses only one third of a STM-1 network capacity.
In the example depicted in the figure below, the path based protection is
disabled for the TU-3 VCG members. One of the two TU-3 VCG
members is transmitted over the working ring to the West and the other
TU-3 VCG member to the East over the protection ring. Node C
recombines the VCG members. In the event of a single point ring failure
the available bandwidth is reduced to half. LCAS provides a hitless
reconfiguration of the bandwidth.

122 (156)

Nokia Siemens Networks

DN70592449
Issue 2-0 en

Setup and configuration

Node
B

UPSR/SNCP
Path protected
Ring

VC

Working
Ring

Protecting
Ring

West

Node
C

Node
A
VC

East

VC

VC

VC

VC

Fast Ethernet
E-Line service

Figure 71.

EOS-LCAS protected ring

To configure this E-Line service, follow the steps summarized in the


points and figures below.
1. Create the VCAT group
2. Drag the first member to the Working, A trunk
3. Drag the second member to the Protection, B trunk
4. Install
5. Close

DN70592449
Issue 2-0 en

Nokia Siemens Networks

123 (156)

DF1/4 Blade

Figure 72.

LCAS protected ring cross connect

EoS LCAS reusable bandwidth

This EoS configuration is also based on a conventional protected path


ring network. The 100BaseT E-line service between nodes A and C
only uses ring bandwidth between nodes A and C. The same virtual
circuits can be re-used between all other node pairs on the ring, A-B
and B-C.
In the example depicted in the figure below the path based protection is
automatically disabled for the TU-3 VCG members. The two TU-3 VCG
members are transmitted from the East trunk port of node A and
received on the West trunk port of Node C. In the event of a single
point ring failure between nodes A and C the E-line service will fail. A
single point of failure at any other network point will have no impact on
the E-line service.

124 (156)

Nokia Siemens Networks

DN70592449
Issue 2-0 en

Setup and configuration

Node
B

UPSR/SNCP
Path protected
Ring

Working
Ring

Protecting
Ring
Node
A
VC

West
VC

VC

Node
C
VC

VC

VC

East

Fast Ethernet
E-Line service

Figure 73.

LCAS Reusable bandwidth

To configure this E-Line service, follow the steps summarized in the


points and figures below.
For the Node A the VCG must face East, using port A, follow these
steps:
1. Create the VCAT group
2. Drag the VCG members to the East, B trunk
3. Install
4. Close

DN70592449
Issue 2-0 en

Nokia Siemens Networks

125 (156)

DF1/4 Blade

Figure 74.

LCAS Reusable Bandwidth - Step #1

Making the cross-connect to the protection ring B port automatically


disables the SNCP/UPSR path bridging function. Subsequent cross
connects to the same VT/VCs on the A port will not be protected.
For the Node C, the VCG must face West, follow these steps:
1. Create the VCAT group
2. Drag the VCG members to the West, A trunk
3. Install
4. Close

126 (156)

Nokia Siemens Networks

DN70592449
Issue 2-0 en

Setup and configuration

Figure 75.

LCAS Reusable Bandwidth - Step #2

Making the cross-connect to the working ring A port automatically


enables the SNCP/UPSR path bridging function. If independent B port
VC/VT connections are not made, then the data payload will be bridged
by the SNCP/UPSR function onto the B port, protection ring.

3.14

Trunk and Data Path Configuration

3.14.1

SDH Alarms
The front GUI alarm window shows a high level summary of the current
and historic alarm status for each of the trunk ports.

DN70592449
Issue 2-0 en

Nokia Siemens Networks

127 (156)

DF1/4 Blade

Figure 76.

SDH Alarm Summary Window

The current and historical statuses of the SDH alarms are displayed in
summary form on the main screen of Multiservice Manager. The window
will look different depending on how the trunks are set. Additional details
are available for each section by pressing on the alarm buttons (The
green, red, or yellow LEDs). The cross connect must be configured
before the Path/HO-Path and VT/LO-Path alarms can be configured, if
this is not done the Path/HO-Path alarm window will be blank and the
VT/LO-Path alarms windows are not accessible. Each alarm can be
enabled to display as either a red or a yellow. The history and current
status of each alarm are also displayed. If any of the configured yellow
alarms are active, the tributary unit box will be yellow. If any configured
red alarms are active, the box will be red. If red and yellow alarms are

128 (156)

Nokia Siemens Networks

DN70592449
Issue 2-0 en

Setup and configuration

active, the box will show red. If the box is green, it indicates that all user
configured alarm events are normal.
Alarms can be disabled on a layer basis or individually at any given
layer. This means that as a network is commissioned, the installer can
disable all low order alarms until the higher order is established.
3.14.1.1

Section/line or regenerator/multiplexer

The alarms that are monitored are:


Section/RSOH
Loss of incoming Optical Signal

LOS

Loss of Optical Frame

LOF

J0 Byte Trace Identifier Mismatch

TIM

Line/MSOH

DN70592449
Issue 2-0 en

Alarm Indication Signal

AIS

Signal Fail

SF

Signal Degrade

SD

Remote defect indicator

RDI

Nokia Siemens Networks

129 (156)

DF1/4 Blade

Figure 77.

130 (156)

Section and line alarms

Nokia Siemens Networks

DN70592449
Issue 2-0 en

Setup and configuration

3.14.1.2

Path or high order

Path/HO-Path

DN70592449
Issue 2-0 en

Alarm Indication Signal

AIS

Loss of Multiframe

LOM

Path Unequipped

UNEQ

J1 byte Trace Identifier Mismatch

TIM

Loss of Pointer

LOP

Remote Defect Indicator

RDI

Payload Label Mismatch

PLM

Nokia Siemens Networks

131 (156)

DF1/4 Blade

Figure 78.

3.14.1.3

Path alarms

VT or Low order

VT/LO-Path

132 (156)

Alarm Indication Signal

AIS

Payload Label Mismatch

PLM

Path Unequipped

UNEQ

Nokia Siemens Networks

DN70592449
Issue 2-0 en

Setup and configuration

J2 byte Trace Identifier Mismatch

TIM

Loss of Pointer

LOP

Remote Defect Indicator

RDI

The VT/LO-Path alarm window can be accessed in three ways:


1. Double click the VT/LO-Path alarm LED on the main screen.
2. Select SDH -> Lo Alarms from the main menu.
Double-click the X to view alarm details.

Figure 79.

Alarm dialog from main window

3. The alarm window can be accessed in the Cross Connect window.


Left select the top VT/TU that contains a circuit (as shown in the
Figure VT circuit from cross connect window), then right click to bring
up the alarm window. Double-click the X to view alarm details.

Figure 80.

DN70592449
Issue 2-0 en

VT circuit from cross connect window

Nokia Siemens Networks

133 (156)

DF1/4 Blade

Figure 81.

134 (156)

SDH Low Order Alarm Window without Protection

Nokia Siemens Networks

DN70592449
Issue 2-0 en

Setup and configuration

Figure 82.

3.14.2

SDH Alarm Window with Protection

Trail Trace Identifier


For each of the SDH alarm configuration windows, there is a TTI (Trail
Trace Identifier) section to enter a unique text string that is associated

DN70592449
Issue 2-0 en

Nokia Siemens Networks

135 (156)

DF1/4 Blade

with the payload at that layer. This is the equivalent to assigning unique
text strings to the J0, J1 and J2 overheard bytes. This section has
Received, Expected, Transmit string fields.

Figure 83.

Trace identifier section

The Expected value is compared with the Received TTI, the Transmit
value is forwarded to the next node for the same comparison. The TTIs
are used to allow intuitive interconnection of multiple nodes. Unique text
labels are encapsulated with data as it is transmitted, at the destination a
comparison is performed between the received and the expected text to
confirm that the correct connection is made. Trail Trace Identifiers are
provided;

at the RSOH (Are we connected to the correct node?),

at the HO-path (Are we connected to the correct HO payload?)


and

at the LO-path (Are we connected to the correct tributary?)

TTI Control: Lets the user choose what size TTI to send to the remote
node. TTI Control on both sides needs to match up.

3.15

Network protection
The DF1/4 Blade supports two types of network protection schemes:

136 (156)

Line/Multiplexer
exer Protection: 1+1/MSP unidirectional or bidirectional
for Linear or Terminal Mux mode

VT/LO-Path Protection: UPSR/SNCP for Ring mode

Nokia Siemens Networks

DN70592449
Issue 2-0 en

Setup and configuration

3.15.1

MSP/1+1 Automatic Protection Switch


The MSP (1+1) APS window (the figure below) is located as a tab within
the Section/Line (RSOH/MSOH) alarm window. The MSP (1+1) APS
window displays current and historical status of the fibre optic interfaces.
The green tick icon identifies the active trunk port. The Bit Error Rate is
monitored and trunk protection can be configured to switch on signal
Failure and/or Degradation. If the Revertive box is ticked, the active
trunk will switch from protection back to working after a switch over when
the signal quality of the working trunk is within specification and the
configured timer has expired.

DN70592449
Issue 2-0 en

Nokia Siemens Networks

137 (156)

DF1/4 Blade

Figure 84.

138 (156)

MSP (1+1) APS window

Nokia Siemens Networks

DN70592449
Issue 2-0 en

Setup and configuration

3.15.2

UPSR/SNCP Automatic protection switch


The UPSR(SNCP) APS window (see the following figure) is located as a
tab within the VT/LO-Path alarm window. The UPSR(SNCP) APS
window displays current and historical status of the circuits being
transmitted over the SDH payload.
The DF1/4 Blade is capable of supporting connections to one or two
protected ring networks.
By convention, the working ring transmits in a clockwise rotation and the
protection ring in a counter-clockwise rotation. The West and East
trunk interfaces are defined thus:

West

East

DN70592449
Issue 2-0 en

Port A and Port C


Port B and Port D

Nokia Siemens Networks

139 (156)

DF1/4 Blade

Figure 85.

UPSR/SNCP APS window

The green tick icon identifies the trunk port the circuit is being sent
over. The Bit Error Rate is monitored and trunk protection can be
configured to switch on signal Failure and/or Degradation. If the
Revertive box is ticked, the active circuit will switch from protection back
to working after a switch over when the signal quality of the working
circuit is within specification and the configured timer has expired.

3.16

Clock
The DF1/4 Blade can be configured to generate an internal master
network clock using its integrated Stratum 3 (4.6 ppm) clock.

140 (156)

Nokia Siemens Networks

DN70592449
Issue 2-0 en

Setup and configuration

It can also obtain clocking from external sources:

Trunk Ports

E1 circuit

Below is a figure of the clock configuration window. This can be


accessed by pressing the Clock button on the main front GUI window.

DN70592449
Issue 2-0 en

Nokia Siemens Networks

141 (156)

DF1/4 Blade

Figure 86.

Clock configuration window

The primary and secondary clock references can be chosen from the
internal clock or any of the clock sources in the Clock Reference
Selection section. The Clock Reference Selection section describes
where the clock source is obtained from, what type of clock type it is, the
quality and accuracy of the clock source.

142 (156)

Nokia Siemens Networks

DN70592449
Issue 2-0 en

Setup and configuration

3.16.1

Clock hierarchy
Primary

The node will first attempt to use the clock source selected as
the Primary.

Secondary

If the primary clock cannot be recovered, the node will then


attempt to recover the clock source selected as the
Secondary.

Tertiary

If the secondary clock cannot be recovered, the node will


then attempt to recover the clock source selected as the
Tertiary.
The green tick icon identifies the current clock source in use. If the
Revertive box is ticked, the active clock will switch from
tertiary/secondary back to secondary/primary after a switch over when
the clock quality of the clock source is within specification and the
configured timer has expired.

3.16.2

Clock types
Internal
This is a free running clock that is based on an internal Stratum 3 +/- 4.6
ppm TCXO. In this mode the PLL (Phase Locked Loop) is not locked to
any external clock source. This clock is a valid G.813 synchronization
source for a Stratum 3 SDH/SONET system.
Holdover
If the PLL has been locked to a valid reference and that valid reference
has gone, the PLL can go into Holdover. This means that it will find the
last time that reference was valid and hold the PLL to that frequency
unless told to do otherwise. It will holdover to the G.813 specs for a
Stratum 3 clock.

3.16.3

SSM
The clock source can be configured to Ignore SSM (Synchronization
Status Messaging). SSM is a SDH SONET protocol used to convey
information about the timing (clock) reference. Ignore SSM can be
enabled for interoperation with equipment that does not support SSM (by
using Ignore SSM check boxes on the right).

DN70592449
Issue 2-0 en

Nokia Siemens Networks

143 (156)

DF1/4 Blade

3.17

Troubleshooting

3.17.1

USB driver installation on Windows XP


In some circumstances, the USB drive fails to fully install during DF1/4
Blades installation process. This is due to the software configuration of
the machine on which DF1/4 Blade is to be installed.
Figure 87 shows that the MSB USB Comm driver is unavailable and the
driver must be installed manually.

Figure 87.

MSP USB Driver unavailable

To install the USB driver manually

1.

144 (156)

Click Start, then right-click on My Computer, and in the opening


pop-up menu click Manage.

Nokia Siemens Networks

DN70592449
Issue 2-0 en

Setup and configuration

Figure 88.

2.

DN70592449
Issue 2-0 en

Manual USB Driver Install Step 1

The Computer Management window opens. In the left column,


click Device Manager. Then, in the right column, right-click on the
MSPP USB-to-Serial Comm Port Driver, and select Update
Driver. Note the yellow exclamation mark over the driver.

Nokia Siemens Networks

145 (156)

DF1/4 Blade

Figure 89.

3.

146 (156)

Manual USB Driver Install Step 2

In the Hardware Update Wizard dialog, select the No, not this
time radio button, and click Next.

Nokia Siemens Networks

DN70592449
Issue 2-0 en

Setup and configuration

Figure 90.

4.

DN70592449
Issue 2-0 en

Manual USB Driver Install Step 3

Select Install from a list or specific location (Advanced), then


click Next.

Nokia Siemens Networks

147 (156)

DF1/4 Blade

Figure 91.

5.

148 (156)

Manual USB Driver Install Step 4

Select Search for the best driver in these locations, then tick
Include this location in the search. Browse to the location where
you installed DF1/4 Blade or type it in the field, then click Next.

Nokia Siemens Networks

DN70592449
Issue 2-0 en

Setup and configuration

Figure 92.

6.

DN70592449
Issue 2-0 en

Manual USB Driver Install Step 5

Click Continue Anyway.

Nokia Siemens Networks

149 (156)

DF1/4 Blade

Figure 93.

7.

150 (156)

Manual USB Driver Install Step 6

Click Finish.

Nokia Siemens Networks

DN70592449
Issue 2-0 en

Setup and configuration

Figure 94.

8.

DN70592449
Issue 2-0 en

Manual USB Driver Install Step 7

Note the exclamation mark on the MSPP USB-to-Serial Comm


Port Driver has disappeared. The USB driver is now installed.

Nokia Siemens Networks

151 (156)

DF1/4 Blade

Figure 95.

152 (156)

Manual USB Driver Install Step 8

Nokia Siemens Networks

DN70592449
Issue 2-0 en

International compliances

International compliances
All DF1/4 Blade products have achieved the following international
compliances;

CE
A Tick
C Tick
FCC part 15 class A
UL

FCC COMPLIANCE STATEMENT

This device complies with Part 15 of the FCC Rules. Operation is subject
to the following two conditions: (1) this device may not cause harmful
interference and (2) this device must accept any interference received,
including interference that may cause undesired operation.
NOTE:
This equipment has been tested and found to comply with the limits for a
Class A digital device, pursuant to part 15 of the FCC Rules. These limits
are designed to provide reasonable protection against harmful
interference in a residential installation. This equipment generates, uses
and can radiate radio frequency energy and, if not installed and used in
accordance with the instructions, may cause harmful interference to radio
communications. Operation of this equipment in a residential area is likely
to cause harmful interference in which case the user will be required to
correct the interference at his own expense.
If this equipment does cause harmful interference to radio or television
reception, which can be determined by turning the equipment off and on,

DN70592449
Issue 2-0 en

Nokia Siemens Networks

153 (156)

DF1/4 Blade

the user is encouraged to try to correct the interference by one or more of


the following measures

Reorient or relocate the receiving antenna


Increase the separation between the equipment and the receiver
Connect the equipment into an outlet on a circuit different from that
to which the receiver is connected
Consult the dealer or an experienced radio/TV technician for help

WARNING
Any changes or modifications not expressively approved by Nokia
Siemens Networks could void the users authority to operate this
equipment.
Electromagnetic compatibility (EMC)

CISPR 22 class A
EN55022
EN61000-3-2
EN61000-3-3
ETS300386

Safety

IEC60950, UL60950, and AS-NZ60950:2000 for General safety


IEC60825-1 & -2 for Laser Safety

Immunity

154 (156)

EN61000-4-2

EN61000-4-3

EN61000-4-4

EN61000-4-5

EN61000-4-11

Nokia Siemens Networks

DN70592449
Issue 2-0 en

RoHS statements

RoHS statements
Product collection and disposal within the European Union
Do not dispose of the
product as unsorted
municipal waste. The
crossed-out wheeled
bin means that at the
end of the product's
life it must be taken
to separate collection.
Note: this is applicable only
within the European Union
(see WEEE Directive 2002/96/EC)
DN0577953

Figure 96.

DN70592449
Issue 2-0 en

Product collection and disposal within the European Union

Nokia Siemens Networks

155 (156)

DF1/4 Blade

156 (156)

Nokia Siemens Networks

DN70592449
Issue 2-0 en