Version information: The NE80E is upgraded from V300R003C02B608 to NE40E&80E V300R006C01B297.
Fault symptom: After the NE80E is upgraded, the slave MPU cannot be registered, but all the LPUs are normally registered. Run the display startup command before the NE80E is restarted. The output shows that there is no abnormality and the software version for the next startup for both the master MPU and the slave MPU is NE40E&80E V300R006C01B297. Log in to the slave MPU through the serial interface. It is found that the slave MPU restarts repeatedly. V300R006 can be rolled back to an earlier version. When it is rolled back to V300R003, however, the software version of the slave MPU is inconsistent with that of the master MPU. The slave MPU still cannot be registered.
As information displayed on the console interface does not show "cfcard2:/ - Volume is OK", CF card 2 is probably faulty. Pull out the slave MPU, remove CF card 2, and then plug the slave MPU in the chassis. After a period of time, the slave MPU is successfully registered. It can be concluded that CF card 2 is faulty. Use a card reader to read data from CF card 2. It is found that more than 2000 log files (more than 1 M) are saved in the card. Format the CF card after backing up all the log files. Pull out the slave MPU, insert the CF card, and then install the slave MPU. After a period of time, the slave MPU is successfully registered.
A large number of files may be written to the NE80E, and thus a lot of fragments are generated, which causes timeout when the system reads data from CF card 2. As a result, the NE80E cannot be successfully started.
1. Deleting all the files saved in CF card 2 cannot solve the problem. The problem can be solved only after the CF card is formatted.
2. Before the version upgrade, you need to check CF card 2 on the slave MPU. If the CF card contains an extremely large number of log files, you should back up the files, format the CF card, and then restart the NE80E.