Ping and Traceroute Operational Commands

IP Ping

The IP ping utility is used to test the reachability of a destination IP address and to measure the time taken for packets to travel between the source and the destination.

IP Ping in the Default Instance

The ping command allows you to ping to a destination to check if a device is reachable. When issued in the default instance, the command validates reachability using the default routing table.

Syntax

ping <destination_ip> afi ipv4
ping <destination_ip> count [1 - 65535]
ping <destination_ip> do-not-fragment
ping <destination_ip> exit-interface <exit_interface>
ping <destination_ip> instance <instance>
ping <destination_ip> interval [0.001 - 60.000]
ping <destination_ip> safi [unicast | multicast | labeled-unicast]
ping <destination_ip> size [8 - 32768]
ping <destination_ip> source-interface <source>
ping <destination_ip> source-ip <source_ip>
ping <destination_ip> tos [0 - 255]
ping <destination_ip> ttl [1 - 255]

destination-ip Specify the IPv4 destination IP address to ping.

interface

Specify the source interface used to send the ping packets.

count

Number of ping packets to send. (Default: 5)

do-not-fragment

Sets the do-not-fragment (DF) bit in the IP packet header.

interval

Time interval between packets in seconds. (Default: 1 second).

safi

Subsequent address family identifier. Supported options include 'unicast', 'multicast', and 'labeled-unicast'. Default is 'unicast'.

size

Size of the ping packet in bytes. (Default: 60 bytes).

source-ip

IPv4 address to be used as the source of the ping packets.

ttl

Time-to-live value applied to outgoing packets. Default value is 255.

tos

Type of Service field used for marking packets. Applicable to IP header only. Default value 0.

exit-interface

Enables to force ICMP echo requests through the specified exit interface if route is resolved via that interface.

Example:

The following ping command sends ICMP echo requests (in the default instance) to a IPv4 destination address to verify reachability and measures round-trip latency. The output shows a response received from the destination that includes the icmp_seq (sequence number of the request), ttl (time-to-live value of the returned packet) and time (round-trip latency in milliseconds). The statistics summary displays the number of packets sent/received and the packet-loss percentage, indicating overall connectivity quality.

supervisor@rtbrick: op> ping 192.0.2.2
ping to 192.0.2.2 60 byte packets
68 bytes from 192.0.2.2: icmp_seq=1 ttl=64 time=29.73 ms
68 bytes from 192.0.2.2: icmp_seq=2 ttl=64 time=10.03 ms
68 bytes from 192.0.2.2: icmp_seq=3 ttl=64 time=10.00 ms
68 bytes from 192.0.2.2: icmp_seq=4 ttl=64 time=10.42 ms
68 bytes from 192.0.2.2: icmp_seq=5 ttl=64 time=9.97 ms
--- 192.0.2.2 ping statistics ---
5 sent, 5 received, 0 errors, 0.00% loss, time 5030.29 ms
rtt min/avg/max/mdev = 9.97/14.03/29.73/7.85 ms

api  To access the RESTCONF API that corresponds to this CLI, click here.

IP Ping in a Specific Instance and AFI/SAFI

This command enables you to send ping requests to a destination within a selected routing instance or VRF, rather than the default global instance. You can also choose the required address family (IPv4 or IPv6). You can verify connectivity to check reachability issues in multi-VRF deployments.

Syntax

ping <destination_ip> afi ipv4
ping <destination_ip> count <1 - 65535>
ping <destination_ip> do-not-fragment
ping <destination_ip> instance <instance>
ping <destination_ip> interval <0.001 - 60.000>
ping <destination_ip> safi [unicast | multicast | labeled-unicast]
ping <destination_ip> size <8 - 32768>
ping <destination_ip> source-interface <source>
ping <destination_ip> source-ip <source_ip>
ping <destination_ip> tos <0 - 255>
ping <destination_ip> ttl <1 - 255>

destination-ip IPv4 destination address to ping.

