mcBSC Workshop

• Sebastian Sanchez, Techincal Project Manager - RAN AMX Claro AR, Uy, Py
• 18-09-2017
1 © 2017 Nokia
Topics

DAY 1 DAY 2
• mcBSC Planning Overview
• mcBSC Overview
• (Break 15min)
• (break 15min)
• mcBSC Commissioning
• mcBSC HW Description
• (Lunch 1h)
• (Lunch, 1h)
• mcBSC ATP
• mcBSC Interfaces
• (break 15)
• mcBSC Multicontroller Site IP Connectivity

Contact Information:
Sebastian Sanchez
11-6662-9737
Sebastian.Sanchez@Nokia.com

2 © 2017 Nokia
Topics

DAY 1 DAY 2
• mcBSC Planning Overview
• mcBSC Overview
• (Break 15min)
• (break 15min)
• mcBSC Commissioning
• mcBSC HW Description
• (Lunch 1h)
• (Lunch, 1h)
• mcBSC ATP
• mcBSC Interfaces
• (break 15)
• mcBSC Multicontroller Site IP Connectivity

3 © 2017 Nokia
 mcBSC Introduction
Multicontroller BSC
4 © 2017 Nokia
Multicontroller Network Element
The generic, scalable multicontroller hardware
platform is suitable for implementing a wide
range of processing-intensive products serving
as controller-, gateway- or server-type entities in
telecommunication networks.
Multicontroller-based network elements can consist
of a single hardware module (such as the mcTC,
or FlexiZone Controller) or consist of several
hardware modules in a standalone configuration
where the multicontroller modules provide
capacity extension.
The multicontroller interfacing is based on IP over
Ethernet transport.
Each multicontroller hardware module provides
seven 10-Gigabit Ethernet (10GigE) interfaces
for inter-module cabling and two 10-Gigabit
Ethernet interfaces for external connections, and
ten 1-Gigabit Ethernet (1GigE) interfaces for
external connections. The inter-module cabling
is arranged in a redundant fashion, so that if one
cable breaks, all modules can still communicate
with each other.
 mcBSC Introduction

Multicontroller Platform
• Optimized for different
radio applications
• Ultra high packing density
– minimized site costs and
overall OPEX
• Maximum scaleability –
CS + PS
totally new flexibility in BSC

operator’s network building

• Very high availability with
advanced redundancy RNC

principles
• Integrated high capacity IP Scaling from low to very high capacities just
transmission by adding modules
Controller role can be changed by loading
corresponding software – minimal or no HW
impact

5 © 2017 Nokia
 mcBSC Introduction

• High scalability by just adding modules

• Starting from two module fully HW
redundant configuration
• Module extensions according to traffic needs
• Three TRX capacity extension steps
• Additional PS data capacity extension
steps
• High connectivity and traffic handling
capacity
Multicontroller BSC • Up to 4400 TRXs
• Over 26 000 Erlangs
• Scalable PS data capacity
• Module size 4U - fits into 19” rack

6 © 2017 Nokia
 Modular Configurations - Simple capacity extensions

HW units for external

interfaces

ET16, ETS2, ETIP1-A, ETP, ETP-A

HW module for
additional capacity

HW units for additional

TRX and data capacity

CP1D-A, AS7-D, PCU2-E, PCS6-D

• New TRX Capacity for Flexi BSC
– New HW units for functional BCSU unit
– New HW units for PS data capacity
– Additional new HW units for external interfaces
according transport requirements
• New TRX Capacity for Multicontroller BSC
– New HW module for additional TRX, PCU and
All-IP transport capacity
– TRX capacity addition with less outage
compared to legacy BSC

7 © 2017 Nokia
 Evolution to RNC
Separate
Separatemodules
modulesfor
for RNC Octeon add-in
BSC
BSCandandRNC
RNC modules cards only

Intel + Octeon
add-in cards
RNC
modules

BSC BSC
modules modules

MultiController BSC MultiController BSC + MultiController RNC

RNC

Legacy
LegacyIntel
Inteladd-in
add-incards:
cards:
Power
Powerdown
downororreplace
replacewith
withOcteon
Octeon
add-in
add-incards
cards

– Only Octeon cards (BMPP2) used in RNC

• Intel cards (BJC-A) powered down, or replaced in
capacity upgrade
8 © 2017 Nokia – No specific interaction between cosited mcBSC & mcRNC
 Capacity Steps

11 © 2017 Nokia
 mcBSC Overview
Redundancy
The compact multicontroller design provides a high degree of
availability.
All centralized functions of the network element are redundancy
protected in order to guarantee high availability of the system.
Processors within a hardware module are independent of each
other so that a faulty processor has no effect on the performance
of the rest of the module.
The redundancy principle for each type of functional unit in the
mcBSC is shown in the figure..
The hard disks in the standalone mcBSC are duplicated. The two
basic modules each contain one hard disk AMC.
The power supply is also duplicated. Failure of one power supply
unit does not affect the availability of the controller module,
because the remaining unit is capable of providing sufficient
power to the module.
In the case of OMU failure, traffic handling capability and recovery-
related system maintenance functions of the OMU are taken over
by the MCMU functional unit.

15 © 2017 Nokia
 mcBSC Redundancy

• Different redundancy schemes applied to

different functional units:

– BCXUs are N+2 redundant:

• 2 spare BCXUs enough to replace the BCXUs of one
failed BCN
– PCUMs are N+M redundant:
• Enough spare PCUMs to replace all PCUMs in one
failed BCN.  Max 6 spares required.
– ETMEs are N+M redundant:
• Enough spare ETMEs to replace all ETMEs in one
failed BCN.  Max 3 spares
– ETMAs are SN+ redundant:
• All ETMAs are active: the traffic of a failed unit
distributed between the remaining active units.
– MCMUs are 2N redundant:
• A dedicated spare stands by ready to take over the
tasks of the failed unit.
– OMU not backed up

16 © 2017 Nokia
 mcBSC – Optimised for IP/Ethernet

• Ready for 2G to single RAN modernization with IP/Ethernet

transmission resources for combined 2G/3G implementation
• Packet Abis/Ethernet, Gb/IP, AoIP, SS7/IP (SIGTRAN)

Multicontroller BSC

AoIP

CS Core
SS7 / IP (SIGTRAN)

Packet Abis / Ethernet

Gb / IP
Lb / IP
O&M / IP

NetActTM
SMLC

PS Core

17 © 2017 Nokia
 Flexible Deployment Options
• Multicontroller BSC scales according location specific capacity needs
BTS site BSC site Core site

Scalable
capacity
according
needs
Scalable
capacity CS Core
according
needs
Scalable
capacity
according
needs

PS Core

18 © 2017 Nokia
Benefits – Why multicontroller BSC?

– Revolutionary BSC concept for GSM/EDGE Core ntw

• Compact size with scalable capacity
• All-IP platform
• Reduced installation and site space costs                                          
• Less equipment needed                    
• Less complexity and reduced spare part needs                             mcBSC
• Easy capacity upgrades
• Centralized and distributed network architecture backed by modular scalability

mcBSC

– Fast installation and commissioning times

• Scalable capacity according to needs by just adding modules mcBSC
• Common transport with 3G optimized for IP/Ethernet

mcBSC

– Reuse of HW in 3G secures and optimizes

investments in long run
• Easy capability for Multicontroller BSC/RNC operation
• Common platform with Multicontroller RNC
• Common NetAct OSS

