Typical Stack Configuration of Fixed Switches

S300, S500, S2700, S3700, S5700, S6700, S7700, and S9700 Series Switches Typical Configuration Examples

This document provides campus networks typical configuration examples and feature typical configuration examples. "Campus Networks Typical Configuration Examples" provides typical campus network networking modes and a variety of deployment examples."Feature Typical Configuration Examples" provides typical configuration examples of a single feature on a switch. You can configure required features after deploying a campus network.

Rate and give feedback:

Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).

Typical Stack Configuration of Fixed Switches

Overview of Stack
Stack Deployment Method and Recommendations
Example for Setting Up a Stack Using Stack Cards (V200R001 and Later Versions)
Example for Setting Up a Stack Using Service Ports (V100R006C05)
Example for Setting Up a Stack Using Service Ports (V200R001 to V200R002)
Example for Setting Up a Stack Using Service Ports(V200R003 and Later Versions)
Example for Establishing a Stack Through Service Port Connections Using Dedicated Stack Cables (V200R011C10 and Later Versions)
Stacked Switch Replacement Guide
Changing the Stack ID

Overview of Stack

Fixed switches are often deployed at the aggregation layer and access layer. Unlike modular switches, fixed switches have a fixed number of ports and cannot add LPUs to expand the number of ports. When the network expands continuously, the number of ports provided by a single fixed switch may be insufficient to meet network requirements. Stack technology uses physical member ports and stack cables to combine multiple stacking-capable switches into one logical switch. You can set up a stack to improve network scalability and device reliability.

Stack Deployment Method and Recommendations

Recommended Stack Deployment Scenarios

Scenario 1: The Stack System Operates on Aggregation Switches

This is the most common scenario when aggregation switches set up a stack system, as shown in Figure 3-24.

The following switch models can set up a stack system in this scenario: S6700-EI, S6720S-EI, S6720-EI, S6720-HI, S6730-H, S6730S-H, S5700-HI, S5710-HI, S5710-EI, S5700-EI, S5700-SI, S5720-EI, S5720-HI, S5730-HI, S5731-H, S5731S-H, S5732-H.

In this scenario, each switch in a stack connects to a core device through Eth-Trunk. The stack system simplifies management of aggregation devices and improves uplink reliability of aggregation devices.

Figure 3-24 Stack system operating on aggregation switches

Scenario 2: The Stack System Operates on Access Switches

This is the most common scenario when Layer 2 access switches set up a stack system, as shown in Figure 3-25.

The following switch models can set up a stack system in this scenario: S2720-EI, S2750-EI, S5700-LI, S5700-EI, S5710-C-LI, S5710-X-LI, S5720-LI, S5735-L, S5735S-L, S5735S-L-M, S5720S-LI, S5700-SI, S5720-SI, S5735-S, S5735S-S, S5720S-SI, S5720I-SI, S5700S-LI, S5730-SI, S5730S-EI, S5731-S, S5731S-S, S6720-LI, S6720S-LI, S6720-SI, S6720S-SI, S6730-S, S6730S-S.

In this scenario, each switch in a stack connects to an aggregation device through Eth-Trunk. The stack system simplifies management and improves uplink reliability of access devices.

Figure 3-25 Stack system operating on access switches

Scenario 3: The Stack System Operates on an Access Ring

This scenario rarely occurs. Figure 3-26 shows the networking of this scenario.

In this scenario, multiple stack systems form a ring through Eth-Trunk, and one stack system connects to aggregation switches through Eth-Trunk. This scenario reduces the number of management IP addresses of access devices.

Figure 3-26 Stack system operating on an access ring

Recommendations

The following recommendations are provided based on the positioning of fixed switch models. If customers have special requirements, it is recommended to deploy high-end devices at a lower network layer; it is not recommended to deploy low-end devices at a higher network layer. For example, it is recommended to deploy aggregation switches at the access layer rather than to deploy access switches at the aggregation layer.

To ensure stack reliability and bandwidth, you are advised to do as follows:

Ensure that each member device connects to the core device through an uplink port. This connection prevents upstream traffic forwarding from being affected when any member device fails.
When using multiple devices to set up a stack, ensure the same stack bandwidth between any two devices. Otherwise, the bandwidth of the stack system is the minimum stack bandwidth.

Table 3-9 Scenario recommendations

Model	Scenario 1	Scenario 2	Scenario 3
S5700-HI, S5710-HI, S5710-EI, S6700-EI	First preferred	Second preferred	Not recommended
S5720-EI, S5720-HI, S5730-HI, S5731-H, S5731S-H, S5732-H, S6720-EI, S6720S-EI, S6720-HI, S6730-H, S6730S-H	First preferred	Second preferred	Second preferred
S5700-EI, S5700-SI	First preferred	First preferred	Second preferred
S5720-SI, S5735-S, S5735S-S S5720S-SI, S5720I-SI, S5731-S, S5731S-S, S6730-S, S6730S-S	Second preferred	First preferred	First preferred
S2720-EI, S2750-EI, S5700-LI, S5720-LI, S5735-L, S5735S-L, S5735S-L-M, S5720S-LI, S5730-SI, S5730S-EI, S6720-LI, S6720S-LI, S6720-SI, S6720S-SI	Not recommended	First preferred	Second preferred
S5700S-LI, S5710-C-LI, S5710-X-LI	Not recommended	First preferred	First preferred

Determining the Stack Topology

Networking for a Stack of More Than Two Member Devices

A stack can be connected in a chain or ring topology depending on the stack connection mode, as shown in Figure 3-27. Table 3-10 compares the two stack topologies in terms of reliability, link bandwidth utilization, and convenience of cable connections.

Figure 3-27 Stack topologies

Table 3-10 Comparison between stack topologies

Stack Topology	Advantages	Disadvantages	Applicable Scenario
Chain topology	Applicable to long-distance stacking because the first and last member switches do not need to be connected by a physical link.	Low reliability: If any stack link fails, the stack splits. Low stack link utilization: The entire stack relies on a single path.	Member devices are far from one another and a ring topology is difficult to deploy.
Ring topology	High reliability: If a stack link fails, the topology changes from ring to chain, and the stack can still function normally. High link bandwidth efficiency: Data can be forwarded along the shortest path.	The first and last member switches need to be connected by a physical link, so this topology is not applicable to long-distance stacking.	Member switches are located near one another.

Networking for a Stack of Two Member Devices

Two devices can set up a stack in a chain topology, as shown in Figure 3-28. In this topology, only one logical stack port exists between the two devices and no loop exists in the stack.
Figure 3-28 Only one logical stack port between two member devices
Two devices can set up a stack with back-to-back networking, as shown in Figure 3-29. In this networking, two logical stack ports exist between the two devices, and one loop exists in the stack, which will be automatically eliminated by the system.
Figure 3-29 Two logical stack ports between two member devices

When using two devices to set up a stack, you are advised to do as follows:

If the devices provide no more than 28 ports, use the networking with only one logical stack port. Otherwise, use the back-to-back networking.
If more member devices need to be added to the stack in the future, use the back-to-back networking, which will require minimum modification to the existing system.
Connect at least two stack cables between the two devices to ensure reliability.

Stack Configuration and Deployment Recommendations

Feature Limitations

Version restrictions:

When multiple switches set up a stack, member switches will synchronize the running version of the master switch. If a member switch does not support this running version, it will restart repeatedly.
In V200R009C00, if MPLS-incapable S5720-EIs exist in a stack, this stack cannot have MPLS enabled. If member devices in a stack are running MPLS services, adding MPLS-incapable S5720-EIs to the stack is not allowed.
An S5720-HI supports the stacking function since V200R009C00. When a member device in a stack is faulty and fails to restart for three consecutive times, the device attempts to roll back to a version earlier than V200R009C00 for restart. When the device restarts successfully after rolling back to a version earlier than V200R009C00, a multi-active situation may occur because the version earlier than V200R009C00 does not support the stacking function. To prevent this situation, you are advised to delete the system software earlier than V200R009C00 from member devices when using S5720-HIs to set up a stack.
When two stack member devices use ports on S7Q02001 and ES5D21Q02Q00 cards, respectively, to set up a stack, ensure that the device versions are the same. Otherwise, the stack ports cannot go Up.

MAD specifications:

You can configure a maximum of eight direct detection links for each member switch in a stack.
You can configure the relay mode on a maximum of four Eth-Trunks in a stack.
In V200R008C00 and earlier versions, you can configure a maximum of 64 Eth-Trunks on a relay agent to provide the relay function for multiple stacks. This restriction does not apply to versions later than V200R008C00.

After multiple switches form a stack, the following features cannot be configured in the stack:

Y.1731 one- and two-way frame delay measurement
N:1 VLAN Mapping
IPv6 over IPv4 tunnel
IPv4 over IPv6 tunnel
E-Trunk

When you establish a stack on the switches that support both stack card connection and service port connection, such as S5720-C-EI, note the following:

All member switches must use the same stack connection mode.
When a member switch has stack cards installed and the service port stack configuration, the switch uses the service port connection mode to establish a stack. It does not use the stack card connection mode even though a stack fails to be established in service port connection mode and stack cards are connected correctly.
A switch uses the stack card connection mode to establish a stack only when it has no service port stack configuration.
If a switch is currently using the stack card connection mode, perform the service port stack configuration on the switch before changing the stack connection mode to service port connection. After the service port stack configuration is complete, the switch uses the service port connection mode when restarting.
If a switch using the stack card connection mode has service port configuration, a smooth upgrade cannot be performed on the switch.
If a switch is currently using the service port connection mode, correctly connect stack cards and stack cables and clear the existing service port stack configuration before changing the stack connection mode to stack card connection. You can use the reset stack-port configuration command to clear the existing service port stack configuration.
When changing service port connection to stack card connection, you are advised to remove the cables connected to service ports to prevent loops.

Deployment Recommendations

Connect a stack to other network devices using an Eth-Trunk and add one port of each member switch to the Eth-Trunk.
When a stack connects to access devices, configure ports directly connected to terminals as STP edge ports to prevent STP re-calculation when the ports alternate between Up and Down states. This configuration ensures normal traffic forwarding.
If storm control needs to be configured on many ports, replace storm control with traffic suppression to save CPU resources.
If port security needs to be configured on many ports, replace port security with MAC address learning limiting to save CPU resources.
Loops may occur on a network to which a stack connects. Run the mac-address flapping action error-down command to set an interface to the error-down state when MAC address flapping is detected on the interface. This improves system processing performance and allows the peer device to detect that the interface becomes Down. Additionally, if the peer device has redundant links, traffic can be rapidly switched to a normal link.

Example for Setting Up a Stack Using Stack Cards (V200R001 and Later Versions)

Networking Requirements

A new enterprise network needs to provide sufficient ports for access devices, and the network structure should be simple to facilitate configuration and management.

As shown in Figure 3-30, SwitchA, SwitchB, and SwitchC need to set up a stack in a ring topology and connect to SwitchD through an inter-device Eth-Trunk. SwitchA, SwitchB, and SwitchC are the master, standby, and slave switches respectively, with stack IDs of 0, 1, and 2 and stack priorities of 200, 100, and 100. As the three switches function as one logical device on the network, the number of ports is increased and network management and maintenance are simplified.

In this example, S5700-EIs set up a stack.

Figure 3-30 Stack networking

Configuration Roadmap

Power off SwitchA, SwitchB, and SwitchC, install an ES5D00ETPC00 stack card on each switch, and then power on the three switches.
- The ES5D00ETPC00 stack card does not support hot swap. You need to power off a switch before installing the stack card on the switch.
- You can perform software configurations only after installing a stack card on the switch.
Enable the stacking function.
Configure stack IDs and stack priorities for member switches to facilitate device management and identification.
Power off SwitchA, SwitchB, and SwitchC, connect physical member ports using PCIe cables, and then power on the three switches.
Configure an inter-device Eth-Trunk to increase reliability and uplink bandwidth.
Configure multi-active detection (MAD) in relay mode to ensure network availability when the stack splits. The stack split detection mechanism is called dual-active detection (DAD) in V200R002 and earlier versions and MAD in later versions.

Procedure

Turn off power supplies of SwitchA, SwitchB, and SwitchC, install an ES5D00ETPC00 stack card on each switch, and then power on the three switches.
Enable the stacking function. This function is enabled by default.

Configure stack IDs and stack priorities. The default stack ID is 0, and the default stack priority is 100.

[SwitchA] stack slot 0 priority 200     //Set the stack priority of the master switch to 200, which is larger than those of other member switches, and use the default stack ID 0.

[SwitchB] stack slot 0 renumber 1       //Use the default stack priority 100 and set the stack ID to 1.

[SwitchC] stack slot 0 renumber 2       //Use the default stack priority 100 and set the stack ID to 2.

Turn off power supplies of SwitchA, SwitchB, and SwitchC, connect physical member ports using PCIe cables as shown in Figure 3-31, and then power on the three switches.
- Run the save command to save the configurations before you power off the switches.
- STACK 1 port of one switch must be connected to STACK 2 port of another switch. Otherwise, the stack cannot be set up.
- To ensure that a stack can be set up successfully, you are advised to perform operations in the following sequence. First, power on the switch that you want to specify as the master switch. In this example, SwitchA becomes the master switch after you complete the following operations.
  1. Power off SwitchA, SwitchB, and SwitchC.
  2. Connect SwitchA and SwitchB with a stack cable.
  3. Power on and start SwitchA and then power on SwitchB.
  4. Check whether SwitchA and SwitchB set up a stack successfully. For details, see step 5.
  5. Connect SwitchC to SwitchB and SwitchA using stack cables and then power on SwitchC.
  6. Check whether SwitchA, SwitchB, and SwitchC set up a stack successfully. For details, see step 5.
Figure 3-31 Stack connection
Check whether a stack is set up successfully.
# Check the stack indicator status.

Press the MODE button on any member switch to change the mode status indicator to the stack mode.
- If the mode status indicators on all the member switches change to the stack mode, the stack is set up successfully.
- If the mode status indicator on any member switch does not change to the stack mode, the stack is not set up.
- The S5700-EI, S5700-SI, and S5710-C-LI use the same mode status indicator to show 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.
- The S5720-EI has an independent stack mode indicator (STCK indicator). After you press the MODE button, the indicator is steady green or blinking and off after 45 seconds, indicating that the switch enters the stack mode.
# Check basic stack information.

Log in to the stack to check whether the number of member switches in the stack is the same as the actual value and whether the stack topology is the same as the actual hardware connection.
```
<SwitchA> system-view
[SwitchA] sysname Stack
[Stack] display stack
Stack mode: Card   
Stack topology type: Ring
Stack system MAC: xxxx-xxxx-xxx5
MAC switch delay time: 10 min
Stack reserved vlan : 4093
Slot of the active management port: 0
Slot     Role        Mac address      Priority   Device type
-------------------------------------------------------------
    0     Master      xxxx-xxxx-xxx5   200        S5728C-EI
    1     Standby     xxxx-xxxx-xxx1   100        S5728C-EI
    2     Slave       xxxx-xxxx-xxx2   100        S5728C-EI
```

Configure an inter-device Eth-Trunk.

# Create an Eth-Trunk in the stack and configure uplink physical ports as Eth-Trunk member ports.

[Stack] interface eth-trunk 10
[Stack-Eth-Trunk10] trunkport gigabitethernet 0/0/5
[Stack-Eth-Trunk10] trunkport gigabitethernet 1/0/5
[Stack-Eth-Trunk10] trunkport gigabitethernet 2/0/5
[Stack-Eth-Trunk10] quit

# Create an Eth-Trunk on SwitchD and configure the ports connected to the stack as Eth-Trunk member ports.

<HUAWEI> system-view
[HUAWEI] sysname SwitchD
[SwitchD] interface eth-trunk 10
[SwitchD-Eth-Trunk10] trunkport gigabitethernet 0/0/1
[SwitchD-Eth-Trunk10] trunkport gigabitethernet 0/0/2
[SwitchD-Eth-Trunk10] trunkport gigabitethernet 0/0/3
[SwitchD-Eth-Trunk10] quit

Verify the Eth-Trunk configuration.

# Check Eth-Trunk member port information. The following displays information about Eth-Trunk member ports in the stack.

[Stack] display trunkmembership eth-trunk 10
Trunk ID: 10
Used status: VALID
TYPE: ethernet
Working Mode : Normal
Number Of Ports in Trunk = 3
Number Of Up Ports in Trunk = 3
Operate status: up

Interface GigabitEthernet0/0/5, valid, operate up, weight=1
Interface GigabitEthernet1/0/5, valid, operate up, weight=1
Interface GigabitEthernet2/0/5, valid, operate up, weight=1

Configure MAD in relay mode and configure SwitchD as the relay agent.

# In the stack, configure MAD in relay mode on the inter-device Eth-Trunk.

[Stack] interface eth-trunk 10
[Stack-Eth-Trunk10] mad detect mode relay    //This command is used in versions later than V200R002. The command used in V200R002 and earlier versions is dual-active detect mode relay.
[Stack-Eth-Trunk10] return

# On SwitchD, configure MAD in relay mode on the Eth-Trunk.

