Contents

3  Eth-Trunk Interface Configuration

3.1  Eth-Trunk Interface Introduction

3.1.1  Introduction to the Eth-Trunk Interface

3.1.2  Eth-Trunk Interface Features Supported by the NE80E/40E

3.2  Configuring an Eth-Trunk Interface in Manual Load Balancing Mode

3.2.1  Establishing the Configuration Task

3.2.2  Creating an Eth-Trunk

3.2.3  (Optional) Configuring Working Mode of an Eth-Trunk Interface

3.2.4  Configuring the Operation Mode of the Eth-Trunk as the Manual Load Balancing Mode

3.2.5  Adding Member Interfaces to the Eth-Trunk

3.2.6  Checking the Configuration

3.3  Configuring an Eth-Trunk Interface in 1:1 Active/Standby Mode

3.3.1  Establishing the Configuration Task

3.3.2  Configuring the Operation Mode of the Eth-Trunk as 1:1 Active/Standby Mode

3.3.3  Adding Member Interfaces to the Eth-Trunk and Setting the Primary Interface

3.3.4  Enabling an LAG to Send Flush Packets

3.3.5  Creating a Control VLAN

3.3.6  Enabling an Interface to Receive Packets from the Control VLAN

3.3.7  Enabling an Interface to Receive Flush Packets

3.3.8  Checking the Configuration

3.4  Configuring an Eth-Trunk Interface in Static LACP Mode

3.4.1  Establishing the Configuration Task

3.4.2  Creating an Eth-Trunk

3.4.3  (Optional) Configuring Working Mode of an Eth-Trunk Interface

3.4.4  Configuring the Operation Mode of the Eth-Trunk as the Static LACP Mode

3.4.5  Adding Member Interfaces to the Eth-Trunk

3.4.6  (Optional) Setting the LACP Priority of the System

3.4.7  (Optional) Setting the Upper Threshold for the Number of Active Interfaces

3.4.8  (Optional) Setting the LACP Priority of the Interface

3.4.9  (Optional) Configuring the Mode for Selecting Active Interfaces in an Eth-Trunk Interface

3.4.10  (Optional) Enabling LACP Preemption and Setting the Delay for LACP Preemption

3.4.11  (Optional) Setting the Timeout Period for Receiving LACP Protocol Packets

3.4.12  Checking the Configuration

3.5  Configuring Layer 2 Attributes for an Eth-Trunk Interface

3.5.1  Establishing the Configuration Task

3.5.2  (Optional) Configuring the Lower Threshold of Up Links

3.5.3  (Optional) Configuring the Upper Threshold of Up Links

3.5.4  (Optional) Configuring an Eth-Trunk Interface to Carry out Load Balancing

3.5.5  (Optional) Configuring Weights for Member Links

3.5.6  (Optional) Configuring the Method of Sending Traps on Eth-Trunk Member Interfaces

3.5.7  Checking the Configuration

3.6  Configuring Layer 3 Attributes for an Eth-Trunk Interface

3.6.1  Establishing the Configuration Task

3.6.2  Configuring an IP address for an Eth-Trunk Interface

3.6.3  (Optional) Configuring a MAC Address for the Eth-Trunk Interface

3.6.4  (Optical) Configuring the MTU for an Eth-Trunk interface

3.6.5  (Optional) Configuring the Lower Threshold of Up Links

3.6.6  (Optional) Configuring Load-balancing Mode for the Eth-Trunk Interface

3.6.7  (Optional) Configuring Weights for Member Links

3.6.8  (Optional) Configuring the Method of Sending Traps on Eth-Trunk Member Interfaces

3.6.9  Checking the Configuration

3.7  Configuring an Eth-Trunk Sub-interface

3.7.1  Establishing the Configuration Task

3.7.2  Creating an Eth-Trunk Sub-interface

3.7.3  Configuring an IP address for an Eth-Trunk Sub-interface

3.7.4  Configuring the Encapsulation Type for an Eth-Trunk Sub-interface

3.7.5  (Optical) Configuring the MTU for an Eth-Trunk Sub-interface

3.7.6  (Optional) Configuring the Rate for Sending Gratuitous ARP packets on an Eth-Trunk Sub-interface

3.7.7  Checking the Configuration

3.8  Configuring an E-Trunk

3.8.1  Establishing the Configuration Task

3.8.2  Configuring the LACP System ID and Priority of the E-Trunk

3.8.3  Creating an E-Trunk and Configuring Its Priority

3.8.4  Configuring Local and Peer IP Addresses

3.8.5  Binding the E-Trunk to the BFD Session

3.8.6  Adding an Eth-Trunk to an E-Trunk

3.8.7  (Optional) Configuring the Operation Mode of the Eth-Trunk

3.8.8  (Optional) Configuring the Password

3.8.9  (Optional) Configuring the Timeout Period

3.8.10  (Optional) Setting the Revert Delay

3.8.11  Checking the Configuration

3.9  Maintaining Eth-Trunk Interface

3.9.1  Clearing the Statistics of Eth-Trunk Interface

3.10  Configuration Examples

3.10.1  Example for Configuring Eth-Trunk interfaces in Manual Load Balancing Mode

3.10.2  Example for Configuring Eth-Trunk interfaces in 1:1 Active/Standby Mode

3.10.3  Example for Configuring Eth-Trunk interfaces in Static LACP Mode

3.10.4  Example for Configuring a Layer 2 Eth-Trunk Interface to Allow VLANs to Pass Through

3.10.5  Example for Configuring a Layer 3 Eth-Trunk Interface in Manual Load Balancing Mode

3.10.6  Example for Configuring VLANs to Communicate Through Eth-Trunk Sub-interfaces

3.10.7  Example for Connecting an E-Trunk to a VPLS Network

Figures

Figure 3-1  Determining the active links by the Actor in static LACP mode

Figure 3-2  Typical application of the Layer 2 Eth-Trunk interface (Eth-Trunk ring network)

Figure 3-3  Networking diagram of link aggregation in manual load balancing mode

Figure 3-4  Networking diagram of link aggregation in 1:1 active/standby mode

Figure 3-5  Networking diagram of link aggregation in static LACP mode

Figure 3-6  Networking diagram of the E-Trunk

Figure 3-7  Networking diagram of link aggregation in manual load balancing mode

Figure 3-8  Networking diagram of configuring link aggregation in 1:1 active/standby mode

Figure 3-9  Networking diagram of link aggregation in static LACP mode

Figure 3-10  Configuring a Layer 2 Eth-Trunk interface to allow VLAN frames to pass through

Figure 3-11  Networking diagram of configuring a Layer 3 Eth-Trunk interface

Figure 3-12  Networking diagram of configuring VLANs to communicate through Eth-Trunk sub-interfaces

Figure 3-13  Networking diagram of the E-Trunk

3  Eth-Trunk Interface Configuration

Describes the fundamentals, the configuration procedures and the configuration examples of Trunk interfaces and LACP.

3.1  Eth-Trunk Interface Introduction

Describes basic concepts of Eth-Trunk Interface.

3.1.1  Introduction to the Eth-Trunk Interface

Eth-Trunk Interface

Trunk interfaces are classified into Eth-Trunk interfaces and IP-Trunk interfaces. The Eth-Trunk consists of Ethernet links only. For details of IP-Trunk interface configuration, refer to the HUAWEI NetEngine80E/40E Router configuration Guide - WAN Access.

A maximum of 64 trunk interfaces (including Eth-Trunk and IP-Trunk) can be created on a router, and each trunk interface contains up to 16 physical member links.

The trunk technology has the following advantages:

  • Increasing bandwidth: The bandwidth of an Eth-Trunk interface is the sum of all the bandwidth of member interfaces.

  • Improving reliability: If a member link fails, the traffic automatically switches to another available links.

An Eth-Trunk interface has the following characteristics:

  • Supports the features supported by the Ethernet interface.

  • Supports the configured IP addresses, and member trunk interfaces can borrow the IP address.

  • Supports Layer 2 forwarding, MPLS forwarding, and Layer 3 forwarding including unicast and multicast. The Hash algorithm can be used in load balancing by flow.

  • Supports QoS based on physical interfaces and logical interfaces.

  • Supports MPLS and binding VPN instances.

  • Supports hot backup and hot swap.

  • Supports APDP.

NOTE:

Eth-Trunk sub-interfaces are used between VLANs. For the configuration of Eth-Trunk sub-interfaces, refer to the chapter "VLAN Configuration" in this manual.

LACP

Link aggregation refers to a method of binding a group of physical interfaces as a logical interface to increase the bandwidth. Link aggregation is called multi-interface load balancing group or link aggregation group (LAG). For more information about link aggregation, refer to IEEE802.3ad.

By setting up an LAG between two devices, you can obtain higher bandwidth and greater reliability. The link aggregation provides redundancy protection for communications among devices without upgrading the hardware.

  • Active and Inactive Interfaces

    The interfaces in the active state that are responsible for forwarding data are active interfaces. On the contrary, the interfaces in the inactive state that do not forward data are inactive interfaces. According to the operation modes, active and inactive interfaces are classified as follows:

    • Manual load balancing mode: Generally, all member interfaces are active ones unless a fault occurs on these interfaces.

    • 1:1 active/standby mode: Normally, the primary interface is the active interface and the backup interface is the inactive interface. When the primary interface fails, the backup interface is activated and the primary interface becomes the inactive interface.

    • Static LACP mode: The interfaces connected to M links are active interfaces. The active interfaces are responsible for forwarding data. The interfaces connected to N links are inactive interfaces. The inactive interfaces are responsible for backup.

  • Actor and Partner

    In static LACP mode, the device with a higher LACP priority at both ends of an LAG is the Actor and the device with a lower LACP priority is the Partner.

    Differentiating the Actor and the Partner is to keep the active interfaces of devices at both ends the same. If devices at both ends select active interfaces according to the priority of their own interfaces, the active interfaces are different and the active links cannot be set up. Therefore, the Actor is first determined. The Partner selects active interfaces according to the priority of the interfaces of the Actor, as shown in Figure 3-1.

Figure 3-1  Determining the active links by the Actor in static LACP mode

  • Control VLAN

    In 1:1 active/standby mode, the VLAN that sends or receives flush packets is the control VLAN.

3.1.2  Eth-Trunk Interface Features Supported by the NE80E/40E

Lower and Upper Threshold for the Number of Up Links

The number of trunk member links in the Up state affects the status and bandwidth of the Eth-Trunk interface. To maintain stability, you can set the threshold to limit the number of trunk member interfaces in the Up state, and thus to reduce the impact brought about by the status change of member interfaces.

  • Lower threshold for the number of Up links: When the number of Up member links is less than the threshold, the Eth-Trunk interface becomes Down.

  • Upper threshold for the number of Up links: When the number of Up member links reaches the threshold, the increasing of UP member links does not affect the bandwidth of the trunk interface. That is, the bandwidth of the trunk does not increase; however, when member link becomes Down, the bandwidth of the trunk decreases.

Load Balancing

In an Eth-Trunk, member interfaces can balance the traffic after they are set with different weights.

Load balancing can be carried out in the following ways:

  • Session-by-session load balancing: The packets with the same source and destination IP addresses or with the same source and destination MAC addresses pass through the same member link.

    Layer 2 Eth-Trunk interfaces support only session-by-session load balancing based on the source and destination MAC addresses of packets.

    Layer 3 Eth-Trunk interfaces support only session-by-session load balancing based on the source and destination IP addresses of packets.

  • Packet-by-packet load balancing: One packet travels on one link and the next packet is sent out on another link.

    Both Layer 2 and Layer 3 Eth-Trunk interfaces support packet-by-packet load balancing.

Backup

To improve the reliability of an Eth-Trunk interface, you can configure backup interfaces for member interfaces.

When one interface in the Eth-Trunk group becomes Down, the traffic rapidly switches to other interfaces in the Eth-Trunk group. That is, other Up interfaces in the Eth-Trunk group function as the auxiliary interfaces.

NOTE:

For the trunk whose member interfaces reside on different LPUs, you should create a BFD session to detect the link between member interfaces of the trunk, and use the process-pst command to associate the BFD session with the status of the interface. Otherwise, the traffic may be lost in some situations. For example, the LPU where the member interface of the trunk resides is restarted.

For the configuration of BFD, refer to the Configuration Guide - Reliability.

Eth-Trunk Sub-interfaces

Besides on the Eth-Trunk main interface, in the NE80E/40E, sub-interfaces can be created on both the Layer 3 Ethernet interface and the Layer 2 Eth-Trunk interface.

After Eth-Trunk sub-interface is encapsulated with 802.1Q and associated with VLAN, the VLAN can communicate with devices out of VLAN through Eth-Trunk sub-interfaces.

The Eth-Trunk sub-interface is also used in dot1q termination and QinQ termination mode. For details about the principle, see the chapter "QinQ Configuration" in this manual.

Besides the preceding applications, the Layer 2 Eth-Trunk sub-interface transmits the Layer 2 and Layer 3 services simultaneously along one physical link. As shown in Figure 3-2, the backbone of the MAN is a Layer 2 Eth-Trunk ring network that supports QinQ services. On the Eth-Trunk ring network, each NE80E/40E node is connected to a Layer 2 ring network comprising several switches. The digital subscriber line access multiplexer (DSLAM) devices connect to switches and access the roadband remote access servers (BRASs) through VLAN mapping over the Layer 2 ring network and the Eth-Trunk network. For the successful implementation of the application , the entire Eth-Trunk ring network needs to support Layer 2 functions.

At the same time, CEs can access the NE80E/40E and L3VPN services through the TE tunnel. This requires the Layer 2 interfaces of the NE80E/40Es forming an Eth-Trunk ring network can support the TE tunnel of Layer 3 interfaces simultaneously.

Then, you can use a Layer-2 Eth-Trunk sub-interface. Thus, the main interface of the Eth-Trunk ring network performs Layer 2 functions and Layer 2 Eth-Trunk sub-interfaces perform MPLS TE functions.

Figure 3-2  Typical application of the Layer 2 Eth-Trunk interface (Eth-Trunk ring network)

Manual Load Balancing Mode

In manual load balancing mode, you can manually add member interfaces to an LAG. All interfaces transmit packets. The manual load balancing mode that the NE80E/40E supports is IP, MAC, and Packet-all. IP and MAC are applicable to the flow-based load balancing and Packet-all to the packet-based load balancing.

Manual 1:1 Active/Standby Mode

In 1:1 active/standby mode, an LAG contains only two member interfaces. One interface is the primary interface and the other is the backup interface.

In manual mode, you must manually set up an Eth-Trunk and add an interface to the Eth-Trunk. You must also manually configure member interfaces to be in the active state. The Link Aggregation Control Protocol Date Units (LACPDUs) are not required.

The manual load balancing mode is used when the peer device does not support Link Aggregation Control Protocol (LACP).

Static LACP Mode

Static LACP mode refers to a link aggregation method that determines active and inactive interfaces by negotiating parameters through LACPDUs. In static LACP mode, you must manually set up an Eth-Trunk and determine active and inactive interfaces by negotiating parameters through LACPDUs.

Static LACP mode is also called M: N mode. In static LACP mode, load balancing and backup are carried out. In an LAG, M links are active to forward data and perform load balancing. In addition, the other N links are inactive. The N links function as backup links and do not forward data. When a link of M links fails, the system selects the link with the highest priority from N backup links to replace the faulty link. At the same time, the link becomes active and starts to forward data.

3.2  Configuring an Eth-Trunk Interface in Manual Load Balancing Mode

Describes how to create an Eth-Trunk interface in Manual Load Balancing Mode.

3.2.1  Establishing the Configuration Task

Applicable Environment

To improve the communication ability of links, bind multiple Ethernet ports to form an Eth-Trunk interface to increase bandwidth.

Eth-Trunk interfaces can realize load balancing. Traffic to the same destination is transported on different member links to avoid congestion.

In addition, Eth-Trunk interfaces can improve link reliability. If a member port is Down, traffic is switched to other available ports.

When the bandwidth or the reliability of two devices should be increased and one of the two devices does not support LACP, you should create an Eth-Trunk in manual load balancing mode on the Router and add multiple member interfaces to increase the bandwidth and reliability of devices.

As shown in Figure 3-3, RouterA supports LACP, but RouterB does not support LACP.

NOTE:

In manual load balancing mode, member interfaces with different speeds and duplex modes, and on different boards, can be aggregated to an Eth-Trunk.

Figure 3-3  Networking diagram of link aggregation in manual load balancing mode

Pre-configuration Tasks

Before creating an Eth-Trunk interface, complete the task of powering on the Router or switch and starting it normally

Data Preparation

To create an Eth-Trunk interface in manual load balancing mode, you need the following data.

No.

Data

1

Eth-Trunk ID

2

Type and number of Eth-Trunk member ports

3.2.2  Creating an Eth-Trunk

Context

Do as follows on the routers where Eth-Trunk interface needs to be configured.

Procedure

  1. Run:
    system-view

    The system view is displayed.

  2. Run:
    interface eth-trunk trunk-id

    An Eth-Trunk is created.

3.2.3  (Optional) Configuring Working Mode of an Eth-Trunk Interface

Procedure

  1. Run:
    system-view

    The system view is displayed.

  2. Run:
    interface eth-trunk trunk-id

    The Eth-Trunk interface view is displayed.

  3. Run:
    portswitch

    The Layer 3 Eth-Trunk interface is converted to a Layer 2 interface.

    By default, an Eth-Trunk interface operates in Layer 3 mode.

    After an Eth-Trunk interface is switched to Layer 2 mode, its Layer 3 functions are disabled, and its MAC address is adopted.

    To add an Eth-Trunk interface into a VLAN, switch the interface from Layer 3 mode to Layer 2 mode. Before the switching, delete all configurations on the interface.

    Using the undo portswitch command, you can switch a Layer 2 Eth-Trunk interface to Layer 3 mode.

    NOTE:
    • The minimum interval for running the portswitch and undo portswitch commands continually is 30 seconds.

    • The working mode of an Eth-Trunk interface does not affect the addition of member interfaces, for example, an Ethernet interface can join either a Layer 2 Eth-Trunk or a Layer 3 Eth-Trunk interface.

3.2.4  Configuring the Operation Mode of the Eth-Trunk as the Manual Load Balancing Mode

Context

NOTE:

Ensure that an Eth-Trunk does not contain any member interface before you configure the operation mode of the Eth-Trunk; otherwise, the operation mode of the Eth-Trunk cannot be changed. Run the undo eth-trunk trunk-id command in the interface view to delete the existing member interfaces.

Both Layer 2 and Layer 3 Eth-Trunk interfaces support the manual load balancing mode.

Do as follows on the routers at both ends:

Procedure

  1. Run:
    system-view

    The system view is displayed.

  2. Run:
    interface eth-trunk trunk-id

    The Eth-Trunk interface view is displayed.

  3. Run:
    mode manual load-balance

    The operation mode is configured as the manual load balancing mode for the Eth-Trunk.

    By default, an Eth-Trunk works in manual load balancing mode.

3.2.5  Adding Member Interfaces to the Eth-Trunk

Procedure

  • Configuration in the Eth-Trunk Interface View
    1. Run:
      system-view

      The system view is displayed.

    2. Run:
      interface eth-trunk trunk-id

      The Eth-Trunk interface view is displayed.

    3. Run the following command as required.
      • trunkport interface-type { interface-number1 [ to interface-number2 ] } &<1-16>

        The member interfaces are added in batches.

      • trunkport interface-type interface-number

        A member interface is added.

      When you specify the range of member interfaces, you can add or delete a maximum of 16 member interfaces once.

  • Configuration in the Member Interface View
    1. Run:
      system-view

      The system view is displayed.

    2. Run:
      interface { ethernet | gigabitethernet } interface-number

      The view of the interface to be added to the Eth-Trunk is displayed.

    3. Run:
      eth-trunk trunk-id

      The current interface is added into the Eth-Trunk.

      Before adding member interfaces, note the following:

      • Each Eth-Trunk interface can contain up to 16 physical member links.

      • Ensure the interfaces are not configured with Layer 3 configuration such as IP address, and any services.

      • Member interfaces cannot be configured with static MAC addresses.

      • Member interfaces of an Eth-Trunk cannot be Eth-Trunk.

      • An Ethernet interface can join only one Eth-Trunk interface. To join another Eth-Trunk interface, the interface must quit from the original Eth-Trunk first.

      • Fast Ethernet and Gigabit Ethernet interfaces can be added to the same Eth-Trunk.

      • Ethernet interfaces of different interface boards can be added into an Eth-Trunk.

      • For a router, if a member interface is a Layer 2 interface, the interface can be added into an Eth-Trunk only after it is switched to a Layer 3 interface by using the undo portswitch command.

      • Eth-Trunk has two working modes: Layer 2 mode and Layer 3 mode. An Ethernet port can be added into either a Layer 2 Eth-Trunk or a Layer 3 Eth-Trunk.

      • If an Eth-Trunk is created on a local device, the peer device interfaces that are directly connected with the member interfaces must be bound to an Eth-Trunk interface. Otherwise, the two ends cannot communicate.

3.2.6  Checking the Configuration

Prerequisite

The configurations of an Eth-Trunk interface in manual load balancing mode are complete.

Procedure

  1. Run the display trunkmembership eth-trunk trunk-id command to check information about Eth-Trunk member interfaces.

Example

Run the display trunkmembership eth-trunk command. If information about usage state of member interfaces, network protocol status, and link status is displayed, it means that the configuration succeeds. For example:

<HUAWEI> display trunkmembership eth-trunk 1
Trunk ID: 1
used status: VALID
TYPE: ethernet
Working Mode : Normal
Working State: Normal
Number Of Ports in Trunk = 2
Number Of UP Ports in Trunk = 2
operate status: up

Interface GigabitEthernet1/0/0, valid, operate up, weight=1,
Interface GigabitEthernet1/0/1, valid, operate up, weight=1,

3.3  Configuring an Eth-Trunk Interface in 1:1 Active/Standby Mode

Describes how to configure an Eth-Trunk interface in 1:1 active/standby mode.

3.3.1  Establishing the Configuration Task

Applicable Environment

As shown in Figure 3-4, RouterA and RouterD are NE80E/40E devices. The transit device can receive flush packets. The reliability of data transmission from RouterA to RouterD should be implemented through primary and backup links.

Figure 3-4  Networking diagram of link aggregation in 1:1 active/standby mode

NOTE:

In 1:1 active/standby mode, member interfaces of different rates and duplex modes, and on different boards, can be added to an Eth-Trunk.

Pre-configuration Tasks

Before configuring link aggregation in 1:1 active/standby mode, complete the following task:

  • Creating an Eth-Trunk interface

Data Preparation

To configure link aggregation in 1:1 active/standby mode, you need the following data.

No.

Data

1

ID of the LAG of RouterA and RouterD

2

Type and number of the member interface

3

ID of the control VLAN that sends or receives flush packets

3.3.2  Configuring the Operation Mode of the Eth-Trunk as 1:1 Active/Standby Mode

Context

NOTE:

Ensure that an Eth-Trunk does not contain any member interface before you configure the operation mode of the Eth-Trunk; otherwise, the operation mode of the Eth-Trunk cannot be changed. Run the undo eth-trunk command in the interface view to delete the existing member interfaces. For details, refer to the chapter "Link Aggregation" in the Command Reference.

Layer 2 Eth-Trunk interfaces support the 1:1 active/standby mode, but Layer 3 Eth-Trunk interfaces do not support the 1:1 active/standby mode.

Do as follows on RouterA and RouterD:

Procedure

  1. Run:
    system-view

    The system view is displayed.

  2. Run:
    interface eth-trunk trunk-id

    The Eth-Trunk interface view is displayed.

  3. Run:
    portswitch

    The Eth-Trunk interface switches from Layer 3 mode to Layer 2 mode.

  4. Run:
    mode manual backup

    The operation mode is configured as manual 1:1 active/standby mode for the Eth-Trunk.

    By default, an Eth-Trunk works in manual load balancing mode.

3.3.3  Adding Member Interfaces to the Eth-Trunk and Setting the Primary Interface

Context

Do as follows on RouterA and RouterD:

Procedure

  1. Run:
    system-view

    The system view is displayed.

  2. Run:
    interface interface-type interface-number

    The interface view is displayed.

    The interface mentioned here is the member interface that need be added to an Eth-Trunk.

  3. Run:
    eth-trunk trunk-id

    The interface is added to the Eth-Trunk.

    In 1:1 active/standby mode, only two interfaces can be added to the same Eth-Trunk.

    NOTE:

    Ensure that no configuration exists on an interface when the interface is added to an Eth-Trunk. You can run the display this command to check whether there are configurations on the interface. If there are configurations on the interface, you can reserve only the configurations of shutdown, undo shutdown, and description. Other configurations, however, must be deleted through the commands. You can then add the interface to the Eth-Trunk.

  4. Run:
    port-master

    The member interface of the Eth-Trunk is specified as the primary interface.

    By default, the member interface of an Eth-Trunk is the backup interface in 1:1 active/standby mode. Therefore, you need specify only the primary interface.

    You can specify only one primary interface.

3.3.4  Enabling an LAG to Send Flush Packets

Context

Do as follows on RouterA and RouterD:

Procedure

  1. Run:
    system-view

    The system view is displayed.

  2. Run:
    interface eth-trunk trunk-id

    The Eth-Trunk interface view is displayed.

  3. Run:
    smart-link flush send vlan vlan-id

    The LAG is enabled to send flush packets.

    NOTE:

    The VLAN is the control VLAN. After the command is used, when the switchover between master and slave interfaces is performed, flush packets are sent from the new master interface to notify the peer end of aging MAC addresses. In this manner, data transmission interruption that is caused by different MAC addresses can be avoided.

3.3.5  Creating a Control VLAN

Context

Do as follows on RouterB and RouterC:

Procedure

  1. Run:
    system-view

    The system view is displayed.

  2. Run:
    vlan vlan-id

    A VLAN is created and the VLAN view is displayed.

    The VLAN is used to receive flush packets sent by RouterA or RouterD, so the ID of the VLAN should be the same as the ID of the VLAN that sends flush packets.

3.3.6  Enabling an Interface to Receive Packets from the Control VLAN

Context

Do as follows on the interfaces connected to primary links and backup links of RouterB and RouterC:

Procedure

  1. Run:
    system-view

    The system view is displayed.

  2. Run:
    interface interface-type interface-number

    The interface view is displayed.

  3. Run:
    portswitch

    The Ethernet interface switches from Layer 3 mode to Layer 2 mode.

  4. Run:
    port trunk allow-pass vlan { { vlan-id1 [ to vlan-id2 ] } & <1-10> | all }

    The interface is enabled to receive packets from the control VLAN.

    The ID of the VLAN that receives flush packets should be the same as the ID of the VLAN that sends flush packets.

3.3.7  Enabling an Interface to Receive Flush Packets

Context

Do as follows on the interfaces connected to primary links and backup links of RouterB and RouterC:

Procedure

  1. Run:
    system-view

    The system view is displayed.

  2. Run:
    interface interface-type interface-number

    The interface view is displayed.

  3. Run:
    smart-link flush enable control-vlan vlan-id

    The interface is enabled to recevie flush packets.

3.3.8  Checking the Configuration

Prerequisite

The configurations of an Eth-Trunk interface in 1:1 active/standby mode function are complete.

Procedure

  • Run the display trunkmembership eth-trunk trunk-id command to check the member interface of an Eth-Trunk.
  • Run the display eth-trunk [ trunk-id [ interface interface-type interface-number ] ] command to check the operation mode of the Eth-Trunk, primary interface, and backup interface.

Example

Take RouterA as an example. Run the display trunkmembership eth-trunk command. If the current operation mode is Backup and if the primary interface GE1/0/1 is Up, it means that the configuration succeeds.

<RouterA> display trunkmembership eth-trunk 1
Trunk ID: 1
used status: VALID
TYPE: ethernet
Working Mode : Backup-access
Number Of Ports in Trunk = 2
Number Of UP Ports in Trunk = 1
operate status: up

Interface GigabitEthernet1/0/1, valid, operate up, weight=1,
Interface GigabitEthernet1/0/2, valid, operate down, weight=1,
<RouterA> display eth-trunk 1
 Eth-Trunk1's state information is:
 WorkingMode: BACKUP
 WorkingState: Master
--------------------------------------------------------------------------------
 PortName                   Slave/Master
 GigabitEthernet1/0/1            M
 GigabitEthernet1/0/2            S

3.4  Configuring an Eth-Trunk Interface in Static LACP Mode

Describes how to configure an Eth-Trunk interface in static mode.

3.4.1  Establishing the Configuration Task

Applicable Environment

To improve the bandwidth and the reliability of two devices, you should configure the LAG on two directly connected routers. The requirements are as follows:
  • The links between two devices can implement backup. When a fault occurs on some links, the backup links are used to replace the faulty ones to keep data transmission uninterrupted.

  • The active links can carry out load balancing.

Figure 3-5  Networking diagram of link aggregation in static LACP mode

NOTE:

In static LACP mode, member interfaces with different speeds and duplex modes, and on different boards, can be aggregated to an Eth-Trunk. Member interfaces of different rates cannot be in the forwarding state at the same time and member interfaces of half duplex mode cannot forward packets.

Pre-configuration Tasks

Before configuring Eth-Trunk interface in static LACP mode, complete the task of powering on the Router or switch and starting it normally.

Data Preparation

To configure link aggregation in static LACP mode, you need the following data.

No.

Data

1

Number of the Eth-Trunk

2

Type and number of the member interface

3

Upper threshold for the number of active interfaces

3.4.2  Creating an Eth-Trunk

Context

Do as follows on the routers where Eth-Trunk interface needs to be configured.

Procedure

  1. Run:
    system-view

    The system view is displayed.

  2. Run:
    interface eth-trunk trunk-id

    An Eth-Trunk is created.

3.4.3  (Optional) Configuring Working Mode of an Eth-Trunk Interface

Procedure

  1. Run:
    system-view

    The system view is displayed.

  2. Run:
    interface eth-trunk trunk-id

    The Eth-Trunk interface view is displayed.

  3. Run:
    portswitch

    The Layer 3 Eth-Trunk interface is converted to a Layer 2 interface.

    By default, an Eth-Trunk interface operates in Layer 3 mode.

    After an Eth-Trunk interface is switched to Layer 2 mode, its Layer 3 functions are disabled, and its MAC address is adopted.

    To add an Eth-Trunk interface into a VLAN, switch the interface from Layer 3 mode to Layer 2 mode. Before the switching, delete all configurations on the interface.

    Using the undo portswitch command, you can switch a Layer 2 Eth-Trunk interface to Layer 3 mode.

    NOTE:
    • The minimum interval for running the portswitch and undo portswitch commands continually is 30 seconds.

    • The working mode of an Eth-Trunk interface does not affect the addition of member interfaces, for example, an Ethernet interface can join either a Layer 2 Eth-Trunk or a Layer 3 Eth-Trunk interface.

3.4.4  Configuring the Operation Mode of the Eth-Trunk as the Static LACP Mode

Context

NOTE:

Ensure that the Eth-Trunk does not contain any member interfaces before you configure the operation mode of the Eth-Trunk; otherwise, the operation mode of the Eth-Trunk cannot be changed. Run the undo eth-trunk command in the interface view to delete the existing member interfaces. For details, refer to the chapter "Link Aggregation" in the Command Reference.

Both Layer 2 and Layer 3 Eth-Trunk interfaces support the static LACP mode.

Do as follows on the routers at both ends:

Procedure

  1. Run:
    system-view

    The system view is displayed.

  2. Run:
    interface eth-trunk trunk-id

    The Eth-Trunk interface view is displayed.

  3. Run:
    mode lacp-static

    The operation mode of the Eth-Trunk is configured as the static LACP mode.

    By default, an Eth-Trunk works in manual load balancing mode.

3.4.5  Adding Member Interfaces to the Eth-Trunk

Procedure

  • Configuration in the Eth-Trunk Interface View
    1. Run:
      system-view

      The system view is displayed.

    2. Run:
      interface eth-trunk trunk-id

      The Eth-Trunk interface view is displayed.

    3. Run the following command as required.
      • trunkport interface-type { interface-number1 [ to interface-number2 ] } &<1-16>

        The member interfaces are added in batches.

      • trunkport interface-type interface-number

        A member interface is added.

      When you specify the range of member interfaces, you can add or delete a maximum of 16 member interfaces once.

  • Configuration in the Member Interface View
    1. Run:
      system-view

      The system view is displayed.

    2. Run:
      interface { ethernet | gigabitethernet } interface-number

      The view of the interface to be added to the Eth-Trunk is displayed.

    3. Run:
      eth-trunk trunk-id

      The current interface is added into the Eth-Trunk.

      Before adding member interfaces, note the following:

      • Each Eth-Trunk interface can contain up to 16 physical member links.

      • Ensure the interfaces are not configured with Layer 3 configuration such as IP address, and any services.

      • Member interfaces cannot be configured with static MAC addresses.

      • Member interfaces of an Eth-Trunk cannot be Eth-Trunk.

      • An Ethernet interface can join only one Eth-Trunk interface. To join another Eth-Trunk interface, the interface must quit from the original Eth-Trunk first.

      • Fast Ethernet and Gigabit Ethernet interfaces can be added to the same Eth-Trunk.

      • Ethernet interfaces of different interface boards can be added into an Eth-Trunk.

      • For a router, if a member interface is a Layer 2 interface, the interface can be added into an Eth-Trunk only after it is switched to a Layer 3 interface by using the undo portswitch command.

      • Eth-Trunk has two working modes: Layer 2 mode and Layer 3 mode. An Ethernet port can be added into either a Layer 2 Eth-Trunk or a Layer 3 Eth-Trunk.

      • If an Eth-Trunk is created on a local device, the peer device interfaces that are directly connected with the member interfaces must be bound to an Eth-Trunk interface. Otherwise, the two ends cannot communicate.

3.4.6  (Optional) Setting the LACP Priority of the System

Context

Do as follows on the routers at both ends:

Procedure

  1. Run:
    system-view

    The system view is displayed.

  2. Run:
    lacp priority priority

    The LACP priority of the system is set.

    The lower the LACP priority of the system is, the higher the priority is.

    The end with a smaller LACP priority of the system functions as the Actor. By default, the LACP priority of the system is 32768. If the LACP priority of the system of one end is set to be lower than 32768, the end can function as the Actor.

3.4.7  (Optional) Setting the Upper Threshold for the Number of Active Interfaces

Context

In static LACP mode, you can control the maximum number M of active interfaces in the Eth-Trunk by configuring the upper threshold for the number of active interfaces. The remaining member interfaces are backup ones.

If the upper threshold is not configured, up to 16 interfaces in the Eth-Trunk can be in active state.

NOTE:

The upper threshold for the number of active interfaces of the local router and that of the remote router can be different. If the upper thresholds for the number of active interfaces at both ends are different, take the smaller upper threshold.

Do as follows on the routers at both ends:

Procedure

  1. Run:
    system-view

    The system view is displayed.

  2. Run:
    interface eth-trunk trunk-id

    The Eth-Trunk interface view is displayed.

  3. Run:
    max active-linknumber link-number

    The upper threshold for the number of active interfaces is set.

    By default, the upper threshold for the number of active interfaces is 16.

3.4.8  (Optional) Setting the LACP Priority of the Interface

Context

Do as follows on the routers at both ends:

Procedure

  1. Run:
    system-view

    The system view is displayed.

  2. Run:
    interface interface-type interface-number

    The interface view is displayed.

  3. Run:
    lacp priority priority

    The LACP priority of the current interface is set.

    NOTE:

    The LACP priority of the interface indicates the priority when the interface becomes the active interface. The lower the LACP priority of the interface is, the higher the priority is. By default, the LACP priority of an interface is 32768.

3.4.9  (Optional) Configuring the Mode for Selecting Active Interfaces in an Eth-Trunk Interface

Context

Do as follows on the routers at both ends:

Procedure

  1. Run:
    system-view

    The system view is displayed.

  2. Run:
    interface eth-trunk trunk-id

    The Eth-Trunk interface view is displayed.

  3. Run:
    lacp selected { priority | speed }

    The mode for selecting active interfaces in the current interface is configured.

    According to the Link Aggregation Control Protocol (LACP), active interfaces are selected according to the interface priority. In this case, low-speed member interfaces may be selected. To select high-speed member interfaces, you can configure the lacp selected speed command.

    By default, active interfaces are selected according to the interface priority.

    NOTE:

    To ensure that the Eth-Trunk interface works normally, it is recommended to configure the same mode for selecting active interfaces at both ends of the Eth-Trunk interface.

3.4.10  (Optional) Enabling LACP Preemption and Setting the Delay for LACP Preemption

Context

Do as follows on the routers at both ends:

Procedure

  1. Run:
    system-view

    The system view is displayed.

  2. Run:
    interface eth-trunk trunk-id

    The Eth-Trunk view is displayed.

  3. Run:
    lacp preempt enable

    The LACP preemption function is enabled on the Eth-Trunk.

    When the LACP preemption function is enabled, the interface with the highest LACP priority can be an active interface. For example, when an interface with a high priority switches to inactive due to failure and then recovers, the interface can become the active interface again if the LACP preemption function is enabled; the interface cannot become the active interface if the LACP preemption function is disabled.

    NOTE:

    To ensure the smooth running of the Eth-Trunk, you are recommended to simultaneously enable or disable the LACP preemption function at both ends of the Eth-Trunk.

  4. Run:
    lacp preempt delay delay-time

    The delay for LACP preemption on the Eth-Trunk is set.

    The delay for LACP preemption refers to the period when an inactive interface of the Eth-Trunk in static LACP mode switches to active.

    If the delay for LACP preemption of a local device is different from that of a remote peer, the system chooses a longer delay for LACP preemption.

3.4.11  (Optional) Setting the Timeout Period for Receiving LACP Protocol Packets

Context

Do as follows on the Routers at both ends:

Procedure

  1. Run:
    system-view

    The system view is displayed.

  2. Run:
    interface eth-trunk trunk-id

    The Eth-Trunk view is displayed.

  3. Run:
    lacp timeout { fast | slow }

    The timeout period for receiving LACP protocol packets on the Eth-Trunk is set.

    NOTE:
    • After the command is configured, the local end informs the remote peer of the timeout for receiving packets through LACP packets. If the timeout is set as fast, the period that the peer sends LACPDUs is 1s. If the timeout is set as slow, the period that the peer sends LACPDUs is 30s.
    • The timeout set at both ends can be different. To facilitate the maintenance, setting the same timeout for LACPDUs is recommended.

3.4.12  Checking the Configuration

Prerequisite

The configurations of an Eth-Trunk interface in static LACP mode function are complete.

Procedure

  • Run the display trunkmembership eth-trunk trunk-id command to check member interfaces of an Eth-Trunk.
  • Run the display eth-trunk [ trunk-id [ interface interface-type interface-number ] ] command to check the information about the Eth-Trunk and the active interfaces.

Example

Run the display trunkmembership eth-trunk command. You can check whether the operation mode, the priority of the system, and the priority of the interface are valid or not, and check the active interfaces selected by the system.

<HUAWEI> display eth-trunk 1
Eth-Trunk1's state information is:
 Local:
 LAG ID: 1                   WorkingMode: STATIC
 Preempt Delay: Disabled     Hash arithmetic: According to flow
 System Priority: 60         System ID: 00e0-fca8-041a
 Least Active-linknumber: 1  Max active-linknumber: 3
 Operate status: up          Number Of Up Port In Trunk: 3     
 ------------------------------------------------------------------------------
 ActorPortName          Status    PortType  PortPri PortNo  PortKey   PortState Weight
 GigabitEthernet6/0/3   Selected  1GE       32768   387     561       11111100     1
 GigabitEthernet6/0/4   Selected  1GE       10      388     561       11111100     1
 GigabitEthernet6/0/5   Selected  1GE       32768   389     561       11111100     1
 GigabitEthernet1/0/0   Unselect  10GE      32768   64      577       11100000     1
 GigabitEthernet3/0/0   Unselect  10GE      32768   192     577       11100010     1

 Partner:
 ------------------------------------------------------------------------------
 PartnerPortName        SysPri    SystemID    PortPri PortNo  PortKey   PortState
 GigabitEthernet6/0/3   32768  00e0-fca6-7f85  32768  387     561       11111100
 GigabitEthernet6/0/4   32768  00e0-fca6-7f85  32768  388     561       11111100
 GigabitEthernet6/0/5   32768  00e0-fca6-7f85  32768  389     561       11111100
 GigabitEthernet1/0/0   32768  00e0-fca6-7f85  32768  64      577       11100000
 GigabitEthernet3/0/0   0      0000-0000-0000  0       0      0         11100011

<HUAWEI> display trunkmembership eth-trunk 1
Trunk ID: 1
used status: VALID
TYPE: ethernet
Working Mode : Static
Number Of Ports in Trunk = 3
Number Of UP Ports in Trunk = 2
operate status: up

Interface GigabitEthernet1/0/1, valid, operate up, weight=1,
Interface GigabitEthernet1/0/2, valid, operate up, weight=1,
Interface GigabitEthernet1/0/3, valid, operate down, weight=1,

3.5  Configuring Layer 2 Attributes for an Eth-Trunk Interface

Describes how to configure an Eth-Trunk interface.

3.5.1  Establishing the Configuration Task

Applicable Environment

To add an Eth-Trunk interface into a VLAN, you need to configure Layer 2 attributes for the Eth-Trunk interface.

Layer 2 Eth-Trunk interfaces are mainly used in trunk interfaces in VLANs to increase the bandwidth for communication between the VLANs of two devices.

The configuration procedures in this section are optional.

Pre-configuration Tasks

Before configuring Layer 2 attributes for an Eth-Trunk interface, complete the fallowing tasks:

Data Preparation

To configure Layer 2 attributes for an Eth-Trunk interface, you need the following data.

No.

Data

1

Eth-Trunk ID

2

Type and number of Eth-Trunk member interfaces

3

Upper and lower threshold of the member links in the Up state

4

Weights of member interfaces

5

Mode of sending trap messages on Eth-Trunk member interfaces

3.5.2  (Optional) Configuring the Lower Threshold of Up Links

Procedure

  1. Run:
    system-view

    The system view is displayed.

  2. Run:
    interface eth-trunk trunk-id

    The Eth-Trunk interface view is displayed.

  3. Run:
    portswitch

    The Layer 3 Eth-Trunk interface is converted to a Layer 2 interface.

  4. Run:
    least active-linknumber link-number

    The lower threshold of member links in the Up state is configured.

    By default, the lower threshold is 1. That is, an Eth-Trunk remains Up as long as one member interface is Up.

    NOTE:
    • The lower threshold of links in the Up state can be configured in both Layer 2 mode and Layer 3 mode.

    • To ensure normal forwarding, it is recommended to configure the same lower threshold for the trunk interfaces on both ends of the same trunk link.

3.5.3  (Optional) Configuring the Upper Threshold of Up Links

Procedure

  1. Run:
    system-view

    The system view is displayed.

  2. Run:
    interface eth-trunk trunk-id

    The Eth-Trunk interface view is displayed.

  3. Run:
    portswitch

    The Eth-Trunk interface is switched to Layer 2 mode.

  4. Run:
    max bandwidth-affected-linknumber link-number

    The upper threshold of member links in the Up state is configured.

    By default, the upper threshold is 16.

    NOTE:

    The max bandwidth-affected-linknumber command is valid for Layer 2 Eth-Trunk interfaces only.

3.5.4  (Optional) Configuring an Eth-Trunk Interface to Carry out Load Balancing

Procedure

  1. Run:
    system-view

    The system view is displayed.

  2. Run:
    interface eth-trunk trunk-id

    The Eth-Trunk interface view is displayed.

  3. Run:
    portswitch

    The Eth-Trunk interface is switched to the Layer 2 mode.

  4. Run:
    load-balance { mac | packet-all | ip }

    Load balancing is configured on the Eth-Trunk interface.

    • MAC-based load balancing ensures the correctness of packet order but not high bandwidth utilization.

    • Packet-based load balancing ensures high bandwidth utilization but not the correctness of packet order.

    By default, load balancing is carried out based on mac when an Eth-Trunk interface works in Layer 2 mode.

3.5.5  (Optional) Configuring Weights for Member Links

Procedure

  1. Run:
    system-view

    The system view is displayed.

  2. Run:
    interface { ethernet | gigabitethernet } interface-number

    The view of the Eth-Trunk member interface is displayed.

  3. Run:
    distribute-weight weight-value

    The weight of the interface is configured.

    For an Eth-Trunk interface, the sum of weights of all its member interfaces cannot be greater than 16. The Eth-Trunk interface implements load balancing based on the weight of each member interface.

    On an Eth-Trunk interface, the larger the weight of a member interface is, the heavier the traffic on the member link is.

    By default, the weight of a member port is 1.

    NOTE:

    When an Eth-Trunk bears multicast traffic, if you run the distribute-weight command to change the load balancing weight of a member interface, you need to run the shutdown and undo shutdown commands to restart the member interface so that the configuration can take effect.

3.5.6  (Optional) Configuring the Method of Sending Traps on Eth-Trunk Member Interfaces

Context

Do as follows on the devices configured with the Eth-Trunk.

Procedure

  1. Run:
    system-view

    The system view is entered.

  2. Run:
    trunk-member trap in private-mib enable

    Traps are sent by the private MIB when the status of Eth-Trunk member interfaces goes Up or Down.

    By default, traps are sent by the public MIB when the status of the Eth-Trunk member interfaces goes Up or Down.

    Traps sent through the public MIB contain no information about the Eth-Trunk interface. To send traps carrying information about Eth-Trunk interfaces,use this command to send traps through private MIBs.

3.5.7  Checking the Configuration

Prerequisite

The configurations of layer 2 attributes for an Eth-Trunk interface are complete.

Procedure

  • Run the display interface eth-trunk [ trunk-id ] [ | { begin | include | exclude } regular-expression ] command to check status information about an Eth-Trunk interface.
  • Run the display interface brief [ | { begin | include | exclude } regular-expression ] command to check brief information about the Eth-Trunk interface, including physical status, protocol status, and bandwidth utilization.

Example

Run the display interface eth-trunk command. If information includes IP address, MAC address, and load balancing is displayed, it means the configuration succeeds. For example:

<HUAWEI> display interface Eth-Trunk 1
Eth-Trunk1 current state : UP
Line protocol current state : UP
Last line protocol up time: 2008-04-02, 11:00:19
Description : Eth-Trunk1 Interface
Route Port,Hash arithmatic : According to flow,The Maximum Transmit Unit is 1500

Internet protocol processing : disabled 
IP Sending Frames' Format is PKTFMT_ETHNT_2, Hardware address is 00e0-fc09-9722
Physical is ETH_TRUNK
Statistics last cleared: 2008-08-02 15:32:27
    Last 300 seconds input rate 0 bytes/sec, 0 packets/sec
    Last 300 seconds output rate 0 bytes/sec, 0 packets/sec
    Input:     1 packets,3 bytes,
               7 unicast,9 broadcast,8 multicasts
               10 errors,5 drops,11 unknowprotocol
    Output:    2 packets,4 bytes,
               12 unicast,14 broadcast,13x multicasts
               15 errors,6 drops
-----------------------------------------------------
PortName                Status              Weight
-----------------------------------------------------
Ethernet6/0/0           UP                  1
Ethernet6/0/1           UP                  1
-----------------------------------------------------
The Number of Ports in Trunk : 1
The Number of UP Ports in Trunk : 1 

Run the display interface brief [ | { begin | include | exclude } regular-expression ] command. You can view brief information about Eth-Trunk interface, such as physical status, link protocol status, bandwidth utilization, and error packet number. For example:

<HUAWEI> display interface brief | begin Eth-Trunk
*down: administratively down
^down: standby
(l): loopback
(s): spoofing
(b): BFD down
(d): Dampening Suppressed
InUti/OutUti: input utility/output utility 
Interface                   Physical Protocol InUti/OutUti  inErrors/outErrors 
Eth-Trunk1                  up        up      0%    0%      0        0 
  GigabitEthernet2/0/1      up        up      0%    0%      0        0 
  GigabitEthernet3/0/18     up        up      0%    0%      0        0
Eth-Trunk1.1                up        up      0%    0%      0        0

3.6  Configuring Layer 3 Attributes for an Eth-Trunk Interface

Describes how to configure a Layer 3 Eth-Trunk interface.

3.6.1  Establishing the Configuration Task

Applicable Environment

To use an Eth-Trunk interface as a Layer 3 interface, you need to configure Layer 3 attributes for the Eth-Trunk interface.

The configuration procedures in this section are optional.

Pre-configuration Tasks

Before configuring Layer 3 attributes for an Eth-Trunk interface, complete the task of creating an Eth-Trunk interface.

Data Preparation

Before configuring Layer 3 attributes for the Eth-Trunk interface, you need the following data.

No.

Data

1

IP address of the Eth-Trunk interface

2

MAC address of the Eth-Trunk interface

3

Lower threshold of the member links in the Up state

4

Weights of member interfaces

3.6.2  Configuring an IP address for an Eth-Trunk Interface

Procedure

  1. Run:
    system-view

    The system view is displayed.

  2. Run:
    interface eth-trunk trunk-id

    The Eth-Trunk interface view is displayed.

  3. Run:
    ip address ip-address { mask | mask-length } [ sub ]

    The IP address of the Eth-Trunk interface is configured.

3.6.3  (Optional) Configuring a MAC Address for the Eth-Trunk Interface

Procedure

  1. Run:
    system-view

    The system view is displayed.

  2. Run:
    interface eth-trunk trunk-id

    The Eth-Trunk interface view is displayed.

  3. Run:
    mac-address mac-address

    The MAC address of the Eth-Trunk interface is configured.

    NOTE:

    The mac-address command is valid for Layer 3 Eth-Trunk interfaces only.

    If a large number of trunk sub-interfaces exist and the MAC address of the trunk is changed, many ARP update packets are sent to the peer. If the peer is configured with CP CAR, you should increase the bandwidth to transmit ARP packets. This avoids the loss of ARP update packets.

3.6.4  (Optical) Configuring the MTU for an Eth-Trunk interface

Context

NOTE:
  • After changing the maximum transmission unit (MTU) by using the mtu command on a specified interface, you need to restart the interface to validate the newly configured MTU. To restart the interface, run the shutdown command and the undo shutdown command in succession, or run the restart command in the interface view.

  • If the Eth-Trunk interface is configured with a sub-interface, the interval for consecutively running the shutdown and undo shutdown commands on the Eth-Trunk interface must be 15 seconds at least.

Do as follows on the Layer 3 Eth-Trunk interface:

Procedure

  1. Run:
    system-view

    The system view is displayed.

  2. Run:
    interface eth-trunk trunk-id

    The Eth-Trunk interface view is displayed.

    By default, the Eth-Trunk interface is in Layer 3 mode.

  3. Run:
    mtu mtu

    The MTU of the Eth-Trunk interface is configured.

    The MTU is measured in bytes.

    By default, MTU is 1500 bytes.

    CAUTION:
    • The MTUs can not be configured on Layer 2 Eth-Trunk interface.

    • The MTUs on the interfaces at both ends of the directly connected link must be consistent. If you use the mtu command to change the MTU value of an interface, you must change the MTU values of the interfaces through which other devices are connected to the local device. Ensure that the MTU values of two connected devices are same. Otherwise, services may be interrupted.

    • For IPv6 running on the Ether-Trunk interface, if you run the mtu command to set the MTU to be less than 1280 bytes on the interface, IPv6 may work abnormally on this interface. To avoid abnormality, you can set a value no less than 1280 bytes on the Eth-Trunk interface where IPv6 is running.

3.6.5  (Optional) Configuring the Lower Threshold of Up Links

Procedure

  1. Run:
    system-view

    The system view is displayed.

  2. Run:
    interface eth-trunk trunk-id

    The Eth-Trunk interface view is displayed.

  3. Run:
    least active-linknumber link-number

    The lower threshold of member links in the Up state is configured.

    By default, the lower threshold is 1. That is, an Eth-Trunk remains Up as long as one member interface is Up.

    NOTE:
    • The lower threshold of member links in the Up state can be configured in both Layer 2 mode and Layer 3 mode.

    • To ensure normal forwarding, it is recommended to configure the same lower threshold for the trunk interfaces on both ends of the same trunk link.

3.6.6  (Optional) Configuring Load-balancing Mode for the Eth-Trunk Interface

Procedure

  1. Run:
    system-view

    The system view is displayed.

  2. Run:
    interface eth-trunk trunk-id

    The Eth-Trunk interface view is displayed.

  3. Run:
    load-balance { ip | packet-all | mac }

    The load-balancing mode is configured.

    • Load balancing based on IP addresses can guarantee the packet order, but cannot improve the bandwidth usage.

    • Packet-by-packet load balancing can improve the bandwidth usage, but cannot guarantee the packet order.

    By default, For a Layer 3 Eth-Trunk interface, load balancing is carried out based on ip.

3.6.7  (Optional) Configuring Weights for Member Links

Procedure

  1. Run:
    system-view

    The system view is displayed.

  2. Run:
    interface { ethernet | gigabitethernet } interface-number

    The view of the Eth-Trunk member interface is displayed.

  3. Run:
    distribute-weight weight-value

    The weight of the interface is configured.

    For an Eth-Trunk interface, the sum of weights of all its member interfaces cannot be greater than 16. The Eth-Trunk interface implements load balancing based on the weight of each member interface.

    On an Eth-Trunk interface, the larger the weight of a member interface is, the heavier the traffic on the member link is.

    By default, the weight of a member port is 1.

    NOTE:

    When an Eth-Trunk bears multicast traffic, if you run the distribute-weight command to change the load balancing weight of a member interface, you need to run the shutdown and undo shutdown commands to restart the member interface so that the configuration can take effect.

3.6.8  (Optional) Configuring the Method of Sending Traps on Eth-Trunk Member Interfaces

Context

Do as follows on the devices configured with the Eth-Trunk.

Procedure

  1. Run:
    system-view

    The system view is entered.

  2. Run:
    trunk-member trap in private-mib enable

    Traps are sent by the private MIB when the status of Eth-Trunk member interfaces goes Up or Down.

    By default, traps are sent by the public MIB when the status of the Eth-Trunk member interfaces goes Up or Down.

    Traps sent through the public MIB contain no information about the Eth-Trunk interface. To send traps carrying information about Eth-Trunk interfaces,use this command to send traps through private MIBs.

3.6.9  Checking the Configuration

Prerequisite

The configurations of the layer 3 attributes for an Eth-Trunk interface are complete.

Procedure

  • Run the display interface eth-trunk [ trunk-id ] [ | { begin | include | exclude } regular-expression ] command to check the status of the Eth-Trunk interface.
  • Run the display trunkmembership eth-trunk trunk-id [ | count ] [ | { begin | include | exclude } regular-expression ] command to check information about the Eth-Trunk member interface.
  • Run the display trunkfwdtbl eth-trunk trunk-id [ slot slot-id ] [ | count ] [ | { begin | include | exclude } regular-expression ] command to check the forwarding table of the Eth-Trunk interface.

Example

Run the display interface eth-trunk command. If information such as the IP address, MAC address and load-balancing mode is displayed, it means the configuration succeeds. For example:

<HUAWEI> display interface Eth-Trunk 1
Eth-Trunk1 current state : UP
Line protocol current state : UP
Last line protocol up time: 2008-04-02, 11:00:19
Description : Eth-Trunk1 Interface
Route Port,Hash arithmatic : According to flow,The Maximum Transmit Unit is 1500