instance-name

Name of the instance in which the ping must be executed.

afi

Address Family Identifier.

safi

Subsequent address family identifier. Supported options include 'unicast', 'multicast', and 'labeled-unicast'. Default is 'unicast'

interface

Source interface used to send the ping packets.

count

Number of ping packets to transmit. (Default: 5).

do-not-fragment

Set the do-not-fragment (DF) bit in IP packet header.

interval

Time interval between packets in seconds. (Default: 1 second).

size

Size of the ping packet in bytes. (Default: 60 bytes).

source-ip

IPv4 address to be used as the source of the ping packets.

ttl

Time-to-live value applied to outgoing packets. Default value is 255.

tos

Type of Service field used for marking packets. Applicable to IP header only. Default value is 0.
AFI and SAFI are optional attributes. If they are not explicitly specified, the system defaults to AFI 'IPv6' and SAFI 'unicast'.

Example:

The following example shows how to ping the destination address within the routing instance vrf1.

supervisor@rtbrick: op> ping 198.51.100.21 instance default afi ipv4 safi labeled-unicast
ping to 198.51.100.21 60 byte packets
68 bytes from 198.51.100.21: icmp_seq=1 ttl=64 time=9.94 ms
68 bytes from 198.51.100.21: icmp_seq=2 ttl=64 time=9.97 ms
68 bytes from 198.51.100.21: icmp_seq=3 ttl=64 time=9.98 ms
68 bytes from 198.51.100.21: icmp_seq=4 ttl=64 time=10.19 ms
68 bytes from 198.51.100.21: icmp_seq=5 ttl=64 time=9.97 ms
--- 198.51.100.21 ping statistics ---
5 sent, 5 received, 0 errors, 0.00% loss, time 5027.39 ms
rtt min/avg/max/mdev = 9.94/10.01/10.19/0.09 ms

api  To access the RESTCONF API that corresponds to this CLI, click here.

IPv6 Ping

The IPv6 ping utility is used to verify the reachability of an IPv6 destination by sending ICMPv6 echo requests. It helps to check IPv6 connectivity and measure basic round-trip delay. It is useful for troubleshooting IPv6 networks.

IPv6 Ping in the Default Instance

The ping command allows you to ping to an IPv6 destination to check an IPv6 destination in the default routing instance. It helps to verify whether a device is reachable over IPv6 and provides basic round-trip time and connectivity information.

Syntax:

ping <destination_ipv6> afi ipv6
ping <destination_ipv6> count <1-65535>
ping <destination_ipv6> instance <instance>
ping <destination_ipv6> interval <0.001-60.000>
ping <destination_ipv6> safi <unicast | multicast | labeled-unicast>
ping <destination_ipv6> size <8 - 32768>
ping <destination_ipv6> source-interface <source>
ping <destination_ipv6> source-ip <source_ip>
ping <destination_ipv6> tos <0-255>
ping <destination_ipv6> ttl <1-255>

destination-ipv6 IPv6 destination address.

interface

Source interface to use for sending packets.

count

Number of ping packets to send (Default: 5).

do-not-fragment

Sets the 'do-not-fragment' (DF) bit in IP packet header.

interval

Interval time between the successive packets (Default: 1 second).

size

Size of the ping packet in bytes (Default: 60 bytes).

source-ipv6

IPv6 source address to use for the ping.

ttl

Time-to-Live value for the packet. Default value is 255.

tos

Type of Service (TOS) value to use in the packet. Applicable to IP header only. Default value 0

Example:

The following ping command sends ICMP echo requests (in the default instance) to a IPv6 destination address to verify reachability and measures round-trip latency.

