MCBSC O&M

mcBSC Operations and Maintenance
Multicontroller Base Station Controller
1 © Nokia Siemens Networks RN23823EN30GLA1

mcBSC Operations & Maintenance
Content
mcBSC Alarm Administration
mcBSC Interface Interrogation
BTS Restart Phase Monitoring in mcBSC
mcBSC Packet Control Unit Interrogation
mcBSC Redundancy Concept Interrogation
Replacing HW Units

Content
Replacing HW Units

Alarm Urgency Level
Alarm Class Description
Alarm which is not cancelled and which only informs about a fault
Notice event without printing out the urgency class
Disturbance is used for informing about temporary disturbance

Disturbance situations, which means informing about a short failure event that
does not have any permanent effect on service
An alarm or transient disturbance marked with one asterisk

* does not usually require user actions
An alarm marked with two asterisks does not threaten the operation of
the system. However, if the fault occurs during working hours, it must
** be corrected at once. If the fault occurs outside working hours, it can
be corrected the next day
Alarms marked with three asterisks require immediate action from the
user. An alarm like this is set when the system has become faulty to
*** the extent that some essential functionality of the system has
stopped, or is in danger of stopping. The maintenance personnel must
take immediate action

Structure of Long Alarm Printout
Alarm Event Type (COMM, QUAL, PROC, ENVIR)
Network Element
Printout Type (CANCEL, DISTUR,NOTICE) Alarm Object Recovery Info
Consecutive Number Alarm Object location Info Date & Time

18:52:56.91
( 032) MCBSC32 1A001- 00-1 SWITCH *--------* 2009-03-26

** ALARM PCUM-0
3695 UNIT TYPE HAS NOT ENOUGH MODULE LEVEL REDUNDANCY
RCXPRO OMU
MCBC 3D 2
Alarm Text
Alarm Issuer
Alarm Number Computer Sending Alarm
Urgency Level Supplementary Info Fields (PIU type/Rack No/Subrack No/SlotNo.)

Alarm Reference
• Alarm manual is the main • Alarm number
reference for alarm handling – Notices (0 – 999)
• It is available on – Disturbances (1000 – 1999)
– NED, as part of BSC RG30 – Failure printout (2000 – 3999)
Operating Documentation – Diagnosis reports (3700 – 3999)
– Alarm Monitor – Base Station alarms (7000 – 7999)
(Alarm Monitor)
(NED)
Alarm Reference
Alarm number
and text
Full description
Additional
information
Instruction in
handling the alarm
Cancelling
information
mcBSC Alarm Handling
Alarm System Administration Menu
mcBSC MCBSC32 2013-05-10 22:23:52
ALARM SYSTEM ADMINISTRATION
? ..... DISPLAY MENU

B ..... BLOCKED ALARMS HANDLING
C ..... ALARM CANCELLING
E ..... ERROR RATIO COUNTER HANDLING
Alarm System
H ..... ALARM HISTORY HANDLING Administration Command
L ..... LAMP PANEL HANDLING
O ..... ALARM OPERATING INSTRUCTION HANDLING
Class Menu
P ..... ALARM PARAMETERS HANDLING
Q ..... EXTERNAL ALARM CONNECTIONS HANDLING
R ..... ALARM SYSTEM RULEBASE HANDLING
T ..... ALARM PRINTING HANDLING
Z; .... RETURN TO MAIN LEVEL
ALARM SYSTEM ADMINISTRATION COMMAND <A__>

<
mcBSC MCBSC32 2013-05-20 22:26:11
ALARM HISTORY HANDLING COMMANDS
? ..... DISPLAY MENU Alarm History Handling

O: ..... PRINT ALARMS CURRENTLY ON
P: ..... PRINT ALARM HISTORY
Command Group Menu
Z; ..... RETURN TO MAIN LEVEL Active Alarms: ZAHO
ALARM HISTORY HANDLING COMMAND <AH_><
History:ZAHP

Content
Replacing HW Units

mcBSC Interfaces
mcBSC External Interfaces

mcBSC Interfaces
External & Internal Interfaces
Multicontroller BSC
MCMU OMU
TRXSIG,
OMUSIG
BCXU
SIGTRAN Aif
MSS
ETPSIG
FlexiEDGE/ AoIP
ETMA
mrBTS PCUSIG MGW
ETPSIG
P-Abis (PS+CS)
EEP
Gb
ETME PCUM
PEP SGSN

mcBSC Interfaces
ETME interfaces
•ETME unit supports the following logical interfaces/links:
– Packet Abis over Ethernet interface
▪ Packet Abis link towards the IP enabled BCF
▪ Used for transmitting CS and PS U-plane IP packets between BCF and ETM.
– PEP link
▪ PCU-ETP Protocol link (over Ethernet) between PCUM and ETME
▪ Used for transmitting PS U-plane IP packets between PCUM and ETME
– EEP link
▪ ETP-ETP Protocol link (over Ethernet) between ETMA and ETME
▪ Used for transmitting CS U-plane IP packets between ETMA and ETME
– ETPSIG-M
▪ O&M / management plane link (over Ethernet) between the GW BCXU and ETME
▪ Used for management purposes (alarms, supervision, diagnostics, recovery, restoration, and
configuration)
▪ Also used in controlled ETME switchover when the (WO -> SP) ETME unit warms-up the (SP ->
WO) ETME unit
– ETPSIG-C:
▪ Telecom / control plane link between the BCXUs and ETME
▪ There is a separate ETPSIG-C link to each BCXU and it is used for CS call control purposes

mcBSC Interfaces
ETMA interfaces
•ETMA unit supports the following logical interfaces/links:
– A over IP interface
▪ A over IP link towards MGW in ‘TC in MGW’ configuration.
▪ Used for transmitting CS U-plane IP packets between MGW and ETMA
– EEP link
▪ ETP-ETP Protocol link (over Ethernet) between ETME and ETMA
▪ Used for transmitting CS U-plane IP packets between ETME and ETMA
– ETPSIG-M
▪ O&M / management plane link (over Ethernet) between the GW BCXU and ETMA
configuration)
– ETPSIG-C
▪ Telecom / control plane link between the BCXUs and ETMA. There is a separate ETPSIG-C link
to each BCXU and it is used for CS call control purposes
– mcTC
▪ Used to transmit DL CS U-plane IP packets from mcETPC

mcBSC Interfaces
BCXU interfaces
•BCXU unit supports the following logical interfaces/links:
– SIGTRAN interface
▪ Signaling transport over IP (SIGTRAN): standardized way to carry SS7 signaling over an
Internet Protocol (IP) backbone
– OMUSIG interface
▪ O&M traffic of BTS
– TRXSIG interface
▪ Control traffic of TRXs in BTS
– ETPSIG-M /PCUSIG
▪ O&M / management plane link (over Ethernet) between the GW BCXU and ETMA /PCUM
configuration)
– ETPSIG-C
▪ Telecom / control plane link between the BCXUs and ETMA. There is a separate ETPSIG-C link
to each BCXU and it is used for CS call control purposes

mcBSC Interfaces
PCUM interfaces
•PCUM unit supports the following logical interfaces/links:
– ETPSIG-M /PCUSIG
▪ O&M / management plane link (over Ethernet) between the GW BCXU and ETMA /PCUM
configuration)
– Gb over IP
▪ The Gb over IP interface is the packet data user interface between the BSC and the SGSN
▪ UDP/IP stack used as a transport method in the transmission network
OMU interfaces
– O&M over IP
▪ The O&M interface (Q3 interface) is the interface between NetAct and the mcBSC
▪ The implementation of this interface is based on the O&M framework of the ITU-T and the
International Standards Organization (ISO)
▪ Physical interface used is Ethernet

mcBSC internal ETMA, ETME, PCUM interfaces
ETPSIG-M, ETPSIG-C, PCUSIG interrogation
• Interrogating ETPSIG-M, ETPSIG-C, PCUSIG: ZD2I
D2I:
1. ETPSIG-M
/* SPECIFY IUA SIGNALING TYPE: • Management plane
for ETMA, ETME
M ... ETPSIG-M
C ... ETPSIG-C 2. ETPSIG-C
P ... PCUSIG • Control plane for
ETMA, ETME
DEFAULT IS ALL ETPSIG TYPE*/
3. PCUSIG
D2I:P:;
mcBSC MCBSC32 2013-05-15 21:13:08 • Management plane
INTERROGATE IUA MESSAGING CONFIGURATION for PCUM
UNIT CONN-TYPE SIG-TYPE GW UNIT D-CHN
--------- --------- -------- -------- -----
PCUM-0 NORMAL PCUSIG BCXU-0 64
BCXU-0 IP ADDR: 10.0.1.10
PCUM-0 IP ADDR: 10.0.1.20
PCUM-2 NORMAL PCUSIG BCXU-0 66 PCUSIG interfaces
between PCUMs &
PCUM-3 NORMAL PCUSIG BCXU-0 67 Gateway BCXUs
COMMAND EXECUTED

• Interrogating ETPSIG-M: ZD2I
D2I:M:;
mcBSC MCBSC32 2013-05-20 21:20:11
INTERROGATE IUA MESSAGING CONFIGURATION

--------- --------- -------- -------- -----
ETME-0 NORMAL ETPSIG-M BCXU-0 69
ETME-0 IP ADDR: 10.0.1.70
ETME-1 NORMAL ETPSIG-M BCXU-0 70
ETPSIG-M interfaces
ETMA-0 NORMAL ETPSIG-M BCXU-0 71 between ETMAs, ETMEs
BCXU-0 IP ADDR: 10.0.1.10 & Gateway BCXUs
ETMA-0 IP ADDR: 10.0.1.80
ETMA-1 NORMAL ETPSIG-M BCXU-0 72
ETMA-1 IP ADDR: 10.0.1.81
COMMAND EXECUTED

