You are on page 1of 62

mcBSC/mcTC O&M

Specialist training
• Antti Salokoski

Agenda
Methods how to take connection to BCN
Connecting to BSAC, Switches and CPUs
Switch management
Updating eSW via MML
VLAN’s, IP interfaces and routes used in mcBSC
VLAN’s, IP interfaces and routes used in mcTC
Call/traffic flow
Synchronization
HW Redundancy
L2 redundancy
External alarms

16 for box6 10.10.0 root@BCNMB-A:~# Default IP addresses 10.Methods how to take connection to LMP Connection to LMP 1/5 Connection to LMP with telnet by using Virtual MML in OMU •Connection is taken to the BCN’s VLAN800 address .10.10.10.10.17 for box7 .10.14 for box4 10.10.10.VIM 00-MAN> 1CT::10.15 for box5 10.10.10.2 Wind River Linux glibc_small (standard) 2.209.10.10.144.10.Login as root/root and LMP prompt should appear Connection to MCBC-0 00-MAN> ZLP:1.10 for box0 10.10 Linux 2.12 for box2 10.21.10.10.10.0ap_standard (BCNMB-A) (09:47 on Wednesday.6.10 VIMMLA: connected to: 10.10 VIMMLA: connecting to: 10.10.10. 21 May 2014) login: root Password: Last login: Wed May 21 08:58:18 from 10.10.11 for box1 10.10.7-hrt1-WR2.13 for box3 10.10.10.

Methods how to take connection to LMP Connection to LMP 2/5 Direct connection to LMP with serial cable • You can directly connect your PC via serial cable to BOX itself .Connect ”Cisco compliant” RS232 cable to SER port .Login as root/root and LMP prompt should appear • root@BCNMB-A:~# .Define connection settings • Baud rate 115200 • No parity • 8 data bits • 1 stop bit • No flow control .

Methods how to take connection to LMP Connection to LMP 3/5 IP Management interface via port MGT • By default LMP management IP configuration is defined according following table .

255. .16 NETMASK=255.41.Define IP for the PC from the same subnet as the mgmt IP of the BCN.255. Output the eth0 configuration file with ”cat” command root@BCNMB-A:~# cat /etc/sysconfig/network-scripts/ifcfg-eth0 DEVICE=eth0 BOOTPROTO=static BROADCAST=10.81.41.31 IPADDR=10.Methods how to take connection to LMP Connection to LMP 4/5 Connect Ethernet cable to MGT port .81.Login with SSH as root/root and LMP prompt should appear .224 ONBOOT=yes .If IP connection fails you can check the existing configuration via serial interface.

0ap_standard (BCNMB-A) (00:29 on Wednesday. When connecting with SSH only password is given. you can take connection to another BOX via telnet or SSH and giving IP address of the BOX.11.10.0 Linux 2..11 Trying 10. root@10.. Last login: Wed May 30 00:29:53 2014 from 10.10.21.Methods how to take connection to LMP Connection to LMP 5/5 Connecting from the box to another box • When you are already connected to BCN.10.10 Escape character is '^]'.10.6.10.10.11.10. Wind River Linux glibc_small (standard) 2.10.10. 30 May 2014) root@BCNMB-A:~# login: root .10.10.11's password: Connected to 10.10. root@BCNMB-A:~# telnet 10.7-hrt1-WR2.11 root@BCNMB-A:~# ssh 10.

.

6.10.0.10. Linux 2.Connecting to BSAC.51's password: Welcome to BCNSA-A AMC Command-Line Wind River Linux glibc_cgl (cgl) 3.51)' can't be established.10.10. Switches and CPUs Connection to BSAC (PTUM) plug-in unit Local connection to BSAC is taken with telnet and SSH from LMP • Telnet is used to connect synch application and SSH to WindDriver linux in BSAC • IP address to the BSAC is allocated via DHCP and the default addresses are PTUM0 10.10.39-grsec (BCNSA-A) (16:25 on Monday. 23 February 1970) root@BCNMB-A:~# ssh 10.10.10.10.51.10. root@10. RSA key fingerprint is 8a:36:a4:e1:ac:75:7b:9e:bc:6e:1e:dd:db:a6:c6:b3.10.10.51 10000 Trying 10..50 and PTUM1 10.2 User: root Password: **** (BCNSA-A)> Session is closed with quit command root@BCNSA-A:/root> Session is closed with exit command .10..10.51 root@BCNMB-A:~# telnet 10.27.51 (10.51' (RSA) to the list of known hosts.10.51 The authenticity of host '10. Escape character is '^]'.10.10. Are you sure you want to continue connecting (yes/no)? yes Warning: Permanently added '10.10. Connected to 10.10.10.10.51.

