FastIron Hardware Installation Guide for the FSX, FSX 800, and FSX 1600
6 - 10
© 2008 Foundry Networks, Inc.
December 2008
NOTE:
Layer 2 services and protocols that are not listed (not supported by the 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.
NOTE:
See also “How a Hitless OS Upgrade and Hitless Switchover Impacts System Functions” on page 6-7.
Configuration Considerations
Consider the following when using the Layer 2 hitless OS upgrade feature:
•
For a description of the events that occur during a hitless OS upgrade, see “What Happens During a Hitless
OS Upgrade and Hitless Switchover” on page 6-6.
•
For a description of how this feature impacts major system functions, see “How a Hitless OS Upgrade and
Hitless Switchover Impacts System Functions” on page 6-7.
•
You must have both active and standby management modules installed to use this feature.
•
Hitless OS upgrade is supported in software release FSX 05.0.00 or higher, with boot image FSX 05.0.00 or
higher.
•
Hitless OS upgrade between different types of software images is not supported. 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, etc..
•
Hitless OS upgrade should be performed locally, since remote connectivity will be lost during the upgrade.
During a reload, HTTP, SSH, Telnet, SNMP, and ping sessions will be dropped.
•
The active management module switches from the initial active management module to the standby
management module during the hitless upgrade process. Therefore, a connection to the console interface on
both management modules is required.
•
Upon being reset, traffic going through the ports (if present) on the management 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 Layer 3 router configuration is not allowed to be changed any time during the hitless upgrade process.
•
System-max configuration changes require a system reload. System-max 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 FastIron 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.
•
Other commands requiring a software reload also do not take effect upon hitless upgrade and require a
system reload before being placed in effect.
•
This feature can be used to upgrade an image to a higher or lower compatible 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.
•
The Layer 2/Layer 3 hitless failover feature is not supported in this release.
•
Topology groups
•
Traffic policies
•
UDLD
•
VLAN groups
•
VSRP
Содержание FastIron SuperX
Страница 139: ...Maintaining the Hardware December 2008 2008 Foundry Networks Inc 7 25 AC1 AC2 AC3 AC4 Cord Retainer Cord Retainer...
Страница 148: ...FastIron Hardware Installation Guide for the FSX FSX 800 and FSX 1600 7 34 2008 Foundry Networks Inc December 2008...
Страница 168: ...FastIron Hardware Installation Guide for the FSX FSX 800 and FSX 1600 8 20 2008 Foundry Networks Inc December 2008...
Страница 198: ...FastIron Hardware Installation Guide for the FSX FSX 800 and FSX 1600 C 16 2008 Foundry Networks Inc December 2008...