Licensing Requirements and Limitations for Link Aggregation

S12700 V200R010C00 Configuration Guide - Ethernet Switching

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.

About This Document
Ethernet Switching Overview
- Introduction to Ethernet Switching
- Basic Concepts of Ethernet
- Switching on the Ethernet
  - Layer 2 Switching
  - Layer 3 Switching
- Application Environment
  - Building an Enterprise Network
MAC Address Table Configuration
- Introduction to the MAC Address
- Principles
- Application
- Configuration Task Summary
- Licensing Requirements and Limitations for MAC Address Tables
- Default Configuration
- Configuring a MAC Address Table
- Configuring MAC Address Flapping Prevention
  - Configuring a MAC Address Learning Priority for an Interface
  - Preventing MAC Address Flapping Between Interfaces with the Same Priority
- Configuring MAC Address Flapping Detection
- Configuring the Switch to Discard Packets with an All-0 MAC Address
- Configuring the Switch to Discard Packets That Do Not Match Any MAC Address Entry
- Enabling MAC Address-Triggered ARP Entry Update
- Enabling Port Bridge
- Configuring Re-marking of Destination MAC Addresses
- Maintaining the MAC Address Table
- Configuration Examples
- Common Misconfigurations
  - MAC Address Entries Failed to Be Learned on an Interface
- FAQs
Link Aggregation Configuration
- Introduction to Link Aggregation
- Principles
- Applications
- Configuration Task Summary
- Licensing Requirements and Limitations for Link Aggregation
- Default Settings
- Configuring Link Aggregation in Manual Mode
- Configuring Link Aggregation in LACP Mode
- Configuring Preferential Forwarding of Local Traffic in a CSS
- Creating an Eth-Trunk Sub-interface
- Configuring an E-Trunk
- Maintaining Link Aggregation
- Configuration Examples
- Common Configuration Errors
  - Traffic Is Unevenly Load Balanced Among Eth-Trunk Member Interfaces Because the Load Balancing Mode Is Incorrect
  - Eth-Trunk at Both Ends Cannot Be Up Because the Lower Threshold for the Number of Active Interfaces Is Incorrect
- FAQ
VLAN Configuration
- VLAN Overview
- Principles
- Applications
- Configuration Task Summary
- Licensing Requirements and Limitations for VLANs
- Default Configuration
- Configuring VLAN Technology
- Maintaining VLANs
- Configuration Examples
- Common Misconfigurations
- FAQ
VLAN Aggregation Configuration
- Introduction to VLAN Aggregation
- Principles
- Application Scenario
- Licensing Requirements and Limitations for VLAN Aggregation
- Default Configuration
- Configuring VLAN Aggregation
- Configuration Examples
  - Example for Configuring VLAN Aggregation
- FAQ
  - How Do I Implement Communication Between Specific Sub-VLANs in a Super-VLAN
  - How Should a Traffic Policy Be Configured in a Super-VLAN or Sub-VLAN to Make the Traffic Policy Take Effect
VLAN Switch Configuration
- Introduction to VLAN Switch
- Application Scenario
- Licensing Requirements and Limitations for VLAN Switch
- Default Configuration
- Configuring VLAN Switch
- Maintaining VLAN Switch
- Configuration Examples
  - Example for Implementing Inter-VLAN Communication Using VLAN Switch
MUX VLAN Configuration
- Introduction to MUX VLAN
- Licensing Requirements and Limitations for MUX VLANs
- Default Configuration
- Configuring the MUX VLAN
- Configuration Examples
  - Example for Configuring MUX VLAN on the Access Device
  - Example for Configuring MUX VLAN on the Aggregation Device
