Integrated LAN Administration DN0423824 Issue 3-2

7/29/2019 Integrated LAN Administration DN0423824 Issue 3-2

http://slidepdf.com/reader/full/integrated-lan-administration-dn0423824-issue-3-2 1/102

Integrated LAN AdministrationDN0423824

Issue 3-2



2 DN0423824

Issue 3-2

Integrated LAN Administration

Id:0900d805805788bb

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 whichthe 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 DOCUMENTA-

TION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDI-

RECT, 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 respectiveowners, and they are mentioned for identification purposes only.

Copyright © Nokia Siemens Networks 2009/5/25. All rights reserved

f Important Notice on Product SafetyElevated voltages are inevitably present at specific points in this electrical equipment.

Some of the parts may also have elevated operating temperatures.

Non-observance of these conditions and the safety instructions can result in personal

injury or in property damage.

Therefore, only trained and qualified personnel may install and maintain the system.

The system complies with the standard EN 60950 / IEC 60950. All equipment connected

has to comply with the applicable safety standards.

The same text in German:

Wichtiger Hinweis zur Produktsicherheit

In elektrischen Anlagen stehen zwangsläufig bestimmte Teile der Geräte unter Span-

nung. Einige Teile können auch eine hohe Betriebstemperatur aufweisen.

Eine Nichtbeachtung dieser Situation und der Warnungshinweise kann zu Körperverlet-

zungen und Sachschäden führen.

Deshalb wird vorausgesetzt, dass nur geschultes und qualifiziertes Personal die

Anlagen installiert und wartet.

Das System entspricht den Anforderungen der EN 60950 / IEC 60950. Angeschlossene

Geräte müssen die zutreffenden Sicherheitsbestimmungen erfüllen.



DN0423824

Issue 3-2

3


Id:0900d805805788bb

Table of ContentsThis document has 102 pages.

Summary of changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

1 Planning the LAN implementation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

1.1 Redundancy scheme of the switching units and LANs. . . . . . . . . . . . . . . . 10

1.2 Planning the IP connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

1.3 Selecting the management principle. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

1.4 Supervising unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

1.5 Planning the LAN division. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

1.6 Planning the VLAN division. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

1.7 Multiple Spanning Tree Protocol (802.1s) and load sharing. . . . . . . . . . . . 17

1.8 LAN topology with third-party L2 switches . . . . . . . . . . . . . . . . . . . . . . . . . 20

2 Preparing LAN implementation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

2.1 Activating LAN Device Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

2.2 Selecting the LAN topology. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

2.3 Network element upgrades. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

2.4 Updating the size of the event log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

2.5 Enabling or disabling the automatic loading of configuration files . . . . . . . 24

3 Creating LANs in a new network element. . . . . . . . . . . . . . . . . . . . . . . . . . 25

3.1 Creating the hardware configuration description . . . . . . . . . . . . . . . . . . . . 25

3.1.1 Creating the hardware configuration of an integrated ESB LAN switch of a

DX 200 network element (M98 mechanics) . . . . . . . . . . . . . . . . . . . . . . . . 25

3.1.2 Creating a hardware configuration of a 3rd-party LAN switch of a DX 200 net-work element (M98 mechanics) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

3.2 Working states of LAN switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

3.3 Creating TCP/IP connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

3.4 Preconfiguring LAN switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

3.5 Activating LAN switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

3.6 Configuring LAN switches. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

3.7 Copying LAN switch configuration files. . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

4 Supervising LAN devices and connections. . . . . . . . . . . . . . . . . . . . . . . . . 38

4.1 Starting the supervision of LAN devices and connections . . . . . . . . . . . . . 38

4.2 Ending the supervision of LAN devices and connections . . . . . . . . . . . . . . 394.3 Inquiring LAN connection information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

4.4 Handling LAN hardware supervision logs. . . . . . . . . . . . . . . . . . . . . . . . . . 40

5 Maintaining LANs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

5.1 Updating the password of a LAN switch . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

5.2 Configuring a LAN switch of the communication network (CNW). . . . . . . . 43

5.3 Updating the software package of a LAN switch . . . . . . . . . . . . . . . . . . . . 44

5.4 Removing a LAN switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

5.5 Adding a LAN switch. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

5.6 Replacing a LAN switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

5.6.1 Replacing a switch with one of a different type. . . . . . . . . . . . . . . . . . . . . . 48

5.6.2 Replacing a switch with one of the same type . . . . . . . . . . . . . . . . . . . . . . 51



4 DN0423824

Issue 3-2


Id:0900d805805788bb

5.7 Removing confidential information from a LAN switch. . . . . . . . . . . . . . . . . 52

5.7.1 Removing confidential information from a LAN switch. . . . . . . . . . . . . . . . . 53

5.8 Diagnosis of LAN or LAN switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

5.9 LAN statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 545.9.1 LAN statistics reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

5.9.2 Measurement handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

5.9.3 Traffic measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

5.9.3.1 LAN Switch Traffic Measurement reports (288/120H) . . . . . . . . . . . . . . . . . 57

5.9.3.2 LAN Host Unit Traffic Measurement report (289/121H) . . . . . . . . . . . . . . . . 63

5.9.4 Availability measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

5.9.4.1 LAN Switch Availability Measurement report (290/122H) . . . . . . . . . . . . . . 67

5.9.5 Error measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

5.9.5.1 LAN Switch Error Measurement report (291/123H) . . . . . . . . . . . . . . . . . . . 70

5.9.5.2 LAN Host Unit Error Measurement report (292/124H). . . . . . . . . . . . . . . . . 74

5.9.6 Short time measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

6 Changing and expanding the LAN topology of the communication network 81

7 Integrated LAN Administration troubleshooting . . . . . . . . . . . . . . . . . . . . . . 84

7.1 Supervision of a LAN switch fails. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

7.2 Supervision of a connection fails . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

7.3 The software package or sysloader update of a LAN switch fails . . . . . . . . 84

7.3.1 Wrong software version in the LAN switch. . . . . . . . . . . . . . . . . . . . . . . . . . 84

7.3.2 Wrong LAN switch password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

7.3.3 Missing or incorrect LAN switch IP address. . . . . . . . . . . . . . . . . . . . . . . . . 85

7.4 Configuration file transfer to a LAN switch fails . . . . . . . . . . . . . . . . . . . . . . 85

7.5 Traps not received from a LAN switch. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

7.5.1 There is no connection from the LAN switch to the system . . . . . . . . . . . . . 85

7.5.2 The trap host IP address could not be set to the LAN switch by the system86

7.5.3 Traps have not been activated in the LAN switch . . . . . . . . . . . . . . . . . . . . 87

7.5.4 The SNMP server is disabled. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

7.5.5 The reason for the problem is unknown. . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

7.5.6 SNMP Trap overload detected. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

7.6 SNMP operation fails . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

7.6.1 Incorrect parameters in MML command . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

7.6.2 There is no IP connection to the LAN switch . . . . . . . . . . . . . . . . . . . . . . . . 88

7.6.3 The SNMP configuration in the LAN switch is incorrect. . . . . . . . . . . . . . . . 897.6.4 Capacity has been exceeded. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

7.7 IP addressing failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

7.8 LAN switch is faulty . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

7.9 LAN Hardware Supervision Handling log has been corrupted. . . . . . . . . . . 97

7.10 LAN statistics troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

7.10.1 A LAN statistics measurement has failed. . . . . . . . . . . . . . . . . . . . . . . . . . . 98

7.10.2 A LAN statistics measurement report indicates problems in the LAN . . . . . 98

7.11 Network element upgrade changed the configuration . . . . . . . . . . . . . . . . . 99

7.11.1 To determine if any changes have occurred . . . . . . . . . . . . . . . . . . . . . . . . 99

7.11.2 To make topology management configurations up to date . . . . . . . . . . . . 100

7.12 Errors in SNMP, DHCP and TFTP operations . . . . . . . . . . . . . . . . . . . . . . 101



DN0423824

Issue 3-2

5


Id:0900d805805788bb

List of FiguresFigure 1 LAN topology of managed and supervised LAN switches in the network el-

ement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Figure 2 Example of LAN switch topology for inband management . . . . . . . . . . 11

Figure 3 Example of LAN switch topology for outband management . . . . . . . . . 12

Figure 4 VLANs of management LANs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Figure 5 Configuration of 802.1Q-compliant DMX computer unit and LAN switch

port. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Figure 6 Load sharing with Multiple Spanning Tree Protocol (MSTP) . . . . . . . . . 19

Figure 7 LAN topology with third-party L2 switches. . . . . . . . . . . . . . . . . . . . . . . 20



6 DN0423824

Issue 3-2


Id:0900d805805788bb

List of TablesTable 1 Example of an IP address plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Table 2 Measured objects in reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55



DN0423824

Issue 3-2

7

Integrated LAN Administration Summary of changes

Id:0900d805805490e9

Summary of changesChanges between document issues are cumulative. Therefore, the latest document

issue contains all changes made to previous issues.

Changes made between issues 3-2 and 3-1

Procedure has been clarified in chapter Updating the software package of a LAN switch.


Added section Removing confidential information from LAN switch.


Changes made to the instructions Network element upgrades:

• introduction updated

• TELE information replaced with ASWDIR information

• note added about the case if the configuration files do not exist

• added 'LAUDATGX file and ILDATA database'

• added 'Event log of Integrated LAN Administration'

• added 'Parameters for automatic configuration file loading'

Changes made to the instructions Creating LANs in a new network element :

• in 'Creating the hardware configuration description', removed step 'Change the

working state of the LAN switch to WO-EX (USC).'

• in 'Creating TCP/IP connections', added step 'Change the working state of the LAN

switch to WO-EX (USC).'

• in 'Activating LAN switches, added a note about EMB LAN switches in Configuring

LAN switches, removed step 'If the state of the switch is not TE-EX, set the state

(USC).' and removed step 'Set the state of the switch to WO-EX (USC).'

Changes made to the instructions Supervising LAN devices and connections:

• in 'Handling LAN hardware supervision logs', updated the list of situations

Changes made to the instructions Maintaining LANs:

• in 'Updating the software package of a LAN switch', added step 'Type the contents

of the configuration file in the system (W6R).', added step 'Check the configuration

of the LAN switch (W6T).', and removed step 'Check the configuration (W6R).'

• in 'Removing a LAN switch', removed step 'Store the configuration file of the com-

munication network (CNW) switch to the system (YFM).'

• in 'Adding a LAN switch', removed the note about Non-BiNOS switches, removed

step 'Check the configuration of the LAN switch (W6T).', and removed step 'Check

the configuration of the LAN switch (W6T).'

• in 'Replacing a switch with one of a different type', added step 'Reload the current

LAN topology (W6G).'

• in 'Short time measurement', corrected 'TRANSMITTED BIT RATE' to 'TOTAL BIT

RATE'

Changes made to the instructions Changing and expanding the LAN topology of the

communication network :

• changed the number of preconfigured topologies from 'up to five' to 'several'

Changes made to the instructions Integrated LAN Administration troubleshooting :



8 DN0423824

Issue 3-2


Id:0900d805805490e9

Summary of changes

• added 'SNMP Trap overload detected in the SNMP configuration'

• in the LAN switch is incorrect, replaced the old example with 3 new examples

• added 'Network element upgrade changed the configuration'

• added 'Errors in SNM P, DHCP, and TFTP operations'


MML command order corrected in Updating the password of a LAN switch.

Changes made between issues 2–3 and 2–2

Removed all references to the TCP/IP Guide.



DN0423824

Issue 3-2

9

Integrated LAN Administration Planning the LAN implementation

Id:0900d805803e99ef

1 Planning the LAN implementationThe management and supervision of LAN switches applies to all the LAN switches that

are integrated in the network element. In some cases, the LAN switches of a third party

are also managed and supervised. All the managed LAN switches are part of the redun-

dancy scheme of the network element. Typically, the LAN switches are connected

directly to the Ethernet ports of the computer units (hosts) of the network element. In the

figure LAN topology of managed and supervised LAN switches in the network element,

the managed and supervised LAN switches are inside the network element boundary.

g This figure is an example. It does not illustrate a LAN switch topology of any real

network element.

Figure 1 LAN topology of managed and supervised LAN switches in the network

element

The examples and instructions given here describe the principles that should be

followed when planning TCP/IP connections, IP subnets, and VLANs. The LAN topology

of a real network element varies according to the type of the network element.

When planning the LAN implementation, consider the following aspects carefully:

• What kind of IP address space you need in routing and on the core site.• What kinds of LAN switches need to be managed and supervised.

• What management principle you are using.

• Which unit must be used as the supervising unit.

• What kind of LAN division you need.

• What kind of VLAN division you need.

• Whether Ethernet-based Message Bus (EMB) is used and supervised.

g In these instructions, the term LAN refers to a group of switches that have been con-

nected and form a communication network (CNW) or internal management LAN for

Ethernet-based Message Bus (EMB) inside a DX200 network element.

ML Switch ML Switch

BSU 0 BSU 1 BSU 2 BSU x

SWU 2 SWU 3

OMU 0 STU 0 BDCU 0

Network elementboundary

Blocked

Forwarding

ML Switch = Multi Layer Switch

SWU 9SWU 8



10 DN0423824

Issue 3-2


Id:0900d805803e99ef

Planning the LAN implementation

1.1 Redundancy scheme of the switching units and LANs

The division of management LANs is based on the redundancy principles of the LAN

switches used by the user plane traffic. The supervising units have two Ethernet inter-

faces that are connected to two redundant LAN switches. If one unit breaks down, thetraffic goes through the other one. In the figure LAN topology of managed and super -

vised LAN switches in the network element, the LAN switch pairs SWU-2/SWU-3 and

SWU-8/SWU-9 share the load according to the redundancy scheme.

When the hardware description of a new LAN switching unit (SWU) is added to the

equipment database, the state of the unit is SE-NH. You can check the state with the

USI command.

The SWU units are created in the hardware configuration as pairs. The first index of a

load sharing pair is an even number, the second one is the next odd number. For

example, SWU-0 and SWU-1 form the first SWU pair, SWU-2 and SWU-3 the second

pair, and so forth.

The redundancy of SWU units is N+1 (load sharing), and the units have a pair redun-

dancy rule. Normally, both units of an SWU pair are in the WO-EX state. Only one of the

units in a pair can be set to a state other than WO-EX at a time.

If you want to set both units to a state other than WO-EX at the same time, you have to

use the forced mode (the FCD parameter of the USC command). When you enter the

forced state transition command, the program gives you a warning and asks you to

confirm the command.

The LAN unit (CNW and EMB) and the switch units (SWU) belonging to the LAN unit

form a hierarchical entity. The LAN unit is the mother unit; the switch units are its child

units. When the working state of the mother unit is changed, the states of the child units

also change with the following exceptions:• A child unit which is not in the same working state as its mother unit can be changed

to the state of the mother unit.

• The working state of switch units that belong to a communication network unit

(CNW) can be changed separately.

When you are managing Ethernet switches of a CNW LAN, it is not recommended that

you change the working state of a communication network unit (CNW). Instead, the

working state of one single switch unit (SWUs) should be changed at a time. When you

are managing Ethernet switches of an EMB LAN, it is not recommended that you change

the working state of a single switch unit (SWU). Instead, the working state of the entire

EMB LAN (EMB) should be changed at once.

1.2 Planning the IP connections

Before you can perform LAN division and IP address space allocation, you need to

check the use of existing IP address space on the core site, and consider how the

routing is done.

According to the principle, the management IP addresses of the LAN switches belong

to an IP address space that is not visible outside the network element. Routing is not

allowed to this address space from outside the network element.

The use of VLANs in the network element also affects the planning of VLANs for the LAN

switch management. You need to plan which LAN switches are put under management

and supervision.



DN0423824

Issue 3-2

11


Id:0900d805803e99ef

If the LAN switches, or some of them, are supervised by the network management

system (NetAct), you need to plan how they are transferred under the supervision of the

actual network element. If a LAN switch already has a management IP address, you

need to decide whether the same IP address is going to be used also after the supervi-

sion change.

g For management and security reasons, it is important that a network element has

all the LAN switches under its own supervision. The supervision of a LAN switch

must not be divided between the network element and the network management

system.

1.3 Selecting the management principle

There are two alternative management principles: inband management and outband

management.

Inband management

In inband management, there is no separate LAN available for management purposes.

Bandwidth must be “borrowed” from the LANs for other purposes. The management

traffic is separated with the VLAN technique. The Ethernet-based Message Bus (EMB)

is managed this way.

Figure 2 Example of LAN switch topology for inband management

Outband management

In outband management, there is a separate LAN for management purposes, and man-

agement functions are carried out independently of the user plane LANs. This allows the

user plane LANs to utilise their full bandwidth capacity. The VLAN technique is used to

separate the particular interfaces of LAN switches for management and security pur-

poses.

BCSU 0CPU

BCSU XCPU

BCSU 0PCU

BCSU XPCU

SWU 0 SWU 2

OMU 0 MCMU 1MCMU 0


secondary routeprimary route


SWU 3SWU 1

VRRP

ML SwitchML Switch

Thin lines are cables for NetAct O&M and signallingtraffic.

Thick lines are cables for Internal LAN administrationtraffic.



12 DN0423824

Issue 3-2


Id:0900d805803e99ef


Outband management requires that there is at least one pair of additional LAN switches

dedicated to management purposes.

In management LANs, the default VLANs are used for incoming traffic of LAN interfaces.

VLANs are used inside a LAN switch when forwarding traffic from one interface toanother, but the outgoing traffic is not tagged with a VLAN ID. This ensures that the man-

agement traffic also goes to those LAN switches where no VLANs have been configured

yet. This kind of situation may occur when a LAN switch has the factory settings.

Example:

The figure Example of LAN switch topology for outband management shows an

example of a LAN topology for outband management. All the following examples of

outband management configuration are based on this topology.

Figure 3 Example of LAN switch topology for outband management

According to the principle, there are two separate LANs for management purposes: one

that contains switches with even index numbers, and one that contains switches with

odd index numbers.

LAN switches SWU-6 and SWU-7 are aggregating switches that bind all the other

switches together. Through the aggregating switches, the management has access to

the other switches.

SWU-6 aggregates the management traffic from the LAN switches that are connected

to EL0 interfaces of all hosts. Correspondingly, SWU-7 aggregates the management

traffic from the LAN switches that are connected to EL1 interfaces of all hosts. In this

example, the CMM unit acts as a gateway to all switches from the management point of

view.

ML Switch ML Switch


SWU 6 SWU 7

Blocked

Forwarding


Thick lines from SWU 6 & SWU 7are cables for LAN management traffic.

Black lines are cables for O&M/Controltraffic.

BSU 0 BSU 1 BSU 2 BSU xCMM 0 OMU 0 STU 0 BDCU 0

SWU 3 SWU 8 SWU 9SWU 2



DN0423824

Issue 3-2

13


Id:0900d805803e99ef

The aggregating switches are used for management purposes only. User plane traffic

does not go through them. In every LAN switch, one interface is dedicated to manage-

ment use.

Comparing inband management and outband management

In situations where both inband and outband management are available, outband man-

agement is highly recommended as the management principle.

In the inband management topology, there are no aggregated switches for Internal LAN

administration traffic. Administration traffic is transferred along with other NetAct O&M

and signalling traffic. In the inband topology, Internal LAN management links are needed

to those LAN switches that are not directly connected to the supervising unit. In the

figure Example of LAN switch topology for inband management, the MCMU unit is a

supervising unit of SWU units and it acts as a gateway to all the switches from the man-

agement point of view. Links between SWU-0 and SWU-2 and between SWU-1 and

SWU-3 are reserved for Internal LAN administration traffic. Other IP traffic types are

dropped out from these links with a suitable VLAN configuration. Administration traffic

from MCMU to SWU-2 is transferred through SWU-0.

When the Ethernet-based Message Bus (EMB) is used, two internal administration

LANs are needed for the supervision and management of the Ethernet switches of EMB.

These internal management LANs are separated from one another.

1.4 Supervising unit

You need to check which unit is going to be the supervising unit for the LAN switches.

The supervising unit acts as a gateway for management traffic from the DX200

