Sie sind auf Seite 1von 7

BGP RIB Failures and BGP Synchronization

BGP RIB-Failures are common when BGP synchronization is enabled. In general BGP RIB-
Failures are BAD, but in the case of BGP Synchronization, they are GOOD. When you check the
reason for the RIB-Failure using the "sh ip bgp rib-failure" command you should see the comment
"Higher admin distance". Then if you check the output of the "sh ip bgp <route prefix/prefix-
length>" you should see the route as "synchronized". This is a GOOD RIB-Failure, because the
route is advertised to the eBGP speakers. See the example outputs below.

R3_AS65100#sh ip bgp
BGP table version is 48, local router ID is 3.3.3.3
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


* i10.0.0.0 10.10.45.5 0 100 0i
*> 0.0.0.0 0 32768 i
*> 20.0.0.0/12 192.168.13.1 0 0 65200 i
*> 20.0.0.0 192.168.13.1 0 0 65200 i
*> 20.16.0.0/12 192.168.13.1 0 0 65200 i
*> 20.32.0.0/12 192.168.13.1 0 0 65200 i
*> 20.48.0.0/12 192.168.13.1 0 0 65200 i
*> 30.0.0.0/12 192.168.23.2 0 0 65300 i
*> 30.0.0.0 192.168.23.2 0 0 65300 i
*> 30.16.0.0/12 192.168.23.2 0 0 65300 i
*> 30.32.0.0/12 192.168.23.2 0 0 65300 i
*> 30.48.0.0/12 192.168.23.2 0 0 65300 i
* i40.0.0.0/12 10.10.45.5 0 100 0 65400 i
r>i40.0.0.0 10.10.45.5 0 100 0 65400 i
* i40.16.0.0/12 10.10.45.5 0 100 0 65400 i
* i40.32.0.0/12 10.10.45.5 0 100 0 65400 i
* i40.48.0.0/12 10.10.45.5 0 100 0 65400 i

R3_AS65100#sh ip bgp rib-failure


Network Next Hop RIB-failure RIB-NH Matches
40.0.0.0 10.10.45.5 Higher admin distance n/a

R3_AS65100#sh ip bgp 40.0.0.0/8


