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

CX11x, CX31x, CX710 (Earlier Than V6.03), and CX91x Series Switch Modules V100R001C10 Configuration Guide 12

The documents describe the configuration of various services supported by the CX11x&CX31x&CX91x series switch modules The description covers configuration examples and function configurations.
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).
Maintaining Link Aggregation

Maintaining Link Aggregation

This section describes how to maintain link aggregation.

Clearing LACP Packet Statistics

Context

The LACP packet statistics cannot be restored after you clear them.

Procedure

  • Run the reset lacp statistics eth-trunk [ trunk-id [ interface interface-type interface-number ] ] command in user view to clear statistics about LACP packets received and sent.

Monitoring the Operating Status of an LAG

Context

During daily maintenance, run the following commands in any view to check the operating status of LAGs.

Procedure

  • Run the display eth-trunk [ trunk-id [ interface interface-type interface-number | verbose ] ] command to check the Eth-Trunk configuration and status.
  • In LACP mode, run the display lacp statistics eth-trunk [ trunk-id [ interface interface-type interface-number ] ] command to check the statistics about LACP packets sent and received.
  • Run the display interface eth-trunk [ trunk-id ] command to check the status of an Eth-Trunk interface.
  • Run the display eth-trunk membership trunk-id command to displays information about member interfaces of an Eth-Trunk..

Using Ping to Monitor the Reachability of Layer 3 Eth-Trunk Member Interfaces

Context

Multiple physical interfaces can be bundled into a logical Eth-Trunk interface, and these physical interfaces are Eth-Trunk member interfaces. A specific transmission path is used by each member interface. The path-specific service parameters, such as delay time, jitter time, and packet loss ratio, are also different. Therefore, you cannot determine which member interface is faulty when the quality of services on a Eth-Trunk interface deteriorates. To resolve this problem, perform a ping test to detect each physical link to help locate the faulty link.

NOTE:

The ping test applies when two devices are directly connected through Eth-Trunk interfaces.

Pre-configuration Tasks

Before using ping to monitor the reachability of Layer 3 Eth-Trunk member interfaces, complete the following task:

  • An Eth-Trunk interface works in Layer 2 mode by default. Before configuring Layer 3 parameters for an Eth-Trunk interface, run the undo portswitch command to configure the Eth-Trunk interface to work in Layer 3 mode and configure an IP address for the Layer 3 Eth-Trunk.

Procedure

  1. Enable the receive end to monitor Layer 3 Eth-Trunk member interfaces.
    1. Run:

      system-view

      The system view is displayed.

    2. Run:

      trunk member-port-inspect

      The receive end is enabled to monitor Layer 3 Eth-Trunk member interfaces.

      By default, the receive end is disabled from monitoring Layer 3 Eth-Trunk member interface.

      NOTE:

      The trunk member-port-inspect command takes effect on all Layer 3 Eth-Trunk interfaces on a device. Therefore, if you only need to test the connectivity of Eth-Trunk interfaces, disable this function after the monitoring process finishes. If this function is not disabled, the device keeps monitoring the Eth-Trunk member interfaces, which consumes a lot of system resources.

  2. Ping Layer 3 Eth-Trunk member interfaces from the transmit end.
    1. Run:

      ping [ ip ] [ -8021p 8021p-value | -a source-ip-address | -c count  | -d | { -f | ignore-mtu } | -h ttl-value | -i interface-type interface-number | -m time | -p pattern | -q | -r | -ri | -s packetsize | -system-time | -t timeout | { -tos tos-value | -dscp dscp-value } | -v | -vpn-instance vpn-instance-name ] * host [ ip-forwarding ]

      The transmit end is enabled to monitor the reachability of a Layer 3 Eth-Trunk member interface.

      NOTE:

      When testing the reachability of Layer 3 Eth-Trunk member interfaces, you must specify the -a and -i parameters in the ping command, which indicate the source IP address and source interface of ICMP Echo Request packets, respectively.

      The ping command output contains the following information:

      • Response to each ping message: If an echo response message is not received by the transmit end after the corresponding timer expires, a message reading "Request time out" is displayed, indicating that a member interface of the Eth-Trunk is faulty. If an echo response message is received, the data bytes, message sequence number, and response time are displayed, indicating no member interface of the Eth-Trunk is faulty.

      • Final statistics: include the number of sent and received packets, percentage of failure response packets, and minimum, maximum, and average response time.

      <HUAWEI> ping -a 192.168.1.1 -i 10ge 1/17/0 10.1.1.2
      PING 10.1.1.2: 56  data bytes, press CTRL_C to break                                                                             
          Reply from 10.1.1.2: bytes=56 Sequence=1 ttl=254 time=2 ms                                                                     
          Reply from 10.1.1.2: bytes=56 Sequence=2 ttl=254 time=1 ms                                                                     
          Reply from 10.1.1.2: bytes=56 Sequence=3 ttl=254 time=2 ms                                                                     
          Reply from 10.1.1.2: bytes=56 Sequence=4 ttl=254 time=1 ms                                                                     
          Reply from 10.1.1.2: bytes=56 Sequence=5 ttl=254 time=2 ms                                                                     
                                                                                                                                          
        --- 10.1.1.2 ping statistics ---                                                                                                 
          5 packet(s) transmitted                                                                                                         
          5 packet(s) received                                                                                                            
          0.00% packet loss                                                                                                               
          round-trip min/avg/max = 1/1/2 ms

Translation
Download
Updated: 2019-08-09

Document ID: EDOC1000041694

Views: 57475

Downloads: 3619

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