– Enables evolution of installed Flexi BSCs towards

Multicontroller capability
• Flexi BSC capacity extensions with Multicontroller BSC modules instead of
traditional Flexi BSC BCSU and/or PCU2/ETP extensions
19 © 2017 Nokia
Topics

DAY 1 DAY 2
• mcBSC Planning Overview
• mcBSC Overview
• (Break 15min)
• (break 15min)
• mcBSC Commissioning
• mcBSC HW Description
• (Lunch 1h)
• (Lunch, 1h)
• mcBSC ATP
• mcBSC Interfaces
• (break 15)
• mcBSC Multicontroller Site IP Connectivity

20 © 2017 Nokia
 BCN Box - Box Controller Node
19”

4U Front View
AMC slots

Optional Replaceable
Air Filter

Dual Hot Swappable

Power Supply
Either 110/220V AC
or 48V DC
Rear View

3 Hot Swappable
Dual Fans
21 © 2017 Nokia
 Motherboard and Processor Add in Cards

•All interfaces, Interconnections and

HW management on the Motherboard
•Processing elements on the
Processor Add-in Cards
•Standard Ethernet, PCIe, IPMI,
interface between Motherboard and
Add-in Card
•No need to change Motherboard when
upgrading processing power - Full duplex
240 Gb Ethernet Switching capacity.
•Easy to upgrade new Processor Add-
in Card, when processor technology
evolves
•It is possible to use almost any kind of
processor architecture (Intel, PQ, Octeon,
DSP) in processor Add-in Cards and
mix them

22 © 2017 Nokia
 BCN Front Plate Connectors, Controls and LEDs

Node
selected
Power on
Alarm
LEDs

Reset button
RJ45

Add-in card
status LEDs

Network Network
USB for interfaces interfaces 2,048MHz
SW debugging 10/1GigE 1GigE reference
RS232 Fiber or Copper Fiber or Copper
Debugging Hard disc SFP+/SFP SFP 8 x external
Interfaces cross connect
OR alarm input
Element
Interconnections Management
between 1GigE 1000Base-T
Controller Nodes Fiber or Copper Local Management
10GigE SFP ( HW Management)
Direct Copper or And 2xUSB for
Fiber SW download

23 © 2017 Nokia
 BCN module architecture

PCI

UART USB
USB/
1GigE 10GigE PCI USB
SFP UART
PCIe#0
GigE 10GigE Primary FE Flash
SFP USB
GigE Octeon disc
IPMB-L
LMP

VCMC
SFP PCIe#1 5 UART
10GigE PQ
GigE UART RS232
SFP 10GigE
PCIe#0
processor
GigE
Payload FE
SFP Octeon USB
IPMB-L
External
GigE alarms
SFP 10GigE
UART
GigE PCIe#0
SFP 10GigE Payload FE
GigE
Telco
Octeon USB
RTC

UART
SFP IPMB-L
synch.. 2MHz sync.

IPMB-L
PCIe
Ethernet Switch Domain

USB
FE
GigE 10GigE
22 x10GE + 20 x 1GE
SFP UART
PCIe#0
GigE 10Gig Payload FE
SFP E USB
GigE Octeon IPMB-L
SFP 3 BI AMC
10GigE
GigE 1
FI Bay 2
UART
SFP 10GigE
PCIe#0
GigE
Payload FE 7
SFP Octeon USB
IPMB-L
GigE
SFP 10GigE
UART
GigE BI
SFP 10GigE Payload
PCIe#0
FE
4 AMC
GigE Octeon USB
2 FI Bay 1
SFP IPMB-L HD
10GigE Contr.
UART
10GigE
Payload PCIe#0
FE
10GigE Octeon Hard disc
SFP+ USB
IPMB-L
Cross connect
10GigE
SFP+ 10GigE
UART PCIe SFP
10GigE Payload/Primary
PCIe#0 5 MAC
SFP+ 10GigE FE
Octeon USB PCIe
10GigE
SFP+ GigE IPMB-L
6
6 MAC SFP

Management
PCIe#1
10GigE GigE 1 USB
SFP+

Ethernet
GigE 2 PCIe

Switch
HUB
10GigE
SFP+ GigE 3 switch
GigE 4 1000Base-T
7
GigE

24 © 2017 Nokia
 Module 1 Standalone mcBSC

PCI

UART USB
USB/
GigE 10GigE
PCI USB
SFP UART
PCIe#0
GigE 10GigE BJC-A FE Flash
SFP USB
GigE MCMU IPMB-L disc
LMP

VCMC
SFP PCIe#1 5 UART
GigE PQ
GigE UART RS232
SFP GigE
BJC-A PCIe#0
processor
FE
GigE BCXU USB
SFP IPMB-L External
GigE PCIe#1
alarms
SFP GigE
UART
GigE BJC-A PCIe#0
SFP GigE FE
GigE BCXU USB Telco
RTC

UART
IPMB-L
SFP synch.. 2MHz sync.

IPMB-L
PCIe
PCIe#1
Ethernet Switch Domain

FE

USB
GigE GigE
22 x10GE + 20 x 1GE
SFP UART

GigE GigE
BMPP2 PCIe#0

SFP
FE HDSAM-A
PCU/ETP USB
GigE IPMB-L
3 HDU
SFP GigE
PCIe#1 BI
GigE UART 1 AMC
SFP BMPP2 PCIe#0 FI Bay 1
GigE FE 7
GigE PCU/ETP USB
SFP IPMB-L
GigE PCIe#1
SFP GigE BSAC-A
UART
GigE BMPP2 PCIe#0
4 BI PTU
SFP GigE FE
GigE PCU/ETP USB
2 AMC
SFP IPMB-L
HD FI
PCIe#1
GigE Contr. Bay 2
UART

GigE
BMPP2 PCIe#0
FE
10GigE PCU/ETP USB Hard disc
SFP+ IPMB-L
PCIe#1 Cross connect
10GigE
SFP+ 10GigE
UART PCIe SFP
10GigE BJC-A PCIe#0 5 MAC
SFP+ 10GigE FE

10GigE OMU USB

PCIe
SFP+ GigE IPMB-L
6 MAC SFP
PCIe#1 6

Management
10GigE GigE 1 USB
SFP+

Ethernet
GigE 2 PCIe

Switch
HUB
10GigE
SFP+ GigE 3 switch
GigE 4 1000Base-T
7
GigE
25 © 2017 Nokia
 Module 2 Standalone mcBSC
PCI

USB
UART USB/
PCI USB
GigE 10GigE
SFP UART
PCIe#0
GigE 10GigE BJC-A FE Flash
SFP USB
MCMU IPMB-L disc
GigE LMP

VCMC
PCIe#1
SFP 5 UART
GigE PQ
GigE UART RS232
SFP BJC-A PCIe#0
processor
GigE FE
GigE BCXU USB
SFP IPMB-L External
PCIe#1
GigE alarms
SFP GigE
UART
GigE BJC-A PCIe#0
SFP GigE FE
BCXU USB Telco
GigE IPMB-L RTC

UART
SFP synch.. 2MHz sync.

PCIe

IPMB-L
PCIe#1

Ethernet Switch Domain

FE