• Interrogating ETPSIG-C : ZD2I
< D2I:C:;
LOADING PROGRAM VERSION 2.11-0
mcBSC MCBSC32 2013-05-20 21:22:17

--------- --------- -------- -------- -----
ETME-0 NORMAL ETPSIG-C BCXU-0 73
BCXU-0 IP ADDR: 10.0.20.10
ETMA-1 NORMAL ETPSIG-C BCXU-0 74
BCXU-0 IP ADDR: 10.0.20.10 ETPSIG-C interfaces
ETMA-1 IP ADDR: 10.0.1.101
between ETMAs, ETMEs
BCXU-0 IP ADDR: 10.0.20.10 & Gateway BCXUs
ETMA-0 IP ADDR: 10.0.1.100
ETME-0 NORMAL ETPSIG-C BCXU-1 76
ETMA-1 IP ADDR: 10.0.1.101
ETMA-0 IP ADDR: 10.0.1.100
COMMAND EXECUTED

mcBSC Interfaces
A over IP Interface
• The AoIP interface between the MSS/MGW and the mcBSC (or mcTC depending on network
scenario) is implemented according to the 3GPP standards
• Together with the signaling over IP (SIGTRAN), it offers an all IP transport towards the core
network
• The 3GPP has standardized AoIP for Rel-8, including two basic alternatives:
1. Transcoder located in the base station system (BSS) network ( PCM coded speech
(G7.11) is sent over IP stack) allowing optimized transcoder resource allocation within
the BSS network
2. Transcoder located in core network (BSS is sending coded frames, for example GSM
codecs like AMR, over A interface using IP stack)

mcBSC Interfaces
A over IP Interface interrogation
• Interrogating ETMA network interfaces (AoIP): ZQRI
QRI:ETMA;
mcBSC MCBSC32 2013-05-15 20:48:03
INTERROGATING NETWORK INTERFACE DATA
UNIT ADMIN ADDR

INTERFACE STATE MTU ATTR IP ADDRESS
------------ ----- ----- -------- ---------------------------------------------
ETMA-0
IFETH0 UP 1500 PIDM (10.0.1.80/24)
LIC (10.0.1.100/24)
IFETH1 UP 1500
VLAN23 UP 1500 L (10.0.3.20/25) ETMA,0 working
EEP AoIP userplane: vlan xx46
->IFETH0 23 0/0
VLAN3246 UP 1500 L (10.2.32.68/27)
->IFETH1 3246 0/0
ETMA-1
IFETH0 UP 1500 PIDM (10.0.1.81/24)
LIC (10.0.1.101/24)
IFETH1 UP 1500
VLAN23 UP 1500 L (10.0.3.21/25) ETMA,1 working
EEP AoIP userplane: vlan xx46
->IFETH0 23 0/0
VLAN3246 UP 1500 L (10.2.32.69/27)
->IFETH1 3246 0/0
COMMAND EXECUTED

mcBSC Interfaces
A over IP Interface interrogation
• Interrogating ETMA default gateways (AoIP): ZQKB
QKB:ETMA;
mcBSC MCBSC32 2013-05-20 20:53:51
INTERROGATED STATIC ROUTES

GATEWAY ADDRESS ROUTE
UNIT ->DESTINATION TYPE ETME IP address in the
NBR EEP vlan
---------------------- -------------------------------------------- ----- --
---
ETMA-0 10.0.3.10 LOG 4 BTS subnetwork IP &
->10.2.33.128/27 mask
ETMA-1 10.0.3.10 LOG 5
->10.2.33.128/27 Site Switch > Core (MGW)
ETMA-0 10.2.32.65 LOG 7
->DEFAULT ROUTE
ETMA-1 10.2.32.65 LOG 8
->DEFAULT ROUTE
COMMAND EXECUTED

mcBSC Interfaces
SIGTRAN – Signaling for the A interface
BSC MSS
BSSAP BSSAP
SCCP SCCP
M3UA M3UA
SIGTRAN
SCTP SCTP
IP IP
Ethernet Ethernet
SIGTRAN defines a standardized way of carrying any SS7 Signaling over IP

networks

mcBSC Interfaces
SCTP Association set
MSS (Server) (up to 16 associations) mcBSC (Client)
BSU 0 BCXU 0
IP BCXU 1
BSU 1
BSU 2 BCXU 2
SCTP Associations
An SCTP Association is identified by the computer unit (BCXU) and destination

address. Only one association allowed per computer unit.
A “SIGTRAN link" consists of one SCTP Association set.
Signaling Link Set can only contain one "SIGTRAN link".
mcBSC Interfaces
• Interrogating Association sets: ZOYI
mcBSC MCBSC32 2013-05-19 01:30:43
INTERROGATING ASSOCIATION SET DATA
ASSOCIATION SET NAME ASSOC SET ID SCTP USER ROLE

-------------------- ------------ --------- -------- Association Set
MSSKERNEL 0 M3UA CLIENT
COMMAND EXECUTED
SCTP Association set

MSS (Server) (up to 16 associations)
mcBSC (Client)
BSU 0 BCXU 0
BSU 1 IP BCXU 1
BSU 2 BCXU 2
SCTP Associations
mcBSC Interfaces
• Interrogating Association sets: ZOYI
mcBSC MCBSC32 2013-05-16 01:30:35
INTERROGATING ASSOCIATION SET DATA
ASSOCIATION SET NAME ASSOC SET ID SCTP USER ROLE

-------------------- ------------ --------- --------
MSSKERNEL 0 M3UA CLIENT
ASSOC. ASSOC ID PARAMETER SET

IND UNIT IN UNIT NAME STATE
--- ------- --------- ---------------- --------------------
0 BCXU-0 1 SS7 ASP-ACTIVE
SOURCE ADDRESS 1 . . . . . : 10.2.32.196

SOURCE ADDRESS 2 . . . . . : 10.2.32.228
Association in
SOURCE PORT . . . . . . . : EPHEMERAL Association Set
PRIMARY DEST. ADDRESS . . : 10.20.209.132/28
SECONDARY DEST. ADDRESS . : 10.20.209.148/28
DESTINATION PORT . . . . . : 2905
DATA STREAM COUNT . . . . : 16
SPECIFICATION VERSION . . : 1.0 (RFC)

TRAFFIC MODE . . . . . . . : LOAD-SHARE
ASP MESSAGES . . . . . . . : YES
REGISTRATION REQUEST . . . : YES
SSNM MESSAGES BROADCAST . : NO
NETWORK APPEARANCE . . . . : 12
ASP MESSAGES IN IPSP . . . : NO
ROUTING CONTEXT . . . . . : ---
FIRST DATA STREAM NUMBER . : 1
TACK ......................: 2 SECONDS

M3UA HB.INTERVAL...........: 15 SECONDS
ACTIVATION DELAY...........: 0 SECONDS
COMMAND EXECUTED

mcBSC Interfaces
• Interrogating M3UA signaling link (L3): ZNET
mcBSC MCBSC32 2013-05-16 01:18:39
NETWORK ITEM STATES
SIGNALLING ROUTE SETS
NETWORK: NA1
SIGNALLING ROUTES
SP CODE H/D NAME STATE IN ROUTE SET STATE INFO
================== ================ ===== ========================== ==========
0350/00848 BSC32 OWN SIGNALLING POINT AS SIGNALLING END POINT Signaling Route Set
0DB6/03510 MSSK AV 0DB6/03510 AV-EX
SIGNALLING LINK SETS
NET SP CODE H/D LINK SET STATE SIGNALLING LINKS IN LINK SET
=== ================== =================== ===== =============================
NA1 0DB6/03510 16 MSSK AV 0 Signaling Link Set
LINK TEST NOT ALLOWED
SIGNALLING LINKS
M3UA BASED LINKS

================
M3UA ASSOCIATION LINK
LINK LINK SET SET STATE
==== ===================== =========== ====== M3UA signaling link
0 16 MSSK 0 AV-EX
COMMAND EXECUTED

mcBSC Interfaces
Gb Interface Identifiers (IP)
BSC
BSSGP BVCI BSSGP Virtual Connection Identifier

NSEI Network Service Entity
Network Service PSEI Packet Network Service Entity
control part NS-VL Network Service Virtual Connection Identifier
UDP LPNBR Local User Datagram Protocol Port Number

RPNBR Remote User Datagram Protocol Port
Number
IP RIP Remote IP address
RHOST Remote Host Name (If DNS exists)
L2
L1

mcBSC Interfaces
Gb IP Interface example with PCP & multiGb
SGSN2
NSVLI 52103 NSEI 52103
NSEI 52103 NRI:73 Rip:10.16.153.144 RPNBR
71 52103 PGI:1
LPNBR 52103 68
BSC21 RPNBR 49999 65
Rip:10.16.153.145 RPNBR
52103
PRE:Y (Dynamic) 64
Rip:10.16.144.75
PSEI:00
Gb Interface 1
PCUM 5
PCUM 6 Mutlpoint Gb
PCU pooling
NSVLI 52104
NSEI 52104 Gb Interface 2
LPNBR 52104
RPNBR 49999 NRI:47 SGSN60
PRE:Y (Dynamic)
Rip:10.16.144.76
PAPU 15
NSEI 52104
Rip:10.16.153.144 RPNBR
52104
Rip:10.16.153.145 RPNBR
52104

mcBSC Interfaces
Gb IP Interface Interrogation
• Interrogating PSEI and NSEI parameters: ZFXL , ZFXI
mcBSC MCBSC32 2013-05-16 01:10:02 mcBSC MCBSC32 2013-05-16 01:12:22
PACKET SERVICE ENTITY DATA NETWORK SERVICE VIRTUAL LINK PARAMETERS:
PSE-00 PSE-00 NSE-01818

====== ================
PS_SGSN_LOAD_BALANCING: NORMAL ROUND ROBIN LOCAL UDP PORT: 50000

