INSTRUCTION 1 (7)

Prepared (Subject resp) No.

Rajesh Singh (errhssh)

Approved (Document resp) Checked Date Rev Reference

2013-12-19 A 1/109 22-CXC 132 9107

Uen Rev V

BSC NWI-E UPGRADE

Abstract
This document describes how an upgrade GSM BSC IP network interface NWI-E is performed, and what to do before
and after the procedure.

Application
BSC NWI-E 450A, a GEM/eGEM-board based on a redesigned Summit X450a from Extreme Networks with
ExtremeXOS SW. The BSC NWI-E 450A is hereafter referred to as NWI-E. The NWI-E SW is called XOS.

Concepts
Current Image: This is where the ExtremeWare/XOS version is loaded on the Switch. It is part of the non-persistent
memory. In the printout from ‘show switch’ the ‘Booted Image’ resides in the Current Image space.

Primary image: Part of the persistent memory that contains one ExtremeWare or XOS version on the Switch. If the
‘Use image’ tag points to this area, then the Switch will set this ExtremeWare/XOS version as the current image after
a reboot. Is seen in the ‘show switch’ printout in ‘Image Selected’ and ‘Image Booted’.

Secondary image: Part of the persistent memory that contains one ExtremeWare or XOS version on the Switch. If the
‘Use image’ tag points to this area, then the Switch will set this version as the current image after a reboot. Is seen in
the ‘show switch’ printout in ‘Image Selected’ and ‘Image Booted’.

Current Configuration: Contains the non-persistent configuration of the Switch, such as VLAN set-up, security ACL’s
etc. In the printout from ‘show switch’ the Booted Configuration resides in the Current Configuration space.

Primary Configuration: The current configuration can be backed up into this area of the Switch persistent memory. If
the ‘Use configuration’ tag points to this area, then the Switch uses this configuration as the current configuration
after a reboot. Is seen in the ‘show switch’ printout in ‘Config Selected’ and ‘Config Booted’.

Secondary Configuration: The current configuration can be backed up into this area of the Switch persistent
memory. If the ‘Use configuration’ tag points to this area, then the Switch uses this configuration as the current
configuration after a reboot. Is seen in the ‘show switch’ printout in ‘Config Selected’ and ‘Config Booted’.

Note. For the NWI-E, the name for the configuration file can be chosen by the operator. Generally the configuration
name is either primary or secondary.

Minimum Supported XOS Firmware Versions

The minimum supported version to upgrade to 15.1.3.4 patch1-2 from for NWI-E is XOS 12.3.1.2 and BootROM
1.0.5.6.
 INSTRUCTION 2 (7)
Prepared (Subject resp) No.

Rajesh Singh (errhssh)

Approved (Document resp) Checked Date Rev Reference

2013-12-19 A 1/109 22-CXC 132 9107

Uen Rev V

Pre-Requisite and Requirements

1. Network and OSS set-up (in OSS)
To be able to upgrade the Switch it must be defined as a node (NE) in OSS Network Explorer with Type as
‘LANSwitch’ and Platform as ‘EXTREME’ and connected to the appropriate BSC. There should be a node defined for
each Switch and both nodes should be upgraded separately.
Note. The Node Version for the NWI-E it is ‘BSC_NWI-E_450A’.

2. Communication set-up
• ensure that SSH2 Secure has to be enabled for both NWI-Es (in NWI-E)

That can be done by command "enable ssh2"

• Security State has to be ON for both the NWI-Es (in OSS)

From OSS Network Explorer it can be set to ON but for that it will ask for password and login password details
would be needed for same.

3. Heart beat alarm (in OSS)

During Switch upgrade a Heart Beat alarm can be raised by OSS. The alarm is raised when the switch reboots, as the
reboot time for the NWI-E is longer than the Heart Beat timeout value in application IMIM, default set to 120
seconds. Extend the timeout in IMIM to avoid the alarm, for example to 180 seconds.

4. APG-Switch connections (in OSS)

It is recommended to start the upgrade with the Switch that connects to the passive side of APG4x to avoid
unnecessary failovers.
If “Reliable Ethernet” is used, the APG will not failover as traffic is then directed to the other Switch through the
interconnection between the Switches.

5. Upgrade package should be available on SMO (in OSS)

This Upgrade package consists of one gzipped tar-file:
10_CXC1329107_<RevisionNumber>.tar.gz – package to upgrade the Switch.
For import to SMO File store, un-gzip the Upgrade package file to get the tar file which shall be imported into SMO.
As SMO is used for the upgrade, the Upgrade products are packaged according to SMO specifications.

6. Check UNIX FTP user is active in OSS (default password is oss123)

OSS/SMO administrator or equivalent user is required for below action.

pwAdmin -get UNIX FTP ossftp

oss123

Login to OSS with user ossftp and password. Verify if login is successful.
If password is expired change it immediately.
 INSTRUCTION 3 (7)
Prepared (Subject resp) No.

Rajesh Singh (errhssh)

Approved (Document resp) Checked Date Rev Reference

2013-12-19 A 1/109 22-CXC 132 9107

