How does Ciscoworks use ping and trace root tests to identify potential faults?
You send an ICMP Echo Request (ping) to an IP node. If it is enabled, and typically it is, it will respond back with an ICMP Echo Reply. This reply will show various bits of information such as the latency on the link and more importantly number of packet drops. If the pack drop rate is quite high, this typically indicates there are errors in the transmission. (High latency can be attributed to poor performance) Traceroute is particularly useful in determining where an issue may lie. For example, if I couldn’t reach my Server in the US from the UK, I will issue a traceroute which will help me narrow down where the fault lies e.g. is it my UK office, UK ISP, USA ISP, USA Office or Other that is cause the problem? Traceroute will in a way, Ping each router on the way to the US office. Letting me know how far along the line the packet has got. If I suddenly get to a router that is not sending me a ping-reply, I can start to dig deeper. E.g. it can can get to the USA ISP but not further, n
