Re: Weird trace results [7:5259]

All, When performing a trace on an IP address (for "testing purposes we'll use 10.1.2.3) this is the result I get: router#trace 10.1.2.3 Type escape sequence to abort. Tracing the route to 10.1.2.3 1 192.1.2.2 4 msec 192.1.2.10 4 msec 192.1.2.2 4 msec 2 10.1.2.3 0 msec 4 msec 4 mse

Re: Weird trace results [7:5259]

I suggest that you check your routing table, that's what come out my mind. HTH Vincent Chong ""Watson, Rick, CTR, OUSDC"" All, > > When performing a trace on an IP address (for "testing purposes we'll use > 10.1.2.3) this is the result I get: > > router#trace 10.1.2.3 > > Type escape sequence

Re: Weird trace results [7:5259]

I've seen this before in networks using HSRP and no route caching. Is it causing a problem or just interesting? Darren At 11:59 AM 05/21/2001 -0400, Vincent Chong wrote: >I suggest that you check your routing table, that's what come out my mind. > >HTH >Vincent Chong > >""Watson, Rick, CTR, OUS

Re: Weird trace results [7:5259]

Like the other reply sez, a routing table check may be in order, you have multiple routes out of equal preference? Brian "Sonic" Whalen Success = Preparation + Opportunity On Mon, 21 May 2001, Watson, Rick, CTR, OUSDC wrote: > All, > > When performing a trace on an IP address (for "testing pur

Re: Weird trace results [7:5259]

ssage- From: Watson, Rick, CTR, OUSDC [mailto:[EMAIL PROTECTED]] Sent: Monday, May 21, 2001 11:53 AM To: [EMAIL PROTECTED] Subject: Re: Weird trace results [7:5259] All, When performing a trace on an IP address (for "testing purposes we'll use 10.1.2.3) this is the result I get: router

Re: Weird trace results [7:5259]

Just a couple other things to chew on.. There are two varieties of Trace. Cisco and Unix traces send to a large UDP port. The goal is that the final destination send an ICMP Destination Unreachable/Port Unreachable. This is in addition to the fact that the intermediate hops decrement the T