NSE STATUS: TRAFFIC ALLOWED
PSE NRI MASK: 1111111111 NSE PFC MODE: ON
NSE NRI LIST (BINARY/DECIMAL):
PSEI WITH ONE PCU NSE NRI MASK: 1111111111
ATTACHED NSE(S) TO PSE: STATIC CONFIGURED NS-VL(S):
NSEI OP REMOTE REMOTE

---------------------------------------------------------- ID NAME STATE RDW RSW IP ADDRESS UDP PORT
----------- ----- ---------- ----- --- --- --------------- --------
01818 01818 SGSNKERNEL WO-EX 010 010 10.20.210.133 50005
ATTACHED PCU(S) TO PSE:

ID REMOTE HOST NAME
PCU PCU PCU OBJECT PCU UP ----- ----------------
ID INDEX STATE TO DATE 01818
--- ----- ----------- -------
00 00 WORKING Y COMMAND EXECUTED
COMMAND EXECUTED

mcBSC Interface Parameters
Modifying RNW parameters
Start
Lock Network Object (BTS, TRX)
Modify Parameter
Influence Yes
on involved Network Modify involved NE (eg. MSS,BTS)
Elements
No
Unlock Network Object (BTS, TRX)
End

mcBSC Packet Abis Interface
MML commands for operating the RNW packet abis sites
ZEQ...
BTS 1 BTS 2
BSC
TRX 1 TRX 3
ZEE...
TRX 2 TRX 4
ZER...
BCF 1
TRXSIG / BCFSIG ZEF... BTS Power

ETME Control
ZDWQ
ZQR... SCTP ASSOCIATIONS TRX 5 ZEU...
ZQK... ZOY...
TRX 6 BTS
-Adjacencies
BTS SW ZEA...
ZEW... BTS
-Handover Control
ZEH...

RNW – BCF site Interrogation
• Interrogating the BCF site: ZEFO
mcBSC MCBSC32 2013-05-15 21:33:12 PACKET ABIS CONGESTION CONTROL ....................(PACC)... 0 (NOT IN USE)
BU1 ABIS THROUGHPUT THRESHOLD .....................(BU1).... 75%
BASE CONTROL FUNCTION BCF-0001 DATA BU2 ABIS THROUGHPUT THRESHOLD .....................(BU2).... 90%
SITE TYPE ............................ M - MULTIRADIO PACKET LOSS IN ETHERNET ON DL ABIS PL1 THRESHOLD ..(PL1).... 14
ADMINISTRATIVE STATE ................. UNLOCKED PACKET LOSS IN ETHERNET ON DL ABIS PL2 THRESHOLD ..(PL2).... 28
OPERATIONAL STATE .................... WO DOWNLINK COMMITTED INFORMATION RATE ...............(DLCIR).. 0
MAXIMUM ETP MULTIPLEXING WAIT TIME ................(MEMWT).. 2
ABIS INTERFACE CONNECTION TYPE ....... 2(PACKET ABIS OVER ETHERNET) MAXIMUM BTS MULTIPLEXING WAIT TIME ................(MBMWT).. 2
D-CHANNEL LINK SET 1 ............. MR1OM WO-EX MAXIMUM MULTIPLEXING PACKET SIZE ..................(MMPS)... 300
RX DIFFERENCE LIMIT ..........(RXDL).. 10 dB ETME HARDWARE ID ..................................(ETMEID). 0
BTS BATTERY BACKUP PROCEDURE .(BBU)... ALL IPSEC ENABLED .....................................(IPSEC).. 0 (NOT IN USE)
TRX SHUTDOWN TIMER ...........(NTIM).. 0 min BCF UP TO DATE ............................................. T
TRX SHUTDOWN TIMER2 ..........(NTIM2). 0 min PACKET DELAY VARIATION.............................(PDV).... 5000 microsec
TRX SHUTDOWN TIMER3 ..........(NTIM3). 0 min PACKET ABIS OVER SATELLITE IN USE........................... F
BCCH TRX SHUTDOWN TIMER ......(BTIM).. 0 min BTS C/U-PLANE IP ADDRESS AND SUBNET MASK LENGTH ...........
MASTER CLOCK BCF .............(MCBCF). -- 010.002.033.151/27
CLOCK SOURCE .................(CS).... -- BTS M-PLANE IP ADDRESS AND SUBNET MASK LENGTH .............
010.002.033.151/27
SYNCHRONIZATION ENABLED ......(SENA).. F
USED CS UDP MUX PORT ..............................(CSMUXP). 49154
SYNCHRONIZATION MODE .........(SM).... UNSYNCH
USED PS UDP MUX PORT ..............................(PSMUXP). 49554
EXTERNAL 1PPS SYNC SOURCE ....(EPPS).. 0 (DISABLED)
MCPA POWER POOLING ENABLED ...(MCPAEN) 0 (DISABLED)
AUTOMATIC UNLOCK ALLOWED .....(AU).... 0
MCPA POWER POOLING BCF STATUS (MCPABS) 0 (DISABLED)
PACKET ABIS BCF GROUP ID .....(PABGID) 65535
ETHERNET RING/PATH PROTECTION ..(ERPP) 0 (DISABLED)
FACCH LAPDM T200 .............(T200F). 0 (BCF PREDEFINED VALUES)
QOS AWARE ETHERNET SWITCH USAGE.(QOSA) 0 (DISABLED)
SDCCH LAPDM T200 .............(T200S). 0 (BCF PREDEFINED VALUES)
ABIS OVER IP ETHERNET USAGE ..(TRS1).. 0 (NOT IN USE)
BTS UNDER THIS BCF ARE:
TRS ABIS GROOMING USAGE ......(TRS3).. 0 (NOT IN USE)
SEG-0001
TRS LOOP PROTECTION USAGE ....(TRS4).. 0 (NOT IN USE)
BTS-0001 SECTOR-001 ..... UNLOCKED
PACKET TRS E1/T1 USAGE .......(TRS5).. 0 (NOT IN USE)
SEG-0003
ETHERNET OAM ENABLE...........(EOAME) 0 (DISABLED)
20W POWER LICENCE USAGE............... 0 (20W)
SEG-0002
RF SHARING STATE...................... 0 (NOT SHARED)
ETP BCF ID ........................................(EBID)... 0
VLAN ID ...........................................(VLANID). 3248
COMMAND EXECUTED
UPLINK TRAFFIC SHAPING ............................(ULTS)... 0
UL COMMITTED INFORMATION RATE .....................(ULCIR).. 0
UL COMMITTED BURST SIZE ...........................(ULCBS).. 1522
RNW – BTS / SEG Interrogation
• Interrogating the BTS/SEG (cell) : ZEQO
EQO:BTS=1; LOCATION AREA ID.........................(LAI)
MOBILE COUNTRY CODE...................(MCC)... 244
mcBSC MCBSC32 2013-05-20 21:06:41 MOBILE NETWORK CODE...................(MNC)... 06
LOCATION AREA CODE....................(LAC)... 01755
BTS IDENTIFICATION PARAMETERS :
=============================== BTS HOPPING MODE.........................(HOP).... N
UNDERLAY BTS HOPPING MODE................(UHOP)... N
SEG-0001 ANTENNA HOPPING..........................(AHOP)... N
BCF-0001 BTS-0001
------------------------------------- MOBILE ALLOCATION FREQUENCY LIST......(MAL).... -
BTS ADMINISTRATIVE STATE ... UNLOCKED UNDERLAY MOBILE ALLOC FREQ LIST.......(UMAL)... -
BTS OPERATIONAL STATE ...... WO DFCA MOBILE ALLOCATION FREQUENCY LISTS(DMAL)... CS: -
PS: -
CELL IDENTITY............................(CI)..... 10400 DFCA UNSYNCHRONIZED MODE MA FREQ LIST.(DUMAL).. -
FREQUENCY BAND IN USE....................(BAND)... 900
HOPPING SEQUENCE NUMBER 1.............(HSN1)... 0
BS IDENTITY CODE.........................(BSIC) HOPPING SEQUENCE NUMBER 2.............(HSN2)... 0
UNDERLAY HOPPING SEQUENCE NUMBER......(UHSN)... 0
NETWORK COLOUR CODE...................(NCC)... 0
BTS COLOUR CODE.......................(BCC)... 0 COMMAND EXECUTED

RNW – TRX Interrogation
• Interrogating the TRX: ZERO
mcBSC MCBSC32 2013-05-20 21:24:14 TRX RF POWER -10000 mW NUMBER OF TRX RF POWER LEVELS 16
TRANSCEIVER DATA TRX MCPA PORT ID 0 TRX MCPA POSITION 0

TRX MCPA NUMBER 0
ADM.STATE OP.STATE
-------------------------------------- D-CH TELECOM LINK SET 2 MR1T1
BCF-0001 UNLOCKED WO
SEG-0001 RTSL PCM-TSL SUB_TSL TYPE I.LEV ADM.STATE OP.STATE CH.STATUS
BTS-0001 UNLOCKED WO ----------------------------------------------------------------------------
TRX-001 EDGE UNLOCKED WO --
BCXU-0 0 - - MBCCHC - UNLOCKED WO
1 - - TCHF 0 UNLOCKED WO ID
GTRX Y (EDGE) BB_UNIT EDGE 2 - - TCHF 0 UNLOCKED WO ID
ETRX N HRS Y PREF P 3 - - TCHF 0 UNLOCKED WO ID
DFCA N 4 - - TCHF 0 UNLOCKED WO ID
5 - - TCHF 0 UNLOCKED WO ID
FREQ 40 TSC 0 FRT 0 (REGULAR) LEV N (NOT 6 - - TCHF 0 UNLOCKED WO ID
USED) 7 - - TCHF 0 UNLOCKED WO ID
DAL N (NOT USED) LEVD N (NOT TRANSCEIVER HAS NO INTERFERING CELLS

USED)
DDU INDEPENDENT SDG - COMMAND EXECUTED
RFHA Y

