Foundry FastIron SuperX, Руководство по установке оборудования

Страница: 107 / 198

Using a Redundant Management Module
December 2008 © 2008 Foundry Networks, Inc. 6 - 7
5. The standby management module takes over the active role.
6. The old active management module resets and reloads with the same software image running on the current
active management module.
7. The FastIron switch is now operating on the new software image. The management module that was initially
configured as the standby management module is now the active management module and the management
module that was initially configured as the active management module is now the standby.
NOTE: The events described above occur internally and do not create or affect the external network topology.
How a Hitless OS Upgrade and Hitless Switchover Impacts System Functions
The following table highlights the implications of a hitless OS upgrade or hitless switchover to the system’s major
functions.
NOTE: All traffic going through Ethernet interfaces (if present) on the management modules will be interrupted
during a hitless OS upgrade. This is because both management modules must be reloaded with the new image.
This applies to hitless OS upgrade only. It does not apply to hitless switchover, which does not interrupt traffic
going through Ethernet interfaces on the management modules.
Syslog Message for Hitless OS Upgrade and Hitless Switchover
The following Syslog message is generated as a result of a switchover during a hitless OS upgrade or hitless
switchover:
HITLESS-RELOAD COMPLETED – Mgmt Module in slot <slotnum> is now Active
Traffic Type Impact
Layer 2 switched traffic,
including unicast and multicast Layer 2 switched traffic is not impacted during a manual switchover. All
existing switched traffic flows continue uninterrupted. New switched flows
are not learned by the FastIron switch during the switchover process and
are flooded to the VLAN members in hardware. After the new active
management module becomes operational, new switched flows are
learned and forwarded accordingly. The Layer 2 control protocol states
are not interrupted during the switchover process.
Layer 3 routed traffic, including
unicast and multicast Layer 3 routed traffic is briefly interrupted during the manual switchover
process. The traffic will converge to normalcy after the new active CPU
becomes operational.
Management traffic All existing management sessions (SNMP, TELNET, HTTP, HTTPS, FTP,
TFTP, SSH etc.), are briefly interrupted during the switchover process. All
such sessions are terminated and can be re-established after the new
active CPU takes over.
Security features All security features other than configured ACLs are not hitless.
Configured ACLs will continue to operate in a hitless manner, meaning
the system will continue to permit and deny traffic during the switchover
process.
All other security features are briefly interrupted during the switchover
process and will return to normalcy after the new active management
module is operational.