computer units to the LAN switches. The Telnet client and the DCHP and TFTP servers

are used for IP address allocation and for transferring the configuration file and software

to and from the LAN switches. In the supervising unit, there is also an SNMP mediator

that forwards SNMP GET and SET requests and responses between DX200 computer

units and the LAN switches. The LAN topology and cabling determine which supervising

unit (or units) can be used. Some actions on EMB Ethernet switches are restricted.

Administration differences between CNW and EMB switches are described later in this

document.

The selection of the supervising unit depends on the management principle.

• If outband management is used, only one computer unit (central memory unit) is the

supervising unit.

• If inband management is used, there must be at least one supervising unit for eachL2 network.

The redundancy scheme of the supervising unit has to be 2N, so that if the supervising

unit breaks down, there is a backup unit to continue the management and supervision

of the LAN switches.

A supervising unit has one different IP address configured in each Ethernet interface.

The IP address belongs to the same IP subnet as the management addresses of the

LAN switches connected to the supervising unit.

The IP addresses of the EL0, EL1, EMB0, and EMB1 interfaces must not be in the same

IP subnet. For example, the IP address configured in the EL0 interface of the CMM unit

belongs to the same IP subnet as the management IP address of SWU-6, and the IP

address configured in the EL1 interface of the CMM unit belongs to the same IP subnet



14 DN0423824

Issue 3-2


Id:0900d805803e99ef


as the management IP address of SWU-7. EMB Ethernet switches are added to their

own EMB-0 and EMB-1 LAN.

The management IP addresses for EMB Ethernet switches are configured in the EMB0

and EMB1 interfaces of the supervising unit. The IP addresses of the EMB0 and EMB1interfaces must not be in the same IP subnet.

For instructions on how to check the supervising unit, see Use of the LAN links in LAN

Switches.

1.5 Planning the LAN division

The internal management LANs for NetAct O&M, Control, and User plane switches are

described as CNW functional units. The internal management LANs for Ethernet-based

Message Bus switches are described as EMB functional units. You need to decide into

how many LANs the network element is going to be divided. This has a direct impact on

how big a part of the network element is affected by a LAN switchover.The redundancy principle requires that there be an even amount of LANs. The redun-

dancy principle of LAN switching units is N+1 (load sharing), and the units have a pair

redundancy rule. A supervising unit can be connected directly to two O&M, Control, and

User plane L2 networks; one for each Ethernet interface (EL0 and EL1) of the supervis-

ing unit. The same supervising unit can also be connected directly to two Ethernet-

based Message Bus L2 networks; one for each Ethernet interface (EMB0 and EMB1) of

the supervising unit.

You can give names to the LANs to separate them according to their usage. The names

are only for informative purposes, to help you when reading information about the LANs.

The IP address space used by the management and supervision of LAN switches is

divided into IP subnets so that there is an address allocation for each LAN (CNW or

EMB). If you want to use an IP address that has been defined beforehand for a LAN

switch, the IP address space must be planned so that it includes this IP address.

Example:

In the figure Example of LAN switch topology for outband management, the LAN

topology is divided into two LANs. One of them consists of the even-indexed LAN

switches, and the other one of the odd-indexed switches. One IP subnet is planned for

the supervising unit, for example CMM. The plan for IP address spaces and naming is

described in the table Example of an IP address plan below.

The IP subnet (SUBN1) for the supervising unit is created because this is the only way

to configure the supervising unit in the system. The added supervising unit receives an

LAN ID LAN unit LAN name (info) IP address range

2 CNW-0 MGMT1 10.12.18.1–10.12.18.62 /26

3 CNW-1 MGMT2 10.12.18.65–10.12.18.126 /26

4 EMB-0 EMB0 10.12.18.129–10.12.18.190 /26

5 EMB-1 EMB1 10.12.18.193–10.12.18.254 /26

10 SUBN1 10.12.19.1–10.12.19.6 /29

Table 1 Example of an IP address plan



DN0423824

Issue 3-2

15


Id:0900d805803e99ef

IP address from the address space that was allocated to the IP subnet. The system,

however, does not use this IP address at all.

1.6 Planning the VLAN divisionVirtual Bridged Local Area Networks (IEEE 802.1Q) is a group of devices on one or

more LANs that are configured so that they can communicate as if they were attached

to the same wire, when in fact they are located on a number of different LAN segments.

Because VLANs are based on logical instead of physical connections, this ensures very

flexible user/host management, bandwidth allocation and resource optimisation.

The IEEE 802.1Q specification establishes a standard method for tagging Ethernet

frames with VLAN membership information. The IEEE 802.1Q standard defines the

operation of VLAN Bridges that permit the definition, operation and administration of

Virtual LAN topologies within a Bridged LAN infrastructure. The standard is intended to

address the problem of how to break large networks into smaller parts to prevent broad-

cast and multicast traffic from grabbing more bandwidth than necessary. The standard

also helps provide a higher level of security between segments of internal networks.

The key for the IEEE 802.1Q to perform the above functions is in its tags. 802.1Q-com-

pliant switch ports can be configured to transmit tagged or untagged frames. A tag field

containing VLAN and IEEE 802.1p priority information can be inserted into an Ethernet

frame. If a port has an 802.1Q-compliant device attached (such as another VLAN-aware

switch), these tagged frames can carry VLAN membership information between

switches, thus letting a VLAN span multiple switches. However, it is important to ensure

that ports with non-802.1Q-compliant devices attached are configured to transmit

untagged frames. DMX computer units can act as 802.1Q-compliant or non-802.1Q-

compliant devices.

There are several VLANs in the network element. They are used for different purposes;

see the Site connectivity documentation for details about the VLANs. After that, you can

plan the VLANs for management purposes.

A LAN switch that has not been configured yet must not increase the congestion of the

LAN broadcast domain. Broadcast traffic, for example, must not propagate to unwanted

interfaces or LAN switches. Management traffic is allowed only in particular interfaces.

All the switches must be configured so that only management traffic is allowed to travel

to the management LANs. The VLAN technique is used to separate the LANs.

The management and supervision of LAN switches require that management IP

addresses be assigned to the switches.

In the figure Example of LAN switch topology for outband management, the LAN

switches are configured to form two LANs (even indexed and odd indexed).

g VLANs are not configured in EMB Ethernet switches.

These LANs also form VLANs as presented in the figure VLANs of management LANs.

In this figure, CMM computer units are configured as non-802.1Q-compliant devices;

thus not tagged Ethernet frames are transferred between the CMM unit and LAN

switches. All switch ports in the figure are left untagged, and their default VLAN is con-

figured as 10 and 11 for the ports indicated in dark grey and light grey, respectively.



16 DN0423824

Issue 3-2


Id:0900d805803e99ef


Figure 4 VLANs of management LANs

VLAN techniques make it possible to construct multiple Ethernet broadcast domains

(networks) over a single physical medium so that these broadcast domains are com-

pletely separated from each other on the Ethernet level. When a DMX computer unit is

configured as a 802.1Q-compliant device, this means that the computer unit adds VLAN

tagging to all Ethernet frames sent by the physical Ethernet interface in question. Con-

versely, on the data receiving side the Ethernet driver filters out (drops out) Ethernet

frames not equipped with valid VLAN tagging related to that physical Ethernet interface.

As shown in the figure Configuration of 802.1Q-compliant DMX computer unit and LAN

switch port, a virtual network interface (for example, vlan 8) is created in the computer

unit and mapped to a physical Ethernet interface (for example, el0). Several virtual inter-

faces can be mapped to one physical interface at the same time. The IP address is

assigned to a virtual interface instead of a physical one. A LAN switch port connected to

a DMX unit is configured as a tagged switch port (dot1q encapsulation). For more infor-

mation, see the user guides for the various ESB variants (ESB14-A, ESB20, ESB20-A,

and ESB26 ).

Figure 5 Configuration of 802.1Q-compliant DMX computer unit and LAN switch

port

CMM 0

18 17 16 14

SWU 7

18 17 16 14

CMM 1

SWU 2 SWU 3 SWU 8 SWU 9

VLAN 10

VLAN 11

19 19 19 19

SWU 6

EL0 EL1 EL0 EL1

IP traffic type A192.b.c.d / 24

IP traffic of InternalLAN Management

10.b.c.d / 24

DMX computer unit(802.1Q-compliant)

VLAN 8

VLAN 1

EL0

1/1/12

TAGGED

ESB LAN switch (SWU)

member of VLANs

PVID1

1

VID8

8

VID1



DN0423824

Issue 3-2

17


Id:0900d805803e99ef

1.7 Multiple Spanning Tree Protocol (802.1s) and load sharing

The Multiple Spanning Tree Protocol (MSTP) is defined in the 2003 edition of IEEE

Standard 802.1Q. MSTP is an evolution of the Spanning Tree Protocol and the Rapid

Spanning Tree Protocol, and was introduced in IEEE 802.1s as an amendment to802.1Q, 1998 edition. Standard IEEE 802.1Q–2003 now includes MSTP.

The Spanning-Tree Protocol (STP) as defined in IEEE 802.1D is a link management

protocol that provides path redundancy while preventing undesirable loops in the

network. For an Ethernet network to function properly, only one active path can exist

between two end stations (data terminal equipment, DTE). Bridged loops occur in

networks for a variety of reasons. The most common cause of bridged loops in networks

are attempts to provide redundancy of trunk links, that is, cables between L2 switches.

When one link or switch fails, another can take over. Multiple active paths between

stations cause loops in the network. If a loop exists in the network topology, some

switches will see stations appear on both sides of the switch. This duplicated path

confuses the forwarding algorithm and allows the forwarding of duplicate frames. In theworst case, this may lead to a broadcast storm, which may halt the whole Layer 2

segment.

STP is a technology that allows bridges to communicate with each other in order to

discover physical loops in the network. The protocol then specifies an algorithm that

bridges can use to create a loop-free logical topology. In other words, STP creates a tree

structure of loop-free leaves and branches that spans the entire Layer 2 network.

Spanning-Tree Protocol operation is transparent to end stations (DTE), which are

unaware of whether they are connected to a single LAN segment or a switched LAN of

multiple segments. Where two bridges are used to interconnect the same two computer

network segments, STP is a protocol that allows the bridges to exchange information so

that only one of them will handle a given message that is being sent between two com-puters within the network. The STP algorithm finds the most efficient path when faced

with multiple paths. STP forces certain redundant data paths into a standby (blocked)

state. If one network segment in the STP becomes unreachable, or if STP path costs

change, the spanning-tree algorithm recalculates the spanning-tree topology and re-

establishes the link by activating the standby (next best) path.

Bridge Protocol Data Units (BPDUs) are used by bridges in a network to exchange infor-

mation about their status. The Spanning-Tree Protocol uses the BPDU information to

select the root switch and root port for the switched network, as well as the root port and

designated port for each switched segment.

The Spanning-Tree Protocol root switch is the logical center of the spanning-tree

topology in a switched network. All paths that are not needed to reach the root switch

from anywhere in the switched network are placed in Spanning-Tree Protocol standby

(blocked) state.

The switch with the lowest bridge ID is selected as the root switch. If all switches are

enabled with default settings, the switch with the lowest MAC address in the network

becomes the root switch. The switch with the second lowest bridge ID becomes the sec-

ondary root. All Ethernet frames that are going outside or coming in from or into an L2-

switched network are always transferred through the root switch. When configuring

STP, it is strongly recommended to predefine the root and secondary root switches man-

ually. Normally switches from the distribution layer (directly connected to the L3 router)

are selected as root and secondary root.



18 DN0423824

Issue 3-2


Id:0900d805803e99ef


The Multiple Spanning Tree Protocol (MSTP) is an evolution of the Spanning Tree Pro-

tocol. When common STP is used, there is only one STP process running in the switch.

This means that all Ethernet frames that are going outside or coming in from or into an

L2-switched network are bridged through one switch (root). The secondary root does not

participate in bridging.

With the Multiple Spanning Tree Protocol (MSTP), multiple STP processes (up to 15)

can be run at the same time. MSTP allows Ethernet frames assigned to different VLANs

to follow separate paths, each based on an independent Multiple Spanning Tree

Instance (MSTI). All these Multiple Spanning Tree Instances belong to the same

Multiple Spanning Tree Region.

The Multiple Spanning Tree Protocol and algorithm provide a loop-free topology for any

LAN or bridged network. If there is only one Virtual LAN (VLAN) in the network, single

(traditional) STP works appropriately. However, if the network contains more than one

VLAN, the logical network configured by single STP does not work properly in all LAN

topologies. STP may block the path of some VLAN. The Multiple Spanning TreeProtocol configures a separate Spanning Tree for each VLAN group and blocks the links

that are redundant within each Spanning Tree. VLANs 1–4094 can be freely assigned

to configured Multiple Spanning Tree Instances.

MSTP root and secondary root switches can be selected freely for each Multiple

Spanning Tree Instance. This means that in practice, the Multiple Spanning Tree

Protocol offers the possibility of load sharing of Ethernet frames transferred from or to

the Layer 2 segment.



DN0423824

Issue 3-2

19


Id:0900d805803e99ef

Figure 6 Load sharing with Multiple Spanning Tree Protocol (MSTP)

The figure shows a network where two Multiple Spanning Tree Instances (MST1 and

MST2) have been created. VLAN 2 and 4 are mapped to MST1 and VLAN 5 and 7 are

mapped to MST2. The distribution layer switch (Multi Layer Switch) on the left has been

selected as root for the MST1 instance; the one on the right has been selected as root

for MST2. The secondary root roles are configured vice versa. In this configuration, all

Ethernet traffic of VLANs 2 and 4 is transferred through the ML switch on the left, andall Ethernet traffic of VLANs 5 and 7 is transferred through the one on the right. So we

have configured load sharing between MST1 and MST2.

If, for example, the ML switch on the right goes down for some reason and MST2 loses

its active root switch, the Spanning Tree inside the MST2 instance is renegotiated and

the secondary root switch takes the role of new primary root. After the spanning-tree

topology of MST2 has been rearranged, the traffic of VLANs 5 and 7 is transferred

through the ML switch on the left. With Multiple Spanning Tree Instances, it is possible

to get redundancy in the Layer 2 segment. When the ML switch on the right recovers

from the fault, the root roles are switched back and the traffic of VLANs 5 and 7 is moved

back to the ML switch on the right.

In Nokia network elements, the benefits of the Multiple Spanning Tree Protocol can beused to full capacity. Different IP traffic types (such as Internal LAN administration,

MSTP region mySite

device#show mstp configurationName

RevisionInstance- - - - - - - -

01

2- - - - - - - - - - - - - - - - - - - - - - -

[mySite]

1

Vlans mapped- - - - - - - - - - - - - -1,3,6,8-40942,45,7

V L A N

4

V L A N

2

V L A N

7

V L A N

5

MST 1 MST 2

(2,4)(2,4) (5,7)

(5,7)

VRRP

(2,4,5,7)

MST 1 RootMST 2SecondaryRoot

MST 2 RootMST 1SecondaryRoot



20 DN0423824

Issue 3-2


Id:0900d805803e99ef


NetAct O&M, Control and User plane signalling) can be encapsulated in their own

VLANs. After this, the count of Multiple Spanning Tree Instances is decided and VLANs

are mapped to MSTIs. Usually one MSTI is created per distribution switch. Note that you

can encapsulate more than just one IP traffic type (that is, IP subnet) within the same

VLAN. When configuring MSTP, all switch ports that are directly connected to DMX

computer units should be defined as MSTP edge ports. That way, the spanning-tree

topology will be rearranged more quickly.

For information on various ESB variants, see the following documents: ESB14-A,

ESB20, ESB20-A, and ESB26 .

1.8 LAN topology with third-party L2 switches

In some older network elements with M92-mechanics hardware, third-party L2 switches

may be used. These third-party switches are placed outside of the DMX cabinet. Despite

of this, these switches are integrated as a part of the network element. Configuration and

maintenance of third-party switches has to be done manually. The Integrated LAN

Administration feature supervises third-party switches and their connections.

Figure 7 LAN topology with third-party L2 switches

BCSU 0CPU

BCSU XCPU

BCSU 0PCU

BCSU XPCU

OMU 0


secondary route

primary route

ML Switch = Multi Layer Switch VRRP

ML SwitchML Switch

n nes are ca es or et ct an s gna ngtraffic.

Thick lines are cables for Internal LAN administrationtraffic.

SWU 0 SWU 1

cabinet

3rd partyL2 switches

MCMU 1MCMU 0



DN0423824

Issue 3-2

21

Integrated LAN Administration Preparing LAN implementation

Id:0900d805802904e3

2 Preparing LAN implementation

2.1 Activating LAN Device IntegrationLAN Device Integration is an optional feature. When the LAN Device Integration feature

is not active (default value), the switches and connections of the internal management

LANs are not supervised and no maintenance task for switches can be performed with

the help of this feature. You can toggle the feature on and off by changing the value of

the LAN_ADMINISTRATION parameter. LAN Device Integration can only be configured

in a network element if it is already activated.

g No configuration changes are allowed when the network element is split into a

TELE/TRIAL configuration.

Measurements should be taken in a stable environment in order to yield reliable

data. Running measurements should therefore be stopped before any LAN topology

changes are made.

Steps

1 Check the value of the LAN_ADMINISTRATION parameter (WOI).

ZWOI:2,1120;

2 Change the value of the LAN_ADMINISTRATION parameter (WOC).

Steps

a Set the feature On (value 1).

ZWOC:2,1120,1;

b Set the feature Off (value 0 ).

ZWOC:2,1120,0;

2.2 Selecting the LAN topology

The system automatically selects one preconfigured network element topology. You first

have to check that the preconfigured topology is similar to the LAN connection that exist

in the network element.

g If a preconfigured topology exists, it is highly recommended that you use it. If,

however, it is absolutely necessary to use a different kind of hardware in the network

element than the hardware configuration and cabling defined by Nokia Siemens Net-

works, or if no preconfigured topology exists, you have to modify the preconfigured

topology.

Steps

1 Print out the selected preconfigured LAN topology (W6I).

a) Internal LAN switches:

ZW6I;



22 DN0423824

Issue 3-2


Id:0900d805802904e3

Preparing LAN implementation

b) EMB LAN switches:

ZW6I::T=EMB;

2 Compare the preconfigured topology to the existing network element topology.

Compare the printout to the existing LAN topology of the network element (see the

network-element-specific Use of LAN ports documentation for details). All the LAN

switch indexes and connections should be identical in the preconfigured topology and in

the existing one. If there are differences, select another preconfigured topology.

3 To implement this step, choose one of the following alternatives:

a Select a new topology (W6G).

ZW6G:<topology index>;

You get the following kind of printout:/* IDENTIFY TOPOLOGY INDEX:

T1 - T4 (CURRENT IS T1, NETWORK ELEMENT MSCi)

P ... ACTIVATE PREVIOUS TOPOLOGY

R ... RELOAD CURRENT TOPOLOGY */

☞ The parameter guide of the W6G command shows the currently active topology,

the network element type of the active topology, and the number of different

topologies found in the preconfigured topology file.

b Modify the preconfigured topology.

If none of the preconfigured topologies matches the existing LAN topology of thenetwork element, you have to modify the preconfigured topology file. For instruc-

tions, see Changing and expanding the LAN topology.

2.3 Network element upgrades

To be able to access the LAN switches of a communication network (CNW) through a

telnet connection, you need to know the password defined for each switch. Telnet con-

nections to EMB LAN switches are not allowed. Before a network element upgrade,

make sure you know the passwords of all CNW and EMB LAN switches.

Upgrade is made with semi-automatic HIT macro, upgrade procedure. Procedure will

take care of needed checking and data transfer. Upgrade is described in more detailedlevel in release upgrade documents.

Integrated LAN Administration does not work during upgrade in TRIAL configuration. In

TRIAL configuration, LAN topology changes on the TELE or TRIAL side are prohibited.

In a network element upgrade, upgrade procedure macro copies the configuration files

automatically to the new software build.

Topology Management files

The topology management configuration file and all LAN switch configuration files are

located in the LFILES or ASWDIR directory in the source software build and they are

copied to the ASWDIR directory in the new software build during upgrade.

• The name of the topology management configuration file is TGYFILGX.FIL.



DN0423824

