ISSUE WITH RIB failure

[networkinblood]

As I read in documents , in case of BGP RIB failure , it do advertise RIB failure route to their peers but I tested in lab (eveng ) RIB failure prefix is not getting advertise to their peer (i have not used suppress inactive command ).. pls find the attached config .

ON RR router 

AG1#sh ip bg
AG1#sh ip bgp
BGP table version is 36, local router ID is 101.101.101.101
Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,
r RIB-failure, S Stale
Origin codes: i - IGP, e - EGP, ? - incomplete

Network Next Hop Metric LocPrf Weight Path
r>i1.1.1.1/32 1.1.1.1 0 100 0 ?
r>i3.3.3.3/32 3.3.3.3 0 100 0 ?
r>i10.0.0.0/24 1.1.1.1 0 100 0 ?
r>i10.0.1.0/24 1.1.1.1 0 100 0 ?
r>i20.0.1.0/24 3.3.3.3 0 100 0 ?
*>i172.16.0.2/32 3.3.3.3 0 100 0 ?
*> 192.168.0.1/32 0.0.0.0 0 32768 ?
AG1#

On RR client router 

CSS2#SH IP BGp
BGP table version is 2, local router ID is 2.2.2.2
Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,
r RIB-failure, S Stale
Origin codes: i - IGP, e - EGP, ? - incomplete

Network Next Hop Metric LocPrf Weight Path
*>i192.168.0.1/32 100.100.100.100 0 100 0 ?
CSS2#sh run | b r bg
router bgp 1
bgp router-id 2.2.2.2
bgp log-neighbor-changes
neighbor 100.100.100.100 remote-as 1
neighbor 100.100.100.100 update-source Loopback0
neighbor 101.101.101.101 remote-as 1
neighbor 101.101.101.101 update-source Loopback0
!
address-family ipv4
neighbor 100.100.100.100 activate
neighbor 100.100.100.100 route-reflector-client
neighbor 101.101.101.101 activate
neighbor 101.101.101.101 route-reflector-client
no auto-summary
no synchronization
exit-address-family

[Harold Ritter · Accepted solution]

Hi @networkinblood ,

You are correct in saying that the routes should be propagated by BGP, even if they are marked with a RIB failure. I think the issue is somewhere else. 

I see 172.16.0.2/32 is not flagged for RIB failure, but it is not seen either on CSS2, probably for the same reason as the other prefixes. I believe you have not enabled route reflection on AG1.

Since CSS2 is a route reflector client you do not need "neighbor route-reflector-client" configured on  neighbor 100.100.100.100 and 101.101.101.101 (AG1), but you need to make sure that you include this statement on the neighbors that are route reflector clients (such as CSS2 (2.2.2.2)) in AG1 BGP configuration, since AG1 is the route reflector. You will need to do the same on 100.100.100.100, if it it also a route reflector.

Regards,

[networkinblood]

Yes I ll share the same in few time

[networkinblood]

Thnks a lot sir for your valuable reply ..I got misunderstood issue with
RR configuration, not an issue with RIB failure prefix .

Once I ll test the same in lab and come back to you .Once again thank you
sir for support. Love from India .

[MHM Cisco World · Accepted solution]

I think the mis config and you config two RR in your topology, 

CSS2 which is RR client is mis config with this command router-reflector-client where this command must config in RR not in RR client.