[SwitchD] interface eth-trunk 10
[SwitchD-Eth-Trunk10] mad relay               //This command is used in versions later than V200R002. The command used in V200R002 and earlier versions is dual-active relay.
[SwitchD-Eth-Trunk10] return

Verify the MAD configuration.

# Check the MAD configuration of the stack.

<Stack> display mad verbose    //This command is used in versions later than V200R002. The command used in V200R002 and earlier versions is display dual-active verbose.
Current MAD domain: 0 
Current MAD status: Detect
Mad direct detect interfaces configured:
Mad relay detect interfaces configured:
 Eth-Trunk10 
Excluded ports(configurable):
Excluded ports(can not be configured):

# Check the MAD proxy configuration on SwitchD.

<SwitchD> display mad proxy    //This command is used in versions later than V200R002. The command used in V200R002 and earlier versions is display dual-active proxy.
Mad relay interfaces configured:
 Eth-Trunk10

Configuration Files

Stack configuration file (the stack configuration is written to the flash memory instead of the configuration file)

#
sysname Stack
#
interface Eth-Trunk10
 mad detect mode relay
#
interface GigabitEthernet0/0/5
 eth-trunk 10
#
interface GigabitEthernet1/0/5
 eth-trunk 10
#
interface GigabitEthernet2/0/5
 eth-trunk 10
#
return

SwitchD configuration file

#
sysname SwitchD
#
interface Eth-Trunk10
 mad relay
#
interface GigabitEthernet0/0/1
 eth-trunk 10
#
interface GigabitEthernet0/0/2
 eth-trunk 10
#
interface GigabitEthernet0/0/3
 eth-trunk 10
#
return

Example for Setting Up a Stack Using Service Ports (V100R006C05)

Overview

When S2710-SI, S2700-EI, S3700-SI, and S3700-EI switches set up stacks using service ports, you do not need to manually configure stack ports. After the switches are correctly connected using stack cables, a stack can be set up automatically.

Networking Requirements

A new enterprise network needs to provide sufficient ports for access devices, and the network structure should be simple to facilitate configuration and management.

As shown in Figure 3-32, SwitchA, SwitchB, and SwitchC need to set up a stack in a ring topology and connect to SwitchD through an inter-device Eth-Trunk. SwitchA, SwitchB, and SwitchC are the master, standby, and slave switches respectively, with stack IDs of 0, 1, and 2 and stack priorities of 200, 100, and 100. As the three switches function as one logical device on the network, the number of ports is increased and network management and maintenance are simplified.

In this example, S3700-EIs set up a stack.

Figure 3-32 Stack networking

Configuration Roadmap

The stacking function is enabled by default on the S3700-EI. Therefore, these switches can set up a stack immediately after they are connected using stack cables, without additional configuration. To facilitate device management and identification, configure device names, stack IDs, and stack priorities for stack member switches.
Power off SwitchA, SwitchB, and SwitchC, connect physical member ports using SFP stack cables, and then power on the three switches.
Configure an inter-device Eth-Trunk to increase reliability and uplink bandwidth.

Procedure

Configure device names to differentiate devices.
# Configure a device name for SwitchA.
```
<HUAWEI> system-view
[HUAWEI] sysname SwitchA
```
# Configure a device name for SwitchB.
```
<HUAWEI> system-view
[HUAWEI] sysname SwitchB
```
# Configure a device name for SwitchC.
```
<HUAWEI> system-view
[HUAWEI] sysname SwitchC
```

Configure stack IDs and stack priorities. The default stack ID is 0, and the default stack priority is 100.

[SwitchA] stack slot 0 priority 200     //Set the stack priority of the master switch to 200, which is larger than those of other member switches, and use the default stack ID 0.

[SwitchB] stack slot 0 renumber 1       //Use the default stack priority 100 and set the stack ID to 1.

[SwitchC] stack slot 0 renumber 2       //Use the default stack priority 100 and set the stack ID to 2.

Turn off power supplies of SwitchA, SwitchB, and SwitchC, connect physical member ports using SFP stack cables as shown in Figure 3-33, and then power on the three switches.
- Run the save command to save the configurations before you power off the switches.
- To ensure that a stack can be set up successfully, you are advised to perform operations in the following sequence. To specify a member switch as the master switch, power on that switch first. In this example, SwitchA becomes the master switch after you complete the following operations.
  1. Power off SwitchA, SwitchB, and SwitchC.
  2. Connect SwitchA and SwitchB with a stack cable.
  3. Power on and start SwitchA and then power on SwitchB.
  4. Check whether SwitchA and SwitchB set up a stack successfully. For details, see step 4.
  5. Connect SwitchC to SwitchB and SwitchA using stack cables and then power on SwitchC.
  6. Check whether SwitchA, SwitchB, and SwitchC set up a stack successfully. For details, see step 4.
Figure 3-33 Stack connection

Check whether a stack is set up successfully.

# Log in to the stack through the console port of the master switch to check whether the number of member switches in the stack is the same as the actual value and whether the stack topology is the same as the actual hardware connection.

<SwitchA> system-view
[SwitchA] sysname Stack
[Stack] display stack
Stack topology type: Ring
Stack system MAC: xxxx-xxxx-xxx8
MAC switch delay time: never
Stack reserved vlanid : 4093
Slot     Role        Mac address      Priority   Device type
-------------------------------------------------------------
0         Master      xxxx-xxxx-xxx8   200       S3728TP-EI
1         Standby     xxxx-xxxx-xxx1   100       S3728TP-EI
2         Slave       xxxx-xxxx-xxx5   100       S3728TP-EI

Configure an inter-device Eth-Trunk.

# Create an Eth-Trunk in the stack and configure uplink physical ports as Eth-Trunk member ports.

[Stack] interface eth-trunk 10
[Stack-Eth-Trunk10] trunkport ethernet 0/0/5
[Stack-Eth-Trunk10] trunkport ethernet 1/0/5
[Stack-Eth-Trunk10] trunkport ethernet 2/0/5
[Stack-Eth-Trunk10] return

# Create an Eth-Trunk on SwitchD and configure the ports connected to the stack as Eth-Trunk member ports.

<HUAWEI> system-view
[HUAWEI] sysname SwitchD
[SwitchD] interface eth-trunk 10
[SwitchD-Eth-Trunk10] trunkport ethernet 0/0/1
[SwitchD-Eth-Trunk10] trunkport ethernet 0/0/2
[SwitchD-Eth-Trunk10] trunkport ethernet 0/0/3
[SwitchD-Eth-Trunk10] return

Verify the Eth-Trunk configuration.

# Check Eth-Trunk member port information. The following displays information about Eth-Trunk member ports in the stack.

<Stack> display trunkmembership eth-trunk 10
Trunk ID: 10
used status: VALID
TYPE: ethernet
Working Mode : Normal
Number Of Ports in Trunk = 3
Number Of UP Ports in Trunk = 3
operate status: up

Interface Ethernet0/0/5, valid, operate up, weight=1
Interface Ethernet1/0/5, valid, operate up, weight=1
Interface Ethernet2/0/5, valid, operate up, weight=1

Configuration Files

Stack configuration file (the stack configuration is written to the flash memory instead of the configuration file)

#
 sysname Stack
#
interface Eth-Trunk10
#
interface Ethernet0/0/5
 eth-trunk 10
#
interface Ethernet1/0/5
 eth-trunk 10
#
interface Ethernet2/0/5
 eth-trunk 10
#
return

SwitchD configuration file

#
 sysname SwitchD
#
interface Eth-Trunk10
#
interface Ethernet0/0/1
 eth-trunk 10
#
interface Ethernet0/0/2
 eth-trunk 10
#
interface Ethernet0/0/3
 eth-trunk 10
#
return

Example for Setting Up a Stack Using Service Ports (V200R001 to V200R002)

Overview

Service port connection allows member switches to be connected using service ports, without requiring dedicated stack cards.

To improve stack efficiency and reduce manual configuration, since V200R011C10, switches can set up a stack using dedicated stack cables. Service port connections are classified into ordinary and dedicated cable connections based on cable types.

Ordinary cable connection: Switches use optical cables, network cables, and high-speed cables to set up a stack.
Dedicated cable connection: Switches use dedicated stack cables to set up a stack. The two ends of a dedicated stack cable are the master end with the Master tag and the slave end without any tag. The device connected to the master end of a dedicated stack cable assumes the master role and the device connected to the slave end assumes the slave role only after you perform operations as required.

Networking Requirements

A new enterprise network needs to provide sufficient ports for access devices, and the network structure should be simple to facilitate configuration and management.