RNW - Packet Abis Interface Lapd links & Associations
•Interrogating Packet Abis SCTP associations: ZOYV •Interrogating Packet Abis LAPD links: ZDWQ
OYV:IUA:; ZDWQ;
mcBSC MCBSC32 2013-05-20 00:46:25 INTERROGATING ABIS D-CHANNEL DATA
INTERROGATING SCTP ASSOCIATION DATA DATA OF ABIS D-CHANNEL
SCTP ASSOCIATION ASSOC SCTP PARAMETER SET INTERF STREAM HOST

NAME IND UNIT USER ROLE NAME STATE NAME NUM ID SAPI TEI ASSOCIATION NAME NUMBER UNIT STATE
---------------- ----- ------- ----- ------ ---------------- ------------- ----- ----- ------ ---- --- ---------------- ------ ------ -----
MR1OM 0 BCXU-0 IUA SERVER AFAST ASP-ACTIVE MR1OM 1 256 62 1 MR1OM 0 BCXU-0 WO-EX
MR1T1 2 BCXU-0 IUA SERVER AFAST ASP-ACTIVE MR1T1 2 257 0 1 MR1T1 0 BCXU-0 WO-EX
COMMAND EXECUTED COMMAND EXECUTED

SCTP ASSOCIATION ASSOC SCTP PARAMETER SET SCTP ASSOCIATION ASSOC SCTP PARAMETER SET
NAME IND UNIT USER ROLE NAME STATE NAME IND UNIT USER ROLE NAME STATE
---------------- ----- ------- ----- ------ ---------------- ---------- ---------------- ----- ------- ----- ------ ---------------- ----------
MR1OM 0 BCXU-0 IUA SERVER AFAST ASP-ACTIVE MR1T1 2 BCXU-0 IUA SERVER AFAST ASP-ACTIVE
SOURCE ADDRESS 1 . . . . . . . : 10.2.33.68 SOURCE ADDRESS 1 . . . . . . . : 10.2.33.36

SOURCE ADDRESS 2 . . . . . . . : SOURCE ADDRESS 2 . . . . . . . :
SOURCE PORT . . . . . . . . . : 49152 SOURCE PORT . . . . . . . . . : 49153
PRIMARY DEST. ADDRESS . . . . : 10.2.33.151/27 PRIMARY DEST. ADDRESS . . . . : 10.2.33.151/27
SECONDARY DEST. ADDRESS . . . : SECONDARY DEST. ADDRESS . . . :
DESTINATION PORT . . . . . . . : 49152 DESTINATION PORT . . . . . . . : 49153
MAX. DATA STREAM COUNT . . . . : 4 MAX. DATA STREAM COUNT . . . . : 4

SPECIFICATION VERSION . . . . : 1 SPECIFICATION VERSION . . . . : 1

Content
Replacing HW Units

mcBSC BTS Restart Phase Monitoring
BCF restart
BCF TRX OPERATION PHASE FILE STAT TIME
001 Pending BTS OMU STARTED ............ 00000 16:09:12

001 OMU RESET BTS OMU STARTED ............ 00000 16:09:43
001 OMU RESET DOWNLOAD STARTED ............ 00000 16:09:44
001 OMU RESET DOWNLOADING MF BTS_S300.048 00000 16:09:44
001 OMU RESET DOWNLOADING AF OMU_S300.045 00000 16:09:45
001 OMU RESET DOWNLOADING AF HWD_S300.026 00000 16:11:12
001 OMU RESET DOWNLOADING AF FUC_S300.045 00000 16:11:14
001 OMU RESET DOWNLOADING AF DSP_S300.048 00000 16:12:29
001 OMU RESET DOWNLOADING AF CFG_S300.049 00000 16:12:38
001 OMU RESET DL COMPLETED ............ 00000 16:12:38
001 OMU RESET VER REQ RECEIVED ............ 00000 16:12:50
001 OMU RESET CONF REQ RECEIVED ............ 00000 16:12:52
001 OMU RESET CONF DATA SENT ............ 00000 16:12:53
001 OMU RESET CONF COMPLETED ............ 00000 16:14:59
001 OMU RESET SW SAVE STARTED ............ 00000 16:15:00
001 OMU RESET SW SAVE COMPLETED ............ 00000 16:16:11
001 OMU RESET OPERAT COMPETED ............ 00000 16:16:12

macro.

Exercise: Monitoring the BCF Start-up
• Load the Service Terminal extension

RPHASESX
• Start Restart Phase Monitoring for all sites
• Restart one or more sites and observe the
restart Phases
• Start Restart Phase Monitoring for one site
• Restart the BCF and observe the restart
Phases
• Analyse the phase order when reseting the
BCF

macro.

Exercise: Monitoring the BCF Start-up
• From MML command, go to Service Terminal environment
ZDDS;
• Load extention RPHASESX from hardisk
ZLE:1,RPHASESX
• Monitor the restart phase of BCF
Z1DC:258
BCF number
Continues Mode
Command to display
BCF state phase

Content
Replacing HW Units

mcBSC Packet Control Unit - PCUM
Operating states of PCUM
Main state Sub state PCU States comments

DX DX
recovery recovery
WO WO-EX Working, •GW BCXU exists
WO-RE configuring •PCUM has hosting signaling BCXU-PCUM association
Restarting created.
•PCUMs which are not in WO-state, do not have hosting
signaling unit.
SP SP-EX Not relevant •GW BCXU exists
SP-UP (Technically, there is SP-UP working state for a moment
SP-RE although no warming would performed)
TE TE-EX Not relevant •GW BCXU exists
SE SE-OU Not relevant •GW BCXU not needed
SE-NH

PCUM units, indexes, addresses
• Interrogating PCUM units, indexes, addresses: ZUSI, ZWTI
mcBSC MCBSC32 2013-05-14 16:29:45
WORKING STATE OF UNITS

UNIT PHYS STATE LOCATION INFO
PCUM-0 1400 WO-EX MCBC-0 BCXU-0 -
PCUM-1 1401 WO-EX MCBC-0 BCXU-0 -
PCUM-2 1404 SP-EX MCBC-1 BCXU-0 IDLE
TOTAL OF 5 UNITS
COMMAND EXECUTED
READING DATA FROM DATABASE ...
PIU TYPE INDEX LOC UNIT SEN ITI

-------- ----- ------------------- ---------- ------------------ --------------
BOC_A 0 1A001-00-01-AIC-04 PCUM-0 FM110400446 C111723.A1A
TOTAL OF 5 PLUG-IN UNITS
COMMAND EXECUTED

PCUMs network interface interrogation
• Interrogating PCUM network interfaces: ZQRI
mcBSC DX220-LAB 2013-05-17 17:02:10
INTERROGATING NETWORK INTERFACE DATA
UNIT ADMIN ADDR

INTERFACE STATE MTU ATTR IP ADDRESS
------------ ----- ----- -------- ---------------------------------------------
PCUM-0
IFETH0 UP 1500 PDM (10.0.20.12/24)
IFETH1 UP 1500
VLAN24 UP 1500 L (10.0.24.1/24)
PEP Working
->IFETH0 24 0/0 PCUM IP’s
VLAN449 UP 1500 L (10.31.249.132/26)
GB
->IFETH1 449 0/0
PCUM-1
IFETH0 UP 1500 PDM (10.0.20.13/24)
IFETH1 UP 1500
VLAN24 UP 1500 L (10.0.24.2/24)
Spare
PEP PCUM IP’s
->IFETH0 24 0/0
VLAN449 UP 1500
->IFETH1 449 0/0

BCXU Roles for the PCUM
• Hosting signaling unit (BCSU or BCXU)
– The BCSU or BCXU, to which PCUM is logically connected
– The term is comparable with the term “controlling BCSU” i.e. BCSU into which
the PCU PIU is equipped in the legacy BSC
• Gateway (GW) BCSU or BCXU
– The BCSU or BCXU, which has the post office service, via which the PCUM
receives its PCUSIG messages
• BCSU or BCXU can have a role of (from PCUM viewpoint)

– Hosting signaling unit
– Gateway
– Both Hosting signaling unit and Gateway
– Neither Hosting signaling unit nor Gateway

mcPCUSIG protocol stack GW BCSU
• mcPCUSIG protocol stack between GW BCXU and PCUM
– The same protocol stack is used for ETPSIG
mcPCUSIG
Modified IUA
UDP
IP
Ethernet L2
Ethernet L1

PCUSIG messaging interface between GW BCXU and
PCUM
• Interrogating PCUSIG messaging interface between GW BCXU and PCUM: ZD2I
D2I:P::PCUM,;
mcBSC MCBSC32 2013-05-10 16:16:20

--------- --------- -------- -------- -----
COMMAND EXECUTED

PCUSIG interface creation between GW BCXU and PCUM
1. User creates gateway BCXU unit and PCUM unit with ZWTU MML command
2. User configures IP addresses for gateway BCXU and PCUM with ZQRN MML
command
3. User configures messaging interface configuration with ZD2C MML
• Example: ZD2C:P:BCXU,1::PCUM,0;
4. PCUM’s DHCP client sends DHCP discovery to DHCP server
5. PCUM’s DMX post office establishes DMX messaging connection to the gateway
BCXU

Hosting signaling BCXU and PCUM association creation
• Interrogating host signaling BCXU and PCUM association: ZD3I
D3I:PCUM,::;
mcBSC MCBSC32 2013-05-14 16:27:40
INTERROGATE LOGICAL PCU ASSOCIATION CONFIGURATION
HOST UNIT PCUM

--------- -------
BCXU-0 PCUM-1
BCXU-0 PCUM-0
COMMAND EXECUTED
1. User connects hosting signaling BCXU and PCUM with ZD3C MML
▪ Example: ZD3C:PCUM,0:BCXU,1:;
▪ Command is given only to those BCXU/PCUMs, which will be moved to WO-EX
state
2. Platform creates automatically a logical PCU index for PCUM.
3. Platform changes state of connected BCXU and PCUM from SP to WO
4. Platform sends a notification to application about hosting signaling BCXU-PCUM
association creation

