No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.


Abnormal Automatic Matching During the OptiX OSN 6800 Package Loading

Publication Date:  2012-07-25 Views:  112 Downloads:  0

Issue Description

In the OptiX OSN 6800 package upgrade project, insert the upgraded SCC (from to into the subrack. Insert the OTU, amplifier board and other boards in the subrack. Enable the automatic matching function to upgrade these boards. Some time later, however, the OTU, amplifier board and other boards are still not upgraded and the SCC reports the SWDL_CHGMNG_NOMATCH alarm.
The SCC version information is as follows:
BIOS 8.20.03T02 20070413 17:07:41 inactive
ExtBios 9.20.04T02 20070808 22:25:16 active
NeSoft(D) 20070815 16:44:36
Platform(D) 5.00.08.B01c 20070706 12:22:35
Logic (U109)120Dsp 

Alarm Information


Handling Process

Insert the SCC and wait until the indicators are normal. Wait for ten more minutes and then insert other boards. 

Root Cause

The causes of the SWDL_CHGMNG_NOMATCH alarm are as follows:
The SCC software version and software package version for replacement are inconsistent with original versions. The SCC for replacement mismatches software versions of other boards in the subrack. To avoid the alarm generated due to incorrect load mismatch, the SCC version should be later than other board versions in the subrack.
At this time, the SCC is upgraded first and then other boards are upgraded. Other boards are inserted after all SCC indicators become normal. But other boards still mismatch the SCC.
After the original SCC is powered on, even if the indicators are normal, you should wait for 5 to 10 minutes until the SCC works stably. That is, when using a Toolkit to load packages, you can see a process from the normal state to the stable state.
If you insert other boards in the subrack in the waiting period, the loading information of the SCC is unstable. After the information becomes stable, other boards are started. Hence, inconsistent board versions are detected. If you insert other boards first and then the SCC, the same result occurs. As a result, automatic matching fails. 


Wait until the SCC state is normal and then insert other boards. Pay attention to the load sequence of the SCC and other boards.