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

ME60 V800R010C10SPC500 Configuration Guide - LAN Access and MAN Access 01

This is ME60 V800R010C10SPC500 Configuration Guide - LAN Access and MAN Access
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 an Eth-Trunk Interface to Work in Manual Load Balancing Mode

Configuring an Eth-Trunk Interface to Work in Manual Load Balancing Mode

You can configure Eth-Trunk interfaces working in manual load balancing mode on two connected devices if one or both of them do not support LACP. Then, you can add physical interfaces to the Eth-Trunk interfaces to increase bandwidth and improve reliability.

Usage Scenario

As the volume of services deployed on networks increases, the bandwidth provided by a single P2P physical link working in full-duplex mode cannot meet the requirements of service traffic.

To increase bandwidth without obtaining more hardware resources or requiring more IP addresses, configure Eth-Trunk interfaces using the link aggregation technique. When one or both of the devices at the two ends of an Eth-Trunk link does not support LACP, you can configure the Eth-Trunk interfaces to work in manual load balancing mode. In addition, you can add multiple member interfaces to increase the bandwidth between the two devices and improve reliability.

On the network shown in Figure 4-1, an Eth-Trunk interface is configured to work in manual load balancing mode on each of the two directly connected devices to implement load balancing.
Figure 4-1 Eth-Trunk interfaces in manual load balancing mode

NOTE:

An Eth-Trunk interface working in manual load balancing mode can contain member interfaces at different rates, in different duplex modes, and on different boards.

Pre-configuration Tasks

Before configuring an Eth-Trunk interface to work in manual load balancing mode, connect interfaces and configure physical parameters for the interfaces to make sure that the physical status of the interfaces is Up.

Configuration Procedures

Figure 4-2 Flowchart for configuring an Eth-Trunk interface in manual load balancing mode

Creating an Eth-Trunk Interface and Configuring It to Work in Manual Load Balancing Mode

You can add physical interfaces to an Eth-Trunk interface working in manual load balancing mode. All the member interfaces are in the forwarding state and load-balance traffic.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run interface eth-trunk trunk-id

    An Eth-Trunk interface is created and the Eth-Trunk interface view is displayed.

  3. (Optional) Run portswitch

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

    NOTE:

    Physical interfaces can be added to an Eth-Trunk interface regardless of which mode the Eth-Trunk interface works in. If the Eth-Trunk interface needs to work in Layer 3 mode, skip this step and go to the next step.

  4. Run mode manual load-balance

    The Eth-Trunk interface is configured to work in manual load balancing mode.

  5. Run commit

    The configuration is committed.

Adding Physical Interfaces to the Eth-Trunk Interface

After creating an Eth-Trunk interface and configuring it to work in manual load balancing mode, add physical interfaces to the Eth-Trunk interface to increase interface bandwidth and improve reliability.

Context

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

Note the following when adding physical interfaces to an Eth-Trunk interface:

  • Eth-Trunk interfaces cannot be added to Eth-Trunk interfaces.

  • Ethernet interfaces on different interface boards can be added to the same Eth-Trunk interface.

  • Eth-Trunk interfaces work in either Layer 2 or Layer 3 mode. Ethernet interfaces can join an Eth-Trunk interface regardless of the mode in which the Eth-Trunk interface works.

NOTE:
After a physical interface is added to an Eth-Trunk interface, the physical interface will undergo status changes according to the command run on the Eth-Trunk interface.
  • If you run the shutdown command on the Eth-Trunk interface, the physical status of both the Eth-Trunk interface and its member interface becomes Administratively DOWN, and the configuration file of the member interface displays shutdown automatically.
  • If you run the undo shutdown command on the Eth-Trunk interface, the configuration file of the member interface displays undo shutdown automatically.