USB
GigE GigE
SFP 22 x10GE + 20 x 1GE UART
BMPP2 PCIe#0
GigE GigE FE HDSAM-A
SFP PCU/ETP USB
IPMB-L
GigE PCIe#1 3 HDU
SFP BI
GigE AMC
GigE UART 1
SFP BMPP2 PCIe#0 FI Bay 1
GigE FE 7
GigE PCU/ETP USB
SFP IPMB-L
PCIe#1
GigE
SFP GigE BSAC-A
UART
GigE BMPP2 PCIe#0
4 BI PTU
SFP GigE FE

GigE PCU/ETP USB

2 AMC
SFP
IPMB-L
HD FI
PCIe#1
GigE Contr. Bay 2
UART
BMPP2 PCIe#0
GigE FE
10GigE PCU/ETP USB Hard disc
SFP+ IPMB-L
PCIe#1 Cross connect
10GigE
SFP+ 10GigE
UART PCIe SFP
10GigE BMPP2 PCIe#0 5 MAC
SFP+ 10GigE FE

10GigE PCU/ETP USB

IPMB-L PCIe
SFP+ GigE PCIe#1 6 MAC SFP
6
1

Management
10GigE GigE USB
SFP+

Ethernet
GigE 2 PCIe HUB

Switch
10GigE
SFP+ GigE 3 switch
GigE 4 1000Base-T
7
GigE
26 © 2017 Nokia
 TRX extension module
PCI

USB
UART USB/
PCI USB
GigE 10GigE
SFP UART
PCIe#0
GigE 10GigE BJC-A FE Flash
SFP USB
BCXU IPMB-L disc
GigE LMP

VCMC
PCIe#1
SFP 5 UART
GigE
10GigE
UART
PQ RS232
SFP BJC-A PCIe#0
processor
10GigE FE
GigE BCXU USB
SFP IPMB-L External
PCIe#1
GigE alarms
SFP 10GigE
UART
GigE BMPP2 PCIe#0
SFP 10GigE FE
PCU/ETP USB Telco
GigE IPMB-L RTC

UART
SFP synch.. 2MHz sync.

PCIe

IPMB-L
PCIe#1

FE

USB
Ethernet Switch Domain
GigE 10GigE
SFP 22 x10GE + 20 x 1GE UART
BMPP2 PCIe#0
GigE 10GigE FE
SFP PCU/ETP USB
IPMB-L
GigE PCIe#1 3 Bay 2
SFP BI
10GigE
GigE UART 1
SFP BMPP2 PCIe#0 FI
10GigE FE 7
GigE PCU/ETP USB
SFP IPMB-L
PCIe#1
GigE 10GigE
SFP
UART
GigE 10GigE BMPP2 PCIe#0
4 BI Bay 1
SFP FE

GigE PCU/ETP USB

2
SFP
IPMB-L
HD FI
PCIe#1
10GigE Contr.
UART
BMPP2 PCIe#0
10GigE FE
10GigE PCU/ETP USB Hard disc
SFP+ IPMB-L
PCIe#1 Cross connect
10GigE
SFP+ 10GigE
UART PCIe SFP
10GigE BMPP2 PCIe#0 5 MAC
SFP+ 10GigE FE

10GigE PCU/ETP USB

IPMB-L PCIe
SFP+ GigE PCIe#1 6 MAC SFP
6
1

Management
10GigE GigE USB
SFP+

Ethernet
GigE 2 PCIe HUB

Switch
10GigE
SFP+ GigE 3 switch
GigE 4 1000Base-T
7
GigE
27 © 2017 Nokia
 PS extension module
PCI

USB
UART USB/
PCI USB
GigE 10GigE
SFP UART
PCIe#0
GigE 10GigE BMPP2 FE Flash
SFP USB
PCU/ETP IPMB-L disc
GigE LMP

VCMC
PCIe#1
SFP 5 UART
GigE
10GigE
UART
PQ RS232
SFP BMPP2 PCIe#0
processor
10GigE FE
GigE PCU/ETP USB
SFP IPMB-L External
PCIe#1
GigE alarms
SFP 10GigE
UART
GigE BMPP2 PCIe#0
SFP 10GigE FE
PCU/ETP USB Telco
GigE IPMB-L RTC

UART
SFP PCIe#1 synch.. 2MHz sync.

IPMB-L
PCIe

FE

USB
10GigE
Ethernet Switch Domain
GigE
SFP
22 x10GE + 20 x 1GE
UART
BMPP2 PCIe#0
GigE 10GigE FE
SFP PCU/ETP USB
IPMB-L
GigE PCIe#1 3 Bay 2
SFP BI
10GigE
GigE UART 1
SFP BMPP2 PCIe#0 FI
10GigE FE 7
GigE PCU/ETP USB
SFP IPMB-L
PCIe#1
GigE 10GigE
SFP
UART
GigE 10GigE BMPP2 PCIe#0
4 BI Bay 1
SFP FE

GigE PCU/ETP USB

2
SFP
IPMB-L
HD FI
PCIe#1
10GigE Contr.
UART
BMPP2 PCIe#0
10GigE FE
10GigE PCU/ETP USB Hard disc
SFP+ IPMB-L
PCIe#1 Cross connect
10GigE
SFP+ 10GigE
UART PCIe SFP
10GigE BMPP2 PCIe#0 5 MAC
SFP+ 10GigE FE

10GigE PCU/ETP USB

IPMB-L PCIe
SFP+ GigE PCIe#1 6 MAC SFP
6
1

Management
10GigE GigE USB
SFP+

Ethernet
GigE 2 PCIe HUB

Switch
10GigE
SFP+ GigE 3 switch
GigE 4 1000Base-T
7
GigE
28 © 2017 Nokia
BMPP2-B card
contains a Cavium
Octeon II CN68xx
processor with 32
cores running at
1200 MHz and 4MB
L2 cache.
Each card also
contains 4 DDR3
slots supporting a
total of 32 GByte in
RAM.

29 © 2017 Nokia
 BCN X86 processor add-in card (BJC-A)

The BJC-A is an X86-
architecture-based
processor add-in card. Up
to eight add-in cards can
be installed in the BCN
module.
The BJC-A add-in card
contains four DIMM slots
and it supports up to 16
GB DDR3 800-1066 MHz
memory. The add-in card
supports both single and
dual channel operation. In
dual channel operation
the channels run at the
same speed as the
slowest DIMM module.
Supported memory
configurations are 1x2
GB, 2x2 GB and 4x2 GB.

30 © 2017 Nokia
Hard disk drive carrier AMC (HDSAM-A)

• AMC (HDSAM-A) is a mid-size

(single-width, 4 HP) AMC module
• Provides serial attached SCSI
(SAS) storage in the system
• HDSAM-A is equipped with a 2.5-
inch small form factor serial
attached SCSI (SAS) hard disk
drive
• Hard disk drive needs to be
acquired separately

31 © 2017 Nokia
 Synchronization AMC for BCN (BSAC-A)

BSAC-A is a mid-size (single-width, 4 HP)

synchronization AMC unit that is installed in
an AMC bay on the BCN module. The AMC
complies with AdvancedMC specifications of
the PICMG.

• Physically, the BSAC-A provides two SFP and two RJ45 interfaces. For both connector types, the other interface is
the main interface, and the other one provides redundant connection. The SFP interface provides input and output
for synchronous Ethernet and input for IEEE1588v2 (only slave mode is supported), whereas the RJ45 interfaces
are used for other external timing references (E1, T1, JT1, 1.544 MHz, 2.048 MHz, 10 MHz). When synchronous
Ethernet is used, an optical SFP module must be used. Direct attach copper/optical cables without integrated PHY
device are also usable. A 1000BASE-T SFP module does not work correctly as a synchronous Ethernet interface.