Uen Rev V

Ex:
pwAdmin -changePw UNIX FTP ossftp -pw ADmin@12#

pwAdmin -get UNIX FTP ossftp

ADmin@12#

7. Other requirements
a. A local engineer on site is required for worst case local support.
b. If APG connectivity is through NWIE boards, the failover for the APG should be tested before the activity.
c. If GB traffic is running on the NWI-Es, a Drive tester is required, who can test the GPRS calls before and
after the software upgrade activity.

Upgrade Activity
1. Before starting take the health Complete Health Check and Backup of BSC and NWI-E Switches. NWI-E A & B
Switches are upgraded Separately.
2. Make APG Node-A Passive.
Note- It is recommended to start the upgrade with the Switch that connects to the passive side of APG4x to
avoid unnecessary failovers.
If “Reliable Ethernet” is used, the APG will not failover as traffic is then directed to the other Switch through
the interconnection between the Switches.
Here I have assumed Node A is passive.
3. Block GPRS serving RP group by “BLRCI:GROUP=GBIP,NET=A;”
Not applicable for SATRC NWI-E NE.
4. Login to NWI-E A and Check XOS images and configuration type in NWI-E A proper.
Ex:
Recovery Mode: All
System Watchdog: Enabled

Current Time: Thu Dec 19 07:31:53 2013

Timezone: [Auto DST Disabled] GMT Offset: 0 minutes, name is UTC.
Boot Time: Sat Nov 26 17:16:35 2011
Boot Count: 6
Next Reboot: None scheduled
System UpTime: 753 days 14 hours 15 minutes 18 seconds

Current State: OPERATIONAL

Image Selected: primary
Image Booted: primary
Primary ver: 12.3.1.2
Secondary ver: 12.3.1.2

Config Selected: primary.cfg

 INSTRUCTION 4 (7)
Prepared (Subject resp) No.

Rajesh Singh (errhssh)

Approved (Document resp) Checked Date Rev Reference

2013-12-19 A 1/109 22-CXC 132 9107

Uen Rev V
Config Booted: Factory Default

primary.cfg Created by ExtremeXOS version 12.3.1.2

123472 bytes saved on Wed Dec 18 13:35:58 2013

Note. In this switch ‘Config Booted’ has ‘Factory Default’ configuration which needs to be changed before
upgrading. Here this configuration should ‘primary.cfg’ or ‘secondary.cfg’
- Reboot the NWI-E switch at this step.
Command: reboot
Wait for 2 Minutes and check Switch is Operational and all ports are active /ready state.

New Print:
Image Selected: primary
Image Booted: primary
Primary ver: 12.3.1.2
Secondary ver: 12.3.1.2

Config Selected: primary.cfg

Config Booted: primary.cfg

5. Login to SMO and Click on NWI-E A NE, Right Click on the same and select Upgrade NE, now select available
software package which needs to be loaded.

6. Here you can add more NE for same switch upgarde job.
A Switch upgrade can be done on a number of switches in parallel in the same SMO job. But all Switches to
be upgraded must be connected to the passive side, so the two switches belonging to the same BSC cannot
be upgraded at the same time.
 INSTRUCTION 5 (7)
Prepared (Subject resp) No.

Rajesh Singh (errhssh)

Approved (Document resp) Checked Date Rev Reference

2013-12-19 A 1/109 22-CXC 132 9107

Uen Rev V

7. In Appeared Window Click Next and Select Immediate in place of Manual and Click Next.

8. Under the Job Parameters select another Tab “NE Parameters” and fill correct parameters as below
 INSTRUCTION 6 (7)
Prepared (Subject resp) No.

Rajesh Singh (errhssh)

Approved (Document resp) Checked Date Rev Reference

2013-12-19 A 1/109 22-CXC 132 9107

Uen Rev V

.
Mention IMAGE version: 15.1.3.4 path1-2 exactly.

9. Add a Comment which will make you to identify your Job Later and click Finish
 INSTRUCTION 7 (7)
Prepared (Subject resp) No.

Rajesh Singh (errhssh)

Approved (Document resp) Checked Date Rev Reference

2013-12-19 A 1/109 22-CXC 132 9107

Uen Rev V
10. Now Go to Jobs in SMO identify Your job by the Job comment you have Given, Select it and click logs
beneath it as it will show the progress of Upgrade

Generally 1 side upgrade will take 30-45 min.

After 100 % execution unblock RP group “BLRCE:GROUP=GBIP,NET=A;”

11. Then Make APG Node B Passive and Give the Command
“BLRCI:GROUP=GBIP,NET=B;”
And Carry on the Upgrade for B side and Follow all the steps.
Do remember to Unblock RP Groups after completion of B side Upgrade
“BLRCE:GROUP=GBIP,NET=A”

12. Ask Drive tester to take a drive in BSC and check CS and PS calls.
13. After Confirmation of drive tester Take a Health Check of BSC and NWI-E’s.
14. Job Completed, prepare the report.

15. ROLL-BACK
In Case Roll Back Is needed then Fallback is needed to be Selected in Select Activity Column.