Procedure

  • Add one or more physical interfaces 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 either of the following commands as required.

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

      • To add a single physical interface to an Eth-Trunk interface, run the trunkport interface-type interface-number command.

    4. Run commit

      The configuration is committed.

  • Add a physical interface to an Eth-Trunk interface in the view of the physical interface.
    1. Run system-view

      The system view is displayed.

    2. Run interface interface-type interface-number

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

    3. Run eth-trunk trunk-id

      The physical interface is added to the 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.

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

      • Before adding a Layer 2 interface on the ME device to an Eth-Trunk interface, run the undo portswitch command to configure the Eth-Trunk interface to work in Layer 3 mode.

      • If an Eth-Trunk member interface is directly connected to an interface on the peer, the interface must also be an Eth-Trunk member interface; otherwise, the devices cannot communicate with each other.

    4. Run commit

      The configuration is committed.

Follow-up Procedure

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

When Eth-Trunk member interfaces change from Up to Down or Down to Up, you need to learn the status changes through trap messages so to determine whether the status changes are caused by device faults.

By default, Eth-Trunk member interfaces use a public MIB to send trap messages. The trap content can be checked through linkDown_active and linkDown_clear in the log reference. Trap messages do not carry the physical status information of a specific Eth-Trunk member interface if sent through a public MIB, whereas carry the desired information if sent through a private MIB. To obtain the physical status of a specific Eth-Trunk member interface, run the trunk-member trap in private-mib enable command. The Eth-Trunk member interface then uses a private MIB to send trap messages about its status changes. You can check the trap content through TRUNK_MEM_LINKDOWN and TRUNK_MEM_LINKUP in the log reference.

Configuring Eth-Trunk Interface Parameters

Eth-Trunk interfaces in manual load balancing mode working in Layer 2 and Layer 3 modes need to be configured with different parameters.