As shown in Figure 3-34, SwitchA, SwitchB, and SwitchC need to set up a stack in a ring topology and connect to SwitchD through an inter-device Eth-Trunk. SwitchA, SwitchB, and SwitchC are the master, standby, and slave switches respectively, with stack IDs of 0, 1, and 2 and stack priorities of 200, 100, and 100. As the three switches function as one logical device on the network, the number of ports is increased and network management and maintenance are simplified.

In this example, S5700-LIs set up a stack.

Figure 3-34 Stack networking

Configuration Roadmap

Configure logical stack ports and add physical member ports to the corresponding logical stack ports to enable packet forwarding between member switches.
Configure stack IDs and stack priorities for member switches to facilitate device management and identification.
Power off SwitchA, SwitchB, and SwitchC, connect physical member ports using SFP+ stack cables, and then power on the three switches.
Configure an inter-device Eth-Trunk to increase reliability and uplink bandwidth.
Configure dual-active detection (DAD) in relay mode to ensure network availability when the stack splits.

Procedure

Configure logical stack ports and add physical member ports to them.

Interface stack-port 0/1 of one switch must be connected to interface stack-port 0/2 of another switch. Otherwise, the stack cannot be set up.

# Configure service ports GigabitEthernet0/0/27 and GigabitEthernet0/0/28 on SwitchA as physical member ports and add them to corresponding logical stack ports.

<HUAWEI> system-view
[HUAWEI] sysname SwitchA
[SwitchA] stack port interface gigabitethernet 0/0/27 enable
[SwitchA] stack port interface gigabitethernet 0/0/28 enable
[SwitchA] interface stack-port 0/1
[SwitchA-stack-port0/1] port member-group interface gigabitethernet 0/0/27
[SwitchA-stack-port0/1] quit
[SwitchA] interface stack-port 0/2
[SwitchA-stack-port0/2] port member-group interface gigabitethernet 0/0/28
[SwitchA-stack-port0/2] quit

# Configure service ports GigabitEthernet0/0/27 and GigabitEthernet0/0/28 on SwitchB as physical member ports and add them to corresponding logical stack ports.

<HUAWEI> system-view
[HUAWEI] sysname SwitchB
[SwitchB] stack port interface gigabitethernet 0/0/27 enable
[SwitchB] stack port interface gigabitethernet 0/0/28 enable
[SwitchB] interface stack-port 0/1
[SwitchB-stack-port0/1] port member-group interface gigabitethernet 0/0/27
[SwitchB-stack-port0/1] quit
[SwitchB] interface stack-port 0/2
[SwitchB-stack-port0/2] port member-group interface gigabitethernet 0/0/28
[SwitchB-stack-port0/2] quit

# Configure service ports GigabitEthernet0/0/27 and GigabitEthernet0/0/28 on SwitchC as physical member ports and add them to corresponding logical stack ports.

<HUAWEI> system-view
[HUAWEI] sysname SwitchC
[SwitchC] stack port interface gigabitethernet 0/0/27 enable
[SwitchC] stack port interface gigabitethernet 0/0/28 enable
[SwitchC] interface stack-port 0/1
[SwitchC-stack-port0/1] port member-group interface gigabitethernet 0/0/27
[SwitchC-stack-port0/1] quit
[SwitchC] interface stack-port 0/2
[SwitchC-stack-port0/2] port member-group interface gigabitethernet 0/0/28
[SwitchC-stack-port0/2] quit

Configure stack IDs and stack priorities. The default stack ID is 0, and the default stack priority is 100.

[SwitchA] stack slot 0 priority 200     //Set the stack priority of the master switch to 200, which is larger than those of other member switches, and use the default stack ID 0.

[SwitchB] stack slot 0 renumber 1       //Use the default stack priority 100 and set the stack ID to 1.

[SwitchC] stack slot 0 renumber 2       //Use the default stack priority 100 and set the stack ID to 2.

Turn off power supplies of SwitchA, SwitchB, and SwitchC, connect physical member ports using SFP+ stack cables as shown in Figure 3-35, and then power on the three switches.
- Run the save command to save the configurations before you power off the switches.
- To ensure that a stack can be set up successfully, you are advised to perform operations in the following sequence. To specify a member switch as the master switch, power on that switch first. In this example, SwitchA becomes the master switch after you complete the following operations.
  1. Power off SwitchA, SwitchB, and SwitchC.
  2. Connect SwitchA and SwitchB with a stack cable.
  3. Power on and start SwitchA and then power on SwitchB.
  4. Check whether SwitchA and SwitchB set up a stack successfully. For details, see step 4.
  5. Connect SwitchC to SwitchB and SwitchA using stack cables and then power on SwitchC.
  6. Check whether SwitchA, SwitchB, and SwitchC set up a stack successfully. For details, see step 4.
Figure 3-35 Stack connection
Check whether a stack is set up successfully.
# Check the stack indicator status.

Press the MODE button on any member switch to change the mode status indicator to the stack mode.
- If the mode status indicators on all the member switches change to the stack mode, the stack is set up successfully.
- If the mode status indicator on any member switch does not change to the stack mode, the stack is not set up.
- The S6700-EI uses the mode status indicator to show 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.
- The S5700-LI and S5710-EI have an independent stack mode indicator (STCK indicator). After you press the MODE button, the indicator is steady green or blinking and off after 45 seconds, indicating that the switch enters the stack mode.
# Check basic stack information.

Log in to the stack to check whether the number of member switches in the stack is the same as the actual value and whether the stack topology is the same as the actual hardware connection.
```
<SwitchA> system-view
[SwitchA] sysname Stack
[Stack] display stack
Stack topology type : Ring
Stack system MAC: 00e0-fc00-1234
MAC switch delay time: 10 min
Stack reserved vlanid : 4093
Slot     Role        Mac address      Priority   Device type
-------------------------------------------------------------
    0     Master      00e0-fc00-1234   200        S5700-28P-LI-AC
    1     Standby     00e0-fc00-1235   100        S5700-28P-LI-AC
    2     Slave       00e0-fc00-1236   100        S5700-28P-LI-AC
```

Configure an inter-device Eth-Trunk.

# Create an Eth-Trunk in the stack and configure uplink physical ports as Eth-Trunk member ports.

[Stack] interface eth-trunk 10
[Stack-Eth-Trunk10] trunkport gigabitethernet 0/0/5
[Stack-Eth-Trunk10] trunkport gigabitethernet 1/0/5
[Stack-Eth-Trunk10] trunkport gigabitethernet 2/0/5
[Stack-Eth-Trunk10] quit

# Create an Eth-Trunk on SwitchD and configure the ports connected to the stack as Eth-Trunk member ports.

<HUAWEI> system-view
[HUAWEI] sysname SwitchD
[SwitchD] interface eth-trunk 10
[SwitchD-Eth-Trunk10] trunkport gigabitethernet 0/0/1
[SwitchD-Eth-Trunk10] trunkport gigabitethernet 0/0/2
[SwitchD-Eth-Trunk10] trunkport gigabitethernet 0/0/3
[SwitchD-Eth-Trunk10] quit

Verify the Eth-Trunk configuration.

# Check Eth-Trunk member port information. The following displays information about Eth-Trunk member ports in the stack.

[Stack] display trunkmembership eth-trunk 10
Trunk ID: 10
Used status: VALID
TYPE: ethernet
Working Mode : Normal
Number Of Ports in Trunk = 3
Number Of Up Ports in Trunk = 3
Operate status: up

Interface GigabitEthernet0/0/5, valid, operate up, weight=1
Interface GigabitEthernet1/0/5, valid, operate up, weight=1
Interface GigabitEthernet2/0/5, valid, operate up, weight=1

Configure DAD in relay mode on SwitchD and configure SwitchD as the relay agent.

# In the stack, configure DAD in relay mode on the inter-device Eth-Trunk.

[Stack] interface eth-trunk 10
[Stack-Eth-Trunk10] dual-active detect mode relay
[Stack-Eth-Trunk10] return

# On SwitchD, configure DAD in relay mode on the Eth-Trunk.

[SwitchD] interface eth-trunk 10
[SwitchD-Eth-Trunk10] dual-active relay
[SwitchD-Eth-Trunk10] return

Verify the DAD configuration.

# Check the DAD configuration of the stack.

<Stack> display dual-active verbose
Current DAD status: Detect                                                      
Dual-active direct detect interfaces configured:                                
Dual-active relay detect interfaces configured:                                 
 Eth-Trunk10
Excluded ports(configurable):                                                   
Excluded ports(can not be configured): 
 GigabitEthernet0/0/27                                          
 GigabitEthernet0/0/28
 GigabitEthernet1/0/27                                          
 GigabitEthernet1/0/28                                          
 GigabitEthernet2/0/27                                          
 GigabitEthernet2/0/28

# Check the DAD proxy configuration on SwitchD.

