mcBSC training for BSC TS (BSC up and running)
Antti Palojärvi
For internal use
Unique document identifier (ID) / Version number / Life cycle status
1
© Nokia Siemens Networks 2012
Dept. / Author / Date
mcBSC up and running
•
In this document it is briefly described all the steps what are needed to get 2
module mcBSC up and running.
• Referred documents
•
•
•
•
•
•
•
•
•
Multicontroller Site IP Connectivity Guidelines DN0982823
BSC Site IP Configuration Principles DN0982835
Commissioning a standalone mcBSC
Commissioning mcBSC and mcTC DN0982859
Creating and Managing mcBSC Hardware DN0982847
BSS Integration DN9812243
Multicontroller BSC and Multicontroller TC Installation Quick Guide DN05209732
All the steps are not necessarily needed in case SW is already been preinstalled in factory.
Also all the printouts are straight from working environment located in Tampere TS lab.
For internal use
Unique document identifier (ID) / Version number / Life cycle status
2
© Nokia Siemens Networks 2012
Dept. / Author / Date
BCN/BOC-A esw manual upgrade
For internal use
Unique document identifier (ID) / Version number / Life cycle status
3
© Nokia Siemens Networks 2012
Dept. / Author / Date
BCN/BOC-A esw manual upgrade 1/6
•
•
Currently with the latest MP’s esw upgrade to BCN and BOC-A units is
possible to do via MML command class ZWD.
Check the current esw of BCN and BOC-A units.
root@BCNMB-A:~# sw_fw_versioninfo
Active U-Boot Version 3.1.1 (in flash 0)
This part of the printout tells the current esw SW of BCN
Backup U-Boot Version 3.1.1 (in flash 1)
LMP Version 3.1.1
PCB Version A103-2/A103-3/A103-4/A103-5/A103-6/A103-7
LED CPLD Version 05
PCI-LPC bridge XP2 Version 03
VCMC Version 3.1.1
PWR1014 Version 0007
FRUD Version 3.1.1
Part Number C111721.A1A
...
...
This part of the printout tells the current esw SW of BOC-A in cpu slot 4
Add-in Card 4
MMC Version 3.1.1
Part Number C111723.A1A
BCNOC-A PCPL Version 0.3.0
BCNOC-A OCTF Version 3.1.1
BCNOC-A FRUD Version 3.1.1
For internal use
Unique document identifier (ID) / Version number / Life cycle status
4
© Nokia Siemens Networks 2012
Dept. / Author / Date
BCN/BOC-A esw manual upgrade 2/6
•
•
If manual upgrade is needed like in case very old box is taken into use
upgrade can be done from USB memory stick.
Proven working steps for upgrading esw is 1.4->1.8.->2.0->2.4->2.7.1->3.1.1.
1. Before the upgrade save following data from BCN.
•
•
•
Swtich configurations (main/ext)
•
With WinSCP or straight from terminal
LMP IP configuration
root@BCNMB-A:~#
root@BCNMB-A:~#
root@BCNMB-A:~#
root@BCNMB-A:~#
cat /etc/sysconfig/network-scripts/ifcfg-eth0
cat /etc/sysconfig/network
cat /etc/sysconfig/network-scripts/ifcfg-eth0.800
ifconfig -a
root@BCNMB-A:~#
root@BCNMB-A:~#
root@BCNMB-A:~#
root@BCNMB-A:~#
mch_cli
mch_cli
mch_cli
mch_cli
HW management info
For internal use
Unique document identifier (ID) / Version number / Life cycle status
5
© Nokia Siemens Networks 2012
Dept. / Author / Date
GetNodeNumber
GetRackNumber
GetFRUPCIeRC
GetPCIeRC
BCN/BOC-A esw manual upgrade 3/6
•
Message Bus & boot script configuration
root@BCNMB-A:~# mch_cli FRU info 0x20
root@BCNMB-A:~# cat /etc/ipmi/mch.conf
•
Current SW info
root@BCNMB-A:~# sw_fw_versioninfo
2. For the BCN & BOC-A upgrade prepare usb memory stick that has the
correct esw. (from isource/sharenet)
•
Following files need to be present
autorun.scr
autorun.scr.md5
ncp20000.dtb
ncp20000.dtb.md5
ncp20000-initrd-upgrade-3.1.1.gz.uboot
ncp20000-initrd-upgrade-3.1.1.gz.uboot.md5
setip.sh
setip.sh.md5
uImage
uImage.md5
For internal use
Unique document identifier (ID) / Version number / Life cycle status
6
© Nokia Siemens Networks 2012
Dept. / Author / Date
BCN/BOC-A esw manual upgrade 4/6
3. Check that LMP has valid date settings
root@BCNMB-A:~# date
Tue Sep 25 11:13:05 UTC 2012
If not okay give valid date
root@BCNMB-A:~# date –set=”25 sep 2012 11:14:00”
4. Disable OMU in M1 to prevent DX diagnostic for the units during the
upgrade
root@BCNMB-A:~#
5.
mch_cli Deactivate cpu8
Plug the USB stick into BCN and give power restart.
•
At first SW will be copied into LMP.
•
After succesfull copy actual upgrade process will start.
•
If upgare does not start automatically script can be started manually (check the date before this).
root@BCNMB-A:~# /opt/upgrade/upgrade.sh
•
From the menu select ”Fully automatic upgrade”
For internal use
Unique document identifier (ID) / Version number / Life cycle status
7
© Nokia Siemens Networks 2012
Dept. / Author / Date
BCN/BOC-A esw manual upgrade 5/6
6. Upgrade procedure can be followed from log files
Progress
root@BCNMB-A:~# cat /tmp/autoupgrade.log
Result
root@BCNMB-A:~# cat /opt/upgrade/autorun.log
7. Once upgrade is complete remove the USB stick and give power restart
8. After BCN has restarted to the new SW check the SW config
root@BCNMB-A:~# sw_fw_versioninfo
Active U-Boot Version 3.1.1 (in flash 0)
Backup U-Boot Version 3.1.1 (in flash 1)
LMP Version 3.1.1
PCB Version A103-2/A103-3/A103-4/A103-5/A103-6/A103-7
LED CPLD Version 05
PCI-LPC bridge XP2 Version 03
VCMC Version 3.1.1
PWR1014 Version 0007
FRUD Version 3.1.1
Part Number C111721.A1A
…
9. Enable OMU
root@BCNMB-A:~# mch_cli Activate cpu8
For internal use
Unique document identifier (ID) / Version number / Life cycle status
8
© Nokia Siemens Networks 2012
Dept. / Author / Date
BCN/BOC-A esw manual upgrade 6/6
10. Modify the mnt/fastpath2/module/post.soc with vi editor
root@BCNMB-A:~# cat /mnt/fastpath2/module/post.soc
echo "/mnt/fastpath2/module/post.soc"
linkscan interval=10000
#trunk add id=0 pbmp=0x3000000
!Trunk add line has to be commented
For internal use
Unique document identifier (ID) / Version number / Life cycle status
9
© Nokia Siemens Networks 2012
Dept. / Author / Date
BJC-A esw manual upgrade
For internal use
Unique document identifier (ID) / Version number / Life cycle status
10
© Nokia Siemens Networks 2012
Dept. / Author / Date
BJC-A esw manual upgrade
•
•
•
Currently with the latest MP’s esw(GA) upgrade to BJC-A units is possible to
do via MML command class ZWD.
If manual upgrade is needed like in case very old box is taken into use
upgrade can be done from USB memory stick.
GA SW need to be updated step by step
• For detailed instructions refer attached document
For internal use
Unique document identifier (ID) / Version number / Life cycle status
11
© Nokia Siemens Networks 2012
Dept. / Author / Date
BJC-A BIOS settings
For internal use
Unique document identifier (ID) / Version number / Life cycle status
12
© Nokia Siemens Networks 2012
Dept. / Author / Date
BJC-A BIOS settings
1. Connect to the BIOS in each BJC-A module and configure the BIOS as
instructed in the Commissioning mcBSC and mcTC document.
• BIOS of the BJC-A unit can be accessed only from restart prompt of the
unit.
• Correct steps:
1. Restart the unit with mch_cli (deactivate -> activate)
2. Immediately open connection to the same unit (minicom)
3. Wait for the ” Press <ESC> or <F2> to enter setup”
4. Immediately press ESC and BIOS terminal should open.
•
TIP!
•. BIOS terminal alignment is really confusing with minicom access
from LMP.
•. Better way is to use direct port access via IP mgmt interface
For internal use
Unique document identifier (ID) / Version number / Life cycle status
13
© Nokia Siemens Networks 2012
Dept. / Author / Date
Switch config restore
For internal use
Unique document identifier (ID) / Version number / Life cycle status
14
© Nokia Siemens Networks 2012
Dept. / Author / Date
Switch config restore 1/2
•
•
If text based configuration file with binary header is available upload the file
into correct /mnt/fastpath folder with WinSCP (main: fastpath, ext:fastpath2)
Then apply the new script in correct switch. (Stated in training doc1)
(Broadcom FASTPATH Switching) >
(Broadcom FASTPATH Switching) >ena
Password:
(Broadcom FASTPATH Switching) #clear config
Are you sure you want to clear the configuration? (y/n)y
Clearing configuration. Please wait for login prompt.
(Unit 1)>m20 SFP+1 (phy21) DOWN, set secondary via SFP+2 (phy22)
m20 SFP+2 (phy22) DOWN, set secondary via SFP+1 (phy21)
User:admin
Password:
(Broadcom FASTPATH Switching) >
(Broadcom FASTPATH Switching) #script apply Husabox2main_190912.scr
Are you sure you want to apply the configuration script? (y/n)y
Configuration script 'Husabox2main_190912.scr' applied.
(HusaBox2MainSwitch) #
(HusaBox2MainSwitch) #write mem
This operation may take a few minutes.
Management interfaces will not be available during this time.
Are you sure you want to save? (y/n) y
Config file 'startup-config' created successfully .
Configuration Saved!
(HusaBox2MainSwitch) #
For internal use
Unique document identifier (ID) / Version number / Life cycle status
15
© Nokia Siemens Networks 2012
Dept. / Author / Date
Switch config restore 2/2
•
•
Configuration can be also written (copy paste) directly into switch terminal.
Default configuration scripts for M1 and M2 attached.
• These can be applied with copy paste direclty into switch prompt in
priviledge mode.
• Application VLAN’s and external interfaces are not defined as well the
prompt name.
SA_main1.txt
•
SA_main2.txt
SA_Ext_1& 2
Detailed description of switch related files can be found from MultiController
Site IP Connectivity Guidelines & BSC Site IP Configuration Principles.
For internal use
Unique document identifier (ID) / Version number / Life cycle status
16
© Nokia Siemens Networks 2012
Dept. / Author / Date
FRU data configuration
For internal use
Unique document identifier (ID) / Version number / Life cycle status
17
© Nokia Siemens Networks 2012
Dept. / Author / Date
FRU data configuration 1/5
Rack & Node number
1. Check Rack & Node number definition in FRU
BOX 1 (M1)
root@BCNMB-A:~#
65
root@BCNMB-A:~#
1
root@BCNMB-A:~#
BOX 2 (M2)
root@BCNMB-A:~#
65
root@BCNMB-A:~#
1
root@BCNMB-A:~#
mch_cli GetRackNumber
mch_cli GetNodeNumber
mch_cli GetRackNumber
mch_cli GetNodeNumber
Rack number is the ascii coordinate of Rack. (eg. A=65, F = 70)
Node number is the module number in mcBSC.
Example OMU box M1 cartridge in rack A is created with 1A1-0
2. Modify
rack & node number if needed
BOX 1 (M1)
root@BCNMB-A:~# mch_cli SetRackNumber 65
root@BCNMB-A:~# mch_cli SetNodeNumber 1
BOX 2 (M2)
root@BCNMB-A:~# mch_cli SetRackNumber 65
root@BCNMB-A:~# mch_cli SetNodeNumber 2
For internal use
Unique document identifier (ID) / Version number / Life cycle status
18
© Nokia Siemens Networks 2012
Dept. / Author / Date
FRU data configuration 2/5
Root complex
3. Check root complex configuration
BOX 1 (M1)
root@BCNMB-A:~#
Slot8
root@BCNMB-A:~#
RC: 8
root@BCNMB-A:~#
BOX 2 (M2)
root@BCNMB-A:~#
LMP
root@BCNMB-A:~#
RC: 0
root@BCNMB-A:~#
mch_cli GetFRUPCIeRC
mch_cli GetPCIeRC
mch_cli GetFRUPCIeRC
mch_cli GetPCIeRC
Unit in M1 slot 8 (OMU) has root complex. In other modules it is configured to LMP.
4. Modify root complex if needed
BOX 1 (M1)
root@BCNMB-A:~# mch_cli SetFRUPCIeRC slot8
root@BCNMB-A:~# mch_cli SetPCIeRC 8
BOX 2 to 8 (M2-M8)
root@BCNMB-A:~# mch_cli SetFRUPCIeRC LMP
root@BCNMB-A:~# mch_cli SetPCIeRC 0
Unit in M1 slot 8 (OMU) has root complex. In other modules it is configured to LMP.
For internal use
Unique document identifier (ID) / Version number / Life cycle status
19
© Nokia Siemens Networks 2012
Dept. / Author / Date
FRU data configuration 3/5
MB address
5. Check MB address definitions of BJC-A units
M1
root@BCNMB-A:~# mch_cli FRU info 0x20
[NSN.EMB Addresses]
Vendor Format Version = 0
Slot 1 = 0x0004
//MCMU 0
Slot 2 = 0x0049
//BCXU 0
Slot 3 = 0x004A
//BCXU 1
Slot 4 = 0xFFFF
Slot 5 = 0xFFFF
Slot 6 = 0xFFFF
Slot 7 = 0xFFFF
Slot 8 = 0x0000
//OMU
M2
root@BCNMB-A:~# mch_cli FRU info 0x20
[NSN.EMB Addresses]
Vendor Format Version = 0
Slot 1 = 0x0005
//MCMU 1
Slot 2 = 0x004B
//BCXU 2
Slot 3 = 0x004C
//BCXU 3
Slot 4 = 0xFFFF
Slot 5 = 0xFFFF
Slot 6 = 0xFFFF
Slot 7 = 0xFFFF
Slot 8 = 0xFFFF
For internal use
Unique document identifier (ID) / Version number / Life cycle status
20
© Nokia Siemens Networks 2012
Dept. / Author / Date
FRU data configuration 4/5
MB address
6. Define MB addresses of CPU units in Box1 (M1) if needed
MCMU-0 in slot 1:
ipmitool -I lan -H 127.0.0.1 -U admin -P admin raw 0x2e 0x20 0x2a 0x6f 0x00 0x2a 0x6f 0x00 0x07 0x00 0x01 0x02 0x00 0x04
BCXU-0 in slot 2:
ipmitool -I lan -H 127.0.0.1 -U admin -P admin raw 0x2e 0x20 0x2a 0x6f 0x00 0x2a 0x6f 0x00 0x07 0x00 0x03 0x02 0x00 0x49
BCXU-1 in slot 3:
ipmitool -I lan -H 127.0.0.1 -U admin -P admin raw 0x2e 0x20 0x2a 0x6f 0x00 0x2a 0x6f 0x00 0x07 0x00 0x05 0x02 0x00 0x4A
OMU in slot 8:
ipmitool -I lan -H 127.0.0.1 -U admin -P admin raw 0x2e 0x20 0x2a 0x6f 0x00 0x2a 0x6f 0x00 0x07 0x00 0x0f 0x02 0x00 0x00
Refresh IPMI FRU:
mch_cli FRU refresh 0x20
Check MB addresses with mch_cli:
mch_cli FRU info 0x20
For internal use
Unique document identifier (ID) / Version number / Life cycle status
21
© Nokia Siemens Networks 2012
Dept. / Author / Date
FRU data configuration 5/5
MB address
7. Define MB addresses of CPU units in Box2 (M2) if needed
MCMU-1 in slot 1:
ipmitool -I lan -H 127.0.0.1 -U admin -P admin raw 0x2e 0x20 0x2a 0x6f 0x00 0x2a 0x6f 0x00 0x07 0x00 0x01 0x02 0x00 0x05
BCXU-2 in slot 2:
ipmitool -I lan -H 127.0.0.1 -U admin -P admin raw 0x2e 0x20 0x2a 0x6f 0x00 0x2a 0x6f 0x00 0x07 0x00 0x03 0x02 0x00 0x4B
BCXU-3 in slot 3:
ipmitool -I lan -H 127.0.0.1 -U admin -P admin raw 0x2e 0x20 0x2a 0x6f 0x00 0x2a 0x6f 0x00 0x07 0x00 0x05 0x02 0x00 0x4C
Refresh IPMI FRU:
mch_cli FRU refresh 0x20
Check MB addresses with mch_cli:
mch_cli FRU info 0x20
For internal use
Unique document identifier (ID) / Version number / Life cycle status
22
© Nokia Siemens Networks 2012
Dept. / Author / Date
Boot script & boot order
For internal use
Unique document identifier (ID) / Version number / Life cycle status
23
© Nokia Siemens Networks 2012
Dept. / Author / Date
Boot script & Boot order 1/2
•
PIU’s bootscript and correct boot sequence are defined in
/etc/ipmi/mch.conf file
• Use vi editor to configure the file in each module
• Correct boot sequence in M1 module is 8 1 2 3 4 5 6 7 which meas
that OMU will be restarted first. For the other modules sequence is 1
2 3 4 5 6 7 8.
• Correct bootscript for the BOC-A units is 17 and for the BJC-A units
99.
• Also check
that the
first octect in each card config for BOC-A units is
root@BCNMB-A:~#
vi /etc/ipmi/mch.conf
0x18, notBasic
0x08.vi commands:
a
Esc
:wq!
:q!
i
 Enter to edit mode (Add new text)
 Enter from edit mode to command mode
 Save changes and exit from vi
 Exit from vi without saving changes
