Ping Validation Testing from a Cisco IOS Router
Related Articles to Read
Ping testing is a fundamental basis of troubleshooting ip network testing. Pings are the lowest form of traffic, and generally are the most likely to be disregarded by equipment, or responded to last in the event that there is processor utilization or other traffic utilization. Therefore if pings go through, it is highly likely that all other traffic is going through, likey better than pings. Pings allow detection of lost packets and can help determine if there are errors or help in Debugging Ethernet Port Duplex and Speed Settings. Sending a series of pings simulates traffic flow over a network interface, and as traffic goes over an interface potential errors can be detected.
- Pings use bandwidth on a link, and often substantial amounts, dependent on the capability of the system to send pings.
- Ping testing generally does not negatively affect current operations of the customers connection, however the pinging will use some of the bandwidth.
- Ping is the lowest form of packet, therefore if pings go through with no reliability issues, the other traffic is likely to have no reliability problems.
- Ping testing can located instances of latency that could help in finding QOS issues on a customer link that are underlying in the network layer.
ALL TROUBLESHOOTING AND DEBUGGING OF CONNECTIONS SHOULD START AND FINISH WITH PING TESTING.
Ping testing from a device
Ping testing over short periods of time will not invoke a problem with a customer voice traffic, as ping has a lower priority than VOIP QOS traffic. However, all ping testing to and from cisco routers, or other network equipment is generally not considered accurate, because network equipment is designed to send traffic through it, not to it. Cisco routers are going to delay ping traffic that go to its interface as the Cisco router or switch, uses only the main cpu to ship the traffic.