Do show ip cef 150.16.10.1 internal to see how the packets are getting distributed. Also read up on CCO how load-sharing per-packet and per-flow works. As for the example you provided.. It uses two paths as expected.
Side note: I'd keep off using load-sharing per-packet as you're mixing two different mediums (Serial and Fast Ethernet) which will have different latencies - starting with serialization delay (*) - which WILL cause packet reordering at the destination. With the default hash settings (IP SA/DA only) per flow will work in real life too. *) SD = frame size (b) / link bandwidth (bps) :) Kaj > From: Taqdir Singh <[email protected]> > Date: Fri, 14 Aug 2009 05:35:41 -0700 > To: <[email protected]> > Subject: [OSL | CCIE_RS] EIGRP loadbalancing , packet flow issue ? > > When I traceroute from R1 to 150.16.10.1 , how packet is actually going , can > any1 please explain this ??
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com
