Specifying the system software to be used at the next startup ensures that the device runs the new system software after being restarted.
Before specifying system software to be used at the next startup, make sure that there is no running patch in the system. Otherwise, the system software cannot be upgraded.
Before the version upgrade, you can run the upgrade rollback enable rollback-timer time-value command in the user view to enable the version rollback function and set a timeout period for version rollback during version upgrade. After the timeout period is set, the system will perform version rollback if no users log in to the device during the set timeout period.
The display upgrade rollback command displays whether the version rollback function is enabled on a device.
Before the startup, run the check system-software command to verify the digital signature and check whether the target software is secure and available. The execution of this command lasts for about 3 to 10 minutes.
The patches in the running state are checked.
All running patches are deleted.
If there are running patches in the system, perform this step. Otherwise, go to the next step.
The system software to be used on the main control board at the next startup is specified.
system-file indicates the file name of the system software, which is in the format of *.cc.
The system software to be used on the SMB at the next startup is specified.
system-file indicates the file name of the system software, which is in the format of *.cc.
During the next restart, ensure that the master and slave OMUs use the same system software. Otherwise, the reboot operation fails to be performed.
In VS mode, this command is supported only by the admin VS.
Before you specify a next startup configuration file for the system without configurations, you must run the save command to save the current configurations.
When you need to specify a configuration file with new hardware information as the next startup configuration file, you must install the new hardware and activate it, and then run the save command to save the hardware configurations.
The current version does not allow you to transfer the hardware configuration file (device.sys) of one device to another device and then immediately restart that device. If you do so, the hardware on that device cannot be registered.
If you want a PAF file to be loaded and run after the system restarts, you can run the startup paf { default | file-name } command to specify the PAF file to be used at the next startup.