10.Connecting to BSAC. When connecting to switches. Taking connection to another BOX’s switches is not possible.1 between switches Ctrl-g + 2 to MCH_CLI Ctrl-g + d detach the screen back to the original console Session closed with ctrl-c Telnet connection successfully opened to MCBC 100 (BCN_A).10. Transfer between these: Ctrl-g + 0. . !Do not use screen without any parameter (KoffM1MainSwitch) > Screen has sessions open to FASTPATH switches and MCH_CLI.10. IP=10.100:. you need to be logged in same BOX’s BCN. Screen from LMP: Telnet: root@BCNMB-A:~# screen -r User:admin Password: (KoffM1MainSwitch) > ZW6T:MCBC. Switches and CPUs Main and External Switch connection Connection to BCN switches can be taken by activating screen application in LMP or with telnet via LDI.

you need to be logged in same BOX’s BCN. Taking connection to another BOX’s CPU(s) is not possible with minicom. Only possible way to monitor start-up log for the computer is to have a connection via BCN. root@BCNMB-A:~# minicom cpu8 Welcome to minicom 2. Press CTRL-A Z for help on special keys root@BCNMB-A:~# reverting back to BCN ctrl – a + q . When connecting from BCNs to CPU(s). Switches and CPUs Connecting to CPUs Connection CPU(s) (OMU.Connecting to BSAC.2 OPTIONS: I18n Compiled on Dec 4 2013. 11:18:00.MCMUs and BCXUs) service terminal is taken from the BCN or a via MML.

.

Protected ports do not forward traffic to each other. even if the ports are configured to allow same VLANs.Switch management Configuring main and external switches 1/2 BCN module has three separate switch units. Only Main and Extension switches are accessible and need to be configured by user. Ports between the Main and Extension switches are configured as Protected and this way L2 loops are prevented between the switches. .

•Two 10 Gigabit Ethernet XAUI interface implements the interconnection between Main and Extension switch. .Switch management Configuring main and external switches 2/2 •A Multicontroller BCN unit comprises three Broadcom Ethernet switch processors integrated on the Motherboard: •The management switch is used for providing a connection between LMP and Main switch and it is not controlled through Fastpath command line interface •Add-in card slots has a Fast Ethernet connection to Management switch but those connections are not used by mcBSC.

Loop creation over the interface between the two site equipment units is prevented by configuring an L3 hop between these. HiGig is not compatible with spanning-tree protocols. which is used for Ethernet loop prevention and for managing the inter-switch connections. HiGig does not extend to the site equipment. HiGig settings are loaded to the main and extension switches from LMP at system startup and do not require user intervention. .Switch management Main purpose of Ethernet Switches in mcBSC • Perform traffic aggregation • VLAN tagging/untagging • Providing loop free topologies • The HiGig protocol.

The CLI can be accessed via LMP’s prompt with screen application by using a console connection or by using a remote SSH connection. . view settings and statistics and send trap messages. •Simple Network Management Protocol (SNMP) traps The SNMP agent allows the user to configure the Ethernet switch.Switch management Ethernet switch can be managed through • configuration files () • Command Line Interface (CLI) The command line interface (CLI) is a text-based way to manage and monitor the system.

Switch management Configuration files of BCN switches Path structure of switch configuration files .

. Detailed instructions are provided in Technical Note TS-BSC-SW-0910 Note! BSC software fallback is not copying switch configuration. Once configurations are done it is important that the backup bank is updated as well.Switch management Configuring BCN switches Manually configuring switches from switch prompt.

scr) is a text-based file with binary headers but it still could be edited by the text editor application. (Main1) #script apply n9.scr … Configuration script 'n9.scr Config script created successfully.scr' validated.scr (Main1) #show running-config n9. .Switch management Save. validate and apply the running setting to script file •This will save the running setting to /mnt/fastpath/n9. •It is easy to backup the switch setting to the script file and apply it at another switch by using save and apply command •The script file (n9. (Main1) #script validate n9.scr Are you sure you want to apply the configuration script? (y/n)y … Configuration script 'n9. •Validate the configuration file to check if any syntax error and apply it. The point is just modifying the text area as you want without changing the binary header.scr' applied.

.

Updating eSW via MML
Overview
•In order to install eSW to BCN/BOC/BMPP2/BJC/BSAC add in cards with MML
commands FTP/Telnet server should be activated in BSC and in every MCBC box.
•Some of the eSW needs to be updated to both flashbanks of the unit separately.
•When new version of the BOLEROGX.IMG is published it needs to be copied root
directory before starting eSW upgrade.
•Some of the new eSW is published as ZIP file, which means that those needs to
be manually copied from LFILES directory to LMP.
• Also some ZIP files also need to be installed/upgraded manually using the LMP
commands, as those are not supported by eSW management MMLs
•Log file (CBLFILGX.LOG) for the eSW installation can be found from the ASWDIR
•For the detailed eSW upgrade instructions refere to the release documentation.

Updating eSW via MML
eSW is updated to mcBSC in following order
In BCN, BSAC and BOC-A the back-up bank is updated. This means that
after current back-up is flashed restart is given so that unit boots from
2. BJC-A
1.BCN-A/BCN-B( mandatory
to be updated before other unit types)
updated
bank.
BIOS/BIOSBB
BCNHIGIG
 
 
 

BCNRESET
VCMC
UBOOT
KERNEL
ROOTFS
FRU
LCPL(BCN-A) /CPLD
At this point restart is pending for the BCN
Box is restarted to activate another flash
Another bank BCNHIGIG
Another bank BCNRESET
Another bank UBOOT
Another bank KERNEL
Another bank ROOTFS
Reboot LMP

BACKUPBIOS/BACKUPBIOSBB
FPGA
MMC
FRU

3. BOC-A/BMPP2-B
MMC
UBOOT
FRU
At this point restart is pending for the updated unit
Reboot boards
Another bank UBOOT
Restart boot board
4. BSAC-A
FRU
MMC
At this point restart is pending for the BCN
Reboot boards
Another bank FRU
Another bank MMC
Reboot boards

Updating eSW via MML
eSW names in MML printout 1/2

Updating eSW via MML eSW names in MML printout 2/2 .

.

DHCP for LMP and PTUM. EMB is Layer 2 Ethernet based implementation and do not need IP addresses configured for the interfaces.g. . IPMI and SNMP VLAN interfaces are configured to OMU and MCMUs.VLAN’s. IP interfaces and routes used in mcBSC Management VLAN 800 VLAN 800 is used for internal management purposes inside of Multicontroller platform e. EMB VLANs are redundant for each other in EL interfaces in BJC-A add-in cards. This VLAN is created to the default configuration in factory prior delivery. These VLANs are configured to Main Switches in the default configuration done in factory. EMB VLANs 5 and 6 Two VLANs is used to implement EMB (Ethernet Message Bus) in mcBSC.

This VLAN is configured to the Main Switches in the default configuration done in factory. PCUMs. VLAN interfaces are configured to ETMEs and PCUMs. .VLAN’s.MCMUs. DHCP and software downloading purposes for BOC-A cards as ETMA. VLAN interfaces are configured to OMU. PEP VLAN 24 PEP VLAN is used for transport PS traffic between PCUM and ETME cards. EEP VLAN 23 EEP VLAN is used for transporting CS traffic between ETMA and ETME cards. ETMAs and ETMEs . This VLAN is configured to the Main Switches. This VLAN is configured to the Main Switches. BCXUs. IP interfaces and routes used in mcBSC Signaling VLAN 20 Signaling VLAN 20 is used for management and control traffic (ETPSIG and PCUSIG). VLAN 20 is redundant for the ifeth interfaces in every octeon add-in card. VLAN interfaces are configured to ETMAs and ETMEs. ETME and PCUM.

