Stack Membership - Cisco SGE2000 - - Gigabit Switch Administration Manual

Managing Device Information
Managing Stacking
Cisco Small Business SFE/SGE Managed Switches Administration Guide
configured through the web management system. By default, Unit IDs are
assigned automatically. However, you can use the browser to assign a
specific Unit ID; for example, the same unit ID as the unit which was recently
removed.

Stack Membership

The system supports up to eight switching units per stack. A stack is comprised of
three stacking member types:
•
Stacking Master — Provides a single control, configuration and management
point for stacking members through a single IP address interface. The Stacking
Master maintains the stack management, device configuration. In addition, the
Stacking Master detects and reconfigures the ports with minimal operational
impact in the event of unit failure, inter-unit link failure, and unit insertion or
removal. A stack must contain a single Stacking Master.
Each port in the stack has a specific Unit ID, port type, and port number, which
is part of both the configuration commands and the configuration files.
Configuration files are managed only from the Master unit. This includes:
•
Saving to the FLASH
•
Uploading Configuration files to an external TFTP Server
•
Downloading Configuration files from an external TFTP Server
•
The Backup Master is a stacking member that receives a copy of the Stacking
Master Configuration file. A stack can contain a single Backup unit or none at all.
The Backup unit replaces the Master unit if one of the following events occur:
•
The Master unit fails or is removed from the stack.
•
Links from the Master unit to the stacking units fail.
•
A soft switchover is performed via the web interface.
Switching between the Stacking Master and the Backup Master results in a
limited service loss. The Stacking Master and the Backup Master maintain a
Warm Standby, meaning that the Stacking Master and the Backup units are
synchronized with the static configuration only. Any Dynamic Address Tables
are relearned if a failure occurs. The Running Configuration file is synchronized
between the Stacking Master and the Backup, and continues running on the
Backup Master.
2
14