Procedure

  • Configure parameters for a Layer 2 Eth-Trunk interface.
    1. Run system-view

      The system view is displayed.

    2. Run interface eth-trunk trunk-id

      An Eth-Trunk interface is created and the Eth-Trunk interface view is displayed.

    3. Run portswitch

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

    4. Perform one or more operations shown in Table 4-6 as needed.

      Table 4-6 Parameter for a Layer 2 Eth-Trunk Interface

      Parameter for a Layer 2 Eth-Trunk Interface

      Operation

      Maximum number of Up member links that determine the Eth-Trunk link bandwidth

      Run the max bandwidth-affected-linknumber link-number command.

      Minimum number of Up member links

      Run the least active-linknumber link-number command.

      An Eth-Trunk interface is Up as long as one member interface is Up.

      Minimum bandwidth configured for the member links that are Up on an Eth-Trunk interface

      Run the least active-bandwidth bandwidth command.

      NOTE:
      • Ensure that the least active-linknumber link-number command has not been run when you run the least active-bandwidth bandwidth command because the two commands are mutually exclusive.
      • The minimum bandwidth configured for both ends of an Eth-Trunk must be the same to prevent the Eth-Trunk interface from flapping.
      • After the minimum bandwidth is configured for the member links that are Up on an Eth-Trunk interface, do not run the max active-linknumber link-number command to configure the maximum number of active links. That is because the Eth-Trunk interface will go Down if the total bandwidth of the maximum number of active links is less than the minimum bandwidth.
      • In virtual access scenarios where member interfaces of an Eth-Trunk interface reside on different APs, do not configure the minimum bandwidth for the member links that are Up on the Eth-Trunk interface. That is because the required maximum number of active links is 1, which may cause the Eth-Trunk interface to go Down easily.

      Load balancing mode

      Run the { load-balance { src-dst-mac | src-dst-ip | packet-all | symmetric-hash [ complement ] } command.

      Period that an Eth-Trunk interface waits before changing its state to Down

      Run the link-state down-delay-time delay-value command.

      By default, a Down Eth-Trunk interface changes its state to Down immediately without any delay.

    5. Run commit

      The configuration is committed.

  • Configure parameters for a Layer 3 Eth-Trunk interface.
    1. Run system-view

      The system view is displayed.

    2. Run interface eth-trunk trunk-id

      An Eth-Trunk interface is created and the Eth-Trunk interface view is displayed.

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

      Table 4-7 Eth-Trunk interface parameters

      Parameter for a Layer 3 Eth-Trunk Interface

      Operation

      IP address of the Eth-Trunk interface

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

      MAC address of the Eth-Trunk interface

      Run the mac-address mac-address command.

      MTU of the Eth-Trunk interface

      Run the mtu mtu command.

      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.
      • If IPv6 runs on an Eth-Trunk interface, and the MTU set by using the mtu mtu command on the interface is smaller than 1280 bytes, IPv6 does not properly work on this interface. To prevent such a problem, set the MTU of the interface to a value equal to or greater than 1280 when IPv6 runs on the interface.

      Minimum number of Up member links

      Run the least active-linknumber link-number command.

      An Eth-Trunk interface is Up as long as one member interface is Up.

      Minimum bandwidth configured for the member links that are Up on an Eth-Trunk interface

      Run the least active-bandwidth bandwidth command.

      NOTE:
      • Ensure that the least active-linknumber link-number command has not been run when you run the least active-bandwidth bandwidth command because the two commands are mutually exclusive.
      • The minimum bandwidth configured for both ends of an Eth-Trunk must be the same to prevent the Eth-Trunk interface from flapping.
      • After the minimum bandwidth is configured for the member links that are Up on an Eth-Trunk interface, do not run the max active-linknumber link-number command to configure the maximum number of active links. That is because the Eth-Trunk interface will go Down if the total bandwidth of the maximum number of active links is less than the minimum bandwidth.
      • In virtual access scenarios where member interfaces of an Eth-Trunk interface reside on different APs, do not configure the minimum bandwidth for the member links that are Up on the Eth-Trunk interface. That is because the required maximum number of active links is 1, which may cause the Eth-Trunk interface to go Down easily.
      NOTE:
      • Ensure that the least active-linknumber link-number command has not been run when you run the least active-bandwidth bandwidth command because the two commands are mutually exclusive.
      • The minimum bandwidth configured for both ends of an Eth-Trunk must be the same to prevent the Eth-Trunk interface from flapping.
      • After the minimum bandwidth is configured for the member links that are Up on an Eth-Trunk interface, do not run the max active-linknumber link-number command to configure the maximum number of active links. That is because the Eth-Trunk interface will go Down if the total bandwidth of the maximum number of active links is less than the minimum bandwidth.
      • In virtual access scenarios where member interfaces of an Eth-Trunk interface reside on different APs, do not configure the minimum bandwidth for the member links that are Up on the Eth-Trunk interface. That is because the required maximum number of active links is 1, which may cause the Eth-Trunk interface to go Down easily.

      Load balancing mode

      Run the { load-balance { src-dst-mac | src-dst-ip | packet-all | symmetric-hash [ complement ] } command.

      Period that an Eth-Trunk interface waits before changing its state to Down

      Run the link-state down-delay-time delay-value command.

      By default, a Down Eth-Trunk interface changes its state to Down immediately without any delay.

    4. Run commit

      The configuration is committed.

Configuring Parameters for Eth-Trunk Member Interfaces

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

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run interface interface-type interface-number

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

  3. Run distribute-weight weight-value

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

    The number of member interfaces of an Eth-Trunk interfaces cannot exceed the maximum number of member interfaces allowed.

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

  4. Run commit

    The configuration is committed.

(Optical) Configuring an Eth-Trunk Sub-interface

To transmit both Layer 2 and Layer 3 services over the same physical link, create a sub-interface on a Layer 2 Eth-Trunk interface.

Context

If Layer 2 switching devices belong to different VLANs, and hosts in the VLANs need to communicate with each other, you need to create sub-interfaces on the Eth-Trunk interface connecting a Layer 3 device to a Layer 2 switching device, bind a VLAN to each sub-interface, configure 802.1Q encapsulation on the sub-interfaces, and assign an IP address to each sub-interface.

After the configuration is complete, hosts in the VLANs can use these sub-interfaces to communicate with each other. Eth-Trunk sub-interfaces can be configured to terminate dot1q and QinQ VLAN tags.

After sub-interfaces are configured for Layer 2 Eth-Trunk interfaces, the Eth-Trunk interfaces provide Layer 2 functions, and their sub-interfaces provide Layer 3 functions.

Figure 4-3 Typical usage scenario of Layer 2 Eth-Trunk sub-interfaces

For applications of Eth-Trunk sub-interfaces in VLAN services, see VLAN Configuration.

For applications of Eth-Trunk sub-interfaces in QinQ services, see QinQ Configuration.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run interface eth-trunk trunk-id.subnumber

    A sub-interface is created on a Layer 2 Eth-Trunk interface.

    A maximum of 4094 sub-interfaces can be created on an Eth-Trunk interface.

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

    An IP address is assigned to the Eth-Trunk sub-interface.

    When more than one IP address is configured for an Eth-Trunk interface, the keyword sub must be used to indicate the second and subsequent IP addresses.

  4. Run vlan-type dot1q vlan-id

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

    The VLAN IDs associated with the two communicating Eth-Trunk sub-interfaces must be the same.

    The VLAN IDs associated with a sub-interface of a Layer 2 Eth-Trunk interface cannot conflict with the VLAN IDs associated with the Layer 2 Eth-Trunk interface.

    NOTE:

    For configurations of sub-interfaces for dot1q or QinQ VLAN tag termination, see QinQ Configuration.

  5. Run mtu mtu

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

    The MTU value of an Eth-Trunk interface ranges from 46 to 9600, in 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 divided into many fragments and discarded by the QoS queue. To avoid this situation, lengthen the QoS queue accordingly.

  6. Run commit

    The configuration is committed.

Verifying the Configuration of the Eth-Trunk Interface in Manual Load Balancing Mode

After an Eth-Trunk interface in manual load balancing mode is successfully configured, verify the configuration, including the Eth-Trunk ID, working mode, and status of member interfaces.

Prerequisites

An Eth-Trunk interface in manual load balancing mode has been configured.

Procedure

  • Run the display trunkmembership eth-trunk trunk-id command to check information about member interfaces of the Eth-Trunk interface.
  • Run the display eth-trunk [ trunk-id [ interface interface-type interface-number ] ] command to check information about the Eth-Trunk interface and its active member interfaces.
  • Run the display interface eth-trunk [ trunk-id ] command to check the status of the Eth-Trunk interface.
  • Run the display interface brief command to check brief information about the 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 Eth-Trunk interface.

    NOTE:

    The parameter slot slot-id in this command is supported only on the Admin-VS.

Example

Run the display trunkmembership eth-trunk command to view the configured working mode and LACP system priority of the Eth-Trunk interface, LACP priority of each member interface, and active member interfaces.
<HUAWEI> display trunkmembership eth-trunk 20
Trunk ID: 20
used status: VALID
TYPE: ethernet
Working Mode : Normal
Number Of Ports in Trunk = 1
Number Of UP Ports in Trunk = 1
operate status: up

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

Run the display eth-trunk command to check information about the Eth-Trunk interface and its active member interfaces.

<HUAWEI> display eth-trunk 20
Eth-Trunk20's state information is:
WorkingMode: NORMAL         Hash arithmetic: According to flow
Least Active-linknumber: 1  Max Bandwidth-affected-linknumber: 64
Operate status: up          Number Of Up Ports In Trunk: 1
--------------------------------------------------------------------------------
PortName                      Status      Weight
GigabitEthernet1/0/1          Up          1

Run the display interface eth-trunk command to view the status of the Eth-Trunk interface.

<HUAWEI> display interface eth-trunk 20
Eth-Trunk20 current state : UP (ifindex: 20)
Line protocol current state : UP
Link quality grade :  -- 
Last line protocol up time : 2013-08-07 06:17:13
Description:
Route Port,Hash arithmetic : According to flow, Maximal BW: 200Mbps, Current BW: 200Mbps, The Maximum Transmit Unit is 1500
Internet Address is 1.1.1.2/24
IP Sending Frames' Format is PKTFMT_ETHNT_2, Hardware address is 38ba-121c-9f02
Current system time: 2013-08-08 06:30:47
Physical is ETH_TRUNK
    Last 300 seconds input rate 913 bits/sec, 2 packets/sec
    Last 300 seconds output rate 933 bits/sec, 3 packets/sec
    Input: 827 packets,0 bytes
           410 unicast,417 broadcast,0 multicast
           0 errors,0 drops
    Output:819 packets,0 bytes
           402 unicast,417 broadcast,0 multicast
           0 errors,0 drops
    Last 300 seconds input utility rate:  0.00%
    Last 300 seconds output utility rate: 0.00%
----------------------------------------------------------
PortName                      Status              Weight
----------------------------------------------------------
GigabitEthernet1/0/1          UP                  1
----------------------------------------------------------
The Number of Ports in Trunk : 1
The Number of UP Ports in Trunk : 1

Run the display interface brief command to view brief information about the Eth-Trunk interface, including the physical status, link protocol status, bandwidth usage, and statistics about error packets.

<HUAWEI> display interface brief | begin Eth-Trunk
PHY: Physical
*down: administratively down
^down: standby
(l): loopback
(s): spoofing
(b): BFD down
(e): EFM down
(d): Dampening Suppressed
(dl): DLDP down
InUti/OutUti: input utility/output utility
Interface                PHY  Protocol  InUti  OutUti  inErrors    outErrors
Eth-Trunk10              down  down         0%      0%         0            0
GigabitEthernet1/0/1     up    up          50%     60%        23          125
GigabitEthernet1/0/2     down  down         0%      0%         0            0

Run the display trunkfwdtbl eth-trunk command to view the forwarding table on the Eth-Trunk interface.

<HUAWEI> display trunkfwdtbl eth-trunk 1
 Eth-Trunk1's forwarding table is:
  MASTER                        SLAVE
GigabitEthernet1/0/1          GigabitEthernet1/0/2
GigabitEthernet1/0/2          GigabitEthernet1/0/1
GigabitEthernet1/0/1          GigabitEthernet1/0/2
GigabitEthernet1/0/1          GigabitEthernet1/0/2
GigabitEthernet1/0/2          GigabitEthernet1/0/1
GigabitEthernet1/0/1          GigabitEthernet1/0/2
GigabitEthernet1/0/1          GigabitEthernet1/0/2
GigabitEthernet1/0/2          GigabitEthernet1/0/1
GigabitEthernet1/0/2          GigabitEthernet1/0/1
GigabitEthernet1/0/1          GigabitEthernet1/0/2
GigabitEthernet1/0/2          GigabitEthernet1/0/1
GigabitEthernet1/0/2          GigabitEthernet1/0/1
GigabitEthernet1/0/1          GigabitEthernet1/0/2
GigabitEthernet1/0/2          GigabitEthernet1/0/1
GigabitEthernet1/0/2          GigabitEthernet1/0/1
GigabitEthernet1/0/1          GigabitEthernet1/0/2
GigabitEthernet1/0/1          GigabitEthernet1/0/2
GigabitEthernet1/0/2          GigabitEthernet1/0/1
GigabitEthernet1/0/1          GigabitEthernet1/0/2
GigabitEthernet1/0/1          GigabitEthernet1/0/2
GigabitEthernet1/0/2          GigabitEthernet1/0/1
GigabitEthernet1/0/1          GigabitEthernet1/0/2
GigabitEthernet1/0/1          GigabitEthernet1/0/2
GigabitEthernet1/0/2          GigabitEthernet1/0/1
GigabitEthernet1/0/2          GigabitEthernet1/0/1
GigabitEthernet1/0/1          GigabitEthernet1/0/2
GigabitEthernet1/0/2          GigabitEthernet1/0/1
GigabitEthernet1/0/2          GigabitEthernet1/0/1
GigabitEthernet1/0/1          GigabitEthernet1/0/2
GigabitEthernet1/0/2          GigabitEthernet1/0/1
GigabitEthernet1/0/2          GigabitEthernet1/0/1
GigabitEthernet1/0/1          GigabitEthernet1/0/2
Translation
Download
Updated: 2019-01-04

Document ID: EDOC1100059440

Views: 26416

Downloads: 18

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