Cisco Cisco Packet Data Gateway (PDG)

 

▄  VPC-VSM System Administration Guide, StarOS Release 19 

   

--- 192.29.96.1 ping statistics -- 

5 packets transmitted, 5 received, 0% packet loss, time 4005ms 

rtt min/avg/max/mdev = 0.606/2.090/4.831/1.839 ms 

If no response is received from the target follow these troubleshooting procedures: 



 

Verify that the correct IP address was entered. 



 

Attempt to ping a different device on the same network. If the ping was successful then it is likely that your 

system configuration is correct. Verify that the device you are attempting to ping is powered and functioning 
properly. 



 

Verify the port is operational. 



 

Verify that the configuration of the ports and interfaces within the context are correct. 



 

If the configuration is correct and you have access to the device that you’re attempting to ping, ping the system 

from that device. 



 

If there is still no response, it is likely that the packets are getting discarded by a network device. Use the 

traceroute or traceroute6 and show ip static-route commands discussed in this segment to further 
troubleshoot the issue. 

The traceroute or traceroute6 command collects information on the route data will take to a specified host. This is a 
useful troubleshooting command that can be used to identify the source of significant packet delays or packet loss on the 
network. This command can also be used to identify bottle necks in the routing of data over the network. 

The traceroute command has the following syntax: 

traceroute { host_name | host_ipv4_address } [ count packets ] [ df ] [ maxttl 
max_ttl ] [ minttl min_ttl ] [ port port_number ] [ size octet_count ] [ src { 
src_host_name | src_host_ipv4_address } ] [ timeout seconds ] [ vrf vrf_nam ] 

For complete information regarding the above command, see the Exec Mode Commands chapter of the Command line 
Interface Reference. 

The following displays a sample output. 

traceroute to 192.168.250.1 (192.168.250.1), 30 hops max, 40 byte packets 

 1  192.168.250.1 (192.168.250.1)  0.446 ms  0.235 ms 0.178 ms