ping access-user

Function

The ping access-user command checks the network reachability between an access user and servers.

This command is supported only on the NetEngine 8000 F1A.

Format

ping access-user { user-mac mac | user-id user-id | user-ip ip-address [ vpn-instance vpn-instancename ] } [ { -t milliseconds | -c times | -m milliseconds } ^* ] [ capture-enable ]

Parameters

Parameter	Description	Value
user-mac mac	Specifies the MAC address of a user.	The value is in the format of H-H-H, in which each H is a 4-digit hexadecimal number, such as 00e0 and fc01. If an H contains fewer than 4 digits, the left-most digits are padded with zeros. For example, e0 is displayed as 00e0. The MAC address cannot be set to FFFF-FFFF-FFFF.
user-id user-id	Specifies the ID of a user.	The value is an integer ranging from 0 to 4294967295.
user-ip ip-address	Specifies the IP address of the user.	The value is in dotted decimal notation.
vpn-instance vpn-instancename	Specifies a VPN instance name.	The value is a string of 1 to 31 case-sensitive characters, spaces not supported. _public_ cannot be used as a VPN instance name. The string can contain spaces if it is enclosed in double quotation marks (").
-t milliseconds	Specifies the timeout period for waiting for an ICMP Echo Reply message.	The value is an integer ranging from 0 to 65535, in milliseconds. The default value is 2000.
-c times	Specifies the number of sent ICMP Echo Request messages.	The value is an integer ranging from 1 to 20. The default value is 5.
-m milliseconds	Specifies the interval at which ICMP Echo Request messages are sent. After an ICMP Echo Request message is sent, the device waits for an ICMP Echo Reply message. If no ICMP Echo Reply message is received within the specified interval, the device sends another ICMP Echo Request message.	The value is an integer ranging from 1 to 10000, in milliseconds. The default value is 500.
capture-enable	Enables the device to obtain packet headers.	-

Views

All views

Default Level

1: Monitoring level

Task Name and Operations

Task Name	Operations
forwarding	execute

Usage Guidelines

Usage Scenario

If a user fails to access the Internet, you can run the ping access-user command to check the reachability between the user and servers. You can specify the MAC address, IP address, or ID of the user in the command to check whether ICMP Echo Request messages reach the servers, the number of sent and received messages, and the message loss ratio.

If the number of sent ICMP Echo Request messages is equal to the number of received ICMP Echo Reply messages, no messages are lost, and the corresponding server is reachable.
If the number of sent ICMP Echo Request messages is different from the number of received ICMP Echo Reply messages, messages are lost. In this case, locate the fault based on the message loss cause.
You can edit a file to set IP addresses for ping operations. The file must be named as PingIpAddressList.txt and stored in the cfcard/home: directory of the device. Each line in the file is one record and contains one IP address or URL. When obtaining an address or URL from a file, the system checks its validity. If the address or URL is invalid, the system stops obtaining the current and rest addresses or URLs. A maximum of 50 records can be obtained. If the file contains more than 50 records, the system does not obtain excess records.
If this command is run and the PingIpAddressList.txt file is configured, the system obtains address or URL information from the file to perform ping operations after checking the network reachability between the specified access user and RADIUS or DNS servers.
If this command is run, but the PingIpAddressList.txt file is not configured, the system checks the network reachability between the specified access user and RADIUS or DNS servers only.

Precautions

When the IP address of a server is not forwarded through the interface board, for example, the RADIUS server, only the reachability between the user and servers can be detected. Packet headers cannot be obtained.
For LNS users, only the reachability between the users and servers can be detected, and packet headers cannot be obtained.
When the outbound interface of downstream packets is a VE interface, packets headers of multiple instances can be obtained.

Example

# Check the reachability between the user whose user ID is 0. IN the example, the server can reply the message, and the transmitted packes are equal to the received packets.

<HUAWEI> ping access-user user-id 0
Info: ping user IP address
  PING 192.168.227.6: 56  data bytes, press CTRL_C to break
    Reply from 192.168.227.6: bytes=56 Sequence=1 ttl=255 time=5 ms
    Reply from 192.168.227.6: bytes=56 Sequence=2 ttl=255 time=2 ms
    Reply from 192.168.227.6: bytes=56 Sequence=3 ttl=255 time=2 ms
    Reply from 192.168.227.6: bytes=56 Sequence=4 ttl=255 time=2 ms
    Reply from 192.168.227.6: bytes=56 Sequence=5 ttl=255 time=1 ms

  --- 192.168.227.6 ping statistics ---
    5 packet(s) transmitted
    5 packet(s) received
    0.00% packet loss
    round-trip min/avg/max = 1/2/5 ms
Info: ping IP address of the primary DNS server 
  PING 192.168.227.7: 56  data bytes, press CTRL_C to break
    Reply from 192.168.227.7: bytes=56 Sequence=1 ttl=255 time=5 ms
    Reply from 192.168.227.7: bytes=56 Sequence=2 ttl=255 time=2 ms
    Reply from 192.168.227.7: bytes=56 Sequence=3 ttl=255 time=2 ms
    Reply from 192.168.227.7: bytes=56 Sequence=4 ttl=255 time=2 ms
    Reply from 192.168.227.7: bytes=56 Sequence=5 ttl=255 time=1 ms

  --- 192.168.227.7 ping statistics ---
    5 packet(s) transmitted
    5 packet(s) received
    0.00% packet loss
 round-trip min/avg/max = 1/2/5 ms
Info: ping IP address of the secondary DNS server
  PING 192.168.227.8: 56  data bytes, press CTRL_C to break
    Reply from 192.168.227.8: bytes=56 Sequence=1 ttl=255 time=5 ms
    Reply from 192.168.227.8: bytes=56 Sequence=2 ttl=255 time=2 ms
    Reply from 192.168.227.8: bytes=56 Sequence=3 ttl=255 time=2 ms
    Reply from 192.168.227.8: bytes=56 Sequence=4 ttl=255 time=2 ms
    Reply from 192.168.227.8: bytes=56 Sequence=5 ttl=255 time=1 ms

  --- 192.168.227.8 ping statistics ---
    5 packet(s) transmitted
    5 packet(s) received
    0.00% packet loss
 round-trip min/avg/max = 1/2/5 ms
Info: ping IP address of the RADIUS authentication server
  PING 192.168.227.9: 56  data bytes, press CTRL_C to break
    Reply from 192.168.227.9: bytes=56 Sequence=1 ttl=255 time=5 ms
    Reply from 192.168.227.9: bytes=56 Sequence=2 ttl=255 time=2 ms
    Reply from 192.168.227.9: bytes=56 Sequence=3 ttl=255 time=2 ms
    Reply from 192.168.227.9: bytes=56 Sequence=4 ttl=255 time=2 ms
    Reply from 192.168.227.9: bytes=56 Sequence=5 ttl=255 time=1 ms

  --- 192.168.227.9 ping statistics ---
    5 packet(s) transmitted
    5 packet(s) received
    0.00% packet loss
 round-trip min/avg/max = 1/2/5 ms
Info: ping IP address of the RADIUS accounting server
  PING 192.168.227.10: 56  data bytes, press CTRL_C to break
    Reply from 192.168.227.10: bytes=56 Sequence=1 ttl=255 time=5 ms
    Reply from 192.168.227.10: bytes=56 Sequence=2 ttl=255 time=2 ms
    Reply from 192.168.227.10: bytes=56 Sequence=3 ttl=255 time=2 ms
    Reply from 192.168.227.10: bytes=56 Sequence=4 ttl=255 time=2 ms
    Reply from 192.168.227.10: bytes=56 Sequence=5 ttl=255 time=1 ms

  --- 192.168.227.10 ping statistics ---
    5 packet(s) transmitted
    5 packet(s) received
    0.00% packet loss
 round-trip min/avg/max = 1/2/5 ms

# Check the validity of user IP address in the files between the user whose user ID is 0. IN the example, the IP address is invalid.

<HUAWEI> ping access-user user-id 0
Info: ping user IP address
  PING 192.168.255.254: 56  data bytes, press CTRL_C to break
    Reply from 192.168.255.254: bytes=56 Sequence=1 ttl=128 time=24 ms
    Reply from 192.168.255.254: bytes=56 Sequence=2 ttl=128 time=21 ms
    Reply from 192.168.255.254: bytes=56 Sequence=3 ttl=128 time=26 ms
    Reply from 192.168.255.254: bytes=56 Sequence=4 ttl=128 time=18 ms
    Reply from 192.168.255.254: bytes=56 Sequence=5 ttl=128 time=24 ms
Info: ping IP address 1.1.1.1
  PING 192.168.10.10: 56  data bytes, press CTRL_C to break
    Request time out
    Request time out
    Request time out
    Request time out
    Request time out
Error: Invalid IP address or host 2.2.2.2.2.2.

**Table 1** Description of the **ping access-user** command output
Item	Description
PING x.x.x.x	Destination IP address.
press CTRL_C to break	You can press CTRL+C to stop the ongoing ping test.
Reply from x.x.x.x	Information about the reply to each ICMP Echo Request message, including: bytes: length of an ICMP Echo Reply message. Sequence: sequence number of an ICMP Echo Reply message. ttl: TTL of an ICMP Echo Reply message. time: delay after which an ICMP Echo Reply message is received If no ICMP Echo Reply message is received within the timeout period, the "Request time out" message is displayed.
Request time out(xxxx)	Request timeout. The timeout cause is displayed, which can be: unroutable: No routes are available. no ARP: No ARP entries are available. outgoing interface down: The outbound interface is Down. icmp_id is xxxx not xxxx: The ICMP_ID is incorrect. Sequence is xxxx not xxxx: The sequence number is incorrect. ttl iquals 0 during transit: TTL times out. Other causes of message loss are not displayed.
x data bytes	Length of each sent ICMP Echo Request message.
x.x.x.x ping statistics	Ping statistics. packets transmitted: number of sent ICMP Echo Request messages. packets received: number of received ICMP Echo Reply messages. % packet loss: proportion of ICMP Echo Request messages to which the remote end does not respond to the sent ICMP Echo Request messages. round-trip min/avg/max: minimum, average, and maximum response time, in milliseconds.