Hosting signaling BCXU and PCUM association deletion
1. User disconnects hosting signalling BCXU and PCUM, with ZD3D MML
• Example: ZD3D:PCUM,0:BCXU,1:;
• PCUM can not be in WO-EX state
2. Platform SW inquires DX O&M if deletion of association is ok
3. DX O&M checks if PCUM has configuration (RNW/Gb/PEP link)
• If it exists, association deletion is cancelled
4. Platform deletes the PCUM’s logical PCU index and logical IP addresses
5. Platform changes state of the disconnected PCUMs from WO to SP (PCUM is restarted)
6. Platform sends a notification to application about hosting signalling BCXU-PCUM
association deletion

BCXU switchover – same BCXU unit as GW and Host
Signaling unit
Old hosting sign.

BCXU#0
WO-EX->SP-EX - Hosting signaling BCXU changes
Unit/GW PCUM#0 - GW BCXU changes
WO-EX - PCUM doesn’t change
New hosting sign.
Unit/GW
BCXU#1
SP-EX->WO-EX
Hosting signaling BCXU/PCUM association: Before: After:
PCUSIG: Before: After:

Hosting signaling BCXU switchover- different BCXU units
as GW and hosting signaling unit
Old hosting sign.

BCXU#0
unit WO-EX->SP-EX
- Hosting signaling BCXU changes

BCXU#1 PCUM#0 - GW BCXU doesn’t change
New hosting sign. WO-EX - PCUM doesn’t change
Unit SP-EX->WO-EX
GW
BCXU#2
WO-EX

PCUM switchover – Same BCXU unit as GW and Hosting
signaling unit
BCXU#0 PCUM#0 - Hosting signaling BCXU doesn’t change

WO-EX WO-EX->SP-EX - Physical PCUM associated to hosting signaling
BCXU changes
- Old and New WO-EX PCUM has the same GW
BCXU
PCUM#1
SP-EX->WO-EX

PCUM switchover – Different BCXU unit as GW and
Hosting signaling unit
BCXU#0 PCUM#0
WO-EX WO-EX->SP-EX - Hosting signaling BCXU does not change
- Physical PCUM associated to hosting signaling
BCXU changes
-Old and New WO-EX PCUM has own GW BCXUs
BCXU#1 PCUM#1
WO-EX SP-EX->WO-EX

BCXU Switchover
• PCUM#0 has only GW BCXU since it’s state is SP-EX
• PCUM#1 has different BCXU units as GW and hosting signaling BCXU
• PCUM#2 has the same BCXU unit as GW and hosting signaling BCXU
BCXU#0 PCUM#0 GW: BCXU#0->BCXU#1

WO-EX->SP-EX SP-EX
PCUM#1 Hosting signaling unit:

BCXU#1 WO-EX BCXU#0->BCXU#1
SP-EX->WO-EX
GW/hosting signaling unit:

BCXU#2 PCUM#2 BCXU#0->BCXU#1
WO-EX
WO-EX

Limitation for amount of PCUM/PCUs per hosting
signaling BCSU/BCXU and gateway BCSU/BCXU
• If amount of PCUMs/PCUs per hosting signaling or GW BCS(X)U is exceeded
ALARM 3693 is triggered: TOO MANY PCUS CONFIGURED TO BCSU OR
BCXU
• Objective: inform the operator that the 'recommended' limit has been exceeded
• S/A mcBSC:
– Eleven (11) PCUMs per hosting signaling BCXU
– Fourteen (14) PCUMs per Gateway BCXU Host
BCXU
PCUM
Host
BCXU
PCUM
GW
… BCXU
PCUM
GW
BCXU
mcBSC BCXU – PCUM relationships
BCXU – PCUM relationships & PCUM vs PCU2 comparison
• PCU2-E is physically attached to Host BCSU

• PCUM needs logical association with Host BCSU or BCXU
• PCU2-E and PCUM needs to be associated with GW BCSU or BCXU
• PCU2-E is identified by BCSU-ID & PCU ID (0 to 15)

• PCUM is identified by PCU ID (…)
• PCU2-E follows BCSU redundancy scheme

• PCUM has independent n+m redundancy( one or more spares) (only PCUM can
backup PCUM)
• PCU Pool may contain mixture of PCU2-E and PCUM (RG30 EP1 combined
configuration)

mcBSC ETME – PCUM relationships
ETME - PCU relationships & ETME/ETPE comparison
• Up to 11 PCUM can be connected on one ETME (ETP unit in mcBSC)
• ETPE is identified by ETP Group index
• ETME is identified by mcETP index
• ETPE may have 2N redundancy scheme
• ETME has N+1 redundancy scheme (N+M; one or more spares)
– Ongoing calls survives in a controlled switchover of active ETME unit
– Ongoing calls can be cleared in case of a fault of ETME or in case of a forced state change
• PCUM performance is in the same level as that of PCU2-E in Packet Abis configuration (e.g.
number of supported RTSLs is 1024, Gb throughput, RTT, restart time)
• Some exceptions:
• Maximum number of cells, BTSs and TRXs is 550 per PCUM
• Object id range for BCFs, BTSs, segments and TRXs is 4400
• Maximum number of BCFs in ETME (1100) is supported in PCUM (in PEP) as well.
• Performance of 8 AI cores scaled down accordingly (6 DSPs in PCU2-E)
• ETME supports 30 VLANs in external interface (towards BCF)
• UDP ports 6000 is used for Inter-PCU LAN, 9900 is used for PCUSIG and 65535 is used
for PEP. These cannot be used on Gb

Content
Replacing HW Units

mcBSC Redundancy Concept
Redundancy Models in mcBSC
Functional Unit Redundancy principle

MCMU 2N
OMU None
BCXU N+2
PCUM N+M
ETME N+M
ETMA SN+
HDD 2N
PTUM 1+1

Redundancy rules
• In legacy DX200 the HW defines unit configuration and therefore the redundancy
rules
– Functional units have CPU and preprocessors
• In mcBSC/BCN HW is different then DX200 HW
– Identical BOC-A HW for PCUM, ETME and ETMA
– Identical BJC-A HW for OMU, MCMU and BCXU
– Functional Units are configured on SW, HW does not limit the configuration
• Certain rules need to be obeyed to ensure sufficient redundancy
– Module mother board has no redundancy – module level redundancy needed but
without SP modules
• Main rule for each functional unit type :
– There has to be at least as many SP units in other modules as is the maximum
number of WO units in any module

Redundancy of Functional units
• N+M redundancy is applied to PCUMs and ETMEs
• For a given group of N active units there is a set of M backup units
• The backup units are not paired with the active units as in the 2N scheme, but
any backup unit may replace a failed active unit
• The spare unit(s) is (are) kept in cold standby, which means that
synchronization of the spare unit is performed during the switchover procedure
• There is no upper limit for the number of backup units, but in practice as many
spare units in the spare module as there are active units in one module
• SN+ redundancy is applied to ETMAs
• SN+ is also called 'Load sharing', and it means that within a group of active
units, the traffic of a unit which fails is redistributed between the units which
remain active
• Usually the total traffic handling capacity of a set of units applying SN+ is
dimensioned to exceed the expected amount of user traffic by at least the
capacity offered by one unit
• 1+1 redundancy is applied to PTUM
• Two active units performing a similar task and this duplication allows one unit
to fail without disrupting the service

ETME / ETMA Redundancy
ETME Redundancy
• N+1 replaceable Redundancy model is used in ETME
• There is one or more spare ETME unit for many working ETME units
• Ongoing calls survives in a controlled switchover of active ETME unit
• Ongoing calls can be cleared in case of a fault of ETME or in case of a
forced state change
ETMA Redundancy
• SN+ load sharing group redundancy model is used in ETMA
• Normally all ETMA units are in WO-EX state
• DX call control allocates resources based on availability and load of
ETMA units

Redundancy rules - example
m b b p p a e o b b p p p p e a
w w w s w w w w w w w w w w w w
Module 1 Module 3a
HDD BSAC
PCUM-SP
MCMU
PCUM
PCUM
PCUM
PCUM
PCUM
BCXU
BCXU
ETMA
BCXU
BCXU
ETMA
ETME
ETME
OMU
m b b p p p e a b b p p p p e a
s s s s s s s s w w w w w w w w
HDD-spBSAC-sp
Module 2 Module 3b
MCMU-SP
PCUM-SP
PCUM-SP
PCUM-SP
BCXU-SP
BCXU-SP
ETMA-SP
ETME-SP
PCUM
PCUM
PCUM
PCUM
BCXU
BCXU
ETMA
ETME
• If any of the modules fail there is sufficient number of PS unit capacity on
remaining modules
– Max amount: MCMU: 1, BCXU: 2, PCUM: 4, ETME: 1, ETMA: 1*
▪ *) ETMA has no real SP unit but additional WO capacity for 1 unit
– Excluding OMU as in BSC3i/ FlexiBSC

Redundancy rules – example (invalid)
m b b p p a e o b b p p p e e a
w w w s w w w w w w w w w w w w
Module 1 Module 3a
HDD BSAC
PCUM-SP
MCMU
PCUM
PCUM
PCUM
PCUM
BCXU
BCXU
ETMA
BCXU
BCXU
ETMA
ETME
ETME
ETME
OMU
m b b p p p e a b b p p p p p a
s s s s s s s s w w w w w w w w
HDD-spBSAC-sp
Module 2 Module 3b
MCMU-SP
PCUM-SP
PCUM-SP
PCUM-SP
BCXU-SP
BCXU-SP
ETMA-SP
ETME-SP
PCUM
PCUM
PCUM
PCUM
PCUM
BCXU
BCXU
ETMA
• The number of units is the same as on previous example
• If module 3a fails, there is no suffcient SP ETME capacity
• If module 3b fails, there is no sufficient SP PCUM capacity
• Alarms on insufficient redundancy

