Manual Upgrade Procedure For RNC
Manual Upgrade Procedure For 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 Packages xml file in the OSS.
c. OSS username
d. OSS password
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, well fire the command:
acc 3805 nonblockingforcedinstall
Type Y when asked whether we are sure or not.
Log is shown below for this step:
3.
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
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.
5.
Then we Verify the upgrade package using the Proxy of the upgrade package
using the command:
acc 2115 verifyUpgrade
Log is shown below:
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:
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:
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:
9.
Log is as follows:
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:
11.
Finally the Upgrade is Successfully completed and confirmed once the Upgrade
progress Header shows IDLE State again.
Log is as follows:
12.
Finally you can check the Software Level by firing the command cvls.