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 Static LACP Mode

Configuring an Eth-Trunk Interface to Work in Static LACP Mode

If two LACP-capable devices are directly connected through an Eth-Trunk link, you can configure the Eth-Trunk interfaces on the two devices to work in static LACP mode. Eth-Trunk interfaces working in static LACP mode implement both load balancing and link backup.

Usage Scenario

As network services expand, the bandwidth provided by a single P2P physical link working in full-duplex mode cannot meet the requirement 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. Configuring an Eth-Trunk interface to work in static LACP mode increases interface bandwidth and provides reliability. When an Eth-Trunk member link fails, traffic is automatically switched to other available links, preventing traffic interruption. In addition, Eth-Trunk interfaces working in static LACP mode can implement load balancing. The configuration is simple.

As shown in Figure 4-4, the Eth-Trunk interfaces on the two directly-connected devices can be configured to work in static LACP mode to implement load balancing. The static LACP mode is also called the M:N mode. M links function as active links and N links function as standby links to implement link backup.
Figure 4-4 Eth-Trunk interfaces in static LACP mode

NOTE:

Interfaces operating at different rates, in different duplex modes, and on different boards can be added to the same Eth-Trunk interface working in static LACP mode. Member interfaces working at different rate, however, cannot be in the forwarding state at the same time, and member interfaces working in half-duplex mode cannot forward traffic. Confirm the boards where member interfaces reside, interface rate, and duplex mode.

To enable interfaces operating at different rates to forward traffic after they are added to an Eth-Trunk interface, run the lacp mixed-rate link enable command.

Pre-configuration Tasks

Before configuring an Eth-Trunk interface to work in static LACP mode, connect interfaces and set their physical parameters to ensure that the physical interface status is Up.

Configuration Procedures

Figure 4-5 Flowchart for configuring an Eth-Trunk interface in static LACP mode

Creating an Eth-Trunk Interface and Configuring It to Work in Static LACP Mode

