1 1.

BASIC BSC KNOWLEDGE MXBSC HW overview

General concept: ATCA

1.1.1 1.1.1.1

Advanced Telecom Computing Architecture, or AdvancedTCA(ATCA) is a series of industry standard specifications for the next generation of carrier grade communications equipment. As the largest specification effort in PICMG's history and with more than 100 companies participating, AdvancedTCA incorporates the latest trends in high speed interconnect technologies, next generation processors, and improved reliability, manageability and serviceability, resulting in a new blade (board) and chassis (shelf) form factor optimized for communications. AdvancedTCA provides standardized platform architecture for carrier-grade telecommunication applications, with support for carrier-grade features such as NEBS, ETSI, and 99.999% availability. The PICMG 3.X specification is intended to define open architecture modular computing components that can be quickly integrated to deploy high performance services solutions. In PICMIG 3.X document, it presents base requirements: - Mechanicals - System Management - Power Distribution - Power Connector Zone (for Dual -48 VDC power to each Slot) - Rear I/O Access Zone - Data Transport Connector Zone (for System management and switching fabric interconnect) - Shelf Thermal Dissipation - Regulatory Guidelines In one word, ATCA (based on PICMIG specification) have already provided lot of HW related features for telecom product. It saves the effort for HW design.

1.1.1.2

IPMI

In addition to the Gigabit Ethernet switching function and to the TDM switching over Ethernet function, another key function of the MXBSC is the implementation and use of ATCA standards for the low level management of the modules at the shelf level: the IPMI. IPMI is used to control all the ATCA HW entity. This interface is implemented in the ATCA middleplane by two redundant IPM busses (IPMB), which interconnect all the FRUs of a shelf together. The figure below shows the principle of IPMI implementation in an ATCA shelf.

SYSTEM MANAGER

Figure 1 General IPMI implementation in an ATCA shelf

1.1.1.3

High Availability

MXBSC is Carry Grade Equipment. In case of failure, the system must be able to continue processing the same amount of users, after a service interruption of less than 30 seconds. When a software or hardware component is unique for the whole system, redundant behaviour shall be used, allowing keeping the stable calls. Maintenance Reason Hardware failure Protection N+1 hardware redundancy Recovery of faults of centralized units (1+1 redundancy, audit, ) Software failure New software release Data protection and software restart without losing stable calls Future target: keep calls in case of minor software release change (same processing as for software failures) Table 1: Requirements for a Five 9s System

Board SSW OMCP CCP TP GSM

EPS(Equipment Protection Switching) 1+1 1+1 N+1 1+1

Manager ATCA BSC+MXPF SW BSC+MXPF SW BSC+MXPF SW

SMM

1+1

ATCA

External Ethernet Links

OMCP1 TP1

OMCP2

CCP1 TP2 SSW

(duplicated)

Radio Network links

16E1

LIU1 MUX1 LIU16 MUX2

CCP6

16E1

1.1.2 1.1.3 1.1.4 1.1.5 MXBSC Physical architecture

The following figure shows the general hardware architecture of the MXBSC:

1.1.6

Physical address logical address

3 9-7

5 5-3

7 1-2

9 4-6

10

11

12

13

14

13 - 11

8 - 10

12 -14

1U

3U

8U

T P G S M 1 3

T P G S M 1 1

C C P

C C P

C C P

O M C P

S S W

S S W

O M C P

C C P

C C P

C C P

E M P T Y 1 2

E M P T Y 1 4

1 0

Function block Architecture

48 or 60V DC

1 GbE links (2 x RJ45 connectors)

48 or 60V DC

P E M

L I U

L I U

L I U

L I U

L I U

L I U

L I U

L I U

M U X

M U X

L I U

L I U

L I U

L I U

L I U

L I U

L I U

L I U

P E M

External E1 links (16 x sub -D 68 pins connectors)

External E1 Links

O&M + TELECOM E1 Termination Shelf CCP P OMCP P OMCP W TP P TP W CCP N CCP 1

