Dear Bryan, I tried changing the BGP next hop and it also didn't work, and about the IOS it tried this secanrio on both 12.2S and 12.3T and they are both producing the same output and as per Marko comment that there is no misbihaving we only need to find out why the code is making this specific selection.
On Mon, Oct 19, 2009 at 1:50 AM, Bryan Bartik <[email protected]> wrote: > This is an interesting scenario. There's only so many attributes left :) I > tried changing RT and RD, didn't do anything. Perhaps the BGP next hop > attribute is used? Try making R3 (123.123.123.3) lower than R2 > (123.123.123.2)... > > On Sun, Oct 18, 2009 at 3:41 PM, Marko Milivojevic <[email protected]>wrote: > >> On Sun, Oct 18, 2009 at 22:22, Matt Hill <[email protected]> wrote: >> > I've been looking at this to see what transpires... It certainly is >> > an interesting one... I certainly have not got a decent answer... >> > >> > The only thing I can think of is changing the IOS. Try a slightly >> > different feature set, there might be a bug in your BGP code. It's >> > normally the only way of explaining ridiculous things like this... >> >> I'm not sure that would help in any way. Nothing is misbehaving here, >> i.e. both routes *should* be advertised and one should be selected as >> the best. The problem is that we can't really figure out why... >> >> Anyone else with an idea? >> >> -- >> Marko >> CCIE #18427 (SP) >> My network blog: http://cisco.markom.info/ >> _______________________________________________ >> For more information regarding industry leading CCIE Lab training, please >> visit www.ipexpert.com >> > > > > -- > Bryan Bartik > CCIE #23707 (R&S), CCNP > Sr. Support Engineer - IPexpert, Inc. > URL: http://www.IPexpert.com >
_______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com