Content
Replacing HW Units

General procedures in Replacing HW Units (BOC-A/BJC-A)
Cabinet with sliding rails
MML:Change unit state from SE-NH state

MML:Change unit state from WO-EX/SP- to SP-EX
EX state to SE-NH Example: ZUSC:BCXU,2:SE;
Example: ZUSC:BCXU,2:TE; ZUSC:BCXU,2:TE;
ZUSC:BCXU,2:SE; ZUSC:BCXU,2:SP;
ZUSC:BCXU,2:SE; Processor LED state should be GREEN
LMP Linux: Using the IPMI interface power

LMP Linux: Using the IPMI interface power on the specific plug in unit
off the specific plug in unit Example: mch_cli Activate cpu1
Example: mch_cli Deactivate cpu1
•Wait for processor LED state: BLUE
• Close the lid
• Using the cabinet sliding rails place
the mcbc module back to the cabinet
Using the sliding rails pull the specific • Fasten bolts@front
mcbc module out of the cabinet
•Remove bolts@front
•Check grounding cable length@rear
•Check power cable length@rear
Open the lid and replace the specific faulty

piu (example: BJC-A slot 1)

General procedures in Replacing HW Units (BOC-A/BJC-A)
Cabinet CAB216 (no sliding rails)
MML:Remove traffic from all the units MML: Take all units into SP-EX state
in the specific mcbc module Monitor using OMU service terminal:
All units> SP-EX state> SE-NH RCBUGGGX
Power on the mcbc module

Power off the mcbc module
Remove the specific mcbc module Place the mcbc module back to the
from the cabinet cabinet (reconnect power, grounding,
Remove bolts and all needed cables in higig & interface cables)
the rear&front
Open the lid and replace the specific

faulty piu (BJC-A, BOC-A)

Replacing HW Units
Replacing a synchronization AMC for mcBSC
• You may need to replace a synchronization AMC (BSAC-A) if it is faulty or if it needs to be

replaced due to configuration changes, extensions or servicing
• Before starting:
• Electrostatic discharge (ESD) may damage components in the module or other units
• Wear an ESD wrist strap or use a corresponding method when handling the units, and
• Do not touch the connector surfaces
1. Change the working state of the AMC to SE-NH
ZUSC:PTUM,0:TE;
ZUSC:PTUM,0:SE-OU;
ZUSC:PTUM,0:SE-NH;

Replacing HW Units
2. Remove the unit description of the AMC
ZWTQ:PTUM,0:BSAC_A,0;
ZWTV:PTUM,0;
3. Gently pull the hot swap handle on the front panel of the AMC
• Do not pull the handle out all the way yet
• Pulling the handle notifies the hardware management system that you are going to
remove the AMC and tells it to finish all processes
• The hot swap LED starts flashing
4. Wait until the hot swap LED turns into a solid blue

Replacing HW Units
5. Pull the hot swap handle again more firmly and slide the AMC out of the bay
6. If you are not installing another AMC immediately, install an AMC filler into the empty AMC
bay: to ensure adequate cooling and a proper EMC shield in the module

Replacing HW Units
Installing a synchronization AMC
1. Check that the EMC gasket is correctly in place and that its contacts are clean
2. Insert the AMC into the bay, sliding it along the guide rails as shown in the figure
Make sure that the AMC is firmly seated in the module’s connectors

Replacing HW Units
Installing a synchronization AMC
3. Press the hot swap handle firmly
Wait until the blue hot swap LED turns off and the power LED turns solid green
4. Create the unit description of the AMC

ZWTU:PTUM,0:1F1-0:UTY=MCBC,UIN=0;
ZWTP:PTUM,0:BSAC_A,0,1,1;
5. Change the working state of the AMC to WO-BU
ZUSC:PTUM,0:SE-OU;>TE;>WO;
Replacing HW Units
Replacing the hard disk drive on hard disk drive carrier AMC
Before starting
• Wear an ESD wrist strap or use a corresponding method when handling the units
• The HDSAM-A supports both SAS and SATA hard disk drives
• SAS/SATA switch for selecting the disk type
• BCN platform supports only SAS hard disk !!!!!

Replacing HW Units
Removing the hard disk drive
1. Check the state of the hard disk
ZISI:,OMU:WDU;
2. Prevent disk updates
a) Prevent file updates to the hard disk
ZDUP:OMU;
b) Prevent database updates to the hard disk
To check the databases in use, give the DBL command
ZDBP:EQUIPM,0:DISK;
ZDBP:ILDATA,0:DISK;
3. Change the state of the hard disk into BL-US
ZISC:,OMU:WDU,0:WO-ID;
ZISC:,OMU:WDU,0:BL-US;

Replacing HW Units
4. Remove the hard disk drive carrier AMC from the AMC bay
a) Gently pull the hot swap handle on the front panel of the AMC
• Do not pull the handle out all the way yet
• Pulling the handle notifies the hardware management system that you are going to remove
the AMC and tells it to finish all processes
• The hot swap LED starts flashing

Replacing HW Units
b) Wait until the hot swap LED turns into a solid blue
c) Pull the hot swap handle again more firmly and slide the AMC out of the bay
d) If you are not installing another AMC immediately, install an AMC filler into the empty AMC
bay > This is to ensure adequate cooling and a proper EMC shield in the module

Replacing HW Units
5. Place the AMC so that the hard disk drive side is facing down
• Unscrew the four screws on the metal bracket of the AMC module, then turn the module
over
6. Disconnect the hard disk drive
• Detach the hard disk drive from the connector by pulling it gently (from right to left in the
following figure)

Replacing HW Units
Installing the hard disk drive
1. Connect the hard disk drive to the SAS connector of HDSAM-A
Connect the hard disk drive to the SAS connector in the HDSAM-A by pushing it gently (from left to
right)
2. Turn the AMC over and attach the hard disk drive to the AMC with four screws

Replacing HW Units
3. Install the AMC module back into the AMC bay
a) Check that the EMC gasket is correctly in place and that its contacts are clean
b) Insert the AMC into the bay, sliding it along the guide rails as shown in the figure
below

Replacing HW Units
c) Press the hot swap handle firmly
Wait until the blue hot swap LED turns off and the power LED turns solid green

Replacing HW Units
4. If the hard disk is a new one, initialize it
The hard disk must be in the WO-ID state so that it can be initialized
ZISC:,:WDU,0:WO-ID;
To initialize the disk:
ZIWI:,:WB,<format>,<volume label>,<number of files>,<versionlimit>,<initials>;
5. Change the state of the hard disk into TE-ID
ZISC:,OMU:WDU,0:TE-ID;
6. Check the version of the unit’s IPMI software
ZWDD:UT=OMU,UI=0;
7. Update the IPMI software, if needed
ZWDF:UT=OMU,UI=0,PT=BJC_A,PI=0;
8. Run diagnostics on the unit
ZUDD:OMU,0:WDU,0;
9. Check the diagnostics report
ZUDH:OMU,0:;
10. Change the working state of the hard disk back into WO-ID.
ZISC:,:WDU,0:WO-ID;

Replacing HW Units
11. Copy the SCMANA directory, software package directory, and BOLERO image file to the
hard disk
ZIWY:S:UNIT=OMU,PATH=/,DRIVE=WDU-S;
ZIWY:D:UNIT=OMU,PATH=/,DRIVE=WDU-B;
ZIBC:,,,,,,,,,DIR:;
12. Change the state of the hard disk into WO-BU
ZISC:,:WDU,0:WO-BU;
13. Enable disk updates
a) Resume file updates to the hard disk
ZDUR:OMU;
b) Resume database updates to the hard disk
ZDBR:EQUIPM,0:DISK;
ZDBR:ILDATA,0:DISK;
14. Check that there are no alarms active
ZAHO:OMU,0;
ZAHO:WDU,0;

Replacing HW Units
Replacing a fan module
Before starting
• Only one fan module can be replaced at once
• Prepare the spare fan unit for replacement beforehand
• After removing a fan from the BCN module, the systems starts to heat up very quickly
• Proceed immediately with the new fan installation
• Procedure applies to all three fan modules of the BCN module

Replacing HW Units
Replacing a fan module
Removing a fan module
1. Unscrew the two thumbscrews attaching the fan module to the BCN
2. Pull the fan module out from the BCN module
Installing a fan module
1. Insert the fan module to its slot at the rear side of the BCN module
2. Tighten the fan module’s thumbscrews

Replacing HW Units
Replacing an add-in card
The following types of add-in cards can be installed in the BCN module:
• BCN Octeon Card Variant A (BOC-A)
• BCN Octeon2 Card Variant A (BMPP2-A)
• BCN Octeon2 Card Variant B (BMPP2-B)
• BCN Jasper Card Variant A (BJC-A)
• BCN DSP Card Variant A (BDSP-A)
BOC-A, BMPP2-A, and BMPP2-B are processor add-in cards which can be used in:
• Packet Control Unit in Multicontroller BSC (PCUM)
• Multicontroller Exchange Terminal for Ethernet Abis (ETME)
• Multicontroller Exchange Terminal for A-interface (ETMA)
Before starting

Replacing HW Units
Removing an add-in card
1. If the BCN module is installed in the cabinet
Prepare the BCN module for add-in card replacement:
a) Gracefully shut down the BCN module
b) If there is PDU used with the BCN module,
Then
Switch off the circuit breaker on the PDU for the BCN module in question
c) Disconnect the power feed cables
d) Disconnect the network cables from the transceivers on the front side of the module
e) Disconnect the BCN grounding cable
f) Keep the network cables attached to the front cable tray of the BCN module
g) Uninstall the cable tray with attached network cables from the BCN module
h) Move the cable tray with attached network cables under the module, so the module
can be easily pulled out from the cabinet