VLAN Termination Configuration
- Introduction to VLAN Termination
- Application Scenario
- Configuration Task Summary
- Licensing Requirements and Limitations for VLAN Termination
- Default Configuration
- Using a Dot1q Termination Sub-interface to Implement Inter-VLAN Communication
- Configuring a Dot1q Termination Sub-interface and Connecting It to an L2VPN
- Configuring a Dot1q Termination Sub-interface and Connecting It to an L3VPN
- Configuring a QinQ Termination Sub-interface and Connecting It to an L2VPN
- Configuring a QinQ Termination Sub-interface and Connecting It to an L3VPN
- Configuration Examples
Voice VLAN Configuration
- Introduction to Voice VLAN
- Typical Networking
- Principles
- Applicable Scenario
- Licensing Requirements and Limitations for Voice VLAN
- Default Configuration
- Configuring a MAC Address-based Voice VLAN
- Configuring a VLAN ID-based Voice VLAN
- Configuration Examples
  - Example for Configuring a MAC Address-based Voice VLAN (IP Phones Send Untagged Voice Packets)
  - Example for Configuring a VLAN ID-based Voice VLAN (IP Phones Send Tagged Voice Packets)
QinQ Configuration
- Introduction to QinQ
- Principles
- Applications
  - Public User Services on a Metro Ethernet Network
  - Enterprise Network Connection Through Private Lines
- Configuration Task Summary
- Licensing Requirements and Limitations for QinQ
- Configuring Basic QinQ
- Configuring Selective QinQ
- Configuring the TPID Value in an Outer VLAN Tag
- Configuring the Device to Add Double VLAN Tags to Untagged Packets
- Configuring QinQ Mapping
  - Configuring 1-to-1 QinQ Mapping
  - Configuring 2-to-1 QinQ Mapping
- Maintaining QinQ
  - Displaying VLAN Translation Resource Usage
- Configuration Examples
- Common Misconfigurations
  - QinQ Traffic Forwarding Fails Because the Outer VLAN Is Not Created
  - QinQ Traffic Forwarding Fails Because the Interface Does Not Transparently Transmit the Outer VLAN ID
- FAQ
VLAN Mapping Configuration
- Introduction to VLAN Mapping
- Principles
- Applications
- Licensing Requirements and Limitations for VLAN Mapping
- Configuring VLAN ID-based VLAN Mapping
- Configuring 802.1p Priority-based VLAN Mapping
- Configuring MQC-based VLAN Mapping
- Maintaining VLAN Mapping
  - Displaying VLAN Translation Resource Usage
- Configuration Examples
- Common Configuration Errors
  - Communication Failure After VLAN Mapping Configuration
GVRP Configuration
- Introduction to GVRP
- Principles
- Applications
- Licensing Requirements and Limitations for GVRP
- Default Configuration
- Configuring GVRP
- Maintaining GVRP
  - Clearing GVRP Statistics
- Configuration Examples
  - Example for Configuring GVRP
- FAQ
  - Why Is the CPU Usage High When VLANs Are Created or Deleted Through GVRP in Default Configuration?
VCMP Configuration
- Introduction to VCMP
- Principles
  - VCMP Concepts
  - Implementation
- Applicable Scenario
- Licensing Requirements and Limitations for VCMP
- Default Configuration
- Configuring VCMP
- Maintaining VCMP
  - Displaying VCMP Running Information
  - Clearing VCMP Running Information
- Configuration Examples
  - Example for Configuring VCMP to Implement Centralized VLAN Management
STP/RSTP Configuration
- Introduction to STP/RSTP
- Principles
- Applications
- Configuration Task Summary
- Licensing Requirements and Limitations for STP/RSTP
- Default Configuration
- Configuring Basic STP/RSTP Functions
- Setting STP Parameters that Affect STP Convergence
- Setting RSTP Parameters that Affect RSTP Convergence
- Configuring RSTP Protection Functions
- Setting Parameters for Interoperation Between Huawei and Non-Huawei Devices
- Maintaining STP/RSTP
  - Clearing STP/RSTP Statistics
  - Monitoring STP/RSTP Topology Change Statistics
- Configuration Examples
  - Example for Configuring Basic STP Functions
  - Example for Configuring Basic RSTP Functions
