Nsn Flexi Ns Sgsn-Ahub3-A and Hbrt3-A User Guide

7/24/2019 Nsn Flexi Ns Sgsn-Ahub3-A and Hbrt3-A User Guide

http://slidepdf.com/reader/full/nsn-flexi-ns-sgsn-ahub3-a-and-hbrt3-a-user-guide 1/46

Nokia Siemens Networks Flexi

Network Server - SGSN, Rel.

SG8.0, OperatingDocumentation, v. 1, DRAFT

AHUB3-A and HBRT3-A User Guide

DN0945015

Issue 1-0



2

DN0945015 Issue 1-0


Id:0900d805807e7912

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 2010/12/27. 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.



DN0945015 Issue 1-0

3


Id:0900d805807e7912

Table of ContentsThis document has 46 pages.

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

1 Hub blade AHUB3-A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

1.1 Overview of AHUB3-A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

1.2 Mechanical structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

1.3 Logical structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

2 Rear transitit ion module HBRT3-A. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

2.1 Overview of HBRT3-A rear transition module . . . . . . . . . . . . . . . . . . . . 16

2.2 Mechanical structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

2.3 Logical structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

3 Embedded software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223.1 U-Boot and operating system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

3.2 IPMC subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

3.2.1 IPMC subsystem overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