An Eth-Trunk interface must be created before you add physical interfaces to the 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

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

  4. (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.

  5. Run mode lacp-static

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

  6. Run commit

    The configuration is committed.

Adding Physical Interfaces to the Eth-Trunk Interface

After an Eth-Trunk interface is created and configured to work in static LACP mode, add physical interfaces to the Eth-Trunk interface to increase interface bandwidth, carry out load balancing, 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.

  • Different Ethernet interfaces can be added to the same Eth-Trunk interface.

    To enable interfaces operating at different rates to forward traffic after they are added to an Eth-Trunk interface, run the lacp mixed-rate link enable command.

  • 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. (Optional) Run lacp mixed-rate link enable

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

      NOTE:

      The rate of the interface added to the Eth-Trunk interface is not limited. For example, 10G and 100G interfaces can be added to the same Eth-Trunk interface.

    4. 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.

    5. 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

Layer 2 and Layer 3 Eth-Trunk interfaces need to be configured with different parameters. Configure the parameters as required.

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

      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-8 as needed.

      Table 4-8 Configuring parameters 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.

      Maximum number of Up member links

      Run the max active-linknumber link-number command.

      NOTICE:
      To prevent Eth-Trunk link from flapping, you are advised to configure the same upper limit for the two ends of an Eth-Trunk link. If only one end of the 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.

      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.

      Mode in which active member interfaces are selected

      Run the lacp selected { priority | speed } command.

      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 an Eth-Trunk interface to receive LACP packets

      Run the lacp timeout { fast [ user-defined user-defined ] | 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.

      CollectorMaxDelay field value in LACPDUs to be received by an Eth-Trunk interface

      Run the lacp collector delay delay-dtime command to configure the value of the CollectorMaxDelay field in an LACPDU.

      An LACP system ID for an Eth-Trunk interface

      Run the lacp system-id mac-address command.

      LACP negotiation delay for an Eth-Trunk interface

      Run the lacp negotiate delaydelay-value command to configure the LACP negotiation delay for an Eth-Trunk interface.

      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

      The Eth-Trunk interface view is displayed.

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

      Table 4-9 Configuring parameters for a Layer 3 Eth-Trunk interface

      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.

      Maximum number of Up member links

      Run the max active-linknumber link-number command.

      NOTE:
      To prevent Eth-Trunk link from flapping, you are advised to configure the same upper limit for the two ends of an Eth-Trunk link. If only one end of the 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.

      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.

      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 an Eth-Trunk interface to receive LACP packets

      Run the lacp timeout { fast [ user-defined user-defined ] | 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.

      CollectorMaxDelay field value in LACPDUs to be received by an Eth-Trunk interface

      Run the lacp collector delay delay-dtime command to configure the value of the CollectorMaxDelay field in an LACPDU.

      An LACP system ID for an Eth-Trunk interface

      Run the lacp system-id mac-address command.

      LACP negotiation delay for an Eth-Trunk interface

      Run the lacp negotiate delaydelay-value command to configure the LACP negotiation delay for an Eth-Trunk interface.

      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 interfaceinterface-typeinterface-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 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.

(Optional) 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-6 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.

(Optional) Enabling State Flapping Suppression on an Eth-Trunk Interface

You can enable state flapping suppression on an Eth-Trunk interface to prevent the Eth-Trunk interface from alternating between Up and Down due to member interface state flapping or received incorrect packets.

Context

  • If the state of an Eth-Trunk interface frequently flaps, the LACP protocol status of the Eth-Trunk interface also flaps, affecting the Eth-Trunk interface operations. To resolve this problem, enable the state flapping suppression function on the Eth-Trunk interface working in LACP mode.
  • By default, an Eth-Trunk interface in LACP mode is enabled to suppress invalid MAC addresses in Ethernet headers of received LACPDUs from flapping, in which case the source MAC addresses of the LACPDUs and system ID are checked. To disable the check, run the lacp dampening unexpected-mac disable command to disable MAC address flapping suppression in Ethernet headers of LACPDUs.

Procedure

  • Enable the state flapping suppression function on an Eth-Trunk interface.

    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 dampening state-flapping

      The state flapping suppression function is enabled on the Eth-Trunk interface.

    4. Run commit

      The configuration is committed.

  • Disable the invalid-MAC-based state flapping suppression function on an Eth-Trunk interface.

    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 dampening unexpected-mac

      The invalid-MAC-based state flapping suppression function is disabled on the Eth-Trunk interface.

    4. Run commit

      The configuration is committed.

Verifying the Configuration of the Eth-Trunk Interface in Static LACP Mode

After an Eth-Trunk interface is configured in static LACP mode, verify the configuration, including the interface ID, working mode, member interface status, LACP system priority, LACP interface priority, and LACP preemption delay.

Prerequisites

An 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 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 Eth-Trunk interface status.
  • 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 in 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 10
Trunk ID: 10
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/2, valid, operate up,   weight=1
Interface GigabitEthernet1/0/3, valid, operate up,   weight=1
Interface GigabitEthernet1/0/4, valid, operate down, weight=1

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

<HUAWEI> display eth-trunk 10
Eth-Trunk10's state information is:
Local:
LAG ID: 10                  WorkingMode: STATIC
Preempt Delay Time: 10      Hash arithmetic: According to flow
System Priority: 120        System ID: 0018-82d4-04c3
Least Active-linknumber: 1  Max Active-linknumber: 64
Operate status: up          Ports: 2
Timeout Period: Slow
--------------------------------------------------------------------------------
ActorPortName          Status   PortType PortPri PortNo PortKey PortState Weight
GigabitEthernet1/0/2   Selected 1GE      10      262    2609    10111100  1
GigabitEthernet1/0/3   Selected 1GE      10      263    2609    10111100  1
GigabitEthernet1/0/4   Unselect 1GE      32768   264    2609    10100000  1

Partner:
--------------------------------------------------------------------------------
ActorPortName          SysPri    SystemID  PortPri PortNo  PortKey   PortState
GigabitEthernet1/0/2   32768  00e0-fc6e-bb11  32768  262   2609      10111100
GigabitEthernet1/0/3   32768  00e0-fc6e-bb11  32768  263   2609      10111100
GigabitEthernet1/0/4   32768  00e0-fc6e-bb11  32768  264   2609      10110000

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

<HUAWEI> display interface eth-trunk 10
Eth-Trunk10 current state : UP (ifindex: 20)
Line protocol current state : UP
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
GigabitEthernet1/0/2          UP                  1
----------------------------------------------------------
The Number of Ports in Trunk : 2
The Number of UP Ports in Trunk : 2

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: 27286

Downloads: 18

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