6.3.1 Executing pre-download script fails
Symptoms
The execution of Download task on NetAct interface fails. The following error logs (as an example) are found in the ilsw_upgrade.log file (that locates in /var/log folder on
mcRNC):
2011-09-14 17:56:58 ILSWMAN: Execute pre_downloading_02_fail.sh error!
Status: 1
2011-09-14 17:56:58 SOKERI: Download pre-checking error! Status: 255, Additional Status: 25
Reason analysis
Before downloading the software delivery, the system executes the
pre_downloading_xx.sh script to do pre-download inspection if such script exists. An error in the execution of the script causes the failure of the Download task.
Recovery procedures
Steps
1 Make a copy of syslog file and ilsw_upgrade.log file (both under /var/log directory) respectively.
Software management troubleshooting Troubleshooting Multicontroller RNC
2 Send the copied files to Nokia Customer Service Center.
6.3.2 Parsing targetBD.xml fails
Symptoms
The execution of Download task on NetAct fails. The following error logs (as an example) are found in the ilsw_upgrade.log file (that locates in /var/log folder on mcRNC):
2011-09-14 16:35:58 SOKERI: Parse target BD SWPackages/default/TargetBD.xml start.
2011-09-14 16:35:59 SOKERI: Parse target BD error! Status: 17466, Additional Status: 18
Reason analysis
When the operator starts a Download task on NetAct, mcRNC downloads targetBD.xml file before downloading the actual software delivery. The reason for the failed parsing of the targetBD.xml file can be:
• The format of the targetBD.xml file is incorrect.
• Key information is missing in the file.
g
In this example, the target BD file is named as targetBD.xml. This name could be different in the real environment.Recovery procedures
1 Make a copy of the needed files The files that need to be copied are:
• targetBD.xml located in /var/opt/nsn/SS_ILOMU/SS_ILSWMAN/build/ folder
• syslog located in /var/log folder
• ilsw_upgrade.log located in /var/log folder
2 Send the copied files to Nokia Customer Service Center.
6.3.3 Executing pre-activation script fails
Symptoms
The execution of Download and Activate or Activate task on NetAct fails. The following error logs (as an example) are found in the ilsw_upgrade.log file (that locates in /var/log folder on mcRNC):
2011-09-16 09:35:56 ILSWMAN: Execute pre_activation_02.sh start
2011-09-16 09:35:56 ILSWMAN: Execute pre_activation_02.sh error! Status: 255 2011-09-16 09:35:57 SOKERI: Pre-Activate error! Status: 255, Additional Status: 25
Troubleshooting Multicontroller RNC Software management troubleshooting
Reason analysis
Before activating the software delivery, the system executes the pre_activation_xx.sh script to do pre-activating inspection if such script exists. An error in the execution of the script causes the failure of the Download and Activate or Activate task. The reason for the failed execution of the script varies depending on what are specified in the script.
Recovery procedures
1 Make a copy of syslog file and ilsw_upgrade.log file (both under /var/log directory) respectively.
2 Send the copied files to Nokia Customer Service Center.
6.3.4 Upgrading eSW fails
Symptoms
The eSW upgrade fails during the mcRNC upgrade. The status INSTALLATION_FAILED is displayed on the ACTIVE/MAIN BANK or the PENDING BANK field when you execute the SCLI command show sw-managed embedded-sw status.
Reason analysis
A successful eSW upgrade has certain requirements on the disk space. When the free disk space in the /tmp folder is below 7 MB, or the usage of the /dev/mtdblock1 file system exceeds 83%, the eSW upgrade fails.
Recovery procedures
1 Enter the bash shell as a root user.
To enter the bash shell as a root user, execute the following command:
shell bash full
2 Check the available space of each LMP.
To check the available space of LMP, execute the following command for each LMP:
ssh LMP-1-X-1 "df –h"
Example output for LMP-1-1-1
# ssh LMP-1-1-1 "df -h"
Filesystem Size Used Avail Use% Mounted on /dev/mtdblock1 117M 103M 14M 88% /
tmpfs 506M 2.6M 504M 1% /dev/shm /dev/mtdblock0 10M 2.6M 7.5M 26% /boot none 32M 31M 1M 97% /tmp none 64M 0 64M 0% /mnt/var
none 64M 22M 43M 34% /opt/fastpath/tmpfs none 64M 22M 43M 34% /opt/fastpath2/tmpfs /dev/mtdblock5 117M 96M 21M 83% /mnt/backupfs
Software management troubleshooting Troubleshooting Multicontroller RNC
3 Delete some unnecessary files to free more space.
6.3.5 Alarm 2518 - NO VALID FALLBACK COPY FOR DEFAULT PACKAGE is triggered
Symptoms
Alarm 2518 is seen both from the NetAct Alarm Monitor graphical user interface (GUI), and the mcRNC command line interface when executing show alarm active SCLI command. An example of the command output is as follows:
Alarm ID : 550
Specific problem : 2518 - NO VALID FALLBACK COPY FOR DEFAULT PACKAGE Managed object : fshaRecoveryUnitName=OMUTestServer-
0,fsipHostName=CLA-0,fsFragmentId=Nodes,fsFra
1 Enter SCLI command interface on mcRNC
To get into SCLI command interface, enter the following command:
fsclish
Troubleshooting Multicontroller RNC Software management troubleshooting
2 Create an FB build
Enter the command as follows:
save sw-manage app-sw-mgmt fb-build Expected outcome
The following output is displayed:
FB build has been saved successfully.
Unexpected outcome
The following output is displayed when the active build is not a backup (BU) build.
Current build is not BU.
For more information on creating an FB build, see Creating fallback build from active backup build.
3 Check if Alarm 2518 has been cancelled
After the new FB build is created, the alarm is cancelled automatically. You can see the result by either of the following ways:
• Use the show alarm active SCLI command or the show alarm active filter-by specific-problem 2518 command. Alarm 2518 still exists in the output, but the “Cleared” field is now “yes” and “Severity” has changed to “6 (cleared)”. For example:
Alarm ID : 550
Specific problem : 2518 - NO VALID FALLBACK COPY FOR DEFAULT PACKAGE
Managed object : fshaRecoveryUnitName=OMUTestServer- 0,fsipHostName=CLA-0,fsFragmentId=Nodes,fsFra
gmentId=HA,fsClusterId=ClusterRoot Severity : 6 (cleared)
Cleared : yes Clearing : automatic Acknowledged : no
Ack. user ID : N/A Ack. time : N/A
Alarm time : 2011-12-19 16:21:00:749 CST Event type : x2 (processing error) Application :
fshaProcessInstanceName=IL_Sokeri,fshaRecoveryUnitName=OMUTestServ er-0,fsipHostN
ame=CLA- 0,fsFragmentId=Nodes,fsFragmentId=HA,fsClusterId=ClusterRoot IAppl Addl. Info : 4
Appl. Addl. Info :
• Check the active alarms in the Alarm Monitor of the NetAct GUI. Alarm 2518 has disappeared.
Software management troubleshooting Troubleshooting Multicontroller RNC