I agree this works, but still that doesn;t answers one thing....Cisco and unix boxes where this * trouble is seen doesn;t use ICMP but uses UDP port for the trace output....
then howcome this is the fix !!!!! Thanks -----Original Message----- From: William Pearch [mailto:[EMAIL PROTECTED]] Sent: Friday, January 17, 2003 1:13 AM To: [EMAIL PROTECTED] Subject: RE: Traceroute troubles [7:61247] Solved my own problem - see CSCdu43762 on the CCO. Shows up with the 7200 and an NSE-1 and (evidently though they are not listed) the 1760, 2621, 2621XM, 2611 and 1720. Solution is to turn off PXF (rate limiting of ICMP unreachables) using: no ip icmp rate unreach Lesson learned? Read everything... :) Bill -----Original Message----- From: William Pearch Sent: Thu 1/16/2003 8:12 PM To: William Pearch; [EMAIL PROTECTED] Cc: Subject: Traceroute troubles Why does traceroute seem to have problems with the second check of a final hop? RouterA-----RouterB When trace from routerA loopback to routerB loopback, first one comes back fine, second is a * and third is fine. Seems wierd - 500 pings all go swell. Then to top it off... RouterA trace to RouterA loopback0, first one comes back fine, second is a * and third is fine. 500 pings all go swell. I've tried over ethernet, fast ethernet, serial (HDSL and frame relay). Same behavior on my 2600's and 1700's. All running 12.2.13T. I wasn't able to find anything on the CCO this evening. Thoughts? Bill Pearch, Anchorage Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=61317&t=61247 -------------------------------------------------- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]