Issue 3-2

23

Integrated LAN Administration Preparing LAN implementation

Id:0900d805802904e3

• The names of the LAN switch configuration files correspond to the pattern TGY-

Cxxxx.IMG, where xxxx represents different numbers depending on the LAN

switch’s place in the topology.

g If these files do not exist, this feature has not been in use. In this case, create onlya backup copy of the configuration to a remote laptop or to the LAN switch NVRAM.

If you do not copy these files, you must choose the correct topology to be used (see

Selecting the LAN topology), then store the LAN switch passwords in the network

element (see Updating the password of a LAN switch) and load the configuration file

from the LAN switch to the system (see Configuring a LAN switch of the communi-

cation network (CNW)).

Steps

1 Create a backup copy of the configuration.

The system does not allow changes to the contents of the EMB LAN switch configura-

tion. The configuration files are preconfigured and they are automatically uploaded to

the EMB LAN switches after each successful DHCP request. To make a backup copy

of the running configuration, select any of the following alternatives.

☞ You can also create a backup copy later, when you are configuring the LAN switch

(see Configuring LAN switches).

• Copy the running configuration to a remote laptop with the TFTP server.

device-name# copy running-config < laptop IP-address>

C:/backups/swu_0.txt

• Copy the running configuration to the LAN switch NVRAM.

device-name#copy running-config backup-config

LAUDATGX file and ILDATA database

The LAUDATGX.IMG file and the ILDATA database are converted during the upgrade

from the old software build to the new software build. The ILDATA database consists of

the following database files: ILD001GX.IMG – ILD028GX.IMG. The data dictionary

files of ILDATA are the following: D01069GX.IMG and D02069GX.IMG.

2.4 Updating the size of the event log

When the network element is upgraded, the size of the event log is not modified auto-

matically. You can update it manually.

Steps

1 Update the size of the LAN hardware supervision log (YFL).

ZYFL:UPD,<size>;

Further information

See also Handling LAN hardware supervision logs.



24 DN0423824

Issue 3-2


Id:0900d805802904e3

Preparing LAN implementation

2.5 Enabling or disabling the automatic loading of configura-

tion files

The parameter that sets whether automatic configuration file loading is allowed for

certain type of LAN switches may have been modified in the old build. This parameter

setting is not updated during the network element upgrade. Therefore, you need to

change the parameter manually after the software update.

Steps

1 Check the properties that are specific to the type of the LAN switch in the old build

(YFM).

ZYFM:IST;

2 Change the properties in the new build as needed (YFM).

Depending on whether you want to enable or disable the automatic loading of the con-

figuration files, select the relevant option below.

• Enable the automatic loading of the configuration file.

ZYFM:ENA,<LAN switch type>;

• Disable the automatic loading of the configuration file.

ZYFM:DIS,<LAN switch type>;



DN0423824

Issue 3-2

25

Integrated LAN Administration Creating LANs in a new network element

Id:0900d8058042902a

3 Creating LANs in a new network elementFormerly, a LAN switch was configured in a computer unit (such as the MCMU) as one

plug-in unit among others. When LAN Device Integration is used, however, a LAN switch

is configured in a DX 200 functional unit, usually the SWU. One physical LAN switch

plug-in unit (for example ESB20-A) thus comprises one SWU functional unit. The SWU

has working states that are maintained by the DX 200 Recovery System.

The hardware description of a LAN switch plug-in unit is stored in the equipment data-

base. The switching unit is usually configured to the same cartridge as the computer

unit, and otherwise to the LANU cartridge.

3.1 Creating the hardware configuration description

3.1.1 Creating the hardware configuration of an integrated ESB LANswitch of a DX 200 network element (M98 mechanics)

The following instructions show how the hardware configuration of an integrated LAN

switch is created when the switch consists of Nokia-proprietary hardware.

Steps

1 Check that a cartridge description has been created in the equipment database

(WTI).

ZWTI:C;

2 Create a cartridge description, if it has not been created (WTC).

ZWTC:<cartridge type>,<cartridge coordinate>:

[AL=<location and alarm data of hardware alarms connection cartridge> |

P1=<location of cartridge containing 1st power supply> |

P2=<location of cartridge containing 2nd power supply> |

P3=<location of cartridge containing 3rd power supply> |

P4=<location of cartridge containing 4th power supply> ]...;

For example: ZWTC:CC4C_A,1A2-0:AL=1A1-6-2,P1=1A2-0;

3 Create a functional unit description for the switching unit (WTU).ZWTU:SWU,<unit index>:<cartridge coordinate>;

For example: ZWTU:SWU,0:1A2-0;

4 Create a plug-in unit description for the LAN switch (WTP).

ZWTP:SWU,<unit index>:<piu type>,<piu index>,<track>;

For example: ZWTP:SWU,0:ESB20_A,0,2;

Further information

In a network element with M92 mechanics, a LAN switch cannot be recognised by its

location. In M92 mechanics, the location coordinates differ from the format used in M98



26 DN0423824

Issue 3-2


Id:0900d8058042902a

Creating LANs in a new network element

mechanics. In practice, this means that in a network element with M92 mechanics, the

LAN switches have to be configured and maintained manually.

For more detailed instructions on how to create hardware configuration descriptions of

cartridges, plug-in units, and functional units, see Equipment Management ( WT command group) and Hardware Configuration Management .

3.1.2 Creating a hardware configuration of a 3rd-party LAN switch of a

DX 200 network element (M98 mechanics)

The following instructions show how the hardware configuration of an integrated LAN

switch is created when the switch consists of 3rd-party hardware. The switch is used as

an L3 switch.

Steps

1 Check that a cabinet description has been created in the equipment database

(WTI).

ZWTI:J;

2 Create a cabinet description, if it has not been created (WTJ).

ZWTJ:IPCS,<rack or cabinet coordinate>:

AL=<location and alarm data of hardware alarms connection cartridge>,

AL2=<location of second hardware alarms connection cartridge>,

PDFU=<number of PDFU>;

3 Check that a cartridge description has been created in the equipment database

(WTI).

ZWTI:C;

4 Create a cartridge description, if it has not been created (WTC).

ZWTC:<cartridge type>,<cartridge coordinate>:

[AL=<location and alarm data of hardware alarms connection cartridge> |

P1=<location of cartridge containing 1st power supply> |

P2=<location of cartridge containing 2nd power supply> |

P3=<location of cartridge containing 3rd power supply> |P4=<location of cartridge containing 4th power supply> ]...;

For example: ZWTC:CASE,1C1-0:P1=1C1-0;

5 Create a functional unit description for the switching unit (WTU).

ZWTU:SWU,<unit index>:<cartridge coordinate>;

For example: ZWTU:SWU,18:1C1-0;

6 Create a plug-in unit description for the LAN switch (WTP).

ZWTP:SWU,<unit index>:<piu type of 3rd-party piu>,<piuindex>,<track>;



DN0423824

Issue 3-2

27


Id:0900d8058042902a

For example: ZWTP:SWU,18:CIS3550,0,1;

3.2 Working states of LAN switches

The LAN switching unit has the following working states: SE-NH, SE-OU, TE-EX, and

WO-EX. Before any management operations or supervision can be done on the LAN

switch, the SWU unit needs to be activated in the system. Before activation, the working

state of the SWU has to be changed manually to WO-EX. It is not recommended to

change the working state of a single EMB LAN switch. Instead, the working state of the

entire EMB LAN should be changed at once. If necessary, the working state of a single

EMB LAN switch can be changed with the FCD parameter. When the working state of

the EMB unit is SP-EX, the working state of the LAN switches of the EMB LAN isWO-EX.

The unit can be restarted only when its state is TE-EX. The reset is done with the YFM

command.

g Plug-in unit diagnostics of the SWU unit can be run when the working state of theswitch is WO-EX or TE-EX. The diagnostics do not affect traffic.

When the working state of a LAN switch is changed from WO-EX to TE-EX, the LAN

switch is still capable of forwarding Ethernet frames as before. From the point of view of

the system, which has a suitable redundancy mechanism, the IP traffic is switched to

use the redundant LAN. IP traffic that cannot be switched to the redundant LAN is still

forwarded via the LAN switch in stateTE-EX, which keeps forwarding Ethernet frames

until it loses the forwarding capability. This happens for example when the LAN switch

is reloading. After maintenance, a switch normally recovers after a short break and will

then forward traffic as before.

Steps

1 Check the working state of a LAN switch (USI).

ZUSI:SWU,<unit index>;

2 Change the working state of a LAN switch in the CNW LAN (USC).

ZUSC:SWU,<unit index>:<working state>;

3.3 Creating TCP/IP connections

The following data is transmitted to the LAN switch in a DHCP message:

• IP address

• netmask

• destination IP address (not used in current network element configurations)

• destination netmask (not used in current network element configurations)

• gateway IP address

• supervisor unit IP address

• lease time infinite

• configuration file name and path

g In a 3rd-party switch, these settings have to be made manually.



28 DN0423824

Issue 3-2


Id:0900d8058042902a


Steps

1 Create the LANs (WYB).

If you only give the start point of the IP address range in the command, the end point is

calculated automatically.

ZWYB:<LAN id>:<LAN unit type>,<LAN unit index>,<LAN info>:<ip

address range start>:<ip address range end>:<netmask

length>:<destination IP address>,<destination netmask

length>:<gateway ip address>;

For example:

ZWYB:2:CNW,0,MGMT1:10.12.18.1:10.12.18.62:26:::;

ZWYB:3:CNW,1,MGMT2:10.12.18.65:10.12.18.126:26:::;

ZWYB:4:EMB,0,EMBLAN0:10.12.18.129:10.12.18.190:26:::;

The internal management LAN (CNW) and the EMB LAN (EMB) are created accord-

ingly.

For LANs behind the L3 switch, give also the destination IP address and gateway:

ZWYB:4:CNW,2,MGMT3:10.12.18.130:10.12.18.190:26:10.12.18.0,26:1

0.12.18.129;

g The first address in the address space is always configured to the supervisor unit.

2 Create the IP subnets (WYA).

If you only give the start point of the IP address range in the command, the end point is

calculated automatically.

ZWYA:<ip subnet id>,[<ip subnet info>]:<ip address range

start>:[<ip address range end>]:[<netmask length>]::;

For example: ZWYA:10,SUBN1:10.12.19.1:10.12.19.6:29::;

3 Create hardware descriptions of the supervisor units in the equipment database,

if they have not been created (WTU).

ZWTU:<unit type>,<unit index>:<cartridge coordinate>;

4 Add the supervisor units to the IP subnet (WYC).

ZWYC:C:10:CMM,<unit index of working unit>;

5 Create hardware descriptions of the switching units in the equipment database

(WTU).


6 Add the switching units to the LAN (WYC).

ZWYC:S:<LAN id>:<unit type>,<unit index>:<superv unit

type>,<superv unit index>:[IP address];



DN0423824

Issue 3-2

29


Id:0900d8058042902a

g Only internal LAN switches may be added to the CNW LAN, and only EMB LAN

switches may be added to the EMB LAN.

Steps

a Add the management switches (aggregating switches SWU-6 and SWU-7) to

the LAN.

ZWYC:S:2:SWU,6:CMM,0::;


b Add the other switches to the LAN.





7 Check that the data is correct (WYI).

Steps

a Print out the LAN descriptions.

ZWYI:L;

Compare the printout to the plan (see Planning the IP connections).

b Check the unit descriptions.

ZWYI:U;

Compare the printout to the plan (see Planning the IP connections).

8 Change the working state of the LAN switch to WO-EX (USC).

ZUSC:SWU,<unit index>:SE:;

ZUSC:SWU,<unit index>:TE:;

ZUSC:SWU,<unit index:WO:;

3.4 Preconfiguring LAN switches

The system uses location information to identify the LAN switch that sends the DHCP

messages. The ESB-type switches can read their own location.

The location is set using either the address coding module (ADMODD) installed at the

back of the computer cartridge or by CABID and CARID bridge connectors used with the

LASWC-A cartridge. The location number must be the same in the system topology

management and in the LAN switch.

CABID and CARID bridge connectors are prewired depending of the location of

LASWC-A. For instructions on how to change the location number in the ADMODD

module, see Jumper Settings of the Cartridges in i-series Network Elements.



30 DN0423824

Issue 3-2


Id:0900d8058042902a


When implementing new LAN switches or a new network element, the LAN switches

need not be preconfigured, because the factory default settings and the default config-

uration file from the system include all the necessary preconfigurations.

If the LAN switches have been in use, they have to be preconfigured.If it is safe to reset the LAN switch, check that the version of the LAN switch software is

valid for the use of Integrated LAN Administration. For instructions on how to change the

software version, see Updating the software package of a LAN switch. The system gives

an alarm if the software package in the LAN switch is old.

The supervision and management of LAN switches require that certain features have

been activated in the LAN switches:

• The STP/MSTP/RSTP must be enabled in the LAN switches of the communication

network (CNW) in order to avoid loops in the LAN topology. The STP/MSTP/RSTP

must be disabled in the LAN switches of the Ethernet-based Message Bus (EMB).

• The DHCP must be enabled to get the system-allocated management IP address

for the LAN switches automatically via the DHCP procedure.

The DHCP for a LAN switch of type ESB20 is enabled through the user interface

(console interface) of the ESB20. If the system-allocated IP address is not used, the

DHCP is not enabled in the LAN switch.

• During the DHCP procedure, the LAN switch receives a configuration file (running-

configuration) from the system and executes it. After the DHCP procedure, the LAN

switch saves this configuration file (running-configuration) as startup-configuration.

The configuration file can also be uploaded manually with an MML command and

will then be processed in the same way as in the DHCP procedure.

• Third-party switches cannot be configured with the DHCP procedure. Therefore all

settings to these switches must be made manually.

Check the settings given below for each LAN switch.

You may not change the contents of any configuration files for EMB LAN switches. A

predefined configuration file is uploaded automatically from the system to the EMB LAN

switch in a successful DHCP sequence. Because of this, it is not possible to establish a

Telnet connection to the EMB switch with the W6T command or to download a configu-

ration file from the EMB switch to the system.

Use the W6R command to display the configuration file of the EMB switch on the screen.

g The Spanning Tree protocol is not used in EMB LAN switches.

Steps


a Enable the DHCP and the uploading/downloading of the configuration file in a

switch of type ESB20.

1. In the main menu, select 1.

2. In the following menu, select 6 .

3. In the following menu, select 4.

4. To enable the DHCP, select Yes.

5. In the following menu, select 7 .

6. To enable uploading/downloading of the configuration file, select Yes.

7. Reset the switch if it is safe to do so.



DN0423824

Issue 3-2

31


Id:0900d8058042902a

When the switch has been reset, it starts asking for the IP address via the DHCP

procedure.

b Enable the DHCP in a switch of type ESB14-A, ESB20-A, or ESB26.

1. ESB20-A>enable

2. ESB20-A#configure terminal

3. ESB20-A(config)#

4. ESB20-A(config)#ip address dhcp

Getting IP configuration parameters via DHCP

client

5. ESB20-A(config)#end

6. ESB20-A#

If the DHCP has been shut down in the LAN switch, enable it again.


a Enable the STP/RSTP in a switch of type ESB20.

1. In the main menu, select 2 .

2. To enable the STP, select Yes.

b Enable the STP/MSTP/RSTP in a switch of type ESB14-A, ESB20-A, or ESB26

used in the communication network (CNW).

To implement this step, choose one of the following alternatives:

a Steps

a Enable the RSTP.

ESB20-A#configure terminal

ESB20-A(config)#

ESB20-A(config)#protocol

ESB20-A(cfg protocol)#rapid-spanning-tree enable

ESB20-A(cfg protocol)#

ESB20-A(cfg protocol)#end

ESB20-A#

b Save the configuration changes.

ESB20-A#write memory

Building the configuration...

Configuration is successfully written to

NVRAM

c Check the changes in the startup configuration.

ESB20-A#show startup config

You get the a printout similar to the following example:

! NVRAM Configuration:

!! Version 3.11.1



32 DN0423824

Issue 3-2


Id:0900d8058042902a


!

ip address dhcp

!

! Snmp-server configuration:

!

...

!

! Protocol configuration:

!

protocol

rapid-spanning-tree enable

!

! VLAN configuration:

...

!

ESB20-A#

3 Configure the SNMP in a LAN switch of type ESB20.

a) In the main menu, select 2.

b) For Read community name, set the value public .

c) For Write community name, set the value public .

d) For Trap community name, set the value public .

e) For Send alert traps, set the value Yes.

f) For Advanced Mode, set the value No.

Further informationNon-BiNOS LAN switches (ESB20) are always configured manually.

3.5 Activating LAN switches

LAN switch activation means that the system is allowed to provide data (for example, an

IP address) in response to a LAN switch DHCP message, and to start supervising the

LAN switch and the LAN connections.

When the switch has been activated in the current LAN topology and it has received an

IP address, you can start to analyse and maintain LAN switches with the commands of

Integrated LAN Administration. Integrated LAN Administration can only supervise

switches and connections that are activated in the topology.

Before you start

Check that all TCP/IP connections of the LAN switch have been created. For instructions

on how to configure the connections, see Creating TCP/IP connections.

Steps

1 Check that the LAN switching unit is in working state (USI).

ZUSI:SWU,<unit index>::;



DN0423824

Issue 3-2

33


Id:0900d8058042902a

2 If the switching unit is not in working state, change the state (USC).

If necessary, use the forced parameter (FCD).

ZUSC:SWU,<unit index>:SE:;

ZUSC:SWU,<unit index>:TE:;

ZUSC:SWU,<unit index>:WO:;

3 Update the LAN switch password in the system.

For instructions, see Updating the password of a LAN switch.

4 Select the mode of automatic configuration file loading to communication

network LAN switches (CNW).

To implement this step, choose one of the following alternatives:

a Steps

a To implement this step, choose one of the following alternatives:

1 Enable the automatic loading of the configuration file (YFM).

If automatic loading is enabled, the system transfers the configuration file to

the LAN switch automatically with DHCP message.

ZYFM:ENA,ESB20_A;

2 Disable the automatic loading of the configuration file (YFM).

Steps

1 If the LAN switch is in active use, disable the automatic loading of

the configuration file.

ZYFM:DIS,ESB20_A;

2 Transfer the configuration file to the switch.

g First check that the configuration file is valid for the communication

network LAN switch. If necessary, the configuration files for

Ethernet-based Message Bus LAN switches (EMB) are loaded auto-

matically after each successful DHCP sequence. Only predefined

configuration files are used with EMB LAN switches. Users are notallowed to make any changes in the configuration files of EMB LAN

switches.

3 Configure the LAN switch via telnet.

5 Activate the LAN switch (W6E).

ZW6E:SWU,<unit index>:A;

After the activation, the LAN switch can get the IP address in the DHCP message, and

the supervision of the switch starts. Normally, a LAN switch should receive the IP

address within one minute.



34 DN0423824

Issue 3-2


Id:0900d8058042902a


g Activation of LAN switches that belong to an EMB LAN should be done with follow-

ing rules:

• activate all the LAN switches of an EMB LAN at a time

• start the activation of EMB LAN switches with the farthest LAN switch from thesupervising unit and continue switch by switch towards the supervising unit.


a Check LAN supervision information (YFF).

Check that the IP address of the LAN switch has been configured, the configuration

file has been loaded to the switch (if automatic loading of the configuration file was

enabled), and the supervision data has been defined.

ZYFF:INQ;

You get the following kind of printout:LOADING PROGRAM VERSION 4.2-0

EXECUTION STARTED

READING LAN SWITCH SUPERVISION DATA ...

UNIT PIU TYPE IP ADDRESS MAC ADDRESS LAN UNIT

-------------------------------------------------------------------

SWU - 0 ESB20_A 10.12.18.4 E0:00:1E:80:4C:00 CNW - 0

INTERNAL LAN CONFIGURATION STATUS:

-------------------------------

IP ADDRESS CONFIGURED : OK

CONFIGURATION FILE LOADED : OK

SNMP VERSION CONFIGURED : v2

TRAP HOST CONFIGURED : OK

SUPERVISION STATUS:

-------------------------------

SUPERVISION ENABLED : ON

SUPERVISION CYCLE (SEC) : 60

SUPERVISION STATUS : REACHABLE

LAST SUPERVISION DONE : 2005-09-27 14:37:11.99

b Check LAN switch actions from the LAN hardware supervision event log

(YFL).

ZYFL:INQ:SWU,<unit index>:;

3.6 Configuring LAN switches

When all the LAN switches have been activated, make the required configuration. The

configuration files for EMB LAN switches are loaded automatically after each successful

DHCP sequence, if necessary. Only predefined configuration files are used with EMB

LAN switches. Users are not allowed to make any changes in the configuration files of EMB LAN switches. If the automatic loading of the CNW LAN switch configuration file



DN0423824

Issue 3-2

35


Id:0900d8058042902a

was disabled, you should either check that the configuration file is valid for the switch

and then transfer it to the switch, or you should configure the LAN switch via telnet.

Steps

1 Type the contents of the configuration file in the system (W6R).

ZW6R:SWU,<unit index>:;

Make sure that all the configurations are allowed for this LAN switch.


a Transfer the configuration file to the switch (YFM).

Steps

a Set the state of the switch to TE-EX (USC).

ZUSC:SWU,<unit index>:TE;

b Transfer the configuration file to the switch (YFM).

ZYFM:UCF:SWU,<unit index>;

b Configure all possible internal LAN switch default settings via telnet (W6T).

This is not done when dealing with EMB LAN switches.

Steps

a Open a telnet connection to the LAN switch.

ZW6T:SWU,<unit index>;

b Configure each LAN switch parameter (MSTP, VLANs) for its intended

purpose.

g Do not change the interface names in the configuration.

c When the configuration is ready, close the telnet connection.

g The system supports only one telnet session at a time. Use the EXIT

command to close the connection. The CTRL-C command leaves the con-

nection open and may temporarily block other telnet connections to the

switch.

3 Load the configuration file from the internal LAN switch to the system (YFM).

This is not done when dealing with an EMB LAN switch.

ZYFM:DCF:SWU,<unit index>;

!

LAN switch port configuration and VLAN configuration may block the management

connections to other LAN switches. Therefore, all LAN switch management VLAN

connections must be untagged.



36 DN0423824

Issue 3-2


Id:0900d8058042902a


The system asks you to load the configuration file every time when the LAN switch

password has been changed and the telnet connection has been closed.

gWhen the configuration file is loaded from the LAN switch to the system, the default

configuration file in the system for the switch is overwritten. Before you load the con-figuration file, make sure that the default configurations are in the running configu-

ration of this LAN switch.


ZW6R:SWU,<unit index>;

Further information

Switch types ESB14-A and ESB26 are the only types that may be used as EMB LAN

switches. In a 3rd-party L3 switch, the configuration has to be made manually in order

to make the supervision and route behind the switch work. The following configurations

must be made:

• Ports VLANs.

• A system-given IP address to the VLAN of the management port connected to an

aggregate switch.

• IP helper address to management ports to LANs behind the L3 switch.

• Traphost address. This is the IP address that has been configured to the supervising

unit’s EL0 or EL1 interface. If the SWU has an even index, the supervising unit’s EL0

interface receives the traps. If the SWU has an odd index, the supervising unit’s EL1

interface receives the traps.

Telnet login must go to the enable mode with one password. For example, in a Cisco

switch, privilege level 15 must be set.

3.7 Copying LAN switch configuration files

Internal LAN switch configuration files are saved in the system. Configuration files in

ASCII format can be copied from one functional unit (SWU) to another in order to use

them as the other unit’s configuration file. All copying is done in the system and not in

the switches. A copied file cannot be modified.

This command is meant for situations where many different switches need identical con-

figurations. If the file contains switch-specific configurations, those will be copied along

with the rest of the file and cannot be removed before the configuration file is uploaded

to the target switch.Possible overwriting of old uploaded configuration file in the system is confirmed.

g EMB LAN switch configuration files must not be copied.

Steps

1 Check the source configuration file (W6R).

To check that the configuration is correct, display the contents of the configuration file.

ZW6R:SWU,< source unit index>;



DN0423824

Issue 3-2

37


Id:0900d8058042902a

2 Copy the LAN switch’s configuration file (W6S).

ZW6S:SWU,<source unit index>:SWU,<destination unit index>;

3 Check the destination configuration file (W6R).

To check that the configuration is correct, print out the contents of the configuration file.

ZW6R:SWU,<destination unit index>;

4 Upload the configuration to the destination switch (YFM).

ZYFM:UCF:SWU,<destination unit index>;

5 Configure the rest of the LAN switch settings via telnet (W6T).

ZW6T:SWU,<destination unit index>;

6 Download the configuration file from the LAN switch to the system (YFM).

ZYFM:DCF:SWU,<destination unit index>;

Further information

The system will ask you to load the configuration file every time the LAN switch telnet

connection has been closed.



38 DN0423824

Issue 3-2


Id:0900d805803a4d69

Supervising LAN devices and connections

4 Supervising LAN devices and connectionsLAN device integration provides two kinds of LAN supervision functions:

• supervision of LAN devices (LAN switches)• network element connection supervision.

The following alarms are related to the supervision functionality:

• 2863 – UNKNOWN CONNECTION DETECTED

• 3252 – LAN DEVICE SUPERVISION FAILURE

• 3254 – LAN DEVICE GENERAL FAILURE

• 3292 – INTERNAL LAN LINK BROKEN

The alarms are described in Failure Printouts, with instructions for required recovery

actions.

g Supervision data is not available right away after the OMU unit is started.

☞ You can use the DDE command to check whether the LAN administration data col-

lection process is finished or not.

Enter the ZDDE::"ZGDC"; command to access the OMU log file. If the process is

finished, the log file will contain the following line:

ZYDMAS:ILDATA database has been filled

This means that supervision data is now available.

4.1 Starting the supervision of LAN devices and connections

The LAN switches to be supervised must be in the normal operation state. All activated

LAN switches in the LAN switch topology are supervised by default.

Steps

1 Check the supervision status of the units (YFF).

ZYFF:INQ:SWU,<unit index>;

2 Enable supervision of the units, if necessary (YFF).

If you want to enable supervision of the units, give the following command.

ZYFF:ENA:SWU,<unit index>;The command starts the supervision in activated LAN switches.

3 Set the supervision cycle of the units (YFF).

You can adjust the supervision cycle switch by switch, if you want, for example, that

some switches are supervised more frequently than others.

ZYFF:CYC:SWU,<unit index>:<cycle>;

The minimal cycle length is 30 seconds.

g The cycle length is approximate. The actual cycle may be longer than the value

given, especially with short cycle lengths.



DN0423824

Issue 3-2

39

Integrated LAN Administration Supervising LAN devices and connections

Id:0900d805803a4d69

4 Check that the data was set correctly (YFF).


4.2 Ending the supervision of LAN devices and connections

You can stop the supervision of a malfunctioning LAN switch if it causes an unreason-

able number of log writings or alarms, for example.

Steps

1 Check the supervision status of the units (YFF).


2 Disable supervision of a LAN switch (YFF).

ZYFF:DIS:SWU,<unit index>;

3 Check that the data was set correctly (YFF).


4.3 Inquiring LAN connection information

You can inquire information on LAN links. It is possible to inquire all the links that the

supervision has found to be faulty.

Steps

1 Check if there are any faulty links (YFE).

ZYFE:IFL;

If faulty links were found, you get the following kind of printout:

LOADING PROGRAM VERSION 4.2-0

READING FAULTY LINKS, MAY TAKE SEVERAL MINUTES ...

SOURCE SOURCE SRC DESTINATION DESTINATION DST FAULTUNIT PLUG-IN UNIT IF UNIT PLUG-IN UNIT IF TYPE

-----------------------------------------------------------------------------

SWU-0 ESB20_A-0 1107 - MCMU-0 CP710_A-0 0 FAULTY

SWU-1 ESB20_A-0 1105 - BCSU-1 CP710_A-0 1 NO IP

COMMAND EXECUTED

The printout shows that the link between SWU-0 and MCMU-0 is faulty. This fault gen-

erates an alarm.



40 DN0423824

Issue 3-2


Id:0900d805803a4d69

Supervising LAN devices and connections

2 Check the alarm printouts (AHO).

If faulty links were found, print out all alarms generated for the SWU unit(s) on the

current day.ZAHO:SWU,<unit index>::;

3 Check the recovery instructions.

For recovery instructions, see the alarm description(s) in Failure Printouts and Distur-

bance Printouts.

4.4 Handling LAN hardware supervision logs

A LAN hardware supervision log entry is written in the following situations:

• When an error occurs (for example a failure in the DHCP sequence of a LAN switch).• When the software or the sysloader is updated in the switches.

• When switches are activated in the LAN topology (with the W6E command).

• When switches are deactivated or made passive in the LAN topology (with the W6E

command).

• When SNMP SET operations are performed.

• When SNMP traps are received.

• When switches receive an IP address.

• When an IP address is removed from a switch.

• When a new topology is activated.

• When the configuration file of a LAN switch has been downloaded or uploaded.

Some of the event log writings are simply notifications of actions performed on the LAN

switches. They may indicate, for example, that the software has been updated in a LAN

switch or that an SNMP SET command for a LAN switch has been executed. These

events do not require user action. However, log writings recording, for example, that an

internal LAN switch does not respond to an SNMP GET request, are indications of faults

in the LAN. The LAN switch and its cables should be checked, and changed if neces-

sary.

You can handle LAN hardware supervision log information with the commands of the YF

command group.

Every log item has fields for unit, event class (trap information or notification), date, time,

and description of the event.

Steps


a Inquire events recorded in the LAN hardware supervision log (YFL).

