Help Center User GuideGetting StartedFAQ
 
X
User Guide
Getting Started
FAQ
Contents  

Identifying Connectivity Issues by Using Ping

You can use Contrail Service Orchestration (CSO) to perform a ping operation from a device (provider hub, tenant device, CPE device, EX switch, enterprise hubs, or next-generation firewall device) to a remote host for identifying issues in connectivity with the remote host.

When you ping a remote host from a device, an Internet Control Message Protocol (ICMP) packet is sent to the remote host. By analyzing the results of the ping operation, you can identify the possible device connectivity issues between the remote host and the device.

Note In Contrail Service Orchestration (CSO) Release 5.0, the following devices support ping:

  • EX Series: EX2300, EX3400, and EX4300

  • MX Series

  • NFX Series: NFX150, NFX250

  • SRX Series: SRX300, SRX320, SRX340, SRX345, SRX1500, SRX4100, SRX4200, SRX4600

  • vSRX

Procedure

To perform the ping operation:

  1. Select Resources > Devices.

    The Devices page appears.

  2. Select a device from the list of devices displayed and click More > Ping.

    The Ping page appears.

    Note You can ping from a device only when its operational status is Up in CSO.

  3. Complete the configuration according to the guidelines provided in Table 92.

    Note  Fields marked with an asterisk (*) are mandatory.

  4. Click Ping to initiate the ping request.

    A job is created and the Ping Progress page appears. After the device sends the ping packets, the Ping Result page appears. . If the ping operation is successful, the Ping Result page displays the parameters specified in Table 93.

    If the ping operation fails, the Ping Result page displays an appropriate error message (such as No response or No route to host), indicating that there is an issue in the connectivity to the remote host.

Table 92: Fields on the Ping page

Field

Description

Remote Host

Enter the IPv4 address or hostname of the remote host.

Ping Request Packets

Enter the number of ping request packets to be sent to the remote host.

Default: 5.

Range: 1 through 300.

Advanced

Source Interface

Select the source interface on the device through which you want to send the ping request to the remote host. If you do not select a source interface, ping requests are sent on all interfaces.

To clear the selected interface, click Clear All and select another interface.

Hostname Resolution

Click the toggle button to enable or disable (default) the display of hostname of the hops along the path to the remote host.

Rapid Ping

Click the toggle button to enable or disable (default) sending ping requests rapidly.

If you enable this option, the source device sends a minimum of 100 ping request packets per second or sends a packet as soon as a response to the previous packet is received, whichever is greater.

  • If the source device does not receive a response for 500 ms, timeout is considered.

  • If the source device receives a response within 500 ms, the next ping request packet is sent immediately.

Note: The ping results are displayed in a single consolidated message instead of individual messages for each ping request packet sent.

Packet Fragmentation

Click the toggle button to enable or disable (default) the fragmenting of ping request packets.

If packet fragmentation is disabled, ping packets with the maximum transmission unit (MTU) greater than 1500 bytes are dropped.

Packet Size (bytes)

Enter the size (in bytes) of the ping request packet.

Default: 56 bytes.

Range:

  • 1 through 1,472 bytes, if packet fragmentation is disabled.

  • 1 through 65,468 bytes, if packet fragmentation is enabled.

Wait Time (seconds)

Enter the time (in seconds) for which the source device waits for a response to the ping request packet. The source device considers the remote host as not reachable after the wait time elapses.

Default: 10 seconds.

Range: 0 through 600 seconds.

Incoming Interface

Click the toggle button to include or exclude (default) information (on the Ping Result page) about the interface on the source device that receives the ping responses..

Routing Instance

Select a specific routing instance that the ping request packets can use to reach the remote host.

The ping result displays the information about the connectivity between the source device and the remote host based on the selected routing instance.

To clear the selected routing instance, click Clear All and select another routing instance.

Table 93: Fields on the Ping Result page

Field

Description

Packet Loss

Displays the percentage of ping packets sent for which the source device did not receive a response.

Round Trip Time Taken (in µs)

Displays the following information about the duration (in microseconds) between the time when the source device sends the ping request and the time when the source device receives a response from the remote host.

Displays the following:

  • Minimum: The minimum time taken to receive a response for a ping request packet.

  • Maximum: The maximum time taken to receive a response for a ping request packet.

  • Average: The average time taken to receive a response for all the ping request packets sent in a ping operation.

  • Standard Deviation: The variation of the round trip time from the mean round trip time.

Details

Sequence

Sequence number of all the ping request packets.

Result

Result of the ping request packets—Success or Failure.

Incoming Interface

Interface on the source device on which the responses are received for the ping requests.

This data appears if you have enabled the Incoming Interface option on the Ping page.

Time Taken

Time taken (in microseconds) to receive response to a ping request packet.

Help us to improve. Rate this article.
Feedback Received. Thank You!

Ask questions in TechWiki

Check documentation in TechLibrary

Rating by you:      
X

Additional Comments

800 characters remaining

May we contact you if necessary?

Name:
Email:

Need product assistance? Contact Juniper Support

Submit