Symptom
The OptiX OSN 6800 V100R004C01 version or before and the OptiX OSN 3800 V100R004C01 version or before use the software upgrade with the Toolkit.
The OptiX OSN 6800 and OptiX OSN 3800 automatically matches the master and slave subracks and software packages on them, and reacts differently to the operations on the SCC of the original WDM products such as insertion, removal, and reset.
Loading software package: All files that need to be stored on the NE are bundled into a package (including NE software, board software, INI file, FPGA file, and extended BIOS). This package is sent to the active SCC and copied to the standby SCC and other boards. Finally, the NE software, board software, and FPGA file start running to upgrade the NE.
Automatic software package matching: When the new inserted standby SCC board working normally, the active SCC checks the matching state according to the information sent from the standby SCC. If the software package is mismatched, the active SCC copies a new software package to the standby SCC, and activate the new software package on the standby SCC. This can ensure the consistency of the software on the active SCC and standby SCC.
For details on the symptom, see Table 1.
Cause analysis
Relevant alarms:
When the software package version is inconsistent between the active and standby SCCs, the SCC reports the alarm indicating software mismatch (MSSW_DIFFERENT).
If the new software mismatches the software of any board after the single SCC is replaced, the "replace SCC" alarm is reported (SWDL_CHGMNG_NOMATCH). This alarm can be cleared by loading the package through the Toolkit.
If the configuration data between the new SCC and the original SCC is different, the CFGDATA_OUTRANGE alarm is reported.
Procedure
For details on how to handle the effect caused by inserting, removing, and resetting operations on the SCC, see Table 1.
Reference Information
|
Table 1 Affection of plugging & unplugging and resetting operations of the SCC |
||||
|
SCC Type |
Maintenance Operation |
Phenomenon |
Possible Alarm |
Recommended Handling |
|
Single SCC in master subrack |
Remove and insert the original SCC |
Configuration data on the SCCs is not consistent. |
CFGDATA_OUTRANGE |
Use the Toolkit to deliver the backup configuration data of the SCC. |
|
A board of the same version is inserted when the SCC is out of position (including the SCC in the slave subrack) |
- |
The board gets into service normally. |
||
|
A board of a different version is inserted when the SCC is out of position (including the SCC in the slave subrack) |
SWDL_CHGMNG_NOMATCH |
Use the ToolKit to load the package correctly. |
||
|
Replace SCC |
Replace the SCC with one of the same software version. |
If the configuration data between the new SCC and original SCC is different, the "CFGDATA_OUTRANGE" alarm is reported. If the configuration data is the same, the alarm is not reported. |
- |
|
|
Replace the SCC with one of a different software version. |
SWDL_CHGMNG_NOMATCH |
Use the ToolKit to load the package correctly. |
||
|
Dual SCC master in subrack |
Remove and insert the active SCC. |
The active SCC and standby SCC are switched. The state of the NE software is inconsistent with the state of the standby SCC. When the SCC is of the same software version, there is no effect. When the SCC is of a different software version, automatic package loading is performed to match the current NE software version, and an alarm is reported during the matching period. |
MSSW_DIFFERENT |
Wait until the NE software matches the software package automatically. |
|
Remove and insert the standby SCC. |
When the SCC is of the same software version, there is no effect. When the SCC is of a different software version, automatic package loading is performed to match the current NE software version, and an alarm is reported during the matching period. |
MSSW_DIFFERENT |
Wait until the NE software matches the software package automatically. |
|
|
SCC in slave subrack |
Remove and insert the original SCC. |
The slave subrack is not reachable to the T2000. |
- |
- |
|
Replace the SCC. |
When the new SCC is of the same software version as the original SCC, there is no effect. |
- |
- |
|
|
When the new SCC is of a different software version from the original SCC, automatic package loading is performed to match the current NE software version. |
- |
- |
||