supervisor@rtbrick: op> ping 2001:db8:1:1::2
ping to 2001:db8:1:1::2 60 byte packets
68 bytes from 2001:db8:1:1::2: icmp_seq=1 ttl=64 time=10.15 ms
68 bytes from 2001:db8:1:1::2: icmp_seq=2 ttl=64 time=9.94 ms
68 bytes from 2001:db8:1:1::2: icmp_seq=3 ttl=64 time=9.98 ms
68 bytes from 2001:db8:1:1::2: icmp_seq=4 ttl=64 time=10.09 ms
68 bytes from 2001:db8:1:1::2: icmp_seq=5 ttl=64 time=10.00 ms
--- 2001:db8:1:1::2 ping statistics ---
5 sent, 5 received, 0 errors, 0.00% loss, time 5029.07 ms
rtt min/avg/max/mdev = 9.94/10.03/10.15/0.07 ms

IPv6 Ping in a Specific Instance and AFI/SAFI

This functionality allows you to ping an IPv6 destination within a selected routing instance (VRF). You can specify the IPv6 address family to ensure the ping is executed using the correct protocol. It helps to validate IPv6 connectivity for services operating outside the default instance and to troubleshoot reachability in multi-VRF environments.

Syntax

ping <destination_ipv6> afi ipv6
ping <destination_ipv6> count <1-65535>
ping <destination_ipv6> instance <instance>
ping <destination_ipv6> interval <0.001-60.000>
ping <destination_ipv6> safi <unicast | multicast | labeled-unicast>
ping <destination_ipv6> size <8 - 32768>
ping <destination_ipv6> source-interface <source>
ping <destination_ipv6> source-ip <source_ip>
ping <destination_ipv6> tos <0-255>
ping <destination_ipv6> ttl <1-255>

destination-ipv6 IPv6 destination address.

instance-name

Name of the instance on which ping must be executed.

afi

IPv4 Address Family Identifier.

safi

Subsequent address family identifier. Supported options include unicast, multicast, and labeled-unicast. Default is unicast.

interface

Source interface to use for sending packets.

count

Number of ping packets to send (Default: 5).

do-not-fragment

Sets the do-not-fragment (DF) bit in IP packet header.

interval

Interval time between successive packets (Default: 1 second).

size

Size of the ping packet (Default: 60).

source-ipv6

IPv6 source address.

ttl

Time-to-live value to be used in the packet. Default value is 255.

tos

Type of Service (ToS) value to use in packet. Applicable to IP header only. Default value 0.
AFI and SAFI are optional attributes. If they are not explicitly specified, the system defaults to AFI 'IPv6' and SAFI 'unicast'.

Example:

In the following example, the command sends ICMP echo requests to the IPv6 destination address. It verifies IPv6 connectivity over an MPLS labeled-unicast path within VRF and the output confirms successful or failure scenario.

supervisor@rtbrick: op> ping 2001:db8:1:1::2
ping to 2001:db8:1:1::2 60 byte packets
68 bytes from 2001:db8:1:1::2: icmp_seq=1 ttl=64 time=10.15 ms
68 bytes from 2001:db8:1:1::2: icmp_seq=2 ttl=64 time=9.94 ms
68 bytes from 2001:db8:1:1::2: icmp_seq=3 ttl=64 time=9.98 ms
68 bytes from 2001:db8:1:1::2: icmp_seq=4 ttl=64 time=10.09 ms
68 bytes from 2001:db8:1:1::2: icmp_seq=5 ttl=64 time=10.00 ms
--- 2001:db8:1:1::2 ping statistics ---
5 sent, 5 received, 0 errors, 0.00% loss, time 5029.07 ms
rtt min/avg/max/mdev = 9.94/10.03/10.15/0.07 ms

IP Traceroute

IP Traceroute in the Default Instance

This command traces the path taken by packets to a specified IP destination using the default routing instance.

Syntax:

traceroute <destination_ip> afi <ipv4 | ipv6>
traceroute <destination_ip> instance <instance>
traceroute <destination_ip> interval <0.001 - 60.000>
traceroute <destination_ip> maxhop <1 - 255>
traceroute <destination_ip> repeat <1 - 65535>
traceroute <destination_ip> safi <unicast | multicast | labeled-unicast>
traceroute <destination_ip> size <1 - 65535>
traceroute <destination_ip> source-interface <source>
traceroute <destination_ip> source-ip <source_ip>