The secondary path of the SCTP stream shall have different route towards backbone than the primary SCTP steam. VLANs interfaces are configured to MCMUs and BCSUs. OMUSIG and TRXSIG VLANs xx44 & xx45 OMUSIG and TRXSIG VLANs are used for IP connectivity between BCXU and BTS using Packet Abis over Ethernet VLAN interfaces are configured to BCXUs. Local IP address based Default Gateway is created toward HSRP/VRRP address for VLAN interfaces. Sigtran-2 VLAN is needed when Multihoming is used with SCTP applications. These VLANs are configured to Main and External Switches. . Local IP address based Default Gateway is created toward HSRP/VRRP address for VLAN interface.VLAN’s. BBI and Lb. These VLANs are configured to Main and External Switches. IP interfaces and routes used in mcBSC Sigtran VLANs xx32 Sigtran-1 is used for transport SCTP based traffic and used by different applications: A -Sigtran.

Default Route is created toward HSRP/VRRP address.VLAN’s. Default Route is created toward HSRP/VRRP address. . Pabis VLAN xx48 PAbis is used for transport Packet Abis traffic between ETME and IP BTS using Packet Abis over Ethernet. VLAN interfaces are configured to ETMAs. This VLAN is configured to Main and External Switches. This VLANs is configured to Main and External Switches. VLAN interfaces are configured to ETMEs. IP interfaces and routes used in mcBSC AoIP VLAN xx46 AoIP is used for transport CS user plane traffic between ETMA and MGW.

IP interfaces and routes used in mcBSC Gb VLAN xx49 Gb VLAN is used for interconnection for PCUMs in a case of PCU Pooling (PCP) feature and Gb interface between SGSN and PCUMs. .VLAN’s. VLAN interfaces are configured to PCUMs. This VLAN is configured to Main and External Switches. VLAN interfaces are configured to ETMAs and ETMEs. Pater VLAN xx47 The Packet Ater interface is used for transport CS data traffic between the mcBSC and the mcTC. Default Route is created toward HSRP/VRRP address. Default Route is created toward HSRP/VRRP address. This VLAN is configured to Main and External Switches.

This VLAN is not redundant.VLAN’s. LDI The integrated LAN device management concept provides a system-internal management interface to the Ethernet switches: Internal LAN IP addresses form a network element-internal private network. Default Route is created toward HSRP/VRRP address. . VLAN interfaces are configured to MCMU. IP interfaces and routes used in mcBSC O&M VLAN xx10 O&M VLAN is used for applications such as remote MML. VLAN interfaces are configured to OMU. which makes it possible to have system-internal management connections between the switches and the DMX-based CPU units. NetAct and Cell Broadcast Centre (CBC).

Detailed info regarding how to create VLANs and Routes can be found from the Multicontroller Site IP Connectivity Guidelines document. IP interfaces and routes used in mcBSC IUA messaging configuration within mcBSC 1. ETPSIG-C between BCXU and ETMA 5. PCUSIG between BCXU and PCUM. ETPSIG-C between BCXU and ETME 6. ETPSIG-M between BCXU and ETMA 3.VLAN’s. Logical PCUM association to BCXU (host BCXU) Note! ETPSIG-C is created to every working BCXU Host BCXU is defined for the PCUM’s that shall be in WO-EX state. 2. ETPSIG-M between BCXU and ETME 4. .

.

INTERNAL VLAN 802 INTERNAL VLAN 802 is used for cluster communication purposes inside of Multicontroller Transcoder.VLAN’s. e.g. TFTP and syslog. . INTERNAL VLAN 801 INTERNAL VLAN 801 is used for cluster communication purposes inside of Multicontroller Transcoder. IP interfaces and routes used in mcTC HW-MGMT VLAN 800 HW-MGMT VLAN 800 is used for internal HW management purposes inside of Multicontroller Transcoder. for DHCP.

