No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

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

This document provides examples for configuring features in typical usage scenarios.
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).
Stack Deployment Method and Recommendations

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 5-1.

The following switch models can set up a stack system in this scenario: S6700EI, S6720S-EI, S6720EI, S6720HI, S5700HI, S5710HI, S5710EI, S5700EI, S5700SI, S5720EI, S5720HI, and S5730HI.

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 access devices.

Figure 5-1  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 5-2.

The following switch models can set up a stack system in this scenario: S2720EI, S2750EI, S5700LI, S5700EI, S5710-C-LI, S5710-X-LI, S5720LI, S5720S-LI, S5700SI, S5720SI, S5720S-SI, S5720I-SI, S5700S-LI, S5730SI, S5730S-EI, S6720LI, S6720S-LI, S6720SI, and S6720S-SI.

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

Figure 5-2  Stack system operating on access switches
Scenario 3: The Stack System Operates on an Access Ring

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

The following switch models can set up a stack system in this scenario: S2720EI, S2750EI, S5700LI, S5700EI, S5710-C-LI, S5710-X-LI, S5720LI, S5720S-LI, S5700SI, S5720SI, S5720S-SI, S5720I-SI, S5700S-LI, S5730SI, S5730S-EI, S6720LI, S6720S-LI, S6720SI, and S6720S-SI.

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 5-3  Stack system operating on an access ring
Recommendations
NOTE:

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 5-1  Scenario recommendations

Model

Scenario 1

Scenario 2

Scenario 3

S5700HI, S5710HI, S5710EI, S6700EI

First preferred

Second preferred

Not recommended

S5720EI, S5720HI, S5730HI, S6720EI, S6720S-EI

First preferred

Second preferred

Second preferred

S5700EI, S5700SI

First preferred

First preferred

Second preferred

S5720SI, S5720S-SI, S5720I-SI

Second preferred

First preferred

First preferred

S2720EI, S2750EI, S5700LI, S5720LI, S5720S-LI, S5730SI, S5730S-EI, S6720LI, S6720S-LI, S6720SI, 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 5-4. Table 5-2 compares the two stack topologies in terms of reliability, link bandwidth utilization, and convenience of cable connections.
Figure 5-4  Stack topologies
Table 5-2  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 5-5. In this topology, only one logical stack port exists between the two devices and no loop exists in the stack.
    Figure 5-5  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 5-6. 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 5-6  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 S5720EIs exist in a stack, this stack cannot have MPLS enabled. If member devices in a stack are running MPLS services, adding MPLS-incapable S5720EIs to the stack is not allowed.
  • An S5720HI 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 S5720HIs to set up a stack.
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.
Download
Updated: 2019-04-20

Document ID: EDOC1000069520

Views: 688973

Downloads: 30104

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next