destination-ip IPv4 destination address.

interface

Name of the source interface.

repeat

Number of probe packets sent per hop (Default: 3).

safi

Subsequent address family identifier. Supported options include unicast, multicast, and labeled-unicast. Default is unicast.

interval

Time interval between probe packets (Default: 1 second).

size

Size of each traceroute packet in bytes (Default: 60).

source-ip

Source IP address .

maxhop

Maximum number of hops before the TTL expires (Default: 30).

Example:

This following traceroute command output shows a traceroute to the destination using the default settings. The trace completes in two hops and displays the intermediate router at 198.51.100.90 followed by the destination, along with the round-trip time for three probe packets at each hop.

supervisor@rtbrick: op> traceroute 192.0.2.2
traceroute to 192.0.2.2 30 hops max, 60 byte packets
1    192.0.2.2    9.91ms    10.00ms    9.93ms

api  To access the RESTCONF API that corresponds to this CLI, click here.

IP Traceroute in Specific Instance and AFI/SAFI

This command performs a traceroute to a specified IP destination using the routing table of a specific VRF.

Syntax:

traceroute <destination_ip> afi <ipv4 | ipv6>
traceroute <destination_ip> instance <instance>
traceroute <destination_ip> interval <0.001 - 60.000>
traceroute <destination_ip> maxhop <1 - 255>
traceroute <destination_ip> repeat <1 - 65535>
traceroute <destination_ip> safi <unicast | multicast | labeled-unicast>
traceroute <destination_ip> size <1 - 65535>
traceroute <destination_ip> source-interface <source>
traceroute <destination_ip> source-ip <source_ip>

destination-ip IPv4 destination address.

instance-name

Name of the routing instance in which the traceroute is executed.

afi

Specifies the IP address family to use.

safi

Subsequent address family identifier. Supported options include unicast, multicast, and labeled-unicast. Default is unicast.

interface

Name of the source interface used to send traceroute probe packets.

repeat

Number of probe packets sent to each hop. (Default: 3).

interval

Time interval between packets in seconds. (Default: 1 second).

size

Size of the probe packet in bytes. (Default: 60 bytes).

source-ip

Source IP address for the traceroute probes.

maxhop

Maximum number of hops before the TTL expires. (Default: 30).
AFI and SAFI are optional attributes. If they are not explicitly specified, the system defaults to AFI 'IPv6' and SAFI 'unicast'.

In the following example, the traceroute command verifies IPv4 MPLS LSP connectivity (AFI IPv4, SAFI labeled-unicast) from the specified source interface/IP. The output shows label-switched forwarding and successful reachability of the destination 198.51.100.80 in the next hop. It indicates correct MPLS label distribution and forwarding along the path.

supervisor@rtbrick: op> traceroute 198.51.100.21 instance default afi ipv4 safi labeled-unicast source-interface ifl-0/1/22/100 source-ip 192.0.2.5
traceroute to 198.51.100.21 30 hops max, 60 byte packets
1    198.51.100.21    9.95ms    10.01ms    9.95ms
For the MPLS transport, it displays the ingress labels in each hop.

IPv6 Traceroute

IPv6 Traceroute in the Default Instance

This command allows you to traceroute the hop-by-hop path to a given IP destination.

Syntax

traceroute <destination_ipv6> afi [ipv4 | ipv6]
traceroute <destination_ipv6> instance <instance>
traceroute <destination_ipv6> interval [0.001 - 60.000]
traceroute <destination_ipv6> maxhop [1 - 255]
traceroute <destination_ipv6> repeat [1 - 65535]
traceroute <destination_ipv6> safi [unicast | multicast | labeled-unicast]
traceroute <destination_ipv6> size [1 - 65535]
traceroute <destination_ipv6> source-interface <source>
traceroute <destination_ipv6> source-ip <source_ip>