ZYFL:INQ::[<unit type> | ALL def,[<unit index..1-2 | ALL def]:

[ TRA | NOT | ALL def ]:[<date> | <today> def],

[<time | <00-00-00> def];

For example: Inquire TRAP events of all units, recorded since 7:00 a.m. of

November 15, 2004.



DN0423824

Issue 3-2

41

Integrated LAN Administration Supervising LAN devices and connections

Id:0900d805803a4d69

ZYFL:INQ::TRA:2004-11-15:07-00-00;

b Clear the LAN hardware supervision log (YFL).

ZYFL:CLR;

c Update the size of the LAN hardware supervision log (YFL).

ZYFL:UPD,<size>;



42 DN0423824

Issue 3-2


Id:0900d805805490eb

Maintaining LANs

5 Maintaining LANs

5.1 Updating the password of a LAN switchPurpose

The system needs to be able to recognise the LAN switch passwords so that the

switches can be accessed through a telnet connection. Operations like the downloading

or uploading of the configuration file, software updates, and password updates to the

LAN switch are also done through a telnet connection. This is why the system must have

up-to-date information about the LAN switch passwords.

A LAN switch password cannot be changed unless it has first been stored in the system.

When a password is changed only in the switch, the new password must be updated in

the system again.

A password may also be lost, for example, when the LAN topology is changed and thesame switching unit is not found in the new topology.

g Passwords to LAN switches are case sensitive.

No configuration changes are allowed when the network element is split into the

TELE/TRIAL configuration.

Steps


a Update the current LAN switch password in the system (W6M).

ZW6M:SWU,<unit index>:FCD;

GIVE PASSWORD: ********

GIVE PASSWORD AGAIN: ********

b Change the LAN switch password and update it in the system (W6M).

g Before this operation can be executed, the system must know the current LAN

switch password.

ZW6M:SWU,<unit index>:;

GIVE PASSWORD: ********

GIVE PASSWORD AGAIN: ********

g Do not create a username for this password in the LAN switch configuration!

!

The system does not support the enable-level password. If this password is used, the

system is not able to access the LAN switch properly.



DN0423824

Issue 3-2

43

Integrated LAN Administration Maintaining LANs

Id:0900d805805490eb

5.2 Configuring a LAN switch of the communication network

(CNW)

PurposeThe configuration of a LAN switch must be changed when the default settings are not

adequate or, in some cases, when the LAN topology is changed. Changes in the con-

figuration may also be necessary after a software package update in the LAN switch.

Only predefined configuration files are used with EMB LAN switches. Users are not

allowed to make any changes to configuration files of EMB LAN switches. The configu-

ration file of an EMB LAN switch cannot be loaded from the switch to the system. For

more information, see Updating the software package of a LAN switch.

Steps

1 Load the default configuration to the LAN switch (YFM).ZYFM:UCF:SWU,<unit index>;

2 Type the content of the configuration file in the system (W6R).


3 Open a telnet connection to the LAN switch (W6T).


4 Configure the LAN switch.

g Do not change the interface names in the configuration!

5 Close the telnet connection (EXIT).

g The system supports only one telnet session at a time. Use the EXIT command to

close the connection. If the CTRL-C command is given instead of the EXIT

command, the connection will remain open until it times out. This will take several

minutes and other connections to the switch may be blocked during this time.

6 Load the configuration file from the LAN switch to the system (YFM).ZYFM:DCF:SWU,<unit index>;

The system asks you to load the configuration file every time when the LAN switch

password has been changed and the telnet connection has been closed.

7 Type the content of the configuration file in the system (W6R).




44 DN0423824

Issue 3-2


Id:0900d805805490eb

Maintaining LANs

5.3 Updating the software package of a LAN switch

Purpose

The system does not support automatic loading of software to the LAN switches. In prac-tice, this means that the software of a LAN switch is not loaded from the system to the

switch when the software build of the network element is reloaded (for example, when

a Change Delivery is brought to the build). You need to make sure that the version of

the software running in the LAN switch is the version mentioned in the Software Delivery

documentation. If the software in the LAN switch is older than the software in the build,

update the new software to the switch.

g The LAN switch needs to be reset manually after the software update in order to

take the updated software into use.

It is possible to update the software in several switches and then reset all of them at the

same time instead of resetting after each individual update.

Before you start

Read the Software Delivery documentation for any notes or special conditions on the

software update procedure. Make sure that the current configuration file is compatible

with the new software. For details on the compatibility issues, see the Software Delivery

documentation.

1. Check the software version of the LAN switch (YFM).

ZYFM:ISW:SWU,<unit index>;

2. Compare the software version of the LAN switch to the version in the build.

For the current version of the software, see the Software Delivery documentation.

If the system notices an old software version, it sets the alarm LAN DEVICE

GENERAL FAILURE with cause 09 (Too old software version in LAN device).3. If the software version in the LAN switch is older than the software version in the

build, update the software of the LAN switch according to the following instructions.

Steps

1 Check the state of the LAN switch (USI).

ZUSI:SWU,<unit index>;

2 Set the state of the switch to SE-OU (USC).

When updating the software package of an EMB LAN switch, the working state of theEMB unit, not that of the single SWU unit, should be changed to SE-OU. That way, the

states of all switches of the EMB LAN are changed to SE-OU.

ZUSC:<EMB or SWU>,<unit index>:TE;

ZUSC:<EMB or SWU>,<unit index>:SE;

3 Load the configuration file from the communication network LAN switch of the

communication network (CNW) to the system (YFM).





DN0423824

Issue 3-2

45


Id:0900d805805490eb

4 Update the software package to the LAN switch (YFM).

Steps

a Update the sysloader.

If the Software Delivery documentation states that a new version of the sysloader is

needed, update the sysloader before updating the software package.

ZYFM:USL:SWU,<unit index>;

b Update the software package.

ZYFM:USW:SWU,<unit index>;

5 Repeat steps 1 to 4 for all other switches whose software needs to be updated.

6 Reset the switches whose software has been updated.

• To reset an EMB LAN switch:

ZYFM:RES:SWU,<unit index>;

• To reset a CNW LAN switch:

Open a telnet connection to the switch and give the appropriate reset command. For

more information, including on which reset type is needed, see the

Software Delivery documentation.



8 Load the configuration to the LAN switch (YFM).


g If the Software Delivery documentation suggests that there may be compatibility

problems with the new software version and the old configuration file, follow the con-

figuration upload instructions provided in the Software Delivery documentation.

9 Check the current software version in the switches (YFM).

ZYFM:ISW:SWU,<unit index>;

10 Check the configuration of the LAN switch (W6T).


Remember that you cannot establish a Telnet connection to an EMB LAN switch.


ESB26>enable

ESB26#sho running-config



46 DN0423824

Issue 3-2


Id:0900d805805490eb

Maintaining LANs

11 Change the working state of the LAN switch to WO-EX (USC).

ZUSC:<EMB or SWU>,<unit index> :TE;

ZUSC:<EMB or SWU>,<unit index> :WO;

5.4 Removing a LAN switch

Purpose

The following instructions show how to remove a LAN switch completely from the

system configuration.

For instructions on how to handle confidential information during LAN maintenance

tasks, see section Removing confidential information from a LAN switch.

Steps

1 Set the state of the switch to SE-NH (USC).

When removing a LAN switch of the EMB LAN, the working state of the EMB unit, not

that of the single SWU unit, should be changed to TE-EX. That way, the working states

of all switches of the EMB LAN are changed to TE-EX. After removing the LAN switch

(step 6 below), change the state of the EMB unit back to WO-EX if there are any

switches left. If you are changing the working state of a LAN switch that no longer has a

backup LAN switch, give the ZUSC command with the forced parameter (FCD).


ZUSC:SWU,<unit index>:SE;


When the state of the unit is set to TE, the LAN supervision system directs the traffic to

the spare unit.

2 Deactivate the switch in the topology (W6E).

ZW6E:SWU,<unit index>:P;

When the switch is set to the inactive state, the system stops supervising it.

3 Remove the switch from the LAN (WYD).

ZWYD:<lan id>:SWU,<unit index>:;

This command also releases IP address of the switch.

4 Delete the plug-in unit description from the equipment database (WTQ).

ZWTQ:<unit type>,<unit index>:<piu type>,<piu index>;

5 Remove the plug-in unit of the switching unit.

Remove the plug-in unit used for the switching unit from the cartridge.



DN0423824

Issue 3-2

47


Id:0900d805805490eb

5.5 Adding a LAN switch

Purpose

New LAN switches need to be added to the system when the network element hardwareis upgraded and the upgrade includes new LAN switches.

If the new switches do not belong to any topology and need to be added to the topology,

see Changing and expanding the LAN topology.

Steps

1 Install a plug-in unit for the switching unit in the cartridge.

2 Create the functional unit description in the equipment database (WTU).


3 Create the plug-in unit description in the equipment database (WTP).

ZWTP:<unit type>,<unit index>:<piu type>,<piu index>,<track>::;

If the Hardware Inventory feature has been activated in the network element, you can

add the serial number and the product code of an already equipped plug-in unit to the

equipment database. See Replacing a switch with one of the same type.

4 Add the switch to the LAN (WYC).

ZWYC:S:<lan id>:SWU,<unit index>:CMM,<unit index>:<IP address>;

g Only internal LAN switches may be added to the CNW LAN, and only EMB LAN

switches may be added to the EMB LAN.

5 Set the state of the switching unit to WO-EX (USC).



ZUSC:SWU,<unit index>:WO;

The switch is now in use.

6 Make sure that the DHCP client is active in the switch.

Configure the management VLAN to the management ports of the switch. The default

VLAN (VID=1) should work without configuring.

7 Activate the switch (W6E).


8 Set the state of the switching unit to TE-EX (USC).




48 DN0423824

Issue 3-2


Id:0900d805805490eb

Maintaining LANs

9 Load the configuration to the switch (YFM).

Steps

a Load the configuration file to the new switch.

Use the following command only when adding a LAN switch of communication

network (CNW).


b Check the settings (W6T).

Establish a telnet connection to the LAN switch in order to check the settings. To

save the settings, write the configuration to the startup configuration.

ZW6T:SWU,<index>;

device-name>enabledevice-name#show running-config

device-name#write memory

10 Download the configuration file from the LAN switch to the system.

When you are closing the Telnet connection, answer Y to the question DO YOU WANT

TO DOWNLOAD CONFIGURATION FILE FROM LAN SWITCH or enter the

ZYFM:DCF:SWU,<unit index>; command.



12 Check the LAN switch supervision data (YFF).


5.6 Replacing a LAN switch

Purpose

If a LAN switch is malfunctioning, it must be replaced with a new one. If more LAN ports

are needed, it may also be necessary to replace a LAN switch with a switch of a differenttype.

For instructions on how to handle confidential information during LAN maintenance

tasks, see section Removing confidential information from a LAN switch.

5.6.1 Replacing a switch with one of a different type

Steps

1 Check the configuration of the switch (W6R).




DN0423824

Issue 3-2

49


Id:0900d805805490eb

2 Set the state of the switch to SE-NH (USC).





the spare unit.

3 Deactivate the switch in the topology (W6E).

ZW6E:SWU,<unit index>:P;

When the switch is set to the passive state, the system stops supervising it.

4 Remove the switch from the LAN (WYD).

ZWYD:<lan id>:SWU,<unit index>:;

5 Delete the plug-in unit description from the equipment database (WTQ).

ZWTQ:<unit type>,<unit index>:<piu type>,<piu index>;

6 Remove the plug-in unit of the switching unit.

Remove the plug-in unit used for the switching unit from the cartridge.

7 Install a new plug-in unit for the switching unit in the cartridge.

8 Create the plug-in unit description in the equipment database (WTP).

ZWTP:<unit type>,<unit index>:<piu type>,<piu index>,<track>::;



equipment database. See Replacing a switch with one of the same type.

9 Reload the current LAN topology (W6G).

ZW6G:R;

10 Add the switch to the LAN (WYC).

ZWYC:S:<lan id>:SWU,<unit index>:CMM,<unit index>:<IP address>;





The switch is now in use.



50 DN0423824

Issue 3-2


Id:0900d805805490eb

Maintaining LANs

12 Make sure that the DHCP client is active in the switch.

Make sure that the DHCP client is active in the switch and configure the management

VLAN to the management ports of the switch. The default VLAN (VID=1) should workwithout configuring.

13 Activate the switch (W6E).


The activation may take approximately one minute. See Activating LAN switches.

14 Set the state of the switch to TE-EX (USC).



Use the following command only when replacing a LAN switch of communication

network (CNW).


16 Configure the LAN switch of communication network (CNW) in the same way as

the previous switch was configured.

To save the configuration, write it to the startup configuration.

device-name>enable

device-name#show running-config

device-name#write memory


17 Store the configuration file of the LAN switch of communication network (CNW)

to the system (YFM).



18 Set the state of the switch to WO-EX (USC).


19 Check the configuration (W6R).



20 Check the LAN switch supervision data (YFF).




DN0423824

Issue 3-2

51


Id:0900d805805490eb

5.6.2 Replacing a switch with one of the same type

Steps

1 Store the configuration file of the switch to the disk (YFM).


network (CNW).



2 Set the state of the switching unit to SE-OU (USC).

When replacing an EMB LAN switch, the working state of the EMB unit, not that of the

single SWU unit, should be changed to SE-OU. That way, the working states of all

switches of the EMB LAN are changed to SE-OU.




the spare unit.

3 Replace the plug-in unit of the switching unit.

Remove the plug-in unit used for the switching unit from the cartridge and install a new

one in its place.

4 Add plug-in unit identification data to the equipment database (WOI, WTY).



equipment database.

The Hardware Inventory feature provides network-element-specific hardware configura-

tion data for the network management system (NMS). The hardware configuration infor-

mation contains the hardware component identification data (item identifier and serial

number) of individual hardware components. You can use this information to find out

what hardware components are in use in the system, and where the components are

located in the different network elements (for example, in which cartridge a plug-in unit

has been equipped in the cabinet).

The Hardware Inventory feature is available only when the value of the PRFILE param-

eter HW_INVENTORY_IN_USE (class 2, parameter 0790) is TRUE. To check the param-

eter value, give the ZWOI:2,790; command.

To add plug-in unit identification data to the equipment database, give the following

command:

ZWTY:MODIFY,P:<component coordinates>:SEN=<serial

number>,ITI=<item identifier>;

Example:

Add the identification data (serial number 3G003006754, item identifier C09761.....D3A)for the plug-in unit in cartridge location 1A2-0. The slot number of the plug-in unit is 3.



52 DN0423824

Issue 3-2


Id:0900d805805490eb

Maintaining LANs

ZWTY:MODIFY,P:1A2-0-3:SEN=3G003006754,ITI=C09761.....D3A;

5 Update the software if it is older than the software in the system (YFM).

If the software in the plug-in unit is older than the software in the system, it needs to be

updated with the following command:

ZYFM:USW:SWU,<unit index>;

After the update, the switch is restarted automatically.



network (CNW).

Load the configuration file of the removed switch to the new switch.


7 Set the state of the switch to WO-EX (USC).

When replacing an EMB LAN switch, the working state of the EMB unit, not that of the

single SWU unit, should be changed to WO-EX. That way, the working states of all

switches of the EMB LAN are changed to WO-EX at once.



8 Check the LAN switch supervision data (YFF).ZYFF:INQ:SWU,<unit index>;

5.7 Removing confidential information from a LAN switch

Purpose

If a LAN switch needs servicing, you need to back up the switch configuration before you

remove the switch from the network element and send it to the service point. You also

need to ensure that confidential information is removed from the switch because the

configuration file of an Ethernet switch contains several pieces of confidential informa-

tion:

• information on the management IP network

• IP address of the SNMP trap host

• name and revision of the MST region

• VLAN identifiers

• information on the directly connected IP subnets

• static routes

• default gateway

• logical names of switch ports

• logical names of VLANs

• edge ports

• trunk links



DN0423824

Issue 3-2

53


Id:0900d805805490eb

• Quality of Service parameters

• configuration information on the RADIUS client

• information on the management interfaces

• configuration information on the SNMP• configuration information on OSPF

Furthermore, ESB-type Ethernet switches also have a script file system that may

contain confidential information. For instructions on how to handle the script file system,

follow the instructions below.

1. ESB26#configure terminal

2. ESB26(config)#script-file-system

3. ESB26(config script-file-system)# <?>

5.7.1 Removing confidential information from a LAN switch

Purpose

Steps

1 Check the contents of the configuration file.

ESB26#show running-config

2 Back up the configuration file. (YFM)

ZYFM:DCF:SWU,<index>;

3 Check the contents of your script file system.

For instructions, see File System for Configuration Script Files in ESB User Guide.

4 Back up the script files to a TFTP server outside the network element.


5 Remove the sensitive information from the script file system.


6 Clear the configuration by rebooting the switch to factory defaults.

☞ Rebooting the switch to factory defaults means that the VLAN and STP/MSTP con-

figurations will also be initialized. To avoid possible L2 loops, it is highly recom-

mended that you cut possible cabling loops between switch and site L2/L3 multi-

layer switches. Redundant backup links should be administratively disabled from the

site on which L2/L3 device(s) are connected to the ESB that will be rebooted to

factory defaults.

ESB26#reload to-defaults

ESB26#copy running-config startup-config



54 DN0423824

Issue 3-2


Id:0900d805805490eb

Maintaining LANs

5.8 Diagnosis of LAN or LAN switch

Purpose

You may start a total or partial diagnosis for Internal LAN or for a single LAN switch. Therecovery system may start a total diagnosis job for the EMB LAN automatically if it has

received an alarm that suggests a problem in the EMB unit. The recovery system does

not start automatic diagnosis jobs for the communication network (CNW) or for a single

LAN switch (SWU). You can inquire ongoing diagnosis jobs. After a diagnosis has been

completed, you can display the diagnostic report history on the screen or send it to the

printer.

g You can start a diagnosis of the CNW LAN or of a switch when the units are in

working state WO-EX or TE-EX. The diagnosis does not re-start the LAN switch. A

diagnosis of the EMB LAN is allowed only if the state of the EMB unit is TE-EX.

Steps

1 Start a diagnosis of internal LAN or of a LAN switch (UDU).

ZUDU:<unit type>,<unit index>;

2 List ongoing and queued diagnosis jobs (UDQ).

ZUDQ;

3 Display the results of the diagnostics (UDH).

ZUDH;Further information

For detailed instructions, see Diagnostics Handling .

5.9 LAN statistics

LAN statistics provide data about the load and availability of the LAN in the exchange.

The measurements provided by LAN statistics can help in planning the LAN configura-

tion. They can also be used for a wide variety of tasks related to the operation of the

exchange, such as

• checking that the LAN is configured so that the messaging load is distributed evenlybetween the switches and functional units in the LAN, and which (if any) parts of the

LAN are overloaded

• determining whether any unplanned restarts of switches have occurred, and if so,

how many

• investigating what kinds of errors have occurred in the LAN.

In a LAN, system performance depends mainly on the distribution of the overall messag-

ing load between switches and host units. In order to avoid bottlenecks, the configura-

tion of a LAN should be planned so that those host computers that communicate the

most with each other are connected to the same cabinet-level switch. An overloaded

cabinet-level switch will cause problems, such as rejected messages, and the LAN con-

figuration must then be rearranged. The information provided by LAN statistics helps in



DN0423824

Issue 3-2

55


Id:0900d805805490eb

localising the most heavily loaded switches and in determining load imbalances

between switches.

LAN statistics are especially useful for monitoring the load of the EMB.

A large number of measurements is available for monitoring the LAN in the exchange.

Which LAN statistics services are needed depends on the needs of the operator and the

exchange involved. There are no common rules that can be applied to all operators;

instead, operators can select and define those measurements that they want to use in

the exchange.

There are three different types of measurements:

• Traffic measurements

• Error measurements

• Availability measurements

Each measurement report contains data about pertinent counters (performance indica-

tors). These counters are identified by unique tags. For details about available counters,see the application-specific Counters documentation.

Reports are created as ASCII files. If the feature XML File Format for Statistics is acti-

vated, the reports are available in XML format as well.

5.9.1 LAN statistics reports

A LAN statistics report is written as soon as a measurement stops (either by itself or

through user interaction).

The following measured objects may appear in the reports:

The logical file of a LAN statistics measurement contains the following information:

• exchange type and name

• measurement type

• interval time and date.

Example: First lines of a LAN statistics measurement printout

BSC3i RUOKE 2006-07-04 09:15:09

LAN HOST UNIT TRAFFIC MEASUREMENT REPORT

OUTPUT INTERVAL: 15 MIN SAMPLE DATE: 2006-07-04 09:15:07

In this example, the measurement is taken in a network element of type BSC3i. The

network element name is Ruoke.

LAN statistics measurements on an interface of a LAN element (SWU) are only possibleif the following conditions are met:

Measurement type Measured object

LAN switch traffic measurement (288/120H) Switch

LAN host unit traffic measurement (289/121H) Host unit

LAN switch availability measurement (290/122H) Switch

LAN switch error measurement (291/123H) Switch

LAN host unit error measurement (292/124H) Host unit

Table 2 Measured objects in reports



56 DN0423824

Issue 3-2


Id:0900d805805490eb

Maintaining LANs

• The LAN interface must be connected; that is, its operating state must be up.

• The LAN element must be active in the topology.

• No topology changes should be made in the LAN during the measurement period.

If one of these conditions is not met, the measurement will fail and the next report thatis written will be incomplete.

g Measurements should be taken in a stable environment in order to yield reliable


changes are made.

Steps

1 If a LAN statistics measurement has failed or if a LAN statistics measurement

report indicates a problem in the LAN, see LAN statistics troubleshooting.

5.9.2 Measurement handling

Statistical measurements and statistical object lists are handled with the commands of

the T2 command group.

Use T2C to create, T2H to modify, and T2D to delete object lists used for statistical mea-

surements.

Use T2S to start statistical measurements. This command is also used to define the

measurement schedule.

Use T2I to interrogate the parameters of a measurement.

Use T2E to stop an active statistical measurement, and T2M to modify the definitions of

a measurement schedule.

For more information on the commands, see T2 – Measurement Handling .

For details on the use of these commands for specific measurements as well as usage

examples, see Traffic measurement, Availability measurement, and Error measure-

ment.

Steps

1 Create a measurement (T2C).

Use the T2C command to create a measurement:

T2C: MID = <measurement id>:OID = <object list identifier>:

[OLN = <object list name>]:

[[ID1 = <object identifier 1> |

ID2 = <object identifier 2> |


ID4 = <object identifier 4> ]]:...;

The object identifier parameters specify the unit type and index as well as the

plug-in unit type and index of the interface or interfaces on which the measurement will

be performed.



DN0423824

Issue 3-2

57


Id:0900d805805490eb

2 Start an already created measurement (T2S).

Use the T2S command to start a measurement that has already been created:

T2S: NAME = <measurement name>:OID = <object list identifier>:

[ [RAP = <result accumulation period> | 15 def] |

[SD = <start date> | <current date> def] |

[ST = <start time> | <current time> def] |

[ED = <end date> | <no stop date> def] |

[ET = <end time> | <no stop time> def] |

[ROP = <result output period> | <round the clock> def] |

[OD = <output delay> | 0 def] ]...];

3 Interrogate the parameters of the measurement (T2I).

Use the T2I command to interrogate the parameters of measurements. The parameters

of any created measurement can be interrogated, no matter whether the measurement

is active or not.

T2I: NAME = <measurement name>:

OID = <object list identifier>:

[ICH = <interrogate choice> | S def | O | B ];

4 Stop a running measurement (T2E).

Use the T2E command to stop a measurement while it is still running:

T2E: NAME = <measurement name>:OID = <object list identifier>:

[ [ED = <end date> | <current date> def] |

[ET = <end time> | <current time> def]...];

Further information

For the Short Time LAN Measurement, the YFT command is used instead. For more

information, see YF – LAN HW Supervision Handling and Short time measurement.

5.9.3 Traffic measurement

5.9.3.1 LAN Switch Traffic Measurement reports (288/120H)

The LAN Switch Traffic Measurement provides information on transmitted and received

data traffic for the switch. This includes the amounts, sizes, and average and peak load

rates for the data packages transmitted and received during the accumulation period.

The counter values for this measurement are collected from those LAN elements that

belong to the object group that is defined when the measurement is created.

Use the commands of the T2 command group to create, start, or stop LAN Switch Traffic

Measurement and to modify its parameters.

The objects measured in this report are the switch and its interface (defined by the

object identifier parameters, which specify the unit type of the switches, and the

index as well as the interface or interfaces to be measured).



58 DN0423824

Issue 3-2


Id:0900d805805490eb

Maintaining LANs

Counters are available for

• transmitted and received packets

• transmitted and received octets

• transmitted and received broadcast and multicast packets• transmitted and received packets according to package size:

• up to 64 octets

• 65–127 octets

• 128–255 octets

• 256–511 octets

• 512–1023 octets

• 1024–1518 octets

• average and peak load rates of transmitted and received traffic.

For details, see the application-specific Counters documentation.

Average and peak load rates (in percent) are calculated with the following formula:

where

• Δ octets is the number of octets transmitted or received during the accumulation

period

• Δ packets is the number of packets transmitted or received during the accumulation

period

• interval period is the accumulation time in seconds

• link speed is the bandwidth of the Ethernet interface in kilobits per second.

The value 16 in the formula is actually the sum of two constants, namely 9.6 (the inter-

packet gap time in microseconds) and 6.4 (the start frame delimiter time in microsec-

onds).

The output is stored in the following logical files:

LANTRASWIA ASCII report

LANTRASWIX XML report (Nokia NetAct usage)

Each report begins with a heading that states the type of the exchange in question (for

example, DX MSCi ), followed by the name of the exchange and the report output date

and time. The next lines contain the reporting data, that is, the standard identifier of the

report type (in this case, LAN switch traffic measurement report ), the output interval(between 15 and 60 minutes), and the sample date (the date and time at which the accu-

mulation period of the report ends). After this, the LAN Switch Traffic Measurement

specific identifier and measurement data are given.

Example: Example LAN Switch Traffic Measurement report

In a LAN Switch Traffic Measurement report, the information on total or transmitted data

concerns total (transmitted and received) data if the fields concerning received data are

empty. If the fields concerning received data contain numbers, the information on total

or transmitted data concerns only transmitted data.

BSC3i ELVIS 2006-09-15 11:41:12

LAN SWITCH TRAFFIC MEASUREMENT REPORT

interval period * link speed

octets * 0.8) + (( packets * 16)



DN0423824

Issue 3-2

59


Id:0900d805805490eb


UNIT PIU PIU

TYPE INDEX

SWU-0 ESB26 0

INTERFACE INFO

INT. CONN TYPE CONN UNIT CONN INDEX STATUS

1/1/3 MGMT_DOWNLINK SWU 2 UP

1/1/9 DOWNLINK MCMU 0 UP

1/1/10 DOWNLINK MCMU 1 UP

1/1/11 DOWNLINK OMU 0 UP

TRANSMITTED INTERFACE INFO

INT. TRANSMITTED TRANSMITTED BROADCAST MULTICASTPKTS OCTETS PKTS (T/TR) PKTS (T/TR)

1/1/3 146138 175671377 1 0

1/1/9 72793 100508895 697 0

1/1/10 0 0 0 0

1/1/11 698 171416 698 0

RECEIVED INTERFACE INFO

INT. RECEIVED RECEIVED BROADCAST MULTICAST

PKTS OCTETS PKTS (R) PKTS (R)

1/1/3 146138 175457042 - -

1/1/9 72098 100339494 1 01/1/10 0 0 0 0

1/1/11 0 0 0 0

PACKET SIZE INFO (TOTAL OR TRANSMITTED)

INT. <64 65<127 128<255 256<511 512<1023 1024<1518

PKTS PKTS PKTS PKTS PKTS PKTS

1/1/3 44771 426 14 27 206 248062

1/1/9 284 815 14 12 206 71462

1/1/10 0 0 0 0 0 0

1/1/11 284 178 14 12 206 4

PACKET SIZE INFO (RECEIVED)INT. <64 65<127 128<255 256<511 512<1023 1024<1518


1/1/3 - - - - - -

1/1/9 1 637 0 0 0 71460

1/1/10 0 0 0 0 0 0

1/1/11 0 0 0 0 0 0

TRANSMITTED RECEIVED

INT. AVERAGE PEAK AVERAGE PEAK

LOAD% LOAD% LOAD% LOAD%

1/1/3 1 % 1 % 1 % 1 %1/1/9 0 % 0 % 0 % 0 %



60 DN0423824

Issue 3-2


Id:0900d805805490eb

Maintaining LANs

1/1/10 0 % 0 % 0 % 0 %

1/1/11 0 % 0 % 0 % 0 %

END OF REPORT

Steps

1 Create a LAN Switch Traffic measurement (T2C).

Use the T2C command to create a LAN Switch Traffic measurement:

T2C: MID = <measurement id>:







The object identifier parameters specify the unit type of the switch, and the index

as well as the interface or interfaces to be measured.

2 Start the measurement you created (T2S).

Use the T2S command to start a LAN Switch Traffic measurement that has already been

created:T2S: NAME = <measurement name>:









3 If necessary, interrogate the parameters of the measurement (T2I).

Use the T2I command to interrogate the parameters of a LAN Switch Traffic measure-

ment:




4 If necessary, stop the measurement while it is still running (T2E).

Use the T2E command to stop a running LAN Switch Traffic measurement:

T2E: NAME = <measurement name>:




DN0423824

Issue 3-2

61


Id:0900d805805490eb



LAN Switch Traffic measurement handling examples

Example: Creating a LAN Switch Traffic measurement

To create a LAN Switch Traffic measurement with measurement identifier 120 , object

list identifier 001, object list name TRAFFIC MEASUREMENT 1, and measurement LAN

interfaces SWU-0 1/1/3, SWU-0 1/1/9, SWU-0 1/1/10 , and SWU-0 1/1/11, enter the fol-

lowing command:

T2C:MID=120:OID=001:OLN=TRAFFIC MEASUREMENT

1:ID1=SWU,ID2=0,ID3=1/1/3&1/1/9&1/1/10&1/1/11,;

Example: Starting a LAN Switch Traffic measurement

To start the LAN Switch Traffic measurement created in example 6 above, enter the fol-

lowing command:T2S:NAME=PMEAS120:OID=001:ST=15-30-00,ET=18-00-00;

In this example, the starting time is 15:30:00 and the stopping time is 18:00:00 . For the

measurement accumulation period, the default value (15 minutes) is used.

Example: Interrogating the parameters of a LAN Switch Traffic measurement

To interrogate the parameters of the LAN Switch Traffic measurement created in

example 6 above, enter the following command:

T2I:NAME=AMEAS120:OID=001:ICH=B;

In this example, the measurement is still active.

The output contains information about the measurement schedule as well as the mea-surement LAN interfaces and parameters.

EXECUTION STARTED

BSC3i ELVIS 2006-09-08 15:22:21

MEASUREMENT SCHEDULE:

NAME: AMEAS120

OBJECT LIST ID: 001OBJECT LIST NAME: TRAFFIC MEASUREMENT 1

TYPE: LAN SWITCH TRAFFIC MEASUREMENT

STATE: ACTIVE

RESULT ACC. PERIOD: 15

START TIME: 08.09.2006 15:30:00

STOP TIME: 08.09.2006 18:00:00

RESULT OUT. PERIOD: 00:00-24:00

OUTPUT DELAY: 0

MEASURED LAN INTERFACES:



62 DN0423824

Issue 3-2


Id:0900d805805490eb

Maintaining LANs

UNIT TYPE UNIT INDEX INTERFACE

SWU 0 1/1/3

SWU 0 1/1/9

SWU 0 1/1/10

SWU 0 1/1/11

PARAMETERS:

0 CONN_TYPE

1 CONN_UNIT

2 CONN_INDEX

3 INTERFACE_STATUS

4 TR_PKTS

5 TR_OCTETS6 TR_BROADC_PKTS

7 TR_MULTI_PKTS

8 REC_PKTS

9 REC_OCTETS

10 REC_BROADC_PKTS

11 REC_MULTI_PKTS

12 TR_PKTS_64

13 TR_PKTS_65_127

14 TR_PKTS_128_255

15 TR_PKTS_256_511

16 TR_PKTS_512_102317 TR_PKTS_1024_1518

18 REC_PKTS_64

19 REC_PKTS_65_127

20 REC_PKTS_128_255

21 REC_PKTS_256_511

22 REC_PKTS_512_1023

23 REC_PKTS_1024_1518

24 TR_AVG_UTIL

25 TR_PEAK_UTIL

26 REC_AVG_UTIL

27 REC_PEAK_UTIL

COMMAND EXECUTED

Example: Stopping a running LAN Switch Traffic measurement

To stop the LAN Switch Traffic measurement created in example 6 above, enter the fol-

lowing command:

T2E:NAME=AMEAS120:OID=001:;

In this example, no explicit stopping time is given and therefore the measurement will be

stopped immediately.



DN0423824

Issue 3-2

63


Id:0900d805805490eb

5.9.3.2 LAN Host Unit Traffic Measurement report (289/121H)

The LAN Host Unit Traffic Measurement provides information on transmitted and

received data traffic for the host unit. This includes the amounts, sizes, and average and

peak load rates for the data packages transmitted and received during the accumulationperiod. The counter values for this measurement are collected from those LAN elements

that belong to the object group that is defined when the measurement is created.

Use the commands of the T2 command group to create, start, or stop LAN Host Unit

Traffic Measurement and to modify its parameters.

The objects measured in this report are the plug-in units and their interfaces (defined by

the object identifier parameters, which specify the unit type and index and the

type of the plug-in unit and index).


• transmitted and received packets

• transmitted and received octets• transmitted and received broadcast and multicast packets

• transmitted and received packets according to package size:

• up to 64 octets

• 65–127 octets

• 128–255 octets

• 256–511 octets

• 512–1023 octets

• 1024–1518 octets

• average and peak load rates of transmitted and received traffic.

For details, see the application-specific Counters documentation. Average and peak load rates (in percent) are calculated with the following formula:

where

• Δ octets is the number of octets transmitted or received during the accumulation

period

• Δ packets is the number of packets transmitted or received during the accumulation

period

• interval period is the accumulation time in seconds

• link speed is the bandwidth of the Ethernet interface in kilobits per second.

The value 16 in the formula is actually the sum of two constants, namely 9.6 (the inter-

packet gap time in microseconds) and 6.4 (the start frame delimiter time in microsec-

onds).


LANTRAHOSA ASCII report

LANTRAHOSX XML report (Nokia NetAct usage)


example, DX MSCi ), followed by the name of the exchange and the report output date

