Methods for using boards whose FTP function is recovered in BIOS state

1. Set the PC IP address on the same network segment as that of the NE. Connect the PC to the NM_ETH port of the upgraded NE using a network cable. Run the :cm-set-ftp:open command to enable the FTP function using the Navigator. Open the IE browser and enter the NE IP address ftp://129.9.*.* to log in to the NE.
Character strings such as bd1 and bd10 indicate storage areas of the boards in corresponding slots. Find the board whose hardware version is the same as the faulty one. Copy the files in the osf1\fpga and osf1\hwx folders to the local computer to restore the faulty board.
2. If the desired board is in the slave subrack, run the :cfg-set-dir-map:1-1 (subrack ID-slot ID) command to add a path for the board in the slave subrack. Log in to the NE using the FTP. The board in the slave subrack is displayed.
3. Log in to the faulty NE using the same method and find the faulty board. Copy the local files to the corresponding folder. Generally, boards in BIOS state can still communicate with the SCC board through the internal communication bus. Therefore, the faulty board can be identified using FTP. For most boards, the files in the hwx folder may be missing. For some boards, the files in the fpga file may also be missing. Check whether the files are complete.
4. After files are copied to the destination folder, you need to check whether a logical board exists in the slot of the faulty board through the U2000. If yes, delete the board. Otherwise, the restoration will fail.
5. Remove and re-insert the board. After the board BIOS booting and software loading, the PROG indicator becomes steady green, indicating the board resumes normal operation. Run the :dmm-get-phybd:0 command to query the board status. The board is in SOFT state.

Scroll to top