destination-ipv6 IPv6 destination address.

interface

Source interface name.

repeat

Number of packets sent per hop (Default: 3)

interval

Interval time between packets, in seconds (Default: 1)

size

Size of the traceroute packet in bytes (Default: 60)

source-ip

IPv6 source address.

maxhop

Maximum number of hops before the TTL expires (Default: 30).

The following example shows the IPv6 traceroute traces the hop-by-hop path to IPv6 destination. It shows the successful reachability within two hops and reporting round-trip latency for each hop using default traceroute parameters.

supervisor@rtbrick: op> traceroute 2001:db8:1:1::2
traceroute to 2001:db8:1:1::2 30 hops max, 60 byte packets
1    2001:db8:1:1::2    9.94ms    10.52ms    9.96ms

IPv6 Traceroute in a Specific Instance and AFI/SAFI

This command allows you to traceroute to a particular IPv6 destination in a specific VRF.

Syntax

traceroute <destination_ipv6> afi [ipv4 | ipv6]
traceroute <destination_ipv6> instance <instance>
traceroute <destination_ipv6> interval [0.001 - 60.000]
traceroute <destination_ipv6> maxhop [1 - 255]
traceroute <destination_ipv6> repeat [1 - 65535]
traceroute <destination_ipv6> safi [unicast | multicast | labeled-unicast]
traceroute <destination_ipv6> size [1 - 65535]
traceroute <destination_ipv6> source-interface <source>
traceroute <destination_ipv6> source-ip <source_ip>

destination-ipv6 IPv6 destination address.

instance-name

Instance on which the traceroute command must be executed.

afi

Address Family Identifier (AFI).

safi

Subsequent address family identifier. Supported options include unicast, multicast, and labeled-unicast. Default is unicast.

interface

Name of the source interface.

repeat

Number of packets for each hop (Default, 3).

interval

The interval period between the packets (Default, 1 second).

size

Size of the traceroute packet (Default, 60).

source-ip

Source IPv6 address.

maxhop

Maximum number of hops before the TTL expires (Default, 30)
The AFI and SAFI attributes are optional. If not specified, the default AFI is 'IPv6' and the default SAFI 'unicast'.

The following example traceroute verifies IPv6 reachability using MPLS labeled-unicast in the default routing instance. The probe is sourced from a specific interface. The first hop is an MPLS hop (with the label).

supervisor@rtbrick: op> traceroute 2001:db8:0:1::21 instance default afi ipv6 safi labeled-unicast source-interface ifl-0/1/22/100 source-ip 2001:db8:2:1::1
traceroute to 2001:db8:0:1::21 30 hops max, 60 byte packets
1    2001:db8:0:1::21    9.97ms    10.05ms    9.95ms
For MPLS transport paths, the output displays the ingress MPLS label at each hop.

LSP Ping

The ping mpls command allows you to ping to an MPLS labelled switch path destination to see if a networked device is reachable.

Syntax:

ping mpls <destination_ip_fec> fec-type [ ldp | isis ]
ping mpls <destination_ip_fec> instance <instance>
ping mpls <destination_ip_fec> maxhop [1 - 64]
ping mpls <destination_ip_fec> repeat [1 - 10]
ping mpls <destination_ip_fec> size [1 - 8600]
ping mpls <destination_ip_fec> source-ip <source_ip>
ping mpls <destination_ip_fec> wait-time [1 - 60]

Attribute Description

fec-type

Specifies the type of FEC to help the device identify the exact type. Default 'fec-type' is LDP.

instance

Specify the instance name.

wait-time

Specify the interval time (in seconds) between successive ping packets to send.

size

The size of the PAD TLV to be included in the MPLS Echo Request packet. (Default: 60 bytes).

repeat

