Summary:
When the active system control board on an NG-SDH product of a version listed in
Versions Involved in the preceding table starts from a reset, there is a possibility
that the patch package module cannot obtain the software version of the active system
control board. As a result, software version verification fails when a patch is loaded,
and the patch cannot be installed on the active system control board.
[Problem Description]
Trigger condition:
1. A patch of a version listed in Versions involved in the preceding table is installed
on OSN 1500/OSN 2500/OSN 3500/OSN 3500 II/OSN 7500 equipment.
2. The system control board starts from a reset.
Symptom:
A hot patch cannot be installed on the active system control board.
Identification method:
1. The version of an OSN 1500/OSN 2500/OSN 3500/OSN 3500 II/OSN 7500 NE is
V100R010C03.
2. Query the NE version by running the following command or using the NMS.
SDH
3. Run the following command to query the version of the active system control board
recorded in the patch package:
:mon-get-dump:18,”PATCH.IPATCH.CPATCH”,”018″
The numbers in red represent the slot ID of the active system control board.
The command output indicates that the version of the active system control board is
empty (the ProgVer field behind the slot ID of the active system control board is empty,
as shown in the following figure).
SDH
[Root Cause]
After the active system control board starts from a reset, the patch package module issues
a command to the software management module to query the software version. Because the
CPU is busy, the software management module does not send the software version to the
patch package module within the timeout period. As a result, the query for the software version
times out, and the software version of the active system control board recorded in the patch
package is empty. When the patch is installed, the NE software verifies the software version of
the active system control board and finds that it is not consistent. The verification fails, and the
installation of the hot patch for the active system control board is stopped.
[Impact and Risks]
A patch cannot be installed for the active system control board. Issues which can be resolved by
installing a hot patch remain unresolved.
Measures and Solutions
Preventive measure:
Before installing a patch, run the following command to query whether the version of the active
system control board recorded in the patch package is empty:
:mon-get-dump:18,”PATCH.IPATCH.CPATCH”,”018″
The numbers in red represent the slot ID of the active system control board.
In normal cases, the ProgVer field behind the slot ID of the active system control board records
the detailed version number, as shown in the following figure.
SDH
When exceptions occur, the ProgVer field behind the slot ID of the active system control board is
empty, as shown in the following figure.
SDH
If the version is empty, warm reset the active system control board, or perform an active/standby
switchover between the system control boards (for details, see recovery measures). Then, query the
software version of the active system control board again to ensure that the software version is recovered.
Recovery measures:
5. When possible, warm reset the active system control board.
6. If an NE houses an active system control board and a standby system control board, a patch has
been installed on the standby system control board, and batch backup operations on the active and
standby system control boards are complete, then manually trigger an active/standby switchover
between the active and standby system control boards to resolve the issue when possible.
Solution:
Upgrade the NE software to V100R010C03SPC220 (which will be released in the first quarter of 2015)
or a later version, in which the patch going-online mechanism of the active system control board is
optimized and the query for the software version of the active system control board will not time out.
[Rectification Scope and Time Requirements]
N/A
[Rectification Instructions]
N/A
[Appendix]
N/A
[Inspector Applicable or Not]
Use the inspector to check the entire network. Upon detection of an NE that is suspected to have this issue,
it is recommended to perform the recovery measures and then upgrade the NE.
Version of the inspector: SmartKit V200R009C00SPC201 or later
Inspector upgrade package:
Common_Inspector_V200R009_ON_20140909163631680.exe
Inspector_V200R009_ON_OptiX OSN 1500, OptiX OSN 1500+,+_20140909163631780.exe
Test case name (which will be released at the end of September 2014): Check whether the version number
of the active system control board cannot be obtained and the hot patch cannot take effect.
Comments are closed