Replacing HW Units
1. Unscrew the two thumbscrews securing the top cover of the BCN module
3. If the BCN module is installed in the cabinet

a) Pull the module out of the cabinet, until it locks into the outmost position
b) If there is another BCN module installed immediately above the module in question:
Unscrew the two screws attaching the cable tray to the BCN module immediately
above and lift the cable tray upwards in order to create enough space for the
removal of the lower module's top cover

Replacing HW Units
4. Slide the top cover of module towards the rear side until it stops
• Lift the top cover upwards

Replacing HW Units
5. Unscrew the two thumbscrews securing the add-in card to the rails inside the BCN
module
6. Slide the add-in card upwards to remove it from the BCN module

Replacing HW Units
Installing an add-in card
1. Slide the add-in card into the rails inside the BCN module until the pins of the card fall into
connectors of the main board
2. Secure the add-in card to the rails with built-in thumbscrews

Replacing HW Units
3. Place the BCN module’s cover on the top of the module, leaving small gap between the
top cover and the front edge of the module
4. Slide the top cover to the front side of the module, until it falls into place

Replacing HW Units
5. If the BCN module is installed in the cabinet:
a) If there is another BCN module installed immediately above the module in question:
Place the cable tray of the above BCN module back to position and secure it with
two built-in screws
b) Push the module back into the cabinet, until it locks into position
Pull the green latches on the inner sliding rails towards you and slide the BCN
module into the cabinet
6. Tighten the thumbscrews of the top cover
7. If the BCN module is installed in the cabinet:
Finish the add-in card replacement in BCN module:
a) Install the cable tray with attached network cables back to the BCN module
b) Connect the BCN grounding cable
c) Connect the network cables back to the transceivers on the front side of the module
d) Connect the power feed cables
e) If there is PDU used with the BCN module:
Switch on the circuit breaker on the PDU for the BCN module in question
f) Power on the BCN module
Replacing HW Units
ALARM 3757 - PLUG-IN UNIT TYPE NOT MATCH
• Set when replacing:
• BOC-A with BMPP2-A/B
• BMPP2-A with BMPP2-B
• BMPP2-B with BMPP2-A
• Do not replace BMPP2-A/B with BOC-A. Otherwise, IP addresses cannot be configured
automatically
• Check the value of parameter AUTOMATIC_UPDATE with the following command:
ZWOI:2,2070;
EXECUTION STARTED
PARAMETER CLASS: 2 SYSTEM_FUNCT_CONFIGUR
IDENTIFIER NAME OF PARAMETER VALUE CHANGE POSSIBILITY
02070 AUTOMATIC_UPDATE 00FF YES
COMMAND EXECUTED

Replacing HW Units
If the value of parameter AUTOMATIC_UPDATE is 00FF:
1. Change the state of OMU to WO-EX, if necessary
ZUSC:OMU:SE,;>TE;>WO;
2. Change the state of PCUM, ETME, or ETMA to TE-EX, if necessary
ZUSC:PCUM,0:SE,;>TE;
3. Print out alarm history of ALARM 208 - PIU TYPE HAS BEEN UPDATED IN DATEBASE
to check if the new unit type is updated in the hardware database automatically
ZAHP::NR=208;
mcBSC Heat 2010-07-25 12:33:12
ALARM HISTORY
<HIST> Heat OMU SWITCH 2010-07-25 12:32:54.87

NOTICE OMU 1F001-00-1 EQPPRB
0208 PIU TYPE HAS BEEN UPDATED IN DATEBASE
BMPP2_B 0d 01 46 02 00 01 0A 03
END OF ALARM HISTORY
COMMAND EXECUTED

Replacing HW Units
4. Print out alarm history of ALARM 3757- PLUG-IN UNIT TYPE NOT MATCH to check if
Alarm 3757 is cancelled automatically
ZAHP::NR=3757;
mcBSC Heat 2010-07-25 12:32:56
ALARM HISTORY
<HIST> Heat OMU TRANSM 2010-07-25 12:32:54.87

** ALARM OMU 1F001-00-1 ORZDHC
(0659) 3757 PLUG-IN UNIT TYPE NOT MATCH
BMPP2_B 0129 0d
<HIST> Heat OMU TRANSM 2010-07-25 12:32:54.87

.. CANCEL OMU 1F001-00-1 ORZDHC
(0659) 3757 PLUG-IN UNIT TYPE NOT MATCH
BMPP2_B 0129 0d
END OF ALARM HISTORY

COMMAND EXECUTED

Replacing HW Units
If the value of parameter AUTOMATIC_UPDATE is 0000:
1. Change the state of OMU to WO-EX, if necessary
ZUSC:OMU:SE,;>TE;>WO;
2. Configure the new plug-in unit type manually
ZUSC:PCUM,0:SE,;
ZUSC:PCUM,0:SE,;
ZWTQ:PCUM,0:BMPP2_B,0:;
ZWTP:PCUM,0:BMPP2_A,0,1,3:;
ZUSC:PCUM,0:SE,;
ZUSC:PCUM,0:TE,;

Replacing HW Units
Replacing a power distribution unit
Purpose
If the power distribution unit (PDU) is faulty, you must replace it
with a new one
Before starting
• Make sure you have a digital multi meter or voltage meter
available
• Before connecting or removing any power supply cables to
or from the power distribution unit:
• Make sure that both site power feeds to the power
distribution unit are off
• Circuit breakers on the front panel of the power
distribution unit are in the OFF position
• Equipment is properly earthed (grounded)
• Make sure your hands are dry and remove any metal
objects such as rings before touching the power supply
equipment
• Danger of hazardous voltages and electric shock!

Replacing HW Units
Removing a power distribution unit (PDU)
1. Make sure that the redundant PDU is functional
2. Switch off the circuit breakers on the PDU you are going to remove
3. Check the PDU input feeds with a digital multimeter to ensure there are no voltages in the
cables

Replacing HW Units
Removing a power distribution unit (PDU)
4. Disconnect all cables from the PDU
a) Disconnect the four power feed cables from the PDU
b) Disconnect the CGNDB grounding cable from the PDU
c) Disconnect the eight PSU input feeds from the PDU
5. Unscrew the four fixing screws attaching the PDU to the cabinet.
6. Remove the PDU from the cabinet

Replacing HW Units
Installing a power distribution unit (PDU)
1. Insert the PDU into the cabinet and align the holes of its mounting ear with the cabinet
mounting rail
2. Attach the PDU to the cabinet with four M6x12 screws

Replacing HW Units
3. Connect the PDU grounding cable (CGNDB) to the PDU
4. Check the PDU input feeds with a digital multimeter to ensure there are no voltages in the
cables

Replacing HW Units
5. Connect the site power supply cables to the PDU (for DC power supply only)
a) Crimp the cable lugs to the power
supply cables
b) Route the cables to the PDUs
c) Remove the nuts from the power
terminals with a 10mm socket
wrench
d) Connect the feed cable with lug to
terminal connector marked -48/-
60 VDC IN, and the return cable
with lug to terminal connector
marked RTN
e) Secure the cable lugs on the
terminal connectors with nuts

Replacing HW Units
6. Connect the site power supply cables to the PDU
(for AC power supply only)
a) Route the cables to the PDUs
Run the cables from the rear side of the PDUs
through the top openings (A) or bottom openings
(B) of the cabinet, and along the sides of the
cabinet
b) Plug the power supply cables to the site
power supply
7. Connect the eight PSU input feeds to the PDU
8. Switch on the site power supply to the PDU
9. Switch on the circuit breakers on the PDU

Replacing HW Units
Replacing a power supply unit
Removing a power supply unit
1. If there is PDU used with the BCN module:
Switch off the circuit breaker on the PDU for the power supply unit to be replaced
2. Unplug the power cable connected to the power supply unit
3. Unscrew the two thumbscrews attaching the power supply unit to the BCN
4. Pull the power supply unit out from the BCN module
Removing a AC PSU from the BCN module Removing a DC PSU from the BCN module

Replacing HW Units
Installing a power supply unit
1. Insert the power supply unit to its slot at the rear side of the BCN module so the screws
built into the unit are on the right-hand side
2. Tighten the unit’s thumbscrews
3. Plug the power cable to the power supply unit
4. Attach the cable clamp to the cable
5. If there is PDU used with the BCN module:
Switch on the circuit breaker on the PDU for the power supply unit, which was replaced
AC PSU DC PSU

Replacing HW Units
Replacing the air filter
Purpose
• Inspect the air filter regularly
• To prevent dust from accumulating inside the equipment, the filter element should be
replaced twice a year
1. Unscrew the two thumbscrews attaching the air filer cover to the BCN module
2. Open the air filter cover and pull out the air filter
3. Push the new air filter into the guide rails on both sides of the air filter cover
4. Push the air filter cover back and fasten the two thumbscrews
5. Record the date of the air filter change

Content
Replacing HW Units
mcBSC Synchronization Implementation

Synchronization in standalone mcBSC
Intermodule synchronization cabling
• There are two synchronization ports (SYNC 1, SYNC 2)
• The mcBSC BOXes are connected to each synchronization port in serial
• SYNC-2 port on the first BOX is connected to the SYNC-1 port on the second BOX
• SYNC-2 port on the second BOX will be connected to the SYNC-1 port on the third BOX
• Likewise the connection is done for the remaining BOXes
• Example
• To create sync cable connection between sync port 0 of BCN_A 0 in MCBC 2 and sync
port 1 of BCN_B 0 in MCBC 3:
ZWTA:MCBC,2:BCN_A,0:SYNC,0:MCBC,3:BCN_A,0:SYNC,1;
• To delete sync connection between sync port 0 of BCN_A 0 in MCBC 2 and sync port 1 of
BCN_B 0 in MCBC 3, use the following commands:
ZWTB:MCBC,2:BCN_A,0:SYNC,0:; or
ZWTB:MCBC,3:BCN_A,0:SYNC,1:;