NE1oE

SSW W SSWP
1 Gigabit Ethernet - ATCA Base Interface

1.1.7

Process mapping

Following lists the main characteristics of MxBSC software. - Redundant user plane and control plane - Function splitting between user plane and control plane. - Application process communication is developed based on redundant TCP/IP. - More centralizing on application processing and transmission processing.

V-SCPR

V-OCP

V-DTC(TCH-RM)
Figure 2: Processes Mapping on OMCP.

CMW

TCU TCU TCU CMW V-TCU TCU V-TCU V-TCU V-TCU

Platform service

DTC DTC DTC DTC DTC DTC DTC DTC V-DTC CCP

CPI
Interthreads Communication Bus
SUP Init/SW

Figure 3: Process mapping on CCP

TP-SS7_SLH

CMWP
Platform service

CPI
Interthread comm. bus

TP-Main
Interthread comm. bus

SUP

Init/SW

Configu ration Handler

Fault Manag er Handler

Perf. Param. Handler

HDLC LAPD Handler

HDLC MLPPP Handler

TDM Handler Matrix Framer s Synchr o

QMUX Handler

R/W Bits Alarm Octet Handler

Figure 4: Process Mapping on TPGSM

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16

LIU 1 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16

LIU 2 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32

LIU 3 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48

LIU 4 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64

LIU 5 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80

LIU 6 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96

LIU 7 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112

LIU 8 11 3 11 4 11 5 11 6 11 7 11 8 11 9 12 0 12 1 12 2 12 3 12 4 12 5 12 6 12 7 12 8

LIU 9 LIU 10 129 1 45 130 1 46 131 1 47 132 1 48 133 1 49 134 1 50 135 1 51 136 1 52 137 1 53 138 1 54 139 1 55 140 1 56 141 1 57 142 1 58 143 1 59 144 1 60

LIU 11 LIU 12 LIU 13 LIU 14 LIU 15 LIU 16 161 41 31 21 2 1 162 42 32 22 4 3 163 43 33 23 6 5 164 44 34 24 8 7 165 45 35 25 10 9 166 46 36 26 12 11 167 47 37 27 14 13 168 48 38 28 16 15 169 x 39 29 18 17 170 x 40 30 20 19 171 x 24 18 12 11 172 x 23 17 10 9 173 28 22 16 8 7 174 27 21 15 6 5 175 26 20 14 4 3 176 25 19 13 2 1 1000 800 600 400 - 200

200 - 400 TR X

600 - 1000 TR X

E1 Abis E1 Ater CS

E1 not used E1 Ater PS

Figure 5: 1000 TRX LIU Shelf connections assignment

1.2
1.2.1

Shelf Manager(SMM)
Introduction

The communication between the system manager and the shelf manager is based on: - Remote HPI - Simple Network Management Protocol (SNMP) - Remote Management Control Protocol (RMCP) Two shelf management modules (SMM) are implemented: one active, and one backup for redundancy reasons. The SMM functions are defined as following: - Board power-up - Configuration of the various electronically keyed interfaces within the ATCA shelf: Base interface, Fabric interface, Update interface, Synchronization clock. - Monitors, controls, and assures proper operation of AdvancedTCA boards and other Shelf components, - Watches over the basic health of the system, reports anomalies, and takes corrective action when needed, - Retrieves inventory information and sensor readings as well as receive event reports and failure notifications from boards and other intelligent FRUs, - Perform basic recovery operations such as power cycle or reset of managed entities, - Provides low-level hardware management services to manage the power, cooling, and interconnect resources of a shelf. - Communicates with the System Manager.

200

400

400 TRX

200 TRX

1.2.2 Connection The following table give a list of all the shelf management command. To log in SMM, use the following user name and password: IP address See IP table description in IP address chapter (take 172.17.3.8 as example) User root Pass root Connect method1 If SSW is already configured, telnet 172.17.3.8 via ATCA network(from terminal PC) Connect method2 out of band interface: Direct connect a network cable from terminal PC to SMM Ethernet port: 192.168.x.8(x is the ATCA shelf number) Table 2: SMM connection method

