Performing a Rolling Reload or Upgrade
Starting a Rolling Reload
Starting a Rolling Upgrade
252
CN4093 Application Guide for N/OS 8.4
You can perform a sequential reload or upgrade, otherwise known as a staggered
or rolling reload or upgrade, to avoid the need for an overall outage. With a rolling
reload or upgrade, some of the hardware stays up at all times.
This approach differs from the traditional image upgrade that requires manual
image downloads and install to individual switches, which then requires the entire
logical switch reboot.
After the firmware is copied to all members of the stack, the rolling reload or
upgrade process automatically reboots all switches sequentially in the following
order:
Backup switch
Master switch
Configured stack members, from lowest to highest csnum
Attached but not configured stack members, from lowest to highest asnum
During the rolling firmware reload or upgrade process, there will be continuous
connectivity to the upstream network. From the point of view of the stack, it is as
though a series of switch and uplink failures are occurring. When the design is
cabled and configured properly, the environment redirects traffic.
For detailed instructions on upgrading and rebooting, see Chapter 3, "Switch
Software Management".
To start a rolling reload, use the command:
CN 4093(config)# reload staggered [delay <delay>]
where delay is an integer from 2 to 20 representing the time delay in minutes
between switch reboots. The default value is one minute between switch reboots.
To start a rolling upgrade, use the command:
CN 4093(config)# copy {tftp|ftp|sftp} {image1|image2} {address <IP address>}
{filename <image filename>} staggered-upgrade [delay <2‐20 minutes>]
where:
tftp/ftp/sftp is the protocol for copying
image1/image2 is the image to which the firmware is being copied
address is the IP address from which the firmware is being copied
filename is the name of the firmware file that is being copied
delay is the delay between each reload, in minutes