Configuring a Stack Member ID
Context
Stack member IDs are used to identify and manage member switches in a stack. Each member switch has a unique stack member ID.
If stack member IDs conflict in a stack, the master switch assigns new stack member IDs to member switches. That is, the master switch checks stack member IDs in ascending order (from 1 to the largest stack member ID) to find an unused stack member ID and then assigns the found stack member ID to the member switch with a conflicting stack member ID.
Procedure
- Run the system-view command to enter the system view.
- Run the stack command to enter the stack management view.
- Run the stack member new-member-id command to configure a stack member ID for the local switch.
By default, the stack member ID of a switch is 1. After changing the stack member ID, restart the switch for the configuration to take effect.
When a switch already has the stacking function enabled, run the stack member member-id renumber new-member-id [ inherit-config ] command to change the stack member ID of the switch.
If you specify inherit-config, the switch inherits the original stack configuration after it restarts, including the stack priority, stack domain ID, connection mode, and physical member port configuration.
If you do not specify inherit-config, the current stack configuration is lost after the switch restarts, and the configuration related to the new stack member ID in the configuration file takes effect.
For example, if a switch uses a stack member ID 1 and has the following stack priority configuration:# stack member 1 priority 150 #
If inherit-config is specified when the stack member ID is changed to 2, member ID 2 will inherit the stack priority configuration of member ID 1 after the switch restarts. For example:# stack member 1 priority 150 // Configuration of member ID 1 becomes the offline configuration. # stack member 2 priority 150 // Member ID 2 inherits the stack priority configuration of member ID 1. #
If inherit-config is not specified, member ID 2 will not inherit the stack priority configuration of member ID 1 after the switch restarts. For example:# stack member 1 priority 150 // Configuration of member ID 1 becomes the offline configuration, and configuration of member ID 2 is empty. #
If the switch already has offline configuration of member ID 2 before restarting, for example:# stack member 1 priority 150 # stack member 2 priority 200 // The switch already has offline configuration of member ID 2 before restarting #
When the stack member ID is changed to 2, inherit-config cannot be specified. The switch will use the configuration of member ID 2 in the configuration file after restarting. For example,# stack member 1 priority 150 // Configuration of member ID 1 becomes the offline configuration # stack member 2 priority 200 // Configuration of member ID 2 in the configuration file takes effect. #
-
If the configuration file contains offline configuration for the new stack member ID, do not specify inherit-config in the command.
-
Common service port configurations, for example, port split configuration, will be lost after the stacking function has been enabled, the stack member ID is changed, and the switch restarts.
-
- Run the commit command to commit the configuration.