1.2.3

Face plane & LED status

LED Failure (OOS) LED1

Color Red Off

Description The shelf manager board is out of service The shelf manager board is working properly The shelf manager board is operating properly Otherwise The shelf manager board is active The shelf manager board is in the standby mode The shelf manager board is ready to be extracted The shelf manager board is not ready to be extracted. Do not remove the board during this state. Link to backplane Ethernet 1 is available Otherwise

Power (OK)LED2

Green Off

Active (Act) LED 3

Amber Off

Blue (H/S)

Blue Off

Ethernet 2

Green Off

Ethernet 1

Green Off

Link to backplane Ethernet 2 is available Otherwise Link to Ethernet is available Otherwise Active

Ethernet 3

Green Off

Ethernet 4

Yellow

1.3
1.3.1

Switch Board(SSW)
Introduction

The blade basically provides the following features: - Managed 24 port Layer 3 Gigabit switch for base interface - Gigabit Ethernet support for 14 payload slots - 8 base and 1 fabric Gigabit Ethernet uplinks (SFPs) via rear transition module - 15 port unmanaged Layer 2 Gigabit Ethernet switch for fabric interface - ATCA Management Controller (IPMI version 1.5) - SNMP agent for switch management - Option for TDM clock generation and synchronization via CGM module - Designed for NEBS level 3 and ETSI requirements 1.3.2 Connection Connect method1 Connect method2

We can connect to Switch via COM port(need special cable), run Vxworks command. http://172.17.X.10, user:admin, pass:password Table 3: SSW connection method

1.3.3

LED Status and Ethernet LEDs Base interface LEDs connector Reset key

Status and Ethernet LEDs: Name Color Description OOS Red Out of service Red: The blade is outofservice Off: The blade is working properly OK Green Power OK Green: The blade is operating properly Off: Otherwise ACT Amber Active Amber: The blade is active Off: The blade is in the standby mode H/S Blue Blue: The blade is ready to be extracted Off: The blade is not ready to be extracted. Do not remove the board during this state. ETH1 Orange On: Activity Off: No activity Green On: Link up Off: Link down ETH2 S Green 10 BaseT Orange 100 Base Tx ETH2 L Green On: Link up Off: Link down ETH2 A Orange On: Activity Off: No activity

During powerup ST A Red Green ST B Red Green ST C Red Green Orange During operation ST A Green Orange ST B Red Green Orange ST C Red Green Orange

Power good 3 FPGA initialized Power good 2 Power good of all DC/DCs Power good 1 Power up command from IPMC Power good 1 and power up command from IPMC are indicated Indicates general activity via UART between both boards. No activity Activity Indicates the status at the Ethernet heartbeat connection. Heartbeat connection is dead Active Warning Indicates the status at the UART heartbeat connection. Heartbeat connection is dead Active Warning

ST LED status during startup: During SW startup ST A ST B ST C Red Red Red Orange Red Red Orange Orange Red Orange Orange Orange Green Orange Orange Green Green Orange Green Green Green Red Orange Green During SW shutdown/reset Red Orange Red Red Red Orange Red Orange Red

description Software start Hardware initialization Hardware initialization Hardware initialization Hardware initialization Hardware initialization Hardware initialization done Software initialization (from now on, I/O via console is possible)

Boot loader only! Hardware shutdown Hardware shutdown

Base Interface LEDs meaning Color Description Green Port performed linkup but no activity Orange Port performed linkup and there is activity

1.4
1.4.1

OMCP/CCP
Introduction

