RE: Rib-Failure

From: Brian McGahan (brian@cyscoexpert.com)
Date: Wed Oct 30 2002 - 14:06:48 GMT-3


Hedi,

        This is due to some discrepancies in the next-hop values of BGP
and IGP routes. Here is the bug ID that explains it.

CSCdx26714 Bug Details
   
 
Headline Rib-Failure,if BGP has the same NH as the IGP

First Found-in Version 12.2(8.5)T
First Fixed-in Version 12.2(10.7)T01, 12.2(10.8)PI05

1. Symptom :

  If the prefix get Rib-Failure when installing into bgp table because
of there is already has a prefix in the routing table with a prefered
admin distance (like already learnd by ospf), then this prefix should
not be advertised to other bgp peers unless the next-hop is the same as
the prefix
in the ip routing table. But the behavior is that even if the next-hop
is the same, this prefix still does not advertise to it's bgp peers.

2. Conditions :

  You should see the bgp prefix get a "Rib-Failure" in the output of
"show ip bgp <x.x.x.x> ". This will confirm that this prefix fails to
install into the routing table. Then check the next-hop for the bgp
prefix and the prefix that already in the ip table (it's ospf in this
ddts).
If they are the same, then bgp should still advertise this prfix to it's
bgp peers.
    
3. Workaround :
   
   Thers is not workaround for this problem.

HTH

Brian McGahan, CCIE #8593
Director of Design and Implementation
brian@cyscoexpert.com

CyscoExpert Corporation
Internetwork Consulting & Training
Voice: 847.674.3392
Fax: 847.674.2625

> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf
Of
> Hedi Abdelkafi
> Sent: Wednesday, October 30, 2002 10:25 AM
> To: ccielab@groupstudy.com
> Subject: Rib-Failure
>
> Hi,
>
> I'm practising on CCIE Lab "the Unnamed Lab" of Solie.
> I have a problem on synchronization on R6.
> All the bgp routes are marked as "r" in the BGP table.
>
> Can you tell me what does it mean ?
> Were can I find a document which explains how to solve this problem ?
>
> Thanks for your help.



This archive was generated by hypermail 2.1.4 : Tue Nov 05 2002 - 08:35:59 GMT-3