D-Link xStack DES-3228PA, Web/Installation Manual, Page: 71 / 274

Managing Stacking
Exchanging Stacking Members
Page 68
•
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 Mas-
ter, 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 D-
Link Web Management Interface home page, and can be configured through the web management 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. For example:
Switching the Stacking 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.