Table of Contents
Advertisement
Note: Layer 2 services and protocols that are not listed (not supported by the
Note: See also "How a hitless OS upgrade and hitless switchover impacts system
Configuration considerations
Consider the following when using the Layer 2 hitless OS upgrade feature:
v For a description of the events that occur during a hitless OS upgrade, see
v For a description of how this feature impacts major system functions, see "How a
v You must have both active and standby management modules installed to use
v Hitless OS upgrade is supported in software release 05.0.00 or higher, with boot
v Hitless OS upgrade between different types of software images is not supported.
v Hitless OS upgrade should be performed locally, since remote connectivity will be
v The active management module switches from the initial active management
Table 26. Information regarding Layer 2 hitless OS upgrades (continued)
Rate shaping
Remote Fault Notification (RFN)
Root guard
Single instance LACP
Spanning tree
Static MAC and multi-port static MAC
Static trunks
Subnet VLANs
Super Aggregated VLANs (SAV)
System-max parameters
Topology groups
Traffic policies
UDLD
VLAN groups
VSRP
hitless feature) may encounter disruptions during reset of the management
and interface modules, but will resume normal operation once the modules
are back up and running.
functions" on page 82.
"What happens during a hitless OS upgrade and hitless switchover" on page 81.
hitless OS upgrade and hitless switchover impacts system functions" on page 82.
this feature.
image 05.0.00 or higher.
for example, hitless OS upgrade is supported when upgrading the Layer 2 image
to another Layer 2 image. It is not supported when upgrading the Layer 2 image
to a Layer 3 image, or the base Layer 3 image to a full Layer 3 image, and so
forth.
lost during the upgrade. During a reload, HTTP, SSH, Telnet, SNMP, and ping
sessions will be dropped.
module to the standby management module during the hitless upgrade process.
Therefore, a connection to the console interface on both management modules is
required.
Chapter 6. Using a redundant management module
85
Advertisement
Table of Contents