<SwitchD> display dual-active proxy
Dual-active relay interfaces configured:
 Eth-Trunk10

Configuration Files

Stack configuration file (the stack configuration is written to the flash memory instead of the configuration file)

#
sysname Stack
#
interface Eth-Trunk10
 dual-active detect mode relay
#
interface GigabitEthernet0/0/5
 eth-trunk 10
#
interface GigabitEthernet1/0/5
 eth-trunk 10
#
interface GigabitEthernet2/0/5
 eth-trunk 10
#
return

SwitchD configuration file

#
sysname SwitchD
#
interface Eth-Trunk10
 dual-active relay
#
interface GigabitEthernet0/0/1
 eth-trunk 10
#
interface GigabitEthernet0/0/2
 eth-trunk 10
#
interface GigabitEthernet0/0/3
 eth-trunk 10
#
return

Example for Setting Up a Stack Using Service Ports (V200R003 and Later Versions)

Overview

Service port connection allows member switches to be connected using service ports, without requiring dedicated stack cards.

Ordinary cable connection: Switches use optical cables, network cables, and high-speed cables to set up a stack.
Dedicated cable connection: Switches use dedicated stack cables to set up a stack. The two ends of a dedicated stack cable are the master end with the Master tag and the slave end without any tag. The device connected to the master end of a dedicated stack cable assumes the master role and the device connected to the slave end assumes the slave role only after you perform operations as required.

Networking Requirements

A new enterprise network needs to provide sufficient ports for access devices, and the network structure should be simple to facilitate configuration and management.

As shown in Figure 3-36, SwitchA, SwitchB, and SwitchC need to set up a stack in a ring topology and connect to SwitchD through an inter-device Eth-Trunk. SwitchA, SwitchB, and SwitchC are the master, standby, and slave switches respectively, with stack IDs of 0, 1, and 2 and stack priorities of 200, 100, and 100. As the three switches function as one logical device on the network, the number of ports is increased and network management and maintenance are simplified.

In this example, S5700-28X-LI-AC set up a stack.

Figure 3-36 Stack networking

Configuration Roadmap

Configure logical stack ports and add physical member ports to the corresponding logical stack ports to enable packet forwarding between member switches.
Configure stack IDs and stack priorities for member switches to facilitate device management and identification.
Turn off power supplies of SwitchA, SwitchB, and SwitchC, connect physical member ports using SFP+ stack cables, and then power on the three switches.
Configure an inter-device Eth-Trunk to increase reliability and uplink bandwidth.
Configure multi-active detection (MAD) in relay mode to ensure network availability when the stack splits.

Procedure

Configure logical stack ports and add physical member ports to them.

Interface stack-port 0/1 of one switch must be connected to interface stack-port 0/2 of another switch. Otherwise, the stack cannot be set up.

# Configure service ports GigabitEthernet0/0/27 and GigabitEthernet0/0/28 on SwitchA as physical member ports and add them to corresponding logical stack ports.

<HUAWEI> system-view
[HUAWEI] sysname SwitchA
[SwitchA] interface stack-port 0/1
[SwitchA-stack-port0/1] port interface gigabitethernet 0/0/27 enable
[SwitchA-stack-port0/1] quit
[SwitchA] interface stack-port 0/2
[SwitchA-stack-port0/2] port interface gigabitethernet 0/0/28 enable
[SwitchA-stack-port0/2] quit

# Configure service ports GigabitEthernet0/0/27 and GigabitEthernet0/0/28 on SwitchB as physical member ports and add them to corresponding logical stack ports.

<HUAWEI> system-view
[HUAWEI] sysname SwitchB
[SwitchB] interface stack-port 0/1
[SwitchB-stack-port0/1] port interface gigabitethernet 0/0/27 enable
[SwitchB-stack-port0/1] quit
[SwitchB] interface stack-port 0/2
[SwitchB-stack-port0/2] port interface gigabitethernet 0/0/28 enable
[SwitchB-stack-port0/2] quit

# Configure service ports GigabitEthernet0/0/27 and GigabitEthernet0/0/28 on SwitchC as physical member ports and add them to corresponding logical stack ports.

<HUAWEI> system-view
[HUAWEI] sysname SwitchC
[SwitchC] interface stack-port 0/1
[SwitchC-stack-port0/1] port interface gigabitethernet 0/0/27 enable
[SwitchC-stack-port0/1] quit
[SwitchC] interface stack-port 0/2
[SwitchC-stack-port0/2] port interface gigabitethernet 0/0/28 enable
[SwitchC-stack-port0/2] quit

Configure stack IDs and stack priorities. The default stack ID is 0, and the default stack priority is 100.

[SwitchA] stack slot 0 priority 200     //Set the stack priority of the master switch to 200, which is larger than those of other member switches, and use the default stack ID 0.

[SwitchB] stack slot 0 renumber 1       //Use the default stack priority 100 and set the stack ID to 1.

[SwitchC] stack slot 0 renumber 2       //Use the default stack priority 100 and set the stack ID to 2.

Turn off power supplies of SwitchA, SwitchB, and SwitchC, connect physical member ports using SFP+ stack cables as shown in Figure 3-37, and then power on the three switches.
- Run the save command to save the configurations before you power off the switches.
- To ensure that a stack can be set up successfully, you are advised to perform operations in the following sequence. To specify a member switch as the master switch, power on that switch first. In this example, SwitchA becomes the master switch after you complete the following operations.
  1. Power off SwitchA, SwitchB, and SwitchC.
  2. Connect SwitchA and SwitchB with a stack cable.
  3. Power on and start SwitchA and then power on SwitchB.
  4. Check whether SwitchA and SwitchB set up a stack successfully. For details, see step 4.
  5. Connect SwitchC to SwitchB and SwitchA using stack cables and then power on SwitchC.
  6. Check whether SwitchA, SwitchB, and SwitchC set up a stack successfully. For details, see step 4.
Figure 3-37 Stack connection
Check whether a stack is set up successfully.
# Check the stack indicator status.

Press the MODE button on any member switch to change the mode status indicator to the stack mode.
- If the mode status indicators on all the member switches change to the stack mode, the stack is set up successfully.
- If the mode status indicator on any member switch does not change to the stack mode, the stack is not set up.
- The S5700-SI, S5700-EI, S5700-HI, S6700-EI, S5710-C-LI use the same mode status indicator to show 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.
- The S5732-H, S6730-S, S6730S-S, S6720-HI, S6730-H, and S6730S-H have an independent stack master/slave indicator to show the MST. If the indicator is off, the switch is not a stack master. If the indicator is steady green, the switch is a stack master or standalone switch.
- Other models have an independent stack mode indicator (STCK indicator). After you press the MODE button, the indicator is steady green or blinking and off after 45 seconds, indicating that the switch enters the stack mode.
# Check basic stack information.

Log in to the stack through the console port of any member switch to check whether the number of member switches in the stack is the same as the actual value and whether the stack topology is the same as the actual hardware connection.
```
<SwitchA> system-view
[SwitchA] sysname Stack
[Stack] display stack
Stack mode: Service-port
Stack topology type : Ring
Stack system MAC: xxxx-xxxx-xxx5
MAC switch delay time: 10 min
Stack reserved vlan : 4093
Slot of the active management port: 0 
Slot     Role        Mac address      Priority   Device type
-------------------------------------------------------------
    0     Master      xxxx-xxxx-xxx5   200        S5700-28P-LI-AC
    1     Standby     xxxx-xxxx-xxx4   100        S5700-28P-LI-AC
    2     Slave       xxxx-xxxx-xxx1   100        S5700-28P-LI-AC
```

Configure an inter-device Eth-Trunk.

# Create an Eth-Trunk in the stack and configure uplink physical ports as Eth-Trunk member ports.

[Stack] interface eth-trunk 10
[Stack-Eth-Trunk10] trunkport gigabitethernet 0/0/5
[Stack-Eth-Trunk10] trunkport gigabitethernet 1/0/5
[Stack-Eth-Trunk10] trunkport gigabitethernet 2/0/5
[Stack-Eth-Trunk10] quit

# Create an Eth-Trunk on SwitchD and configure the ports connected to the stack as Eth-Trunk member ports.

<HUAWEI> system-view
[HUAWEI] sysname SwitchD
[SwitchD] interface eth-trunk 10
[SwitchD-Eth-Trunk10] trunkport gigabitethernet 0/0/1
[SwitchD-Eth-Trunk10] trunkport gigabitethernet 0/0/2
[SwitchD-Eth-Trunk10] trunkport gigabitethernet 0/0/3
[SwitchD-Eth-Trunk10] quit

Verify the Eth-Trunk configuration.