32 © 2017 Nokia
DC power distribution unit (BDPDU-A)
• Used in 19-inch cabinet installation
• Take the input power from the site power supply
• Eight circuit breakers installed in the front panel
• One PDU provides eight outputs
• Can provide power up to eight BCN if the two PSU in each module take power from
two PDUs
• Can provide power up to four BCN if the two PSUs in each module take power from
the same PDUs
• A 30 A circuit breaker on the negative wire at the input to protect the PDU from over-
current
• HW Dimensions: 90 mm (2U) x 485 mm x 230 mm

485 230
mm mm

90 mm

33 © 2017 Nokia
DC power supply unit, variant B (BDFE-B)

• 1200-watt redundant DC power supply units

• Located on the rear of the BCN module
• Hot swappable and takes -48/-
• 60 VDC input.
• Two outputs to BCN module
• Main output with 12V for all BCN
electronics including HW management
• Standby output with 3.3V for BCN HW
management

34 © 2017 Nokia
Main fan (BMFU-A)

• For cooling the BCN

• Contains two dual-fans
(BMFU-A)
• Located on the rear of the
BCN module
• Fan speed is controlled by
the hardware management
system
• Regulate the temperature
within the BCN
– Dimensions (H x W x D) -
142 mm x 140 mm x 75 mm

35 © 2017 Nokia
Fan for the AMCs (BAFU-A)

• For cooling the AMCs that

are installed in BCN
• Located on the rear of the
BCN module
• Fan speed is controlled by
the hardware management
system
• Regulate the temperature
within the BCN
– Dimensions (H x W x D) -
95 mm x 75 mm x 105 mm

36 © 2017 Nokia
Air filter (BAFI-A)

• Located at the front of the BCN module in the cooling air

inlet
• Prevent dust from accumulating inside the equipment
• Meets the NEBS GR 63 CORE and GR 78 CORE
requirements
37 © 2017 Nokia
SFP and SFP+ transceivers

38 © 2017 Nokia
Topics

DAY 1 DAY 2
• mcBSC Planning Overview
• mcBSC Overview
• (Break 15min)
• (break 15min)
• mcBSC Commissioning
• mcBSC HW Description
• (Lunch 1h)
• (Lunch, 1h)
• mcBSC ATP
• mcBSC Interfaces
• (break 15)
• mcBSC Multicontroller Site IP Connectivity

39 © 2017 Nokia
 IP Interfaces of multicontroller BSC

MSS
DNS
Site Equipment

MGW
BSC3
i
To
P/
In Sy SIGTRAN
te nc
r na hE
lI IP
nt
er
fa Ao
ce
BTS s mcTC
PacketAbis PacketAter

M
O& Gb
Netac
t SGSN
Lb BB
I
CBI

SMLC mcBSC
CBC

40 © 2017 Nokia
 IP Interfaces of multicontroller BSC

MSS
Site Equipment

MGW

To
P/
Sy SIGTRAN
nc
hE
IP
Ao
BTS

PacketAbis

M
O& Gb
Netac
t SGSN

41 © 2017 Nokia
 Standalone mcBSC Interfaces

External and 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

42 © 2017 Nokia
mcBSC Interfaces – Control Plane – CS

43 © 2017 Nokia
 SCTP

SCTP user SCTP user

(e.g. M3UA) ... ... (e.g. M3UA)
association
... ...
... ... unidirectional
SCTP port port ... port streams port ... port SCTP port
SCTP SCTP
IP multihomed IP
IP Addr. IP Addr. IP host IP Addr. IP Addr.
L2/L1 L2/L1 L2/L1 L2/L1
IP

44 © 2017 Nokia
 SCTP

Association Establishment : problem with TCP

normal connection establishment „denial of service“ attack

Attacker Server
A B
SYN Requests
SYN Request
Resource Resources
allocated SYN ACK allocated
SYN ACK Connection in Connections in
partial state partial state
ACK
ACK
Connection established Attacker never sends
“ACK”
 Server overloaded

45 © 2017 Nokia
 SCTP SIGTRAN

Association Establishment : SCTP mechanism

Cookie mechanism can prevent denial-of-service attack problem

SCTP SCTP
client (MSS) server (MGW)
INIT
(Initialisation Tag : Tag_A)

INIT ACK
(Initialisation Tag : Tag_B, state cookie)
COOKIE ECHO Resource
(state cookie) reservation
Resource COOKIE ACK
reservation

46 © 2017 Nokia
 SCTP

- Multiple streams prevent head of line blocking if one SCTP association is used
- Alternatively prevented by using multiple associations
- Stream #0: used for management messages
- M3UA supports ≤ 16 data streams, system will use less streams as negotiated by
either side

one SCTP association -

multiple SCTP streams
Stream
#0

Stream
#1

Stream
#2

47 © 2017 Nokia
 SCTP SIGTRAN

Data Transfer : SCTP Multi Streaming and Head of Line Blocking problem in TCP

SCTP
Association : TCP Connection:
SCTP Streams TCP Stream
Stream
#1
Stream
#2
Stream
#3 Packet loss in the stream causes all data
Packets are blocked only in one stream. packet to be blocked. This is called head of
Other streams can sent data normally. line blocking.

48 © 2017 Nokia
 SCTP

SCTP Multihoming:

- Client and Server exchange all supported IP addresses in INIT and INIT ACK Chunk
- HEARTBEAT Chunk is sent in the secondary path, with HEARTBEAT ACK as a
response

SCTP
association
192.168.1.20 primary path
SCTP .
.
endpoint 192.168.2.21 secondary
. path

49 © 2017 Nokia
 SCTP SIGTRAN

Example of SCTP multi-homing with the following parameters :

- RTO. (Retransmission Time Out) MIN: 300 ms
- RTO. (Retransmission Time Out) MAX: 500 ms
- PATH. MAX. RETRANS: 2 attempts
- ASSOCIATION. MAX. RETRANS: 4 attempts

50 © 2017 Nokia
mcBSC Interfaces – User Plane - Voice

The AoIP interface connects the base

station system (BSS) to MGW. The BSS
provides the interconnection between
the 2G radio network and core network.
The AoIP interface is implemented using
IP transmission in A interface. In
the AoIP interface, the Real-Time
Transport Protocol (RTP) is used over
UDP protocol to
convey user plane traffic.
The Real-Time Transport Control
Protocol (RTCP) can be used to monitor
the RTP stream and to collect statistical
data. 

51 © 2017 Nokia
mcBSC Interfaces – Control Plane PS

52 © 2017 Nokia
Topics

DAY 1 DAY 2
• mcBSC Planning Overview
• mcBSC Overview
• (Break 15min)
• (break 15min)
• mcBSC Commissioning
• mcBSC HW Description
• (Lunch 1h)
• (Lunch, 1h)
• mcBSC ATP
• mcBSC Interfaces
• (break 15)
• mcBSC Multicontroller Site IP Connectivity

54 © 2017 Nokia
 mcBSC IP Connectivity & Configuration
Multicontroller HW Architecture
• Integrated switches in Multicontroller platform
•Multicontroller BCN unit comprises three Broadcom Ethernet switch processors integrated on the
Motherboard:
•BCM56820 (main switch)
•BCM56512 (extension switch) and
•BCM53212 (management switch)

