Pre-checks before upgrade

TE to provide situation of the nodes subject to upgrade, choose the ones that are free of errors
and alarms
All nodes subject to upgrade should contain all the basic cards i.e. : 2 SYNTH boards
TE should communicate a SW release list for all the nodes subject to upgrade
Patch should be installed on server , to supervise the upgraded NEs through the existing NMS
Good working spare should be ready before the action
Item description
Synth
T-bus
Flash card 256M, charged with initial SW release (+ ISA SW if any)

Qty
1
1
1

A MIB backup should be taken locally and from OMS for the nodes subject to upgrade
Check the compatibility of the existing ISA-ES with the new release as per the below table :

Check the existing ISA SWR compatibility and perform the necessary upgrade in case needed
A print screen of alarm numbers to be taken

Page 1 of 4

1662 Software Upgrade Procedure

Below the full details of the SW upgrade action
During the upgrade of 1662 we have 2 scenarios

Scenario 1
If the 1662 node on SW 2.3 as committed release so in that case we will do the following:
1. Before the night action we will download the SW of 2.4.33 + ES16 2.04.84 + ES4 1.05.55 as a
standby
2. Beginning of the night action take snapshot of the alarms of the 2 nodes involved on the night
action
3. After that activate the SW 2.4.33 + ES16 2.04.84 + ES4 1.05.55
4. After the activation we will start downloading the SW 2.7.86 + ES16 2.04.84 + ES4 1.05.55 as
force download it will continue more than 100% , 120% something like that its normal and it
will give error at the End, the download will take about 45-60Min
5. After the previous error download again not force SW 2.7.86 + ES16 2.04.84 + ES4 1.05.55
not force it will take 2 sec and give 100% successfully and will appear on standby SW
6. Activate the SW 2.7.86 + ES16 2.04.84 + ES4 1.05.55 the node will reboot and will take 1015Min to be ready again.
7. On the server add the SW of ES16B to the SW 2.7.86 to be 2.7.86 + ES16 2.04.84 +ES4 1.05.55
+ ES16B 2.04.41 .
8. The SW must be on the servers as below snapshot

9.

Once the node became active start downloading the SW 2.7.86 + ES16 2.04.84 +ES4 1.05.55 +
ES16B 2.04.41
Page 2 of 4

10. After the download finish start the activation of the SW 2.7.86 + ES16 2.04.84 +ES4 1.05.55 +
ES16B 2.04.41
11. On the site they will add some new cards ES16B card, STM16 Module, etc .. so define them
after the last activation or you can define the cards during the download of the last SW except
ES16B dont insert it before the activation of last SW as it will include on last SW

Scenario 2
If the 1662 node on SW 2.4 as committed release so in that case we will do the following:
1. Before the night action we will download the SW 2.7.86 + ES16 2.04.84 + ES4 1.05.55 as force
download it will continue more than 100% , 120% something like that its normal and it will give
error at the End, the download will take about 45-60Min
2. After the previous error download again not force SW 2.7.86 + ES16 2.04.84 + ES4 1.05.55
not force it will take 2 sec and give 100% successfully and will appear on standby SW
3. Beginning of the night action take snapshot of the alarms of the 2 nodes involved on the night
action
4. After that activate the SW 2.7.86 + ES16 2.04.84 + ES4 1.05.55
5. Activate the SW 2.7.86 + ES16 2.04.84 + ES4 1.05.55 the node will reboot and will take 1015Min to be ready again.
6. On the server add the SW of ES16B to the SW 2.7.86 to be 2.7.86 + ES16 2.04.84 +ES4 1.05.55
+ ES16B 2.04.41 .
7. The SW must be on the servers as below snapshot

Page 3 of 4

8.

Once the node became active start downloading the SW 2.7.86 + ES16 2.04.84 +ES4 1.05.55 +
ES16B 2.04.41
9. After the download finish start the activation of the SW 2.7.86 + ES16 2.04.84 +ES4 1.05.55 +
ES16B 2.04.41
10. On the site they will add some new cards ES16B card , STM16 Module, etc .. so define them
after the last activation or you can define the cards during the download of the last SW except
ES16B dont insert it before the activation of last SW as it will include on last SW

Important Notes:

1st time of downloading 2.7 SW you have to make it force and it will continue more than 100% ,
120% something like that its normal and it will give error at the End, after that download again
2.7 but not force it will take 2 sec and give 100% successfully and will appear on standby SW
For ES16B SW, 1st download 2.7.86 + ES16 2.04.84 +ES4 1.05.55 without the SW of ES16B
then after the activation of the previous release you can add the SW of ES16B on the list to be
2.7.86 + ES16 2.04.84 +ES4 1.05.55 + ES16B and activate it.
If you are downloading any SW on node that doesnt have Standby SW present on the list , after
finishing the download some time not appear on the standby so in that case just stop/start
supervision of that node to align and it will be appear.

Upgrade post checks

Check that alarms number is still the same

Check that there is no fault appeared on any board
Check that there is no exclamation marks In any of the SYNTH boards

Roll Back scenario

Insert the previously prepared flash card

Wait until the node is reachable and start the supervision
Configure the NSAP and OS addresses
Configure LAPD
Make sure that the node is reachable to the server
Traffic can be restored by means of global download from NMS

Page 4 of 4