Problem Description.

A bureau customer reports that a OSN1500 device reports NESOFT_MM alarm after replacing the 83-slot PCXL board. Querying the master board version in the network management, they are all 5.36.30.15P01.
Querying with :hbu-get-backup-info returns Backup-Info : 0x00000002 , the master-backup synchronization fails.

Alarm Information

NESOFT_MM parameters are: 0x02, 0x03, 0x00, 0x08, 0xFF

Processing

1, query NESOFT_MM alarm meaning
According to OSN1500 alarm information, found that the device alarm meaning for the main and backup main control board NeSoft and Platform is inconsistent.
2. Use the command line to query the versions of the two masters:

:sftm-get-testver:82
VERSION-INFORMATION(INCLUDING-PATCH-INFORMATION)
NESOFTNAME VER DATE STATE TEST-VERSION-INFO
NFS 5.36 .30.15P01 20100220 Running T02
NSF1 5.36.30.15P01 20100220 active T02
NSF2 5.36.30.15P01 20100220 inactive T02
INI1 5.36.30.15P01 20091218 active T02
INI2 5.36.30.15P01 20091218 inactive T02
BIOS 08.09.04 20100716 inactive T01
ExtBIOS 09.09.04 20091218 active T01
Logic (U1028)120
LogicE01 ( U1033)300
DRV V1.02 20090515 active T04
Total records :10

:sftm-get-testver:83
VERSION-INFORMATION(INCLUDING-PATCH-INFORMATION)
NESOFTNAME VER DATE STATE TEST-VERSION-INFO
NFS 5.36.30.15P01 20100220 Running T02
NSF1 5.36.30.15P01 20100220 active T02
NSF2 5.36.30.15P01 20100220 inactive T02
INI1 5.36.30.15P01 20091218 active T02
INI2 5.36.30.15P01 20091218 inactive T02
BIOS 08.09.03 20091218 inactive T01
ExtBIOS 09.09.04 20091218 active T01
Logic (U1028)120
LogicE01 (U1033)300
DRV V1.02 20090515 active T04
Total records :10

found that the software versions queried by the primary and backup masters are the same, but the base BIOS is not. Check the version matching table, the base BIOS should be 08.09.03.

3. Use
:sftm-show-dir:82,"/ofs1/hwx"
:sftm-show-dir:82,"/ofs2/hwx"
:sftm-show-dir:83,"/ofs1/hwx"
:sftm-show- dir:83,"/ofs2/hwx"
:sftm-show-dir:82,"/ofs1/fpga"
:sftm-show-dir:82,"/ofs2/fpga"
:sftm-show-dir:83,"/ofs1/fpga"
:sftm-show-dir:83,"/ ofs2/fpga"
and other commands to query the hwx and fpga folders in the OSF1 and OSF2 directories of the master and backup masters respectively, and found that there is one less sccpkg.ini file under the 82-slot master/ofs2/hwx than the corresponding directory of the 83-slot backup master. Checking the version matching table and other normal network elements, I found that this file should exist.

Problem Location:
The files in osf2/hwx of the 82-slot master are inconsistent with those of the 83-slot. The 82-slot base BIOS is not the version required by the version table.


Treatment:
Use Toolkit to reload the PCXL package of slot 82 at board level, and then downgrade the base BIOS to 08.09.03. After observing for some time, the alarm is no longer reported. Problem solved.

Root Cause

Cause 1: The software versions currently running on the master and backup boards are inconsistent.

Cause 2: The software versions in the master and backup zones (OFS1 and OFS2) of the master board are inconsistent.

Cause 3: There is no file with the same name in the corresponding directory of the pair of boards on the master and backup boards.

Suggestion and Summary

1, NESOFT_MM alarm is not reported only when the master and backup master control versions are not the same, but also when the file inspection finds that the files in the directory are not the same, so you need to carefully analyze the alarm parameters.

2、The company's spare parts may be inconsistent with the version running on the network, so you need to pay attention to the replacement of spare parts.