55 © 2017 Nokia
 mcBSC IP Connectivity & Configuration
Cabling and Connections between Multicontroller & Site
Equipment
• Multicontroller BSC with 1GE interfaces to the Site Equipment (10 cables)
• If 1GE interfaces are used for connecting Site Equipment and mcBSC, a total of five connections
per Module 1 and 2 are needed for Standalone and TRX extension
• One connection is reserved for applications which has low capacity requirements. For Abis,
Ater/Aoip two LAGs with 2 GE connections each are configured

56 © 2017 Nokia
 mcBSC IP Connectivity & Configuration
Site Solution concept for Multicontroller
• Layer 2 Ethernet Switched Site Solution

Layer 2 Ethernet Switched Site

Solution used with mcBSC external
connections

57 © 2017 Nokia
 mcBSC IP Connectivity & Configuration
Site Solution concept for Multicontroller
• Layer 3 IP Routed Site Solution

The main purpose of the Layer 3 IP

Routed Site Solution is to offer IP routing
between mcBSC and Site Equipment. In
mcBSC IP routing functionality runs on
Extension switches of modules 1 and 2.

The routes between mcBSC and Site

Equipment are either routed dynamically
with OSPF or configured as static routes.

Layer 3 IP Routed Site Solution offers

isolation since mcBSC internal broadcast
domains are not visible outside of mcBSC.

58 © 2017 Nokia
 mcBSC IP Connectivity & Configuration
Redundancy Concepts
• Stream Control Transmission Protocol (SCTP) multihoming

59 © 2017 Nokia
 mcBSC IP Connectivity & Configuration
Redundancy Concepts

• Redundancy between mcBSC and Site Equipment

• Configuring a number of cables as Link Aggregation
bundle, and connecting all ports belonging this LAG into
same line card at Site Equipment
• If the line card in the Site Equipment fails, then the connection of all
ports are lost and the switchover to the redundant path through
another mcBSC module is done
• LAG also enables redundancy between cables
• e.g. if one cable in the bundle fails then the traffic is forwarded to
other links on the LAG group
• The reliability of LAG bundle can be improved by using
Link Aggregation Control Protocol (LACP)
• LACP sends periodically LACPDUs and this way ensures the
connectivity between entities

60 © 2017 Nokia
 mcBSC IP Connectivity & Configuration
IP/LAN Protocols and Services in Multicontroller BSC
• Telnet server
• Telnet server is available in the OMU unit over TCP protocol port number 23
• Enables the user to open remote MMI sessions over TCP/IP
• FTP server in OMU
• FTP server and client remote disk access over the IP network is based on the DX 200 system’s File
Transfer Protocol (FTP) server
• Server is located in the BSC’s OMU
• FTP server uses the local TCP port 21 for control connections
TFTP servers
– Trivial File Transfer Protocol (TFTP) servers are implemented for mcBSC internal management
purposes (not used over public network interfaces of the mcBSC)

61 © 2017 Nokia
 mcBSC IP Connectivity & Configuration
IP/LAN Protocols and Services in Multicontroller BSC

• Routing protocols supported in mcBSC Site Solutions

(Site switches)
• Static Routing
• Dynamic Routing
• Virtual Router Redundancy Protocol (VRRP)
• Hot Standby Routing Protocol (HSRP)
• Hot Standby Routing Protocol version 2 (HSRPv2)

62 © 2017 Nokia
 mcBSC IP Connectivity & Configuration
IP/LAN Protocols and Services in Multicontroller BSC
• Ethernet Techniques
• Virtual LAN (VLAN)
• mcBSC uses the Virtual LAN (VLAN) technology to separate the different
traffic types
• In the VLAN network, a packet received on a port is forwarded only to ports
that belong to the same VLAN on the receiving port side
• User defines the VLAN IDs - on the basis of the application
• The switches tags all untagged frames with the user-defined Port VLAN ID
(PVID) based on the port at which the frame arrives

63 © 2017 Nokia
 mcBSC IP Connectivity & Configuration
IP Addressing in Multicontroller

• Two different kind of IP addressing are used with Multicontroller:

• Routable IP addresses
• Internal IP addresses
• Routable IP addresses are used for traffic and applications which need to be
reachable from outside of the network element and using networks based on IP
routing
• Final IP addressing depends on the Operator’s own addressing policies and network
implementations.
• Internal IP addresses are used locally inside of the network element
• In mcBSC and mcTC e.g. internal signaling between computer units and Add-in cards
use IP addresses which are not advertised outside (these addresses can be re-used
with other mcBSCs and mcTCs)

64 © 2017 Nokia
 mcBSC IP Connectivity & Configuration
IP Addressing in Multicontroller

• Allocation of internal IP addresses

Purpose Used VLAN ID Preferred Note

Subnet and
mask

Signaling 20 10.0.1.0/25

EEP in BSC3i 21 10.0.1.128/25 Not visible to

mcBSC
PEP 22 10.0.2.0/25

MC-EEP 23 10.0.3.0/25

MC-PEP 24 10.0.3.128/25
MC-Mgmt 800 10.10.10.0/24 mcBSC and
not modifiable

65 © 2017 Nokia
 mcBSC IP Connectivity & Configuration
IP Addressing in Multicontroller
• Allocation of routable application IP addresses in mcBSC
Purpose Used Maximum number Prefered Network Note Used with (3)
VLAN of needed host IP mask
ID (1) addresses (2)
O&M xx10 4 /29 1 x OMU SA

SIGTRAN 1 xx32 12 /28 8 x BCXU SA

1x MCMU
SIGTRAN 2 xx33 12 /28 8 x BCXU SA
1x MCMU
Synch. xx34 3 /29 2 x PTUM SA
ETPsig –M for xx35 4 /29 1 x BCXU SA
mcETPC
ETPsig-C for xx36 Less then 11 /28 Less then 8 x SA
mcETPC BCXU
Omusig xx44 11 /28 8 x BCXU SA Notes:
1) XX can be replaced with the element
Trxsig xx45 11 /28 8 x BCXU SA identifier (1..40).
2) Three Addresses needed for
A over IP xx46 8 /28 5+1 ETME SA VRRP/HSRP and VLANs in Site
Equipment included.
3) SA = Standalone.
Ater xx47 13 /28 5+1 ETME SA

Pabis xx48 8 /28 5 + 1 ETME SA

Gb xx49 37 /26 34 x PCUM SA

66 © 2017 Nokia
 mcBSC IP Connectivity & Configuration
IP Addressing in Multicontroller
• Attributes and IP address tags needed with mcBSC
IP Purpose IP Purpose
address address
attribute TAG

C ETPSIG-C Address GB Identifies the IP address for Gb interface

D Dynamic IP address for DHCP client. The IPL Identifies the IP address for Inter PCU LAN
attribute used when the address is received
via DHCP.
PEP Identifies the IP address for PCU ETP
I Internal IP Address. Informative attribute to protocol
identify internal usage of address.
EEP Identifies the IP address for ETP ETP
protocol
M ETPSIG-M Address

V Virtual IP Address. The address is shared IP address tags used with mcBSC applications
with units in a case of equipment protection. and interfaces

IP address attributes used with mcBSC

applications and interfaces

67 © 2017 Nokia
 mcBSC IP Connectivity & Configuration
IP Addressing in Multicontroller
Application or Purpose Configured to Interface IP Address IP Address Tag Logical or
Interface Attributes Physical

