The ASN is used as a tie breaker when you have two EIGRP routes with the same Administrative Distance.
I'm using cat4500-ipbasek9-mz.122-46.SG1.bin. The behavior I'm experiencing is consistent with: http://www.cisco.com/en/US/tech/tk365/technologies_q_and_a_item09186a008012dac4.shtml#eight2 Eventually I will converge to a single EIGRP ASN, but I was wondering if there was a way to do this until then. Right now I'm just filtering routes to direct traffic in the intended direction. -Yuri On Fri, Dec 10, 2010 at 5:49 PM, Rob Taylor <[email protected]> wrote: > On 12/10/2010 6:00 PM, Gert Doering wrote: > >> Hi, >> >> On Thu, Dec 09, 2010 at 03:51:20PM -0800, Yuri Bank wrote: >> >> >>> Does anyone know of a way to make IOS see two distinct EIGRP processes ( >>> Different ASNs ) equally. The standard behavior (On my version of IOS at >>> least) is to choose the route which was learned from the lower EIGRP ASN >>> regardless of metric. I can influence which routes are chosen by >>> manipulating the Administrative Distance in the EIGRP process, but this >>> is >>> very limited in control. I would like to use the EIGRP metric for more >>> optimal routing. >>> >> >> Though I have not tested this recently, I thought we DID compare metrics > for two eigrp processes with the same prefix and same AD. > > What version are you running, out of curiosity? > > Rob > _______________________________________________ > cisco-nsp mailing list [email protected] > https://puck.nether.net/mailman/listinfo/cisco-nsp > archive at http://puck.nether.net/pipermail/cisco-nsp/ > _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