and time. The next lines contain the reporting data, that is, the standard identifier of thereport type (in this case, LAN host unit traffic measurement report ), the output interval

interval period * link speed

octets * 0.8) + (( packets * 16)



64 DN0423824

Issue 3-2


Id:0900d805805490eb

Maintaining LANs

(between 15 and 60 minutes), and the sample date (the date and time at which the accu-

mulation period of the report ends). After this, the LAN Host Unit Traffic Measurement


Example: Example LAN Host Unit Traffic Measurement report

In a LAN Host Unit Traffic Measurement report, the information on total or transmitted

data concerns total (transmitted and received) data if the fields concerning received data

are empty. If the fields concerning received data contain numbers, the information on

total or transmitted data concerns only transmitted data.

BSC3i ELVIS 2006-09-15 12:29:43

LAN HOST UNIT TRAFFIC MEASUREMENT REPORT


UNIT PIU PIUTYPE INDEX

OMU CP816_A 0

INTERFACE INFO

INT. CONN TYPE CONN UNIT CONN INDEX STATUS

EL0 UPLINK SWU 0 UP

TRANSMITTED INTERFACE INFO

INT. TRANSMITTED TRANSMITTED BROADCAST MULTICAST

PKTS OCTETS PKTS (T/TR) PKTS (T/TR)

EL0 107059 148622146 2 0

RECEIVED INTERFACE INFO

INT. RECEIVED RECEIVED BROADCAST MULTICAST

PKTS OCTETS PKTS (R) PKTS (R)

EL0 107564 150027734 639 0

PACKET SIZE INFO (TOTAL OR TRANSMITTED)

INT. <64 65<127 128<255 256<511 512<1023 1024<1518


EL0 4 1209 0 0 0 105846

PACKET SIZE INFO (RECEIVED)

INT. <64 65<127 128<255 256<511 512<1023 1024<1518


EL0 281 298 12 12 295 106666

TRANSMITTED RECEIVED

INT. AVERAGE PEAK AVERAGE PEAK

LOAD% LOAD% LOAD% LOAD%

EL0 1 % 1 % 1 % 1 %

END OF REPORT



DN0423824

Issue 3-2

65


Id:0900d805805490eb

Steps

1 Create a LAN Host Unit Traffic measurement (T2C).

Use the T2C command to create a LAN Host Unit Traffic measurement:








The object identifier parameters specify the type of the unit, and the index, the

type of the plug-in unit, and the index, and the interface or interfaces to be measured.


Use the T2S command to start a LAN Host Unit Traffic measurement that has already

been created:

T2S: NAME = <measurement name>:










Use the T2I command to interrogate the parameters of a LAN Host Unit Traffic mea-

surement:





Use the T2E command to stop a running LAN Host Unit Traffic measurement:







66 DN0423824

Issue 3-2


Id:0900d805805490eb

Maintaining LANs

LAN Host Unit Traffic measurement handling examples

Example: Creating a LAN Host Unit Traffic measurement

To create a LAN Host Unit Traffic measurement with measurement identifier 121, object

list identifier 001, and object list name HOST TRAFFIC MEASUREMENT 1, whose mea-

surement LAN interfaces are all interfaces of CP816-A-0 in OMU-0, enter the following

command:

T2C:MID=121:OID=001:OLN=HOST TRAFFIC MEASUREMENT

1:ID1=OMU,ID2=0,ID3=CP816_A,ID4=0::;

Example: Starting a LAN Host Unit Traffic measurement

To start the LAN Host Unit Traffic measurement created in example 11 above, enter the

following command:

T2S:NAME=PMEAS121:OID=001:ET=12-00-00,RAP=30,;

In this example, no explicit starting time is given and therefore the measurement willstart immediately. The stopping time is 12:00:00 . The measurement accumulation

period is 30 minutes.

Example: Interrogating the parameters of a LAN Host Unit Traffic measurement

To interrogate the parameters of the LAN Host Unit Traffic measurement created in


T2I:NAME=AMEAS121:OID=001:ICH=S:;


The output contains information about the measurement schedule.

EXECUTION STARTED

BSC3i ELVIS 2006-09-11 09:36:43


NAME: AMEAS121

OBJECT LIST ID: 001

OBJECT LIST NAME: HOST TRAFFIC MEASUREMENT 1

TYPE: LAN HOST UNIT TRAFFIC MEASUREMENT

STATE: ACTIVERESULT ACC. PERIOD: 30

START TIME: 11.09.2006 09:30:29

STOP TIME: 11.09.2006 12:00:00


OUTPUT DELAY: 0

COMMAND EXECUTED



DN0423824

Issue 3-2

67


Id:0900d805805490eb

Example: Stopping a running LAN Host Unit Traffic measurement

To stop the LAN Host Unit Traffic measurement created in example 11 above, enter the

following command:

T2E:NAME=AMEAS121:OID=001:ET=11-45-00,;

In this example, the measurement will not be stopped immediately but only at the spec-

ified stopping time (11:45:00 ).

5.9.4 Availability measurement

5.9.4.1 LAN Switch Availability Measurement report (290/122H)

The LAN Switch Availability Measurement report shows the number of switch restarts

during the accumulation period.

Use the commands of the T2 command group to create, start, or stop LAN Switch Avail-ability Measurement and to modify its parameters.

The objects measured in this report are switches (defined by the object identifier

parameters, which specify the unit type of the switch and the index).


• warm and cold restarts

• topology changes

• time of last restart.



LANAVASWIA ASCII report

LANAVASWIX XML report (Nokia NetAct usage)


example, DX MSCi ), followed by the name of the exchange, and the report output date


report type (in this case, LAN switch availability measurement report ), the output interval


mulation period of the report ends). After this, the LAN Switch Availability Measurement


Example: Example LAN Switch Availability Measurement report

UNIT PIU PIU WARM COLD LAST RESTART TOPOLOGY

TYPE INDEX RESTARTS RESTARTS TIME CHANGED

SWU-0 ESB20_A 0 0 0 0000-00-00 00:00:00 0

SWU-1 ESB26 0 2 0 2006-09-20 08:44:24 4

SWU-2 ESB20_A 0 0 0 0000-00-00 00:00:00 0

SWU-3 ESB26 0 2 0 2006-09-20 08:40:02 2

Please note that in this printout, TOPOLOGY CHANGED does not refer to LAN topology

changes as described in Changing and expanding the LAN topology of the communica-

tion network. Instead, it refers to the number of times the Spanning Tree Protocol had

to reroute a packet because of a problem it detected on the originally designated route.



68 DN0423824

Issue 3-2


Id:0900d805805490eb

Maintaining LANs

Steps

1 Create a LAN Switch Availability measurement (T2C).

Use the T2C command to create a LAN Switch Availability measurement:











Use the T2S command to start a LAN Switch Availability measurement that has already

been created:











Use the T2I command to interrogate the parameters of a LAN Switch Availability mea-

surement:





Use the T2E command to stop a running LAN Switch Availability measurement:







DN0423824

Issue 3-2

69


Id:0900d805805490eb

LAN Switch Availability measurement handling examples

Example: Creating a LAN Switch Availability measurement

To create a LAN Switch Availability measurement with measurement identifier 122 ,

object list identifier 003, and object list name SWITCH AVAILABILITY MEAS 3, that

contains all switches, enter the following command:

T2C:MID=122:OID=003:OLN=SWITCH AVAILABILITY MEAS 3:ID1=ALL:;

Example: Starting a LAN Switch Availability measurement

To start the LAN Switch Availability measurement created in example 16 above, enter

the following command:

T2S:NAME=PMEAS122:OID=003:RAP=60,;

In this example, no explicit starting or stopping time is given. Therefore the measure-

ment will start immediately and remain active until it is stopped explicitely with the T2E

command. The measurement accumulation period is 60 minutes.

Example: Interrogating the parameters of a LAN Switch Availability measurement

To interrogate the parameters of the LAN Switch Availability measurement created in


T2I:NAME=PMEAS122:OID=003:ICH=B:;

In this example, the measurement is not currently active.

The output contains information about the measurement schedule as well as the mea-

surement switching units and parameters.

EXECUTION STARTED

BSC3i ELVIS 2006-09-11 10:03:13


NAME: PMEAS122

OBJECT LIST ID: 003

OBJECT LIST NAME: AVAILABILITY 3

TYPE: LAN SWITCH AVAILABILITY MEASUREMENT

STATE: PASSIVE

RESULT ACC. PERIOD: -START TIME: -

STOP TIME: -

RESULT OUT. PERIOD: -

OUTPUT DELAY: -

MEASURED SWITCHING UNITS:

UNIT TYPE UNIT INDEX

SWU 0



70 DN0423824

Issue 3-2


Id:0900d805805490eb

Maintaining LANs

SWU 1

SWU 2

SWU 3

PARAMETERS:

0 COLD_RESTART

1 WARM_RESTART

2 RESTART_TIME

3 TOPOLOGY_CHANGES

COMMAND EXECUTED

Please note that in this printout, TOPOLOGY_CHANGES does not refer to LAN topology

changes as described in Changing and expanding the LAN topology of the communica-

tion network. Instead, it refers to the number of times the Spanning Tree Protocol had

to reroute a packet because of a problem it detected on the originally designated route.

Example: Stopping a running LAN Switch Availability measurement

To stop the LAN Switch Availability measurement created in example 16 above, enter

the following command:

T2E:NAME=AMEAS122:OID=003:ET=10-30-00,;


ified stopping time (10:30:00 ).

5.9.5 Error measurement

5.9.5.1 LAN Switch Error Measurement report (291/123H)

The LAN Switch Error Measurement provides information about the various types of

error counters in the switches during the accumulation period. The counter values for

this measurement are collected from those LAN elements that belong to the object

group that is defined when the measurement is created.

Use the commands of theT2 command group to create, start, or stop LAN Switch Error

Measurement and to modify its parameters.

The objects measured in this report are switches and their interfaces (defined by the

object identifier parameters, which specify the unit type of the switch, and the

index as well as the interface or interfaces to be measured).


• collisions and aborted transmissions

• CRC or frame alignment errors

• oversize and undersize packets

• FIFO overrun

• line not ready

• unknown packets

• RX pause ON/OFF

• TX pause ON/OFF.




DN0423824

Issue 3-2

71


Id:0900d805805490eb


LANERRSWIA ASCII report

LANERRSWIX XML report (Nokia NetAct usage)




report type (in this case, LAN switch error measurement report ), the output interval


mulation period of the report ends). After this, the LAN Switch Error Measurement


Example: Example LAN Switch Error Measurement report

MSCi HAUKKALA 2006-03-18 01:14:39

LAN SWITCH ERROR MEASUREMENT REPORT


UNIT PIU PIU

TYPE INDEX

SWU-1 CP710_A 7

INT. COLLIS CRC ALIGN OVERSIZE UNDERSIZE FIFO OVER LINE NOT UNKNOWN

ERRORS PKTS PKTS RUN COUNT READY CNT SAP PKTS

1/1/22 1 2 3 4 327681 - -

1/1/22 771 1028 1542 1285 393217 - -

RX PAUSE RX PAUSE TX PAUSE TX PAUSE

ON OFF ON OFF

1/1/22 - - - -

1/1/22 - - - -

UNIT PIU PIU

TYPE INDEX

SWU-1 ESB20_A 8



1/1/26 771 1028 1542 1285 589825 - -


ON OFF ON OFF

1/1/26 - - - -

UNIT PIU PIU

TYPE INDEX

SWU-1 ESB26 7



1/1/26 771 1028 1542 1285 458753 - -1/1/26 771 1028 1542 1285 524289 - -



72 DN0423824

Issue 3-2


Id:0900d805805490eb

Maintaining LANs


ON OFF ON OFF

1/1/26 - - - -

1/1/26 - - - -

END OF REPORT

Steps

1 Create a LAN Switch Error measurement (T2C).

Use the T2C command to create a LAN Switch Error measurement:











Use the T2S command to start a LAN Switch Error measurement that has already beencreated:











Use the T2I command to interrogate the parameters of a LAN Switch Error measure-

ment:





Use the T2E command to stop a running LAN Switch Error measurement:



DN0423824

Issue 3-2

73


Id:0900d805805490eb





LAN Switch Error measurement handling examples

Example: Creating a LAN Switch Error measurement

To create a LAN Switch Error measurement with measurement identifier 123, object list

identifier 001, object list name SWITCH ERROR MEAS 1, and measurement LAN inter-

faces SWU-0 1/1/9 and SWU-2 1/1/3, enter the following command:

T2C:MID=123:OID=001:OLN=SWITCH ERROR MEAS

1:ID1=SWU,ID2=0,ID3=1/1/9,:ID1=SWU,ID2=2,ID3=1/1/3,;

Example: Starting a LAN Switch Error measurement

To start the LAN Switch Error measurement created in example 21 above, enter the fol-lowing command:

T2S:NAME=PMEAS123:OID=001:;

In this example, no explicit starting or stopping time is given. Therefore the measure-

ment will start immediately and remain active until it is stopped explicitely with the T2E

command. For the measurement accumulation period, the default value (15 minutes) is

used.

Example: Interrogating the parameters of a LAN Switch Error measurement

To interrogate the parameters of the LAN Switch Error measurement created in example

21 above, enter the following command:

T2I:NAME=PMEAS123:OID=001:ICH=B:;

In this example, the measurement is not currently active.

The output contains information about the measurement schedule as well as the mea-

surement LAN interfaces and parameters.

EXECUTION STARTED

BSC3i ELVIS 2006-09-11 09:48:02


NAME: PMEAS123

OBJECT LIST ID: 001

OBJECT LIST NAME: SWITCH ERROR MEAS 1

TYPE: LAN SWITCH ERROR MEASUREMENT

STATE: PASSIVE

RESULT ACC. PERIOD: -

START TIME: -

STOP TIME: -

RESULT OUT. PERIOD: -

OUTPUT DELAY: -



74 DN0423824

Issue 3-2


Id:0900d805805490eb

Maintaining LANs

MEASURED LAN INTERFACES:

UNIT TYPE UNIT INDEX INTERFACE

SWU 0 1/1/9

SWU 2 1/1/3

PARAMETERS:

0 COLLISIONS

1 CRC_ALIGN_ERRORS

2 UNDERSIZE_PKTS

3 OVERSIZE_PKTS

4 FIFO_OVERRUN5 LINE_NOT_READY

6 UNKNOWN_SAP_PKTS

7 RX_PAUSE_ON

8 RX_PAUSE_OFF

9 TX_PAUSE_ON

10 TX_PAUSE_OFF

COMMAND EXECUTED

Example: Stopping a running LAN Switch Error measurement

To stop the LAN Switch Error measurement created in example 21 above, enter the fol-

lowing command:

T2E:NAME=AMEAS123:OID=001:;

In this example, no explicit stopping time is given and therefore the measurement will be

stopped immediately.

5.9.5.2 LAN Host Unit Error Measurement report (292/124H)

The LAN Host Unit Error Measurement provides information about the various types of

error counters in the host units during the accumulation period. The counter values for

this measurement are collected from those LAN elements that belong to the object

group that is defined when the measurement is created.Use the commands of the T2 command group to create, start, or stop LAN Host Unit

Error Measurement and to modify its parameters.

The objects measured in this report are plug-in units and their interfaces (defined by the

object identifier parameters, which specify the type of the unit, and the index and

the type of the plug-in unit, and the index).


• collisions and aborted transmissions

• CRC or frame alignment errors

• oversize and undersize packets

• FIFO overrun• line not ready



DN0423824

Issue 3-2

75


Id:0900d805805490eb

• unknown packets

• RX pause ON/OFF

• TX pause ON/OFF



LANERRHOSA ASCII report

LANERRHOSX XML report (Nokia NetAct usage)




report type (in this case, LAN host unit error measurement report ), the output interval


mulation period of the report ends). After this, the LAN Host Unit Error Measurement


Example: Example LAN Switch Error Measurement report

MSCi HAUKKALA 2006-03-18 01:23:29

LAN HOST UNIT ERROR MEASUREMENT REPORT


UNIT PIU PIU

TYPE INDEX

OMU-0 CP710_A 7



EL0 771 1028 1542 1285 393217 2 3

EL1 8 51 42 9 221 1 1