PCUSIG Management and control of PCUM PCUM IFETH0 D, I, M N/A Physical

DHCP and
TFTP BCSU EL0 & EL1 I, M N/A Logical

BCXU EL0 I, M N/A Logical

MCMU EL0 & EL1 I, M N/A Logical

ETPSIG-M, DHCP Management of ETM cards ETMA IFETH0 D, I, M N/A Physical

and TFTP
ETME IFETH0 D, I, M N/A Physical

BCXU EL0 I, M N/A Logical

MCMU EL0 & EL1 I, M N/A Logical

ETPSIG-C Telecom control for ETM cards ETMA IFETH0 C, I N/A Physical

ETME IFETH0 C, I N/A Logical

BCXU EL0 C, I N/A Logical

MC-PEP PCU ETP protocol PCUM VLAN24 (IFETH0) I PEP Logical

ETME VLAN24 (IFETH0) I PEP Logical

MC-EEP ETP ETP protocol ETME VLAN23 (IFETH0) I EEP Logical

ETMA VLAN23 (IFETH0) I EEP Physical

Inter PCU LAN Interface between PCUMs and PCUs when PCU PCUM VLAN50 (IFETH1) I IPL Logical
pooling used
PCU2 IFETH0 & IFETH1 N/A N/A Logical

Gb Gb Interface PCUM VLAN49 (IFETH1) N/A GB Logical

ETPSIG-M ETPSIG-M between mcBSC and mcTC BCXU VLAN35 (EL1) M N/A Logical

mcETPC mcETPC specific M N/A Physical

ETPSIG-C ETPSIG-C between mcBSC and mcTC BCXU VLAN35 (EL1) C N/A Logical

mcETPC mcEPC specific C N/A Logical

Usage of IP attributes and tags in mcBSC

68 © 2017 Nokia
Topics

DAY 1 DAY 2
• mcBSC Planning Overview
• mcBSC Overview
• (Break 15min)
• (break 15min)
• mcBSC Commissioning
• mcBSC HW Description
• (Lunch 1h)
• (Lunch, 1h)
• mcBSC ATP
• mcBSC Interfaces
• (break 15)
• mcBSC Multicontroller Site IP Connectivity

69 © 2017 Nokia
 Interface Dimensioning
• Packet Abis interface dimensioned taken into account traffic of this BTS
• CS U-plane
• PS U-plane
• C-plane
• M-plane
• S-plane
• SSE-traffic

• @ hubBTS
– hubBTS interface towards BSC or the next hubBTS is dimensioned taken into account traffic of
all connected BTS’s sharing the same connection towards the BSC or the next hubBSC.

• @ BSC
– Abis
– AoIP
– SIGTRAN
– Gb

70 © 2017 Nokia
 BSC HW dimensioning
• Step 1
– The number of each functional unit is calculated
• PCUM
• ETME
• ETMA
• BCXU

• Step 2
– The number of required mc-BSC modules is defined
• Type 3 (TRX extension)
• Type 4 (PS extension)

71 © 2017 Nokia
BTS IP subnet and IP@ planning
Aims in BTS subnet planning
• Good scalability
• Apply the most appropriate BTS subnet scenario

Rules
• To change subnets later on is not an easy task
• Subnets are planned to support future extensions
• Subnets needs to be grouped to supernets to keep routing tables simple

Considerations
• Dedicate or share among technologies
• Single VLAN or two VLAN approach  single subnet or two subnets
• Number of nodes per subnet
• Amount/share of free IP@ for future usage

72 © 2017 Nokia
 BTS IP subnet and IP@ planning
Subnet relations to mcBSC interface units
• A BTS is connected to one ETME, the AoIP traffic may be processed by any of the ETMAs
• BTS connected to an ETME shall be reach by minimal number or routing entries in mcBSC  supernetting
• Supernets shall be planned so that routes from ETMA towards each U-plane supernet (/u) via corresponding ETME
– Remains simple
– Covers future BTS ( )
Standalone mcBSC
• To simplify C- and M-plane routing
… PCUM

– all /u to be able to be supernet to ETME PCUM

PCUM
one of few supernet /c
ETMA
ETMA
PCUM
ETME PCUM

… PCUM

BTS equipment sharing

the
the subnet
subnet (2G,
(2G, 3G,
3G, LTE)
LTE)

BTS
BTS U-plane
U-plane
BTS
BTS C-plane
C-plane BTS
BTS U-plane
U-plane supernet (/u)
supernet (/c) subnet (/s)

73 © 2017 Nokia
 QoS Planning

QoS planning consists DSCP value, queue usage and VLAN priority definition. The VLANs are terminated at the first router
from BTS in UL direction. Transport equipment are able to “see” the QoS marking of the given packet based on
VLAN P-bit or
VLAN ID or
IP header DSCP

Rules
• Marking for UL is done at BTS. The same values are used for all BTS within a BSC and the parameters are given at
BSC. (PacketAbis and OSC BSC tab in BSCdatafil)
• Marking for DL packets is done at mcBSC (e.g. port based marking ZQ8N)
• Predefine options can be selected. {BE (0), AF11 (10), AF21 (18), AF31 (26), AF41 (34), EF (46)}
• Both VLAN P-bit and DSCP are planned.

The actual vales depends on the network traffic mix. The values to be applied are agreed at HLD phase.

74 © 2017 Nokia
BCF integration Illustration
• U-plane
– BCF is associated with ETP
– Cell is associated with PCU attached to the given ETP

• M-plane
– SCTP association is created for each BCF
• BTS end point: BTS M-plane IP@
• BSC end point. BCSU/BCXU OMUSIG IP@
– BCSU/BCXU is selected based on load balancing
• SCTP port number:
• C-plane
– SCTP association is created for each TRX
• BTS end point: BTS CUS-plane IP@
• BSC end point: BCSU/BCXU TRXSIG IP@
– BCSU/BCXU is selected based on load balancing
– TRXs of a BTS are distributed across several BCSU/BCXU to minimize impact of BCSU/BCXU
switchover
• SCTP port number:

75 © 2017 Nokia
 BCF integration – BCF to ETP association

• ETP is selected to
– Balance the ETP load
– Subnets within a /u to the same ETPE
Standalone mcBSC
PCUM
ETME PCUM
PCUM
PCUM

PCUM
ETME PCUM
PCUM

Ethernet MLS PCUM

PCUM
ETME PCUM
PCUM
PCUM

76 © 2017 Nokia
 BCF integration – Cell to PCU association

• PCU is selected within the ones associated with the ETP

– Balance the PCU load
– Minimize cell reselection outage
Standalone mcBSC
• To keep neighbor cells in the same PCU PCUM

•  preferred: all cells of a BTS to the same PCU ETME PCUM

PCUM
PCUM

PCUM
ETME PCUM
PCUM

Ethernet MLS PCUM

PCUM
ETME PCUM
PCUM
PCUM

77 © 2017 Nokia
 BCF integration – SCTP association for BCF

• M-plane SCTP association is defined

– For each BCF
– Balance the BCXU load
Standalone mcBSC

BCXU
BCXU
BCXU
Ethernet BCXU
MLS

78 © 2017 Nokia
 BCF integration – SCTP association for BCF

• C-plane SCTP association is defined

– For each TRX
– Balance the BCXU load
Standalone mcBSC
TRX

TRX

TRX

BCXU
BCXU
BCXU

TRX
Ethernet BCXU
MLS
TRX