Internet Address is 100.1.1.1/24
IP Sending Frames' Format is PKTFMT_ETHNT_2, Hardware address is 00e0-fc09-9722
Physical is ETH_TRUNK
Statistics last cleared: 2008-08-02 15:32:27
    Last 300 seconds input rate 0 bytes/sec, 0 packets/sec
    Last 300 seconds output rate 0 bytes/sec, 0 packets/sec
    Input:     1 packets,3 bytes,
               7 unicast,9 broadcast,8 multicasts
               10 errors,5 drops,11 unknowprotocol
    Output:    2 packets,4 bytes,
               12 unicast,14 broadcast,13x multicasts
               15 errors,6 drops
-----------------------------------------------------
PortName                Status              Weight
-----------------------------------------------------
GigabitEthernet1/0/1    UP                  1
GigabitEthernet1/0/2    UP                  1
-----------------------------------------------------
The Number of Ports in Trunk : 2
The Number of UP Ports in Trunk : 2 

Run the display trunkmembership eth-trunk command. If the usage status, network protocol status, and link status of the Eth-Trunk member interface are displayed, it means the configuration succeeds. For example:

<HUAWEI> display trunkmembership eth-trunk 0
Trunk ID: 0
used status: VALID
TYPE: ethernet
Working Mode : Normal
Working State: Normal
Number Of Ports in Trunk = 2
Number Of UP Ports in Trunk = 1
operate status: up

Interface GigabitEthernet6/0/1, valid, operate up, weight=1,
Interface GigabitEthernet6/0/2, valid, operate down, weight=1,

Run the display trunkfwdtbl eth-trunk command. If interface numbers of the main Eth-Trunk links and its backup links are displayed, it means the configuration succeeds.

<HUAWEI> display trunkfwdtbl eth-trunk 1
 Show the Trunk Forwarding Table
 Eth-Trunk1's forwarding table is:
 MASTER                                         SLAVE
GigabitEthernet1/0/0                           GigabitEthernet1/0/0
GigabitEthernet1/0/0                           GigabitEthernet1/0/0
GigabitEthernet1/0/0                           GigabitEthernet1/0/0
GigabitEthernet1/0/0                           GigabitEthernet1/0/0
GigabitEthernet1/0/0                           GigabitEthernet1/0/0
GigabitEthernet1/0/0                           GigabitEthernet1/0/0
GigabitEthernet1/0/0                           GigabitEthernet1/0/0
GigabitEthernet1/0/0                           GigabitEthernet1/0/0
GigabitEthernet1/0/0                           GigabitEthernet1/0/0
GigabitEthernet1/0/0                           GigabitEthernet1/0/0
GigabitEthernet1/0/0                           GigabitEthernet1/0/0
GigabitEthernet1/0/0                           GigabitEthernet1/0/0
GigabitEthernet1/0/0                           GigabitEthernet1/0/0
GigabitEthernet1/0/0                           GigabitEthernet1/0/0
GigabitEthernet1/0/0                           GigabitEthernet1/0/0
GigabitEthernet1/0/0                           GigabitEthernet1/0/0

3.7  Configuring an Eth-Trunk Sub-interface

Describes how to configure an Eth-Trunk sub-interface.

3.7.1  Establishing the Configuration Task

Applicable Environment

The NE80E/40E supports sub-interfaces that can be configured on Layer 3 and Layer 2 Eth-Trunk interfaces.

NOTE:

Besides, Layer 2 Eth-Trunk sub-interfaces can be used as follows:

When MPLS TE features are required on the devices that are connected through Layer 2 Eth-Trunk interfaces, MPLS TE cannot be configured on the main interface. Then, you can create a Layer 2 Eth-Trunk sub-interface and configure MPLS TE on the sub-interface. In this way, a physical link can transmit Layer 2 and Layer 3 services at the same time.

Pre-configuration Tasks

Before configuring an Eth-Trunk sub-interface, complete the following task:

  • Creating an Eth-Trunk interface

  • Connecting physical links between devices correctly

Data Preparation

To configure an Eth-Trunk sub-interface, you need the following data.

No.

Data

1

Number of the main interface

2

Number of the sub-interface

3

VLAN IDs associated with the sub-interface

4

Rate of sending gratuitous ARP packets

3.7.2  Creating an Eth-Trunk Sub-interface

Procedure

  • Creating a Layer 3 Eth-Trunk Sub-interface
    1. Run:
      system-view

      The system view is displayed.

    2. Run:
      interface eth-trunk interface-number.subinterface-number

      A sub-interface is created and the sub-interface view is displayed.

      The parameter subinterface-number specifies the number of the Eth-Trunk sub-interface. The number ranges from 1 to 4094. A maximum of 4094 sub-interfaces can be created on an Eth-Trunk main interface. The total number of Eth-Trunk sub-interfaces on the device is 16376.

      A maximum of 2048 sub-interfaces can be created on an Eth-Trunk main interface. The total number of Eth-Trunk sub-interfaces on the device is 16376.

  • Creating a Layer 2 Eth-Trunk Sub-interface
    1. Run:
      system-view

      The system view is displayed.

    2. Run:
      interface eth-trunk trunk-id

      An Eth-Trunk is created.

    3. Run:
      portswitch

      The Eth-Trunk interface is switched from Layer 3 to Layer 2 mode.

      By default, the Eth-Trunk interface works in Layer 3 mode.

    4. Run:
      interface eth-trunk interface-number.sub-interface-number

      The sub-interface of the Layer 2 Eth-Trunk interface is created.

      The parameter subinterface-number specifies the number of the Eth-Trunk sub-interface. The number ranges from 1 to 4094. The value range of the Eth-Trunk sub-interface number depends on products.

3.7.3  Configuring an IP address for an Eth-Trunk Sub-interface

Procedure

  1. Run:
    system-view

    The system view is displayed.

  2. Run:
    interface eth-trunk interface-number.subinterface-number

    The specified Eth-Trunk sub-interface view is displayed.

  3. Run:
    ip address ip-address ip-mask [ sub ]

    An IP address is configured for the Eth-Trunk sub-interface.

    For the configuration of an IP address, refer to the HUAWEI NetEngine80E/40E Router Configuration Guide - IP Services.

    When more than one IP address is configured for an Eth-Trunk interface, the keyword sub can be used to indicate other IP addresses rather than the first IP address.

3.7.4  Configuring the Encapsulation Type for an Eth-Trunk Sub-interface

Procedure

  1. Run:
    system-view

    The system view is displayed.

  2. Run:
    interface eth-trunk interface-number.subinterface-number

    The Eth-Trunk sub-interface view is displayed.

  3. Run:
    vlan-type dot1q vlan-id

    The encapsulation type and associated VLAN ID are configured for an Eth-Trunk sub-interface.

    NOTE:

    In the NE80E/40E, an Eth-Trunk sub-interface can be associated with a VLAN.

    For information about the configuration of the dot1q and QinQ termination sub-interfaces, see QinQ Configuration.

    By default, no encapsulation type or the associated VLAN ID is configured on the sub-interface.

    For the connectivity of VLANs, the VLAN IDs on interfaces of both ends must be consistent.

    The VLAN ID set to the Eth-Trunk sub-interface cannot be the same as that set to the Eth-Trunk main interface.

3.7.5  (Optical) Configuring the MTU for an Eth-Trunk Sub-interface

Context

NOTE:
  • After changing the MTU by using the mtu command on a specified interface, you need to restart the interface to validate the newly configured value. To restart the interface, run the shutdown and the undo shutdown commands in succession.
  • If the Ethernet interface is configured with a sub-interface, the interval for consecutively running the shutdown and undo shutdown commands on the Ethernet interface must be 15 seconds at least.

Do as follows on the Eth-Trunk sub-interface of the router:

Procedure

  1. Run:
    system-view

    The system view is displayed.

  2. Run:
    interface eth-trunk interface-number.subinterface-number

    The specified Eth-Trunk sub-interface view is displayed.

  3. Run:
    mtu mtu

    The MTU is configured for the Eth-Trunk sub-interface.

    The MTU is expressed in bytes. The MTU ranges form 46 to 9600. By default, the MTU is 1500 bytes.

    NOTE:
    The Quality of Service (QoS) queue length is limited. If the MTU is too small whereas the packet size is large, the packet is probably split into many fragments. Thus, the packet may be discarded due to the insufficient QoS queue length. To avoid this situation, lengthen the QoS queue accordingly.

3.7.6  (Optional) Configuring the Rate for Sending Gratuitous ARP packets on an Eth-Trunk Sub-interface

Procedure

  1. Run:
    system-view

    The system view is displayed.

  2. Run:
    interface eth-trunk trunk-id

    The Eth-Trunk interface view is displayed.

  3. Run:
    arp send-speed-limit

    The rate for sending gratuitous ARP packets on an Eth-Trunk sub-interface is limited.

    By default, the rate is 2000 packets per second.

    To prevent the peer router from discarding ARP packets, the rate for sending gratuitous ARP packets can be configured on the Eth-Trunk sub-interface of the local router. The rate for sending gratuitous ARP packets configured on the Eth-Trunk sub-interface of the local router must be consistent with the receiving ability of the peer end.

3.7.7  Checking the Configuration

Prerequisite

The configurations of an Eth-Trunk Sub-interface are complete.

Procedure

  1. Run the display interface eth-trunk [ trunk-id [ .subnumber ] ] [ | { begin | include | exclude } regular-expression ] command to check the status of the Eth-Trunk sub-interface.

Example

Run the display interface eth-trunk command. If information, such as the IP address and MAC address of the Eth-Trunk sub-interface, is displayed, it means that the configuration succeeds. For example:

<HUAWEI> display interface eth-trunk 1.1
Eth-Trunk1.1 current state : UP
Line protocol current state : UP
Description : Eth-Trunk1.1 Interface
Hash arithmetic : According to IP, The Maximum Transmit Unit is 1500
Internet Address is 10.10.10.100/24
IP Sending Frames' Format is PKTFMT_ETHNT_2, Hardware address is 00e0-3f60-ec00
Encapsulation dot1q Virtual LAN, The number of Vlan is 1, Vlan ID 2
Statistics last cleared: 2008-08-02 15:32:27
    Last 300 seconds input rate 0 bytes/sec, 0 packets/sec
    Last 300 seconds output rate 0 bytes/sec, 0 packets/sec
    Input: 0 packets,0 bytes,
           0 unicast,0 broadcast,0 multicasts
           0 errors,0 drops,0 unknowprotocol
    Output:0 packets,0 bytes,
           0 unicast,0 broadcast,0 multicasts
           0 errors,0 drops
-----------------------------------------------------
PortName                Status              Weight
-----------------------------------------------------
Ethernet6/0/0           UP                  1
-----------------------------------------------------
The Number of Ports in Trunk : 1
The Number of UP Ports in Trunk : 1 

3.8  Configuring an E-Trunk

This section describes how to configure an E-Trunk.

3.8.1  Establishing the Configuration Task

Applicable Environment

As shown in Figure 3-6, the E-Trunk is used to protect the links between the CE and two PEs when the CE is dual-homed to the two PEs to access the VPLS network. The CE is connected to PE1 and PE2 through a static LACP Eth-Trunk respectively. The two Eth-Trunks form an E-Trunk that can implement link backup of aggregation groups between PE1 and PE2 and thus enhance the network reliability.

Figure 3-6  Networking diagram of the E-Trunk

Pre-configuration Tasks

Before configuring the E-Trunk, complete the following tasks:

  • Connecting physical links between devices correctly

  • Configuring static LACP Eth-Trunk interfaces

Data Preparation

To configure the E-Trunk, you need the following data.

No.

Data

1

LACP system ID and priority

2

ID and priority of an E-Trunk

3

Interface numbers and work modes of the Eth-Trunk

4

Local and peer IP addresses

5

Password used for encryption

6

Period of sending Hello packets and time multiplier for detecting Hello packets

3.8.2  Configuring the LACP System ID and Priority of the E-Trunk

Context

Do as follows on the devices at both ends of the E-Trunk:

Procedure

  1. Run:
    system-view

    The system view is displayed.

  2. Run:
    lacp e-trunk system-id mac-address

    The LACP system ID is configured for the E-Trunk.

    By default, the MAC address of the Ethernet interface of the MPU/SRU is the LACP system ID of the E-Trunk.

    The LACP system IDs of the master device and backup device in the E-Trunk must be the same.

  3. Run:
    lacp e-trunk priority priority

    The LACP priority of the E-Trunk is configured.

    By default, the LACP priority of the E-Trunk is 32768.

    The LACP priorities of the master device and backup device in the E-Trunk must be the same.

3.8.3  Creating an E-Trunk and Configuring Its Priority

Context

Do as follows on the devices at both ends of the E-Trunk:

Procedure

  1. Run:
    system-view

    The system view is displayed.

  2. Run:
    e-trunk e-trunk-id

    The E-Trunk is created.

    When the E-Trunk with the specified ID already exists, running the e-trunk e-trunk-id command displays the E-Trunk view.

    In an E-Trunk, the E-Trunk IDs of the two devices must be the same.

    At most 16 E-Trunks can be created on a device.

  3. Run:
    priority priority

    The priority of the E-Trunk is configured.

    The priority is applied to master/backup negotiation between two devices. The device of higher priority is the master. The smaller the priority value is, the higher the priority is.

    If the priorities of two devices are the same, the device with the smaller system ID is the master.

    By default, the priority of the E-Trunk is 100.

3.8.4  Configuring Local and Peer IP Addresses

Context

Do as follows on the devices at both ends of the E-Trunk:

Procedure

  1. Run:
    system-view

    The system view is displayed.

  2. Run:
    e-trunk e-trunk-id

    The E-Trunk view is displayed.

  3. Run:
    peer-address peer-ip-address source-address source-ip-address

    The local and peer IP addresses are configured.

    The peer IP address of the local device is the local IP address of the peer device. For example, an E-Trunk is set up between device A and device B. On device A, the peer IP address is 2.2.2.2 and the local IP address is 1.1.1.1. Then, on device B, the peer IP address is 1.1.1.1 and the local IP address is 2.2.2.2.

3.8.5  Binding the E-Trunk to the BFD Session

Do as follows on the devices at both ends of the E-Trunk:

Procedure

  1. Run:
    system-view

    The system view is displayed.

  2. Run:
    e-trunk e-trunk-id

    The E-Trunk view is displayed.

  3. Run:
    e-trunk track bfd-session session-id

    The E-Trunk is bound to the BFD session.

    BFD sessions are used to fast detect the fault of the control link between the two devices of the E-Trunk.

3.8.6  Adding an Eth-Trunk to an E-Trunk

Context

Do as follows on the devices at both ends of the E-Trunk:

Procedure

  1. Run:
    system-view

    The system view is displayed.

  2. Run:
    interface eth-trunk trunk-id

    The Eth-Trunk interface view is displayed.

    Only static LACP Eth-Trunks can be added to the E-Trunk.

  3. Run:
    e-trunk e-trunk-id

    The Eth-Trunk is added to the E-Trunk.

    An Eth-Trunk can be added to only one E-Trunk.

    The IDs of the Eth-Trunks to which the two devices of an E-Trunk are added must be the same. For example, the Eth-Trunks that are added to E-Trunk 1 on device A are Eth-Trunk 1 and Eth-Trunk 2. Then, the Eth-Trunks that will be added to E-Trunk 1 on device B must be Eth-Trunk 1 and Eth-Trunk 2.

3.8.7  (Optional) Configuring the Operation Mode of the Eth-Trunk

Context

Do as follows on the devices at both ends of the E-Trunk:

Procedure

  1. Run:
    system-view

    The system view is displayed.

  2. Run:
    interface eth-trunk trunk-id

    The Eth-Trunk interface view is displayed.

    Only static LACP Eth-Trunks can be added to the E-Trunk.

  3. Run:
    e-trunk mode { auto | force-master | force-backup }

    The work mode of the Eth-Trunk in the E-Trunk is configured.

    By default, the Eth-Trunk works in automatic state in the E-Trunk.

    You can run the command only on the Eth-Trunk in the E-Trunk. When the Eth-Trunk exits from the E-Trunk, the configurations of the command are automatically deleted.

    When the work mode of the Eth-Trunk is automatic or is switched from forcible master/backup to automatic, the master/backup status of the local Eth-Trunk depends on the master/backup status of the local E-Trunk and faulty information about the peer Eth-Trunk.
    • If the local E-Trunk is the master, the local Eth-Trunk works in forcible master state.

    • If the local E-Trunk is the backup and the peer Eth-Trunk is faulty, the local Eth-Trunk works in forcible master state. When the local Eth-Trunk receives the message that the peer Eth-Trunk recovers, the local Eth-Trunk becomes the backup.

    When the E-Trunk works normally, changing the interval of sending packets or the timeout period causes the E-Trunk to alternate between the master state and the backup state. As a result, it is recommended that you set the work mode of a member Eth-Trunk to forcible master/backup before changing the interval of sending packets or the timeout period. After new configurations take effect, you can restore the work mode to automatic.

3.8.8  (Optional) Configuring the Password

Context

CAUTION:

If simple is selected, the password is saved into the configuration file as plain text. Users at a lower level then can easily obtain the password by viewing the configuration file. As a result, the network security is threatened. Therefore, it is recommended that you select cipher to save the password in the cipher text.

Do as follows on the devices at two ends of the E-Trunk:

Procedure

  1. Run:
    system-view

    The system view is displayed.

  2. Run:
    e-trunk e-trunk-id

    The E-Trunk view is displayed.

  3. Run:
    security-key { simple simple-key | cipher cipher-key }

    The password for encrypting the packet is configured.

    An encrypted password can be configured to enhance the system security. The encrypted passwords configured on the two devices of an E-Trunk must be the same.

    You can encrypt the password with the plain or cipher text.
    • When the password is encrypted in the plain text, it is displayed in plain text in the configuration file.

    • When the password is encrypted in the cipher text, the password is displayed as illegible characters rather than the real password.

3.8.9  (Optional) Configuring the Timeout Period

Context

Do as follows on the devices at both ends of the E-Trunk:

Procedure

  1. Run:
    system-view

    The system view is displayed.

  2. Run:
    e-trunk e-trunk-id

    The E-Trunk view is displayed.

  3. Run:
    timer hello hello-times

    The period for sending Hello packets is configured.

    By default, the value of the period for sending Hello packets is 10. Since the unit is 100 ms, the period is 1s.

  4. Run:
    timer hold-on-failure multiplier multiplier

    The time multiplier for detecting Hello packets is configured.

    The peer device checks the timeout period contained in the received packet to check whether the local device times out. If the peer device is the backup and does not receive Hello packets sent by the local device within the timeout period, the peer device becomes the master after timeout.

    Timeout period = Sending period x Time multiplier It is recommended that you set the multiplier of time to 3 or larger.

    By default, the multiplier for detecting Hello packets is 20.

3.8.10  (Optional) Setting the Revert Delay

Context

When an E-Trunk works together with other services, after the fault on the master device is rectified, the status of the member Eth-Trunk on the master device is restored preferentially over other related services. After the master device is recovered, if traffic on the member Eth-Trunk is immediately reverted back to the master device, service traffic will be interrupted.

After the revert delay of the E-Trunk is set, only when the revert delay timer expires, the local member Eth-Trunk goes Up and the local device of the E-Trunk returns to the master state. This delays reverting traffic on the member Eth-Trunk back to the master device, thus preventing service traffic from being interrupted.

Do as follows on the devices at two sides of the E-Trunk:

Procedure

  1. Run:
    system-view

    The system view is displayed.

  2. Run:
    e-trunk e-trunk-id

    The E-Trunk view is displayed.

  3. Run:
    timer revert delay delay-value

    The revert delay is set.

    By default, the revert delay of an E-Trunk is 120 seconds.

3.8.11  Checking the Configuration

Prerequisite

All configurations of the E-Trunk are complete.

Procedure

  1. Run the display e-trunk e-trunk-id command to check configurations of the E-Trunk.

Example

Run the display e-trunk command, and you can view the priority, system ID, local and peer IP addresses, timeout period, and statistics of packets. For example:

<HUAWEI> display e-trunk 1

               The E-Trunk information
E-TRUNK-ID            : 1              Revert-Delay-Time (s) : 120
Priority               : 10             System-ID             : 00e0-e213-9100
Peer-IP                : 1.1.1.2        Source-IP             : 1.1.1.1
State                  : Master         Causation             : TIMEOUT
Send-Period (100ms)    : 9              Fail-Time (100ms)     : 27
Receive                : 1              Send                  : 1006
RecDrop                : 0              SndDrop               : 0
Peer-Priority          : -              Peer-System-ID        : -
Peer-Fail-Time (100ms) : -              BFD-Session           : 1
--------------------------------------------------------------------------------
                The Member information
Type        ID  LocalPhyState   Work-Mode      State    Causation
Eth-Trunk   10  Up              auto           Master   ETRUNK_MASTER 

3.9  Maintaining Eth-Trunk Interface

Describes how to maintain Eth-Trunk Interface.

3.9.1  Clearing the Statistics of Eth-Trunk Interface

Context

CAUTION:

Statistics cannot be restored after being cleared. Therefore, confirm the action before you run the following commands.

Procedure

3.10  Configuration Examples

Provides several configuration examples of Eth-Trunk and IP-Trunk Interface.

3.10.1  Example for Configuring Eth-Trunk interfaces in Manual Load Balancing Mode

Networking Requirements

As shown in Figure 3-7, RouterA and RouterB are two NE80E/40Es. The link should be of high reliability and the load balancing of data traffic can be performed between RouterA and RouterB.

Figure 3-7  Networking diagram of link aggregation in manual load balancing mode

Configuration Roadmap

The configuration roadmap is as follows:

  1. Create an Eth-Trunk.

  2. Add member interfaces to the Eth-Trunk.

  3. Check the configuration.

NOTE:

After an Eth-Trunk is created, the default operation mode is the manual load balancing mode. By default, you need not configure the Eth-Trunk in manual load balancing mode. If the current operation mode is configured as other modes, use the mode command to change the mode. For details, refer to the chapter "Link Aggregation" in the Command Reference.

Data Preparation

To complete the configuration, you need the following data:

  • Number of the LAG

  • Type and number of the member interface of the Eth-Trunk

Procedure

  1. Create an Eth-Trunk.

    # Configure RouterA.

    <HUAWEI> system-view
    [HUAWEI] sysname RouterA
    [RouterA] interface eth-trunk 1
    [RouterA-Eth-Trunk1] quit

    # Configure RouterB.

    <HUAWEI> system-view
    [HUAWEI] sysname RouterB
    [RouterB] interface eth-trunk 1
    [RouterB-Eth-Trunk1] quit
  2. Add member interfaces to the Eth-Trunk.

    # Configure RouterA.

    [RouterA] interface gigabitethernet 1/0/1
    [RouterA-Gigabitethernet1/0/1] undo shutdown
    [RouterA-Gigabitethernet1/0/1] eth-trunk 1
    [RouterA-Gigabitethernet1/0/1] quit
    [RouterA] interface gigabitethernet 1/0/2
    [RouterA-Gigabitethernet1/0/2] undo shutdown
    [RouterA-Gigabitethernet1/0/2] eth-trunk 1
    [RouterA-Gigabitethernet1/0/2] quit
    [RouterA] interface gigabitethernet 1/0/3
    [RouterA-Gigabitethernet1/0/3] undo shutdown
    [RouterA-Gigabitethernet1/0/3] eth-trunk 1
    [RouterA-Gigabitethernet1/0/3] quit

    # Configure RouterB.

    [RouterB] interface gigabitethernet 1/0/1
    [RouterB-Gigabitethernet1/0/1] undo shutdown
    [RouterB-Gigabitethernet1/0/1] eth-trunk 1
    [RouterB-Gigabitethernet1/0/1] quit
    [RouterB] interface gigabitethernet 1/0/2
    [RouterB-Gigabitethernet1/0/2] undo shutdown
    [RouterB-Gigabitethernet1/0/2] eth-trunk 1
    [RouterB-Gigabitethernet1/0/2] quit
    [RouterB] interface gigabitethernet 1/0/3
    [RouterB-Gigabitethernet1/0/3] undo shutdown
    [RouterB-Gigabitethernet1/0/3] eth-trunk 1
    [RouterB-Gigabitethernet1/0/3] quit
  3. Verify the configuration.

    Run the display trunkmembership command in any view. You can check whether Eth-Trunk 1 is created and whether member interfaces are correctly added. Take RouterA as an example.

    [RouterA] display trunkmembership eth-trunk 1
    Trunk ID: 1
    used status: VALID
    TYPE: ethernet
    Working Mode : Normal
    Working State: Normal
    Number Of Ports in Trunk = 3
    Number Of UP Ports in Trunk = 3
    operate status: up
    
    Interface GigabitEthernet1/0/1, valid, operate up, weight=1,
    Interface GigabitEthernet1/0/2, valid, operate up, weight=1,
    Interface GigabitEthernet1/0/3, valid, operate up, weight=1,
    

Configuration Files

  • Configuration file of RouterA

    #
     sysname RouterA
    #
    interface Eth-Trunk1
    #
    interface GigabitEthernet1/0/1
     undo shutdown
     eth-trunk 1
    #
    interface GigabitEthernet1/0/2
     undo shutdown
     eth-trunk 1
    #
    interface GigabitEthernet1/0/3
     undo shutdown
     eth-trunk 1
    #
    return
  • Configuration file of RouterB

    #
     sysname RouterB
    #
    interface Eth-Trunk1
    #
    interface GigabitEthernet1/0/1
     undo shutdown
     eth-trunk 1
    #
    interface GigabitEthernet1/0/2
     undo shutdown
     eth-trunk 1
    #
    interface GigabitEthernet1/0/3
     undo shutdown
     eth-trunk 1
    #
    return

3.10.2  Example for Configuring Eth-Trunk interfaces in 1:1 Active/Standby Mode

Networking Requirements

As shown in Figure 3-8, RouterA and RouterD are NE80E/40Es. The transit device can receive flush packets. The reliability of data transmission from RouterA to RouterD should be implemented through primary and backup links.

Figure 3-8  Networking diagram of configuring link aggregation in 1:1 active/standby mode

Configuration Roadmap

The configuration roadmap is as follows:

Do as follows on the Routers that need be configured with link aggregation in 1:1 active/standby mode.

  1. Create an Eth-Trunk and configure the operation mode of the Eth-Trunk as the 1:1 active/standby mode.

  2. Add member interfaces to the Eth-Trunk and specify the primary interface.

  3. Enable interfaces to send flush packets.

Do as follows on the transit node:

  1. Create a control VLAN.

  2. Enable interfaces to receive packets from the control VLAN.

  3. Enable interfaces to receive flush packets.

Data Preparation

To complete the configuration, you need the following data:

  • Number of the LAG of RouterA and RouterD

  • Type and number of the member interface

  • ID of the control VLAN

Procedure

  1. Create an Eth-Trunk numbered 1 and configure the operation mode of the Eth-Trunk as the 1:1 active/standby mode.

    # Create an Eth-Trunk on RouterA and specify the operation mode of the Eth-Trunk as the 1:1 active/standby mode.

    <HUAWEI> system-view
    [HUAWEI] sysname RouterA
    [RouterA] interface eth-trunk 1
    [RouterA-Eth-Trunk1] portswitch
    [RouterA-Eth-Trunk1] mode manual backup
    [RouterA-Eth-Trunk1] quit

    # Create an Eth-Trunk on RouterD and specify the operation mode of the Eth-Trunk as the 1:1 active/standby mode.

    <HUAWEI> system-view
    [HUAWEI] sysname RouterD
    [RouterD] interface eth-trunk 1
    [RouterD-Eth-Trunk1] portswitch
    [RouterD-Eth-Trunk1] mode manual backup
    [RouterD-Eth-Trunk1] quit
  2. Add member interfaces to the Eth-Trunk and specify the primary interface.

    # On RouterA, add GE 1/0/1 and GE 1/0/2 to Eth-Trunk 1 and specify GE 1/0/1 as the primary interface.

    [RouterA] interface gigabitethernet 1/0/1
    [RouterA-GigabitEthernet1/0/1] undo shutdown
    [RouterA-GigabitEthernet1/0/1] eth-trunk 1
    [RouterA-GigabitEthernet1/0/1] port-master
    [RouterA-GigabitEthernet1/0/1] quit
    [RouterA] interface gigabitethernet 1/0/2
    [RouterA-GigabitEthernet1/0/2] undo shutdown
    [RouterA-GigabitEthernet1/0/2] eth-trunk 1
    [RouterA-GigabitEthernet1/0/2] quit

    # On RouterD, add GE 1/0/1 and GE 1/0/2 to Eth-Trunk 1 and specify GE 1/0/1 as the primary interface.

    [RouterD] interface gigabitethernet 1/0/1
    [RouterD-GigabitEthernet1/0/1] undo shutdown
    [RouterD-GigabitEthernet1/0/1] eth-trunk 1
    [RouterD-GigabitEthernet1/0/1] port-master
    [RouterD-GigabitEthernet1/0/1] quit
    [RouterD] interface gigabitethernet 1/0/2
    [RouterD-GigabitEthernet1/0/2] undo shutdown
    [RouterD-GigabitEthernet1/0/2] eth-trunk 1
    [RouterD-GigabitEthernet1/0/2] quit
  3. Enable interfaces to send flush packets.

    # Enable interfaces to send flush packets on RouterA.

    [RouterA] interface eth-trunk 1
    [RouterA-Eth-Trunk1] smart-link flush send vlan 5
    [RouterA-Eth-Trunk1] quit

    # Enable interfaces to send flush packets on RouterD.

    [RouterD] interface eth-trunk 1
    [RouterD-Eth-Trunk1] smart-link flush send vlan 5
    [RouterD-Eth-Trunk1] quit
  4. Create a control VLAN on the transit node.

    # Configure RouterB.

    <HUAWEI> system-view
    [HUAWEI] sysname RouterB
    [RouterB] vlan 5
    [RouterB-vlan5] quit

    # Configure RouterC.

    <HUAWEI> system-view
    [HUAWEI] sysname RouterC
    [RouterC] vlan 5
    [RouterC-vlan5] quit
  5. Enable interfaces of the transit node to receive packets from the control VLAN.

    # Configure RouterB.

    [RouterB] interface gigabitethernet 2/0/1
    [RouterB-GigabitEthernet2/0/1] undo shutdown
    [RouterB-GigabitEthernet2/0/1] portswitch
    [RouterB-GigabitEthernet2/0/1] port trunk allow-pass vlan 5
    [RouterB-GigabitEthernet2/0/1] quit
    [RouterB] interface gigabitethernet 2/0/2
    [RouterB-GigabitEthernet2/0/2] undo shutdown
    [RouterB-GigabitEthernet2/0/2] portswitch
    [RouterB-GigabitEthernet2/0/2] port trunk allow-pass vlan 5
    [RouterB-GigabitEthernet2/0/2] quit
    [RouterB] interface gigabitethernet 2/0/3
    [RouterB-GigabitEthernet2/0/3] undo shutdown
    [RouterB-GigabitEthernet2/0/3] portswitch
    [RouterB-GigabitEthernet2/0/3] port trunk allow-pass vlan 5
    [RouterB-GigabitEthernet2/0/3] quit

    # Configure RouterC.

    [RouterC] interface gigabitethernet 2/0/1
    [RouterC-GigabitEthernet2/0/1] undo shutdown
    [RouterC-GigabitEthernet2/0/1] portswitch
    [RouterC-GigabitEthernet2/0/1] port trunk allow-pass vlan 5
    [RouterC-GigabitEthernet2/0/1] quit
    [RouterC] interface gigabitethernet 2/0/2
    [RouterC-GigabitEthernet2/0/2] undo shutdown
    [RouterC-GigabitEthernet2/0/2] portswitch
    [RouterC-GigabitEthernet2/0/2] port trunk allow-pass vlan 5
    [RouterC-GigabitEthernet2/0/2] quit
    [RouterC] interface gigabitethernet 2/0/3
    [RouterC-GigabitEthernet2/0/3] undo shutdown
    [RouterC-GigabitEthernet2/0/3] portswitch
    [RouterC-GigabitEthernet2/0/3] port trunk allow-pass vlan 5
    [RouterC-GigabitEthernet2/0/3] quit
  6. Enable interfaces of the transit node to receive flush packets.

    # Configure RouterB.

    [RouterB] interface gigabitethernet 2/0/1
    [RouterB-GigabitEthernet2/0/1] smart-link flush enable control-vlan 5
    [RouterB-GigabitEthernet2/0/1] quit
    [RouterB] interface gigabitethernet 2/0/2
    [RouterB-GigabitEthernet2/0/2] smart-link flush enable control-vlan 5
    [RouterB-GigabitEthernet2/0/2] quit
    [RouterB] interface gigabitethernet 2/0/3
    [RouterB-GigabitEthernet2/0/3] smart-link flush enable control-vlan 5
    [RouterB-GigabitEthernet2/0/3] quit

    # Configure RouterC.

    [RouterC] interface gigabitethernet 2/0/1
    [RouterC-GigabitEthernet2/0/1] smart-link flush enable control-vlan 5
    [RouterC-GigabitEthernet2/0/1] quit
    [RouterC] interface gigabitethernet 2/0/2
    [RouterC-GigabitEthernet2/0/2] smart-link flush enable control-vlan 5
    [RouterC-GigabitEthernet2/0/2] quit
    [RouterC] interface gigabitethernet 2/0/3
    [RouterC-GigabitEthernet2/0/3] smart-link flush enable control-vlan 5
    [RouterC-GigabitEthernet2/0/3] quit
  7. Verify the configuration.

    # Check information about the LAG on the Routers that are configured with link aggregation in 1:1 active/standby mode. Take RouterA as an example. If the configuration is correct, you can view information about the operation mode, primary interface, and backup interface.

    [RouterA] display eth-trunk 1
     Eth-Trunk1's state information is:
     WorkingMode: BACKUP
     WorkingState: Master
    --------------------------------------------------------------------------------
     PortName                   Slave/Master
     GigabitEthernet1/0/1            M
     GigabitEthernet1/0/2            S

    # Check the configuration on the interface of the transit node. Take GE 2/0/1 of RouterB as an example.

    [RouterB-GigabitEthernet2/0/1] display current-configuration interface gigabitethernet 2/0/1
     port trunk allow-pass vlan 5
     smart-link flush enable control-vlan 5

Configuration Files

  • Configuration file of RouterA

    #
     sysname RouterA
    #
    interface Eth-Trunk1
     portswitch
     mode manual backup
     smart-link flush send vlan 5
    #
    interface GigabitEthernet1/0/1
     undo shutdown
     eth-trunk 1
     port-master
    #
    interface GigabitEthernet1/0/2
     undo shutdown
     eth-trunk 1
    #
    return
  • Configuration file of RouterB

    #
     sysname RouterB
    #
    vlan batch 5
    #
    interface GigabitEthernet2/0/1
     undo shutdown
     portswitch
     port trunk allow-pass vlan 5
     smart-link flush enable control-vlan 5
    #
    interface GigabitEthernet2/0/2
     undo shutdown
     portswitch
     port trunk allow-pass vlan 5
     smart-link flush enable control-vlan 5
    #
    interface GigabitEthernet2/0/3
     undo shutdown
     portswitch
     port trunk allow-pass vlan 5
     smart-link flush enable control-vlan 5
    #
    return
  • Configuration file of RouterC

    #
     sysname RouterC
    #
    vlan batch 5
    #
    interface GigabitEthernet2/0/1
     undo shutdown
     portswitch
     port trunk allow-pass vlan 5
     smart-link flush enable control-vlan 5
    #
    interface GigabitEthernet2/0/2
     undo shutdown
     portswitch
     port trunk allow-pass vlan 5
     smart-link flush enable control-vlan 5
    #
    interface GigabitEthernet2/0/3
     undo shutdown
     portswitch
     port trunk allow-pass vlan 5
     smart-link flush enable control-vlan 5
    #
    return
  • Configuration file of RouterD

    #
     sysname RouterD
    #
    interface Eth-Trunk1
     portswitch
     mode manual backup
     smart-link flush send vlan 5
    #
    interface GigabitEthernet1/0/1
     undo shutdown
     eth-trunk 1
     port-master
    #
    interface GigabitEthernet1/0/2
     undo shutdown
     eth-trunk 1
    #
    return

3.10.3  Example for Configuring Eth-Trunk interfaces in Static LACP Mode

Networking Requirements

To improve the bandwidth and the reliability of two devices, configure the LAG on two directly-connected Routers. As shown in Figure 3-9, the requirements are as follows:

  • m active links can implement load balancing.

  • n backup links exist between two devices. When a fault occurs on a link of active links, the backup link replaces the faulty link to keep the reliability of data transmission.

  • The preemption function is configured. When the faulty interface is recovered, this interface can become the active interface again.

Figure 3-9  Networking diagram of link aggregation in static LACP mode

Configuration Roadmap

The configuration roadmap is as follows:

  1. Create an Eth-Trunk on the Router and configure the Eth-Trunk in static LACP mode.

  2. Add member interfaces to the Eth-Trunk.

  3. Configure the system priority and determine the Actor.

  4. Configure the upper threshold for the number of active interfaces.

  5. Configure the priority of the interface and determine the active link.

  6. Configure LACP preemption and set the delay for LACP preemption.

  7. Verify the configuration.

Data Preparation

To complete the configuration, you need the following data:

  • Number of the LAG of the Routers at both ends

  • System priority of RouterA

  • Upper threshold for the number of the active interfaces

  • LACP priority of the active interface

  • Delay for LACP preemption