BGP routing table entry for 40.0.0.0/8, version 38
Paths: (1 available, best #1, table Default-IP-Routing-Table, RIB-failure(17))
Advertised to update-groups:
2

© BTS Communications, LLC 1 01/02/12


BGP RIB Failures and BGP Synchronization

65400, (received & used)


10.10.45.5 (metric 128) from 10.10.45.5 (5.5.5.5)
Origin IGP, metric 0, localpref 100, valid, internal, synchronized, best

R3_AS65100#sh ip bgp nei 192.168.13.1 advertised-routes


BGP table version is 48, local router ID is 3.3.3.3
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


*> 10.0.0.0 0.0.0.0 0 32768 i
*> 20.0.0.0/12 192.168.13.1 0 0 65200 i
*> 20.0.0.0 192.168.13.1 0 0 65200 i
*> 20.16.0.0/12 192.168.13.1 0 0 65200 i
*> 20.32.0.0/12 192.168.13.1 0 0 65200 i
*> 20.48.0.0/12 192.168.13.1 0 0 65200 i
*> 30.0.0.0/12 192.168.23.2 0 0 65300 i
*> 30.0.0.0 192.168.23.2 0 0 65300 i
*> 30.16.0.0/12 192.168.23.2 0 0 65300 i
*> 30.32.0.0/12 192.168.23.2 0 0 65300 i
*> 30.48.0.0/12 192.168.23.2 0 0 65300 i
r>i40.0.0.0 10.10.45.5 0 100 0 65400 i <--- route is still advertised
Total number of prefixes 12
R3_AS65100#

On R5 we have two routes that show up as RIB-Failures. Again, when we look at the outputs of the
"sh ip bgp rib-failure" and "sh ip bgp <prefix/prefix-length> commands we want to look for the
those keywords "Higher admin distance" and "synchronized". See the outputs below.

R5_AS65100#sh ip bgp
BGP table version is 86, local router ID is 5.5.5.5
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


*> 10.0.0.0 0.0.0.0 0 32768 i
*i 10.10.34.3 0 100 0i
* i20.0.0.0/12 10.10.34.3 0 100 0 65200 i
r>i20.0.0.0 10.10.34.3 0 100 0 65200 i

© BTS Communications, LLC 2 01/02/12


BGP RIB Failures and BGP Synchronization

* i20.16.0.0/12 10.10.34.3 0 100 0 65200 i


* i20.32.0.0/12 10.10.34.3 0 100 0 65200 i
* i20.48.0.0/12 10.10.34.3 0 100 0 65200 i
* i30.0.0.0/12 10.10.34.3 0 100 0 65300 i
r>i30.0.0.0 10.10.34.3 0 100 0 65300 i
* i30.16.0.0/12 10.10.34.3 0 100 0 65300 i
* i30.32.0.0/12 10.10.34.3 0 100 0 65300 i
* i30.48.0.0/12 10.10.34.3 0 100 0 65300 i
*> 40.0.0.0/12 192.168.56.6 0 0 65400 i
*> 40.0.0.0 192.168.56.6 0 0 65400 i
*> 40.16.0.0/12 192.168.56.6 0 0 65400 i
*> 40.32.0.0/12 192.168.56.6 0 0 65400 i
*> 40.48.0.0/12 192.168.56.6 0 0 65400 i

R5_AS65100#sh ip bgp rib-failure


Network Next Hop RIB-failure RIB-NH Matches
20.0.0.0 10.10.34.3 Higher admin distance n/a
30.0.0.0 10.10.34.3 Higher admin distance n/a

R5_AS65100#sh ip bgp 20.0.0.0/8


BGP routing table entry for 20.0.0.0/8, version 72
Paths: (1 available, best #1, table Default-IP-Routing-Table, RIB-failure(17))
Advertised to update-groups:
2
65200, (received & used)
10.10.34.3 (metric 128) from 10.10.34.3 (3.3.3.3)
Origin IGP, metric 0, localpref 100, valid, internal, synchronized, best

R5_AS65100#sh ip bgp 30.0.0.0/8


BGP routing table entry for 30.0.0.0/8, version 73
Paths: (1 available, best #1, table Default-IP-Routing-Table, RIB-failure(17))
Advertised to update-groups:
2
65300, (received & used)
10.10.34.3 (metric 128) from 10.10.34.3 (3.3.3.3)
Origin IGP, metric 0, localpref 100, valid, internal, synchronized, best
R5_AS65100#

But what about the /12 subnet routes we have in the BGP table? Why do these show no RIB-
Failure, yet they are not advertised to our external BGP speaker R6? Because they are "not
synchronized". Remember the BGP Synchronization rule. See the output below.

© BTS Communications, LLC 3 01/02/12


BGP RIB Failures and BGP Synchronization

R5_AS65100#sh ip bgp 20.0.0.0/12


BGP routing table entry for 20.0.0.0/12, version 0
Paths: (1 available, no best path)
Not advertised to any peer
65200, (received & used)
10.10.34.3 (metric 128) from 10.10.34.3 (3.3.3.3)
Origin IGP, metric 0, localpref 100, valid, internal, not synchronized

R5_AS65100#sh ip bgp 20.16.0.0 /12


BGP routing table entry for 20.16.0.0/12, version 0
Paths: (1 available, no best path)
Not advertised to any peer
65200, (received & used)
10.10.34.3 (metric 128) from 10.10.34.3 (3.3.3.3)
Origin IGP, metric 0, localpref 100, valid, internal, not synchronized

R5_AS65100#sh ip bgp 20.32.0.0 /12


BGP routing table entry for 20.32.0.0/12, version 0
Paths: (1 available, no best path)
Not advertised to any peer
65200, (received & used)
10.10.34.3 (metric 128) from 10.10.34.3 (3.3.3.3)
Origin IGP, metric 0, localpref 100, valid, internal, not synchronized

R5_AS65100#sh ip bgp 20.48.0.0 /12


BGP routing table entry for 20.48.0.0/12, version 0
Paths: (1 available, no best path)
Not advertised to any peer
65200, (received & used)
10.10.34.3 (metric 128) from 10.10.34.3 (3.3.3.3)
Origin IGP, metric 0, localpref 100, valid, internal, not synchronized
R5_AS65100#

Notice in R6s routing table there are no entries for the 20.0.0.0/12, 20.16.0.0/12, 20.32.0.0/12 and
20.48.0.0/12 subnets.

R6_AS65400#sh ip rou
Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2
i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2

© BTS Communications, LLC 4 01/02/12


BGP RIB Failures and BGP Synchronization

ia - IS-IS inter area, * - candidate default, U - per-user static route


o - ODR, P - periodic downloaded static route

Gateway of last resort is not set

B 20.0.0.0/8 [20/0] via 192.168.56.5, 00:28:33


C 192.168.56.0/24 is directly connected, Serial0/0
40.0.0.0/8 is variably subnetted, 5 subnets, 2 masks
C 40.32.0.0/12 is directly connected, Loopback32
C 40.48.0.0/12 is directly connected, Loopback48
C 40.0.0.0/12 is directly connected, Loopback0
S 40.0.0.0/8 is directly connected, Null0
C 40.16.0.0/12 is directly connected, Loopback16
B 10.0.0.0/8 [20/0] via 192.168.56.5, 00:12:12
B 30.0.0.0/8 [20/0] via 192.168.56.5, 00:28:33
R6_AS65400#

So how do we get these to be advertised? We have to "synchronize" our iBGP and IGP. Then we
will see these routes on R6. We need to include the "subnets" keyword on our redistribution
command back on R3. Now the routes show as “synchronized” in the BGP table.

R5_AS65100#sh ip bgp 20.0.0.0/12


BGP routing table entry for 20.0.0.0/12, version 90
Paths: (1 available, best #1, table Default-IP-Routing-Table, RIB-failure(17))
Advertised to update-groups:
2
65200, (received & used)
10.10.34.3 (metric 128) from 10.10.34.3 (3.3.3.3)
Origin IGP, metric 0, localpref 100, valid, internal, synchronized, best

R5_AS65100#sh ip bgp 20.16.0.0/12


BGP routing table entry for 20.16.0.0/12, version 88
Paths: (1 available, best #1, table Default-IP-Routing-Table, RIB-failure(17))
Advertised to update-groups:
2
65200, (received & used)
10.10.34.3 (metric 128) from 10.10.34.3 (3.3.3.3)
Origin IGP, metric 0, localpref 100, valid, internal, synchronized, best

© BTS Communications, LLC 5 01/02/12


BGP RIB Failures and BGP Synchronization

R5_AS65100#sh ip bgp 20.32.0.0/12


BGP routing table entry for 20.32.0.0/12, version 97
Paths: (1 available, best #1, table Default-IP-Routing-Table, RIB-failure(17))
Advertised to update-groups:
2
65200, (received & used)
10.10.34.3 (metric 128) from 10.10.34.3 (3.3.3.3)
Origin IGP, metric 0, localpref 100, valid, internal, synchronized, best

R5_AS65100#sh ip bgp 20.48.0.0/12


BGP routing table entry for 20.48.0.0/12, version 98
Paths: (1 available, best #1, table Default-IP-Routing-Table, RIB-failure(17))
Advertised to update-groups:
2
65200, (received & used)
10.10.34.3 (metric 128) from 10.10.34.3 (3.3.3.3)
Origin IGP, metric 0, localpref 100, valid, internal, synchronized, best
R5_AS65100#

Now we see the routes in R6s routing table as well.

R6_AS65400#sh ip rou
Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2
i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
ia - IS-IS inter area, * - candidate default, U - per-user static route
o - ODR, P - periodic downloaded static route

Gateway of last resort is not set

20.0.0.0/8 is variably subnetted, 5 subnets, 2 masks


B 20.16.0.0/12 [20/0] via 192.168.56.5, 00:11:23
B 20.0.0.0/12 [20/0] via 192.168.56.5, 00:11:23
B 20.0.0.0/8 [20/0] via 192.168.56.5, 01:08:48
B 20.48.0.0/12 [20/0] via 192.168.56.5, 00:11:23
B 20.32.0.0/12 [20/0] via 192.168.56.5, 00:11:23
C 192.168.56.0/24 is directly connected, Serial0/0
40.0.0.0/8 is variably subnetted, 5 subnets, 2 masks
C 40.32.0.0/12 is directly connected, Loopback32
C 40.48.0.0/12 is directly connected, Loopback48

© BTS Communications, LLC 6 01/02/12


BGP RIB Failures and BGP Synchronization

C 40.0.0.0/12 is directly connected, Loopback0


S 40.0.0.0/8 is directly connected, Null0
C 40.16.0.0/12 is directly connected, Loopback16
B 10.0.0.0/8 [20/0] via 192.168.56.5, 00:52:28
30.0.0.0/8 is variably subnetted, 5 subnets, 2 masks
B 30.16.0.0/12 [20/0] via 192.168.56.5, 00:11:24
B 30.0.0.0/12 [20/0] via 192.168.56.5, 00:11:24
B 30.0.0.0/8 [20/0] via 192.168.56.5, 01:08:48
B 30.48.0.0/12 [20/0] via 192.168.56.5, 00:11:24
B 30.32.0.0/12 [20/0] via 192.168.56.5, 00:11:24
R6_AS65400#

Notice we also get the /12 subnet routes for 30.0.0.0/8 network. In addition, you might have noticed
in the lab we have the same problem on R5 with the 40.0.0.0/8 network. I will let you try your hand
at fixing the 40.0.0.0/12, 40.16.0.0/12, 40.32.0.0/12 and 40.48.0.0/12 subnets received on R5 from
R6. Do you see these routes on R3? How about R1? R2? Go ahead give it try!

© BTS Communications, LLC 7 01/02/12