ON OFF ON OFF

EL0 2 5 6 7

EL1 3 1 2 3

END OF REPORT

Steps

1 Create a LAN Host Unit Error measurement (T2C).

Use the T2C command to create a LAN Host Unit Error measurement:







76 DN0423824

Issue 3-2


Id:0900d805805490eb

Maintaining LANs




The object identifier parameters specify the type of the unit, and the index, thetype of the plug-in type and the index, and the interface or interfaces to be measured.


Use the T2S command to start a LAN Host Unit Error measurement that has already

been created:











Use the T2I command to interrogate the parameters of a LAN Host Unit Error measure-

ment:





Use the T2E command to stop a running LAN Host Unit Error measurement:





LAN Host Unit Error measurement handling examples

Example: Creating a LAN Host Unit Error measurement

To create a LAN Host Unit Error measurement with measurement identifier 124, object

list identifier 002 , and object list name HOST ERROR MEAS 2 , whose measurement

interfaces are all interfaces of CP816-A-0 in MCMU-0, enter the following command:

T2C:MID=124:OID=002:OLN=HOST ERROR MEAS

2:ID1=MCMU,ID2=0,ID3=CP816_A,ID4=0;

Example: Starting a LAN Host Unit Error measurement

To start the LAN Host Unit Error measurement created in example 26 above, enter the

following command:

T2S:NAME=PMEAS124:OID=002:SD=2006-10-01,ST=00-00-00,ED=2006-10-31,ET=23-59-59,;



DN0423824

Issue 3-2

77


Id:0900d805805490eb

In this example, the starting time and date are 00:00:00 on 01 Oct 2006 and the stopping

time and date are 23:59:59 on 31 Oct 2006 . For the measurement accumulation period,

the default value (15 minutes) is used.

Example: Interrogating the parameters of a LAN Switch Error measurement

To interrogate the parameters of the LAN Switch Error measurement created in example

26 above, enter the following command:

T2I:NAME=AMEAS124:OID=002:ICH=B;


The output contains information about the measurement schedule and the measure-

ment objects.


EXECUTION STARTED

BSC3i ELVIS 2006-09-11 09:56:07


NAME: AMEAS124

OBJECT LIST ID: 002

OBJECT LIST NAME: HOST ERROR MEAS 2

TYPE: LAN HOST UNIT ERROR MEASUREMENT

STATE: ACTIVERESULT ACC. PERIOD: 15

START TIME: 01.10.2006 00:00:00

STOP TIME: 31.10.2006 23:59:59


OUTPUT DELAY: 0

MEASURED HOST UNITS:

UNIT TYPE UNIT INDEX PIU TYPE PIU INDEX

MCMU 0 CP816_A 0

PARAMETERS:

0 COLLISIONS

1 CRC_ALIGN_ERRORS

2 UNDERSIZE_PKTS

3 OVERSIZE_PKTS

4 FIFO_OVERRUN

5 LINE_NOT_READY

6 UNKNOWN_SAP_PKTS7 RX_PAUSE_ON



78 DN0423824

Issue 3-2


Id:0900d805805490eb

Maintaining LANs

8 RX_PAUSE_OFF

9 TX_PAUSE_ON

10 TX_PAUSE_OFF

COMMAND EXECUTED

Example: Stopping a running LAN Switch Error measurement

To stop the LAN Switch Error measurement created in example 26 above, enter the fol-

lowing command:

T2E:NAME=AMEAS124:OID=002:ED=2006-10-10,ET=12-00-00;


ified stopping time and date (12:00:00 on 10 Oct 2006 ).

5.9.6 Short time measurement

The Short Time LAN Measurement provides statistical data about the LAN element in

question during the short measurement period. This data includes information about the

utilisation of the interface (received and transmitted load rates) and the amount of data

actually transmitted through the interface.

Use the YFT command to perform a Short Time LAN Measurement and to modify its

parameters.

Statistics can be collected for one specific interface from the switch (defined by the

parameters unit type, unit index, and port index) or for all interfaces of the

plug-in unit (defined by the parameters unit type, unit index, piu type, and piu

index).

Each report begins with the measurement heading (Short Time LAN Measurement report ), followed by the output interval (between 2 and 20 seconds). After this, the fol-

lowing data is presented in the form of a table:

UNIT The unit type and index of the measurement object.

PIU The plug-in unit type and index of the measurement object.

INTERFACE The identifier of the LAN Ethernet interface.

TRANSMITTED LOAD RATE (%) The average utilisation rate of the transmitting

interface during the measurement period.

RECEIVED LOAD RATE (%) The average utilisation rate of the receiving interface

during the measurement period.

TOTAL BIT RATE (KBIT/SEC) The sum of the bit rates at the receiving and the trans-

mitting end of the connection (that is, the bit rate for transmissions from

either end of the connection).

Example: Example Short Time LAN Measurement report

The transmitted bit rate value refers to the total bit rate (that is, transmissions from both

ends of the connection are taken into account).

EXECUTION STARTED

SHORT TIME LAN MEASUREMENT REPORT

INTERVAL : 5 SEC

TRANSMITTED RECEIVED TOTAL BIT RATE



DN0423824

Issue 3-2

79


Id:0900d805805490eb

UNIT PIU INTERFACE LOAD RATE (%) LOAD RATE (%) (KBIT/SEC)

----------------------------------------------------------------------------

SWU-0 ESB26 1/1/3 1 1 3099

COMMAND EXECUTED

Steps

1 Perform a Short Time LAN measurement (YFT).

Use the YFT command to perform a Short Time LAN measurement:

YFT:[ < action > | STA def ]:

< unit type >,< unit index >,

[ < piu type >,< piu index > ]:

[ < port index > | 0 def ]:

[ < measurement time > | 10 def ];

Short Time LAN measurement handling examples

Example: Performing a Short Time LAN measurement on a switch

To perform a Short Time LAN measurement on interface 1/1/3 of SWU-0 over the

course of the next ten seconds, enter the following command:

ZYFT:STA:SWU,0:ESB26:3:10;

EXECUTION STARTED


INTERVAL : 10 SEC TRANSMITTED RECEIVED TOTAL BIT RATE


----------------------------------------------------------------------------

SWU-0 ESB26 1/1/3 1 1 3111

COMMAND EXECUTED

Example: Performing a Short Time LAN measurement on a host unit

To perform a Short Time LAN measurement on all interfaces of CP816-A-0 in MCMU-0

over the course of the next five seconds, enter the following command:

ZYFT:STA:MCMU,0,CP816_A,0:0:5:;

EXECUTION STARTED


INTERVAL : 5 SEC

TRANSMITTED RECEIVED TOTAL BIT RATE


----------------------------------------------------------------------------

MCMU-0 CP816_A-0 EL0 1 1 3105

EL1 0 0 0

COMMAND EXECUTED



80 DN0423824

Issue 3-2


Id:0900d805805490eb

Maintaining LANs

The measurement period of a Short Time LAN measurement begins at the moment the

command is entered. In this example, it ends five seconds later.



DN0423824

Issue 3-2

81

Integrated LAN Administration Changing and expanding the LAN topology of the com-munication network

Id:0900d8058034257b

6 Changing and expanding the LAN topology

of the communication network

The system can have several preconfigured LAN topologies. A preconfigured topologycan be used in the network element as such, if it is similar to the LAN connections

existing in that network element. (For instructions on how to select the right topology,

see Selecting the LAN topology.)

If it is necessary to use a different kind of hardware in the network element than the

hardware configuration and cabling defined by Nokia Siemens Networks, you have to

modify the preconfigured topology, or to create a new topology from scratch.

A modified topology is not saved before you have finished the modification. If an OMU

unit restart or switchover is made during the modification, all data is lost.

☞ If you want to take a backup copy of the topology when you are making the modifi-

cations, do the following:

1. Finish the modification by saving the topology to the next free topology available

(see step Finish the modification of the topology below).

2. Form the topology you saved.

3. Modify the topology further.

4. When you have made all necessary modifications, finish the modification by

overwriting the saved topology.

g No configuration changes are allowed when the network element is split into

TELE/TRIAL configurations.

The topology of EMB LAN cannot be modified.

Measurements should be taken in a stable environment in order to yield reliable


changes are made.

Steps

1 Form the topology (W6N).

The topology must be formed before it can be modified. Choose any of the following

alternatives:

a) To form an empty topology which you intend to create from scratch, give the follow-

ing command:ZW6N:FRM,N,<emb topology index>:;

The EMB topology is copied from an existing topology and cannot be changed.

b) To select one of the existing topologies and form a topology that can be used as a

basis for modifications, give the following command:

ZW6N:FRM,<topology index>;

This command can be used when opening an unfinished topology that can be

modified further.


a Add a new LAN switch to the topology (W6N).

ZW6N:ADD:SWU,<unit index>,<role>,<ports>;



82 DN0423824

Issue 3-2


Id:0900d8058034257b

Changing and expanding the LAN topology of the com-munication network

The role parameter in the command indicates the place of the LAN switch in the

topology. It consists of two numbers: the first one indicates how many connection

link steps there are from any computer unit to the switch, and the second one indi-

cates how many management connection link steps there are from the network ele-

ment’s supervising unit to the switch.

Example of role determination: In the figure Example of LAN switch topology for

outband management, the role number of SWU-2 is 12, the role number of SWU-8

is also 12, and the role number of SWU-6 is 11.

The maximum number of switches in one topology is 100 (up to 70 communication

network switches and up to 30 EMB LAN switches).

☞ Add all the new LAN switches to the topology first, so that all connections can

be created.

b Remove a LAN switch from the topology (W6N).

If there are connections to a LAN switch in the topology, the switch cannot be

removed. First remove the connections.

Steps

a Check that the LAN switch does not have any connections in the topology.

b If the LAN switch has any connections, remove them.

ZW6N:MCO:SWU,<unit index>:port;

c Remove the LAN switch from the topology.

ZW6N:DEL:SWU,<unit index>;

c Modify the data of a LAN switch (W6N).

ZW6N:MOD:SWU,<unit index>,<role>,<ports>,<new unit type>,<new

unit index>;

The new unit type and new unit index parameters in the command replace

the LAN switch index with a new one, but the command cannot make a copy.

The command automatically creates all existing connections to the new unit index.

The command can also be given without the new unit type and new unit

index parameters.

d Modify LAN switch data and create a port connection (W6N).

ZW6N:MCO:SWU,<unit index>:<port index>,<dest unit type>,<dest

unit index>,<dest piu type>,<dest piu index>,<dest port

index>,<connection type>;

This command can be executed only if the destination LAN switch type and index

can be found in the topology.

The parameters destination piu type and destination piu index are

used only for those network element units that have a separate plug-in unit card for

LAN connections.

e Delete the LAN port connection (W6N).

ZW6N:MCO:SWU,<unit index>:port;



DN0423824

Issue 3-2

83

Integrated LAN Administration Changing and expanding the LAN topology of the com-munication network

Id:0900d8058034257b

The command overwrites all parameters given for the port connection.

3 Check that the modifications were made correctly (W6I).

ZW6I:SWU,<unit index>::M;

4 Finish the modification of the topology (W6N).

You can finish the modification of a topology in any of the following ways:

a) Overwrite one of the existing preconfigured network element topologies.

ZW6N:END,<topology index>;

b) Save the modified topology to the first free space available in the file.

ZW6N:END,T5;

c) Close the topology file without saving the modifications.

ZW6N:END,Q;

g A topology can be saved only if all the connections defined in the topology are

correct. If saving the topology fails, check the computer logs of the OMU working unit

with the service terminal command 00-LOG>ZGSC;,651 .

Further information

The parameter guide of command ZW6N shows the topologies existing in the network

element, and the next empty space where the new/modified topology can be saved. For

example:

W6N:END

/* IDENTIFY TOPOLOGY INDEX:T1 - T4 REPLACE OLD TOPOLOGY

T5 ... SAVE TO EMPTY PLACE

Q ... DELETE TOPOLOGY WITHOUT SAVING */

5 Activate the topology (W6G).

Steps

a When you have finished all the modifications, activate the new topology.


b If the saved topology is already active, reload the current topology.

ZW6G:R;



84 DN0423824

Issue 3-2


Id:0900d80580461473

Integrated LAN Administration troubleshooting

7 Integrated LAN Administration troubleshoot-

ing

7.1 Supervision of a LAN switch fails

When the LAN Hardware Supervision Handling detects that a switch is not answering to

the supervision, it sets the alarm 3252 – LAN DEVICE SUPERVISION FAILURE.

Steps

1 For recovery instructions, see Failure Printouts.

7.2 Supervision of a connection fails

When the LAN Hardware Supervision Handling detects a faulty connection, it sets the

alarm 3292 – INTERNAL LAN LINK BROKEN.

Steps


7.3 The software package or sysloader update of a LAN

switch fails

This error situation may occur when you have tried to load software from the system tothe LAN switch with the YFM command (see Updating the software package of a LAN

switch). If the update fails, the received error code is printed out on the MML terminal,

and the alarm 3254 – LAN DEVICE GENERAL FAILURE with cause 05 (SW package

cannot be loaded to LAN device) is set.

For recovery instructions, see Failure Printouts.

7.3.1 Wrong software version in the LAN switch

After restarting a LAN switch, the system compares the version of the running software

to the version delivered in the current software build. If the system detects that new

software is available in the build, the alarm 3254 – LAN DEVICE GENERAL FAILUREwith cause 09 (Too old software version in LAN device) is set.

Steps


7.3.2 Wrong LAN switch password

The system sets the alarm 3254 – LAN DEVICE GENERAL FAILURE with cause 08

( Wrong password of LAN device in Topology Management data).



DN0423824

Issue 3-2

85

Integrated LAN Administration Integrated LAN Administration troubleshooting

Id:0900d80580461473

Steps

1 Check the password of the LAN switch.

Check that the password of the LAN switch is the same in the switch and in the system.

2 Update the password, if necessary.

For instructions, see Updating the password of a LAN switch.

7.3.3 Missing or incorrect LAN switch IP address

Steps

1 For recovery instructions, see IP addressing failure.

7.4 Configuration file transfer to a LAN switch fails


(Configuration file cannot be loaded to LAN device).

Steps


7.5 Traps not received from a LAN switch A LAN switch SNMP agent can be programmed to send out a trap when a certain set of

circumstances arises. These circumstances are usually hard-coded in the SNMP agent

of the LAN switch and cannot be modified. The LAN switch SNMP agent sends the trap

to the SNMP manager’s trap host IP address. The address must be the same as the IP

address of the LAN switch supervising unit interface.

If traps are not received from a LAN switch, the reason may be one of the following:

7.5.1 There is no connection from the LAN switch to the system

If a LAN switch does not seem to have a connection to the system, there may be a failure

in the IP connections.

Steps

1 Check the supervision data of the LAN switch (YFF).


2 Try to open a Telnet connection to the switch (W6T).

This cannot be done with an EMB LAN switch.

ZW6T:SWU,<unit index>;If the Telnet connection works, there is no problem with the IP connection.



86 DN0423824

Issue 3-2


Id:0900d80580461473


7.5.2 The trap host IP address could not be set to the LAN switch by the

system


(Internet Protocol (IP) address of Simple Network ManagementProtocol (SNMP) manager cannot be set to Local Area Network (LAN)

device).

Steps



2 Check the IP address of the SNMP manager (QRI).

Steps

a Find out to which LAN the LAN switch belongs (WYI).

ZWYI:U;

b Find out the IP address range of the LAN (WYI).

ZWYI:L:<LAN id>;

The IP address in IP ADDRESS RANGE: START (that is, the first address of the

address space for this LAN) should have been configured to the supervising unit’s

interface. This is also the address of the SNMP manager.

c Check that the IP address is configured to the interface of the supervising unit(QRI).

ZQRI:<supervising unit>;

The following rules should apply:

• The first IP address of the LAN that contains LAN switches with even indexes,

such as SWU-0 or SWU-2, is configured to the EL0 interface.

• The first IP address of the LAN that contains LAN switches with odd indexes,

such as SWU-1 or SWU-3, is configured to the EL1 interface.

• The first IP address of the LAN that contains EMB LAN switches with even

indexes, such as SWU-60 or SWU-62, is configured to the EMB0 interface.

• The first IP address of the LAN that contains EMB LAN switches with oddindexes, such as SWU-61 or SWU-63, is configured to the EMB1 interface.

d Check that the SNMP manager’s IP address is configured correctly in the LAN

switch as well (W6T).

1. Open a Telnet session to the LAN switch.

ZW6T:SWU,<index>;

g You cannot open a Telnet session to an EMB LAN switch.

2. Switch to enabled mode.

Switch prompt>ena



DN0423824

Issue 3-2

87


Id:0900d80580461473

3. Query the running configuration of the LAN switch.

SWU-0#show running-config

The running configuration should contain the following kind of row:

snmp-server target-addr mcmu 10.0.2.1 162 Nm_public tag14. Verify that the snmp-server target-addr has the same IP address as the one

found in the supervising unit’s interface.

3 Compare the SNMP manager’s IP address to the LAN switch configuration.

4 Update the IP address, if necessary.

If the SNMP manager’s IP address is different in the running configuration and in the

system, change the address to the configuration.

For instructions, see SNMP operation fails.

5 Load the configuration file from the CNW LAN switch to the system (YFM).


7.5.3 Traps have not been activated in the LAN switch

Steps

1 Check the running configuration of the LAN switch.

2 Add the missing traps to the configuration so that the SNMP server can be

notified about additional event and error types.



Further information


7.5.4 The SNMP server is disabled

Steps

1 Check the running configuration of the LAN switch.

2 Enable the SNMP in the configuration.





88 DN0423824

Issue 3-2


Id:0900d80580461473


Further information


7.5.5 The reason for the problem is unknown

Steps

1 Check the SnmpTargetAddrEntry and SnmpTargetParams tables of the SNMP-

TARGET MIB.

Further information

For instructions, see Preconfiguring LAN switches.

7.5.6 SNMP Trap overload detectedLAN device integration SNMP mediator has detected too many TRAPs of the same type

created continuously by the same IP-address. Incoming TRAPS are filtered out from the

particular IP-address and alarm 3440 - SNMP TRAP OVERLOAD is set.

Steps


7.6 SNMP operation fails

The SNMP is used to monitor and configure the LAN switches by means of GET andSET operations and traps. If a LAN switch does not respond to SNMP GET/SET

requests, the reason may be one of the following:

7.6.1 Incorrect parameters in MML command

Steps

1 Check the IP address and switch type (W6I).

ZW6I:SWU,<unit index>:::;

2 If the problem occurs with the SET requests, check that the new value given is

suitable for the object identifier (OID) (YFS).

ZYFS:INQ:<switch type>:<request id>;

7.6.2 There is no IP connection to the LAN switch

Steps





DN0423824

Issue 3-2

89


Id:0900d80580461473

2 Try to open a Telnet connection to the switch (W6T).

g This cannot be done with an EMB LAN switch.


If the Telnet connection works, there is no problem with the IP connection.

3 Check the IP configuration of the supervision unit (QRI).

ZQRI:<unit index>,<unit index>;

4 Establish a console (SERIAL) connection to the switch and check its configura-

tion.

ESB26#sho run;

7.6.3 The SNMP configuration in the LAN switch is incorrect


(SNMP settings are incorrect).

The most common problems with the SNMP are caused by incorrect configurations. The

configuration of individual LAN switches varies, but it should be done according to the

following general principles:

• The community string must be the same in the LAN switch configuration and in the

system.

• A false community string generates an authenticationFailure trap or several traps,

because the system tries many times to execute every command with a false com-munity string.

• It is possible to set authenticationFailure traps to ON and OFF via the SNMP by

updating OID snmpEnableAuthen traps.

Steps






a Configure the SNMP in a LAN switch of type ESB20.

1. For Read community name, set the value public .

2. For Write community name, set the value public .

3. For Trap community name, set the value public .

4. For Send alert traps, set the value Yes.

5. For Advanced Mode, set the value No.



90 DN0423824

Issue 3-2


Id:0900d80580461473


b Configure the SNMP in a LAN switch of a different ESB type than ESB20.

(The terms enclosed in quotation marks (‘-’) are user defined.)

Steps

a Check the current parameter settings.


