OSN1500 BIOS_STATUS is a BIOS state alarm. By default, this alarm is reported when the single board software fails to load for three consecutive times within five minutes and the single board is in BIOS state. When a single board software exception or hardware exception causes this alarm, the service is interrupted. The possible reasons for the alarm BIOS_STATUS are as follows: 1) Software loss. 2) Wrong software loaded. 3) Software read/write abnormality. 4) Hardware failure of the single-board.

Problem Description

Due to an operational error, a local employee of Country Y Representative Office used a script to delete the database of one of the data veneers of a network element, and a hard reset of the veneer resulted in the veneer not being able to come online in the BIOS state.

Alarm message

The single board reports NO_BD_SOFT emergency alarm and BIOS_STATUS, COMMUN_FAIL important alarms.

Processing

1, data veneer file is missing, first of all, to obtain the same veneer model, the same version and normal operation of the veneer file. The most suitable method is to copy out the same version and model of the veneer file from the same network element or gateway network element (other network elements are also available, and gateway network elements are faster through ftp login). Operation steps:

1) Use Navigator to log in to the network element where the veneer you need to copy software from is located. Use the command cm-set-ftp:open to open the ftp function of the network element, and use the command cm-get-ip to get the IP address of the network element.

2) Login to the network element where the single board you need to copy files from by ftp, and find the folder corresponding to the single board you need to copy files from according to the slot (the folder is named after the single board slot). Copy all the files in the folder to the portable computer.

Copy the files back to the missing board (i.e., the board in BIOS state). Operation steps:

1) Use Navigator to log in to the network element where the single board in BIOS state is located. Use the command cm-set-ftp:open to turn on the ftp function of the network element, and use the command cm-get-ip to get the IP address of the network element.

2) Login to the network element where the single board in BIOS state is located by ftp (if you cannot log in remotely, you need to go to the site to operate, connect the portable computer to the ETH communication port of the auxiliary board with a direct cable), and locate the folder corresponding to the single board in BIOS state according to the slot (the folder is named according to the slot of the single board). Delete all the files in the folder (note that the folder should be kept), and copy all the contents of the folder previously copied to the portable to the single board folder.

3. Use the command cfg-reset-board:X,hard to hard reset the board (X is the slot number of the board). If you are at the site, you can also reset the board by unplugging it.

Root Cause

According to the structure of the file system of Netscape's data veneer, the fpga file of the data veneer exists in the file system as a file with the extension pga, and is loaded into the logic chip by the BIOS bootloader during a hard reset or power-on (a soft reset will not start the loading of the fpga file). During normal operation, deleting the fpga file from the file system does not affect normal system operation, but a hard reset or power-down reboot at this time will cause the board to stay in the BIOS state. The data veneer software is stored in the file system with the extension hwx, ini, cfg and other files. When the single-board soft reset is started, the software is guided by the BIOS to run in the memory and execute the functions of the data single-board. In normal operation, the deletion of the software in the file system has no effect, but once the single board soft reset, the files in the file system does not exist, it will stay in the BIOS state. Combined with the description of the local staff, it can be initially judged that the data veneer fpga file or software is missing, resulting in the BIOS can not guide the veneer startup. It makes the single board stay in the BIOS state, so the three alarms NO_BD_SOFT, BIOS_STATUS, and COMMUN_FAIL appear.

Suggestions and Summary

Database operation is a relatively dangerous operation, especially the use of scripts to issue commands, unlike the network management as well as prompts, it is recommended to use the network management for all such operations.