The PENT/ATCA-715 is an AdvancedTCA compliant single blade computer offering high processing performance. Four on-board PMC sites, redundant GBit Ethernet connection to the AdvancedTCA Base interface and standard I/O interfaces make it ideal for telecommunication and datacom applications. Important features are: -Pentium M processor with up to 1.8 GHz speed -Up to four GByte main memory DDR2 SDRAM with ECC protection -Designed for PICMG 3.0 and 3.1 compliant systems -Redundant AdvancedTCA Base interfacea -Four on-board 64-bit/100MHz PCI-X compliant PMC slots -Two USB 2.0 interfaces at face plate -Optional on-board CompactFlash and 2.5 inch hard diska -Support for Windows 2000/2003 and Carrier Grade Linux Ed. 3.1 -Intelligent Platform Management Controller (IPMC) compliant to IPMI V.1.5 with redundant IPMB support -Support for four PMC Modules with Telecom clocking synchronization -Different accessory kits, for example: >Rear Transition Modules (RTMs) >CMC debug module >Hard disk accessory kit >Cable accessory kits 1.4.2 Connection method Connect method1 Login SMM, then - telnet localhost 4503 to connect to OMCP1 - telnet localhost 4504 to connect to OMCP2 - telnet localhost 4505 to connect to CCP1 450X x=logical number Connect method2 From BSC terminal PC, if BSC terminal is connected to SSW1: - telnet 172.17.3.30 to connect to OMCP1 - telnet 172.17.3.40 to connect to OMCP2 if BSC terminal is connected to SSW2: - telnet 172.18.3.30 to connect to OMCP1 - telnet 172.18.3.40 to connect to OMCP2 /common/bsc/SCPRDISK SCPR disk MXBSC

/common/bsc/RI /common/bsc/backup /common/bsc/OCPRDISK /var/log/MX/trace/daily /var/log/MX/trace/realtime /var/log/MX/trace

RI files generated by CM used for fast restore OCPR disk daily trace realtime trace non-VOS trace

MXBSC MXBSC MXBSC MXBSC MXBSC MXBSC+MXPF

1.5
1.5.1

PC card
Introduction

The PC card(A100) is a general purpose device to provide for all of the functions that may not be included by the other Field Replaceable Units (FRUs). The PC Card alarm board: - Contains the Shelf FRU Information Store - Contains rotary switches for setting SGAs - Provides HA, SGA and configuration bit inputs -Provides interfaces for up to two filter switches and four temperature sensors, for example, air inlet - Provides Telco alarming, that is, relay outputs for major, minor, and critical errors and up to four opto-solated inputs - Visualizes the states and alarms via LEDs on the front panel

1.5.2

LEDs and connecter Failure (OOS) LED Red On: The ATCAA100 alarm board is outofservice Red blinking: The shelf FRU information is invalid and no board is powered Off: The ATCAA100 alarm board is working properly On: The IPMC has initialized properly and is ready Off: Otherwise On steady: The ATCAA100 alarm board is ready to be extracted

OK LED Blue (H/S)

Green

Blue

1.6

TP

B10 MXBSC supports TP v1/v2/v3 boards. 1.6.1 TPv1 Introduction

All TPGSM v1 board functions were grouped in the following modules: Configuration Management Fault Manager Application Alarms Management and Notifications Performance Parameters Management TDM Management TDM switching, E1 Alarms, TDM Clock Management HDLC-LAPD Handler Management SS7 Configuration Management

ML-PPP Management Qmux Handler Management R/W Bits Handling Module General Utilities Common Buffer Pool, Timers Management, Trace Routines, etc. - not treated by this document.

We want to distinguish between several domains for TPGSM v1 operation by BSC application. 1) OBC application: Everything related to the telecom services of the TPGSM: Switching, SS7, HDLC, A-Trunks, E1. And management functions : Configuration manager, Fault manager, Performance manager.(running with Pentium M). The TPGSM Services domain is tightly integrated with the BSC application. The messages are exchanged using the CMW communication system. It covers: Configuration Fault management Performance Management Telecom services