- FAQ
MSTP Configuration
- Introduction to MSTP
- MSTP Principles
- Application Environment
- Configuration Task Summary
- Licensing Requirements and Limitations for MSTP
- Default Configuration
- Configuring Basic MSTP Functions
- Configuring MSTP Multi-Process
- Configuring MSTP Parameters on an Interface
- Configuring MSTP Protection Functions
- Configuring MSTP Interoperability Between Huawei and Non-Huawei Devices
- Maintaining MSTP
  - Clearing MSTP Statistics
  - Monitoring the Statistics on MSTP Topology Changes
- Configuration Examples
- FAQ
VBST Configuration
- Introduction to VBST
- Principles
- Applicable Scenario
- Configuration Task Summary
- Licensing Requirements and Limitations for VBST
- Default Configuration
- Configuring Basic VBST Functions
- Setting VBST Parameters That Affect VBST Convergence
- Configuring Protection Functions of VBST
- Setting Parameters for Interworking Between a Huawei Datacom Device and a Non-Huawei Device
- Maintaining VBST
  - Displaying VBST Running Information and Statistics
  - Clearing VBST Statistics
- Configuration Examples
  - Example for Configuring VBST
SEP Configuration
- Introduction to SEP
- Principles
- Applications
- Configuration Task Summary
- Licensing Requirements and Limitations for SEP
- Configuring Basic SEP Functions
- Specifying an Interface to Block
- Configuring SEP Multi-Instance
- Configuring the Topology Change Notification Function
- Maintaining SEP
  - Clearing SEP Statistics
- Configuration Examples
RRPP Configuration
- Introduction to RRPP
- Principles
- Application Scenarios
- Configuration Task Summary
- Licensing Requirements and Limitations for RRPP
- Default Configuration
- Configuring RRPP
- Configuring RRPP Snooping
- Maintaining RRPP
  - Clearing RRPP Statistics
- Configuration Examples
- Common Configuration Errors
  - A Loop Occurs After the RRPP Configuration is Complete
  - After the Primary Port of a Transit Node on an RRPP Ring Network Becomes Down and Then Recovers, the Transit Node and Other Transit Nodes Cannot Register With the Master Node
- FAQ
ERPS (G.8032) Configuration
- Introduction to ERPS
- Principles
- Applicable Scenario
- Configuration Task Summary
- Licensing Requirements and Limitations for ERPS
- Default Settings
- Configuring ERPSv1
- Configuring ERPSv2
- Maintaining ERPS
  - Clearing ERPS Statistics
- Configuration Examples
  - Example for Configuring ERPS Multi-instance
  - Example for Configuring Intersecting ERPS Rings
- Common Configuration Errors
  - Traffic Forwarding Fails in an ERPS Ring
LDT and LBDT Configuration
- Introduction to LBDT and LDT
- Principles
- Applicable Scenario
- Licensing Requirements and Limitations for LDT and LBDT
- Default Configuration
- Configuring LDT to Detect Loops
- Configuring Automatic LBDT
- Configuring Manual LBDT
- Configuration Examples
Layer 2 Protocol Transparent Transmission Configuration
- Introduction to Layer 2 Protocol Transparent Transmission
- Principles
- Application Environment
- Configuration Task Summary
- Licensing Requirements and Limitations for Layer 2 Protocol Transparent Transmission
- Configuring Interface-based Layer 2 Protocol Transparent Transmission
- Configuring VLAN-based Layer 2 Protocol Transparent Transmission
- Configuring QinQ-based Layer 2 Protocol Transparent Transmission
- Configuration Examples
- FAQ

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

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
S12700	S12708, S12712	V200R005C00, V200R006C00, V200R007C00, V200R007C20, V200R008C00, V200R009C00, V200R010C00, V200R011C10
	S12710	V200R010C00, V200R011C10
	S12704	V200R008C00, V200R009C00, V200R010C00, V200R011C10

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.
- 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:
  
  S12700: SC series, EE series, X series, and ET1D2X48SEC0 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.

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: 2022-05-23

Document ID: EDOC1000142081

Downloads: 894

Average rating:

This Document Applies to these Products

Related Version

Digital Signature File

Digital Signature Authentication Mode

Enterprise

Huawei Cloud

Carrier

Consumer

Corporate