Will the configuration of the standby switch of a stack of S series fixed switches be deleted when the master switch fails

1

After S series fixed switches set up a stack, the stack uses the configuration of the master switch, and the master switch synchronizes its configuration to the standby switch. If a fault occurs on the master switch and the master switch restarts, the standby switch becomes the new master switch. The stack uses the configuration file of the new master switch, but the configuration of the stack does not change.

Other related questions:
Identify the master and standby switches in a stack of S series switches
You can identify the master and standby switches in a stack of S series switches using either the CLI or indicator method. 1. CLI Run the display stack command to check the stack information, including the stack topology, roles of stack member switches, MAC address, and priority. 2. Indicators Press the MODE button on any member switch to change the mode status indicator to the stack mode. You can determine the stack IDs of the master switch and member switches through the status of service port indicators. Note: a. On an S5700EI, S5700SI, S5710-C-LI, S6700, or S5700HI switch, the stack mode status indicator shows the stack and speed modes. After you press the MODE button, the indicator is steady red and off after 45 seconds, indicating that the switch enters the stack mode. b. The S2720, S2750, S5700-LI, S5710-X-LI, S5710EI, S5720SI, S5720S-SI, and S6720EI switches have an independent stack mode indicator (STCK indicator). After you press the MODE button, the indicator is steady green or blinking, and then off in 45 seconds, indicating that the switch enters the stack mode. If the service port indicator is steady green, the member switch is a non-master switch. If the service port indicator blinks green, the member switch is the master switch. a. If the indicator of a port is steady on or blinking, the number of this port is the stack ID of the switch. b. If the first nine port indicators of a switch are steady on or blink, the stack ID of the switch is 0. To identify the standby switch, run the display stack command to check the stack ID of the standby switch and then check the status of the service port indicators.

Configure a switch as a slave switch in a stack of S series fixed switches
When more than two S series fixed switches set up a stack, one member switch is elected as the master switch, and one as the standby switch. The rest member switches function as slave switches, which are also called cold standby switches. A member switch function as a cold standby switch only when the stack elects other two member switches as the master and standby switches. You can configure using one of the following methods: 1. (Recommended) If you can control the switch startup, start the two switches to make them function as the master and standby switches and then start the switches that function as slave switches. 2. Configure a lower priority for a switch to reduce the possibility that the switch is elected as the master or standby switch. 3. If a stack has been set up, you can restart the master or standby switch. After the switch restarts, it rejoins the stack as a slave switch.

After a stack of S series fixed switches splits, the split stacks merge. Do I need to power off the master and standby switches
You do not need to power off the master and standby switches when stacks of S series fixed switches merge. You are advised to add a new switch to a stack during service idle time. Power off the new switch, configure the stack function on the switch, connect stack cables, and then power on the switch.

Advantages of stacks of S series fixed switches
Stacking technology provides high network reliability and forwarding performance while simplifying network management. It has the following advantages: 1. High reliability: Member switches in a stack work in redundancy mode. Link redundancy can also be implemented between member switches through inter-device link aggregation. 2. High scalability: You can increase ports, bandwidth, and processing capacity of a stack by simply adding member switches to the stack. Member switches can join or leave the stack without affecting other member switches. New switches automatically synchronize the configuration file and system software version with the master switch. 3. Simpler configuration and management: You can log in to a stack from any member switch to manage and configure all the member switches in the stack. In addition, complicated Layer 2 ring protection protocols or Layer 3 protection switching protocols are not required after switches set up a stack; therefore, the network configuration is much simpler.

Upgrade stacks of S series fixed switches
You can upgrade a stack of S series fixed switches using either of the following methods: Traditional upgrade: All member switches in the stack need to restart. This upgrade method causes service interruption in a relatively long time and can be used in scenarios insensitive to the service interruption time. Upgrade procedure 1. Upload system software to the master switch in the stack. 2. Run the startup system-software system-file all command to set the next startup software for all member switches in the stack. 3. Run the reboot command to upgrade the stack by restarting the entire system. Smooth upgrade: Member switches in a stack can be divided into an active area and a backup area that back up each other. Member switches in the two areas are upgraded in turn. During the upgrade of an area, traffic is transmitted through the other area, minimizing the impact of the upgrade on services. This upgrade method applies to scenarios sensitive to the service interruption time. The stack and networking must meet the following requirements: The uplinks and downlinks work in redundancy mode. The system software for next startup supports the smooth upgrade function. Member switches in the stack are running the same system software with the same software package name, version, and path. Member switches in the stack have the same system software for next startup with the same software package name, version, and path. Upgrade procedure 1. Upload system software to all the member switches in the stack. Ensure that member switches have the same system software with the same software package name, version, and path. 2. Run the system-view command to enter the system view. 3. Run the upgrade backup-area slot slot-id to slot-id command to define the active and backup areas for a smooth upgrade. The member switches with stack IDs in the specified range join the backup area, and the other member switches automatically join the active area. Note: Follow these rules to define the active and backup areas in a stack: The active and backup areas cannot contain the same member switch, and both areas must have at least one member switch. The backup area cannot contain the master switch. Member switches in each area must be directly connected. Member switches in the active and backup areas form the entire stack. 4. (Optional) Run the display upgrade area command to check whether the configured areas meet the requirements of the current stack topology. If the stack topology changes after the areas are configured, the smooth upgrade will fail. To avoid this problem, check the area configuration before starting a smooth upgrade. If the areas fail the check, redefine the active and backup areas correctly according to the current stack topology. 5. Run the upgrade start command to enable a smooth upgrade. 6. (Optional) Run the display upgrade state [ slot slot-id ] command to check the smooth upgrade status.

If you have more questions, you can seek help from following ways:
To iKnow To Live Chat
Scroll to top