2) nE1oE module: part which is in charge of routing the user traffic between the TPGSM board and the MUX board. The nE1oE module is managed using the nE1oE agent delivered with the MX_PF software and located on the OMCP. NE1oE stands for NE1 Over Ethernet: its role is to ensure the transport of data carried by E1 links over a Giga Ethernet network between MUX (LIUs) and TP/GPs. The NE1oE service covers: Configuration Role Assignment Takeover Reset Fault Management Start - Stop Software Change Hardware Management PM Reporting Traces/Logs Service 3) MX_PF: Everything related to the software running on the board, independently of what that software does. This is mostly for supervision and control. No PM should be necessary for that domain. And at that level, the configuration is not controlled by BSC application. The MxPF Services domain covers. Task management (mostly process management). SW management (ex: SW inventory services) HW management (board status, hardware notification, remote inventory, INIT, Reset).

TPGSM fault notification, subscribe/publish services.

These services are common to every board. This means that those services are accessed by the same API for TPGSM/OMCP/CCP boards. 4) HardWare : Everything related to the HW aspects of the board, as seen through the ATCA shelf manager. Likewise, this should concern only supervision and control. The HW management domain (Interface1) is managed through Endur-X/IPMI. This means that those services are accessed by the same API as for OMCP/CCP/SSW boards. The interface 1 covers: basic board operations (Power On, Reset, Power Off), HW events (HW failures). Indeed it means that the OBC part of the TPGSM board is treated like any other element of the ATCA shelf for these generic services.

1.6.2

TP v2/v3 Introduction

With the introduction of High-speed Signalling Link(HSL) and IP transport in B10, a new generation of TPGSM board is necessary which is called TPGSM v2/v3. TPGSM v2/v3 is an extension of the existing TPGSM with a new daughter board and all existing functions are kept. This daughter board is called TPIP, its main function is to handle the IP stacks, it has IP over E1 termination for up to 252 E1 links. TPGSMv2/v3 is compatible with MxBSC B9. It can be inserted in an MxBSC B9 platform without the need to change BSC SW. TPGSMv2/v3 will support the IP routing function and forwarding function, and also support the (ML)PPP connection management. In addition to the services supported by TPGSM v1, TPGSM v 2 also supports the following handlers as a part of TP_MAIN process:

E1 switch handler: It is in charge of the communication between the E1 switch driver

and the TPGSM application. Especially, it is in charge of the configuration of the E1 switch and of the fault that may occur on the E1 switch

IP routing handler: It is in charge of the communication between the IP forwarding function

and the TPGSM application. It manages the routing table configuration, the PM counters, the faults, and the DHCP extractions.

Abis/Ater MLPPP hander: It manages the establishment, release and supervision of the
(ML)PPP connection 1.6.3 Connection method

Connect method1 Use one serial cable which connect the PC COM port to monitor TP startup Baud rate 38400

Connect method2

For connection to NE1OE part of TP ,refer to chapter 4.2.19 From BSC terminal PC, if BSC terminal is connected to SSW1: - telnet 172.17.3.130 to connect to TP1 - telnet 172.17.3.110 to connect to TP2 if BSC terminal is connected to SSW2: - telnet 172.18.3.130 to connect to TP1 - telnet 172.18.3.110 to connect to TP2

1.7
1.7.1

MUX board/LIU board/PEM board

Introduction

As defined in the MX Hardware Architecture and Principles, the LIU Shelf will have the following external interfaces: Up to 256 Physical E1 links termination Two 1000 Base T Ethernet links 2 Redundant DC power supply Debug interfaces.

The LIU Shelf will be structured with following internal entities: 1.7.2 One mechanical shelf including an interconnection backplane Up to 16 LIU boards gathering 1 to 16 physical links each Two MUX boards interfacing the TP GSM through the Gigabit Ethernet switches Two Power Entry Modules (PEM) Cooling Fans if needed.

Function of each board

