Administration: Stack Management
Software Auto Synchronization in Stack
Cisco 500 Series Stackable Managed Switch Administration Guide Release 1.3 70
5
Reconnecting the Original Master Unit After Failover
After failover, if the original master is connected again, the master selection
process is performed. If the original master (unit 1) is reselected to be the master,
the current master (unit 2, which was the original backup unit) is rebooted and
becomes the backup once again.
NOTE During master/backup failover, the up time of the backup unit is retained.
Software Auto Synchronization in Stack
All the units in the stack must run the same software version (firmware and
bootcode). Each unit in a stack automatically downloads firmware and bootcode
from the master unit if the firmware and/or boot code that the unit and the master
are running is different. The unit automatically reboots itself to run the new version.
Stack Unit Mode
A device has a Stack Unit mode that indicates whether the device is or will be part
of a stack or whether it is operating on its own.
Devices can operate in one of the following Stack Unit modes:
• Standalone—A device in Standalone Stack Unit mode is not connected to
any other device and does not have a stack port.
• Native Stacking—A device in Native Stacking mode can be connected to
other devices of the same type through its stack ports to form a stack. All
units in a native stack must be of the same type (either all Sx500s or all
SG500Xs).
• Basic Hybrid—A device in Basic Hybrid mode can be connected to other
devices of all types to form a stack. The only limitation (and the reason that
this mode is called Basic Hybrid as opposed to Advanced Hybrid) is that
there is no support for VRRP or RIP. The GUI displays the pages of Sx500,
even if the stack master is SG500X, since the feature set is that of the
Sx500.
In this mode, any type of device can take the master/backup roles. Only the
5G stacking ports can be used as stack ports.
To Next Page
Loading...
Need help?
General
