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

S7700 and S9700 V200R011C10

This document describes the configuration of Ethernet services, including configuring link aggregation, VLANs, Voice VLAN, VLAN mapping, QinQ, GVRP, MAC table, STP/RSTP/MSTP, SEP, and so on.
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

S7700

S7703, S7706, S7712

V100R003C01, V100R006C00, V200R001(C00&C01), V200R002C00, V200R003C00, V200R005C00, V200R006C00, V200R007C00, V200R008C00, V200R009C00, V200R010C00, V200R011C10

S9700

S9703, S9706, S9712

V200R001(C00&C01), V200R002C00, V200R003C00, V200R005C00, V200R006C00, V200R007(C00&C10), V200R008C00, V200R009C00, V200R010C00, V200R011C10

NOTE:
To know details about software mappings, see Hardware Query Tool.

Feature Limitations

Configuration Guidelines Before an Eth-Trunk Is Configured
  • 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 only when cards with Eth-Trunk specification extension are installed on the switch. 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.
    NOTE:
    • If cards without Eth-Trunk specification extension are installed on the switch, this command cannot be run to change the maximum number of Eth-Trunks that are supported and maximum number of member interfaces in each Eth-Trunk. In this case, the switch supports a maximum of 128 Eth-Trunks with each Eth-Trunk supporting a maximum of eight member interfaces in each Eth-Trunk.

    • Cards are classified into cards with and without Eth-Trunk specification extension depending on the support for the assign trunk command. Cards with Eth-Trunk specification extension are as follows and other cards do not support Eth-Trunk specification extension:

      • S7700: FC series, SC series, EE series, and X series cards

      • S9700: FC series, SC series, EE series, X series, ET1D2X48SEC0, and EH1D2X48SEC0 cards

  • Some commands (such as port link-type access) and static MAC address entries cannot be configured on member interfaces of an Eth-Trunk. Otherwise, errors will be reported.

  • An Eth-Trunk cannot be added to another Eth-Trunk.
  • In earlier versions of V200R011C10, interfaces with different rates cannot join the same Eth-Trunk. In V200R011C10 and later versions, interfaces with different rates can join the same Eth-Trunk by running mixed-rate link enable.

  • 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 on 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 so that the two ends can communicate.
  • Devices on both ends of an Eth-Trunk must use the same link aggregation mode.
  • In V200R008 and earlier versions, the assign trunk command fails to be executed on the device enabled with SVF, and Eth-Trunk specifications can only use the default settings.
  • 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.
  • Before the software version V100R006 is upgraded to any version in the range from V200R001 to V200R011C10, ensure that no Eth-Trunk is established across an ES1D2X40SFC0/ES1D2X16SFC0 board and a non-ES1D2X40SFC0/ES1D2X16SFC0 board. If such an Eth-Trunk exists, traffic forwarding may fail on the Eth-Trunk after the upgrade.

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

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

Switches Are Connected Across a Transmission Device Using Link Aggregation

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

Switches Connect to Transmission Devices Using Link Aggregation

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 Using Link Aggregation

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

    Intel network adapter is used as an example. 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.

Switches Are Connected Through Inter-card Link Aggregation

Interfaces on different cards of a switch can join the same Eth-Trunk, that is, inter-card Eth-Trunk. Interfaces on cards without Eth-Trunk specification extension can constitute an inter-card Eth-Trunk. Before interfaces on a card with Eth-Trunk specification extension and interfaces on another card constitute an inter-card Eth-Trunk, use the eth-trunk load-balance hash-mode command to configure the hash mode for the card with Eth-Trunk specification extension.
  • When interfaces on different cards with Eth-Trunk specification extension form an Eth-Trunk, ensure that the cards use the same hash mode.

  • When interfaces on the card with Eth-Trunk specification extension form an Eth-Trunk with interfaces on the card without Eth-Trunk specification extension, configure the normal hash mode on the card with Eth-Trunk specification extension.

In earlier versions of V200R010C00, only X series cards among cards with Eth-Trunk specification extension support the hash mode configuration. The hash mode on other cards with Eth-Trunk specification extension has a fixed value of advance. In V200R010C00 and later versions, interfaces on only X series cards among cards with Eth-Trunk specification extension can form Eth-Trunks with interfaces on cards without Eth-Trunk specification extension. Interfaces on other cards with Eth-Trunk specification extension cannot form Eth-Trunks with interfaces on cards without Eth-Trunk specification extension.

In V200R010C00 and later versions, cards with Eth-Trunk specification extension support the hash mode configuration. When the hash mode on a card with Eth-Trunk specification extension is set to normal, interfaces on the card with Eth-Trunk specification extension can form an Eth-Trunk with interfaces on the card without Eth-Trunk specification extension.

Configuration Guidelines 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, only 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 modes:

  • Manual
  • LACP

Link aggregation modes supported by the device:

  • Intra-card: Member interfaces of an Eth-Trunk are located on the same card.
  • Inter-card: Member interfaces of an Eth-Trunk are located on different cards.
  • Inter-chassis: Member interfaces of an Eth-Trunk are located on member devices of a CSS.
  • Inter-device: Inter-device link aggregation refers to E-Trunk. E-Trunk allows links between multiple devices to be aggregated based on 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:

  • Based on source MAC addresses of packets
  • Based on destination MAC addresses of packets
  • Based on source IP addresses of packets
  • Based on destination IP addresses of packets
  • Based on the Exclusive-Or result of source and destination MAC addresses of packets
  • Based on the Exclusive-Or result of source and destination IP addresses of packets
  • Enhanced load balancing: based on VLAN IDs and source physical interface numbers for Layer 2, IPv4, IPv6, and MPLS packets
Translation
Download
Updated: 2019-10-18

Document ID: EDOC1000178310

Views: 286913

Downloads: 141

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