3.2.2 System event log (SEL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

3.2.3 Sensor data records (SDR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

3.2.4 AHUB3-A FRU information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

3.2.5 HBRT3-A FRU information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

3.2.6 AHUB3-A sensors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

3.2.7 HBRT3-A sensors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

3.3 Ethernet switching software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

3.4 Timing and synchronization software. . . . . . . . . . . . . . . . . . . . . . . . . . . 34

4 Administering the blade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

4.1 Connecting to the blade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

4.2 Rebooting the blade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

5 Monitoring the blade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

5.1 Monitoring port statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

5.2 Enabling and configuring syslog-ng . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

5.3 Viewing SNMP trap statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

6 Managing the blade configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

6.1 Saving a configuration as a startup configuration . . . . . . . . . . . . . . . . . 426.2 Creating a backup configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

6.3 Restoring a backup configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

6.4 Creating configuration scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45



4

DN0945015 Issue 1-0


Id:0900d805807e7912

List of FiguresFigure 1 AHUB3-A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Figure 2 AHUB3-A front panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Figure 3 AHUB3-A logical structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Figure 4 HBRT3-A. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Figure 5 HBRT3-A front panel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Figure 6 HBRT3-A logical structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21



DN0945015 Issue 1-0

5


Id:0900d805807e7912

List of TablesTable 1 AHUB3-A technical data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Table 2 AHUB3-A front panel connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Table 3 AHUB3-A system status LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Table 4 Console port status LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Table 5 FI port status LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Table 6 BI port status LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Table 7 HBRT3-A technical data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Table 8 HBRT3-A front panel connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Table 9 System status LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Table 10 BI status LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Table 11 FI status LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Table 12 AHUB3-A hub blade FRU information . . . . . . . . . . . . . . . . . . . . . . . . . 26

Table 13 HBRT3-A hub blade FRU information . . . . . . . . . . . . . . . . . . . . . . . . . . 28Table 14 AHUB3-A sensors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Table 15 HBRT3-A sensors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31



6

DN0945015 Issue 1-0


Id:0900d805807e7912



DN0945015 Issue 1-0

7

AHUB3-A and HBRT3-A User Guide Summary of changes

Id:0900d8058071dba1

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

issue contains all changes made to previous issues.

Issue 1-0

This is the first issue.



8

DN0945015 Issue 1-0


Id:0900d805807e7921

Hub blade AHUB3-A

1 Hub blade AHUB3-A

1.1 Overview of AHUB3-AThe ATCA hub blade AHUB3-A is the main switch used for internal traffic between

nodes in a network element and, by employing its Layer 3 capability, it can also be used

for routing traffic to/from external networks.

The hub blade provides connections for two types of networks:

• Base interface (BI) switch for the network element’s internal traffic (for communica-

tion between computer nodes)

• Fabric interface (FI) switch for communicating with external networks as well as for

the network element’s internal user data communication (for example, user data

transmitted through AMC modules).

In addition, AHUB3-A provides management interfaces towards shelf manager throughthe base switch, and the hub can also can be used for distributing a reference clock

signal to other ATCA units (the signal can be either received from an external source or

it can be generated locally.

http://general_glossary.pdf/








DN0945015 Issue 1-0

9

AHUB3-A and HBRT3-A User Guide Hub blade AHUB3-A

Id:0900d805807e7921

Figure 1 AHUB3-A

The hub blade is a single-slot wide blade equipped in the two hub slots (slots 8-9) in the

16-slot ATCA shelf. Two hub blades are always required in one shelf for redundancy.

Hub blades on different shelves can be chained together through front panel base inter-

face connectors. Larger configurations may require a separate, second-level Ethernet

switch, depending on the network topology.

Technical data

Width Single slot (6 HP)

Weight 1960 g

Table 1 AHUB3-A technical data



10

DN0945015 Issue 1-0


Id:0900d805807e7921

Hub blade AHUB3-A

Features • Integrated 1GbE base interface

switch (24 ports) and 10GbE fabric

interface switch (20 ports)

• Master clock generator for distributing

synchronized clock signals to other

nodes in the network element.

• PowerPC-based 833 MHz unit com-

puter, using 1GB DDR SDRAM

Table 1 AHUB3-A technical data (Cont.)



DN0945015 Issue 1-0

11

AHUB3-A and HBRT3-A User Guide Hub blade AHUB3-A

Id:0900d805807e7921

Interfaces Front panel interfaces:

• 4 x 1GbE base interface SFP ports,

using optical or electrical transceivers

for, respectively, LC or RJ-45 connec-tors

• 1 x 10GbE base interface XFP port,

using optical transceiver for LC con-

nector

• 3 x 10GbE fabric interface XFP ports,

using optical transceivers for LC con-

nectors

• 1 x serial (RS-232) RJ-45 manage-

ment port to unit computer

• 1 x Fast Ethernet RJ-45 management

port to unit computer

Additional COM ports and USB port on the

front panel are not in use.

Backplane interfaces through base switch:

• 14 x 1GbE base interfaces through

Zone 2 connector

• 2 x 1GbE base interfaces towards

HBRT3-A via Zone 3 connector

• 1 x 1GbE base interface to redundant

hub blade on the shelf

• 2 x Fast Ethernet management inter-

faces to shelf manager via Zone 2

connector

Backplane interfaces through fabricswitch:

• 14 x 10GbE (XAUI) fabric interfaces

through Zone 2 connector

• 2 x 10GbE fabric (XAUI) interfaces

towards HBRT3-A via Zone 3 connec-

tor

Other backplane interfaces:

• 2 x 8 kHz clock synchronization out-

puts/inputs to HBRT3-A via Zone 3

connector

• 19.44 MHz and 8 kHz clock synchro-

nization interfaces via Zone 2 connec-tor

• 1 x update channel interface via Zone

2 connector

• IPMB interface and and power feed

through Zone 1 connector

Table 1 AHUB3-A technical data (Cont.)



12

DN0945015 Issue 1-0


Id:0900d8058063da7d

1.2 Mechanical structure

The mechanical structure of the AHUB3-A complies with the AdvancedTCA specifica-

tions defined by the PCI Industrial Manufacturers Group (PICMG). Slots 8 and 9 in the

16-slot ATCA shelf are reserved for hub blades. Mechanical keying prevents the bladefrom being inserted into a wrong slot.

Front panel

The front panel of AHUB3-A is illustrated in the following figure.

Figure 2 AHUB3-A front panel

-

LMP

SER

Not in use

COM-E ETH

LMP

ETH

Not in use

COM-E USB

XFP 1/1

XFP 1/2

XFP 1/3

XFP 1/5

Link

Port

LinkPort

Link

Port

Link

Port

A P P

Link

PortSFP 1/6

Link

PortSFP 1/7

Link

PortSFP 1/8

Link

PortSFP 1/9

Reset

CLASS 1 LASER PRODUCT

IEC/EN 60825-1

DN0936733

Not in use

COM-E SER

FABRIC

BASE







DN0945015 Issue 1-0

13


Id:0900d8058063da7d

In the AHUB3-A front panel, there is a hot-swap switch, reset push button, and various

connectors and LEDs.

The connectors in AHUB3-A front panel are described in the following table.

The system status LEDs in AHUB3-A front panel are described in the following table.

The console port status LEDs are described in the following table.

Name Description

COM Express USB port Not in use.

COM Express serial port Not in use.

LMP serial port Provides serial access to the local management

processor (LMP) console port through an RJ-45

connector.

COM Express Ethernet port Not in use.

LMP Ethernet maintenance port Blade maintenance port with an RJ-45 connector.

XFP ports Three 10 Gb ports for FI and one for BI switchaccess.

SFP ports Four SFP ports for BI switch access.

Table 2 AHUB3-A front panel connectors

Name and

symbol

Color State Description

Out of service

LED

OOS

Amber Steady amber The blade is out of service.

Off The blade is operating normally.

Power good

LED

PWR

Green Steady green The power is good from all the power

supplies.

Off The power is bad from at least one of the

power supplies, or the blade is powered

off.

Application-specific LED

APP

This LED is not in use.

Hot swap LED

H/S

Blue Steady blue The blade is ready for hot swap.

Blinking blue The blade is being transferred to hot

swap state.

Off The blade is operating normally.

Table 3 AHUB3-A system status LEDs



14

DN0945015 Issue 1-0


Id:0900d8058063da7d

The FI port status LEDs are described in the following table.

The BI port status LEDs are described in the following table.

Name Color State Description

COM Express

port status

Green Not in use.

COM Express

link status

Amber Not in use.

LMP Ethernet

maintenance

port status

Green Steady green The port is enabled.

Off The port is disabled.

LMP Ethernet

maintenance

link status

Amber Blinking amber The link is active.

Off The link is inactive.

Table 4 Console port status LEDs


XFP 1/1-1/3

port statuses

(3 LEDs)



XFP 1/1-1/3

link statuses

(3 LEDs)

Green Steady green The link is up.

Blinking green The link is active.

Off The link is down.

Table 5 FI port status LEDs


XFP 1/5 port

status



XFP 1/5 link

status




SFP 1/6-1/9

port statuses

(4 LEDs)



SFP 1/6-1/9

link statuses

(4 LEDs)




Table 6 BI port status LEDs



DN0945015 Issue 1-0

15


Id:0900d8058063dab0

1.3 Logical structure

Logically, AHUB3-A consists of the following components:

• local management processor (LMP), also referred to as unit computer

• Base Ethernet switch

• Fabric Ethernet switch

• system real time clock (RTC)

• telecom synchronization module

• network timing subsystem (NTS)

• IPMC and ShMC subsystems

• power converters

• front panel connectors and LEDs

• zone 1, 2 and 3 connectors in the back panel

The logical structure is illustrated in the following figure.

Figure 3 AHUB3-A logical structure



16

DN0945015 Issue 1-0


Id:0900d805807e794b

Rear transitition module HBRT3-A

2 Rear transitition module HBRT3-A

2.1 Overview of HBRT3-A rear transition moduleThe HBRT3-A rear transition module provides external base and fabric connectivity as

well as external synchronization connectivity for the AHUB3-A hub blades.

The HBRT3-A is a single-width rear transition module (RTM) which can be equipped into

RTM slots where an AHUB3-A hub blade is located.

Figure 4 HBRT3-A

Width Single slot (6HP)

Weight 500 g

Table 7 HBRT3-A technical data





DN0945015 Issue 1-0

17

AHUB3-A and HBRT3-A User Guide Rear transitition module HBRT3-A

Id:0900d805807e794b

Features • 2 x dual 10Gb PHY elements for converting

between SFP+ and XAUI in fabric interfaces

• 2 x BITS elements for signal framing/deframing

in clock synchronization interfaces

Main interfaces Front panel interfaces:

• 2 x 1GbE SFP ports for base interface, using

optical or electrical transceivers with, respec-

tively, LC or RJ-45 connectors

• 2 x 1GbE/10GbE SFP+ ports for fabric inter-

face, using optical transceivers for LC connec-

tors

The two mid-most fabric ports on the front panel

are not in use

• 2 x SSU/BITS ports for 2.048 / 1.544 MHz

external synchronization input/output, using RJ-

48C (RJ-45) connectors

Backplane interfaces:

• 2 x 1GbE base interfaces towards AHUB3-A via

Zone 3 connector

• 2 x 10GbE fabric interfaces towards AHUB3-A

via Zone 3 connector

• 2 x 8 kHz clock synchronization outputs towards

AHUB3-A via Zone 3 connector

• 1 x 8 kHz or 2.048 / 1.544 Mbit/s clock synchro-

nization input from AHUB3-A via Zone 3 con-

nector

• IPMB interface and power feed through a

paddle board connector

Table 7 HBRT3-A technical data (Cont.)



18

DN0945015 Issue 1-0


Id:0900d8058063e3cb

2.2 Mechanical structure

The mechanical structure of HBRT3-A complies with the AdvancedTCA specifications

defined by the PCI Industrial Manufacturers Group (PICMG).

Front panel

The HBRT3-A front panel is shown in the following figure.

Figure 5 HBRT3-A front panel

In the HBRT3-A front panel, there is a hot-swap latch, a Telco alarm interface, and

several LEDs and connectors.

The HBRT3-A front panel connectors are listed in the following table.

-

FABRIC

BASE

T1/E1

CLASS 1 LASER PRODUCT

IEC/EN 60825-1

SSU/

BITS 1

SSU/

BITS 2

Link

PortSFP+ 3/1

Link

Port

Not in use

SFP+ 3/2

Link

Port

Not in use

SFP+ 3/3

Link

PortSFP+ 3/4

Link

PortSFP 3/5

Link

PortSFP 3/6

APP

DN0936757







DN0945015 Issue 1-0

19


Id:0900d8058063e3cb

The system status LEDs are described in the following table.

The BI status LEDs are described in the following table. There are two LEDs (port and

link status) for each BI port.

Name Description

SSU/BITS (two ports) SSU/BITS interfaces are used for:

• chaining ATCA shelves (if multiple shelves are

used) to syncronize time in the entire system

• connecting the system to an external clock

signal source (NTP server)

SFP+ 1/1-1/4 The SFP+ ports 1/1 and 1/4 are used for FI switch

access. Ports 1/2 and 1/3 are not in use.

SFP 1/5 and 1/6 The SFP ports 1/5 and 1/6 are used for BI switch

access.

Table 8 HBRT3-A front panel connectors

Name and

symbol

Color State Description

Out of service

LED

OOS

Amber Steady amber The RTM is out of service.

Off The RTM is operating normally.

Power good

LED

PWR

Green Steady green The power is good from all power sup-

plies.

Off The power is bad from at least one of the

power supplies.

Application-

specific LED

APP

This LED is not in use.

Hot swap LED

H/S

Blue Steady blue The RTM is ready for hot swap.

Blinking blue The RTM is being transferred to hot

swap state.

Off The RTM is operating normally.

Table 9 System status LEDs



20

DN0945015 Issue 1-0


Id:0900d8058063e3cb

The FI status LEDs are described in the following table. There are two LEDs (port and

link status) for each FI port.

Namel Color State Description

Port status Green

oramber

Steady green The port is enabled.

Steady amber The port is in standby mode.


Link status Green

or

amber

Steady green The 1 Gigabit Ethernet (GbE) copper or

optical link is up.

Steady amber The 10 or 100 Mbit/s Ethernet link is up.

Blinking green The 1 GbE copper or optical link is

active.

Blinking amber The 10 or 100 Mbit/s Ethernet link is

active.


Table 10 BI status LEDs


Port status Green

or

amber

Steady green The port is enabled.

Steady amber The port is in standby mode.


Link status Green

or

amber

Steady green The 10 GbE optical, or 1 GbE copper or

optical link is up.

Steady amber The 10 or 100 Mbit/s Ethernet link is up.

Blinking green The 10 GbE optical, or 1 GbE copper or

optical link is active.

Blinking amber The 10 or 100 Mbit/s Ethernet link is

active.


Table 11 FI status LEDs



DN0945015 Issue 1-0

21


Id:0900d8058063e3d9

2.3 Logical structure

Logically, HBRT3-A consists of the following elements:

• zone 3 connector towards the AHUB3-A

• chassis paddle bd connector towards AHUB3-A for zone 1 and 2 connections

• two T1/E1 framers

• I2C expander

• EEPROM for storing FRU data

• FPGA

• IPMC subsystem

• DC/DC converter

• multiplexers and buffers

• front panel connectors and LEDs

The logical structure is illustrated in the following figure.

Figure 6 HBRT3-A logical structure

HBRT3-A

C h a s s

i s

P a

d d l e B d

T1/E1Framer

LEDDecoder

T1/E1Framer

Dual 10GbPHY

Xfmr &Protect

Xfmr &Protect

RJ48C

QuadSFP+

DualSFP

RJ48C

EEPROM

I C Expander 2

Buf

Buf

Zone3

Mux

2XAUI/SERDES/SGMII

2

2

2

XAUI/SERDES/SGMII

EE

PROM

2

2

4

2

2

LMP I C2

SFP LEDs

Dual 10GbPHY

BASE LED BUS

8 KHz In B

8 KHz In A

8 KHz Out

SPI Bus

Base

Fabric

2

FABRIC LED BUS

NTS

ALT Out

BITS Out

Mux

H8IPMC

FPGA Ejector

& LEDs

Buf

Buf

DCDCConv

Relays DB15OR

Circuit

Hdrs

IButton, SDP & Sensors

Slot ID

IPMB-A

12V A

IPMB-B

12V B

SERDES/SGMII

DN0939657



22

DN0945015 Issue 1-0


Id:0900d8058063e3be

Embedded software

3 Embedded software

3.1 U-Boot and operating systemThe Universal Bootloader (U-Boot) initializes main components of the blade like proces-

sor, memory, serial lines and other hardware. After unit startup, it starts the Wind River

Linux operating system, which resides in boot flash memory and is loaded to random

access memory (RAM). Both the primary and secondary boot flash devices on a unit

contain a copy of the U-Boot image and its environment variables.

The U-Boot version and other software packages installed on a unit can be determined

by viewing the contents of the /etc/versions file from Linux. When the software

image of the unit is upgraded, the U-Boot should be upgraded also to ensure it includes

the most current changes. When U-Boot is upgraded, the unit’s software image and the

U-Boot environment variables are reset to the factory defaults.



DN0945015 Issue 1-0

23


Id:0900d80580660d25

3.2 IPMC subsystem

3.2.1 IPMC subsystem overview

Each blade contains an Intelligent Platform Management Controller (IPMC) subsystem,

which provides the ability to monitor, query, and log system management events on the

blade. The functions of the IPMC subsystem include controlling the blade state, power

supplies, and LEDs, monitoring voltages and temperatures, logging events, and main-

taining information on the blade.

The IPMC subsystem consists of the following components:

• IPM Controller

• EEPROM

• Local voltage and temperature sensors

• Serial interfaces

• Power load control

The IPMC subsystem communicates with the shelf manager through the Intelligent

Platform Management Bus (IPMB). It also stores a Local System Event Log (SEL) and

Sensor Data Records (SDR) which can be used for troubleshooting purposes. In addi-

tion, the EEPROM contains a Field Replaceable Unit (FRU) information storage. The

user can access the information stored in the IPMC subsystem through the system

manager.



24

DN0945015 Issue 1-0


Id:0900d805805f9e9c

3.2.2 System event log (SEL)

The system event log (SEL) stores all IPMI events, such as hot swaps and resets. This

information can be used for troubleshooting. The SEL is stored in an EEPROM

managed by the IPM controller. The SEL can log 447 entries. When it fills up, the oldestevents are deleted. The SEL information is periodically sent to the system manager. The

user can read the local SEL through the system manager.



DN0945015 Issue 1-0

25


Id:0900d805806e2ada

3.2.3 Sensor data records (SDR)

The IPMC subsystem contains sensors for monitoring the payload power, voltages, or

the general health of the field replaceable unit. The power sensors monitor all voltages

of the IPMC power supplies. An alarm is raised if one of the values exceeds the allowedrange. The temperature sensors monitor the temperature of the board and components

as well as the ambient temperature at the blade's backplane. Sensor data record may

also contain information about, for example, the state of the FRU hot swap or software

upgrade.

The user can access the sensor data record through the system manager.



26

DN0945015 Issue 1-0


Id:0900d8058069f31e

3.2.4 AHUB3-A FRU information

FRU information for the AHUB3-A hub blade consists of the fields presented in the table

below.

Information area Contents Description

Board Information area Manufacturing date/time Indicates when the blade was manufac-

tured.

Board manufacturer Manufacturer of the blade

Board product name The off icial, abbreviated product name

of the blade

Board serial number The serial number is in the format

CCYYWWSSSSS, where

• CC = Nokia Siemens Networks-

assigned Factory Code (unique to

each manufacturing plant)

• YY = Year, 2 last digits of the man-

ufacturing year

• WW = Manufacturing week

• SSSSS = running serial number,

uniquely identifies the FRU in

question

Board Nokia Siemens

Networks type number

The C-code: C111968.A01

• C111968 = The unique product

code (C-number)

• A01 = The product revision

NSN PIU ID 0x0D03 (hexadecimal)

Product information

area

Product name Product name defined by manufacturer.

Product part/model number Product part/model number defined by

manufacturer.

Manufacturer name Manufacturer of the blade

Product version Manufacturer product version

Product serial number Manufacturer's serial number for the

product.

FRU file ID bytes The filename for FRU file.

Table 12 AHUB3-A hub blade FRU information





DN0945015 Issue 1-0

27


Id:0900d8058069f31e

Multirecord area PICMG Board point-to point

connectivity record

Connection types supported by the

board's BI and FI interfaces towards the

backplane.OEM SW and FW version

information records

These records contain the version

number, build date, update date for the

following software and firmware:

• IPMC firmware #1

• IPMC firmware #2

• Unit Computer application SW

• FRU Data

OEM CPU information

records • Processor count (number of pro-

cessors installed)

• Processor architecture

•Processor max clock speed

• Installed memory (Memory size in

megabytes)


Table 12 AHUB3-A hub blade FRU information (Cont.)



28

DN0945015 Issue 1-0


Id:0900d8058069f31f

3.2.5 HBRT3-A FRU information

FRU information for the HBRT3-A hub blade consists of the fields presented in the table

below.


Board Information area Manufacturing date/time Indicates when the blade was manufac-

tured.

Board product name The off icial, abbreviated product name

of the blade

Board serial number The serial number is in the format

CCYYWWSSSSS, where

• CC = Nokia Siemens Networks-

assigned Factory Code (unique to

each manufacturing plant)

• YY = Year, 2 last digits of the man-ufacturing year

• WW = Manufacturing week

• SSSSS = running serial number,

uniquely identifies the FRU in

question

Board Nokia Siemens

Networks type number

The C-code: C111974.A01

• C111974 = The unique product

code (C-number)

• A01 = The product revision

NSN PIU ID 0x0D09 (hexadecimal)

Product information

area

Product name Product name defined by manufacturer.

Product part/model number Product part/model number defined by

manufacturer.

Manufacturer name Manufacturer of the blade

Product version Manufacturer product version

Product serial number Manufacturer's serial number for the

product.

FRU file ID bytes The filename for FRU file.

Multirecord area OEM SW and FW version

information records

These records contain the version

number, build date, update date for the

software and firmware of FRU data.

Table 13 HBRT3-A hub blade FRU information





DN0945015 Issue 1-0

29


Id:0900d805806814c7

3.2.6 AHUB3-A sensors

The sensors in AHUB3-A are listed in the following table.

Sensor name Description

ATCA Hot swap Return M0 to M7 ATCA hot-swap states for FRU 0.

COME (COM express)

Hot Swap

Return M0 to M7 ATCA hot-swap states for FRU 1.

RTM Hot swap Return M0 to M7 ATCA hot-swap states for FRU 0.

ATCA IPMB-0 Physical IPMB0 status information as defined in

AdvancedTCA Base Specification.

This sensor checks override state and local status of IMPB

A and B.

Ejector closed This sensor detects whether the ejector latch is open orclosed.

-48 V Absent A This sensor checks presence of power supply A.

-48 V Absent B This sensor checks presence of power supply B.

-48 V Fuse fault This sensor checks whether both fuses A and B are OK.

SEL Overflow This sensor detects SEL overflow.

IPMC WDT (watchdog

timer) RESET

This sensor checks if IPMC watchdog is valid.

HW REV (hardware

revision)

This sensor is not implemented.

+5 V This sensor measures voltage in volts.

IPMC +3.3 V This sensor measures voltage in volts.

+3.3 V This sensor measures voltage in volts.






Inlet Temp This sensor measures temperature in degrees Celsius.

XFP Temp This sensor measures temperature in degrees Celsius.

Fabric Temp This sensor measures temperature in degrees Celsius.

PIM (power input

module) Alarm

This sensosr indicates whether PIM alarm is asserted.

PB (push button) Reset This sensors indicates whether the push button reset is

asserted.

Table 14 AHUB3-A sensors



30

DN0945015 Issue 1-0


Id:0900d805806814c7

IPMB 0 PU Ch A 0: No pull-up

1: Half pull-up

2: Full pull-up

IPMB 0 PU Ch B 0: No pull-up

1: Half pull-up

2: Full pull-up

ComE (COM Express)

Present

0: COM express is present.

1: COM express is not present.

IPMC Watchdog This sensor detects whether the IPMB is reset due to

Watchdog or not.

RTM Present This sensor indicates whether RTM is present.RTM Temp This sensor measures temperature of the RTM in degrees

Celsius.

RTM I2C Ready This sensor detects whether RTM I2C is ready.

RTM Pwr Fail This sensor detects whether RTM power supply is OK.

RTM Eject This sensor detects whether the RTM latch is open or

closed.


Table 14 AHUB3-A sensors (Cont.)



DN0945015 Issue 1-0

31


Id:0900d805806a0d4f

3.2.7 HBRT3-A sensors

The sensors in HBRT3-A are listed in the following table.


ATCA FRU Hot swap Module hot-swap information as defined in AdvancedTCA

Base Specification. Sensor state represents the M-state of

the module.

ATCA physical IPMB This sensor checks override state and local status of IMPB

A and B.

Version change This sensor detects following changes:

• Hardware change detected with associated entity.

• Firmware or software change detected with associated

entity.

• Hardware incompatibility detected with associated

entity.

• Firmware or software incompatibility detected with asso-

ciated entity.

• Entity is of an invalid or unsupported hardware version.

• Entity contains an invalid or unsupported firmware or

software version.

• Hardware change detected with associated entity was

successful.

• Software or firmware change detected with associated

entity was successful.

Ejector closed This sensor detects whether the ejector latch is open or

closed.

Board temp This sensor measures board temperature in degrees

Celsius.

+12 V PEM-A This sensor measures voltage in volts.

+12 V PEM-B This sensor measures voltage in volts.




IPMC Watchdog This sensor detects whether the IPMC is reset due to

Watchdog or not.

SPM Active Indicates that the SPM is active.

RTM Eject ready Indicates if the SCM is finished using the RTM I/O interfaces

and the board can be removed.

Table 15 HBRT3-A sensors



32

DN0945015 Issue 1-0


Id:0900d805806703f0

3.3 Ethernet switching software

AHUB3-A uses two Ethernet switches to implement Base and Fabric interfaces. The

Ethernet switching software supports layer 2 (L2) and layer 3 (L3) switching. Both IPv4

and IPv6 are supported.

Layer 2 switching software

L2 switching (or Ethernet switching) is supported by both Base and Fabric switches in

AHUB3-A. The L2 switching software includes the following protocols and features:

• L2 frame forwarding

• one of the following spanning tree protocols per switch:

– Spanning Tree Protocol (STP)

– Rapid Spanning Tree Protocol (RSTP)

– Multiple Spanning Tree Protocol (MSTP)

• virtual LANs (VLANs)

• Generic Attribute Registration Protocol (GARP), including GARP VLAN Registration

Protocol (GVRP) and GARP Multicast Registration Protocol (GMRP)

• traffic storm control

• denial-of-service (DoS) attack protection

• class-of-service (CoS) queuing

• quality of service with differentiated services (QoS with DiffServ)

• link aggregation groups

• port mirroring

• MAC filtering

• port security

• port filtering • Internet Group Management Protocol (IGMP) snooping

• Link Layer Discovery Protocol (LLDP)

In addition, the following information is maintained for troubleshooting and monitoring

purposes:

• switch-level statistics (including all L2 protocols)

• port-level statistics

• statistics per multicast forwarding database (MFDB)

• syslog

• Simple Network Management Protocol (SNMP) trap statistics

Layer 3 switching software

L3 switching (or IP routing) is supported in the AHUB3-A Fabric switch. The L3 switching

software is fully integrated with the L2 switching software and includes the following pro-

tocols and features:

• port- and VLAN-based routing

• multiple IP addresses per interface

• Address Resolution Protocol (ARP)

• static routing

• Routing Information Protocol (RIP)

• Open Shortest Path First (OSPF)

• Virtual Router Redundancy Protocol (VRRP)



DN0945015 Issue 1-0

33


Id:0900d805806703f0

• route redistribution

• multicast routing

• Internet Group Management Protocol (IGMP)

•Distance Vector Multicast Routing Protocol (DVMRP)



34

DN0945015 Issue 1-0


Id:0900d805806703fa

3.4 Timing and synchronization software

Timing and synchronization software in AHUB3-A is responsible for controlling the

timing and synchronization of the network element. Together with a circuit block, it con-

stitutes the timing and syncronization domain.

Timing and synchronization domain is responsible for providing shelf-internal timing

signal to other units in the shelf. For synchronization between shelves, one shelf is

selected as the master shelf. Synchronization clock signal is received from an external

clock source and distributed to other units in the shelf via the synchronization clock inter-

face in the backplane, and to other shelves via the SSU/BITS interfaces in the HBRT3-

A rear transmission module. The synchronization signal (2.048 MHz) is regenerated in

the Master Clock Generator (MCG) in each hub blade. Configurations of up to three

shelves are supported.



DN0945015 Issue 1-0

35

AHUB3-A and HBRT3-A User Guide Administering the blade

Id:0900d805806607c1

4 Administering the blade

4.1 Connecting to the bladeBefore you start

Make sure that you have the following equipment available:

• a field engineering workstation (FEWS)

• a 9-pin D-shell to RJ-45 serial cable or an Ethernet cable

Summary

There are two ways to access the AHUB3-A blade: serial connection through the LMP

(unit computer) serial port and Telnet connection throught the LMP Ethernet mainte-

nance port.

Accessing the blade with serial connection

Connect a serial cable between a COM port in the FEWS and the LMP serial port

in the blade front panel.

2 Start a terminal-emulation application on the FEWS with 38400 baud rate, 8 data

bits, no parity, one stop bit, and no hardware or software flow control.

3

Log into the blade.

Use the root user account to login to the blade Linux or the admin account to login tothe blade CLI.

Connecting to the blade with Telnet

Connect an Ethernet cable between the FEWS and the LMP Ethernet maintenance

port in the blade front panel.

2

Configure the FEWS to a subnet IP address 10.0.0.x (not 10.0.0.1) and set the

netmask to 255.255.255.0.

3 Connect with Telnet to the IP address 10.0.0.1.

4

Log into the blade.

Use the root user account to login to the blade Linux or the admin account to login to

the blade main CLI.

Further information

If you want to switch from Linux shell to main CLI, enter the following Linux command:

mcli



36

DN0945015 Issue 1-0


Id:0900d805806607c1

Administering the blade

If you want to switch from main CLI to Linux shell, enter the following CLI command:

linux-shell

In AHUB3-A there are also separate Ethernet CLIs for managing Base and Fabric

Ethernet switches. You can access these CLIs from the main CLI with the following com-mands:

base-ethernet

fabric-ethernet



DN0945015 Issue 1-0

37


Id:0900d80580660c95

4.2 Rebooting the blade

Summary

The blade can be rebooted either by pressing the reset button in the front panel, or byexecuting the reboot command in the blade Linux.

Rebooting the blade from Linux

Connect to the blade and log in as root user.

2 Reboot the blade.

Enter the following command:

reboot



38

DN0945015 Issue 1-0


Id:0900d805806610c5

Monitoring the blade

5 Monitoring the blade

5.1 Monitoring port statisticsSummary

AHUB3-A and HBRT3-A port statistics can be monitored from the CLI. The statistics

include information on sent and received packets, different packet types and sizes, as

well as erroneous and dropped packets.

Steps

Connect to the blade and log in as admin user.

2 If you want to monitor BI port statistics

Then

Switch to the BI CLI.


base-ethernet

3

If you want to monitor FI port statistics

Then

Switch to the FI CLI.


fabric-ethernet

4

Display the port statuses.

Enter the following CLI command:

show port all

From the output you can see which ports are enabled (EKey and Admin Modes

Enabled). Statistics are only available for enabled ports.

5 Display the port statistics.

Enter the following CLI command:

show interface ethernet <domain/port>

<domain/port> must be one of the values shown in the first column of the output of

the show port all command. The domain values are interpreted as follows:

• 0 (ports in the back panel)

• 1 (ports in the front panel)

• 2 (internal ports)

• 3 (ports in the RTM)

port is a number of an enabled port in the given domain.



DN0945015 Issue 1-0

39


Id:0900d8058067d694

5.2 Enabling and configuring syslog-ng

Summary

Syslog-ng is a standard Linux service, which collects messages from different softwarecomponents and writes the output to a log file. It can be used for monitoring the blade

operation and analyzing fault situations. The module-wide syslog-ng in AHUB3-A is

disabled by default.

When syslog-ng is enabled, the messages are stored by default to the local

/var/log/messages file. However, it is not recommended to use a local file on the

RAM disk for this purpose, because large files can affect the blade operation. Therefore

it is better to configure syslog-ng to use a remote file for storing the messages.

Configuring syslog-ng

Connect to the blade and log in as root user.

2 Open the configuration file /etc/syslog-ng/syslog-ng.conf in a text editor.

3

If you want to configure the syslog-ng message destination to a remote server (recom-

mended)

Then

Add the following two lines to the configuration file.

destination d_remote { <protocol> ("<IP address>"); }

log { source(<message type>); destination (d_remote); }

You must specify the following parameters:

<protocol> specifies the protocol (either TCP or UDP) used for the remote logging.

<IP address> specifies the IP address of the remote server.

<message type> specifies the type of messages (for example s_sys for system mes-

sages) to be redirected to the remote server.

4

If you want to change the local file where the syslog-ng messages are stored

Then

Modify the line starting with ‘destination d_mesg’.

Replace /var/log/messages with the full path and name of the new file.

Further information

The syslog-ng configuration file on the remote server specifies the name and location of

the log file. The remote system’s syslog-ng service must be configured to receive remote

messages. Syslog-ng can be restarted with the following command:

sysklogd -r



40

DN0945015 Issue 1-0


Id:0900d8058067d694

Enabling module-wide syslog-ng


2

Switch to the blade management mode.


blade-mgmt

3

Switch to the configuration mode.


config

4 Enable syslog.


service syslog

5 Exit the configuration mode.


exit

6

Verify that syslog is enabled.Enter the following command:

show service syslog

The output should read:

Service syslog

Enabled Status : enabled

Init File : /etc/init.d/syslog-ng

Conf File : /etc/syslog-ng/syslog-ng.conf

7

Exit the blade management mode.


exit

8

Save the new configuration.


copy system:running-config nvram:startup-config

Further information

If you want to disable syslog, enter the following command in the blade management

mode:

no service syslog



DN0945015 Issue 1-0

41


Id:0900d805806a3095

5.3 Viewing SNMP trap statistics

Summary

SNMP trap statistics can be viewed from the blade CLI. They are displayed as a list ofreceived traps.

Steps

Log into the blade as admin user.

2 If you want to view SNMP trap statistics of BI ports

Then


Enter the following command:base-ethernet

3 If you want to view SNMP trap statistics of FI ports

Then



fabric-ethernet

4

Display the SNMP trap statistics.Enter the folowing command:

show logging traplogs

Expected outcome

The output can be, for example, the following:

Number of Traps Since Last Reset............... 16

Trap Log Capacity.............................. 256

Number of Traps Since Log Last Viewed.......... 0

Log System Up Time Trap

--- ------------------------ ----------------------------------0 6 days 20:22:35 Failed User Login: Unit: 1 User ID:

1 6 days 19:19:58 Multiple Users: Unit: 0 Slot: 3 Port: 1



4 2 days 23:16:32 Link Down: Unit: 0 Slot: 1 Port: 2

5 2 days 23:16:03 Link Down: Unit: 0 Slot: 1 Port: 1





10 2 days 00:55:38 Failed User Login: Unit: 1 User ID: admin11 2 days 00:20:12 Multiple Users: Unit: 0 Slot: 3 Port: 1



42

DN0945015 Issue 1-0


Id:0900d80580698778

Managing the blade configuration

6 Managing the blade configuration

6.1 Saving a configuration as a startup configurationSummary

The AHUB3-A file system is recreated in random access memory (RAM) every time the

blade is rebooted. Therefore, all configuration changes must be saved to permanent

storage in order to preserve them after reboot.

Steps


2 Save the running configuration.





DN0945015 Issue 1-0

43


Id:0900d8058069954c

6.2 Creating a backup configuration

Summary

You can create backups of AHUB3-A configuration and store them to permanentstorage. By default, the backup configuration files are stored to the /etc directory. You

can also choose to copy a backup configuration file to a TFTP server. Backup configu-

ration files can be used later, for example in fault situations, for restoring a previously

active and working configuration.

Steps


2

Create a backup configuration file.


copy system:running-config [tftp://<IP address>/<file name>]

If you use the tftp://<IP address>/<file name> parameter and enter a valid

TFTP server IP address and a file name, the configuration will be stored to the given

TFTP server.

If you do not use this parameter, the configuration file will be stored to the /etc direc-

tory.



44

DN0945015 Issue 1-0


Id:0900d8058069954d

6.3 Restoring a backup configuration

Summary

If the blade operation becomes undesired after some configuration changes, you canrestore a backup configuration, stored to the /etc directory or a TFTP server.

Steps


2 Restore a backup configuration.


copy {/etc/<file name> | tftp://<IP address>/<file name>} \

system:running-configYou must specify the backup file source by using either the /etc/<file name>

parameter (enter an existing configuration file name in the /etc directory), or the

tftp://<IP address>/<file name> parameter (enter a valid TFTP server IP

address and a name of a configuration file stored there).

3

If you want to assign the restored configuration as the startup configuration

Then

Save the running configuration.





DN0945015 Issue 1-0

45


Id:0900d805806a300f

6.4 Creating configuration scripts

Summary

The configuration of the blade can be saved as a text-formatted script file. It is possibleto generate multiple configuration scripts, upload and apply them to one or many hub

blades.

Use the show running-config command to capture the running configuration into a

script. Use the copy command to transfer the configuration script to or from the blade.

For showing the hint on scripting commands, use the script ? command. The hint

contains the most common commands:

apply Applies a configuration script to the switch.

delete Deletes a configuration script file from the switch.

import Imports a plain text configuration script file.

list Lists all configuration script files present on the switch.

show Displays the contents of a configuration script.

validate Validates the commands of a configuration script.

Steps


2

If you want to create a configuration script to the BI switch

Then



base-ethernet

3 If you want to create a configuration script to the FI switch

Then



fabric-ethernet

4 Create a script from the running configuration.


show running-config running-config.scr

Expected outcome

Config script created successfully.

Further information

If you want to change the configuration stored in the script, you can open the sript file in

a text editor and add, delete, or modify the commands. It is also possible to create ascript from scratch by typing commands to a text file and saving it as .scr file.




5 Verify the script file.


script list

Expected outcome

The expected outcome can be as following:

Configuration Script Name Size(Bytes)

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

running-config.scr

3201

1 configuration script(s) found.

1020799 bytes free.

6 Validate the script file.


script validate running-config.scr

7

Apply the script to change the configuration.


script apply running-config.scr

Expected outcome

The outcome should be the following:Are you sure you want to apply the configuration script? (y/n)

Type y to apply the configuration script.

The systems has unsaved changes.Would you like to save them

now? (y/n)

Type y to apply the configuration script.

Further information

To upload the script to TFTP server, use the following command:

copy nvram:script running-config.scr /tftp://<IP address>/running-config.scr

where <IP address> is the IP address of the TFTP server.

To delete the script, use the following command:

script delete running-config.scr

Documents

Nsn Flexi Ns Sgsn-Ahub3-A and Hbrt3-A User Guide