TRX

TRX

79 © 2017 Nokia
 IP routing

1. Default route from each ETMA to MGW 10.0.88.0/26 10.0.77.0/26

SGSN .8 .7 MGW
• GW: MLS AoIP VLAN virtual GW .1 .1
2. From each ETMA to each BTS CUS-plane
• GW: EEP VLAN ETME IP@ .1
3. From each ETME to each BTS CUS-plane
10.0.66.0/30
• GW: MLS Pabis VLAN virtual GW
4. Default route from each active PCU to SGSN
• GW: MLS Gb VLAN virtual GW
5. From each active BCXU to each BTS CUS-plane
Standalone
• GW: MLS TRXSIG Virtual GW IP@
mcBSC
6. From each active BCXU to each BTS M-plane ETME
• GW: MLS OMUSIG Virtual GW IP@ .2

.1 .62 ETMA
10.0.55.0/26
MLS
Ethernet ETMA

80 © 2017 Nokia
Topics

DAY 1 DAY 2
• mcBSC Planning Overview
• mcBSC Overview
• (Break 15min)
• (break 15min)
• mcBSC Commissioning
• mcBSC HW Description
• (Lunch 1h)
• (Lunch, 1h)
• mcBSC ATP
• mcBSC Interfaces
• (break 15)
• mcBSC Multicontroller Site IP Connectivity

81 © 2017 Nokia
 mcBSC Commissioning
mcBSC standalone Commissioning Procedure
Establishingconnection
Establishing connectionwith
withmcBSC
mcBSC
ConnectingOMU
Connecting OMUvia
viaserial
serialconnection
connection
• Setup the serial connection to mcBSC • Serial to RJ45 Adapter
Serial connection settings
Baud rate 115200
Data bits 8
Stop bits 1
Parity None
Blue 8
Flow Control Xon/Xoff
Orange 6
Black 2
Red 5
Green 9
Yellow 3
Brown 4
White (grey) 7
82 © 2017 Nokia
 mcBSC Commissioning
mcBSC standalone Commissioning Procedure
InitialInspection
Initial Inspection
AccessingLMP
Accessing LMP

1. Connect TO the Local Management Processor

• Default connection to LMP is 115200 – 8N1 (serial)
• Connection to LMP can also be done through Management Ethernet
Interface
• Default IP address of LMP is 10.10.10.10 (mask 255.255.255.0)

Serial 115200- 8N1 management port

1 GigE local

83 © 2017 Nokia
 mcBSC Commissioning
mcBSC standalone Commissioning Procedure
InitialInspection
Initial Inspection
AccessingLMP
Accessing LMP

2. Login to LMP
– Login to LMP as a root user with user name ‘root’ and default password
‘root’
3. Check LMP configurations
– LMP configurations can be checked using the following commands:
mch_cli GetNodeNumber;
mch_cli GetRackNumber;
– Node number is the vertical position of the BCN box
– Rack number refers to the rack value of the entire box setup (ASCII value)

84 © 2017 Nokia
 mcBSC Commissioning
mcBSC standalone Commissioning Procedure
InitialInspection
Initial Inspection
AccessingLMP
Accessing LMP

3. Check LMP configurations

– Node number is the vertical position of
the BCN box
– Rack number refers to the rack value
of the entire box setup (ASCII value)

85 © 2017 Nokia
 mcBSC Commissioning
mcBSC standalone Commissioning Procedure
InitialInspection
Initial Inspection
VerifyingLEDs
Verifying LEDs

• All units should be at M4 state

State Description LED status
M0 FRU not installed OFF
M1 FRU installed but inactive Blue
M2 Waiting for activation request Blue
M3 Activation in progress Blue
M4 Active Red / Green
M5 Waiting for deactivation request Red
M6 Deactivation in progress Red

Description of LED status in each state of the module

86 © 2017 Nokia
 mcBSC Commissioning
mcBSC standalone Commissioning Procedure
Establishingconnection
Establishing connectionwith
withmcBSC
mcBSC
ConnectingOMU
Connecting OMUvia
viaserial
serialconnection
connection

1. Connect to active OMU by minicom command in LMP prompt

2. Enable the VIMMLAGX service terminal extension ZLP:1,VIM;
3. Open an MML session via VIMMLALX Z1CT:0;
4. To Configure the OMU network interfaces (if still needed) follow:
ZQRA:OMU::EL0::UP:;
ZQRA:OMU::EL1::UP:;
ZQRA:OMU::VLAN20,20,EL0,::;
ZQRN:OMU::VLAN20,:"10.0.1.13",26,P,IM::;
ZQRA:OMU::VLAN800,800,EL0,::;
ZQRN:OMU::VLAN800,:"10.10.10.1",24,P,I::;

87 © 2017 Nokia
 mcBSC Commissioning
mcBSC standalone Commissioning Procedure
Monitoringthe
Monitoring themcBSC
mcBSCStart-up
Start-up

MonitoringOMU
Monitoring OMUstartup
startup
• The startup order of the mcBSC system is as follows:
1. Operation and Maintenance Unit (OMU)
2. Marker and Cellular Management Unit (MCMU)
3. Other units (BCXU, PCUM, ETME, ETMA)
• Monitor the startup of the Operation and Maintenance Unit (OMU) A failure in
the OMU startup may lead to a similar failure in all other units
• When the startup of the OMU has reached the stage where the service
terminal software is started up, the Recovery Service Terminal
(RCBUGG) extension can be taken into use
• Check that the working state of the OMU is WO-EX during the startup of
the system
• If the state of OMU is TE or SE, the maintenance programs will be started up in the
Marker and Cellular Management Unit (MCMU) and the startup can be monitored there

88 © 2017 Nokia
 mcBSC Commissioning
mcBSC standalone Commissioning Procedure
Monitoringthe
Monitoring themcBSC
mcBSCStart-up
Start-up

MonitoringOMU
Monitoring OMUstartup
startup
1. Connect to service terminal
– Connect to mcBSC via minicom.
Minicom cpu<module number>;
2. Monitor the startup
• Monitor the startup of units with the RCBUGG extension.
a) Take the RCBUGG into use:
ZLE:U,RCBUGGGX;
b) Monitor the states of the computer units:
ZUSIC:COMP;
3. Reset the unit
ZAUL;
4. Monitor the startup of the OMU

89 © 2017 Nokia
 mcBSC Commissioning
mcBSC standalone Commissioning Procedure
Monitoringthe
Monitoring themcBSC
mcBSCStart-up
Start-up

MonitoringOMU
Monitoring OMUstartup
startup