Total number ping attempts the device sends to the destination. Default 3.

maxhop

Maximum number of hops the packet traverse (Default: 30).

source-ip

Specify the source IP address for the MPLS Echo Request.

Example: LSP ping for a prefix

In the following example, the MPLS ping verifies LDP-based MPLS connectivity to the FEC 62.154.10.70/32 by sending MPLS echo requests along the label-switched path. All probes are successfully replied. The output shows 0 percent packet loss and stable round-trip times. The RTTs range from 7.61 ms to 47.30 ms confirms that the MPLS LSP to the destination is reachable and operational.

supervisor@rtbrick: op> ping mpls 198.51.100.22/32
Sending 5 MPLS echoes to ldp FEC 198.51.100.22/32
Success: Response from 192.0.2.2: Egress for the FEC: seq = 1 rtt = 39.30 ms
Success: Response from 192.0.2.2: Egress for the FEC: seq = 2 rtt = 2.26 ms
Success: Response from 192.0.2.2: Egress for the FEC: seq = 3 rtt = 2.22 ms
Success: Response from 192.0.2.2: Egress for the FEC: seq = 4 rtt = 2.22 ms
Success: Response from 192.0.2.2: Egress for the FEC: seq = 5 rtt = 2.33 ms
--- 198.51.100.22/32 mpls ping statistics ---
5 sent, 5 received, 0 errors, 0.00% loss, time 5103.94 ms
rtt min/avg/max = 2.22/9.67/39.30 ms

Example: LSP ping for a FEC type

In the following example, the MPLS ping tests MPLS reachability to the FEC 62.154.20.70/32 using ISIS FEC. MPLS echo requests are sent along the IS-IS–signaled label-switched path. Four replies are received from 217.239.37.58. It is identified as the egress LSR for this FEC. While one probe does not receive a response, resulting in 20% packet loss. The measured RTTs range from 11.23 ms to 34.01 ms. It indicates that the MPLS LSP is reachable, though with an intermittent loss observed.

supervisor@rtbrick: op> ping mpls 198.51.100.22/32 fec-type ldp
Sending 5 MPLS echoes to ldp FEC 198.51.100.22/32
Success: Response from 192.0.2.2: Egress for the FEC: seq = 1 rtt = 2.27 ms
Success: Response from 192.0.2.2: Egress for the FEC: seq = 2 rtt = 2.36 ms
Success: Response from 192.0.2.2: Egress for the FEC: seq = 3 rtt = 2.36 ms
Success: Response from 192.0.2.2: Egress for the FEC: seq = 4 rtt = 2.21 ms
Success: Response from 192.0.2.2: Egress for the FEC: seq = 5 rtt = 1.14 ms
--- 198.51.100.22/32 mpls ping statistics ---
5 sent, 5 received, 0 errors, 0.00% loss, time 5104.11 ms
rtt min/avg/max = 1.14/2.07/2.36 ms

api  To access the RESTCONF API that corresponds to this CLI, click here.

MPLS LSP Traceroute

The traceroute mpls command is used to trace the path of an MPLS Label Switched Path (LSP) hop by hop.

Syntax:

traceroute mpls <destination_ipv6_fec> fec-type [ldp | isis]
traceroute mpls <destination_ipv6_fec> instance <instance>
traceroute mpls <destination_ipv6_fec> maxhop [1 - 64]
traceroute mpls <destination_ipv6_fec> repeat [1 - 10]
traceroute mpls <destination_ipv6_fec> size [1 - 8600]
traceroute mpls <destination_ipv6_fec> source-ip <source_ip>
traceroute mpls <destination_ipv6_fec> wait-time [1 - 60]

Attribute Description

-

Without any option, the command traceroute for the specified prefix.

fec-type [ldp | isis]

Specifies the type of FEC to help the device identify the exact type. Default 'fec-type' is LDP.

instance

Specify the instance name. Instance in which the prefix needs to be looked up (Default: 'default')