Procedure

  1. Create an Eth-Trunk numbered 1 and configure the operation mode of the Eth-Trunk as the static LACP mode.

    # Configure RouterA.

    <RouterA> system-view
    [RouterA] interface eth-trunk 1
    [RouterA-Eth-Trunk1] mode lacp-static
    [RouterA-Eth-Trunk1] quit

    # Configure RouterB.

    <RouterB> system-view
    [RouterB] interface eth-trunk 1
    [RouterB-Eth-Trunk1] mode lacp-static
    [RouterB-Eth-Trunk1] quit
  2. Add member interfaces to the Eth-Trunk.

    # Configure RouterA.

    [RouterA] interface gigabitethernet 1/0/1
    [RouterA-Gigabitethernet1/0/1] undo shutdown
    [RouterA-Gigabitethernet1/0/1] eth-trunk 1
    [RouterA-Gigabitethernet1/0/1] quit
    [RouterA] interface gigabitethernet 1/0/2
    [RouterA-Gigabitethernet1/0/2] undo shutdown
    [RouterA-Gigabitethernet1/0/2] eth-trunk 1
    [RouterA-Gigabitethernet1/0/2] quit
    [RouterA] interface gigabitethernet 1/0/3
    [RouterA-Gigabitethernet1/0/3] undo shutdown
    [RouterA-Gigabitethernet1/0/3] eth-trunk 1
    [RouterA-Gigabitethernet1/0/3] quit

    # Configure RouterB.

    [RouterB] interface gigabitethernet 1/0/1
    [RouterB-Gigabitethernet1/0/1] undo shutdown
    [RouterB-Gigabitethernet1/0/1] eth-trunk 1
    [RouterB-Gigabitethernet1/0/1] quit
    [RouterB] interface gigabitethernet 1/0/2
    [RouterB-Gigabitethernet1/0/2] undo shutdown
    [RouterB-Gigabitethernet1/0/2] eth-trunk 1
    [RouterB-Gigabitethernet1/0/2] quit
    [RouterB] interface gigabitethernet 1/0/3
    [RouterB-Gigabitethernet1/0/3] undo shutdown
    [RouterB-Gigabitethernet1/0/3] eth-trunk 1
    [RouterB-Gigabitethernet1/0/3] quit
  3. Set the system priority on RouterA to 100 and make RouterA as the LACP Actor.

    [RouterA] lacp priority 100

  4. Set the upper threshold M for the number of active interfaces on RouterA to 2.
    [RouterA] interface eth-trunk 1
    [RouterA-Eth-Trunk1] max active-linknumber 2
    NOTE:

    RouterA functions as the Actor and RouterB need not set the upper threshold.

  5. Set priorities of the interfaces and determine active links.

    # Configure RouterA.

    [RouterA] interface gigabitethernet 1/0/1
    [RouterA-Gigabitethernet1/0/1] lacp priority 100
    [RouterA-Gigabitethernet1/0/1] quit
    [RouterA] interface gigabitethernet 1/0/2
    [RouterA-Gigabitethernet1/0/2] lacp priority 100
    [RouterA-Gigabitethernet1/0/2] quit
    [RouterA] interface gigabitethernet 1/0/3
    [RouterA-Gigabitethernet1/0/3] lacp priority 150
    [RouterA-Gigabitethernet1/0/3] quit

    # Configure RouterB.

    [RouterB] interface gigabitethernet 1/0/1
    [RouterB-Gigabitethernet1/0/1] lacp priority 100
    [RouterB-Gigabitethernet1/0/1] quit
    [RouterB] interface gigabitethernet 1/0/2
    [RouterB-Gigabitethernet1/0/2] lacp priority 100
    [RouterB-Gigabitethernet1/0/2] quit
    [RouterB] interface gigabitethernet 1/0/3
    [RouterB-Gigabitethernet1/0/3] lacp priority 150
    [RouterB-Gigabitethernet1/0/3] quit
  6. Configure LACP preemption and set the delay for LACP preemption.

    # Configure RouterA.

    [RouterA] interface eth-trunk 1
    [RouterA-Eth-Trunk1] lacp preempt enable
    [RouterA-Eth-Trunk1] lacp preempt delay 20

    # Configure RouterB.

    [RouterB] interface eth-trunk 1
    [RouterB-Eth-Trunk1] lacp preempt enable
    [RouterB-Eth-Trunk1] lacp preempt delay 20
  7. Verify the configuration.

    # Check information about the Eth-Trunk of the Routers and check whether the negotiation succeeds or fails on the link.

    [RouterA] display eth-trunk 1
     Eth-Trunk1's state information is:
     Local:
     LAG ID: 1               WorkingMode: STATIC
     Preempt Delay: 20            Hash arithmetic: According to flow
     System Priority: 100    System ID: 00e0-fca8-0417
     Least Active-linknumber: 1   Max active-linknumber: 2
     Operate status: up           Number Of Up Port In Trunk: 2     
     -----------------------------------------------------------------------------------------
     ActorPortName          Status        PortType  PortPri PortNo  PortKey   PortState Weight
     GigabitEthernet1/0/1   Selected  1GE       100      6145    2865      11111100   1
     GigabitEthernet1/0/2   Selected  1GE       100      6146    2865      11111100   1
     GigabitEthernet1/0/3   Unselect  1GE       150      6147    2865      11100000   1
    
    
     Partner:
     ---------------------------------------------------------------------------------
     PartnerPortName        SysPri    SystemID     PortPri PortNo  PortKey   PortState
     GigabitEthernet1/0/1   32768  00e0-fca6-7f85  32768     6145  2609      11111100
     GigabitEthernet1/0/2   32768  00e0-fca6-7f85  32768     6146  2609      11111100
     GigabitEthernet1/0/3   32768  00e0-fca6-7f85  32768     6147  2609      11110000
    
    
    <RouterB> display eth-trunk 1
     Eth-Trunk1's state information is:
     Local:
     LAG ID: 1               WorkingMode: STATIC
     Preempt Delay: 20            Hash arithmetic: According to flow
     System Priority: 32768       System ID: 00e0-fca6-7f85
     Least Active-linknumber: 1   Max active-linknumber: 16
     Operate status: up           Number Of Up Port In Trunk: 2      
     ---------------------------------------------------------------------------------------------
     ActorPortName          Status         PortType  PortPri  PortNo  PortKey   PortState   Weight
     GigabitEthernet1/0/1   Selected  1GE       32768      6145    2609      11111100  1
     GigabitEthernet1/0/2   Selected  1GE       32768      6146    2609      11111100  1
     GigabitEthernet1/0/3   Unselect       1GE       32768      6147    2609      11100000  1
    
    
     Partner:
     ------------------------------------------------------------------------------
     PartnerPortName        SysPri    SystemID  PortPri PortNo  PortKey   PortState
     GigabitEthernet1/0/1   32768  00e0-fca8-0417  100     6145  2865      11111100
     GigabitEthernet1/0/2   32768  00e0-fca8-0417  100     6146  2865      11111100
     GigabitEthernet1/0/3   32768  00e0-fca8-0417  150     6147  2865      11110000

    The preceding information shows that the system priority of RouterA is 100 and it is higher than the system priority of RouterB. GE 1/0/1 and GE 1/0/2 of the Eth-Trunk become active interfaces and they are in the Selected state. GE 1/0/3 is in the Unselected state. The load balancing can be implemented on two links and the backup can be carried out on one link.

Configuration Files

  • Configuration file of RouterA

    #
     sysname RouterA
    #
     lacp priority 100
    #
    interface Eth-Trunk1
     mode lacp-static
     max active-linknumber 2
     lacp preempt enable
     lacp preempt delay 20
    #
    interface GigabitEthernet1/0/1
     undo shutdown
     eth-trunk 1
     lacp priority  100
    #
    interface GigabitEthernet1/0/2
     undo shutdown
     eth-trunk 1
     lacp priority  100
    #
    interface GigabitEthernet1/0/3
     undo shutdown
     eth-trunk 1
     lacp priority 150
    #
    return
  • Configuration file of RouterB

    #
     sysname RouterB
    #
    interface Eth-Trunk1
     mode lacp-static
    lacp preempt enable
     lacp preempt delay 20
    #
    interface GigabitEthernet1/0/1
     undo shutdown
     eth-trunk 1
    lacp priority 100
    #
    interface GigabitEthernet1/0/2
     undo shutdown
     eth-trunk 1
    lacp priority 100
    #
    interface GigabitEthernet1/0/3
     undo shutdown
     eth-trunk 1
    lacp priority 150
    #
    return

3.10.4  Example for Configuring a Layer 2 Eth-Trunk Interface to Allow VLANs to Pass Through

Networking Requirements

As shown in Figure 3-10, RouterA is connected to RouterB through Eth-Trunk 1, which is a Layer 2 interface.

Configure Eth-Trunk 1 as a trunk interface to allow all VLAN frames between RouterA and RouterB to pass through.

Figure 3-10  Configuring a Layer 2 Eth-Trunk interface to allow VLAN frames to pass through

Configuration Roadmap

The configuration roadmap is as follows:

  1. Create an Eth-Trunk interface.

  2. Switch the Eth-Trunk interface to a Layer 2 interface.

  3. Configure the Eth-Trunk interface as a trunk interface and allow all VLAN frames to pass through.

  4. Add Ethernet interfaces to the Eth-Trunk interface.

Data Preparation

To complete the configuration, you need the following data:

  • Two Eth-Trunk member interfaces GE 1/0/0 and GE 2/0/0 on RouterA

  • Two Eth-Trunk member interfaces GE 1/0/0 and GE 2/0/0 on RouterB

Procedure

  1. Configure RouterA.
    <HUAWEI> system-view
    [HUAWEI] sysname A

    # Configure the VLANs allowed on the interface.

    [RouterA] interface eth-trunk 1
    [RouterA-Eth-Trunk1] portswitch
    [RouterA-Eth-Trunk1] port link-type trunk
    [RouterA-Eth-Trunk1] port trunk allow-pass vlan all
    [RouterA-Eth-Trunk1] quit

    # Add GE 1/0/0 and GE 2/0/0 to Eth-Trunk 1.

    [RouterA] interface gigabitethernet 1/0/0
    [RouterA-GigabitEthernet1/0/0] undo shutdown
    [RouterA-GigabitEthernet1/0/0] eth-trunk 1
    [RouterA-GigabitEthernet1/0/0] quit
    [RouterA] interface gigabitethernet 2/0/0
    [RouterA-GigabitEthernet2/0/0] undo shutdown
    [RouterA-GigabitEthernet2/0/0] eth-trunk 1
    [RouterA-GigabitEthernet2/0/0] quit
  2. Configure RouterB.
    <HUAWEI> system-view
    [HUAWEI] sysname B

    # Create Eth-Trunk 1 and configure the VLANs allowed on the interface.

    [RouterB] interface eth-trunk 1
    [RouterB-Eth-Trunk1] portswitch
    [RouterB-Eth-Trunk1] port link-type trunk
    [RouterB-Eth-Trunk1] port trunk allow-pass vlan all
    [RouterB-Eth-Trunk1] quit

    # Add GE 1/0/0 and GE 2/0/0 to Eth-Trunk 1.

    [RouterB] interface gigabitethernet 1/0/0
    [RouterB-GigabitEthernet1/0/0] undo shutdown
    [RouterB-GigabitEthernet1/0/0] eth-trunk 1
    [RouterB-GigabitEthernet1/0/0] quit
    [RouterB] interface gigabitethernet 2/0/0
    [RouterB-GigabitEthernet2/0/0] undo shutdown
    [RouterB-GigabitEthernet2/0/0] eth-trunk 1
    [RouterB-GigabitEthernet2/0/0] quit
  3. Verify the configuration.

    You can view that the interface status is Up.Take the display of RouterA as an example.

    <RouterA> display trunkmembership eth-trunk 1
    Trunk ID: 1
    used status: VALID
    TYPE: ethernet
    Working Mode : Normal
    Working State: Normal
    Number Of Ports in Trunk = 2
    Number Of UP Ports in Trunk = 2
    operate status: up
    
    Interface GigabitEthernet6/0/1, valid, operate up, weight=1,
    Interface GigabitEthernet6/0/2, valid, operate up, weight=1,

    Run the display port vlan command. You can view information about the VLANs allowed on the Eth-Trunk interface. Take RouterA as an example.

    <RouterA> display port vlan Eth-Trunk 1
    Port                    Link Type      PVID       Trunk VLAN List
    -----------------------------------------------------------------
    Eth-Trunk1              trunk        0     1-4094

Configuration Files

  • Configuration file of RouterA

    #
     sysname RouterA
    #
    interface Eth-Trunk1
     portswitch
     port link-type trunk
     port trunk allow-pass vlan 1 to 4094
    #
    interface GigabitEthernet1/0/0
     undo shutdown
     eth-trunk 1
    #
    interface GigabitEthernet2/0/0
     undo shutdown
     eth-trunk 1
    #
    return
  • Configuration file of RouterB

    #
     sysname RouterB
    #
    interface Eth-Trunk1
     portswitch
     port link-type trunk
     port trunk allow-pass vlan 1 to 4094
    #
    interface GigabitEthernet1/0/0
     undo shutdown
     eth-trunk 1
    #
    interface GigabitEthernet2/0/0
     undo shutdown
     eth-trunk 1
    #
    return

3.10.5  Example for Configuring a Layer 3 Eth-Trunk Interface in Manual Load Balancing Mode

Networking Requirements

As shown in Figure 3-11, an Eth-Trunk interface that is bound from two GE interfaces is created between RouterA and RouterB.

Figure 3-11  Networking diagram of configuring a Layer 3 Eth-Trunk interface

Configuration Roadmap

The configuration roadmap is as follows:

  1. Create an Eth-Trunk interface and configure an IP address for it.

  2. Add Ethernet interfaces to the Eth-Trunk interface.

Data Preparation

To complete the configuration, you need the following data:

  • Layer 3 GE interface through which RouterA is connected to RouterB

  • IP address of the Eth-Trunk interface on RouterA

  • IP address of the Eth-Trunk interface on RouterB

Procedure

  1. Configure RouterA.
    <HUAWEI> system-view
    [HUAWEI] sysname RouterA

    # Create an Eth-Trunk interface and configure an IP address for it.

    [RouterA] interface eth-trunk 1
    [RouterA-Eth-Trunk1] ip address 100.1.1.1 24
    [RouterA-Eth-Trunk1] quit

    # Add GE 1/0/0 and GE 2/0/0 to Eth-Trunk 1.

    [RouterA] interface gigabitethernet 1/0/0
    [RouterA-GigabitEthernet1/0/0] undo shutdown
    [RouterA-GigabitEthernet1/0/0] eth-trunk 1
    [RouterA-GigabitEthernet1/0/0] quit
    [RouterA] interface gigabitethernet 2/0/0
    [RouterA-GigabitEthernet2/0/0] undo shutdown
    [RouterA-GigabitEthernet2/0/0] eth-trunk 1
    [RouterA-GigabitEthernet2/0/0] quit
  2. Configure RouterB.
    <HUAWEI> system-view
    [HUAWEI] sysname RouterB

    # Create an Eth-Trunk interface and configure an IP addresses for it.

    [RouterB] interface eth-trunk 1
    [RouterB-Eth-Trunk1] ip address 100.1.1.2 24
    [RouterB-Eth-Trunk1] quit

    # Add GE 1/0/0 and GE 2/0/0 to Eth-Trunk 1.

    [RouterB] interface gigabitethernet 1/0/0
    [RouterB-GigabitEthernet1/0/0] undo shutdown
    [RouterB-GigabitEthernet1/0/0] eth-trunk 1
    [RouterB-GigabitEthernet1/0/0] quit
    [RouterB] interface gigabitethernet 2/0/0
    [RouterB-GigabitEthernet2/0/0] undo shutdown
    [RouterB-GigabitEthernet2/0/0] eth-trunk 1
    [RouterB-GigabitEthernet2/0/0] quit
  3. Verify the configuration.

    Run the display interface eth-trunk command. You can view that the interface status is Up.

    Take the display of RouterA as an example.

    [RouterA] display interface eth-trunk 1
    Eth-Trunk1 current state : UP
    Line protocol current state : UP
    Last line protocol up time: 2008-04-02, 11:00:19
    Description : Eth-Trunk1 Interface
    
    
    Internet Address is 100.1.1.1/24
    IP Sending Frames' Format is PKTFMT_ETHNT_2, Hardware address is 00e0-fc09-9722
    Physical is ETH_TRUNK
        Last 300 seconds input rate 0 bytes/sec, 0 packets/sec
        Last 300 seconds output rate 0 bytes/sec, 0 packets/sec
        Input:     1 packets,3 bytes,
                   7 unicast,9 broadcast,8 multicasts
                   10 errors,5 drops,11 unknowprotocol
        Output:   2 packets,4 bytes,
                   12 unicast,14 broadcast,13x multicasts
                   15 errors,6 drops
    -----------------------------------------------------
    PortName                Status              Weight
    -----------------------------------------------------
    GigabitEthernet1/0/0    UP                  1
    GigabitEthernet2/0/0    UP                  1
    -----------------------------------------------------
    The Number of Ports in Trunk : 2
    The Number of UP Ports in Trunk : 2 

    Eth-Trunk interfaces on RouterA and RouterB can ping through each other.

    [RouterA] ping -a 100.1.1.1 100.1.1.2
      PING 100.1.1.2: 56  data bytes, press CTRL_C to break
        Reply from 100.1.1.2: bytes=56 Sequence=1 ttl=255 time=31 ms
        Reply from 100.1.1.2: bytes=56 Sequence=2 ttl=255 time=31 ms
        Reply from 100.1.1.2: bytes=56 Sequence=3 ttl=255 time=62 ms
        Reply from 100.1.1.2: bytes=56 Sequence=4 ttl=255 time=62 ms
        Reply from 100.1.1.2: bytes=56 Sequence=5 ttl=255 time=62 ms
    
    
      --- 100.1.1.2 ping statistics ---
        5 packet(s) transmitted
        5 packet(s) received
        0.00% packet loss
        round-trip min/avg/max = 31/49/62 ms

Configuration Files

  • Configuration file of RouterA

    #
     sysname RouterA
    #
    interface Eth-Trunk1
     ip address 100.1.1.1 255.255.255.0
    #
    interface GigabitEthernet1/0/0
     undo shutdown
     eth-trunk 1
    #
    interface GigabitEthernet2/0/0
     undo shutdown
     eth-trunk 1
    #
    return
  • Configuration file of RouterB

    #
     sysname RouterB
    #
    interface Eth-Trunk1
     ip address 100.1.1.2 255.255.255.0
    #
    interface GigabitEthernet1/0/0
     undo shutdown
     eth-trunk 1
    #
    interface GigabitEthernet2/0/0
     undo shutdown
     eth-trunk 1
    #
    return