a) The first phase output indicates the startup of the boot loader l) The FISLIB Library Manager (FIZSLM) is started up:
program block(BOLERO): PROCESSING FAMILIES FIZ ...
DMX SYSTEM STARTUP TESTS m) Loading of the first load group:
b) Scanning PCI bridges: LOADING STARTED 0003..
SCANNING PCI BRIDGES n) Initialization of work files:
c) Configuring PCI bridges: INITIALIZING WORK FILES
CONFIGURING PCI/PCI BRIDGES o) The FUNLIB Library Manager (FUZNLM) startup:
d) Scanning PCI devices: PROCESSING FAMILIES FUZ ...
SCANNING PCI DEVICES p) The unit state administration program block (USAPRO) is given
e) Flash version of CPU is shown: permission to load:
BOPBJCGX.PAC <ver> READY - PHASE 2
f) Choosing software package in the OMU successful: FILE LOADING ACTIVATED
CHOOSING PACKET q) Loading of a load group OK. All remaining load groups are loaded:
g) Loading of the computer configuration table successful: LOADING STARTED ...
LOADING NET CONFIG... r) The USAPRO is given permission to start the program blocks:
h) Loading of the load list successful: READY - PHASE 3
LOADING LOAD LIST FROM <source> s) Startup of program blocks:
i) Loading of the load modules successful: PROCESSING FAMILIES...
MODULE LOADING STARTS t) Running SW package information:
LOADING MODULES FROM <source> RUNNING PACKAGE
ALL MODULES LOADED u) Startup of unit is terminated:
j) Debugger software started up: READY - WO
DEBUGGER READY
k) First 'PROCESSING FAMILIES' notice is output on the terminal:
PROCESSING FAMILIES
90 © 2017 Nokia
 mcBSC Commissioning
mcBSC standalone Commissioning Procedure
Monitoringthe
Monitoring themcBSC
mcBSCStart-up
Start-up

MonitoringMCMU
Monitoring MCMUstartup
startup
1. Connect to service terminal
i) Loading of the load modules successful:
– Connect to mcBSC via minicom. MODULE LOADING STARTS
LOADING MODULES FROM <source>
Minicom cpu<module number>;; ALL MODULES LOADED
j) Debugger software started up:
DEBUGGER READY
2. Reset the unit k) First 'PROCESSING FAMILIES' notice is output on the terminal:
PROCESSING FAMILIES
ZAUL; l) The FISLIB Library Manager (FIZSLM) is started up:
PROCESSING FAMILIES FIZ ...
3. Monitor the startup of the MCMU m) Loading of the first load group:
LOADING STARTED 0003..
n) Initialization of work files:
a) The first phase output indicates the startup of the boot loader program INITIALIZING WORK FILES
block(BOLERO): o) The FUNLIB Library Manager (FUZNLM) startup:
DMX SYSTEM STARTUP TESTS PROCESSING FAMILIES FUZ ...
b) Scanning PCI bridges: p) The unit state administration program block (USAPRO) is given permission to load:
SCANNING PCI BRIDGES READY - PHASE 2
c) Configuring PCI bridges: FILE LOADING ACTIVATED
CONFIGURING PCI/PCI BRIDGES q) Loading of a load group OK. All remaining load groups are loaded:
d) Scanning PCI devices: LOADING STARTED ...
SCANNING PCI DEVICES r) The USAPRO is given permission to start the program blocks:
e) Flash version of CPU is shown: READY - PHASE 3
BOPBJCGX.PAC <ver> s) Startup of program blocks:
f) Choosing software package in the OMU successful: PROCESSING FAMILIES...
CHOOSING PACKET t) Running SW package information:
g) Loading of the computer configuration table successful: RUNNING PACKAGE
LOADING NET CONFIG... u) Startup of unit is terminated:
h) Loading of the load list successful: READY - WO
LOADING LOAD LIST FROM <source>

91 © 2017 Nokia
 mcBSC Commissioning
mcBSC standalone Commissioning Procedure
Monitoringthe
Monitoring themcBSC
mcBSCStart-up
Start-up

MonitoringBCXU
Monitoring BCXUstartup
startup
1. Connect to service terminal
i) Loading of the load modules successful:
– Connect to mcBSC via minicom. MODULE LOADING STARTS
LOADING MODULES FROM <source>
Minicom cpu<module number>;; ALL MODULES LOADED
j) Debugger software started up:
DEBUGGER READY
2. Reset the unit k) First 'PROCESSING FAMILIES' notice is output on the terminal:
PROCESSING FAMILIES
ZAUL; l) The FISLIB Library Manager (FIZSLM) is started up:
PROCESSING FAMILIES FIZ ...
3. Monitor the startup of the BCXU m) Loading of the first load group:
LOADING STARTED 0003..
n) Initialization of work files:
a) The first phase output indicates the startup of the boot loader program INITIALIZING WORK FILES
block(BOLERO): o) The FUNLIB Library Manager (FUZNLM) startup:
DMX SYSTEM STARTUP TESTS PROCESSING FAMILIES FUZ ...
b) Scanning PCI bridges: p) The unit state administration program block (USAPRO) is given permission to load:
SCANNING PCI BRIDGES READY - PHASE 2
c) Configuring PCI bridges: FILE LOADING ACTIVATED
CONFIGURING PCI/PCI BRIDGES q) Loading of a load group OK. All remaining load groups are loaded:
d) Scanning PCI devices: LOADING STARTED ...
SCANNING PCI DEVICES r) The USAPRO is given permission to start the program blocks:
e) Flash version of CPU is shown: READY - PHASE 3
BOPBJCGX.PAC <ver> s) Startup of program blocks:
f) Choosing software package in the OMU successful: PROCESSING FAMILIES...
CHOOSING PACKET t) Running SW package information:
g) Loading of the computer configuration table successful: RUNNING PACKAGE
LOADING NET CONFIG... u) Startup of unit is terminated:
h) Loading of the load list successful: READY - WO
LOADING LOAD LIST FROM <source>

92 © 2017 Nokia
Topics

DAY 1 DAY 2
• mcBSC Planning Overview
• mcBSC Overview
• (Break 15min)
• (break 15min)
• mcBSC Commissioning
• mcBSC HW Description
• (Lunch 1h)
• (Lunch, 1h)
• mcBSC ATP
• mcBSC Interfaces
• (break 15)
• mcBSC Multicontroller Site IP Connectivity

93 © 2017 Nokia
Copyright and confidentiality
The contents of this document are proprietary and
confidential property of Nokia. This document is
provided subject to confidentiality obligations of
the applicable agreement(s).
This document is intended for use of Nokia’s
customers and collaborators only for the purpose
for which this document is submitted by Nokia. No
part of this document may be reproduced or made
available to the public or to any third party in any
form or means without the prior written permission
of Nokia. This document is to be used by properly
trained professional personnel. Any use of the
contents in this document is limited strictly to the
use(s) specifically created in the applicable
agreement(s) under which the document is
submitted. The user of this document may
voluntarily provide suggestions, comments or
other feedback to Nokia in respect of the contents
of this document ("Feedback").
Such Feedback may be used in Nokia products
and related specifications or other documentation.
Accordingly, if the user of this document gives
Nokia Feedback on the contents of this document,
Nokia may freely use, disclose, reproduce,
95license, distribute
© 2017 Nokia and otherwise commercialize
the feedback in any Nokia product, technology,
Nokia operates a policy of ongoing development. This document and the product(s) it describes
Nokia reserves the right to make changes and are protected by copyright according to the
improvements to any of the products and/or applicable laws.
services described in this document or withdraw
this document at any time without prior notice. Nokia is a registered trademark of Nokia
Corporation. Other product and company names
The contents of this document are provided "as mentioned herein may be trademarks or trade
is". Except as required by applicable law, no names of their respective owners.
warranties of any kind, either express or implied,
including, but not limited to, the implied warranties
of merchantability and fitness for a particular
purpose, are made in relation to the accuracy,
reliability or contents of this document. NOKIA
SHALL NOT
BE RESPONSIBLE IN ANY EVENT FOR
ERRORS IN THIS DOCUMENT or for any loss of
data or income or any special, incidental,
consequential, indirect or direct damages
howsoever caused, that might arise from the use
of this document or any contents of this document.