maxhop

Maximum number of hops (Default: 30).

size

The size of the PAD TLV to be included in the MPLS Echo Request packet. (Default: 60 bytes).

wait-time

Specify the wait time (in seconds) to receive the response. (1-60).

repeat

Number of packets to be repeated with same TTL. Default 3.

source-ip

Source IP address.

Example: LSP traceroute for a FEC type

The following example shows the MPLS traceroute traces the LDP-signaled label-switched path to the FEC 192.168.0.40/32 by sending MPLS echo requests with increasing TTL values. The output shows three MPLS hops in the LSP. At each transit hop, labels are swapped. It confirms correct LDP label forwarding. The final hop (34.0.0.4) is identified as the egress LSR for the FEC. All probes are successfully received (0% loss), with measured RTTs at each hop.

Sending MPLS echoes to ldp FEC 192.168.0.40/32 for traceroute
TTL  Address       Label    Protocol  Down Addr                Down Label  Status                             RTT
  1  12.0.0.2      519942   ldp       23.0.0.3                 519938      Label switched at stack-depth 1    45.15ms, 3.20ms, 3.21ms
  2  23.0.0.3      519938   ldp       34.0.0.4                 3           Label switched at stack-depth 1    3.18ms, 4.25ms, 2.17ms
  3  34.0.0.4      3        ldp       -                        -           Egress for the FEC                 37.18ms, 4.23ms, 3.22ms
--- 192.168.0.40/32 mpls traceroute statistics ---
9 sent, 9 received, 0 errors, 0.00% loss, time 17617.15 ms

api  To access the RESTCONF API that corresponds to this CLI, click here.

Show Commands

Show OAM MPLS

The command displays LSP ping command details.

Syntax:

show oam mpls <option>

Option Description

statistics

Displays MPLS LSP ping statistics.

Example: OAM MPLS LSP Ping statistics

The show oam mpls statistics output indicates that no MPLS OAM activity has occurred on the device. No MPLS echo requests or replies have been sent or received. All transmit and receive error counters remain at zero. It indicates that MPLS OAM is currently idle, with no tests.

supervisor@rtbrick: op> show oam mpls statistics
Sent Statistics:
MPLS echo request sent          : 13
MPLS echo reply sent            : 0
Sent error                      : 0
Sent error - No table           : 0
Sent error - No FEC             : 0
Sent error - No Adjacency       : 0
Sent error - No MPLS Adjacency  : 0
Sent error - No interface       : 0
Sent error - Encode failure     : 0

Received Statistics:
MPLS echo received              : 0
MPLS echo request received      : 0
MPLS echo reply received        : 13
Receive error - L3 decode       : 0
Receive error - header decode   : 0
Receive error - TLV decode      : 0
Receive error - FEV TLV decode  : 0
Receive error - unsupported FEV : 0
Receive error - no session      : 0

Show OAM IP Statistics

The 'show oam ip statistics' command displays information about sent and received OAM IP packet counters.

Syntax:

show oam ip statistics

The following example show command output displays the sent and received statistics for an echo request message.

supervisor@rtbrick: cfg> show oam ip statistics
Sent Statistics:
Echo request sent                          : 0
Sent error                                 : 0
Sent error - no table                      : 0
Sent error - no route                      : 2
Sent error - no adjacency                  : 0
Sent error - no interface                  : 0
Sent error - encode failure                : 0

Received Statistics:
Echo reply received                        : 0
Echo reply - TTL expired                   : 0
Echo reply - destination unreachable       : 0
Receive error - L3 decode                  : 0
Receive error - no session                 : 0

Clear Commands

clear oam ip statistics

The 'clear oam ip statistics' command is used to reset the OAM IP statistics counters.

Syntax:

clear oam ip statistics

Example for 'clear oam ip statistics' command:

supervisor@rtbrick: cfg> clear oam ip statistics
Success: IP oam statistics cleared