# Check Eth-Trunk member port information. The following displays information about Eth-Trunk member ports in the stack.

[Stack] display trunkmembership eth-trunk 10
Trunk ID: 10
Used status: VALID
TYPE: ethernet
Working Mode : Normal
Number Of Ports in Trunk = 3
Number Of Up Ports in Trunk = 3
Operate status: up

Interface GigabitEthernet0/0/5, valid, operate up, weight=1
Interface GigabitEthernet1/0/5, valid, operate up, weight=1
Interface GigabitEthernet2/0/5, valid, operate up, weight=1

Configure MAD in relay mode on SwitchD and configure SwitchD as the relay agent.

# In the stack, configure MAD in relay mode on the inter-device Eth-Trunk.

[Stack] interface eth-trunk 10
[Stack-Eth-Trunk10] mad detect mode relay 
[Stack-Eth-Trunk10] return

# On SwitchD, configure MAD in relay mode on the Eth-Trunk.

[SwitchD] interface eth-trunk 10
[SwitchD-Eth-Trunk10] mad relay     
[SwitchD-Eth-Trunk10] return

Verify the MAD configuration.

# Check the MAD configuration of the stack.

<Stack> display mad verbose
Current MAD domain: 0 
Current MAD status: Detect                                                      
Mad direct detect interfaces configured:                                
Mad relay detect interfaces configured:                                 
 Eth-Trunk10                                                                  
Excluded ports(configurable):                                                   
Excluded ports(can not be configured):
 GigabitEthernet0/0/27                                          
 GigabitEthernet0/0/28
 GigabitEthernet1/0/27                                          
 GigabitEthernet1/0/28                                          
 GigabitEthernet2/0/27                                          
 GigabitEthernet2/0/28

# Check the MAD proxy configuration on SwitchD.

<SwitchD> display mad proxy
Mad relay interfaces configured:                                        
 Eth-Trunk10

Configuration Files

Stack configuration file (the stack configuration is written to the flash memory instead of the configuration file)

#
sysname Stack
#
interface Eth-Trunk10
 mad detect mode relay
#
interface GigabitEthernet0/0/5
 eth-trunk 10
#
interface GigabitEthernet1/0/5
 eth-trunk 10
#
interface GigabitEthernet2/0/5
 eth-trunk 10
#
return

SwitchD configuration file

#
sysname SwitchD
#
interface Eth-Trunk10
 mad relay
#
interface GigabitEthernet0/0/1
 eth-trunk 10
#
interface GigabitEthernet0/0/2
 eth-trunk 10
#
interface GigabitEthernet0/0/3
 eth-trunk 10
#
return

Example for Establishing a Stack Through Service Port Connections Using Dedicated Stack Cables (V200R011C10 and Later Versions)

Overview

Service port connection allows member switches to be connected using service ports, without requiring dedicated stack cards.

Ordinary cable connection: Switches use optical cables, network cables, and high-speed cables to set up a stack.
Dedicated cable connection: Switches use dedicated stack cables to set up a stack. The two ends of a dedicated stack cable are the master end with the Master tag and the slave end without any tag. The device connected to the master end of a dedicated stack cable assumes the master role and the device connected to the slave end assumes the slave role only after you perform operations as required.

Precautions

Connect member switches using dedicated stack cables based on the following rules:
- Connect the switches in sequence from top to bottom.
- Ensure that all logical stack ports of the top switch are connected to the master ends of cables, all logical stack ports of the bottom switch are connected to the slave ends of cables, and two logical stack ports of the intermediate switch are connected to the master and slave ends respectively.
- After the switches have been connected using dedicated stack cables, they automatically set up a stack and their stack IDs as well as stack roles are automatically assigned.
- If the switches are not connected in a ring topology, you only need to ensure that logical stack port 1 of the local switch is connected to logical stack port 2 of the remote switch. In this situation, these switches can set up a stack, but their master and standby roles and stack IDs are randomly generated.
Ensure that there are no service configurations on the ports that have dedicated stack cables connected. Otherwise, these ports cannot automatically become stack ports and the switches cannot set up a stack.
- On ASs in an SVF system, ensure that there are no other configurations except the shutdown and stp root-protection command configurations on ports.
- On other switches, ensure that there are no other configurations except the shutdown command configuration on ports.
If logical stack port numbers have been manually configured before dedicated stack cables are connected, the configured port numbers still take effect after the cables are connected. You need to connect these ports based on the configured port numbers. If logical stack port numbers are not manually configured, corresponding logical stack port numbers will be automatically generated after dedicated stack cables are connected. To view logical stack ports of ports supporting dedicated stack cables and master as well as slave ends of the cables connected to these ports, run the display stack port auto-cable-info command.

Networking Requirements

An enterprise network needs to provide sufficient ports for access devices, and the network structure should be simple to facilitate configuration and management.

As shown in Figure 3-38, Switches A to C set up a stack in a ring topology and connect to SwitchD through an inter-chassis Eth-Trunk. To reduce the configuration, Switches A to C set up a stack using dedicated stack cables. In the stack, SwitchA needs to function as the master switch, Switch B as the standby switch, and SwitchC as the slave switch.

This example describes how to use S5720-28P-PWR-LI-AC switches to set up a stack.

Figure 3-38 Stack topology

Configuration Roadmap

Power off SwitchA, SwitchB, and SwitchC to ensure security.
Connect the switches using dedicated stack cables based on dedicated stack cable connection rules.
Power on these switches in the following sequence to ensure that SwitchA, SwitchB, and SwitchC become the master switch, standby switch, and slave switch respectively.
Save the stack configuration automatically generated for dedicated cable stacking to the flash memory. This ensures that the stack configuration still takes effect when these cables are removed or other cables are connected.
Configure an inter-chassis Eth-Trunk to increase reliability and uplink bandwidth.
Configure multi-active detection in relay mode to ensure network availability when the stack splits.

Procedure

Power off SwitchA, SwitchB, and SwitchC.
Power off SwitchA, SwitchB, and SwitchC and then connect them using dedicated stack cables as shown in Figure 3-39.
- Logical stack port 1 of the local switch must be connected to logical stack port 2 of the adjacent switch. Otherwise, these switches cannot set up a stack.
- All logical stack ports of SwitchA must be connected to the master ends of dedicated stack cables, and all logical stack ports of SwitchC must be connected to the slave ends of these cables.
Figure 3-39 Dedicated stack cable connection
Power on SwitchA, SwitchB, and SwitchC in sequence.
# Power on these switches in the following sequence to ensure that SwitchA, SwitchB, and SwitchC become the master switch, standby switch, and slave switch respectively.
1. Power on SwitchA first.
2. Power on SwitchB after SwitchA starts.
3. Power on SwitchC after SwitchB starts.
The preceding power-on sequence can guarantee only roles of these switches but not their slot IDs. The following assumes that SwitchA, SwitchB, and SwitchC use automatically generated slot IDs 0, 1, and 2 respectively.
Check whether a stack has been set up successfully.
# Check the stack indicator status.

Press the mode switching (MODE) button on any member switch to change the mode status indicator to the stack mode.
- If the mode status indicators on all member switches change to the stack mode, a stack has been set up successfully.
- If the mode status indicator on any member switch does not change to the stack mode, a stack has not been set up.
- The S5700-SI, S5700-EI, S5700-HI, S6700-EI, S5710-C-LI use the same mode status indicator to show 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.
- The S5732-H, S6730-S, S6730S-S, S6720-HI, S6730-H, and S6730S-H have an independent stack master/slave indicator to show the MST. If the indicator is off, the switch is not a stack master. If the indicator is steady green, the switch is a stack master or standalone switch.
- Other models have an independent stack mode indicator (STCK indicator). After you press the MODE button, the indicator is steady green or blinking and off after 45 seconds, indicating that the switch enters the stack mode.
# Check basic stack information.

Log in to the stack through the console port of any member switch to check whether the number of member switches in the stack is the same as the actual value and whether the stack topology status is the same as the actual hardware connection.
```
<SwitchA> system-view
[SwitchA] sysname Stack
[Stack] display stack
Stack mode: Service-port
Stack topology type : Ring
Stack system MAC: xxxx-xxxx-xxx5
MAC switch delay time: 10 min
Stack reserved vlan : 4093
Slot of the active management port: 0 
Slot     Role        Mac address      Priority   Device type
-------------------------------------------------------------
    0     Master      xxxx-xxxx-xxx5   100        S5720-28P-LI-AC
    1     Standby     xxxx-xxxx-xxx4   100        S5720-28P-LI-AC
    2     Slave       xxxx-xxxx-xxx1   100        S5720-28P-LI-AC
```
Save the stack configuration that is automatically generated for dedicated cable stacking to the flash memory.
# After verifying that a stack has been set up, save the stack configuration that is automatically generated for dedicated cable stacking to the flash memory.
```
[Stack] save stack configuration 
Warning: This operation will save all stack configurations to flash. Are you sure you want to continue? [Y/N]:y
```

