No relevant resource is found in the selected language.

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

Reminder

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

upgrade

NE40E V800R010C00 Configuration Guide - Virtual Access 01

Rate and give feedback :
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Configuring a Virtual Access Eth-Trunk Interface to Work in Static LACP Mode

Configuring a Virtual Access Eth-Trunk Interface to Work in Static LACP Mode

You can configure a virtual access Eth-Trunk interface working in static LACP mode on a master if master and CE support LACP. Virtual access Eth-Trunk interfaces working in static LACP mode implement both load balancing and link backup.

Usage Scenario

To increase bandwidth without obtaining more hardware resources or requiring more IP addresses in virtual access scenarios, configure Eth-Trunk interfaces on the master and CE using the link aggregation technique. Configuring a virtual access Eth-Trunk interface to work in static LACP mode on a master increases interface bandwidth and provides reliability. When a virtual access Eth-Trunk member link fails, traffic is automatically switched to other available links, preventing traffic interruption. In addition, virtual access Eth-Trunk interfaces working in static LACP mode can implement load balancing. The configuration is simple.

As shown in Figure 3-7, the virtual access Eth-Trunk interface on the master can be configured to work in static LACP mode to implement load balancing. The static LACP mode can also support M:N mode. M links function as active links and N links function as standby links to implement link backup.
Figure 3-7  Virtual access Eth-Trunk interfaces in static LACP mode
NOTE:

When a virtual access Eth-Trunk interface is configured to work in M:N (1:1 included) mode:

  • If the remote CE is a non-Huawei device, configuring the Eth-Trunk interfaces of both the master and CE to work in the same M:N mode is recommended.

  • If LACP preemption is not enabled on a master and the remote CE is a non-Huawei device, the LACP priority of the remote CE must be set to the highest

  • If the LACP priority of the master is the highest and the remote CE is a non-Huawei device, LACP preemption must be enabled on the master.

  • The Eth-Trunk interfaces on the primary and secondary masters should work in the same M:N modes. Otherwise LACP must renegotiate if a primary/secondary master switchover occurs. In this situation, the service switchover performance may be worse.

Pre-configuration Tasks

Before configuring a virtual access Eth-Trunk interface to work in static LACP mode, establish a virtual access system.

Configuration Procedures

Figure 3-8  Flowchart for configuring a virtual access Eth-Trunk interface in static LACP mode

Creating a Virtual Access Eth-Trunk Interface and Configuring It to Work in Static LACP Mode

A virtual access Eth-Trunk interface must be created before you add virtual access interfaces to the virtual access Eth-Trunk interface.

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Run:

    lacp priority priority

    The LACP system priority is configured.

    The smaller the value, the higher the priority.

    To configure one end as the Actor, set its LACP system priority to a value smaller than the default value. This end can serve as the Actor because the other end uses the default LACP system priority.

    NOTE:

    The LACP system priority is configured using the lacp priority command in the system view, and the LACP interface priority is configured using the same command but in the interface view.

    A change in the LACP system priority will cause LACP renegotiation. During the renegotiation process, Eth-Trunk interfaces in LACP mode will go Down until the renegotiation succeeds, which may interrupt services. If a maintenance engineer who wants to configure an LACP interface priority runs the lacp priority command in the system view by mistake, an LACP system priority is configured, which may cause Eth-Trunk interface flapping. To address this problem, run the lacp priority-command-mode command so that the LACP system priority and LACP interface priority configurations require different commands.

    When running the lacp priority-command-mode { default | system-priority } command, note the following points:
    • If you specify default in the command, the LACP system priority and LACP interface priority configurations still use the same command (lacp priority priority).
    • If you specify system-priority in the command, run the lacp system-priority priority command to configure the LACP system priority and run the lacp priority priority command to configure the LACP interface priority.

  3. Run:

    interface eth-trunk trunk-id remote

    A virtual access Eth-Trunk interface is created and the Eth-Trunk interface view is displayed.

  4. Run:

    mode lacp-static

    The virtual access Eth-Trunk interface is configured to work in static LACP mode.

  5. Run:

    commit

    The configuration is committed.

