beautypg.com

Recovering from stack failure or topology change, Resilient ip interface for management access, 6 recovering from stack failure or topology change – SMC Networks SMC TigerStack IV SMC6224M User Manual

Page 44

background image

I

NITIAL

C

ONFIGURATION

2-6

Recovering from Stack Failure or Topology Change

Note the following points about recovering from a stack change:

When using a “line” topology, if any link or unit in the stack fails, the
stack will be split into two separate segments. The new stack segments
will then reboot and resume normal operation if a new segment
contains the original Master unit, or if a new segment now contains
only one switch. In other words, a new segment will resume normal
operation unless it contains more than one switch and the Master
button is not depressed on any of these switches. If the later case is
true, and a segment fails to resume operation, you can either replace
the failed connection to restore operation to the original stack, or
depress the Master button on one of the switches in this segment..

If you are using a wrap-around stack topology, a single point of failure
in the stack will not cause the stack to fail. It would take two or more
points of failure to break the stack apart. The stack will merely reboot
to detect the new stack’s topology, and then resume normal operation.

When a link or unit in the stack fails, a trap message is sent and a failure
event is logged. The stack will be rebooted after any system failure or
topology change. It takes two to three minutes for the stack to reboot.
Also note that powering down a unit or inserting a new unit in the stack
will cause the stack to reboot.

Resilient IP Interface for Management Access

The stack functions as one integral system for management and
configuration purposes. You can therefore manage the stack through any
unit in the stack. The Master unit does not even have to include an active
port member in the VLAN interface used for management access.
However, if the unit to which you normally connect for management
access fails, and there are no active port members on the other units within
this VLAN interface, then this IP address will no longer be available. To
retain a constant IP address for management access across fail over events,
you should include port members on several units within the primary
VLAN used for stack management.

This manual is related to the following products: