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, 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.
In Contrail Service Orchestration (CSO) Release 5.0, the following devices support ping:
NFX Series: NFX150, NFX250
SRX Series: SRX300, SRX320, SRX340, SRX345, SRX1500, SRX4100, SRX4200, SRX4600
To perform the ping operation:
- Do one of the following:
To initiate a ping from a provider hub device, select Resources > Provider Hub Devices.
The :Provider Hub Devices page appears.
To initiate a ping from a tenant device, select Resources > Tenant Devices.
The Tenant Devices page appears.
- Select a device from the list of devices displayed and
click More > Ping.
The Ping page appears.
You can initiate a ping from a device only when its operational status (in CSO) is Up.
- Complete the configuration according to the guidelines
provided in Table 1.
Fields marked with an asterisk (*) are mandatory.
- Click Ping to initiate the ping request.
A job is created and a Ping Progress page appears. After the host 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 2.
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 1: Fields on the Ping page
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.
Range: 1 through 300.
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.
Click the toggle button to enable or disable (default) the display of hostname of the hops along the path to the remote host.
Click the toggle button to enable or disable (default) sending ping requests rapidly.
If you enable this option, the 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.
Note: The ping results are displayed in a single consolidated message instead of individual messages for each ping request packet sent.
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.
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.
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..
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 2: Fields on the Ping Result page
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 device sends the ping request and the time when the device receives a response from the remote host.
Displays the following:
Sequence number of all the ping request packets.
Result of the ping request packets—Success or Failure.
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 (in microseconds) to receive response to a ping request packet.