Solved: Failed iBGP

John Blakley · ‎07-19-2010

All,

Over the weekend, I attempted to convert us from a single router to a redundant router with hsrp. This worked fine, but in the process I wanted to change the currently configured ebgp config between our switch and routers to ibgp.

The problem was that the switch was receiving all of the routes from RtrA, but only 2 routes from RtrB. All of the routers were peered and sessions were established. I can't reproduce this is GNS, so I'm wondering what could've happened. I'm going to eventually have to revisit this because this is the design that I want. Any ideas why this could've happened? I've attached a diagram of how it was laid out. I was always under the impression that a fully meshed ibgp peering would pass all routes between ibgp peers. In my bgp table on the switch, I only showed the routes from RtrA and 2 from B that were external to this AS. I should've had about 180 subnets.

Thanks,

John

HTH, John *** Please rate all useful posts ***

milan.kulik · ‎07-19-2010

Hi John,

more details would be necessary about the missing prefixes.

What I can imagine is:

Let's say both RtrA and RtrB are receiving the same prefixes from eBGP.

RtrA is sending all prefixes to RtrB via iBGP.

RtrB has something in the configuration (weight, local preference), which makes the prefixes received from RtrA more preferred than the same prefixes received from eBGP.

In that case, RtrB would NOT advertise these prefixes to the 3750 switch (as only best prefixes are advertised but prefixes received by iBGP are not advertised to another iBGP neighbor).

Wasn't that your case?

BR,

Milan

View solution in original post

milan.kulik · ‎07-19-2010