NO_BD_SOFT Alarms
NO_BD_SOFT is the No Software for Veneer Board alarm. This alarm indicates that the software required for the single board is not available on the single board, or the single board software has the wrong name.
Alarm Attributes
|
Alarm Level |
Alarm Type |
|
Emergency |
Device |
Alarm Parameters
When you view the alarm in the network management, select the alarm, and the alarm parameters will be displayed in the "Alarm Details". The format of alarm parameters is "Alarm Parameters ( hexadecimal ): Parameter 1 Parameter 2...Parameter n ". See the following table for the meaning of each parameter.
|
Parameter name |
Meaning of parameter |
|
Parameter 1 |
For packet domain cross board, parameter 1 is fixed to 0x01. For packet processing boards, packet interface boards, indicates the board number. For other single boards, it is fixed to 0x01 and has no meaning. |
|
Parameter 2, Parameter 3 |
For packet domain cross boards, parameter 2 and parameter 3 indicate the type of file missing from the single board software, parameter 2 is fixed to 0x00, and parameter 3 has the following specific meanings: - 0x01indicates that the master software is missing. - 0x02indicates that the master logic file is missing. - 0x03indicates that the function or auxiliary logic file is missing. - 0x81indicates that the ini file is missing. - 0x0Dindicates a missing BIOS file. For other single boards, indicates the missing file number. For example, for EFT8, EFT8A, R1EFT4 single boards, parameter 2 is fixed to 0x00, and parameter 3 has the following specific meaning: - 0x01indicates that the hwx file of the single board is lost. - 0x03indicates that the net element ini file is missing. - 0x07indicates that the FPGA control logic is missing. - 0x09indicates that the extended BIOS is missing. If N4EFS0, N2EFS4, N5EFS0, N1EFS0A, N2EGT2, N3EFS4, N3EGS2, N1EMS2 veneer boards, parameter 2 is fixed to 0x00, and parameter 3 has the following specific meaning: - 0x01indicates that the single board software is lost. - 0x03indicates that the network element ini file is lost. - 0x05indicates that a chip logic is lost. - 0x07indicates that FPGA control logic is missing. - 0x09indicates that the extended BIOS file is missing. For example, for N1EGS4 and N3EGS4 single boards, parameter 2 is fixed to 0x00, and the specific meaning of parameter 3 is as follows: - 0x01indicates that the single board software is lost. - 0x03indicates that the network element ini file is lost. - 0x05, 0x07 indicates that a part of the logic of the single board is lost. - 0x09indicates that the extended BIOS file is missing. - 0x0Bindicates that the configuration file is missing. For example, for N1EAS2 single board, parameter 2 is fixed to 0x00, and the specific meaning of parameter 3 is as follows: - 0x01indicates that the single board software is lost. - 0x02indicates that the network element ini file is lost. - 0x03means FPGA is lost. - 0x04indicates that the extended BIOS file is missing. - 0x05indicates that the configuration file is missing. If N4EGS4 single board, parameter 2 is fixed to 0x00, and parameter 3 has the following specific meaning: - 0x01indicates that the single board software is lost. - 0x02indicates that the configuration item is lost. - 0x03indicates FPGA loss. - 0x04indicates that the extended BIOS file is missing. If SDH, DDN, PDH, Raman amplification type of single board, parameter 2 is fixed to 0x00, parameter 3 has the following specific meaning: - 0x01indicates that the single board software is lost. - 0x02means FPGA file is lost. - 0x0Dindicates that the extended BIOS file is missing. - 0x81indicates that the network element ini file is missing. - 0x03indicates that the function or auxiliary logic file is missing. (Only for N1SLQ16 and N1SLD16 single boards) If OBU1 single board, parameter 2 is fixed to 0x00, and the specific meaning of parameter 3 is as follows: - 0x01indicates that the primary single board software is lost. - 0x02indicates that the standby single board software is lost. - 0x03indicates that the primary FPGA software is lost. - 0x04indicates that the standby FPGA software is lost. - 0x05indicates that the main ini file is missing. - 0x06indicates that the backup ini file is missing. - 0x07indicates that a part of the primary logic of the single board is missing. - 0x08indicates that a part of the standby logic of the single board is missing. - 0x0Bindicates that the current configuration file is missing. - 0x0Dindicates that the DSP parameter table is missing. For example, VST4 single board, parameter 2 is fixed to 0x00, and the specific meaning of parameter 3 is as follows: - 0x01indicates that the single board software is lost. - 0x02indicates that the single board FPGA file is missing. - 0x03means firmware FPGA file is lost. - 0x81indicates that the network element ini file is missing. |
|
Parameter 4 |
Parameter 4 is meaningless for packet domain cross boards. For N1SLQ16 and N1SLD16 boards, parameter 4 is meaningless. For other single boards, indicates the cause of the alarm: - 0x01: File does not exist. - 0x02: File checksum failure. - 0x04: Inconsistent file versions in the master and backup areas. - 0x08: Inconsistent file versions for master and backup boards. - 0x0E: File validation failed, and the version of the file is inconsistent with the version of the corresponding file in the backup zone, and the version of the corresponding file on the backup board. |
|
Parameter 5 |
Not used. |
Impact on the system
The impact of this alarm on the system is as follows:
- If you do not reset the board that reported the alarm, the services and functions of the board will not be affected.
- If you reset the single board that reported the alarm, the single board will not be able to start. For processing boards that are not configured with protection, the service is interrupted; for processing boards that are configured with protection, the service is reversed.
Possible Causes
The alarm NO_BD_SOFT arises for the following possible reasons:
- The single board software is not loaded.
- The single board software is incorrectly loaded or missing.
- The FPGA program in the single board file system is missing or incorrect.
Processing steps
1. Check the alarm information on the network management, identify the board that generates the alarm, and identify the type of veneer software that is missing from the board.
2. After reloading the single board software, soft reset the faulty single board through the network management. Check whether the alarm is canceled.
3. If the alarm is still not removed, replace the board that generated the alarm.


Chinese
English