Adding Member Interfaces to the Virtual Access Eth-Trunk Interface

After a virtual access Eth-Trunk interface is created and configured to work in static LACP mode, add member interfaces to the virtual access Eth-Trunk interface to increase interface bandwidth, carry out load balancing, and improve reliability.

Context

There are two methods for adding virtual access interfaces to a virtual access Eth-Trunk interface:
  • Add virtual access interfaces in the view of the virtual access Eth-Trunk interface. Using this method, you can add a single virtual access interface or virtual access interfaces in batches.
  • Add a virtual access interface in the interface view.

Note the following when adding virtual access interfaces to a virtual access Eth-Trunk interface:

  • Virtual access Eth-Trunk member interfaces can only be virtual access interfaces.

  • Virtual access interfaces that belong to different APs can only be added to a virtual access Eth-Trunk in static LACP mode, and the maximum number of Up members is 1.

  • The number of virtual access interfaces that belong to the same AP and are added to a virtual access Eth-Trunk cannot exceed the upper limit for trunks on a master.

Procedure

  • Add one or more virtual access interfaces in the virtual access Eth-Trunk interface view.
    1. Run:

      system-view

      The system view is displayed.

    2. Run:

      interface eth-trunk trunk-id remote

      The virtual access Eth-Trunk interface view is displayed.

    3. (Optional) Run:

      lacp mixed-rate link enable

      Interfaces operating at different rates are enabled to forward packets after the interfaces are added to a virtual access Eth-Trunk interface in static LACP mode.

    4. Run either of the following commands as required.

      • To add virtual access interfaces to the virtual access Eth-Trunk interface in batches and configure the mode in which member interfaces of an Eth-Trunk interface send packets, run:
        trunkport interface-type { interface-number1 [ to interface-number2 ] } &<1-64>
      • To add a single virtual access interface to a virtual access Eth-Trunk interface, run:
        trunkport interface-type interface-number

    5. Run:

      commit

      The configuration is committed.

  • Add a virtual access interface to a virtual access Eth-Trunk interface in the view of the virtual access interface.
    1. Run:

      system-view

      The system view is displayed.

    2. Run:

      interface interface-type interface-number

      The view of a virtual access interface that needs to be added to a virtual access Eth-Trunk interface is displayed.

    3. Run:

      eth-trunk trunk-id

      The virtual access interface is added to the virtual access Eth-Trunk interface.

      NOTE:
      • Member interfaces cannot be configured with services or Layer 3 configurations such as IP addresses.

      • Member interfaces cannot be manually configured with MAC addresses.

      • A virtual access interface can be added to only one virtual access Eth-Trunk interface. The virtual access interface must be deleted from the original virtual access Eth-Trunk interface before joining another virtual access Eth-Trunk interface.

    4. Run:

      commit

      The configuration is committed.

NOTE:
If services are running on a live network, it is recommended that you perform the following operations when adding an interface to a virtual access Eth-Trunk interface:
  1. Run the shutdown command on the interface to be added to a virtual access Eth-Trunk interface.
  2. Add the virtual access interface to the virtual access Eth-Trunk interface.
  3. Run the undo shutdown command on the interface that has been added to the virtual access Eth-Trunk interface.

Configuring Virtual Access Eth-Trunk Interface Parameters