3.10.6  Example for Configuring VLANs to Communicate Through Eth-Trunk Sub-interfaces

Networking Requirements

As shown in Figure 3-12, RouterA is connected to RouterB through Eth-Trunk 1, and RouterB is connected to RouterC through Eth-Trunk 2.

Configure VLAN 10 on RouterA and VLAN 20 on RouterC.

Create a sub-interface on RouterB so that VLAN 10 and VLAN 20 can communicate through the Eth-Trunk sub-interface.

Figure 3-12  Networking diagram of configuring VLANs to communicate through Eth-Trunk sub-interfaces

Configuration Roadmap

The configuration roadmap is as follows:

  1. On RouterB, create an Eth-Trunk sub-interface and configure an IP address for it.

  2. Configure the encapsulation mode of each Eth-Trunk sub-interface as 802.1Q and configure the associated VLANs.

  3. Configure Eth-Trunk interfaces on RouterA and RouterC as Layer 2 interfaces and allow VLAN frames to pass through.

Data Preparation

To complete the configuration, you need the following data:

  • Two member interfaces GE 1/0/0 and GE 2/0/0 of a Layer 2 interface Eth-Trunk 1 on RouterA

  • Two member interfaces GE 1/0/0 and GE 2/0/0 of a Layer 3 interface Eth-Trunk 1 on RouterB

  • Two member interfaces GE 1/0/1 and GE 2/0/1 of a Layer 3 interface Eth-Trunk 2 on RouterB

  • Two member interfaces GE 1/0/0 and GE 2/0/0 of a Layer 2 interface Eth-Trunk 2 on RouterC

  • VLAN 10 associated with sub-interface Eth-Trunk 1.1 and VLAN 20 associated with Eth-Trunk 2.1 on RouterB

  • IP address 10.110.1.10 of sub-interface Eth-Trunk 1.1 and IP address 10.110.2.10 of sub-interface Eth-Trunk 2.1

Procedure

  1. Configure RouterA.
    <HUAWEI> system-view
    [HUAWEI] sysname RouterA

    # Create Eth-Trunk 1 and configure the VLANs allowed on the interface.

    [RouterA] interface eth-trunk 1
    [RouterA-Eth-Trunk1] portswitch
    [RouterA-Eth-Trunk1] port link-type trunk
    [RouterA-Eth-Trunk1] port trunk allow-pass vlan 10
    [RouterA-Eth-Trunk1] quit

    # Add GE 1/0/0 and GE 2/0/0 to Eth-Trunk 1.

    [RouterA] interface gigabitethernet 1/0/0
    [RouterA-GigabitEthernet1/0/0] undo shutdown
    [RouterA-GigabitEthernet1/0/0] eth-trunk 1
    [RouterA-GigabitEthernet1/0/0] quit
    [RouterA] interface gigabitethernet 2/0/0
    [RouterA-GigabitEthernet2/0/0] undo shutdown
    [RouterA-GigabitEthernet2/0/0] eth-trunk 1
    [RouterA-GigabitEthernet2/0/0] quit
  2. Configure RouterC.
    <HUAWEI> system-view
    [HUAWEI] sysname RouterC

    # Create Eth-Trunk 2 and configure the VLANs allowed on the interface.

    [RouterC] interface eth-trunk 2
    [RouterC-Eth-Trunk2] portswitch
    [RouterC-Eth-Trunk2] port link-type trunk
    [RouterC-Eth-Trunk2] port trunk allow-pass vlan 20
    [RouterC-Eth-Trunk2] quit

    # Add GE 2/0/0 and GE 2/0/0 to Eth-Trunk 2.

    [RouterC] interface gigabitethernet 1/0/0
    [RouterC-GigabitEthernet1/0/0] undo shutdown
    [RouterC-GigabitEthernet1/0/0] eth-trunk 2
    [RouterC-GigabitEthernet1/0/0] quit
    [RouterC] interface gigabitethernet 2/0/0
    [RouterC-GigabitEthernet2/0/0] undo shutdown
    [RouterC-GigabitEthernet2/0/0] eth-trunk 2
    [RouterC-GigabitEthernet2/0/0] quit
  3. Configure RouterB.
    <HUAWEI> system-view
    [HUAWEI] sysname RouterB

    # Create Eth-Trunk 1.

    [RouterB] interface eth-trunk 1
    [RouterB-Eth-Trunk1] quit

    # Add GE 1/0/0 and GE 2/0/0 to Eth-Trunk 1.

    [RouterB] interface gigabitethernet 1/0/0
    [RouterB-GigabitEthernet1/0/0] undo shutdown
    [RouterB-GigabitEthernet1/0/0] eth-trunk 1
    [RouterB-GigabitEthernet1/0/0] quit
    [RouterB] interface gigabitethernet 2/0/0
    [RouterB-GigabitEthernet2/0/0] undo shutdown
    [RouterB-GigabitEthernet2/0/0] eth-trunk 1
    [RouterB-GigabitEthernet2/0/0] quit

    # Create Eth-Trunk 1.1 and configure an IP addresses for it.

    [RouterB] interface eth-trunk 1.1
    [RouterB-Eth-Trunk1.1] ip address 10.110.1.10 24

    # Configure Eth-Trunk 1.1 to be encapsulated with 802.1Q and be associated with VLAN 10.

    [RouterB-Eth-Trunk1.1] vlan-type dot1q 10
    [RouterB-Eth-Trunk1.1] quit

    # Create Eth-Trunk 2.

    [RouterB] interface eth-trunk 2
    [RouterB-Eth-Trunk2] quit

    # Add GE 1/0/1 and GE 2/0/1 to Eth-Trunk 2.

    [RouterB] interface gigabitethernet 1/0/1
    [RouterB-GigabitEthernet1/0/1] undo shutdown
    [RouterB-GigabitEthernet1/0/1] eth-trunk 2
    [RouterB-GigabitEthernet1/0/1] quit
    [RouterB] interface gigabitethernet 2/0/1
    [RouterB-GigabitEthernet2/0/1] undo shutdown
    [RouterB-GigabitEthernet2/0/1] eth-trunk 2
    [RouterB-GigabitEthernet2/0/1] quit

    # Create Eth-Trunk 2.1 and configure an IP addresses for it.

    [RouterB] interface eth-trunk 2.1
    [RouterB-Eth-Trunk2.1] ip address 10.110.2.10 24

    # Configure Eth-Trunk 2.1 to be encapsulated with 802.1Q and be associated with VLAN 20.

    [RouterB-Eth-Trunk2.1] vlan-type dot1q 20
    [RouterB-Eth-Trunk2.1] quit
  4. Verify the configuration.

    On the hosts in VLAN 10, configure the IP address of the host to be in the same network segment as the address of Eth-Trunk 1.1 and configure the default gateway address as the IP address 10.110.1.10/24 of Eth-Trunk 1.1.

    On the host in VLAN 20, configure the IP address of the host to be in the same network segment as the address of Eth-Trunk 2.1 and configure the default gateway address as the IP address 10.110.2.10/24 of Eth-Trunk 2.1.

    After the configuration, the hosts between VLAN 10 and VLAN 20 can ping through each other.

Configuration Files

  • Configuration file of RouterA

    #
     sysname RouterA
    #
    interface Eth-Trunk1
     portswitch
     port link-type trunk
     port trunk allow-pass vlan 10
    #
    interface GigabitEthernet1/0/0
     undo shutdown
     eth-trunk 1
    #
    interface GigabitEthernet2/0/0
     undo shutdown
     eth-trunk 1
    #
    return
  • Configuration file of RouterB

    #
     sysname RouterB
    #
    interface Eth-Trunk1
    #
    interface Eth-Trunk1.1
     vlan-type dot1q 10
     ip address 10.110.1.10 255.255.255.0
    #
    interface Eth-Trunk2
    #
    interface Eth-Trunk2.1
     vlan-type dot1q 20
     ip address 10.110.2.10 255.255.255.0
    #
    interface GigabitEthernet1/0/0
     undo shutdown
     eth-trunk 1
    #
    interface GigabitEthernet1/0/1
     undo shutdown
     eth-trunk 2
    #
    interface GigabitEthernet2/0/0
     undo shutdown
     eth-trunk 1
    #
    interface GigabitEthernet2/0/1
     undo shutdown
     eth-trunk 2
    #
    return
  • Configuration file of RouterC

    #
     sysname RouterC
    #
    interface Eth-Trunk2
     portswitch
     port link-type trunk
     port trunk allow-pass vlan 20
    #
    interface GigabitEthernet1/0/0
     undo shutdown
     eth-trunk 2
    #
    interface GigabitEthernet2/0/0
     undo shutdown
     eth-trunk 2
    #
    return
    
    

3.10.7  Example for Connecting an E-Trunk to a VPLS Network

Networking Requirements

As shown in Figure 3-13, the CE is connected to PE1 and PE2 through an Eth-Trunk, and is dual-homed to a VPLS network.

In normal situations, the CE communicates with devices in the VPLS network through PE1. If the Eth-Trunk between the CE and PE1 becomes faulty, or PE1 becomes faulty, the CE is no longer able to communicate with PE1. To prevent services from being interrupted, E-Trunk protocol needs to be deployed on PE1 and PE2 so that traffic sent by the CE can be switched from PE1 to PE2, and that the CE can continue to communicate with devices in the VPLS network through PE2.

When the fault on the Eth-Trunk between the CE and PE1 or on PE1 is rectified, traffic is switched back to PE1. In this manner, the E-Trunk protocol can backup the link aggregation group between PE1 and PE2, thus enhancing the network stability.

Figure 3-13  Networking diagram of the E-Trunk

Enhanced Trunk (E-Trunk), developed from the Link Aggregation Control Protocol (LACP) for a single device, is the protocol that controls and implements link aggregation among multiple devices. E-Trunk can achieve the device-level link reliability, instead of the board-level link reliability achieved by LACP.

E-Trunk is mainly applied to the scenario that a CE is dual homed to the VPLS, VLL, or PWE3 network (a CE is connected to double PEs). In the scenario, E-Trunk can be used to protect the PEs and the links between the CE and PEs through the link and PE switchover.

Configuration Roadmap

The configuration roadmap is as follows:

  1. Connect the CE to the VLPS network as follows:

    • Run IGP to ensure the connectivity of routers on the backbone network.

    • Run a routing protocol to ensure connectivity of routes on the backbone network, enable basic MPLS capabilities, and set up an LSP tunnel between the PEs.

    • Enable MPLS L2VPN on the PEs.

    • Set up a VSI and then configure the VSI.

  2. Configure the E-Trunk as follows:

    • Create an Eth-Trunk between the CE and PE1 and between the CE and PE2 separately. Set the two Eth-Trunks to static LACP mode and add members to the two Eth-Trunks.

    • Create an E-Trunk on PE1 and PE2 and add the two static LACP Eth-Trunks to the E-Trunk.

    • Configure the E-Trunk as follows:

      • Priority

      • LACP system ID and priority

      • Period of sending Hello packets

      • Time multiplier for detecting Hello packets

      • Local and peer IP addresses in the E-Trunk

  3. Verify the configuration.

Data Preparation

To complete the configuration, you need the following data:

  • VSI IDs on PEs (they must be consistent)

  • MPLS LSR ID of each PE

  • Names of the VSIs on PE1 and PE2

  • Interfaces to which the VSIs are bound

  • Priority of an E-Trunk

  • LACP system ID and priority of an E-Trunk

  • Interface numbers and work modes of the Eth-Trunk

  • Local and peer IP addresses

  • Period of sending Hello packets and time multiplier for detecting Hello packets

Procedure

  1. Configure a VPLS network.
    1. Configure IGP over the MPLS backbone network. OSPF is used as the IGP protocol in this example.

      Assign an IP address to each interface on the PEs as shown in Figure 3-13. When configuring OSPF, you need to configure PEs to advertise the 32-bit addresses of loopback interfaces.

      # Configure PE1.

      <PE1> system-view
      [PE1] interface loopback 1
      [PE1-LoopBack1] ip address 1.1.1.9 32
      [PE1-LoopBack1] quit
      [PE1] interface gigabitethernet 1/0/1
      [PE1-GigabitEthernet1/0/1] undo shutdown
      [PE1-GigabitEthernet1/0/1] ip address 100.1.1.1 30
      [PE1-GigabitEthernet1/0/1] quit
      [PE1] ospf
      [PE1-ospf-1] area 0
      [PE1-ospf-1-area-0.0.0.0] network 1.1.1.9 0.0.0.0
      [PE1-ospf-1-area-0.0.0.0] network 100.1.1.0 0.0.0.3
      [PE1-ospf-1-area-0.0.0.0] quit
      [PE1-ospf-1] quit

      # Configure PE2.

      <PE2> system-view
      [PE2] interface loopback 1
      [PE2-LoopBack1] ip address 2.2.2.9 32
      [PE2-LoopBack1] quit
      [PE2] interface gigabitethernet 1/0/2
      [PE2-GigabitEthernet1/0/2] undo shutdown
      [PE2-GigabitEthernet1/0/2] ip address 100.1.1.2 30
      [PE2-GigabitEthernet1/0/2] quit
      [PE2] ospf
      [PE2-ospf-1] area 0
      [PE2-ospf-1-area-0.0.0.0] network 2.2.2.9 0.0.0.0
      [PE2-ospf-1-area-0.0.0.0] network 100.1.1.0 0.0.0.3
      [PE2-ospf-1-area-0.0.0.0] quit
      [PE2-ospf-1] quit

      After the configuration, PE1 and PE2 discover IP routes of the peer loopback1 through OSPF. PE1 and PE2 can ping through each other.

      Take the display on PE1 as an example.

      <PE1> display ip routing-table
      Route Flags: R - relay, D - download to fib
      ------------------------------------------------------------------------------
      Routing Tables: Public
               Destinations : 6        Routes : 6
      
      Destination/Mask    Proto  Pre  Cost     Flags NextHop         Interface
      
              1.1.1.9/32  Direct 0    0        D     127.0.0.1       InLoopBack0
              2.2.2.9/32  OSPF   10   1        D     100.1.1.2       GigabitEthernet1/0/1
            100.1.1.0/30  Direct 0    0        D     100.1.1.1       GigabitEthernet1/0/1
            100.1.1.1/32  Direct 0    0        D     127.0.0.1       InLoopBack0
            127.0.0.0/8   Direct 0    0        D     127.0.0.1       InLoopBack0
            127.0.0.1/32  Direct 0    0        D     127.0.0.1       InLoopBack0 
      
      <PE1> ping 2.2.2.9
      PING 2.2.2.9: 56  data bytes, press CTRL_C to break
          Reply from 2.2.2.9: bytes=56 Sequence=1 ttl=255 time=260 ms
          Reply from 2.2.2.9: bytes=56 Sequence=2 ttl=255 time=30 ms
          Reply from 2.2.2.9: bytes=56 Sequence=3 ttl=255 time=50 ms
          Reply from 2.2.2.9: bytes=56 Sequence=4 ttl=255 time=30 ms
          Reply from 2.2.2.9: bytes=56 Sequence=5 ttl=255 time=60 ms
      
        --- 2.2.2.9 ping statistics ---
          5 packet(s) transmitted
          5 packet(s) received
          0.00% packet loss
          round-trip min/avg/max = 30/86/260 ms  
    2. Enable basic MPLS capabilities and LDP over the MPLS backbone network.

      # Configure PE1.

      [PE1] mpls lsr-id 1.1.1.9
      [PE1] mpls
      [PE1-mpls] quit
      [PE1] mpls ldp
      [PE1-mpls-ldp] quit
      [PE1] interface gigabitethernet 1/0/1
      [PE1-GigabitEthernet1/0/1] mpls
      [PE1-GigabitEthernet1/0/1] mpls ldp
      [PE1-GigabitEthernet1/0/1] quit

      # Configure PE2.

      [PE2] mpls lsr-id 2.2.2.9
      [PE2] mpls
      [PE2-mpls] quit
      [PE2] mpls ldp
      [PE2-mpls-ldp] quit
      [PE2] interface gigabitethernet 1/0/2
      [PE2-GigabitEthernet1/0/2] mpls
      [PE2-GigabitEthernet1/0/2] mpls ldp
      [PE2-GigabitEthernet1/0/2] quit

      After the preceding configuration, LDP sessions are set up between the PEs. Run the display mpls ldp session command. The command output shows that the Status field displays Operational. Run the display mpls ldp lsp command, and you can check whether LDP LSPs are set up.

      Take the display on PE1 as an example.

      <PE1> display mpls ldp session
       LDP Session(s) in Public Network 
       Codes: LAM(Label Advertisement Mode), SsnAge Unit(DDDD:HH:MM)
       A '*' before a session means the session is being deleted.
       ------------------------------------------------------------------------------
       Peer-ID            Status      LAM  SsnRole  SsnAge      KA-Sent/Rcv
       ------------------------------------------------------------------------------
       2.2.2.9:0          Operational DU   Passive  000:00:00   1/1
       ------------------------------------------------------------------------------
       TOTAL: 1 session(s) Found.
      <PE1> display mpls ldp lsp
       LDP LSP Information
       ----------------------------------------------------------------------------------------------------
       DestAddress/Mask   In/OutLabel   NextHop         OutInterface   UpstreamPeer
       ----------------------------------------------------------------------------------------------------
       1.1.1.9/32         3/NULL        127.0.0.1       InLoop0        2.2.2.9
      *1.1.1.9/32         Liberal
       2.2.2.9/32         NULL/3        100.1.1.2       GE1/0/1        -
       2.2.2.9/32         1024/3        100.1.1.2       GE1/0/1/       2.2.2.9
       ----------------------------------------------------------------------------------------------------
       TOTAL: 3 Normal LSP(s) Found.
       TOTAL: 1 Liberal LSP(s) Found.
       A '*' before an LSP means the LSP is not established 
       A '*' before a Label means the USCB or DSCB is stale 
       A '*' before a UpstreamPeer means the session is in GR state
      NOTE:

      If PEs are indirectly connected, you need to run the mpls ldp remote-peer command and the remote-ip command to set up remote LDP sessions between the PEs.

    3. Enable MPLS L2VPN on the PEs.

      # Configure PE1.

      [PE1] mpls l2vpn
      [PE1-l2vpn] quit

      # Configure PE2.

      [PE2] mpls l2vpn
      [PE2-l2vpn] quit
    4. Create VSIs and specify LDP as the signaling protocol of VSIs.

      # Configure PE1.

      [PE1] vsi ldp1 static
      [PE1-vsi-ldp1] pwsignal ldp
      [PE1-vsi-ldp1-ldp] vsi-id 2
      [PE1-vsi-ldp1-ldp] peer 2.2.2.9
      [PE1-vsi-ldp1-ldp] mac-withdraw enable
      [PE1-vsi-ldp1-ldp] interface-status-change mac-withdraw enable
      [PE1-vsi-ldp1-ldp] quit
      [PE1-vsi-ldp1] ignore-ac-state
      [PE1-vsi-ldp1] quit

      # Configure PE2.

      [PE2] vsi ldp1 static
      [PE2-vsi-ldp1] pwsignal ldp
      [PE2-vsi-ldp1-ldp] vsi-id 2
      [PE2-vsi-ldp1-ldp] peer 1.1.1.9
      [PE2-vsi-ldp1-ldp] mac-withdraw enable
      [PE2-vsi-ldp1-ldp] interface-status-change mac-withdraw enable
      [PE2-vsi-ldp1-ldp] quit
      [PE2-vsi-ldp1] ignore-ac-state
      [PE2-vsi-ldp1] quit
      CAUTION:
      The ignore-ac-state command is configured to prevent VSI status from being affected by the Attachment Circuit (AC) status. Though no AC is connected to the VSI, the VSI can still be Up. Be cautious to use the ignore-ac-state command.
    5. Configure Eth-Trunk sub-interfaces on PEs and bind VSIs to AC interfaces.

      # Configure PE1.

      [PE1] interface Eth-Trunk 10
      [PE1-Eth-Trunk10] quit
      [PE1] interface Eth-Trunk 10.1
      [PE1-Eth-Trunk10.1] vlan-type dot1q 1
      [PE1-Eth-Trunk10.1] l2 binding vsi ldp1
      [PE1-Eth-Trunk10.1] undo shutdown
      [PE1-Eth-Trunk10.1] quit

      # Configure PE2.

      [PE2] interface Eth-Trunk 10
      [PE2-Eth-Trunk10] quit
      [PE2] interface Eth-Trunk 10.1
      [PE2-Eth-Trunk10.1] vlan-type dot1q 1
      [PE2-Eth-Trunk10.1] l2 binding vsi ldp1
      [PE2-Eth-Trunk10.1] undo shutdown
      [PE2-Eth-Trunk10.1] quit
    6. Configure Layer 2 forwarding on the CE.

      # Add Eth-Trunk 20 to VLAN 1.

      <HUAWEI> system-view
      [HUAWEI] sysname CE
      [CE] interface Eth-Trunk 20
      [CE-Eth-Trunk20] portswitch
      [CE-Eth-Trunk20] quit
      [CE] vlan 1
      [CE-vlan1] port Eth-Trunk 20
      [CE-vlan1] quit
      [CE] interface Eth-Trunk 20
      [CE-Eth-Trunk20] port trunk allow-pass vlan 1

      # Configure the work mode of Eth-Trunk 20 as the static LACP mode.

      [CE-Eth-Trunk20] mode lacp-static
      [CE-Eth-Trunk20] quit

      # Add the member interface to Eth-Trunk 20.

      [CE] interface gigabitethernet 1/0/1
      [CE-GigabitEthernet1/0/1] undo shutdown
      [CE-GigabitEthernet1/0/1] eth-trunk 20
      [CE-GigabitEthernet1/0/1] quit
      [CE] interface gigabitethernet 1/0/2
      [CE-GigabitEthernet1/0/2] undo shutdown
      [CE-GigabitEthernet1/0/2] eth-trunk 20
      [CE-GigabitEthernet1/0/2] quit
      
      
  2. Configure the E-Trunk.
    1. Create the Eth-Trunk numbered 10 and configure the work mode of the Eth-Trunk as the static LACP mode.

      # Configure PE1.

      [PE1] interface eth-trunk 10
      [PE1-Eth-Trunk10] mode lacp-static
      [PE1-Eth-Trunk10] quit

      # Configure PE2.

      [PE2] interface eth-trunk 10
      [PE2-Eth-Trunk10] mode lacp-static
      [PE2-Eth-Trunk10] quit
    2. Add member interfaces to the Eth-Trunk.

      # Configure PE1.

      [PE1] interface gigabitethernet 1/0/2
      [PE1-GigabitEthernet1/0/2] undo shutdown
      [PE1-GigabitEthernet1/0/2] eth-trunk 10
      [PE1-GigabitEthernet1/0/2] quit

      # Configure PE2.

      [PE2] interface gigabitethernet 1/0/1
      [PE2-GigabitEthernet1/0/1] undo shutdown
      [PE2-GigabitEthernet1/0/1] eth-trunk 10
      [PE2-GigabitEthernet1/0/1] quit
    3. Configure the E-Trunk and add the two static LACP Eth-Trunks to the E-Trunk.

      # Configure PE1.

      [PE1] e-trunk 1
      [PE1-e-trunk-1] quit
      [PE1] interface eth-trunk 10
      [PE1-Eth-Trunk10] e-trunk 1
      [PE1-Eth-Trunk10] quit

      # Configure PE2.

      [PE2] e-trunk 1
      [PE2-e-trunk-1] quit
      [PE2] interface eth-trunk 10
      [PE2-Eth-Trunk10] e-trunk 1
      [PE2-Eth-Trunk10] quit
    4. Configure the E-Trunk attributes.
      • Configure the priority of the E-Trunk.

        # Configure PE1.

        [PE1] e-trunk 1
        [PE1-e-trunk-1] priority 10
        [PE1-e-trunk-1] quit

        # Configure PE2.

        [PE2] e-trunk 1
        [PE2-e-trunk-1] priority 20
        [PE2-e-trunk-1] quit
      • Configure the LACP system ID and priority of the E-Trunk.

        # Configure PE1.

        [PE1] lacp e-trunk priority 1
        [PE1] lacp e-trunk system-id 00E0-FC00-0000

        # Configure PE2.

        [PE2] lacp e-trunk priority 1
        [PE2] lacp e-trunk system-id 00E0-FC00-0000

        The LACP system IDs and priorities in the same E-Trunk must be consistent between PE1 and PE2.

      • Configure the multiple of the time for the E-Trunk to detect Hello packets.

        # Configure PE1.

        [PE1] e-trunk 1
        [PE1-e-trunk-1] timer hold-on-failure multiplier 3

        # Configure PE2.

        [PE2] e-trunk 1
        [PE2-e-trunk-1] timer hold-on-failure multiplier 3
      • Configure the period for the E-Trunk to send Hello packets.

        # Configure PE1.

        [PE1-e-trunk-1] timer hello 9

        # Configure PE2.

        [PE2-e-trunk-1] timer hello 9
    5. Configure the local and peer IP addresses in the E-Trunk.

      # Configure PE1.

      [PE1-e-trunk-1] peer-address 100.1.1.2 source-address 100.1.1.1
      [PE1-e-trunk-1] quit

      # Configure PE2.

      [PE2-e-trunk-1] peer-address 100.1.1.1 source-address 100.1.1.2
      [PE2-e-trunk-1] quit
    6. Bind the E-Trunk to the BFD session.

      • Create a BFD session.

        # Configure PE1.

        [PE1] bfd
        [PE1-bfd] quit
        [PE1] bfd hello bind peer-ip 100.1.1.2 source-ip 100.1.1.1
        [PE1-bfd-session-hello] discriminator local 1
        [PE1-bfd-session-hello] discriminator remote 2
        [PE1-bfd-session-hello] commit
        [PE1-bfd-session-hello] quit

        The local and peer IP addresses to which the BFD session is bound must be consistent with the local and peer IP addresses in the E-Trunk.

        # Configure PE2.

        [PE2] bfd
        [PE2-bfd] quit
        [PE2] bfd hello bind peer-ip 100.1.1.1 source-ip 100.1.1.2
        [PE2-bfd-session-hello] discriminator local 2
        [PE2-bfd-session-hello] discriminator remote 1
        [PE2-bfd-session-hello] commit
        [PE2-bfd-session-hello] quit
      • Bind the E-Trunk to the BFD session.

        # Configure PE1.

        [PE1] e-trunk 1
        [PE1-e-trunk-1] e-trunk track bfd-session 1
        [PE1-e-trunk-1] quit

        # Configure PE2.

        [PE2] e-trunk 1
        [PE2-e-trunk-1] e-trunk track bfd-session 2
        [PE2-e-trunk-1] quit

        After the configuration, run the display bfd session all verbose command on PE1 and PE2. The command output shows that the BFD session is set up and its status is Up.

        Take the display on PE1 as an example.

        <PE1> display bfd session all verbose 
        --------------------------------------------------------------------------------
        Session MIndex : 256       (Multi Hop) State : Up        Name : hello
        --------------------------------------------------------------------------------
          Local Discriminator    : 1                Remote Discriminator   : 2
          Session Detect Mode    : Asynchronous Mode Without Echo Function
          BFD Bind Type          : Peer IP Address
          Bind Session Type      : Static
          Bind Peer IP Address   : 100.1.1.2
          Bind Interface         : -
          Bind Source IP Address : 100.1.1.1
          FSM Board Id           : 1                TOS-EXP                : 7
          Min Tx Interval (ms)   : 1000             Min Rx Interval (ms)   : 1000
          Actual Tx Interval (ms): -                Actual Rx Interval (ms): -
          Local Detect Multi     : 3                Detect Interval (ms)   : -
          Echo Passive           : Disable          Acl Number             : -
          Destination Port       : 3784             TTL                    : 254
          Proc Interface Status  : Disable          Process PST            : Disable
          WTR Interval (ms)      : -                Local Demand Mode      : Disable
          Last Local Diagnostic  : No Diagnostic
          Bind Application       : E-TRUNK 
          Session TX TmrID       : -                Session Detect TmrID   : -
          Session Init TmrID     : -                Session WTR TmrID      : -
          Session Echo Tx TmrID  : -
          PDT Index              : FSM-0 | RCV-0 | IF-0 | TOKEN-0
          Session Description    : -
        --------------------------------------------------------------------------------
        
             Total UP/DOWN Session Number : 1/0
  3. Verify the configuration.

    # Run the display eth-trunk command on the CE to check the configurations of the Eth-Trunk interfaces.

    <CE> display eth-trunk 20
    Eth-Trunk10's state information is:
    Local:
    LAG ID: 20                  WorkingMode: STATIC
    Preempt Delay: Disabled     Hash arithmetic: According to flow
    System Priority: 32768      System ID: 00e0-657a-6300
    Least Active-linknumber: 1  Max Active-linknumber: 16
    Operate status: up          Number Of Up Port In Trunk: 1
    --------------------------------------------------------------------------------
    ActorPortName                 Status   PortType PortPri PortNo PortKey PortState Weight
    GigabitEthernet1/0/1          Selected 100M     32768   128    2593    11111100  1
    GigabitEthernet1/0/2          Unselect 100M     32768   129    2593    11100010  1
    
    Partner:
    --------------------------------------------------------------------------------
    ActorPortName              SysPri    SystemID       PortPri PortNo  PortKey   PortState
    GigabitEthernet1/0/1          1      00e0-fc00-0000  32768  129     2593      11111100
    GigabitEthernet1/0/2          1      00e0-fc00-0000  32768  32896   2593      11010000
    

    The command output shows on the CE that the member interfaces GigabitEthernet 1/0/1 and GigabitEthernet 1/0/2 are in the Selected and Unselect state respectively.

    # Run the display e-trunk command to check configurations of the E-Trunk.

    <PE1> display e-trunk 1
                   The E-Trunk information
    E-TRUNK-ID            : 1              Revert-Delay-Time (s) : 120 
    Priority               : 10             System-ID             : 00e0-0f74-eb00
    Peer-IP                : 100.1.1.2      Source-IP             : 100.1.1.1
    State                  : Master         Causation             : PRI
    Send-Period (100ms)    : 9              Fail-Time (100ms)     : 27
    Receive                : 41             Send                  : 42
    RecDrop                : 0              SndDrop               : 0
    Peer-Priority          : 20             Peer-System-ID        : 00e0-3b6c-6100
    Peer-Fail-Time (100ms) : 27             BFD-Session           : 1
    --------------------------------------------------------------------------------
                    The Member information
    Type        ID  LocalPhyState   Work-Mode      State    Causation
    Eth-Trunk   10  Up              auto           Master   PEER_MEMBER_DOWN
    
    

    <PE2> display e-trunk 1

                    The E-Trunk information
    E-TRUNK-ID            : 1              Revert-Delay-Time (s) : 120 
    Priority               : 20             System-ID             : 00e0-3b6c-6100
    Peer-IP                : 100.1.1.1      Source-IP             : 100.1.1.2
    State                  : Backup         Causation             : PRI
    Send-Period (100ms)    : 9              Fail-Time (100ms)     : 27
    Receive                : 43            Send                  : 42
    RecDrop                : 3             SndDrop               : 0
    Peer-Priority          : 10             Peer-System-ID        : 00e0-0f74-eb00
    Peer-Fail-Time (100ms) : 27             BFD-Session           : 2
    --------------------------------------------------------------------------------
                     The Member information
    Type        ID  LocalPhyState   Work-Mode      State    Causation
    Eth-Trunk   10  Down            auto           Backup   PEER_MEMBER_UP 

    The command output shows priority of the E-Trunk on PE1 is 10 and the E-Trunk is in the Master state. The priority of the E-Trunk on PE2 is 20 and the E-Trunk is in the Backup state. In this manner, the link backup is implemented.

    # Run the display vsi name ldp1 verbose command to check PW information.

    Take the display on PE1 as an example.

     ***VSI Name               : ldp1
        Administrator VSI      : no
        Isolate Spoken         : disable
        VSI Index              : 0
        PW Signaling           : ldp
        Member Discovery Style : static
        PW MAC Learn Style     : unqualify
        Encapsulation Type     : vlan
        MTU                    : 1500
        Diffserv Mode          : uniform
        Service Class          : --
        Color                  : --
        DomainId               : 255
        Domain Name            :
        Ignore AcState         : enable 
        Create Time            : 0 days, 0 hours, 32 minutes, 30 seconds
        VSI State              : up
    
        VSI ID                 : 2
        LDP MAC-WITHDRAW       : Interface-status-change Enable 
       *Peer Router ID         : 2.2.2.9
        VC Label               : 19456
        Peer Type              : dynamic
        Session                : up
        Tunnel ID              : 0x801002
        Broadcast Tunnel ID    : 0x801002
        CKey                   : 2
        NKey                   : 1
        StpEnable              : 0
        PwIndex                : 0
    
        Interface Name         : Eth-Trunk10.1
        State                  : up
        Last Up Time           : 2009/03/28 15:32:50
        Total Up Time          : 0 days, 0 hours, 8 minutes, 22 seconds
    
       **PW Information:
    
       *Peer Ip Address        : 2.2.2.9
        PW State               : up
        Local VC Label         : 19456
        Remote VC Label        : 19456
        PW Type                : label
        Tunnel ID              : 0x801002
        Broadcast Tunnel ID    : 0x801002
        Ckey                   : 0x2
        Nkey                   : 0x1
        Main PW Token          : 0x801002
        Slave PW Token         : 0x0
        Tnl Type               : LSP
        OutInterface           : GigabitEthernet1/0/1
        Stp Enable             : 0
        Mac Flapping           : 0 
        PW Last Up Time        : 2009/03/28 15:12:13
        PW Total Up Time       : 0 days, 0 hours, 26 minutes, 39 seconds    

    The command output shows that a PW is set up between the VSI named ldp1 and PE2, both the VSI and PW are Up, and the sub-interface of the Eth-Trunk bound to the VSI is also Up.

Configuration Files

  • Configuration file of the CE

    #
     sysname CE
    #
     vlan batch 1
    #
    interface Eth-Trunk20
     portswitch
     port default vlan 1
     port trunk allow-pass vlan 1
     mode lacp-static
    #
    interface GigabitEthernet1/0/1
     undo shutdown
     eth-trunk 20
    #
    interface GigabitEthernet1/0/2
     undo shutdown
     eth-trunk 20
    #
    return       
  • Configuration file of PE1

    #
     sysname PE1
    #
     e-trunk 1
    #
     lacp e-trunk system-id 00e0-fc00-0000
     lacp e-trunk priority 1
    #
     bfd
    #
     mpls lsr-id 1.1.1.9
     mpls
    #
     mpls l2vpn
    #
    vsi ldp1 static
     pwsignal ldp
      vsi-id 2
      mac-withdraw enable
      interface-status-change mac-withdraw enable
      peer 2.2.2.9 
     ignore-ac-state
    #
    mpls ldp
    #
    interface Eth-Trunk10
     mode lacp-static
     e-trunk 1
    #
    interface Eth-Trunk10.1
     vlan-type dot1q 1
     l2 binding vsi ldp1
    #
    interface GigabitEthernet1/0/1
     undo shutdown
     ip address 100.1.1.1 255.255.255.252
     mpls
     mpls ldp
    #
    interface GigabitEthernet1/0/2
     undo shutdown
     eth-trunk 10
    #
    interface LoopBack1
     ip address 1.1.1.9 255.255.255.255
    #
    bfd hello bind peer-ip 100.1.1.2 source-ip 100.1.1.1
     discriminator local 1
     discriminator remote 2
     commit
    #
    ospf 1
     area 0.0.0.0
      network 1.1.1.9 0.0.0.0
      network 100.1.1.0 0.0.0.3
    #
    e-trunk 1
     priority 10
     peer-address 100.1.1.2 source-address 100.1.1.1
     timer hello 9
     e-trunk track bfd-session 1
    #
    return                    
  • Configuration file of PE2

    #
     sysname PE2
    #
     e-trunk 1
    #
     lacp e-trunk system-id 00e0-fc00-0000
     lacp e-trunk priority 1
    #
     bfd
    #
     mpls lsr-id 2.2.2.9
     mpls
    #
     mpls l2vpn
    #
    vsi ldp1 static
     pwsignal ldp
      vsi-id 2
      mac-withdraw enable
      interface-status-change mac-withdraw enable
      peer 1.1.1.9
     ignore-ac-state
    #
    mpls ldp
    #
    interface Eth-Trunk10
     mode lacp-static
     e-trunk 1
    #
    interface Eth-Trunk10.1
     vlan-type dot1q 1
     l2 binding vsi ldp1
    #
    interface GigabitEthernet1/0/1
     undo shutdown
     eth-trunk 10
    #
    interface GigabitEthernet1/0/2
     undo shutdown
     ip address 100.1.1.2 255.255.255.252
     mpls
     mpls ldp
    #
    interface LoopBack1
     ip address 2.2.2.9 255.255.255.255
    #
    bfd hello bind peer-ip 100.1.1.1 source-ip 100.1.1.2
     discriminator local 2
     discriminator remote 1
     commit
    #
    ospf 1
     area 0.0.0.0
      network 2.2.2.9 0.0.0.0
      network 100.1.1.0 0.0.0.3
    #
    e-trunk 1
     priority 20
     peer-address 100.1.1.1 source-address 100.1.1.2
     timer hello 9
     e-trunk track bfd-session 2
    #
    return