Problem description

A bureau's original OSN3500 device is installed and configured with N1EFS4 veneer, R3 version, and when expanding the capacity, it needs to replace the N1EFS veneer with N2EFS veneer (the new veneer) and upgrade the software to R6 version.

In the field operation, firstly, the N2EFS single board is directly inserted into the original N1EFS single board position, and then the whole network element is upgraded to the R6 version through the simulation package loading function.

After the upgrade is completed, check the EFS single board BDSOFT version is 3.17, FPGA ( U42 ) is 208, EXTBIOS is 222, which is the software of N1EFS4.

Reconfigure the single board as N2EFS4, plug and reset the single board, the single board can not work properly, configure it as N1EFS4, it can work properly.

Warning Message

1. Configure the single board as N1EFS4, it can work normally, but cannot realize the function of N2EFS4.

2、Configured as N2EFS4 single board, generating bd_status alarm

Processing

1、Reload the N2EFS4 single-board software through toolkit and navigator software. Due to the function of anti-misloading, the software of N2EFS4 cannot be loaded.

2、Open the FTP function of COM port, re-upgrade N2EFS4 through FTP, after the upgrade is completed, re-plug the single-board, the host is correctly recognized as N2EFS4 single-board, query BDSOFT is 4.13, FPGA ( U42 ) is 210, EXTBIOS is 231.

3. Problem solved.

Root cause

1, SSN2EFS4 single board and N1EFS4 single board have different BDSOFT and FPGA ( U42 ) versions.

2. Because the N2EFS4 single board has a multi-board ID function, the N2EFS4 single board is used as the N1EFS4 when the N2EFS4 is inserted into the subframe and originally configured as the N1EFS4. When the simulation package is loaded to upgrade the network element, toolkit recognizes N2EFS4 as N1EFS4 and upgrades the software of N1EFS4.

Recommendations and Summary

When the multi-board ID function works, the query result for both physical and logical board types are returned as the current working board type, causing toolkit to fail to correctly recognize the real board type and load the correct single-board software, triggering the problem as above.

According to statistics, when SSN2EFS4 replaces N1EFS4, N2EFS0, N4EFS0 replaces N1EFS0, and N4EFS0 replaces N2EFS0, the above problem occurs when the analog packages are loaded, resulting in the disappearance of the multi-board ID function.

To avoid similar problems, it is recommended not to load or activate the software of these single boards when using analog packet loading with substitutions as above, or to use board-level upgrade mode.

If the problem arises from upgrading with analog package loading, it can be solved by FTP upgrading in case of emergency, while other cases can be solved by board replacement.