Yeah, so what you have going on here is load-balancing as you said. When you traceroute something, it will send 3 packets out for each hop. So if you look at your example there, the first packet gets send out to 173.x.x.x , the second to 172.x.x.x then cycles back to the first one...classic load balancing. If you do a show ip route 150.16.10.1 you should see 2 equal cost paths.
On Fri, Aug 14, 2009 at 8:35 AM, Taqdir Singh <[email protected]> wrote: > R0============R1 > > R0 and R1 are directly connected by two links like below > > R0(f1/0)(173.16.10.1)-----R1(f1/0)173.16.10.2/24 > R0(s0/0)(172.16.10.1/24)-----R1(s0/1)172.16.10.2/24<http://172.16.10.1/24%29-----R1%28s0/1%29172.16.10.2/24> > > On R0 I have loopback lo = 150.16.10.1/24 which I am advertising through > EIGRP. > and EIGRP is also running on both R0 and R1 on both the links. > > Just for loadbalancing for route 150.16.10.0, I have configured same > bandowidth and delay on both the links on R1. > > When I traceroute from R1 to 150.16.10.1 , how packet is actually going , > can any1 please explain this ?? > > R1#tr 150.16.10.1 > Type escape sequence to abort. > Tracing the route to 150.16.10.1 > 1 173.16.10.1 44 msec > 172.16.10..1 56 msec > 173.16.10.1 64 msec > R1# > > > > > Taqdir Singh > 91-9911709496 > Do today what others won't, so that you can live tomorrow what others > can't > > > _______________________________________________ > For more information regarding industry leading CCIE Lab training, please > visit www.ipexpert.com > > -- Regards, Joe Astorino - CCIE #24347 R&S Technical Instructor - IPexpert, Inc. Cell: +1.586.212.6107 Fax: +1.810.454.0130 Mailto: [email protected]
_______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com