Configure an inter-device Eth-Trunk.

# Create an Eth-Trunk in the stack and configure uplink physical ports as Eth-Trunk member ports.

[Stack] interface eth-trunk 10
[Stack-Eth-Trunk10] trunkport gigabitethernet 0/0/5
[Stack-Eth-Trunk10] trunkport gigabitethernet 1/0/5
[Stack-Eth-Trunk10] trunkport gigabitethernet 2/0/5
[Stack-Eth-Trunk10] quit

# Create an Eth-Trunk on SwitchD and configure the ports connected to the stack as Eth-Trunk member ports.

<HUAWEI> system-view
[HUAWEI] sysname SwitchD
[SwitchD] interface eth-trunk 10
[SwitchD-Eth-Trunk10] trunkport gigabitethernet 0/0/1
[SwitchD-Eth-Trunk10] trunkport gigabitethernet 0/0/2
[SwitchD-Eth-Trunk10] trunkport gigabitethernet 0/0/3
[SwitchD-Eth-Trunk10] quit

Verify the Eth-Trunk configuration.

# Check Eth-Trunk member port information. The following displays information about Eth-Trunk member ports in the stack.

[Stack] display trunkmembership eth-trunk 10
Trunk ID: 10
Used status: VALID
TYPE: ethernet
Working Mode : Normal
Number Of Ports in Trunk = 3
Number Of Up Ports in Trunk = 3
Operate status: up

Interface GigabitEthernet0/0/5, valid, operate up, weight=1
Interface GigabitEthernet1/0/5, valid, operate up, weight=1
Interface GigabitEthernet2/0/5, valid, operate up, weight=1

Configure MAD in relay mode on SwitchD and configure SwitchD as the relay agent.

# In the stack, configure MAD in relay mode on the inter-chassis Eth-Trunk.

[Stack] interface eth-trunk 10
[Stack-Eth-Trunk10] mad detect mode relay 
[Stack-Eth-Trunk10] return

# Configure MAD in relay mode on the relay agent SwitchD.

[SwitchD] interface eth-trunk 10
[SwitchD-Eth-Trunk10] mad relay     
[SwitchD-Eth-Trunk10] return

Verify the MAD configuration.

# Check detailed MAD configuration of the stack.

<Stack> display mad verbose
Current MAD domain: 0 
Current MAD status: Detect                                                      
Mad direct detect interfaces configured:                                
Mad relay detect interfaces configured:                                 
 Eth-Trunk10                                                                  
Excluded ports(configurable):                                                   
Excluded ports(can not be configured):
 GigabitEthernet0/0/26                                          
 GigabitEthernet0/0/27
 GigabitEthernet1/0/26                                          
 GigabitEthernet1/0/27                                          
 GigabitEthernet2/0/26                                          
 GigabitEthernet2/0/27

# Check the MAD proxy configuration on SwitchD.

<SwitchD> display mad proxy
Mad relay interfaces configured:                                        
 Eth-Trunk10

Configuration Files

Stack configuration file (the stack configuration is written to the flash memory instead of the configuration file)

#
sysname Stack
#
interface Eth-Trunk10
 mad detect mode relay
#
interface GigabitEthernet0/0/5
 eth-trunk 10
#
interface GigabitEthernet1/0/5
 eth-trunk 10
#
interface GigabitEthernet2/0/5
 eth-trunk 10
#
return

SwitchD configuration file

#
sysname SwitchD
#
interface Eth-Trunk10
 mad relay
#
interface GigabitEthernet0/0/1
 eth-trunk 10
#
interface GigabitEthernet0/0/2
 eth-trunk 10
#
interface GigabitEthernet0/0/3
 eth-trunk 10
#
return

Stacked Switch Replacement Guide

You may need to replace a faulty member switch in a stack. To prevent services from being interrupted during the switch replacement, use inter-device link aggregation to connect upstream and downstream devices for link backup.

Replace one member switch in a stack of two member switches.
SwitchA and SwitchB set up a stack. SwitchA is faulty and needs to be replaced by SwitchC. You are advised to follow this procedure to complete the replacement:
1. Before the replacement, ensure that SwitchC has the same system software version and hardware model as SwitchA. To check the system software version and hardware model of switches, run the display version and display device commands.
2. Run the display stack, display stack configuration, and display stack port commands to check and record the before-replacement stack status, stack configuration, and stack port status.
3. Before connecting SwitchC with stack cables, power on it and perform the following procedure to configure it:
  1. After SwitchC starts, upload the configuration file of SwitchA to SwitchC.
  2. Run the startup saved-configuration configuration-file command to specify the uploaded configuration file as the configuration file used for the next startup of SwitchC, and then restart SwitchC.
  3. After SwitchC restarts, manually copy the stack configuration displayed using the display stack configuration command to SwitchC to ensure that SwitchC has the same stack configuration as SwitchA.
4. After the configuration is complete, check whether SwitchC has the same stack configuration as SwitchA. If so, power off SwitchC.
5. (Optional) To prevent OSPF, BGP, or LDP flapping during an master/backup switchover in a stack, configure graceful restart (GR) for the corresponding protocol. For details, see the configuration guide of the corresponding protocol.
6. Run the display stack command to check whether SwitchA is the master switch. If so, run the slave switchover command to perform an active/standby switchover in the stack. If not, go to the next step.
```
<HUAWEI> display switchover state    //Check whether the active/standby switchover conditions are met.
Slot 0 HA FSM State(master): realtime or routine backup.    //The switchover can be performed only in this state.
Slot 1 HA FSM State(slave): receiving realtime or routine data. 
<HUAWEI> system-view
[HUAWEI] slave switchover enable    //Enable the active/standby switchover.
[HUAWEI] slave switchover    //Perform an active/standby switchover.
Warning: This operation will switch the slave board to the master board. Continue? [Y/N]:y
```
  After an active/standby switchover is performed, the master switch will restart. After the switch restarts and joins the stack again, go to the next step. To check whether the switch has joined the stack again, run the display stack command.
7. Power off and remove SwitchA.
8. Install SwitchC and connect cables to its service ports, stack ports, and ports that have dual-active detection (DAD) configured.
9. Power on SwitchC so that SwitchC joins the stack as a new member. Run the display stack command to check whether SwitchC can set up a stack with SwitchB.
10. After SwitchC and SwitchB set up a stack, run the display stack configuration and display stack port commands to check the stack configuration and interface status. Ensure that the stack configuration is the same as that used before the device replacement and that interfaces become Up normally.
11. After confirming all services are normal, run the save command to save the stack configuration.
12. If the current master and standby switches are different from those before the device replacement, perform an active/standby switchover.
Replace one member switch in a stack of three or more member switches (in a ring topology).

In a stack set up by three or more member switches in a ring topology, the device replacement procedure is similar to that in a stack of two member switches. For details, see Replace one member switch in a stack of two member switches.
Replace one member switch in a stack of three or more member switches (in a chain topology).
In a stack set up by three or more member switches in a chain topology, the replacement procedure of edge switches on both ends is similar to that in a stack of two member switches. For details, see Replace one member switch in a stack of two member switches. To replace an intermediate switch, change the stack connection topology to the ring topology and then replace the switch according to Replace one member switch in a stack of two member switches. The procedure is as follows:
1. On edge switches on both ends, create a logical stack port and add member ports into the logical stack port, and then connect these ports using cables.
```
<HUAWEI> system-view
[HUAWEI] interface stack-port 1/1    //Create a logical stack port.
[HUAWEI-stack-port1/1] port interface gigabitethernet 1/0/46 enable    //Add a member port to the logical stack port.
```
  After cables are connected, run the display stack command to check whether the stack connection topology is changed to the ring topology.
2. After the stack connection topology changes to ring topology, replace the switch according to Replace one member switch in a stack of two member switches.
3. To restore the stack connection topology to chain topology after the replacement, remove the stack cables connected in step 1.

Changing the Stack ID

Networking Requirements

In Figure 3-40, the stack IDs of stack members are 3, 1, and 2 from top to bottom. These stack IDs need to be planned again based on the location to facilitate device management.

Figure 3-40 Networking diagram

Check information about the stack members with the stack IDs.

<Stack> display stack
Stack mode: Service-port                                                      
Stack topology type: Ring                                                       
Stack system MAC: 00e0-fc00-1234                                                
MAC switch delay time: 10 min                                                    
Stack reserved VLAN: 4093                                                       
Slot of the active management port: 3
Slot    Role        MAC address       Priority   Device type
-------------------------------------------------------------
    3   Master      00e0-fc00-1234   200          
    1   Standby     00e0-fc00-1235   150          
    2   Slave       00e0-fc00-1236   150