Insert text before cursor, until <Esc> hit
For internal use
Unique document identifier (ID) / Version number / Life cycle status
24
© Nokia Siemens Networks 2012
Dept. / Author / Date
Boot script & Boot order 2/2
•
Example of /etc/ipmi/mch.conf file
root@BCNMB-A:~# cat /etc/ipmi/mch.conf
######################
# Global Configuration
######################
1.bootscript=99
# delay between cards
card_between_delay=5 5 5 5 5 5 5 5
# Data bytes
# byte1:
#
[6] pci boot
#
[5] failsafe
#
[4] clock source
#
[3-0] mul
# byte2:
#
[7] boot flash
#
[6] buffer dir
#
[5-0] reserverd
# byte3: reserved
# byte4: reserved
# byte5-21: reserved
1.card_conf=0x08 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x0
0 0x00 0x00 0x00 0x00 0x00 0x00 0x00
# boot sequence
boot_order=8 1 2 3 4 5 6 7
######################
# CPU Add-in Card #1
######################
# Boot Script
# 0: Rerserved and do nothgin
# 1-32: NSN
# 33: DEMI burn-in
# 34: hw ddr2
# 35: traf_gen_freeze
# 36: U-Boot recover
# 37: U-Boot bootloader_flash_update
# 38: Linux linux_flash_update
# 61-68: Manufacture burn-in program
# 70: Run Linux
# 80: Net boot defined by NSN
For internal use
Unique document identifier (ID) / Version number / Life cycle status
25
© Nokia Siemens Networks 2012
Dept. / Author / Date
# enable
1.enable=1
LMP IP configuration
For internal use
Unique document identifier (ID) / Version number / Life cycle status
26
© Nokia Siemens Networks 2012
Dept. / Author / Date
LMP IP configuration
•
•
Configure IP related files with vi editor.
BCN Management interface (used for LMP terminal connection)
1.
2.
•
/etc/sysconfig/network-scripts/ifcfg-eth0 in M1
DEVICE=eth0
BOOTPROTO=static
BROADCAST=10.41.81.31
IPADDR=10.41.81.15
NETMASK=255.255.255.224
ONBOOT=yes
/etc/sysconfig/network in M1
NETWORKING=yes
HOSTNAME=ncp20000
FORWARD_IPV4=false
GATEWAY="10.41.81.1"
NOZEROCONF=yes
This is management port configuration.
In this example own subnet used for management connections
LMP vlan 800 interface (mcBSC platform internal management)
1. /etc/sysconfig/network-scripts/ifcfg-eth0.800 in M1
DEVICE=eth0.800
VLAN=yes
BOOTPROTO=dhcp
ONBOOT=yes
PERSISTENT_DHCLIENT=Y
DHCLIENTARGS="-nw"
For internal use
Unique document identifier (ID) / Version number / Life cycle status
27
This is management port configuration.
In this example own subnet used for management connections
© Nokia Siemens Networks 2012
Dept. / Author / Date
This is IMPI vlan configuration.
LMP uses dhcp to get adress from OMU.
LMP IP configuration
•
•
Configure IP related files with vi editor.
BCN Management interface (used for LMP terminal connection)
1.
2.
•
/etc/sysconfig/network-scripts/ifcfg-eth0 in M2
DEVICE=eth0
BOOTPROTO=static
BROADCAST=10.41.81.31
IPADDR=10.41.81.16
NETMASK=255.255.255.224
ONBOOT=yes
/etc/sysconfig/network in M2
NETWORKING=yes
HOSTNAME=ncp20000
FORWARD_IPV4=false
GATEWAY="10.41.81.1"
NOZEROCONF=yes
This is management port configuration.
In this example own subnet used for management connections
LMP vlan 800 interface (mcBSC platform internal management)
1. /etc/sysconfig/network-scripts/ifcfg-eth0.800 in M2
DEVICE=eth0.800
VLAN=yes
BOOTPROTO=dhcp
ONBOOT=yes
PERSISTENT_DHCLIENT=Y
DHCLIENTARGS="-nw"
For internal use
Unique document identifier (ID) / Version number / Life cycle status
28
This is management port configuration.
In this example own subnet used for management connections
© Nokia Siemens Networks 2012
Dept. / Author / Date
This is IMPI vlan configuration.
LMP uses dhcp to get adress from OMU.
LMP IP configuration
4. Restart the interfaces & check the configuration. (in both modules)
root@BCNMB-A:~# ifdown eth0
root@BCNMB-A:~# ifup eth0
root@BCNMB-A:~# ifdown eth0.800
Removed VLAN -:eth0.800:root@BCNMB-A:~# ifup eth0.800
Added VLAN with VID == 800 to IF -:eth0:Determining IP information for eth0.800... done.
root@BCNMB-A:~#
root@BCNMB-A:~# ifconfig
...
eth0
Link encap:Ethernet HWaddr 00:D0:C9:BB:AE:1D
inet addr:10.41.81.16 Bcast:10.41.81.31 Mask:255.255.255.224
inet6 addr: fe80::2d0:c9ff:febb:ae1d/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1205075 errors:0 dropped:0 overruns:0 frame:0
TX packets:1189921 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:101678521 (96.9 MiB) TX bytes:154711208 (147.5 MiB)
Base address:0xe000
eth0.800
Link encap:Ethernet HWaddr 00:D0:C9:BB:AE:1D
inet addr:10.10.10.11 Bcast:10.10.10.255 Mask:255.255.255.0
inet6 addr: fe80::2d0:c9ff:febb:ae1d/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:18 errors:0 dropped:0 overruns:0 frame:0
TX packets:23 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1430 (1.3 KiB) TX bytes:1846 (1.8 KiB)
For internal use
Unique document identifier (ID) / Version number / Life cycle status
29
© Nokia Siemens Networks 2012
Dept. / Author / Date
If LMP does not get IP adress from OMU
OMU is not yet in WO state
Rack & Node configurations are not in order
ifcg-eth0.800 file not in order
- Vlan 800 config in main switches are not in order.
LMP boot script installation
For internal use
Unique document identifier (ID) / Version number / Life cycle status
30
© Nokia Siemens Networks 2012
Dept. / Author / Date
LMP Boot script installation
•
LMP Boot script controls the adding card restarts during LMP restart.
1. Download LMP boot script from isource.
isource link
Currently in use revision 2881 dated 30.9.2011
2.
Copy script files to LMP with WinSCP.
"resetNodes.sh" to directory /etc/rc.d/init.d/
"nodeReset.sh" to directory /usr/bin/
3.
Change the modules executable if needed
root@BCNMB-A:~# cd /usr/bin
root@BCNMB-A:/usr/bin# chmod +x+x+x nodeReset.sh
root@BCNMB-A:/usr/bin# cd /etc/rc.d/init.d/
root@BCNMB-A:/etc/rc.d/init.d# chmod +x+x+x resetNodes.sh
root@BCNMB-A:/etc/rc.d/init.d# cd
root@BCNMB-A:~#
For internal use
Unique document identifier (ID) / Version number / Life cycle status
31
© Nokia Siemens Networks 2012
Dept. / Author / Date
LMP Boot script installation
1. Add service “resetNodes.sh” into the configuration.
root@BCNMB-A:~# cd /etc/rc.d/init.d/
root@BCNMB-A:/etc/rc.d/init.d# chkconfig --add resetNodes.sh
root@BCNMB-A:/etc/rc.d/init.d# cd
root@BCNMB-A:~#
2.
Check that resetNodes is added properly
root@BCNMB-A:~#
cracklibd
crond
dhcpd
dhcrelay
netconsole
netfs
network
ntpd
rdisc
resetNodes.sh
sshd
syslog
watchdog
xinetd
chkconfig --list
0:off
1:off
2:on
0:off
1:off
2:on
0:off
1:off
2:off
0:off
1:off
2:off
0:off
1:off
2:off
0:off
1:off
2:off
0:off
1:off
2:on
0:off
1:off
2:off
0:off
1:off
2:off
0:off
1:off
2:off
0:off
1:off
2:on
0:off
1:off
2:on
0:off
1:off
2:off
0:off
1:off
2:off
For internal use
Unique document identifier (ID) / Version number / Life cycle status
32
© Nokia Siemens Networks 2012
Dept. / Author / Date
3:on
3:on
3:off
3:off
3:off
3:on
3:on
3:on
3:off
3:on
3:on
3:on
3:on
3:on
4:on
4:on
4:off
4:off
4:off
4:on
4:on
4:off
4:off
4:off
4:on
4:on
4:off
4:on
5:on
5:on
5:off
5:off
5:off
5:on
5:on
5:off
5:off
5:off
5:on
5:on
5:off
5:on
6:off
6:off
6:off
6:off
6:off
6:off
6:off
6:off
6:off
6:off
6:off
6:off
6:off
6:off
Cabling
For internal use
Unique document identifier (ID) / Version number / Life cycle status
33
© Nokia Siemens Networks 2012
Dept. / Author / Date
Cabling
•
•
Verify that interconnection cables are connected as defined in Multicontroller
BSC and Multicontroller TC Installation Quick Guide.
If cables from extension switches of M1 and M2 are already connected to site
equipment it is good idea to shut down the interface at site equipment side
until all the configurations are done.
For internal use
Unique document identifier (ID) / Version number / Life cycle status
34
© Nokia Siemens Networks 2012
Dept. / Author / Date
HigGig script
For internal use
Unique document identifier (ID) / Version number / Life cycle status
35
© Nokia Siemens Networks 2012
Dept. / Author / Date
HiGig script 1/3
Check
•
Check current HiGig configuration
Used script and xmesh version
root@BCNMB-A:~# cat /opt/cluster/m10/init.soc
echo
echo init mesh6 ver 0.3.9, module 10
0:port 0x1fffffff en=f
0:local module 10
0:mod port 0 29 my_modid=@module
0:mod modport_map 0x0 7424 higig_port_bitmap=0x00000000
0:mod src_modid_block 0x1500 256 port_block_mask_bitmap=0x1fffffff
0:mod src_modid_block 0x1600 256 port_block_mask_bitmap=0x1fffffff
0:mod src_modid_block 0x1700 256 port_block_mask_bitmap=0x1fffffff
0:mod src_modid_block 0x1800 256 port_block_mask_bitmap=0x1fffffff
0:mod src_modid_block 0x0100 256 port_block_mask_bitmap=0x1fffffff
root@BCNMB-A:~#
Module specific fastapath link(m10 for module 1, m20 for module2…)
root@BCNMB-A:~# ls -la /mnt/fastpath/module
lrwxrwxrwx 1 root root 16 Aug 29 14:13 /mnt/fastpath/module -> /opt/cluster/m10
root@BCNMB-A:~#
post.soc file
root@BCNMB-A:~# cat /opt/cluster/m10/post.soc | grep "0x001fffe4"
#0:port 0x001fffe4 enc=ieee sp=10000 an=off en=t
root@BCNMB-A:~#
Line “0:port 0x001fffe4 enc=ieee sp=10000 an=off en=t” has to commented with #
For internal use
Unique document identifier (ID) / Version number / Life cycle status
36
© Nokia Siemens Networks 2012
Dept. / Author / Date
HiGig script 2/3
Installation
•
Install HiGig if needed
1. Copy HiGig file into /opt folder with WinSCP
example: nsn.23a91279e4d4f4f6206e0d470633cbdc2462d7a1.backplane-0.3.9-1.tar.gz
2.
Unzip the HiGig file in LMP
root@BCNMB-A:/opt# tar -xzf nsn.23a91279e4d4f4f6206e0d470633cbdc2462d7a1.backplane-0.3.9-1.tar.gz
root@BCNMB-A:/opt#
3.
Copy HiGig files into correct locations
4.
root@BCNMB-A:/opt# cp backplane-0.3.9/mesh backplane-0.3.9/xmesh /usr/bin
root@BCNMB-A:/opt# cp backplane-0.3.9/xmeshd /etc/init.d
Copy
mesh6.xml into
folder with WinSCP
root@BCNMB-A:/opt#
cp /opt
backplane-0.3.9/*.xml
.
•
•
mesh6.xml used in upto 6 BCN environments
pmesh8.xml used in 7 & 8 BCN environments and xmeshd has to be added into startup list.
For internal use
Unique document identifier (ID) / Version number / Life cycle status
37
© Nokia Siemens Networks 2012
Dept. / Author / Date
HiGig script 3/3
Installation
5. Check that following line is commented away in mesh6.xml
root@BCNMB-A:/opt#
#0:port 0x001fffe4
#0:port 0x001fffe4
#0:port 0x001fffe4
#0:port 0x001fffe4
#0:port 0x001fffe4
#0:port 0x001fffe4
root@BCNMB-A:/opt#
cat mesh6.xml | grep "0:port 0x001fffe4 enc=ieee sp=10000 an=off en=t"
enc=ieee sp=10000 an=off en=t
enc=ieee sp=10000 an=off en=t
enc=ieee sp=10000 an=off en=t
enc=ieee sp=10000 an=off en=t
enc=ieee sp=10000 an=off en=t
enc=ieee sp=10000 an=off en=t
# in every line
6. Install HigGig
Run mesh by using proper box specific attributes
root@BCNMB-A:/opt# mesh -x mesh6.xml -m 10
Box1 m=10, box2 m=20, box3 m=30...
7. Take HiGig into use
!High Cabling and switch configuration has to be on order before this step
Reboot BCN
root@BCNMB-A:/opt# reboot
Or
root@BCNMB-A:/opt# touch var/run/cluster/ext/post.soc
For internal use
Unique document identifier (ID) / Version number / Life cycle status
38
© Nokia Siemens Networks 2012
Dept. / Author / Date
BSC package
For internal use
Unique document identifier (ID) / Version number / Life cycle status
39
© Nokia Siemens Networks 2012
Dept. / Author / Date
BSC package
•
•
•
Current version of BCN OMU does not have visibility to USB port in front
panel.
Therefore the convenient way to copy the BSC package to WDU is to do the
copying in FlexiBSC from U0 to W0 as in this example.
!Note After P8 factory delivered mcBSC’s have SW in the WDU.
For internal use
Unique document identifier (ID) / Version number / Life cycle status
40
© Nokia Siemens Networks 2012
Dept. / Author / Date
BSC package
•
Steps
1. Install the disk into Flexi BSC.
2. Format the disk.
ZMID:W0-<DISK_NAME>.DIR,FF,2,<INITIALS>
3. Create the directories.
ZMCD:W0-/ASF_2_18_0,50
ZMCD:W0-/SCMANA,FF
ZMCD:W0-/ANSI,FF
ZMCD:W0-/ETSI,FF
ZMCD:W0-/ASF_2_18_0/BLCODE,900
ZMCD:W0-/ASF_2_18_0/MMDIRE,900
ZMCD:W0-/ASF_2_18_0/LFILES,900
ZMCD:W0-/ASF_2_18_0/CDTEMP,FF
ZMCD:W0-/ASF_2_18_0/ASWDIR,FF
ZMCD:W0-/ASF_2_18_0/CONVPR,FF
ZMCD:W0-/ASF_2_18_0/LICENCE,200
ZMCD:W0-/ASF_2_18_0/WEBFIL,FF
ZMCD:W0-/ASF_2_18_0/WEBFIL/APPS,FF
ZMCD:W0-/ASF_2_18_0/WEBFIL/CGI,FF
ZMCD:W0-/ASF_2_18_0/WEBFIL/HTDOCS,FF
ZMCD:W0-/ASF_2_18_0/WEBFIL/SCRIPT,FF
ZMCD:W0-/ASF_2_18_0/WEBFIL/ICONS,FF
ZMCD:W0-/ASF_2_18_0/WEBFIL/GRAPHICS,FF
For internal use
Unique document identifier (ID) / Version number / Life cycle status
41
© Nokia Siemens Networks 2012
Dept. / Author / Date
BSC package
3. Attach USB stick that has complete package into OMU of FlexiBSC
•
•
4.
In this example USB root contains valid BOLEROGX.IMG
Also /ETSI & /ANSI folders contain PRFILE and FIFILE
Copy the files from USB to W0
ZMMS:U0-/SCMANA/*.*,W0-/SCMANA/
ZMMS:U0-/*.*,W0-/
ZMMS:U0-/ETSI/*.*,W0-/ETSI/
ZMMS:U0-/ANSI/*.*,W0-/ANSI/
ZMMS:U0-/ASF_2_18_0/LFILES/*.*,W0-/ASF_2_18_0/LFILES/
ZMMS:U0-/ASF_2_18_0/BLCODE/*.*,W0-/ASF_2_18_0/BLCODE/
ZMMS:U0-/ASF_2_18_0/MMDIRE/*.*,W0-/ASF_2_18_0/MMDIRE/
ZMMS:U0-/ASF_2_18_0/ASWDIR/*.*,W0-/ASF_2_18_0/ASWDIR/
ZMMS:U0-/ASF_2_18_0/WEBFIL/*.*,W0-/ASF_2_18_0/WEBFIL/
ZMMS:U0-/ASF_2_18_0/WEBFIL/CGI/*.*,W0-/ASF_2_18_0/WEBFIL/CGI/
ZMMS:U0-/ASF_2_18_0/WEBFIL/HTDOCS/*.*,W0-/ASF_2_18_0/WEBFIL/HTDOCS/
ZMMS:U0-/ASF_2_18_0/WEBFIL/SCRIPT/*.*,W0-/ASF_2_18_0/WEBFIL/SCRIPT/
ZMMS:U0-/ASF_2_18_0/WEBFIL/ICONS/*.*,W0-/ASF_2_18_0/WEBFIL/ICONS/
ZMMS:U0-/ASF_2_18_0/WEBFIL/GRAPHICS/*.*,W0-/ASF_2_18_0/WEBFIL/GRAPHICS/
For internal use
Unique document identifier (ID) / Version number / Life cycle status
42
© Nokia Siemens Networks 2012
Dept. / Author / Date
BSC package
5. Remove the WDU from FlexiBSC and attach it to M1
6. Restart the cpu8 and log into OMU minidebugger by pressing ‘m’ during reboot in
OMU’s minicom session.
root@BCNMB-A:~# mch_cli Deactivate cpu8
Set fru activation policy: clear deactivation lock
bit!
deactivate: Command completed normally
root@BCNMB-A:~# mch_cli Activate cpu8
Clear locked bit!
done: Command completed normally
Set FRU Activation!
done: Command completed normally
root@BCNMB-A:~#minicom cpu8
7. In minidebugger check that OMU sees the WDU and content in W0
ZMX:W0-/
•
8.
If OMU does not see the W0 run the recovery script described in exercise doc and go
back to step 6.
In minidebugger format W1
ZMID:W1-<DISK_NAME>.DIR,FF,2,<INITIALS>
For internal use
Unique document identifier (ID) / Version number / Life cycle status
43
© Nokia Siemens Networks 2012
Dept. / Author / Date
BSC package
9. In minidebugger copy the PRFILE and FIFLE to LFILES
ZMM:W0-/xxxx/*.*,W0-/ASF_2_18_0/LFILES/
Xxxx = ANSI or ETSI
10. If needed patch the NE number to APPARA
ZMVL:W1-/ASF_2_18_0/BLCODE/APPARAGX.IMG,4,B0
ZMVL:W1-/ASF_2_18_0/BLCODE/APPARAG2.IMG,4,B0
You can move to the correct location in the file (block B0) with the arrow keys. At block
B0, the pre-entered value is:
00B0: 45 23 01
If the delivery’s NE number is, for example, 102345, it must be written as following into
the files:
00B0: 45 23 10
Exit the editing mode by pressing <CTRL> <C>, after which the program prompts you to
confirm the modifications made.
WRITE TO DISK Y/N? Y
Confirm the changes by answering
Y
<ENTER>
11. In minidebugger copy the whole content of W0 to W1
ZMMD:W0-/*.*:*,W1-/
For internal use
Unique document identifier (ID) / Version number / Life cycle status
44
© Nokia Siemens Networks 2012
Dept. / Author / Date
BSC package
12. Restart the OMU with “ZAUL”
13. If OMU does not find the disks try recovery scripts stated at the end of exercices
material.
14. If OMU does not start to the correct package start the minidebugger with “m”
during the restart phase and patch the SOMAFI.
•.
•.
•.
!TIP. In practice it is currently possible to copy the SW to mcBSC WDU so that
USB memory is attached directly to the USB port in OMU’s BJCA-A unit.
Once OMU is started into minidebugger OMU sees the USB port as U0.
This is not recommended since it required that BCN cover is opened while BCN
is powered up. Also USB interface will be removed from BJCA-A’s later on.
For internal use
Unique document identifier (ID) / Version number / Life cycle status
45
© Nokia Siemens Networks 2012
Dept. / Author / Date
mcBSC creation
For internal use
Unique document identifier (ID) / Version number / Life cycle status
46
© Nokia Siemens Networks 2012
Dept. / Author / Date
mcBSC creation.
•
•
Please refere to the Creating and Managing mcBSC Hardware document.
In following steps mcKOFF is being created by following IP plan
McBSC KOFF10.255.164.0/24
VLAN name VLAN nbr
BITS in MASK MASK
GATEWAY 1
GATEWAY 2
GW2 switch
GATEWAY 3
GW3 switch
BROADCAST
Koff O&M
3910
29255.255.255.248 10.9.192.232
10.9.192.233
10.9.192.234
techsup1
10.9.192.235
techsup2
10.9.192.239
BTS vlan
3900
28255.255.255.248 10.255.164.176
10.255.164.177
10.255.164.178
techsup1
10.255.164.179
techsup2
10.255.164.191
sigtran-1
3932
28255.255.255.240 10.255.164.160
10.255.164.161
10.255.164.162
techsup1
10.255.164.163
techsup2
10.255.164.175
sigrtan-2
3933
28255.255.255.240 10.255.164.144
10.255.164.145
10.255.164.146
techsup1
10.255.164.147
techsup2
10.255.164.159
Synch
3934
29255.255.255.248 10.255.164.192
10.255.164.193
10.255.164.194
techsup1
10.255.164.195
techsup2
10.255.164.199
etpsig-e
3943
28255.255.255.240 10.255.164.128
10.255.164.129
10.255.164.130
techsup1
10.255.164.131
techsup2
10.255.164.143
omu- trxsig
3944
28255.255.255.240 10.255.164.112
10.255.164.113
10.255.164.114
techsup1
10.255.164.115
techsup2
10.255.164.127
aoip
3946
28255.255.255.240 10.255.164.96
10.255.164.97
10.255.164.98
techsup1
10.255.164.99
techsup2
10.255.164.111
ater
3947
28255.255.255.240 10.255.164.80
10.255.164.81
10.255.164.82
techsup1
10.255.164.83
techsup2
10.255.164.95
pabis
3948
28255.255.255.240 10.255.164.64
10.255.165.65
10.255.164.66
techsup1
10.255.164.67
techsup2
10.255.164.79
gb
3949
26255.255.255.192 10.255.164.0
10.255.164.1
10.255.164.2
techsup1
10.255.164.3
techsup2
10.255.164.63
For internal use
Unique document identifier (ID) / Version number / Life cycle status
47
NETWORK
© Nokia Siemens Networks 2012
Dept. / Author / Date
mcBSC creation.
HW creation
1. Load VIMLA and configure OMU IP for better connection.
ZLP:1,VIM;
Z1CT:1;
ZQRA:OMU::EL0:;
ZQRA:OMU::EL1:;
ZQRA:OMU::VLAN3910,3910,EL1,,::;
ZQRN:OMU::VLAN3910,:"10.9.192.236",29,;
ZQKM:OMU::"10.9.192.236":"10.9.192.233":;
ZIAA:PROFILE::::FTP=W:;“
ZQNM:0:NAME=mcKOFF,LOC=BSCTECHSUPTRE;
Now IP connection is possible if site equipment, main switch & extension switch configuration is on order
2. Change the topology.
ZW6G:SAT1:;
For internal use
Unique document identifier (ID) / Version number / Life cycle status
48
© Nokia Siemens Networks 2012
Dept. / Author / Date
mcBSC creation.
HW creation
3. Create rack BCN’s and BJA-A cards
ZWTJ:GCBV,1A,;
ZWTC:BCNC,1A001-0,,:;
ZWTC:BCNC,1A002-0,,:;
Box 1
ZWTU:MCBC,0:1A1-0;
ZWTP:MCBC,0:BCN_A,0,1,1;
ZWTU:MCMU,0:1A001-0:MB=4,UTY=MCBC,UIN=0:;
ZWTP:MCMU,0:BJC_A,0,1,1;
ZWTU:BCXU,0:1A001-0:MB=49,UTY=MCBC,UIN=0:;
ZWTP:BCXU,0:BJC_A,0,1,2;
ZWTU:BCXU,1:1A001-0:MB=4A,UTY=MCBC,UIN=0:;
ZWTP:BCXU,1:BJC_A,0,1,3;
ZWTU:OMU:1A001-0:MB=0,UTY=MCBC,UIN=0:;
ZWTP:OMU:BJC_A,0,1,8;
For internal use
Unique document identifier (ID) / Version number / Life cycle status
49
© Nokia Siemens Networks 2012
Dept. / Author / Date
Box 2
ZWTU:MCBC,1:1A2-0;
ZWTP:MCBC,1:BCN_A,0,1,1;
ZWTU:MCMU,1:1A002-0:MB=5,UTY=MCBC,UIN=1:;
ZWTP:MCMU,1:BJC_A,0,1,1;
ZWTU:BCXU,2:1A002-0:MB=4B,UTY=MCBC,UIN=1:;
ZWTP:BCXU,2:BJC_A,0,1,2;
ZWTU:BCXU,3:1A002-0:MB=4C,UTY=MCBC,UIN=1:;
ZWTP:BCXU,3:BJC_A,0,1,3;
mcBSC creation.
HW creation
4. Create and Configure EMB, PEM, FAN, WDU, & PTUM for both modules
ZWTU:EMB,0;
ZWTU:EMB,1;
ZWTU:PEM,0:1A1-0:UTY=MCBC,UIN=0;
ZWTP:PEM,0:BPSU_A,0,1,1;
ZWTU:PEM,1:1A1-0:UTY=MCBC,UIN=0;
ZWTP:PEM,1:BPSU_A,0,1,2;
ZWTU:PEM,2:1A2-0:UTY=MCBC,UIN=1;
ZWTP:PEM,2:BPSU_A,0,1,1;
ZWTU:PEM,3:1A2-0:UTY=MCBC,UIN=1;
ZWTP:PEM,3:BPSU_A,0,1,2;
ZWTU:FAN,0:1A1-0:UTY=MCBC,UIN=0;
ZWTP:FAN,0:BFAN_A,0,1,1;
ZWTU:FAN,1:1A1-0:UTY=MCBC,UIN=0;
ZWTP:FAN,1:BFAN_A,0,1,2;
ZWTU:FAN,2:1A1-0:UTY=MCBC,UIN=0;
ZWTP:FAN,2:BFAN_A,0,1,3;
ZWTU:FAN,3:1A2-0:UTY=MCBC,UIN=1;
ZWTP:FAN,3:BFAN_A,0,1,1;
ZWTU:FAN,4:1A2-0:UTY=MCBC,UIN=1;
ZWTP:FAN,4:BFAN_A,0,1,2;
ZWTU:FAN,5:1A2-0:UTY=MCBC,UIN=1;
ZWTP:FAN,5:BFAN_A,0,1,3;
For internal use
Unique document identifier (ID) / Version number / Life cycle status
50
© Nokia Siemens Networks 2012
Dept. / Author / Date
ZWTU:WDU,0:1A001-0:MAS=OMU:;
ZWTP:WDU,0:HDSAM_A,0,1,1;
ZWTU:WDU,1:1A002-0:MAS=OMU:;
ZWTP:WDU,1:HDSAM_A,0,1,1;
! Create PTUM only if equipped.
ZWTU:PTUM,0:1A001-0:UTY=MCBC,UIN=0:;
ZWTP:PTUM,0:BSAC_A,0,1,2;
ZWTU:PTUM,1:1A002-0:UTY=MCBC,UIN=1:;
ZWTP:PTUM,1:BSAC_A,0,1,2;
mcBSC creation.
HW creation
5. Restart the system at this point
ZUSS:SYM;
6. After OMU is restarted activate the modules.
Box1
ZUSC:MCBC,0:SE;
ZUSC:MCBC,0:TE;
ZUSC:MCBC,0:WO;
Follow from service terminal that MCMU0, BCXU0 & BCXU 1 are restarting properly.
Box2
ZUSC:MCBC,1:SE;
ZUSC:MCBC,1:TE;
ZUSC:MCBC,1:WO;
Follow from service terminal that MCMU1, BCXU2 & BCXU 3 are restarting properly.
For internal use
Unique document identifier (ID) / Version number / Life cycle status
51
© Nokia Siemens Networks 2012
Dept. / Author / Date
mcBSC creation.
HW creation
7. Create BOC-A units in both modules
Box 1
ZWTU:PCUM,0:1A001-0:UTY=MCBC,UIN=0:;
ZWTP:PCUM,0:BOC_A,0,1,4;
ZWTU:PCUM,1:1A001-0:UTY=MCBC,UIN=0:;
ZWTP:PCUM,1:BOC_A,0,1,5;
ZWTU:ETME,0:1A001-0:UTY=MCBC,UIN=0:;
ZWTP:ETME,0:BOC_A,0,1,6;
ZWTU:ETMA,0:1A001-0:UTY=MCBC,UIN=0:;
ZWTP:ETMA,0:BOC_A,0,1,7;
Box 2
ZWTU:PCUM,2:1A002-0:UTY=MCBC,UIN=1:;
ZWTP:PCUM,2:BOC_A,0,1,4;
ZWTU:PCUM,3:1A002-0:UTY=MCBC,UIN=1:;
ZWTP:PCUM,3:BOC_A,0,1,5;
ZWTU:PCUM,4:1A002-0:UTY=MCBC,UIN=1:;
ZWTP:PCUM,4:BOC_A,0,1,6;
ZWTU:ETME,1:1A002-0:UTY=MCBC,UIN=1:;
ZWTP:ETME,1:BOC_A,0,1,7;
ZWTU:ETMA,1:1A002-0:UTY=MCBC,UIN=1:;
ZWTP:ETMA,1:BOC_A,0,1,8;
For internal use
Unique document identifier (ID) / Version number / Life cycle status
52
© Nokia Siemens Networks 2012
Dept. / Author / Date
mcBSC creation.
VLAN800
8. Configure management VLAN800 & LDI
•
VLAN 800 is used for internal management purposes inside of Multicontroller platform e.g.
DHCP for LMP and PTUM, IPMI and SNMP
VLAN800
ZQRA:OMU::VLAN800,800,EL0,,::;
ZQRA:MCMU,0::EL0:;
ZQRA:MCMU,0::EL1:;
ZQRA:MCMU,1::EL0:;
ZQRA:MCMU,1::EL1:;
ZQRA:MCMU,0::VLAN800,800,EL0,,::;
ZQRA:MCMU,1::VLAN800,800,EL0,,::;
ZQRN:MCMU::VLAN800:"10.10.10.2",24,L,I,;
LDI
ZWYB:800:CNW,800,LDI:;
ZWYC:800:MCBC,0:MCMU,0,VLAN800:;
ZWYC:800:MCBC,1:MCMU,0,VLAN800:;
ZW6E:MCBC,0:A:;
ZW6E:MCBC,1:A:;
ZW6E:MCBC,100:A:;
//Ei tarvita ??
ZW6E:MCBC,101:A:;
//Ei tarvita ??
ZUSC:CNW,800:SE;
ZUSC:CNW,800:TE;
ZUSC:CNW,800:WO;
ZQRN:MCMU,0::EL0,:"10.200.200.2",24,L,I:;
ZQRN:MCMU,0::EL1,:"10.200.201.2",24,L,i:;
For internal use
Unique document identifier (ID) / Version number / Life cycle status
53
© Nokia Siemens Networks 2012
Dept. / Author / Date
mcBSC creation.
Unit interfaces
9. Create IP interfaces for the units
ZQRA:PCUM,0::IFETH0;
ZQRA:PCUM,0::IFETH1;
ZQRA:PCUM,1::IFETH0;
ZQRA:PCUM,1::IFETH1;
ZQRA:PCUM,2::IFETH0;
ZQRA:PCUM,2::IFETH1;
ZQRA:PCUM,3::IFETH0;
ZQRA:PCUM,3::IFETH1;
ZQRA:PCUM,4::IFETH0;
ZQRA:PCUM,4::IFETH1;
ZQRA:ETME,0::IFETH0;
ZQRA:ETME,0::IFETH1;
ZQRA:ETME,1::IFETH0;
ZQRA:ETME,1::IFETH1;
ZQRA:ETMA,0::IFETH0;
ZQRA:ETMA,0::IFETH1;
ZQRA:ETMA,1::IFETH0;
ZQRA:ETMA,1::IFETH1;
ZQRA:BCXU,0::EL0;
ZQRA:BCXU,0::EL1;
ZQRA:BCXU,1::EL0;
ZQRA:BCXU,1::EL1;
ZQRA:BCXU,2::EL0;
ZQRA:BCXU,2::EL1;
ZQRA:BCXU,3::EL0;
ZQRA:BCXU,3::EL1;
For internal use
Unique document identifier (ID) / Version number / Life cycle status
54
© Nokia Siemens Networks 2012
Dept. / Author / Date
mcBSC creation.
VLAN20
10. Create VLAN20
•
Signalling VLAN 20 is used for management and control traffic (ETPSIG and PCUSIG),
DHCP and software downloading purposes for BOC-A cards as ETMA, ETME and PCUM.
ZQRA:MCMU,0::VLAN20,20,EL0,:::;
ZQRA:MCMU,1::VLAN20,20,EL0,:::;
ZQRN:MCMU,0::VLAN20,:"10.0.1.3",25,L,IM;
ZQRA:BCXU,0::VLAN20,20,EL0,,::;
ZQRA:BCXU,1::VLAN20,20,EL0,,::;
ZQRA:BCXU,2::VLAN20,20,EL0,,::;
ZQRA:BCXU,3::VLAN20,20,EL0,,::;
ZQRN:BCXU,0::VLAN20:"10.0.1.10",25,L,IMC;
ZQRN:BCXU,1::VLAN20:"10.0.1.11",25,L,IMC;
ZQRN:PCUM,0::IFETH0:"10.0.1.20",25,P,DIM:;
ZQRN:PCUM,1::IFETH0:"10.0.1.21",25,P,DIM:;
ZQRN:PCUM,2::IFETH0:"10.0.1.22",25,P,DIM:;
ZQRN:PCUM,3::IFETH0:"10.0.1.23",25,P,DIM:;
ZQRN:PCUM,4::IFETH0:"10.0.1.24",25,P,DIM:;
ZQRN:ETMA,0::IFETH0:"10.0.1.30",25,P,DIM:;
ZQRN:ETMA,1::IFETH0:"10.0.1.31",25,P,DIM:;
ZQRN:ETME,0::IFETH0:"10.0.1.33",25,P,DIM:;
ZQRN:ETME,1::IFETH0:"10.0.1.34",25,P,DIM:;
ZQRN:ETMA,0::IFETH0:"10.0.1.40",25,P,CI:;
ZQRN:ETMA,1::IFETH0:"10.0.1.41",25,P,CI:;
ZQRN:ETME,0::IFETH0:"10.0.1.43",25,L,CI:;
!IP address only for working MCMU / BCXU’s
For internal use
Unique document identifier (ID) / Version number / Life cycle status
55
© Nokia Siemens Networks 2012
Dept. / Author / Date
mcBSC creation.
VLAN23
11. Create VLAN23
•
EEP VLAN 23 is used for transporting CS traffic between ETMA and ETME cards.
ZQRA:ETME,0::VLAN23,23,IFETH0,::UP:;
ZQRA:ETME,1::VLAN23,23,IFETH0,::UP:;
ZQRN:ETME,0::VLAN23:"10.0.3.1",25,L,I:;
ZQRP:ETME,0::VLAN23:"10.0.3.1":TAG,"EEP":;
ZQRA:ETMA,0::VLAN23,23,IFETH0,::UP:;
ZQRA:ETMA,1::VLAN23,23,IFETH0,::UP:;
ZQRN:ETMA,0::VLAN23:"10.0.3.10",25,P,I:;
ZQRP:ETMA,0::VLAN23:"10.0.3.10":TAG,"EEP":;
ZQRN:ETMA,1::VLAN23:"10.0.3.11",25,P,I:;
ZQRP:ETMA,1::VLAN23:"10.0.3.11":TAG,"EEP":;
•
! Once you start to create BTS’s remember to create route from ETMA to BTS via ETME EEP
For internal use
Unique document identifier (ID) / Version number / Life cycle status
56
© Nokia Siemens Networks 2012
Dept. / Author / Date
mcBSC creation.
VLAN24
12. Create VLAN24
•
PEP VLAN 24 is used for transport PS traffic between PCUM and ETME cards.
ZQRA:ETME,0::VLAN24,24,IFETH0,::UP:;
ZQRA:ETME,1::VLAN24,24,IFETH0,::UP:;
ZQRN:ETME,0::VLAN24:"10.0.3.129",25,L,I:;
ZQRP:ETME,0::VLAN24:"10.0.3.129":TAG,"PEP":;
ZQRA:PCUM,0::VLAN24,24,IFETH0,::UP:;
ZQRA:PCUM,1::VLAN24,24,IFETH0,::UP:;
ZQRA:PCUM,2::VLAN24,24,IFETH0,::UP:;
ZQRA:PCUM,3::VLAN24,24,IFETH0,::UP:;
ZQRA:PCUM,4::VLAN24,24,IFETH0,::UP:;
ZQRN:PCUM,0::VLAN24:"10.0.3.140",25,L,I:;
ZQRN:PCUM,1::VLAN24:"10.0.3.141",25,L,I:;
ZQRP:PCUM,0::VLAN24:"10.0.3.140":TAG,"PEP":;
ZQRP:PCUM,1::VLAN24:"10.0.3.141":TAG,"PEP":;
For internal use
Unique document identifier (ID) / Version number / Life cycle status
57
© Nokia Siemens Networks 2012
Dept. / Author / Date
mcBSC creation.
VLAN32
13. Create VLAN32
•
Sigtran-1 VLAN 32 is used for transport SCTP based traffic and used by different
applications: A-Sigtran, BBI and Lb.
ZQRA:MCMU,0::VLAN3932,3932,EL1,::UP:;
ZQRA:MCMU,1::VLAN3932,3932,EL1,::UP:;
ZQRA:BCXU,0::VLAN3932,3932,EL1,::UP:;
ZQRA:BCXU,1::VLAN3932,3932,EL1,::UP:;
ZQRA:BCXU,2::VLAN3932,3932,EL1,::UP:;
ZQRA:BCXU,3::VLAN3932,3932,EL1,::UP:;
ZQRN:MCMU,0::VLAN3932,:"10.255.164.164",28,L,::;
ZQRN:BCXU,0::VLAN3932,:"10.255.164.165",28,L,::;
ZQRN:BCXU,1::VLAN3932,:"10.255.164.166",28,L,::;
ZQKM:MCMU,0::"10.255.164.164":"10.255.164.161":LOG:;
ZQKM:BCXU,0::"10.255.164.165":"10.255.164.161":LOG:;
ZQKM:BCXU,1::"10.255.164.166":"10.255.164.161":LOG:;
For internal use
Unique document identifier (ID) / Version number / Life cycle status
58
© Nokia Siemens Networks 2012
Dept. / Author / Date
mcBSC creation.
VLAN44 & VLAN45
14. Create VLAN44 & VLAN45
•
OMUSIG VLAN 44 and TRXSIG 45 are used for IP connectivity between BCXU and BTS
using Packet Abis over Ethernet.
ZQRA:BCXU,0::VLAN3944,3944,EL1,,::UP:;
ZQRA:BCXU,1::VLAN3944,3944,EL1,,::UP:;
ZQRA:BCXU,2::VLAN3944,3944,EL1,,::UP:;
ZQRA:BCXU,3::VLAN3944,3944,EL1,,::UP:;
ZQRN:BCXU,0::VLAN3944:"10.255.164.116",28,L,::;
ZQRN:BCXU,1::VLAN3944:"10.255.164.117",28,L,::;
ZQKM:BCXU,0::"10.255.164.116":"10.255.164.113":LOG:;
ZQKM:BCXU,1::"10.255.164.117":"10.255.164.113":LOG:;
For internal use
Unique document identifier (ID) / Version number / Life cycle status
59
© Nokia Siemens Networks 2012
Dept. / Author / Date
mcBSC creation.
VLAN46
15. Create VLAN46
•
AoIP VLAN 46 is used for transport CS user plane traffic between ETMA and MGW in a case
of transcoding in MGW.
ZQRA:ETMA,0::VLAN3946,3946,IFETH1,,::UP:;
ZQRA:ETMA,1::VLAN3946,3946,IFETH1,,::UP:;
ZQRN:ETMA,0::VLAN3946:"10.255.164.100",28,P,::;
ZQRN:ETMA,1::VLAN3946:"10.255.164.101",28,P,::;
ZQKC:ETMA,0:::"10.255.164.97":PHY:;
ZQKC:ETMA,1:::"10.255.164.97":PHY:;
For internal use
Unique document identifier (ID) / Version number / Life cycle status
60
© Nokia Siemens Networks 2012
Dept. / Author / Date
mcBSC creation.
VLAN48
16. Create VLAN48
•
PAbis VLAN 48 is used for transport Packet Abis traffic between ETME and IP BTS using
Packet Abis over Ethernet.
ZQRA:ETME,0::VLAN3948,3948,IFETH1,,::UP:;
ZQRA:ETME,1::VLAN3948,3948,IFETH1,,::UP:;
ZQRN:ETME,0::VLAN3948:"10.255.164.68",28,L,::;
ZQKC:ETME,0:::"10.255.164.65":LOG:;
For internal use
Unique document identifier (ID) / Version number / Life cycle status
61
© Nokia Siemens Networks 2012
Dept. / Author / Date
mcBSC creation.
VLAN49
17. Create VLAN49
•
Gb VLAN 49 is used for interconnection for PCUMs in a case of PCU Pooling (PCP) feature
and Gb interface between SGSN and PCUMs.
ZQRA:PCUM,0::VLAN3949,3949,IFETH1,,::UP:;
ZQRA:PCUM,1::VLAN3949,3949,IFETH1,,::UP:;
ZQRA:PCUM,2::VLAN3949,3949,IFETH1,,::UP:;
ZQRA:PCUM,3::VLAN3949,3949,IFETH1,,::UP:;
ZQRA:PCUM,4::VLAN3949,3949,IFETH1,,::UP:;
ZQRN:PCUM,0::VLAN3949:"10.255.164.4",26,L,::;
ZQRN:PCUM,1::VLAN3949:"10.255.164.5",26,L,::;
ZQKC:PCUM,0:::"10.255.164.1":LOG:;
ZQKC:PCUM,1:::"10.255.164.1":LOG:;
ZQRP:PCUM,0::VLAN3949:"10.255.164.4":TAG,"GB":;
ZQRP:PCUM,0::VLAN3949:"10.255.164.4":TAG,"IPL":;
ZQRP:PCUM,1::VLAN3949:"10.255.164.5":TAG,"GB":;
ZQRP:PCUM,1::VLAN3949:"10.255.164.5":TAG,"IPL":;
For internal use
Unique document identifier (ID) / Version number / Life cycle status
62
© Nokia Siemens Networks 2012
Dept. / Author / Date
mcBSC creation.
IUA
18. Create IUA messaging configuration
PCUSIG
ZD2C:P:BCXU,0::PCUM,0;
ZD2C:P:BCXU,1::PCUM,1;
ZD2C:P:BCXU,0::PCUM,2;
ZD2C:P:BCXU,1::PCUM,3;
ZD2C:P:BCXU,0::PCUM,4;
ETPSIG-M
ZD2C:M:BCXU,0::ETME,0;
ZD2C:M:BCXU,1::ETME,1;
ZD2C:M:BCXU,1::ETMA,0;
ZD2C:M:BCXU,0::ETMA,1;
ETPSIG-C for ETME
ZD2C:C,NOR:BCXU,0::ETME,0;
ZD2C:C,NOR:BCXU,1::ETME,0;
ETPSIG-C for ETMA
ZD2C:C,NOR:BCXU,0::ETMA,0;
ZD2C:C,NOR:BCXU,0::ETMA,1;
ZD2C:C,NOR:BCXU,1::ETMA,0;
ZD2C:C,NOR:BCXU,1::ETMA,1;
For internal use
Unique document identifier (ID) / Version number / Life cycle status
63
© Nokia Siemens Networks 2012
Dept. / Author / Date
mcBSC creation.
Host BCXU
19. Create host BCXU
ZD3C:PCUM,0:BCXU,0:;
ZD3C:PCUM,1:BCXU,1:;
!IF PCUM is in SP state platform will raise the PCU to WO state once host is created.
For internal use
Unique document identifier (ID) / Version number / Life cycle status
64
© Nokia Siemens Networks 2012
Dept. / Author / Date
mcBSC creation.
Start up the BOC-A units
20. Start up the BOC-A units
ZUSC:PCUM,0:SE;
ZUSC:PCUM,1:SE;
ZUSC:PCUM,2:SE;
ZUSC:PCUM,3:SE;
ZUSC:PCUM,4:SE;
ZUSC:PCUM,0:TE;
ZUSC:PCUM,1:TE;
ZUSC:PCUM,2:TE;
ZUSC:PCUM,3:TE;
ZUSC:PCUM,4:TE;
Follow that PCUM's are raising up to TE
ZUSC:PCUM,0:SP;
ZUSC:PCUM,1:SP;
ZUSC:PCUM,2:SP;
ZUSC:PCUM,3:SP;
ZUSC:PCUM,4:SP;
Follow that PCUM's are raising up to SP & WO
For internal use
Unique document identifier (ID) / Version number / Life cycle status
65
© Nokia Siemens Networks 2012
Dept. / Author / Date
ZUSC:ETME,0:SE;
ZUSC:ETME,1:SE;
ZUSC:ETMA,0:SE;
ZUSC:ETMA,1:SE;
ZUSC:ETME,0:TE;
ZUSC:ETME,1:TE;
ZUSC:ETMA,0:TE;
ZUSC:ETMA,1:TE;
Follow that ETME & ETMA's are raising up to TE
ZUSC:ETME,0:SP;
ZUSC:ETME,1:SP;
ZUSC:ETMA,0:WO;
ZUSC:ETMA,1:WO;
Follow that ETME & ETMA's are raising up to SP & WO
mcBSC creation.
Lincence & Features
21. Install and activate the licence and features
For internal use
Unique document identifier (ID) / Version number / Life cycle status
66
© Nokia Siemens Networks 2012
Dept. / Author / Date
mcBSC creation.
Sigtran
22. Create Sigtran interface
ZOYC:LIISA:C:M3UA:;
ZOYA:LIISA:BCXU,0:IETF:;
ZOYM:LIISA:NETWORK=8:;
ZOYP:M3UA:LIISA,0:"10.255.164.165",,:"10.8.192.5",24,,,:;
ZNRP:NA0,116,KOFFI,STP:::;
ZNSP:NA0,391,LIISA:0:LIISA:;
ZNRC:NA0,391,LIISA,6,A,:,,,7:;
ZNFD:NA0,116,0:;
ZNFB:NA0,116:FE,BSSAP,0,;
ZNPC:NA0,03,SCCP:Y:Y,208,10F:;
ZNFD:NA0,391,0:FE,BSSAP,0,;
ZNHC:NA0,116:FE:ACT;
ZNVA:NA0,391::;
ZNVC:NA0,391::ACT:;
ZNGC:NA0,391:ACT:;
ZNLA:0:;
ZNLC:0,ACT:;
ZNHC:NA0,391:FE:ACT:;
ZOYS:M3UA:LIISA,0:ACT:;
For internal use
Unique document identifier (ID) / Version number / Life cycle status
67
© Nokia Siemens Networks 2012
Dept. / Author / Date
mcBSC creation.
BTS
23. Create BTS
ZOYX:BTS1SCTPOM1:IUA:S:BCXU,0:AFAST:2:;
ZOYP:IUA:BTS1SCTPOM1:"10.255.164.116",,49152:"10.255.164.180",29,,,49152:;
ZOYX:BTS1SCTPT01:IUA:S:BCXU,0:AFAST:4:;
ZOYP:IUA:BTS1SCTPT01:"10.255.164.116",,49153:"10.255.164.180",29,,,49153:;
ZDWP:OM001:BCXU,0:62,1:BTS1SCTPOM1,0:;
ZDWP:T0001:BCXU,0:0,1:BTS1SCTPT01,0:;
ZOYV:IUA::A;
ZDWQ;
ZEWC:EX4IR2BL110:MF=BTSE4003,EXT=A0X,SDIR=PACK_1,;
ZEWS:E:EX4IR2BL110:;
ZEFC:4,E,:DNAME=OM001,:::::BCUIP=10.255.164.180,SMCUP=29,BMIP=10.255.164.180,SMMP=29,ETMEID=0,VLANID=3948,;
ZOYS:IUA:BTS1SCTPOM1:ACT:;
ZOYS:IUA:BTS1SCTPT01:ACT:;
ZEQC:BCF=4,BTS=1,:CI=1401,BAND=1800:NCC=0,BCC=0:MCC=520,MNC=18,LAC=116::;
ZEUC:BTS=1,;
ZEUG:BTS=1:PMAX2=20;
ZEHC:BTS=1,;
ZERC:BTS=1,TRX=1::FREQ=665,TSC=0,:DNAME=T0001:CH0=MBCCHC,;
•
Route from ETMA to BTS via ETME EEP
ZQKC:ETMA,0::"10.255.164.180",32:"10.0.3.1":PHY:;
ZQKC:ETMA,1::"10.255.164.180",32:"10.0.3.1":PHY:;
For internal use
Unique document identifier (ID) / Version number / Life cycle status
68
© Nokia Siemens Networks 2012
Dept. / Author / Date
mcBSC creation.
NSEI
24. Create PEP links for active PCUM units
ZESK:ETME,0::PCU,0:;
ZESK:ETME,0::PCU,1:;
25. Create NSEI
ZFXA:PSEI=0,PCU=0;
ZFXK:NSEI=401,NSVLI=401,NAME=NETTA1,PSEI=0:LPNBR=50303,NRID=67,PRE=Y:RIP="10.8.37.37",RPNBR=49999,;
ZEBF:MCC=520,MNC=18,LAC=116,RAC=1:NSEI=401:;
For internal use
Unique document identifier (ID) / Version number / Life cycle status
69
© Nokia Siemens Networks 2012
Dept. / Author / Date
mcBSC creation.
Synchronisation
26. Synchronisation
Create sync cables between boxes(2 boxes):
ZWTA:MCBC,0:BCN_A,0:SYNC,1:MCBC,1:BCN_A,0:SYNC,0:;
ZWTA:MCBC,1:BCN_A,0:SYNC,1:MCBC,0:BCN_A,0:SYNC,0:;
Create PTUM/BSAC card (if not created already in step 4) :
PTUM-0, 1st box’s AMC2:
ZWTU:PTUM,0:1A001-0:UTY=MCBC,UIN=0:;
ZWTP:PTUM,0:BSAC_A,0,1,2;
PTUM-1, last box’s AMC2:
ZWTU:PTUM,1:1A003-0:UTY=MCBC,UIN=2:;
ZWTP:PTUM,1:BSAC_A,0,1,2;
ZUSC:PTUM,0:SE;
ZUSC:PTUM,0:TE;
ZUSC:PTUM,0:WO;
ZUSC:PTUM,1:SE;
ZUSC:PTUM,1:TE;
ZUSC:PTUM,1:WO;
For internal use
Unique document identifier (ID) / Version number / Life cycle status
70
© Nokia Siemens Networks 2012
Dept. / Author / Date
mcBSC creation.
Synchronisation
PCM synchronization:
Connect PCM to first box Sync1.
Set sync priority: ZDYM:MCBC,0:EXT,1:PRI=2,;
Check sync status: ZDYI;
- It is possible to use PTUM’s(BSAC card) PCM interface
ToP synchronization with PTUM:
Needs BSAC card
1. Create synchronization role: ZDYA:PTUM,0:I,C:LP=“<LOCAL IP>",RP=“<REMOTE IP>",MASK=<MASK>,GW=“<GATEWAY>":;
2. Set sync priority: ZDYM:PTUM,0:SFP,1:PRI=1,;
3. Check role: ZDYB;
4. Check sync status: ZDYI;
Tips:
If ZDYI fails
* PTUM-0 has always IP 10.10.10.50 and PTUM-1 10.10.10.51.
Try ping from LMP to BSAC card. If fails deactivate/activate amc2:
mch_cli Deactivate AMC2
mch_cli Aactivate AMC2
Try ping again.
- MML state change
- It doesn’t cause resets for BSAC card. Program block includes BSAC card to ZDYI if state is WO-EX.
•.
Complete. Now there should working environment.
For internal use
Unique document identifier (ID) / Version number / Life cycle status
71
© Nokia Siemens Networks 2012
Dept. / Author / Date