Intermodule synchronization cabling

• Synchronization source of mcBSC can be either ToP synchronization using PTUM cards or
PCM based
• Before configuring the synchronization source the intermodule synchronization connections
have to setup
• The master reference clock for mcBSC synchronization has to be the same which is providing
synchronization to the base stations connected to the mcBSC
PCM based syncronization

• When PCM line (E1/T1/J1) is used as external clock reference (synchronization source), it
can be connected directly to SYNC port on mcBSC module front panel
• PTUM units are not needed in this configuration
• Recommended to use two PCMs to improve the reliability
• The first PCM line is connected to SYNC-1 port on the first BOX
• The second PCM line is connected to SYNC 2 port on the last BOX
• To define the primary and secondary source and PCM type:
• Example: ZDYM:MCBC,0:EXT,1:CLK=E1,PRI=1;
• Example: ZDYM:MCBC,5:EXT,2:CLK=E1,PRI=2;
• Set the revertive mode active with command ZDYV
• Example: ZDYV:YES;
• Synchronization settings and status can be checked with command ZDYI

PCM based syncronization
• Example:
SYNCHRONIZATION REFERENCES:
PRI LOCATION REFERENCE CLKTYPE STATUS SSM USED IN SYNCH
--- -------- --------- ------- ------ --- ---------------
1 MCBC-0 EXT - 1 E1 OK - YES
2 MCBC-5 EXT - 2 E1 NOK -
CURRENT OPERATION MODE OF ACTIVE SYSTEM CLOCK IS:
HOLD-OVER
SSM VALUES USED DURING REFERENCE SELECTION:
NO
REVERTIVE CONTROL DURING REFERENCE SELECTION:
YES
COMMAND EXECUTED
• The front panel synchronization ports of mcBSC module are labeled as SYNC 1
and SYNC 2 in the front panel but referred as SYNC 0 and SYNC 1 on ZWT
command group and as EXT 1 and EXT 2 on ZDY command group

ToP or Synchronous Ethernet based synchronization
• PTUM unit on BSAC-A pug-in-unit (AMC card) is used to get the clock reference from
external ToP (IEEE 1588v2) master clock or from synchronous Ethernet clock
• PTUM unit supports the following synchronization sources:
• 2.048 / 1.544 MHz according to G703
• PCM (E1 / T1)
• Ethernet according to IEEE 1588v2
• Synchronous Ethernet for optical connections
• Following external input interface connections are supported by PTUM:
• 2 x RJ-45 for E1/T1/JT1 (framed/plain) clock based synchronization
• 2 x SFP (Optical and Copper) for Timing over Packet and Synchronous Ethernet based
synchronization

1. Insert BSAC card to first and last mcBSC BOX and create PTUM using the following commands
– ZWTU:PTUM,0:1A001-0:UTY=MCBC,UIN=0:;
– ZWTU:PTUM,1:1A006-0:UTY=MCBC,UIN=5:;
– ZWTP:PTUM,0:BSAC_A,0,1,2;
– ZWTP:PTUM,1:BSAC_A,0,1,2;
• Module MCBC-5 in location 1A006-0 is assumed to be the last module in this example
2. Change the state of PTUM to SE
– ZUSC:PTUM,0:SE;
– ZUSC:PTUM,1:SE;
3. Change the state of PTUM to TE
– ZUSC:PTUM,0:TE;
– ZUSC:PTUM,1:TE;
4. Change the state of PTUM to WO
– ZUSC:PTUM,0:WO;
– ZUSC:PTUM,1:WO;
5. Set synchronization protocol and configuration of PTUMs. For IEEE 1588 ToP synchronization:
– ZDYA:PTUM,0:I,C:LP="10.10.10.10",RP="20.0.0.100",MASK=24,GW=”10.10.10.1”:;
– ZDYA:PTUM,1:I,C:LP="10.10.10.11",RP="20.0.0.100",MASK=24,GW=”10.10.10.1”:;

• Example:
SET PTUM SYNCHRONIZATION ROLE
LOCATION OPERATION ROLE CAST MODE STATUS
-------- --------------- --------- --------
PTUM-0 IEEE1588-CLIENT UNICAST ACTIVE
LOCAL IP ADDRESS : 10.10.10.10/24
REMOTE IP ADDRESS: 20.0.0.100
GATEWAY IP ADDRESS: 10.10.10.1
SET PTUM ROLE SUCCESSFULLY
COMMAND EXECUTED

• For Synchronous Ethernet:

– ZDYA:PTUM,0:S:;
– ZDYA:PTUM,1:S:;
The output from the first command is as follows:
SET PTUM SYNCHRONIZATION ROLE
LOCATION OPERATION ROLE CAST MODE STATUS
-------- --------------- --------- --------
PTUM-1 SYNC-E --- ACTIVE
SET PTUM ROLE SUCCESSFULLY
COMMAND EXECUTED

Interrogate synchronization status

Synchronization settings and status can be checked with command ZDYI
SYNCHRONIZATION REFERENCES:
PRI LOCATION REFERENCE CLKTYPE STATUS SSM USED IN SYNCH
--- -------- --------- -------- ------ --- -------------
X PTUM-0 SFP - 1 SYNC-E OK - YES
X PTUM-0 SFP - 2 SYNC-E NOK -
X PTUM-0 EXT – 1 E1 NOK -
X PTUM-0 EXT - 2 E1 NOK -
X MCBC-0 EXT - 1 E1 NOK –
X PTUM-1 EXT - 1 GPS10MHZ NOK -
X PTUM-1 EXT - 2 GPS10MHZ NOK -
X MCBC-5 EXT - 2 E1 NOK -
CURRENT OPERATION MODE OF ACTIVE SYSTEM CLOCK IS:
HOLD-OVER
SSM VALUES USED DURING REFERENCE SELECTION:
NO
REVERTIVE CONTROL DURING REFERENCE SELECTION:
YES
COMMAND EXECUTED

MCBSC O&M

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

MCBSC O&M

Uploaded by

Copyright:

Available Formats

mcBSC Operations and Maintenance

Multicontroller Base Station Controller

1 © Nokia Siemens Networks RN23823EN30GLA1

mcBSC Interface Interrogation

BTS Restart Phase Monitoring in mcBSC

mcBSC Packet Control Unit Interrogation

mcBSC Redundancy Concept Interrogation

3 © Nokia Siemens Networks RN23823EN30GLA1

mcBSC Interface Interrogation

BTS Restart Phase Monitoring in mcBSC

mcBSC Packet Control Unit Interrogation

mcBSC Redundancy Concept Interrogation

4 © Nokia Siemens Networks RN23823EN30GLA1

Disturbance is used for informing about temporary disturbance

An alarm or transient disturbance marked with one asterisk

5 © Nokia Siemens Networks RN23823EN30GLA1

Printout Type (CANCEL, DISTUR,NOTICE) Alarm Object Recovery Info

Consecutive Number Alarm Object location Info Date & Time

( 032) MCBSC32 1A001- 00-1 SWITCH *--------* 2009-03-26

Alarm Number Computer Sending Alarm

Urgency Level Supplementary Info Fields (PIU type/Rack No/Subrack No/SlotNo.)

6 © Nokia Siemens Networks RN23823EN30GLA1

ALARM SYSTEM ADMINISTRATION

? ..... DISPLAY MENU

ALARM SYSTEM ADMINISTRATION COMMAND <A__>

ALARM HISTORY HANDLING COMMANDS

? ..... DISPLAY MENU Alarm History Handling

9 © Nokia Siemens Networks RN23823EN30GLA1

mcBSC Interface Interrogation

BTS Restart Phase Monitoring in mcBSC

mcBSC Packet Control Unit Interrogation

mcBSC Redundancy Concept Interrogation

10 © Nokia Siemens Networks RN23823EN30GLA1

11 © Nokia Siemens Networks RN23823EN30GLA1

12 © Nokia Siemens Networks RN23823EN30GLA1

13 © Nokia Siemens Networks RN23823EN30GLA1

14 © Nokia Siemens Networks RN23823EN30GLA1

15 © Nokia Siemens Networks RN23823EN30GLA1

16 © Nokia Siemens Networks RN23823EN30GLA1

17 © Nokia Siemens Networks RN23823EN30GLA1

mcBSC MCBSC32 2013-05-20 21:20:11

INTERROGATE IUA MESSAGING CONFIGURATION

UNIT CONN-TYPE SIG-TYPE GW UNIT D-CHN

18 © Nokia Siemens Networks RN23823EN30GLA1

LOADING PROGRAM VERSION 2.11-0

mcBSC MCBSC32 2013-05-20 21:22:17

INTERROGATE IUA MESSAGING CONFIGURATION

UNIT CONN-TYPE SIG-TYPE GW UNIT D-CHN

19 © Nokia Siemens Networks RN23823EN30GLA1

20 © Nokia Siemens Networks RN23823EN30GLA1

mcBSC MCBSC32 2013-05-15 20:48:03

INTERROGATING NETWORK INTERFACE DATA

UNIT ADMIN ADDR

21 © Nokia Siemens Networks RN23823EN30GLA1

mcBSC MCBSC32 2013-05-20 20:53:51

INTERROGATED STATIC ROUTES

22 © Nokia Siemens Networks RN23823EN30GLA1

SIGTRAN defines a standardized way of carrying any SS7 Signaling over IP

23 © Nokia Siemens Networks RN23823EN30GLA1

An SCTP Association is identified by the computer unit (BCXU) and destination

mcBSC MCBSC32 2013-05-19 01:30:43

INTERROGATING ASSOCIATION SET DATA

ASSOCIATION SET NAME ASSOC SET ID SCTP USER ROLE

( 032) MCBSC32 1A001- 00-1 SWITCH -------- 2009-03-26