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

A ping command can be run to test the reachability of trunk member interfaces, which helps you learn a physical link's status and locate faulty links.

Context

Multiple physical interfaces can be bundled into a logical trunk interface, and these physical interfaces are 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 trunk interface deteriorates. To resolve this problem, perform a ping test to detect each physical link to help locate the faulty link.

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

Procedure

Enable the receive end to monitor Layer 3 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 trunk member interfaces.
3. Run commit
  The configuration is committed.
To ping Layer 3 trunk member interfaces from the transmit end
1. In most cases, run the ping [ ip ] { [ -a source-ip-address | -c count | -d | { -f | ignore-mtu } | -h ttl-value | { { -i interface-type interface-number | -nexthop nexthop-address } ^* | -si source-interface-type source-interface-number } | -m time | -p pattern | -q | -r | { -s packetsize | -range [ [ min min-size | max max-size | step step-size ] ^* ] } | -system-time | -t timeout | { -tos tos-value | -dscp dscp-value } | -v | -vpn-instance vpn-instance-name | -ri | -8021p 8021p-value | -detail ] ^* host [ ip-forwarding ] } command.
2. If trunk member interface-based fast reply is required, run the ping [ ip ] { [ -c count | { [ -i { interface-name | interface-type interface-number } -fri } | { -s packetsize | -range [ [ min min-value | max max-value | step step-value ] ^* ] } | -t timeout | -m time | -a source-ip-address | -h ttl-value | -p pattern | { -tos tos-value | -dscp dscp-value } | { -f | ignore-mtu } | -vpn-instance vpn-instance-name | -8021p 8021p-value | -name | { -brief | [ -q | -detail | -v | -d | -system-time | -ri ] ^* } ] ^* host [ ip-forwarding ] } command.
  
  Fragmented packets do not support the fast reply function. In this case, configuring the -fri keyword to implement trunk member interface-based fast reply does not take effect.
The ping command output contains the following information:
- Response to each ping message: If an echo response message is not received after the corresponding timer expires, a message reading "Request time out" is displayed; if an echo response message is received, the data bytes, message sequence number, and response time are displayed.
- 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 gigabitethernet 0/1/8 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=255 time=170 ms
    Reply from 10.1.1.2: bytes=56 Sequence=2 ttl=255 time=30 ms
    Reply from 10.1.1.2: bytes=56 Sequence=2 ttl=255 time=30 ms
    Reply from 10.1.1.2: bytes=56 Sequence=2 ttl=255 time=50 ms
    Reply from 10.1.1.2: bytes=56 Sequence=2 ttl=255 time=50 ms    

  --- 10.1.1.2 ping statistics ---
    5 packet(s) transmitted
    5 packet(s) received
    0.00% packet loss
    round-trip min/avg/max = 30/66/170 ms 
```
On an IPv6 network, run the ping ipv6 command.