Exchanging Stacking Members; Switching Between The Stacking Master And The Secondary Master - Alcatel OS-LS-6224 User Manual

3
Managing Stacking
Stacking Master must synchronize the Stacking Secondary Master. The Dynamic
configuration is not saved, for example, dynamically learned MAC addresses are not
saved.
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 device Stacking Master, including:
• Saving to the FLASH
• Uploading Configuration files to an external TFTP Server
• Downloading Configuration files from an external TFTP Server
Whenever a reboot occurs, topology discovery is performed, and the master learns
all units in the stack. Unit IDs are saved in the unit and are learned through topology
discovery. If a unit attempts to boot without a selected Master, and the unit is not
operating in stand-alone mode, the unit does not boot.
Configuration files are changed only through explicit user configuration.
Configuration files are not automatically modified when:
• Units are Added
• Units are Removed
• Units are reassigned Unit IDs
• Units toggle between Stacking Mode and Stand-alone Mode
Each time the system reboots, the Startup Configuration file in the Master unit is
used to configure the stack. If a stack member is removed from the stack, and then
replaced with a unit with the same Unit ID, the stack member is configured with the
original device configuration. Only ports which are physically present are displayed
in the home page, and can be configured through the WebViewMgmt system.
Non-present ports are configured through the CLI or SNMP interfaces.

Exchanging Stacking Members

If a stack member with the same Unit ID replaces an existing Unit ID with the same
Unit ID, the previous device configuration is applied to the inserted stack member. If
the new inserted device has either more than or less ports than the previous device,
the relevant port configuration is applied to the new stack member.

Switching between the Stacking Master and the Secondary Master

The Secondary Master replaces the Stacking Master if the following events occur:
• The Stacking Master fails or is removed from the stack.
• Links from the Stacking Master to the stacking members fails.
• A soft switchover is performed with either via web interface or the CLI.
Switching between the Stacking Master and the Secondary Master results in a
limited service loss. Any dynamic tables are relearned if a failure occurs. The
running configuration file is synchronized between Stacking Master and the
Secondary Master, and continues running on the Secondary Master.
39