Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Troubleshoot Ping MPLS

About Ping MPLS Page

You are here: Device Administration > Tools > Ping MPLS.

You can send variations of ICMP "echo request" packets to the specified MPLS endpoint.

To use the ping MPLS tool:

  1. Click the expand icon next to the ping MPLS option you want to use.

  2. Enter information specified in Table 1 to troubleshoot the issue.

  3. Click Start.

    The results of the ping operation are displayed in Table 2.

  4. Click OK to stop the ping operation before it is complete.

Table 1: Ping MPLS Troubleshooting Options

Field

Action
Ping RSVP-signaled LSP

LSP Name

Type the name of the LSP to ping.

Source Address

Type the source IP address of the ping request packet—a valid address configured on a J Series device interface.

Count

From the list, select the number of ping requests to send. The default is 5 requests.

Detailed Output

Select the check box to display detailed output rather than brief ping output.
Ping LDP-signaled LSP

FEC Prefix

Type the forwarding equivalence class (FEC) prefix and length of the LSP to ping.

Source Address

Type the source IP address of the ping request packet—a valid address configured on a J Series device interface.

Count

From the list, select the number of ping requests to send. The default is 5 requests.

Detailed Output

Select the check box to display detailed output rather than brief ping output.
Ping LSP to Layer 3 VPN prefix

Layer 3 VPN Name

Type the name of the VPN to ping.

Count

From the list, select the number of ping requests to send. The default is 5 requests.

Detailed Output

Select the check box to display detailed output rather than brief ping output.

VPN Prefix

Type the IP address prefix and length of the VPN to ping.

Source Address

Type the source IP address of the ping request packet—a valid address configured on a J Series device interface.
Ping LSP for a Layer 2 VPN connection by interface

Interface

From the list, select the J Series device interface on which ping requests are sent. If you select any, the ping requests are sent on all interfaces.

(See the interface naming conventions in the Junos OS Interfaces Configuration Guide for Security Devices.)

Source Address

Type the source IP address of the ping request packet—a valid address configured on a J series device interface.

Count

From the list, select the number of ping requests to send. The default is 5 requests.

Detailed Output

Select the check box to display detailed output rather than brief ping output.
Ping LSP for a Layer 2 VPN connection by instance

Layer 2VPN Name

Type the name of the Layer 2 VPN to ping.

Remote Site Identifier

Type the remote site identifier of the Layer 2 VPN to ping.

Source Address

Type the source IP address of the ping request packet—a valid address configured on a J Series device interface.

Local Site Identifier

Type the local site identifier of the Layer 2 VPN to ping.

Count

From the list, select the number of ping requests to send. The default is 5 requests.

Detailed Output

Select the check box to display detailed output rather than brief ping output.
Ping LSP to a Layer 2 circuit remote site by interface

Interface

From the list, select the J Series device interface on which ping requests are sent. If you select any, the ping requests are sent on all interfaces.

Source Address

Type the source IP address of the ping request packet—a valid address configured on a J Series device interface.

Count

From the list, select the number of ping requests to send. The default is 5 requests.

Detailed Output

Select the check box to display detailed output rather than brief ping output.
Ping LSP to a Layer 2 circuit remote site by VCI

Remote Neighbor

Type the IP address of the remote neighbor (PE router) within the virtual circuit to ping.

Circuit Identifier

Type the virtual circuit identifier for the Layer 2 circuit.

Source Address

Type the source IP address of the ping request packet—a valid address configured on a J Series device interface.

Count

From the list, select the number of ping requests to send.

Detailed Output

Select the check box to display detailed output rather than brief ping output.
Ping endpoint of LSP

VPN Prefix

Type either the LDP FEC prefix and length or the RSVP LSP endpoint address for the LSP to ping.

Source Address

Type the source IP address of the ping request packet—a valid address configured on a J Series device interface.

Count

From the list, select the number of ping requests to send.

Detailed Output

Select the check box to display detailed output rather than brief ping output.
Table 2: Ping MPLS Results and Output Summary

Field

Function

Exclamation point (!)

Echo reply was received.

Period (.)

Echo reply was not received within the timeout period.

x

Echo reply was received with an error code. Errored packets are not counted in the received packets count and are accounted for separately.

number packets transmitted

number—Number of ping requests (probes) sent to a host.

number packets received

number—Number of ping responses received from a host.

percentage packet loss

percentage—Number of ping responses divided by the number of ping requests, specified as a percentage.

time

For Layer 2 circuits only, the number of milliseconds required for the ping packet to reach the destination. This value is approximate, because the packet has to reach the Routing Engine.

Output = Packet loss of 100 percent

If the device does not receive ping responses from the destination host (the output shows a packet loss of 100 percent), one of the following explanations might apply:

  • The host is not operational.

  • There are network connectivity problems between the device and the host.

  • The host might be configured to ignore echo requests.

  • The host might be configured with a firewall filter that blocks echo requests or echo responses.

  • The size of the echo request packet exceeds the MTU of a host along the path.

  • The outbound node at the remote endpoint is not configured to handle MPLS packets.

  • The remote endpoint's loopback address is not configured to 127.0.0.1.

Related Documentation