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

Configuration Guide - Ethernet Switching

S1720, S2700, S5700, and S6720 V200R012(C00 and C20)

This document describes the configuration of Ethernet services, including configuring MAC address table, link aggregation, VLANs, VLAN aggregation, MUX VLAN, VLAN termination, Voice VLAN, VLAN mapping, QinQ, GVRP, VCMP, STP/RSTP/MSTP, VBST, SEP, RRPP, ERPS, LBDT, and Layer 2 protocol transparent transmission.
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).
Licensing Requirements and Limitations for Link Aggregation

Licensing Requirements and Limitations for Link Aggregation

Involved Network Elements

Other network elements are not required.

Licensing Requirements

Ethernet link aggregation is a basic feature of a switch and is not under license control.

Version Requirements

Table 3-4  Products and versions supporting link aggregation

Product

Product Model

Software Version

S2700 S2700SI

V100R005C01, V100R006(C00&C01&C03&C05)

S2700EI

V100R005C01, V100R006(C00&C01&C03&C05)

S2710SI

V100R006(C03&C05)

S2720EI

V200R006C10, V200R009C00, V200R010C00, V200R011C10, V200R012C00

S2750EI

V200R003C00, V200R005C00SPC300, V200R006C00, V200R007C00, V200R008C00, V200R009C00, V200R010C00, V200R011C00, V200R011C10, V200R012C00

S3700 S3700SI

V100R005C01, V100R006(C00&C01&C03&C05)

S3700EI

V100R005C01, V100R006(C00&C01&C03&C05)

S3700HI

V100R006C01, V200R001C00

S5700 S5700LI

V200R001C00, V200R002C00, V200R003(C00&C02&C10), V200R005C00SPC300, V200R006C00, V200R007C00, V200R008C00, V200R009C00, V200R010C00, V200R011C00, V200R011C10, V200R012C00

S5700S-LI

V200R001C00, V200R002C00, V200R003C00, V200R005C00SPC300, V200R006C00, V200R007C00, V200R008C00, V200R009C00, V200R010C00, V200R011C00, V200R011C10, V200R012C00

S5710-C-LI

V200R001C00

S5710-X-LI

V200R008C00, V200R009C00, V200R010C00, V200R011C00, V200R011C10, V200R012C00

S5700EI

V100R005C01, V100R006(C00&C01), V200R001(C00&C01), V200R002C00, V200R003C00, V200R005(C00&C01&C02&C03)

S5700SI

V100R005C01, V100R006C00, V200R001C00, V200R002C00, V200R003C00, V200R005C00

S5710EI

V200R001C00, V200R002C00, V200R003C00, V200R005(C00&C02)

S5720EI

V200R007C00, V200R008C00, V200R009C00, V200R010C00, V200R011C00, V200R011C10, V200R012C00

S5720LI, S5720S-LI

V200R010C00, V200R011C00, V200R011C10, V200R012(C00&C20)

S5720SI, S5720S-SI

V200R008C00, V200R009C00, V200R010C00, V200R011C00, V200R011C10, V200R012C00

S5720I-SI

V200R012C00

S5700HI

V100R006C01, V200R001(C00&C01), V200R002C00, V200R003C00, V200R005(C00SPC500&C01&C02)

S5710HI

V200R003C00, V200R005(C00&C02&C03)

S5720HI

V200R006C00, V200R007(C00&C10), V200R008C00, V200R009C00, V200R010C00, V200R011C00, V200R011C10, V200R012C00

S5730HI

V200R012C00

S5730SI

V200R011C10, V200R012C00

S5730S-EI

V200R011C10, V200R012C00

S6700 S6700EI

V100R006C00, V200R001(C00&C01), V200R002C00, V200R003C00, V200R005(C00&C01&C02)

S6720EI

V200R008C00, V200R009C00, V200R010C00, V200R011C00, V200R011C10, V200R012C00

S6720S-EI

V200R009C00, V200R010C00, V200R011C00, V200R011C10, V200R012C00

S6720LI, S6720S-LI

V200R011C00, V200R011C10, V200R012C00

S6720SI, S6720S-SI

V200R011C00, V200R011C10, V200R012C00

S6720HI

V200R012C00

NOTE:

For details about software mappings, visit Hardware Query Tool and search for the desired product model.

For feature support of S1700 series switches, see S1700 Series Enterprise Switches - Specifications.

Feature Limitations

Configuration Notes Before an Eth-Trunk Is Configured
  • An Eth-Trunk contains a maximum of 32 member interfaces on the S5720HI, S5730HI, and S6720HI, 16 member interfaces on the S5730SI, S5730S-EI, S6720LI, S6720S-LI, S6720SI, and S6720S-SI, and 8 member interfaces on all other models.

  • Starting from V200R009, for the S6720EI and S6720S-EI, you can run the assign trunk { trunk-group group-number | trunk-member member-number }* command to configure the maximum number of Eth-Trunks and maximum number of member interfaces in each Eth-Trunk. For details, see the description of the assign trunk command in "Ethernet Switching Configuration Commands" in the Command Reference of the corresponding version. After the configuration, you can run the display trunk configuration command to check the default specifications of the maximum number of Eth-Trunks that are supported and maximum number of member interfaces in each Eth-Trunk, current specifications, and configured specifications.

  • Member interfaces cannot be configured with some services or static MAC address entries. For example, when an interface is added to an Eth-Trunk, the interface must use the default link type.

  • Do not configure any member port of an Eth-Trunk as an observing port. If you must do so, ensure that the bandwidth of service traffic on this port and the bandwidth occupied by the mirrored traffic do not exceed the bandwidth limit of the port.

  • Member interfaces of an Eth-Trunk cannot be an Eth-Trunk.
  • Member interfaces of an Eth-Trunk must use the same Ethernet type. For example, GE electrical and optical interfaces can join the same Eth-Trunk.

  • In versions earlier than V200R011C10, interfaces with different rates cannot join the same Eth-Trunk. In V200R011C10 and later versions, interfaces with different rates can temporarily join the same Eth-Trunk by running the mixed-rate link enable command.

  • When an Eth-Trunk performs load balancing calculation, the interface rate cannot be used as the calculation weight. When interfaces with different rates are added to the same Eth-Trunk, traffic is evenly load balanced among all the links. Therefore, the bandwidth of member interfaces is calculated by the minimum rate of the member interfaces in the Eth-Trunk. For example, when a GE interface and a 10GE interface are added to the same Eth-Trunk, the rate of the GE interface is used in calculation and the bandwidth of the Eth-Trunk is 2G.
  • Both devices of the Eth-Trunk must use the same number of physical interfaces, interface rate, duplex mode, and flow control mode.
  • If an interface of the local device is added to an Eth-Trunk, an interface of the remote device directly connected to the interface of the local device must also be added to the Eth-Trunk. Otherwise, communication between the two devices will fail.
  • Both devices of an Eth-Trunk must use the same link aggregation mode.
  • When the number of active interfaces falls below the lower threshold, the Eth-Trunk goes Down. This ensures that the Eth-Trunk has a minimum available bandwidth.
  • In fiber to the x (FTTx) scenarios of MANs, PPPoE is often used for Internet access. If switches use link aggregation, when traffic is aggregated, ensure that PPPoE packets are load balanced. In such scenarios, the following models are recommended: S5700EI, S5710EI, S5720EI, S5700HI, S5710HI, S5720HI, S5730HI, S5730SI, S5730S-EI, S6700EI, S6720EI, S6720HI, S6720S-EI, S6720SI, S6720S-SI, S6720LI, and S6720S-LI.

In the following scenarios, there are other configuration notes in addition to the preceding ones.

Table 3-5  Configuration notes in different scenarios
Usage Scenario Precaution

Switches Are Connected Across a Transmission Device

  • The switches at both ends must use link aggregation in LACP mode.
  • The transmission device between the switches must be configured to transparently transmit LACPDUs.

Switches Connect to Transmission Devices

  • The link aggregation mode on the transmission device must be the same as that of the switch. Configure the transmission device according to its operation guide.

A Switch Connects to a Server

  • Network adapters of the server must be of the same type.
  • The link aggregation modes on the server and access device must be consistent.

    For example, if an Intel network adapter is used, a server often uses static or IEEE 802.3ad dynamic link aggregation. When the server uses static link aggregation, the access device must use the manual mode. When the server uses IEEE 802.3ad dynamic link aggregation, the access device must use the LACP mode.

  • When a server needs to obtain the configuration file from the remote file server through a switch and link aggregation needs to be used, run the lacp force-forward command on the Eth—Trunk of the switch.
Configuration Notes After an Eth-Trunk Is Configured
  • An Ethernet interface can be added to only one Eth-Trunk. To add an Ethernet interface to another Eth-Trunk, delete it from the original one first.
  • After an interface is added to an Eth-Trunk, the Eth-Trunk learns MAC address entries or ARP entries, but the member interface does not.
  • Before deleting an Eth-Trunk, delete member interfaces from the Eth-Trunk.
Specifications

Link aggregation mode:

  • Manual
  • LACP

    If both devices support LACP, link aggregation in LACP mode is recommended.

Link aggregation modes supported by the device:

  • Intra-device: Member interfaces of an Eth-Trunk are located on the same device.
  • Inter-stack-device: Member interfaces of an Eth-Trunk are located on member devices of a stack.
  • Inter-device: The inter-device link aggregation refers to E-Trunk. E-Trunk allows links between multiple devices to be aggregated using LACP.

Load balancing modes supported by the device:

To prevent data packet mis-sequencing, an Eth-Trunk uses flow-based load balancing.

You can use the following load balancing modes based on actual networking:

  • Source MAC addresses of data frames
  • Destination MAC addresses of data frames
  • Source IP addresses of data frames
  • Destination IP addresses of data frames
  • Exclusive-Or result of source and destination MAC addresses of data frames
  • Exclusive-Or result of source and destination IP addresses of data frames
  • (Enhanced load balancing) VLAN IDs and source physical interface numbers for Layer 2, IPv4, IPv6, and MPLS data frames
Translation
Download
Updated: 2018-12-24

Document ID: EDOC1100038339

Views: 166691

Downloads: 697

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