As the system reboots, it loads the new operating system software image and its corresponding CLI
configuration file using the new boot stack entry configured earlier.
After the system reboots, establish a CLI session and enter the show version command to verify that the active
software version is correct.
Optional for PDSN: If you are using the IP Pool Sharing Protocol during your upgrade, refer to Configuring
IPSP Before the Software Upgrade in the PDSN Administration Guide.
Updating the Configuration File
Features in the new operating system may require changes to the configuration file. These changes can be
done manually or facilitated by custom scripts prepared by Cisco TAC. Make whatever changes are necessary
prior to saving the updated configuration file.
Verifying the Software Version
After the system has successfully booted, verify that the new StarOS version is running by executing the Exec
mode show version command.
You can run the Exec mode show build command to display additional information about the StarOS build
release.
Saving the Configuration File
Use the Exec mode save configuration command to save the currently running configuration to the /flash
device and to an off-chassis location (external memory device or network URL). The off-chassis copy assures
that you will have a fallback, loadable configuration file should a problem be encountered.
Completing the Update Process
Repeat the following tasks to complete the upgrade process on the standby secondary chassis:
•
Synchronizing File Systems, on page 366
•
Performing Health Checks, on page 365
•
Performing SRP Checks, on page 365
•
Performing BGP Checks, on page 366
ASR 5500 System Administration Guide, StarOS Release 21.4
367
Interchassis Session Recovery
Standby ICSR System
To Next Page
Loading...
Need help?
General