Configure the parameters as required.

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Run:

    interface eth-trunk trunk-id remote

    The virtual access Eth-Trunk interface view is displayed.

  3. Perform one or more operations shown in Table 3-2 as needed.

    Table 3-2  Configuring parameters for a virtual access Eth-Trunk interface

    Parameter for a virtual access Eth-Trunk Interface

    Operation

    IP address of the virtual access Eth-Trunk interface

    Run the ip address ip-address { mask | mask-length } [ sub ] command.

    MAC address of the virtual access Eth-Trunk interface

    Run the mac-address mac-address command.

    MTU of the virtual access Eth-Trunk interface

    Run the mtu mtu command.

    The MTU is measured in bytes.
    NOTICE:

    The MTUs of two directly-connected interfaces must be the same. After using the mtu mtu command to change the MTU of an interface, change the MTU of the directly-connected interface on another device to ensure that the MTUs of the two ends are the same. Otherwise, services may be interrupted.

    Maximum number of Up member links

    Run the max active-linknumber link-number command.

    NOTE:
    To prevent virtual Eth-Trunk link from flapping, you are advised to configure the same upper limit for the two virtual interfaces of a virtual Eth-Trunk link. If only one end of the virtual Eth-Trunk link is configured, flapping may occur after all the selected member links switchover is triggered.

    Minimum number of Up member links

    Run the least active-linknumber link-number command.

    Load balancing mode

    Run the { load-balance { src-dst-mac | src-dst-ip | packet-all } command.

    Mode in which active member interfaces are selected

    Run the lacp selected { priority | speed } command.

    NOTE:

    To ensure that an Eth-Trunk works properly, you are advised to configure the Eth-Trunk interfaces on both ends to select active member interfaces in the same mode.

    LACP preemption delay

    1. Run the lacp preempt enable command to enable LACP preemption.

    2. Run the lacp preempt delay delay-time command to configure an LACP preemption delay.

      NOTE:
      • To ensure that an Eth-Trunk works properly, you are advised to enable or disable LACP preemption on both ends.

      • The two ends of an Eth-Trunk link can be configured with different LACP preemption delays. If the two ends are configured with different preemption delays, Eth-Trunk uses the greater delay-time value as the preemption delay.

    Timeout period for a virtual access Eth-Trunk interface to receive LACP packets

    Run the lacp timeout { fast | slow } command.

    NOTE:

    The two ends of an Eth-Trunk link can be configured with different timeout periods. To facilitate maintenance, you are advised to configure the same timeout period for both ends.

  4. Run:

    commit

    The configuration is committed.

Configuring Parameters for Virtual Access Eth-Trunk Member Interfaces

To ensure reliable communication between Eth-Trunk interfaces, configure proper parameters for virtual access Eth-Trunk member interfaces.

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Run:

    interfaceinterface-typeinterface-number

    The view of a virtual access Eth-Trunk member interface is displayed.

  3. Run:

    distribute-weight weight-value

    The load balancing weight is configured for the virtual access Eth-Trunk member interface.

    The virtual access Eth-Trunk interface performs load balancing based on the weights of its member interfaces. The greater the weight of a virtual access Eth-Trunk member interface, the heavier the load carried by the member interface.

  4. Run:

    lacp priority priority

    The LACP priority is configured for the member interface.

    NOTE:

    The LACP priority indicates the preference of an interface to become active. The smaller the value, the higher the priority.

  5. Run:

    commit

    The configuration is committed.

Checking the Configurations

After a virtual access Eth-Trunk interface is configured in static LACP mode, you can view information about the virtual access Eth-Trunk interface, including the interface ID, working mode, member interface status, LACP system priority, LACP interface priority, and LACP preemption delay.

Prerequisites

A virtual access Eth-Trunk interface has been configured in static LACP mode.

Procedure

  • Run the display trunkmembership eth-trunk trunk-id command to check information about member interfaces of the virtual access Eth-Trunk interface.
  • Run the display eth-trunk [ trunk-id [ interface interface-type interface-number ] ] command to check information about the virtual access Eth-Trunk interface and its active member interfaces.
  • Run the display interface eth-trunk [ trunk-id ] command to check the virtual access Eth-Trunk interface status.
  • Run the display interface brief command to check brief information about the virtual access Eth-Trunk interface, including the physical status, link protocol status, and bandwidth usage.
  • Run the display trunkfwdtbl eth-trunk trunk-id [ slot slot-id ] command to check the forwarding table on the virtual access Eth-Trunk interface.
Download
Updated: 2018-07-12

Document ID: EDOC1100028541

Views: 7792

Downloads: 92

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