The stack IDs need to be changed according to the following rules: After the change, check whether the change is correct based on the MAC addresses of the devices.

Slot 3 → Slot 1
Slot 1 → Slot 2
Slot 2 → Slot 3

To change the stack IDs, you need to restart the devices, which interrupts services. Therefore, perform this operation in a specified period.

Procedure

Shut down the uplink and downlink ports of the stack to isolate the stack from the network.

<Stack> system-view
[Stack] interface gigabitethernet 3/0/8
[Stack-GigabitEthernet3/0/8] shutdown
[Stack-GigabitEthernet3/0/8] quit
[Stack] interface gigabitethernet 1/0/9
[Stack-GigabitEthernet1/0/9] shutdown
[Stack-GigabitEthernet1/0/9] quit
[Stack] interface gigabitethernet 2/0/5
[Stack-GigabitEthernet2/0/5] shutdown
[Stack-GigabitEthernet2/0/5] quit
[Stack] interface gigabitethernet 3/0/6
[Stack-GigabitEthernet3/0/6] shutdown
[Stack-GigabitEthernet3/0/6] quit

After the stack IDs are changed, the configurations of the interfaces with the original stack IDs will be lost. Therefore, you need to perform the same configurations on the new interfaces before changing the stack IDs.

For example: The configurations of the interfaces with the original stack IDs are as follows:

#
interface GigabitEthernet3/0/6
 description ToPC                                                                                                                   
 port link-type access                                                                                                              
 port default vlan 10  
#
interface GigabitEthernet3/0/8
 eth-trunk 10
#
interface GigabitEthernet1/0/9
 eth-trunk 10
#
interface GigabitEthernet2/0/5
 description ToIPPhone-01                                                                                                                   
 port link-type access                                                                                                              
 port default vlan 20  
#

Change the configurations of these interfaces to the configurations of the interfaces with the new stack IDs.

[Stack] interface gigabitethernet 1/0/6  // Correspond to GE3/0/6.
[Stack-GigabitEthernet1/0/6] description ToPC
[Stack-GigabitEthernet1/0/6] port link-type access
[Stack-GigabitEthernet1/0/6] port default vlan 10
[Stack-GigabitEthernet1/0/6] quit
[Stack] interface gigabitethernet 1/0/8  // Correspond to GE3/0/8.
[Stack-GigabitEthernet1/0/8] eth-trunk 10
[Stack-GigabitEthernet1/0/8] quit
[Stack] interface gigabitethernet 2/0/9  // Correspond to GE1/0/9.
[Stack-GigabitEthernet2/0/9] eth-trunk 10
[Stack-GigabitEthernet2/0/9] quit
[Stack] interface gigabitethernet 3/0/5  // Correspond to GE2/0/5.
[Stack-GigabitEthernet3/0/5] description ToIPPhone-01
[Stack-GigabitEthernet3/0/5] port link-type access
[Stack-GigabitEthernet3/0/5] port default vlan 20
[Stack-GigabitEthernet3/0/5] quit

Change the stack IDs, save the configurations, and restart the switches.

[Stack] stack slot 3 renumber 1
Info: The assigned slot ID already exists in the stack system.
Warning: All the configurations related to the slot ID will be lost after the slot ID is modified.
Do not frequently modify the slot ID because it will make the stack split. Continue? [Y/N]:y
Info: Stack configuration has been changed, and the device needs to restart to make the configuration effective.
[Stack] stack slot 1 renumber 2
Info: The assigned slot ID already exists in the stack system.
Warning: All the configurations related to the slot ID will be lost after the slot ID is modified.
Do not frequently modify the slot ID because it will make the stack split. Continue? [Y/N]:y
Info: Stack configuration has been changed, and the device needs to restart to make the configuration effective.
[Stack] stack slot 2 renumber 3
Info: The assigned slot ID already exists in the stack system.
Warning: All the configurations related to the slot ID will be lost after the slot ID is modified.
Do not frequently modify the slot ID because it will make the stack split. Continue? [Y/N]:y
Info: Stack configuration has been changed, and the device needs to restart to make the configuration effective.
[Stack] quit
<Stack> save
The current configuration will be written to flash:/vrpcfg.zip.
Are you sure to continue?[Y/N]y
Now saving the current configuration to the slot 3.........
Save the configuration successfully.
Now saving the current configuration to the slot 1.
Save the configuration successfully.
Now saving the current configuration to the slot 2.
Save the configuration successfully.
<Stack> reboot
Info: The system is now comparing the configuration, please wait...................
Info: If want to reboot with saving diagnostic information, input 'N' and then execute 'reboot save diagnostic-information'.
System will reboot! Continue?[Y/N]:y

After the restart is complete, check whether the stack status, stack IDs, and interface configurations are correct. If the configurations on the interfaces are incorrect, reconfigure the interfaces.

<Stack> display stack
Stack mode: Service-port                                                      
Stack topology type: Ring                                                       
Stack system MAC: xxxx-xxxx-xxx4                                                
MAC switch delay time: 10 min                                                    
Stack reserved VLAN: 4093                                                       
Slot of the active management port: 1
Slot    Role        MAC address       Priority   Device type
-------------------------------------------------------------
    1   Master      xxxx-xxxx-xxx4   200          
    2   Standby     xxxx-xxxx-xxx1   150          
    3   Slave       xxxx-xxxx-xxx2   150

If the configurations are correct, enable the uplink and downlink ports of the stack.

<Stack> system-view
[Stack] interface gigabitethernet 1/0/8
[Stack-GigabitEthernet1/0/8] undo shutdown
[Stack-GigabitEthernet1/0/8] quit
[Stack] interface gigabitethernet 2/0/9
[Stack-GigabitEthernet2/0/9] undo shutdown
[Stack-GigabitEthernet2/0/9] quit
[Stack] interface gigabitethernet 3/0/5
[Stack-GigabitEthernet3/0/5] undo shutdown
[Stack-GigabitEthernet3/0/5] quit
[Stack] interface gigabitethernet 1/0/6
[Stack-GigabitEthernet1/0/6] undo shutdown
[Stack-GigabitEthernet1/0/6] quit

Overview of Stack
Stack Deployment Method and Recommendations
Example for Setting Up a Stack Using Stack Cards (V200R001 and Later Versions)
Example for Setting Up a Stack Using Service Ports (V100R006C05)
Example for Setting Up a Stack Using Service Ports (V200R001 to V200R002)
Example for Setting Up a Stack Using Service Ports(V200R003 and Later Versions)
Example for Establishing a Stack Through Service Port Connections Using Dedicated Stack Cables (V200R011C10 and Later Versions)
Stacked Switch Replacement Guide
Changing the Stack ID

Translation

Español 日本語 Русский 简体中文

Download

Updated: 2023-05-15

Document ID: EDOC1000069520

Downloads: 40473

Average rating:

This Document Applies to these Products

Related Version

Digital Signature File

Digital Signature Authentication Mode

Enterprise

Huawei Cloud

Carrier

Consumer

Corporate

Overview of Stack

Stack Deployment Method and Recommendations

Recommended Stack Deployment Scenarios

Scenario 1: The Stack System Operates on Aggregation Switches

Scenario 2: The Stack System Operates on Access Switches

Scenario 3: The Stack System Operates on an Access Ring

Recommendations

Determining the Stack Topology

Networking for a Stack of More Than Two Member Devices

Networking for a Stack of Two Member Devices

Stack Configuration and Deployment Recommendations

Feature Limitations

Deployment Recommendations

Example for Setting Up a Stack Using Stack Cards (V200R001 and Later Versions)

Networking Requirements

Configuration Roadmap

Procedure

Configuration Files

Example for Setting Up a Stack Using Service Ports (V100R006C05)

Overview

Networking Requirements

Configuration Roadmap

Procedure

Configuration Files

Example for Setting Up a Stack Using Service Ports (V200R001 to V200R002)

Overview

Networking Requirements

Configuration Roadmap

Procedure

Configuration Files

Example for Setting Up a Stack Using Service Ports (V200R003 and Later Versions)

Overview

Networking Requirements

Configuration Roadmap

Procedure

Configuration Files

Example for Establishing a Stack Through Service Port Connections Using Dedicated Stack Cables (V200R011C10 and Later Versions)

Overview

Precautions

Networking Requirements

Configuration Roadmap

Procedure

Configuration Files

Stacked Switch Replacement Guide

Changing the Stack ID

Networking Requirements

Procedure

Related Version

Related Documents

Digital Signature File