IP interfaces and routes used in mcTC TCUSIG VLAN 823 TCUSIG VLAN 823 is used for TCUSIG traffic between mcETPC and MCU.VLAN’s. Packet Ater side VLANs User configurable Packet Ater side VLANs Packet Ater U-plane. LINX VLAN 822 LINX VLAN 822 is used for LINX based TCUSIG traffic between MCU and TCU. FLIP VLAN 821 FLIP VLAN 821 is used for FLIP based user plane traffic between mcETPC and TCU. . ETPSIG-M and ETPSIG-C.

IP interfaces and routes used in mcTC AoIP VLAN User configurable AoIP U-plane VLAN. .VLAN’s. O&M (NetAct) User configurable O&M (NetAct) VLAN. Note! All the mcTC VLANs are created only to Main Switch and are not redundant.

.

Call/Traffic flow CS call flow chart Packet Abis BTS ETME mcBSC ETMA S W I T C H AoIP MGW .

Call/Traffic flow PS call flow chart Packet Abis BTS ETME mcBSC PCU M S W I T C H SGSN Gb over IP .

Call/Traffic flow Useful service terminal commands for ETMA/ETME 1/3 Traffic - detpcs all • - displays number of active CS calls handled by unit dudul • - displays number of UL IP packets routed by unit duddl • - displays number of DL IP packets routed by unit dpdul • - displays number of UL IP packets dropped by unit dpddl • - displays number of DL IP packets dropped by unit netstat -a • displays TCP/UDP ports used by unit .

Call/Traffic flow Useful service terminal commands for ETMA/ETME 2/3 Configuration - dbcfinfo • - displays all BCFs configured to unit dbcfinfo [bcf_id] • - displays IP configuration related to BCF etpsig_m_info • - displays ETPSIG-M information etpsig_c_info • - displays ETPSIG-C information detpps • displays to which PCU PEP link is created (can be used with ETME only) .

Call/Traffic flow Useful service terminal commands for ETMA/ETME 3/3 Configuration - route or drfdb • - displays IP routing information ifconfig or dinterface • - displays interface information dbscp • displays QoS and overload parameters .

Call/Traffic flow Useful service terminal commands for PCUM 1/4 RNW Configuration - dtrxrnw • - Display RNW configuration for a particular TRX dbtsrnw • - Display RNW configuration for a particular BTS dsegrnw • - Display RNW configuration for a particular segment dsegallocinfo • Display the initial SEG-DSP Association which is the result of DSP Allocation Algorithm .

Call/Traffic flow Useful service terminal commands for PCUM 2/4 Gb configuration - dgbipbvc • - Display the information about certain BVC dgbbvcstatus • - Display BVC status dgbipnsei • - Display the information about certain NSE dgbipnsvc • - Display the information about certain NSVC dmocnpoolinfo • Display the information about certain mocn_pool .

Call/Traffic flow Useful service terminal commands for PCUM 3/4 Traffic - dsegtbf • - Display TBF information specific to identified segment dtrxtbf • - Display TBF information specific to identified TRX dtfitbf • - Display TBF information specific to identified TFI dtsltbf • - Display TBF information specific to identified TSL Dabmtrxinfo • - Display the TRX Information for the specified bts in the specified segment Ddspinfo • - Display the information for all configured DSP's dpcutbf • Displays Number of UL and DL TBFs for all active segments in the PCU .

Call/Traffic flow Useful service terminal commands for PCUM 4/4 Statistics - dbu • - Display buffer Statistics per unit dbp • - Display buffer statistics for a particular application dbs • - Display statistics of buffers of a particular size dtp • - | Display the timers Statistics per application dtu • - Display the timers statistics per unit dsca • - Display Statistics for a specific Category dsco • Display Statistics for a specific Counter .

Call/Traffic flow CS data call flow chart mcBSC Packet Abis BTS Packet Ater ETMA ETME S W I T C H MGW mcTC AoIP .

Call/Traffic flow mcTC Useful service terminal commands for ETPC - cat ETPCFGDT.cfg • - Displays information of the mcTC configuration file etpsig_m_info • - Displays ETPSIG M Interface Information etpsig_c_info • - Displays ETPSIG-C Interface Information detpcs • Displays CS data call information .

