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.


New SCC Boards not recognized by NE

Publication Date:  2018-02-27 Views:  181 Downloads:  0
Issue Description

After a fire, customer need to change all components including the rack (OSN 8800 T1). He has problem to get both SCC boards up and running. They are not recognized. Nothing happens after formatting the SCC board.

The operation that customer performs:

- started the NE with the old SCC board

- formatted the new SCC board by setting the jumper to 1111

- then removed the jumper and plugged the board back in

- customer expected that new board synchronize with the old board

- the PROG led of the new board switches to red after some time

- the NE shows an alarm saying that the board SW version does not match the NE SW version (SWDL_CHGMNG_NOMATCH)

- old SCC board sw version: TN52SCC01

Alarm Information


Handling Process

Check carefully all information provided by customer, an see a key word : jumper set to 1111.


Root Cause

Since the customer set the jumpers to 1111, this means that all data was cleared, and the BIOS can not start, so, implicitly, the synchronization will not be done.


To recover the SCC data, we need a slave shelf.

If there is a slave shelf, pull out the new SCC board from master shelf and set the board jumpers as 0000, then insert the board in the slave shelf. Wait 30 minutes for synchronization. Then, pull out the new SCC board from slave shelf, insert it in master shelf and confirm that there is no SWDL alarm on NE.


If in the slave shelf there are two SCC boards, pull out one of them, and follow the above steps. ( step 1-6 from picture below)