ALM-4287373398 System Rollback
Description
NTITYTRAP/1/SYSTEMROLL:OID [oid] System rollback.(Reason="[OCTET]",Version ="[OCTET]",FileName="[OCTET]")
Rollback occurs on the system.
AttributeAfter the root directory is formatted
Alarm ID |
OID |
Alarm Severity |
Alarm Type |
---|---|---|---|
4287373398 |
1.3.6.1.4.1.2011.5.25.219.2.11.3 |
Critical |
Processing error alarm |
Parameters
Name |
Meaning |
---|---|
OID |
Indicates the MIB object ID of the alarm. |
Reason |
Indicates the error code. |
Version |
Indicates the version before the rollback. |
FileName |
Indicates the file name. |
Impact on the System
The system software supports only the service features of the current version after the startup succeeds.
The system does not support clear alarms. You need to manually clear this alarm.
Possible Causes
- If the specified startup software fails when you upgrade the system software or restart the device, the system will use the software that works last time. This alarm is generated when the startup succeeds, indicating that a version rollback occurs. If the startup fails, the system will use the specified backup software. This alarm is generated when the startup succeeds, indicating that a version rollback occurs.
- If a fault occurs in the flash memory, the system starts from the backup partition of the flash memory. You need to rectify the fault.
Procedure
- If the rollback reason is System software rollback, perform the following operations:
- Run the dir command to check the file system.
- If the storage medium is unavailable, the storage medium is corrupted. Go to step 2.
- If the software that fails to start the system is in the file system, check the file size. If the file size is not in the allowed range, the system software is invalid. Go to step 3.
- If the storage medium is available and the file size is within the allowed range, system software is faulty and cannot start the system. Go to step 4.
- Check the storage medium saved in the system software.
- If the storage medium is an SD card or a USB disk, replace it and restart the upgrade. If the upgrade fails, go to step 4.
- If the storage medium is flash, record the device type and number and collect alarm information and configuration information, and then contact technical support personnel.
- Delete the invalid file and upload a complete file. Perform the upgrade. If the upgrade fails, go to step 4.
- Collect operation results and collect alarm information and configuration information, and then contact technical support personnel.
- Run the dir command to check the file system.
- If the rollback reason is Backup flash space rollback, the system starts from the backup partition of the flash memory. You need to perform the following operations to rectify the fault:
- Run the display startup command in the user view to check information about the current startup system software and configuration file. If the command output shows that the storage path of the system software or configuration file is backup:/, it indicates that the device starts from the secondary flash partition.
- Run the format flash: command in the user view to format the root directory of the flash memory.
After this command is executed, all files and directories in the specified storage medium will be cleared and cannot be restored. Therefore, use this command with caution.
- After the root directory is formatted, run the cd flash: command to change the current working directory to flash. Then, upload the target system software and configuration file to the flash memory through SFTP.
- After the files are uploaded, run the startup system-software system-file [ slave-board | all ] [ verify | signature sign-filename ] command to specify the system software used for the next startup.
- Run the startup saved-configuration configuration-file [ slave-board | all ] command to specify the configuration file used for the next startup.
- After the configurations are complete, check whether the alarm is displayed again. If the alarm persists, contact technical support personnel.
- If the rollback reason is "System software rollback after upgrade, the possible cause is that new version can't register iMaster NCE-Campus": Collect alarm information and configuration information, and then contact technical support personnel.
This cause is supported in V300R022C00SPC100 and later versions.
Clearing
The alarm needs to be cleared manually.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot