Table of Contents
Advertisement
v Upon being reset, traffic going through the ports (if present) on the management
v The Layer 3 router configuration is not allowed to be changed any time during
v System-max configuration changes require a system reload. System-max
v Other commands requiring a software reload also do not take effect upon hitless
v This feature can be used to upgrade an image to a higher or lower compatible
v The Layer 2/Layer 3 hitless failover feature is not supported in this release.
v The Layer 3 hitless upgrade feature is not supported in this release.
Configuration steps
The following is a summary of the configuration steps for a Layer 2 hitless OS
software upgrade:
1. The software image that supports Layer 2 hitless software upgrade is copied
2. The software image is installed in flash memory on the active and standby
3. The hitless-reload command is entered on the active management module.
Loading the software onto the switch
Hitless OS upgrade loads from the primary and secondary images on the
management modules. To perform the hitless upgrade, you must first copy the
software image that supports Layer 2 hitless software upgrade onto the flash
memory of the active and standby management modules.
for instructions for copying these files, see the release notes or the Configuration
Guide.
Executing the hitless-reload command
After loading the software image onto the flash memory of the active and standby
management modules, you can begin the process of performing a hitless OS
upgrade using the hitless-reload command. for example:
#hitless-reload primary
Syntax: hitless-reload primary | secondary
The primary parameter specifies that the management module will be reloaded
with the primary image.
86
Ethernet Switch s-series Installation and User Guide
module will be interrupted. Once the management module is up and running, it
will be able to send and receive packets, even before the hitless upgrade
process is complete.
the hitless upgrade process.
configuration changes do not take effect by the hitless upgrade. Even if a
system-max parameter is changed and saved in the startup configuration, the
switch will revert to the default system-max value upon a hitless software
upgrade. The new system-max value will only take effect after a regular system
reload.
upgrade and require a system reload before being placed in effect.
version of the software, even if the software image does not support hitless
upgrade. However, if hitless upgrade is not supported, the upgrade process will
not be hitless, and the entire system will reload upon upgrading to the software
image.
from a TFTP server to the switch. See "Loading the software onto the switch."
management modules.
The command triggers the events described in the section "What happens
during a hitless OS upgrade and hitless switchover" on page 81.
Advertisement
Table of Contents