.

048 / 1. . PCM synchronization source comes from external PCM connection available in site.544 MHz In this scenario a synchronization source is connected into the first module using one dedicated RJ45 connector on the front panel of the module. In the case of mcTC these synchronization sources are connected to the RJ45 connector at the BCN box front panel. An optional synchronization source for redundancy can be connected to the last module in the synchronization chain.Synchronisation PCM / 2.

The use of optical SFP is mandatory when using Synchronous Ethernet. Source for IEEE 1588-2008 or SyncE must be available from the site since it is not available from BSC.Synchronisation IEEE 1588-2008 and Synchronous Ethernet In mcBSC Ethernet synchronization sources are connected to the PTUM using SFP interface for each unit. Ethernet synchronization sources are connected to the PTUM in mcTC using SFP interface. Two PTUM units have to be provided in two modules of mcBSC (n+1 redundancy). .

544 MHz according to G703 §13 • PCM (E1 / T1) • Ethernet according to IEEE 1588-2008 • Synchronous Ethernet (optical connection only) Note that he second sync source is optional for both PCM based and PTUM based synchronization.048 / 1. but very highly recommended for both. .Synchronisation mcBSC The synchronization Plug-in unit mcBSC (PTUM) can use the following synchronization sources: • 2.

Synchronisation mcTC The synchronization Plug-in unit in mcTC (PTU) can use the following synchronization sources: • Ethernet according to IEEE 1588-2008 • Synchronous Ethernet (optical connection only) .

.

Note that mcTC is not redundant. .HW redundancy Redundancy of the functional units All the crucial units of the mcBSC network elements have been backed up to ensure the reliability of the system's operations. other mcTCs are still functional. In case of malfunction in one mcTC. Network Element level redundancy can be achieved by utilizing multiple mcTCs.

All signaling units are backed up according to the N+1 or N+1/L principle. which means that while all units have their own tasks. . the tasks of unit may be redistributed to the spare unit in case of unit failure or switchover. N+M redundancy is applied to PCUMs and ETMEs. In practice as many spare units in the spare module as there are active units in one module. through hot-standby or spare device methods a dedicated spare unit is kept ready to take over the tasks of its active pair in case the active unit should fail. N+M means that for a given group of N active units there is a set of M backup units.e.HW redundancy The units participating in the switching functions or recording of statistical data are backed up according to the 2N redundancy principle: i.

Some functional units have no redundancy at all. the traffic of a unit which fails is redistributed between the units which remain active. 1+1 redundancy is applied to PTUM and it means there are two active units performing a similar task and this duplication allows one unit to fail without disrupting the service. This is because a failure in them does not prevent the function or cause any drop in the capacity.HW redundancy SN+ redundancy is applied to ETMAs. SN+ is also called 'Load sharing'. . and it means that within a group of active units.

.

L2 Redundancy The recommended method to avoid L2 loops between Site Equipment and multicontroller modules is to have L3 hop between Site Equipment nodes: The L3 hop breaks the Broadcast domain for the multicontroller VLANs visible to the Site Equipment. Sub interfaces enables to divide a physical interface into multiple logical interfaces that are tagged with different VLAN IDs. Spanning Tree. In this situation the L2 connectivity needed between Site Equipment for HSRP / VRPP is provided through the multicontroller LANs. More information about exact configuration details can be found from the BSC Site IP configuration document . preventing VLANs used by mcBSC on the redundant link or using routed VLAN tagged (encapsulation dot1q) sub-interfaces with LAG. If an L2 hop between Site Equipment is nevertheless used. VLANs are interface local when using routed sub-interfaces and are not treated as traditional VLANs received from ports configured as switching ports. the user must take care that creation of L2 loops is prevented by another suitable method or protocol e.g.

.

An alarm is activated by closing the alarm circuit with an external switch. Physical interface for these external alarms are on the front panel. The pins of the RJ-45 connectors shall be connected according to the following table. . Two external alarm input pairs are available in each box.External alarms The BCN module provides eight external alarm interfaces on two RJ45 connectors in the front panel. Both closing the loop and opening it will generate an IPMI event to the HW management system.