Skip navigation
Cisco Learning Home > CCNP R&S Study Group > Discussions
This Question is Not Answered 1 Correct Answer available (4 pts) 1 Helpful Answer available (2 pts)
3733 Views 9 Replies Latest reply: Mar 2, 2011 4:33 PM by YapChinHoong RSS

Currently Being Moderated

RIB-Failure?

Mar 1, 2011 11:07 PM

Walid 34 posts since
Nov 20, 2010

bgp.png

Why some routes apear as rib-failure in the sh ip bgo of SanJose1 and SanJose2??


SanJose1#sh ip bgp

BGP table version is 6, local router ID is 172.16.64.1

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

* i172.16.0.0             172.16.32.1             0         100              0   i

*>                             0.0.0.0                   0                       32768 i

* i192.168.1.0/30       172.16.32.1             0         100              0  200 i

*>                            192.168.1.5             0                             0   200 i

r i192.168.1.4/30       172.16.32.1             0         100              0    200 i

r>                            192.168.1.5             0                             0   200 i

* i192.168.100.0        172.16.32.1             0         100               0 200 i

*>                            192.168.1.5             0                              0 200 i

 

SanJose2#sh ip bgp

BGP table version is 6, local router ID is 172.16.32.1

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

* i172.16.0.0         172.16.64.1              0    100               0 i

*>                         0.0.0.0                    0                 32768 i

r i192.168.1.0/30   172.16.64.1              0    100              0 200 i

r>                        192.168.1.1              0                       0 200 i

* i192.168.1.4/30   172.16.64.1              0    100             0 200 i

*>                        192.168.1.1              0                      0 200 i

* i192.168.100.0    172.16.64.1              0    100             0 200 i

*>                         192.168.1.1             0                      0 200 i

 

 

ISP sh run:

interface Loopback0

ip address 192.168.100.1 255.255.255.0

!

interface Serial0/0

ip address 192.168.1.5 255.255.255.252

clock rate 128000

!

router bgp 200

no synchronization

bgp log-neighbor-changes

network 192.168.1.0 mask 255.255.255.252

network 192.168.1.4 mask 255.255.255.252

network 192.168.100.0

neighbor 192.168.1.2 remote-as 64512

neighbor 192.168.1.6 remote-as 64512

no auto-summary

!

 

SanJose1 sh run:

 

 

 

interface Loopback0

ip address 172.16.64.1 255.255.255.0

!

interface Serial0/0

ip address 192.168.1.6 255.255.255.252

clock rate 2000000

!

interface Serial0/1

ip address 172.16.1.1 255.255.255.0

clock rate 128000

!

router eigrp 64512

network 172.16.0.0

no auto-summary

!

router bgp 64512

no synchronization

bgp log-neighbor-changes

network 172.16.0.0

neighbor 172.16.32.1 remote-as 64512

neighbor 172.16.32.1 update-source Loopback0

neighbor 172.16.32.1 next-hop-self

neighbor 192.168.1.5 remote-as 200

no auto-summary

!

ip route 172.16.0.0 255.255.0.0 Null0

!

 

SanJose2 sh run:

 

interface Loopback0

ip address 172.16.32.1 255.255.255.0

!

interface Serial0/0

ip address 192.168.1.2 255.255.255.252

clock rate 128000

!

interface Serial0/1

ip address 172.16.1.2 255.255.255.0

clock rate 128000

!

router eigrp 64512

network 172.16.0.0

no auto-summary

!

router bgp 64512

no synchronization

bgp log-neighbor-changes

network 172.16.0.0

neighbor 172.16.64.1 remote-as 64512

neighbor 172.16.64.1 update-source Loopback0

neighbor 172.16.64.1 next-hop-self

neighbor 192.168.1.1 remote-as 200

no auto-summary

!

ip route 172.16.0.0 255.255.0.0 Null0

!

  • Brandon Carroll - CCIE (Security) 231 posts since
    Jun 26, 2008
    Currently Being Moderated
    1. Mar 1, 2011 11:43 PM (in response to Walid)
    Re: RIB-Failure?

    A rib failure usually means that the route has entered the routing table via another source.  If you do a show ip route on the SanJose1 router where did the router learn the 192.168.100.0 route?

  • Brandon Carroll - CCIE (Security) 231 posts since
    Jun 26, 2008
    Currently Being Moderated
    2. Mar 1, 2011 11:44 PM (in response to Walid)
    Re: RIB-Failure?

    And just to add to that, the rib failure indicates that some other source had a better administrative distance.

     

    HTH

     

    Brandon

  • Babatunde 43 posts since
    Jul 20, 2008
    Currently Being Moderated
    4. Mar 2, 2011 1:00 AM (in response to Walid)
    Re: RIB-Failure?

    Do a "Sho ip rou "prefix showing as rib"

     

    example on SANJOSE 1:  SanJose1#Sho ip rou 192.168.1.4

     

    this will tell you how the router knows about the prefix.  Then review your route source metric table. connected = 0, static = 1, Eigrp = 90, ext EIgrp = 170 you know the rest of the story.  That will tell you why the result of the command above is prefered.  Assuming you also remember that the router will always prefer lower admin distance except you the adminitrator alter it.

  • sreenivas_naidu 78 posts since
    Sep 29, 2009
    Currently Being Moderated
    5. Mar 2, 2011 1:33 AM (in response to Walid)
    Re: RIB-Failure?

    Walid,

    Try "show ip bgp rib-failure" to identify what is the cause of the rib failure.

    Most  possibly due to to route introduced by another soure having a lower admin distance like Brandon Carroll has suggested.

     

    HTH

  • sreenivas_naidu 78 posts since
    Sep 29, 2009
    Currently Being Moderated
    7. Mar 2, 2011 6:08 AM (in response to Walid)
    Re: RIB-Failure?

    Walid,

     

    Please check the ISP router config,

    The BGP configuration statements:

    router bgp 200
    no synchronization
    bgp log-neighbor-changes

    network 192.168.1.0 mask 255.255.255.252
    network 192.168.1.4 mask 255.255.255.252

    network 192.168.100.0
    neighbor 192.168.1.2 remote-as 64512
    neighbor 192.168.1.6 remote-as 64512
    no auto-summary

    Is there any particular reason you want to advertise these networks into BGP?

    Since they have been advertised into bgp the SanJose1 & SanJose2 receive the route with an AD of 20,additionally since they are directly connected networks to SanJose1 & SanJose2 its already in the routing table with an AD 0, hence you see the rib failure on SanJose1 & SanJose2.

     

    HTH

     

     

    Sreeni

  • YapChinHoong 60 posts since
    Mar 1, 2009
    Currently Being Moderated
    9. Mar 2, 2011 4:33 PM (in response to Walid)
    Re: RIB-Failure?

    You may be interested about suppressing RIB-failure routes as well. Thanks.

    http://www.itcertnotes.com/2011/02/suppressing-inactive-bgp-route.html

Actions

More Like This

  • Retrieving data ...

Bookmarked By (0)