Hello,
Today, I would like to share with you this topic which describe the Recovery method for data single board in BIOS state caused by wrong deletion of single board data.
Problem
A local employee in my country used a script to delete the database of one of the data boards of a certain network element due to operational errors. After the board was hard reset, the board could not go online and was in the BIOS state.
Alarm message
The board reports NO_BD_SOFT critical alarms and BIOS_STATUS, COMMUN_FAIL critical alarms.
Process
1- The data veneer file is missing. First, obtain veneer files of the same veneer model, version and normal operation. The most suitable method on site is to copy the same version and model of the single board file of the same network element or gateway network element (other network elements are also possible, and the gateway network element can log in faster through ftp).
Steps:
1) Use Navigator to log in to the network element where the board to be copied is located. Use the cm-set-ftp:open command to enable the ftp function of the network element, and use the cm-get-ip command to obtain the IP address of the network element.
2) Log in to the network element where the board that needs to copy the file by ftp, and find the folder corresponding to the board that needs to copy the file according to the slot (the folder is named after the board slot). Copy all the files in the folder to the laptop.
2- Copy the board file back to the board with the missing file (that is, the board in the BIOS state).
Steps:
1) Use Navigator to log in to the NE where the board in the BIOS state is located. Use the cm-set-ftp:open command to enable the ftp function of the network element, and use the cm-get-ip command to obtain the IP address of the network element.
2) Use ftp to log in to the network element where the board is in the BIOS mode (if remote login is not possible, you need to go to the site to operate, connect the laptop to the ETH communication port of the auxiliary board with a direct network cable), and find the BIOS according to the slot The folder corresponding to the state of the board (the folder is named after the board slot). Delete all files in the folder (note that the folder should be kept), and copy all the contents of the folder previously copied to the portable computer to the board folder.
3- Use the cfg-reset-board:X,hard command to hard reset the board (X is the slot number of the board). It can also be reset by plugging and unplugging the single board on site.
Root cause
According to the structure of the file system of the network element data single board, the fpga file of the data single board exists in the file system with a file extension of pga, and is loaded into the logic chip by the BIOS boot during hard reset or power-on (soft reset will not Start fpga file loading). During normal operation, deleting the fpga file in the file system does not affect the normal operation of the system, but if a hard reset or power-off restart at this time will cause the board to stay in the BIOS state. The data veneer software is stored in the file system with files with extensions such as hwx, ini, and cfg. When the soft reset of the single board is started, the BIOS boot software enters the memory to run, and executes various functions of the data single board. During normal operation, deleting the software in the file system has no effect, but once the board is soft reset and the file in the file system does not exist, it will stay in the BIOS state. Combined with the descriptions of local employees, it can be preliminarily judged that the fpga file or software of the data veneer is missing, which causes the BIOS to fail to boot the veneer. The board is always in the BIOS state, so three alarms of NO_BD_SOFT, BIOS_STATUS, and COMMUN_FAIL appear.
Recommendations
Database operations are relatively dangerous operations, especially when using scripts to issue commands. Unlike the network management system, there are prompts. It is recommended that you use the network management system for all subsequent operations.
You are welcome to leave a message and exchange in the comment area. Thank you!