You get the following kind of printout (‘A.B.C.D’ occurring in the printout stands

for the supervising unit’s interface IP address):

In ESB20-A type switch


!

!

snmp-server enable

snmp-server view viewAll 1.3 includedsnmp-server group Grp_public v1 read viewAll write viewAll notify viewAll

snmp-server group Grp_public v2c read viewAll write viewAll notify viewAll

snmp-server user public group Grp_public v1

snmp-server user public group Grp_public v2c

snmp-server target-param Nm_public public v2c

snmp-server target-addr traphost.public.A.B.C.D A.B.C.D 162 Nm_public tag1

snmp-server notify authenticationFailure tag1

snmp-server notify coldStart tag1

snmp-server notify linkDown tag1

snmp-server notify linkUp tag1

snmp-server notify warmStart tag1snmp-server notify topologyChange tag1

snmp-server notify mstpTopologyChange tag1

snmp-server notify portsCRCErrExceeded tag1

!

In ESB26 type switch


!

!

snmp-server enable








snmp-server notify coldStart tag1 inform



snmp-server notify warmStart tag1 inform

snmp-server notify topologyChange tag1



DN0423824

Issue 3-2

91


Id:0900d80580461473

snmp-server notify mstpTopologyChange tag1

snmp-server notify cpuTemperatureExceeded tag1

snmp-server notify imageCrcCheckFailed tag1

snmp-server notify configurationLoadFailed tag1

snmp-server notify cpuUtilizationExceeded tag1

snmp-server notify ramFreeSpaceExceeded tag1


!

In ESB14-A type switch


!

!

snmp-server enable








snmp-server notify coldStart tag1



snmp-server notify warmStart tag1

snmp-server notify topologyChange tag1snmp-server notify mstpTopologyChange tag1

snmp-server notify cpuTemperatureExceeded tag1

snmp-server notify imageCrcCheckFailed tag1

snmp-server notify configurationLoadFailed tag1

snmp-server notify cpuUtilizationExceeded tag1

snmp-server notify ramFreeSpaceExceeded tag1


!

If some SNMP setting is missing, continue from the next step.

b Activate the SNMP in the switch.

device-name(config)# snmp-server enable

c Enable access to all ‘viewAll’ object IDs.

device-name(config)# snmp-server view viewAll 1.3 included

The view is defined to start from 1.3 in the OID tree. This view does not restrict

the visibility of OIDs.

d Create group ‘Grp_public’ version 1.

device-name(config)# snmp-server group Grp_public v1 read

viewAll write viewAll notify viewAll



92 DN0423824

Issue 3-2


Id:0900d80580461473


The group uses ‘viewAll’ in the read (GET), write (SET), and notify (trap) opera-

tions.

e Create user ‘public’ version 1.

device-name(config)# snmp-server user public group

Grp_public v1

The user belongs to the ‘Grp_public’ group.

f Create group ‘Grp_public’ version 2c.

device-name(config)# snmp-server group Grp_public v2c read

viewAll write viewAll notify viewAll

The group uses ‘viewAll’ in the read (GET), write (SET), and notify (trap) opera-

tions.

g Create user ‘public’ version 2c.

device-name(config)# snmp-server user public Grp_public v2c

The user belongs to the ‘Grp_public’ group. The group and the user are created

with versions 1 and 2c, because the two versions must be used at the same

time.

h Create user ‘Nm_public’ (which sends traps) version 2c with community

string ‘public’.

device-name(config)# snmp-server target-param Nm_public

public v2c

Nm_public and tag1 must be used every time, because they are coded to

system.

i Set an IP address for the target of the trap host.

The IP address of the trap host is set by the system and should not be modified.

device-name(config)# snmp-server target-addr

traphost.public.A.B.C.D A.B.C.D 162 Nm_public tag1

The IP address to which SNMP traps will be sent is ‘A.B.C.D’. Traps linked to

‘tag1’ are sent to this trap host. You can check the IP address of the supervising

unit with the ZQRI command.

j Link the traps to the ‘tag1’ list.

This command must be executed for every trap the LAN switch sends. In the fol-lowing command example, the trap notifying of a coldstart is linked to the ‘tag1’

list.

device-name(config)# snmp-server notify coldstart tag1

device-name(config)# snmp-server notify warmStart tag1

device-name(config)# snmp-server notify linkDown tag1

device-name(config)# snmp-server notify linkUp tag1

device-name(config)# snmp-server notify

authenticationFailure tag1



DN0423824

Issue 3-2

93


Id:0900d80580461473

k Save the settings to the configuration file.

device-name(config)# write memory

c Configure the SNMP in a 3rd-party switch (L3 switch).

Steps

a Check the current parameter settings.


You get the following kind of printout (‘A.B.C.D’ occurring in the printout stands

for the supervising unit’s interface IP address):

!

version 12.1

!

snmp-server community public RW

snmp-server system-shutdown

snmp-server enable traps snmp authentication warmstart linkdown

linkup coldstart

snmp-server enable traps config

snmp-server enable traps entity

snmp-server enable traps rtr

snmp-server enable traps vlan-membership

snmp-server enable traps vtp

snmp-server enable traps MAC-Notification

snmp-server enable traps hsrp

snmp-server enable traps cluster

snmp-server host A.B.C.D public!

!

end

If some SNMP setting is missing, continue from the next step.

b Activate SNMP and traps in the switch.

Switch(config)#snmp-server enable traps snmp authentication

warmstart linkdown linkup coldstart

c Define community strings read (R) and write (W) for ‘public’.

Switch(config)# snmp-server community public RW

d Define the IP address where the trap host sends the traps.

The community using this trap host is ‘public’. Replace ‘A.B.C.D’ in the

command with the supervising unit’s IP address. You can check the IP

addresses in use with the QRI command.

Switch(config)# snmp-server host A.B.C.D public

e Enable the use of the SNMP reload (reset) command.

Switch(config)# snmp-server system-shutdown

f Define the length of the trap queue.

Switch(config)# snmp-server queue-length <1-1000>



94 DN0423824

Issue 3-2


Id:0900d80580461473


The recommended value is 10. This is also the default value.

g Save the settings in the configuration file.

Switch(config)#write memory

7.6.4 Capacity has been exceeded

The SNMP manager is processing too many tasks at the same time. The error text TOO

MANY OPERATIONS IN QUEUE is displayed on the screen or the error code 16190

MDS_OVERLOADED_EC is written into the computer log of OMU.

Steps

1 Wait for a while, then try again to make the SNMP request.

7.7 IP addressing failure

Problems with the IP address or with the configuration of the LAN switch may be indi-

cated in the following ways:

• The LAN switch cannot be reached (printout of command YFF:INQ;).

• Inquiring the software version of a LAN switch (command YFM) fails.

• Updating the LAN switch software (command YFM) fails.

• Uploading the configuration file to a LAN switch (command YFM) fails.

• Downloading the configuration file from a LAN switch (command YFM) fails. (This

cannot be done with an EMB LAN switch.)

• Resetting a LAN switch (command YFM) fails. (This cannot be done with an EMBLAN switch.)

• Executing an SNMP GET or SET (command YFX) fails. (SETs cannot be done with

an EMB LAN switch.)

• Connecting to the LAN switch via a Telnet (command W6T) fails. (This cannot be

done with an EMB LAN switch.)

• An inquired link of the current LAN topology (command YFE) is not listed either in

the connections or in faulty links.

• Alarm 3252 – LAN DEVICE SUPERVISION FAILURE has been set.

• Alarm 3254 – LAN DEVICE GENERAL FAILURE has been set.

Steps

1 Check the configuration state of the IP addresses of the LAN switches (YFF).


You get the following kind of printout:


EXECUTION STARTED

READING LAN SWITCH SUPERVISION DATA ...

UNIT PIU TYPE IP ADDRESS MAC ADDRESS LAN UNIT



DN0423824

Issue 3-2

95


Id:0900d80580461473

-------------------------------------------------------------------

SWU - 0 ESB20_A 10.12.18.4 E0:00:1E:80:4C:00 CNW - 0

INTERNAL LAN CONFIGURATION STATUS:

-------------------------------

IP ADDRESS CONFIGURED : OK

CONFIGURATION FILE LOADED : OK

SNMP VERSION CONFIGURED : v2

TRAP HOST CONFIGURED : OK

SUPERVISION STATUS:

-------------------------------

SUPERVISION ENABLED : ON

SUPERVISION CYCLE (SEC) : 60

SUPERVISION STATUS : REACHABLE

LAST SUPERVISION DONE : 2005-09-27 14:37:11.99

2 Check the field IP ADDR CONFIGURED of the printout.


a If If the IP ADDR CONFIGURED field has the value OK .

Then

The LAN switch has obtained the management IP address via DHCP.

Steps

a Check the alarm history (AHO).

ZAHO:SWU,<unit index>::;

The alarm 3252 – LAN DEVICE SUPERVISION FAILURE should be active.

b Follow the recovery instructions given in the alarm description.

See Failure Printouts.

b If If the IP ADDR CONFIGURED field has the value NOK .

Then

The LAN switch has not obtained the management IP address via DHCP.

Steps

a Check the alarm history (AHO).

ZAHO:SWU,<unit index>::;

The alarm 3254 – LAN DEVICE GENERAL FAILURE should be active.

b Follow the recovery instructions given in the alarm description.

See Failure Printouts.

c If If the IP ADDR CONFIGURED field has the value ‘-’.

Then



96 DN0423824

Issue 3-2


Id:0900d80580461473


Steps

a Enable the DHCP.

The DHCP client in the LAN switch must be enabled and running to get the

system-allocated management IP address for the LAN switches automatically

via the DHCP procedure.

If the system-allocated IP address is not used, the DHCP is not enabled in the

LAN switch, and the IP address, mask and default route must be set manually

via the service terminal. For instructions on how to enable the DHCP, see Pre-

configuring LAN switches.

b Check the activation status of the LAN switch.

Make sure that the LAN switch has been activated. For instructions on how to

activate the LAN switch, see Activating LAN switches.

c Check the supervising unit static routes (command QKB).

If the LAN switch IP address is not in the same subnet as the supervising unit IP

address, make sure that the supervising unit static routes have been configured

correctly.

d Check the VLAN configurations of the LAN switch.

Make sure that the LAN switch does not have any tagged-mode VLAN configu-

rations in the LAN switch management port.

e Check that the IP address offered is not in use.

Make sure that the IP address the DHCP server is offering to the LAN switch has

not been assigned to another LAN device in the same network.

f Check the DHCP server connection.

If the LAN switch has received a wrong IP address, make sure that there is no

other DHCP server connection to the LAN.

g Check the location of the ADMODD module (W6I).

Make sure that the location of the ADMODD module is correct, and that the

location is the same in the system configuration.

To check the position from the system and from the LAN switch, do the following:

1. Print out the LAN switch location number defined in the topology.

ZW6I:SWU,<unit index>:::;

You get the following kind of printout:

UNIT TYPE STATUS LAN ID LAN NAME LAN UNIT

------------------------------------------------------------

SWU-6 ESB20-A ACTIVE 1 MGMT1 CNW-0

LOCATION IP-ADDRESS IP-MASK MAC-ADDRESS

------------------------------------------------------------

0X1218 10.12.18.3 26 00.00.A7.01.33.A2

2. Print out the LAN switch location number defined in the LAN switch.

device-name#show positioning



DN0423824

Issue 3-2

97


Id:0900d80580461473

3. If the location numbers in the LAN switch and in the topology are not identi-

cal, change either number.

For instructions on how to change the location number in the topology, see

Creating the hardware configuration description.

For instructions on how to change the location number in the ADMODD

module, see Jumper Settings of the Cartridges in i-series Network Elements.

h Check that PING is working.

Make sure that PING (command QRX) to the LAN switches is working between

the supervising unit and the LAN switch you are configuring.

7.8 LAN switch is faulty

If a LAN switch does not respond to the LAN Hardware Supervision Handling, the super-

vision sets an alarm (3252 – LAN DEVICE SUPERVISION FAILURE), and all the ports

in the switch are set to the INI state. When you print out the LAN Hardware Supervision

Handling data with the YFF command, the printout does not show the port data of the

faulty switch.

Steps

1 For instructions on how to replace the faulty switch, see Replacing a switch with

one of the same type.

7.9 LAN Hardware Supervision Handling log has been cor-

ruptedIf an error log entry AKSHA1:cannot parse LFILES/AKSSULOG.XML file is found in the

OMU’s computer log (ZGDC), it means that the LAN Hardware Supervision Handling log

has been corrupted in some way and cannot be parsed to the memory. New log writings

cannot be added to the log file.

Steps

1 Restore a new empty LAN Hardware Supervision Handling log file (YFL).

ZYFL:CLR;

Further information

If the corrupted log file includes data, the file is renamed to LFILES/AKSSULOG.BAK

before a new empty log is written on the disk.

If an empty LAN Hardware Supervision Handling log file is successfully restored, an

entry AKSHA1:empty LFILES/AKSSULOG.XML restored is written in the OMU’s

computer log.



98 DN0423824

Issue 3-2


Id:0900d80580461473


7.10 LAN statistics troubleshooting

7.10.1 A LAN statistics measurement has failed

There are several problems that can cause a LAN statistics measurement to fail. If a

LAN statistics measurement has failed, the problem needs to be identified and fixed

before any attempts to repeat the failed measurement can be made.

Before you start

Some fault situations are only temporary. Before you attempt to identify and fix the

problem that has caused the measurement to fail, repeat the measurement. If it

succeeds this time, no troubleshooting is necessary. If it fails again, take the following

steps:

Steps

1 Perform a Short Time measurement on the same measurement object.

Short Time measurements provide instant feedback about their measurement objects.

This feedback may contain valuable information about the nature of the problem. It also

indicates whether the problem lies in the measurement object in question or somewhere

else and thus helps in locating the problem.

2 Check that the operating state of the LAN interface is up.

If the state of the LAN interface is not up, this means that the interface is not connected.

In this case, alarm 3292 is set. For instructions, see Supervision of a connection fails.

3 Check that the LAN switch is active in the topology.

For instructions on activating a LAN switch, see Activating LAN switches.

4 Check that no changes were made to the LAN topology during the measurement

period.

If changes were made to the LAN topology during the measurement period, repeat the

measurement and take care that this time, no changes are made during the measure-

ment period.

5 Check all relevant connections and cables.

7.10.2 A LAN statistics measurement report indicates problems in the LAN

The information provided in a LAN statistics measurement report indicates not only the

presence or absence of a problem, but also the location of the problem. For further diag-

nosis, different diagnostic tools are used.

Problems reported by LAN statistics can have a variety of causes, such as

• a malfunction in a switch

• a fault in a switch’s configuration



DN0423824

Issue 3-2

99


Id:0900d80580461473

• problems in a unit, or in a program block within a unit, caused by an EMB overload

(or vice versa).

g The above list is not complete; it only gives the most common causes. You may

need to use other diagnostic tools besides LAN statistics in order to pinpoint theproblem.

If a LAN statistics measurement report indicates a heavy load in the LAN, this may be

caused by an unsuitable LAN configuration or by technical problems in an otherwise

well-configured LAN. Consider the following measures:

Steps

1 Increase the capacity of the link.

This usually means changing the LAN topology. For instructions, see Changing and

expanding the LAN topology of the communication network.

2 Check whether the load is caused by a bad connection or a faulty switch that

gives too many traps.

If the problem is caused by an incorrectly configured switch, see The SNMP configura-

tion in the LAN switch is incorrect.

7.11 Network element upgrade changed the configuration

You need to configure topology management again if you detect any of the following

problems:

• Tthere are changes in the activation status of the LAN switch after a network

element upgrade.

• The used topology number has changed.

• The uploaded configuration files are changed back to the default configuration file.

7.11.1 To determine if any changes have occurred

Steps

1 Check the active topology index number (W6G).

ZW6G: <press enter>

/* IDENTIFY TOPOLOGY INDEX:

T1 - T4 (CURRENT IS T1, NETWORK ELEMENT MSCi)

P ... ACTIVATE PREVIOUS TOPOLOGY

R ... RELOAD CURRENT TOPOLOGY */

2 Print out the selected preconfigured LAN topology (W6I).

ZW6I::T=ALL;

For more information, see Selecting the LAN topology .



100 DN0423824

Issue 3-2


Id:0900d80580461473


3 Check the activation status of the LAN switches (W6I).

ZW6I::T=ALL;

For more information, see Activating LAN switches.

4 Type the contents of the configuration file (W6R).

g Configuration file upload is not allowed to EMB switches.


Make sure that all the configurations are up to date. If the printed filename start with

POCC, the uploaded configuration file is missing from the system.

For more information, see Configuring LAN switches.

7.11.2 To make topology management configurations up to date

Steps

1 Activate the correct topology.

For implementing this step, you have the following alternatives:

• Select the topology that is identical to the existing LAN topology of the network

element (W6G).


For more information, see Selecting the LAN topology .

• Copy the topology of the old software build to the new software build.If the topology file had been modified in the of the old software build, you can copy

the file (LFILES/TG4_xxxx.IMG ) only if the version number of the file is the same

in the old build and in the new active build. Select the right topology.

• Modify the preconfigured topology.

If the version number is not the same, you cannot copy the topology from the old

build. You must perform the modifications to the new topology file. For more infor-

mation, see Changing and expanding the LAN topology of the communication

network.

2 Update the current LAN switch password (W6M).

ZW6M:SWU,<unit index>:FCD;

For more information, see Updating the password of a LAN switch.

3 Activate the LAN switches that will be supervised (W6E).


For more information. see Activating LAN switches.

4 Check the configuration of the LAN switch (W6T).


Remember that you cannot establish a Telnet connection to an EMB LAN switch.



DN0423824

Issue 3-2

101


Id:0900d80580461473


ESB26#show running-config

For more information, see Configuring a LAN switch of the communication network

(CNW).

5 Download the configuration file from the LAN switch to the system.

When you are closing the Telnet connection, answer Y to the question DO YOU WANT

TO DOWNLOAD CONFIGURATION FILE FROM LAN SWITCH or enter the command

ZYFM:DCF:SWU,<unit index>;.

6 Type the content of the configuration file (W6R).


7.12 Errors in SNMP, DHCP and TFTP operations

The Integrated LAN administration feature starts listening to the expected ports of

SNMP, DHCP, and TFTP protocols in the working supervising unit when the first IP

address is configured (see Creating TCP/IP connections). Check that it listens to the

right ports if you encounter any of the following problems:

• There are errors in receiving SNMP traps (see Traps not received from a LAN

switch).

• DHCP protocol bootps messages are not responded to the LAN switch (see IP

addressing failure).

• The TFTP file transfer fails (see Configuration file transfer to a LAN switch fails).

Steps

1 Check that all needed TCP/IP connections are configured (WYI).

ZWYI:;

2 Check that the system listens to the needed network IP addresses (QRS).

ZQRS:<WO-EX supervising unit>::;

You get a printout similar to the following example:

BSC3i RUOKE 2008-01-03 11:16:48

UNIT: MCMU-0

Active Internet connections (including servers)

Proto Recv-Q Send-Q Local Address Foreign Address State

udp 0 0 10.12.18.193.snmp-tra *.*

udp 0 0 10.12.18.129.snmp-tra *.*

udp 0 0 10.12.18.65.snmp-tra *.*

udp 0 0 10.12.18.1.snmp-tra *.*

udp 0 0 10.12.19.1.snmp-tra *.*

udp 0 0 10.12.18.193.tftp *.*



Integrated LAN AdministrationIntegrated LAN Administration troubleshooting

udp 0 0 10.12.18.129.tftp *.*

udp 0 0 10.12.18.65.tftp *.*

udp 0 0 10.12.18.1.tftp *.*

udp 0 0 10.12.19.1.tftp *.*

udp 0 0 *.bootps *.*

3 If the needed TCP/IP connections are configured but the system does not listen

to the network IP addresses, preform a switchover to the supervising unit (ZUSC).

ZUSC:<SP-EX supervising unit>:WO,;

4 After few seconds, check that the system listens to the needed network IP

addresses in the new working unit (QRS).

ZQRS:<WO-EX supervising unit>::;

Documents

Integrated LAN Administration DN0423824 Issue 3-2