The LIU board shall ensure the following functions: Connection of up to 16 physical E1 interfaces (Tx / Rx) Multiplexing and de-multiplexing of 16 E1 to/from the two MUX boards LIU synchronization Communication with the MUX boards for LIU board configuration and supervision Detection of LOS on any E1 connected and in use Storage of Remote Inventory data Power up from each PEM (POL implemented on LIU board) Hot insertion.

The MUX board shall ensure the following functions:

 Multiplexing and de-multiplexing of up to 16 E1 streams (16 E1 each) from the LIU boards Control Plane and User Plane management to/from the GbE link Configuration management and supervision of the LIU boards 1 GbE interface

NE1oE packing/unpacking to/from up to 32 physical entities (TPGSM boards, GP boards) Communication with the other MUX Board (Master/Slave indication) Debug interface Storage of Remote Inventory datas (Refer to Appendix 1) Power up from each PEM. Hot insertion.

The Power Entry Modules shall ensure the following functions: Power supply connection DC power filtering -48 V to 12 V DC/DC conversion

LIU Shelf
Transf Transf Transf Transf

LIU

LIU board PLD

PEM

PEM

MX Platform
ATCA Shelf

LIU

MUX Board GbE

Physical E1 Accesses

NE1oE
Transf Transf Transf Transf

SSWW

LIU

LIU board MUX Board PLD GbE

LIU

NE1oE

SSWP

1.7.3

Introduction

In MXBSC, some trace are enable automatic, some other trace need manually to open them. The table show all the trace available for MXBSC Board Trace type Enable Comments OMCP/CCP/TP core dump file Automatic - VOS core, nonVOS core and selfRelient core files=/var/log/MX/dump/ -

OMCP/CCP/TP OMCP/CCP/TP OMCP/CCP OMCP/CCP OMCP/CCP OMCP OMCP/CCP TP/OMCP/CCP

Linux system log, SelfRelient log NTP log VCE realtime trace(SCPR,OCPR, TCU,DTC,TSC) VCE daily trace MxPF current log VCE Interactive trace Non-VCE trace(CMW/CMWP, EIM,CPI, SWMGT,TP_MAIN, server_PH, SLH )

Automatic Automatic Automatic Request from trace terminal Request from trace terminal Automatic Request from trace terminal Manually active from each board

dmesg command to see the startup result all the log file located in /var/log/ selfRelient log file are stored in /var/log/MX/trace/srk/ /var/log/MX/logs/NTP trace file will be finally stored in OMCP disk /var/log/MX/trace/realtime/ trace file will be finally be stored in OMCP disk: /var/log/MX/trace/daily/ trace file will be finally be stored in OMCP disk: /var/log/MX/logs/ trace file will be finally be send to trace facility terminal, use du trace file will be finally be stored in OMCP disk: /var/log/MX/trace/

1.7.4

VLAN config

Without VLAN, all the communication will be broadcast to all the board, it will generate additional load for each board to receive the message it dos not interested. In MXBSC, tagged VLAN is used to separate IP internal/external traffic and pure Ethernet telecom traffic. Fixed values are used for the VLAN-Ids: o o o o o No tag for VLAN1 (internal and external IP traffic). This is the default tag used for non-tagged frames. Tag22 for VLAN22 (External O&M traffic through the SSW1) Tag23 for VLAN23 (External O&M traffic through the SSW2) Tag3 for VLAN3 (telecom traffic coming from Mux1) Tag4 for VLAN4 (telecom traffic coming from Mux2).

In the switch, only the assignment of VLAN ID to physical ports is needed. That means for each physical port describe the list of managed VLAN Ids (contains one ID for port based VLAN, several for tagged VLAN).

The purpose of Tag3 and Tag4 is to send only telecom and supervision (based on broadcast) traffic on right switch ports to not impact other switch ports that are not concerned by this Ethernet traffic. The purpose of Tag22 and Tag23 is: To separate the external O&M traffic from internal traffic

Isolate BSC and MFS internal subnet in case of rack-shared configuration and just let the O&M traffic to be shared between BSC and MFS