Manual Upgrade Procedure for RNC

17
Manual Upgrade Procedure of RNC. # Follow all the points and procedures as mentioned in the RNC Upgrade Checklist. This Doc is an alternative to point number 12 i.e. Upgrade via SMO. In this doc, The Manual Upgrade Procedure of the RNC will be shown. Use this procedure in case, Upgrade is not possible via SMO. 1. First of all we need to download the package on the node. Make sure there is Software package present in the OSS. Now, we create an upgrade package for doing FTP of the software package on the node from the OSS where the package is stored. For that, First connect to the node and fire the command: cr swmanagement=1,upgradepackage=<packagename> Then we need to give: a. The FTP IP address of the OSS. b. Path of the Upgrade Package’s xml file in the OSS.

Transcript of Manual Upgrade Procedure for RNC

Page 1: Manual Upgrade Procedure for RNC

Manual Upgrade Procedure of RNC.

# Follow all the points and procedures as mentioned in the RNC Upgrade Checklist.

This Doc is an alternative to point number 12 i.e. Upgrade via SMO.

In this doc, The Manual Upgrade Procedure of the RNC will be shown.

Use this procedure in case, Upgrade is not possible via SMO.

1. First of all we need to download the package on the node. Make sure there is Software package present in the OSS. Now, we create an upgrade package for doing FTP of the software package on the node from the OSS where the package is stored. For that, First connect to the node and fire the command:

cr swmanagement=1,upgradepackage=<packagename>

Then we need to give:

a. The FTP IP address of the OSS.

b. Path of the Upgrade Package’s xml file in the OSS.

c. OSS username

d. OSS password

Page 2: Manual Upgrade Procedure for RNC

Log is shown below for a clearer view.

31mAPRVJ02> cr swmanagement=1,upgradepackage=CXP9014711%2_R5E

110720-21:37:01 10.105.219.229 7.1m RNC_NODE_MODEL_L_1_119 stopfile=/tmp/9625Last MO: 3804. Loaded 2 MOs. Total: 3803 MOs. MO Class: UpgradePackage.

Attribute 1 of 2, ftpServerIpAddress (string): 10.2.20.211

Attribute 2 of 2, upFilePathOnFtpServer (string): /home/edinyad/CXP9014711%2_R5E/CXP9014711%2_R5E.xml

Following attributes are optional. Enter attribute value or "d" for default.Once the MO is created, these attributes cannot be changed (they are restricted).

Attribute 1 of 2, user (string): evaisax

Attribute 2 of 2, password (string): airtel123

>>> [Proxy ID = 3805] MO name :ManagedElement=1,SwManagement=1,UpgradePackage=CXP9014711%2_R5E

Page 3: Manual Upgrade Procedure for RNC

2. In the above log, we can see that a proxy is shown in the end (in red colour).We use this proxy to Force Install the Package which we hav just done FTP to. For that, next, we’ll fire the command:

acc 3805 nonblockingforcedinstall

Type ‘Y’ when asked whether we are sure or not.

Log is shown below for this step:

APRVJ02> acc 3805 nonblockingforcedinstall

110720-21:38:39 10.105.219.229 7.1m RNC_NODE_MODEL_L_1_119 stopfile=/tmp/9625Call Action nonblockingforcedinstall on following MOs ?=================================================================================== 3805 SwManagement=1,UpgradePackage=CXP9014711%2_R5E===================================================================================Are you Sure [y/n] ? Y

=================================================================================================================Proxy MO Action Nr of Params================================================================================================================= 3805 UpgradePackage=CXP9014711%2_R5E nonBlockingForcedInstall 0 >>> Return value = 160620092

=================================================================================================================Total: 1 MOs attempted, 1 MOs actioned

Page 4: Manual Upgrade Procedure for RNC

3. Next we track the upgrade by firing the command ‘pr upgr’.We take the proxy number for the corresponding upgrade package that we are working on and then fire the command ‘get <proxy> sta|prog’

Log is shown below:

APRVJ02> pr upgr

110720-21:40:10 10.105.219.229 7.1m RNC_NODE_MODEL_L_1_119 stopfile=/tmp/10996===================================================================================Proxy MO=================================================================================== 1516 SwManagement=1,UpgradeTrace=1 1600 SwManagement=1,Repertoire=RNC_DUMMY_UPGRADE 1668 SwManagement=1,Repertoire=CPP_Int_Tran_Upgrade_2 1726 SwManagement=1,Repertoire=CPP_IP_Tran_Upgrade_4 1827 SwManagement=1,Repertoire=CPP_ATM_Tran_Upgrade_2 1921 SwManagement=1,Repertoire=CPP_Control_Upgrade_4 1935 SwManagement=1,UpgradePackage=CXP9014711/2_R3B 2065 SwManagement=1,UpgradePackage=InitialUP 2099 SwManagement=1,Repertoire=CPP_SS7_Upgrade_4 2115 SwManagement=1,UpgradePackage=CXP9014711%2_R5E===================================================================================Total: 10 MOs

Page 5: Manual Upgrade Procedure for RNC

APRVJ02> get 2115 sta|prog

110720-21:40:25 10.105.219.229 7.1m RNC_NODE_MODEL_L_1_119 stopfile=/tmp/10996=================================================================================================================MO Attribute Value=================================================================================================================UpgradePackage=CXP9014711%2_R5E progressCount 12UpgradePackage=CXP9014711%2_R5E progressHeader 1 (DOWNLOADING_FILES)UpgradePackage=CXP9014711%2_R5E progressHeaderAddInfo s[0] = UpgradePackage=CXP9014711%2_R5E progressTotal 366UpgradePackage=CXP9014711%2_R5E state 5 (INSTALL_EXECUTING)=================================================================================================================Total: 1 MOs

Page 6: Manual Upgrade Procedure for RNC

4. As we can see above, the progress Count shown here is 12 and progress total is 366. Once the progress Count reaches the progress Total of 366, The progress Header shows IDLE and State is INSTALL COMPLETED.

Log is shown below:

APRVJ02> get 2115 sta|prog

110720-22:18:25 10.105.219.229 7.1m RNC_NODE_MODEL_L_1_119 stopfile=/tmp/10996=================================================================================================================MO Attribute Value=================================================================================================================UpgradePackage=CXP9014711%2_R5E progressCount 0UpgradePackage=CXP9014711%2_R5E progressHeader 0 (IDLE)UpgradePackage=CXP9014711%2_R5E progressHeaderAddInfo s[0] = UpgradePackage=CXP9014711%2_R5E progressTotal 0UpgradePackage=CXP9014711%2_R5E state 1 (INSTALL_COMPLETED)=================================================================================================================Total: 1 MOs

Page 7: Manual Upgrade Procedure for RNC

5. Then we Verify the upgrade package using the Proxy of the upgrade package using the command:

acc 2115 verifyUpgrade

Log is shown below:

APRVJ02> acc 2115 verifyUpgrade

110720-22:18:56 10.105.219.229 7.1m RNC_NODE_MODEL_L_1_119 stopfile=/tmp/10996Call Action verifyupgrade on following MOs ?=================================================================================== 2115 SwManagement=1,UpgradePackage=CXP9014711%2_R5E===================================================================================Are you Sure [y/n] ? y

=================================================================================================================Proxy MO Action Nr of Params================================================================================================================= 2115 UpgradePackage=CXP9014711%2_R5E verifyUpgrade 0 >>> Return value = 164636417

=================================================================================================================Total: 1 MOs attempted, 1 MOs actioned

Page 8: Manual Upgrade Procedure for RNC

6. Then we trace the upgrade using the proxy again and keep a track until the Progress Header goes in IDLE State again.

Log is as follows:

APRVJ02> get 2115 sta|prog

110720-22:19:07 10.105.219.229 7.1m RNC_NODE_MODEL_L_1_119 stopfile=/tmp/10996===============================================================MO Attribute Value===============================================================UpgradePackage=CXP9014711%2_R5E progressCount 0UpgradePackage=CXP9014711%2_R5E progressHeader 19 (VERIFY_CHECKSUM_FOR_LM)UpgradePackage=CXP9014711%2_R5E progressHeaderAddInfo s[0] = UpgradePackage=CXP9014711%2_R5E progressTotal 0UpgradePackage=CXP9014711%2_R5E state 1 (INSTALL_COMPLETED)===============================================================Total: 1 MOs

APRVJ02> get 2115 sta|prog

110720-22:21:34 10.105.219.229 7.1m RNC_NODE_MODEL_L_1_119 stopfile=/tmp/10996=================================================================================================================MO Attribute Value=================================================================================================================UpgradePackage=CXP9014711%2_R5E progressCount 0UpgradePackage=CXP9014711%2_R5E progressHeader 0 (IDLE)UpgradePackage=CXP9014711%2_R5E progressHeaderAddInfo s[0] = UpgradePackage=CXP9014711%2_R5E progressTotal 0UpgradePackage=CXP9014711%2_R5E state 1 (INSTALL_COMPLETED)

Page 9: Manual Upgrade Procedure for RNC

7. Fire the command ‘get <proxy of upgrade package>’ to confirm that upgrade package verification has been successfully completed and compare with the successful output marked in the ‘red’ below in the log.

Log is as follows:

APRVJ02> get 2115

110720-22:22:37 10.105.219.229 7.1m RNC_NODE_MODEL_L_1_119 stopfile=/tmp/10996=================================================================================================================2115 SwManagement=1,UpgradePackage=CXP9014711%2_R5E=================================================================================================================UpgradePackageId CXP9014711%2_R5EactionResult t[2] = >>> Struct[0] has 5 members: >>> 1.time = Date: 2011-07-20, Time: 16:45:39.842 >>> 2.typeOfInvokedAction = 3 (INSTALL) >>> 3.info = 0 (EXECUTED) >>> 4.actionId = 160620092 >>> 5.additionalInfo = Number of installed Load Module(s): 366. >>> Struct[1] has 5 members: >>> 1.time = Date: 2011-07-20, Time: 16:47:46.241 >>> 2.typeOfInvokedAction = 1 (VERIFY_UPGRADE) >>> 3.info = 0 (EXECUTED) >>> 4.actionId = 164636417 >>> 5.additionalInfo = Upgrade possible, current version is supported as from version. Detailed info: Action rebootNodeUpgrade supported: Yes Action upgrade supported: YesactualTypeOfUP 0 (ADAPTED)administrativeData Struct{5} >>> 1.productNumber = CXP9014711/2 >>> 2.productRevision = R5E >>> 3.productName = UTRAN RNC >>> 4.productInfo = Upgrade Package file for RNC CXP9014711/2 R5E.

Page 10: Manual Upgrade Procedure for RNC

8. Once the Verification is Successful, We will fire the command to begin the actual upgrade of the package for which we hav downloaded and installed the software by firing the command: acc 2115 rebootnodeupgrade.

Log is as follows:

APRVJ02> acc 2115 rebootnodeupgrade

110720-22:23:49 10.105.219.229 7.1m RNC_NODE_MODEL_L_1_119 stopfile=/tmp/10996Call Action rebootnodeupgrade on following MOs ?=================================================================================== 2115 SwManagement=1,UpgradePackage=CXP9014711%2_R5E===================================================================================Are you Sure [y/n] ? y

=================================================================================================================Proxy MO Action Nr of Params================================================================================================================= 2115 UpgradePackage=CXP9014711%2_R5E rebootNodeUpgrade 0 >>> Return value = 165129422

=================================================================================================================Total: 1 MOs attempted, 1 MOs actioned

Page 11: Manual Upgrade Procedure for RNC

9. Keep tracing the upgrade using the proxy.Note: The proxy of the upgrade package changes during the upgrade after the large restart hence make sure you are tracing the correct proxy.Verify the proxy by firing the command ‘pr upgr’ as was explained above.

Once the upgrade is done, The State becomes Awaiting Confirmation.

Log is as follows:

APRVJ02> get 2073 sta|prog proxy is changed after large restart

110720-22:40:01 10.105.219.229 7.1m RNC_NODE_MODEL_L_1_123 stopfile=/tmp/10996=================================================================================================================MO Attribute Value=================================================================================================================UpgradePackage=CXP9014711%2_R5E progressCount 14UpgradePackage=CXP9014711%2_R5E progressHeader 31 (WAIT_FOR_CONF_UPGRADE)UpgradePackage=CXP9014711%2_R5E progressHeaderAddInfo s[0] = UpgradePackage=CXP9014711%2_R5E progressTotal 16UpgradePackage=CXP9014711%2_R5E state 3 (AWAITING_CONFIRMATION)=================================================================================================================Total: 1 MOs

Page 12: Manual Upgrade Procedure for RNC

10. Once the state shows ‘Awaiting Confirmation’, the next thing you need to do is to Confirm the Upgrade by firing the command:

acc 2073 confirmupgrade

Log is as follows:

APRVJ02> acc 2073 confirmupgrade

110720-22:40:24 10.105.219.229 7.1m RNC_NODE_MODEL_L_1_123 stopfile=/tmp/10996Call Action confirmupgrade on following MOs ?=================================================================================== 2073 SwManagement=1,UpgradePackage=CXP9014711%2_R5E===================================================================================Are you Sure [y/n] ? y

=================================================================================================================Proxy MO Action Nr of Params================================================================================================================= 2073 UpgradePackage=CXP9014711%2_R5E confirmUpgrade 0 >>> Return value = null

=================================================================================================================Total: 1 MOs attempted, 1 MOs actioned

Page 13: Manual Upgrade Procedure for RNC

11. Finally the Upgrade is Successfully completed and confirmed once the Upgrade progress Header shows IDLE State again.

Log is as follows:

APRVJ02> get 2073 sta|prog

110720-22:41:15 10.105.219.229 7.1m RNC_NODE_MODEL_L_1_123 stopfile=/tmp/10996=================================================================================================================MO Attribute Value=================================================================================================================UpgradePackage=CXP9014711%2_R5E progressCount 0UpgradePackage=CXP9014711%2_R5E progressHeader 0 (IDLE)UpgradePackage=CXP9014711%2_R5E progressHeaderAddInfo s[0] = UpgradePackage=CXP9014711%2_R5E progressTotal 0UpgradePackage=CXP9014711%2_R5E state 7 (UPGRADE_COMPLETED)=================================================================================================================Total: 1 MOs

12. Finally you can check the Software Level by firing the command ‘cvls’.