10-15
Cisco ONS 15530 Configuration Guide and Command Reference
78-14227-01, Cisco IOS Release 12.1(10)EV2
Chapter10 Managing Your Cisco ONS 155 30 System
Updating System Images
The following upgrade procedures allow you to qualify a new image on one CPU switch m odu le w hile
optionally keeping an older trusted image on the redundant peer CPU switch module.
Caution If you are upgrading or downgrading with system images that differ by mor e than one major release,
the standby CPU switch module might not reach the hot-standby state. If a switchover occurs while
not in the hot-standby state, there is a risk of loss of the configuration. If the processor canno t reach
the hot-standby state, use the procedure described in the “Updating with Non-Hot-Standby
Compatible System Images” section on page10-17.
Updating with Hot-Standby Compatible System Images
The following procedure describes how to copy a new hot-standby compatible sy stem ima ge fro m t he
network to the bootflash device.
Step 1 Verify that the system is configured with the default auto-boot conf iguration, a utomatic synchroniza tion
enabled for both the running-config and startup-config files, and the standby processor in the hot-standby
software state.
Step 2 Copy the new system image to the standby CPU switch module bootflash using the CLI on the active
CPU switch module. Delete the old system image from the standby processor bootflash if there is not
room.
Note Make sure the active CPU switch module bo otflash only c ontains the old system image na me
and not the new system image name.
Step 3 Rearrange any existing boot system commands so the new system image appears as the first boot image
on the list. Optionally, you can configure the original system image as the second boot image.
Note Because the new system image is only present on the standby CPU switch module bootflash,
only the standby CPU switch module will load it. When the former ac tive CPU switch
module reloads, it will load the original system image after trying and failing to load the
missing new system image.
Step 4 Reload the original standby processor with the new system image and make sure it goes to the
hot-standby state. (At this point, we recommend that you copy the running-config file to the
startup-config file before continuing.)
Step 5 Initiate a switchover that causes the new system image reload on the new active CPU switch module.
After the switchover, verify that the new standby CPU switch module, which is running the original
system image, goes to the hot-standby state.
Step 6 Configure new features, and, if desired, qualify the new system image for an extended period of time on
the new active CPU switch module with the old system image running on the standby CPU switch
module.
Note If a switchover occurs back to a processor running an older system image, all configuration
commands supported by the older software version are retained. Any new configuration
features do not appear in the running configuration. New configuration features saved in the
startup configuration will remain.