[c-nsp] Traceroute question.

[Raz Muhammad]

Hi all,
As we all know when we start plunging our heads into amazing world of 
TCP/IP ,  we discover 2 great tools for diagnosing faults. i.e PING and 
Traceroute. I reckon they are great.
But what happens occasionaly someone usually endusers novice networking 
starters  feel some latency  to a  certain webpage or an y IP node, and  
he/she would  than  refresh his  TCP/IP skills and wold  start  pinging 
and  tracerouting  the target IP.
finally they see a delay on one of your border routers , and they jump 
off and say hugh its the ISP who is the culprit. and they start blaming 
thier ISP's.
But when you dif further into these issues Cisco says a router will deal 
with a transitional traceroute  ping request with low priority and would 
deal with the packet with a bit of latency, if the router;s processor is 
busy doing other high priority stuff.
what Cisco says is quite logical as well, but I wonder why the 
definition for same tools vary for a pro and for a beginner.
atleast this should be  mention with Traceroute notes that delay in 
traceroute pings is not a conclusive test for some latency issue.

Regards




-- 
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.308 / Virus Database: 266.7.4 - Release Date: 18/03/2005