Job Aid: Ping And Traceroute Considerations; Running A Ping Test - Avaya 8800 Troubleshooting Manual

Software troubleshooting tool configuration using CLI

Job aid: ping and traceroute considerations

Ping and traceroute may fail when reaching VRF, IP VPN, or MPLS devices if large packet
sizes are used for the operation. Do not use packet sizes larger than the following:
• Ping for VRF Lite: 1480 bytes
• Ping for IP VPN with MPLS: 1480 bytes
• Ping for IP VPN Lite: 1446 bytes
• Traceroute for VRF Lite: 1444 bytes
• Traceroute for IP VPN with MPLS: 1444 bytes
• Traceroute for IP VPN Lite: 1444 bytes

Running a ping test

Use ping operations to determine that a path exists to another device, and that it is
reachable.
Procedure steps
1. Ping a device:
2. Ping an IPX device:
3. Ping an MPLS device:
186 Troubleshooting
ping <HostName/ipv4address/ipv6address> [scopeid <value>]
[datasize <value>] [count <value>] [-s] [-I <value>] [-t
<value>] [-d] [vrf <value>] [source <value>] [interface-port
<value>] [interface-mgmt <value>] [interface-vlan <value>]
[interface-tunnel <value>]
<HostName/ipv4address/ipv6address> specifies the device by host name,
IPv4 address <a.b.c.d>, or IPv6 address <x.x.x.x.x.x.x.x>.
pingipx <ipxhost> [<count>] [-s] [-q] [-t <value>]
<ipxhost> specifies the IPX host in the net.node format:
0x00:0x00:0x00:0x00.0x00:0x00:0x00:0x00:0x00:0x00
mplsping ipv4 <prefix/len> [ttl <value>] [source <value>]
[count <value>]
mplsping rsvp <lsp-name> [ttl <value>] [source <value>]
[count <value>]
Comments? infodev@avaya.com
July 2013