After the OSN2500 (22.214.171.124P01) is powered on, the power fails within one minute. Then, the OSN2500 is powered on again. The main control unit is frequently reset.
Log in to the OSN2500 through the navigator and find a prompt, indicating NEBIOS is running.Download NESOFT please!
30 minutes later, the main control unit is normal. After stabilizing for 3 to 5 minutes, the main control unit is reset again. The main control unit is reset cyclically.
A large number of NE software reset records are found through information collection. For details, see the attachment.
During the reset, the STAT indicator goes off, and the PROG indicator flashes.
Log in to the OSN2500 through the navigator and find a prompt, indicating NEBIOS is running. Download NESOFT please!
Remove the two main control units from the OSN2500. Set DIP switch 4 on a main control unit to ON. Then, mount the main control unit in the OSN2500. In this case, the NE software is not reset any more.
Log in to the OSN2500 through the device COM port by running the telnet command. Run rename "ofs1/hwx/ne1500.hwx","ofs1/hwx/ne1500m.hwx" to change the name of the 1500.hwx file.
Remove the main control unit. Set DIP switch 4 to OFF. Then, mount the main control unit in the OSN2500.
If information collection is required for analysis, enter ftp://192.168.0.82 in the Internet Explorer to log in to the OSN2500 and collect files in the following paths: mfs/vfs, mfs/ocp, ofs1/vfs, ofs1/ocp, ofs1/log.ofs2/vfs, ofs2/ocp, and ofs2/log. The collected information must be submitted to the R&D department. Delete all the files in the msfx folder. Then, delete all the files except hwx and fpga in the ofs1 and ofs2 folders.
Log in to the OSN2500 through telnet. Run the preceding command to change the name of the ne1500m.hwx file to ne1500.hwx. Remove and then mount the main control unit. The main control unit can work properly. Troubleshoot the other main control unit in the same way.
When the NE clears the library and resets, the NE re-establishes the database system. If power failure occurs when the database system is not completely established, the database may be damaged. The NE software provides the repair function. If the repair function is not successful, the NE software is frequently reset.
Follow the preceding steps. That is, change the name of the ne1500.hwx file, collect the information, delete files, change the name of the ne1500.hwx file again, and then mount the board.