[nsp] RIB failure when using backdoor network

[Tim Devries]

I have the same issue, except I am not using an interior routing protocol,
and get RIB failures for a ton of external routes.  I'm only redistributing
a few statics, one to null and the other points to my firewall where the IP
address space resides behind.

So in this case, I don't understand why the failure occures, but it looks
like an IOS upgrade issue with the T train.


> RIB-failure is something new and it came with
>
> CSCdp12004: BGP: Should not advertise if IP rejects BGP route unless nhop
> match
>
> Basically if you have a bgp entry and the same entry learned via IGP, they
> have to be pointing to the same next-hop. Otherwise advertising BGP prefix
> may cause loops.
>
> Ilker
>
> ----- Original Message -----
> From: <Scott.Keoseyan@BroadWing.com>
> To: <cisco-nsp@puck.nether.net>
> Sent: Wednesday, November 13, 2002 2:32 PM
> Subject: [nsp] RIB failure when using backdoor network
>
>
> > I ran into a weird situation and I am hoping someone can shed some light
> > here...
> >
> > I am receiving a default route via eBGP (don't ask).  I also have
> generated
> > a default-route from another router via my IGP, which I prefer.
> >
> > I used the
> >
> > "network 0.0.0.0 mask 0.0.0.0 backdoor"
> >
> > command, to ensure I used the default I prefer.
> >
> > When I did this, I ended up with a RIB Failure in the BGP table.  Is
this
> > normal?
> >
> > router2#sh ip bgp
> > BGP table version is 19286, local router ID is 172.16.0.1
> > Status codes: s suppressed, d damped, h history, * valid, > best, i -
> > internal,
> >               r RIB-failure
> > Origin codes: i - IGP, e - EGP, ? - incomplete
> >
> >    Network          Next Hop            Metric LocPrf Weight Path
> > r> 0.0.0.0          192.168.100.1                  119      0 100 200 i
> >
> > when I remove the command, the route simply drops back to "valid" state,
> > which is what I would expect, but I did not expect to see RIB-Failure
when
> I
> > used the backdoor command since it doesn't appear to be noted anywhere
in
> > the documentation (RIB-Failure as a Status code does not appear to be
> > documented yet in any of the docs I could find... a search on
> "RIB-Failure"
> > produced no meaningful results).
> >
> > I did find a bug (CSCdw84776) that describes a condition when operating
as
> a
> > PE that could cause a RIB failure, but that has little to do with my
> > config...
> >
> > This is a 3660 running 12.2(11)T... and I know... it shouldn't be... :-/
> >
> > thanks,
> >
> > Scott
> >  +++The information transmitted is intended only for the person or
entity
> to
> > which it is addressed and may contain confidential and/or privileged
> > material.  Any review, retransmission, dissemination or other use of, or
> > taking of any action in reliance upon, this information by persons or
> > entities other than the intended recipient is prohibited.   If you
> received
> > this in error, please contact the sender and destroy any copies of this
> > document.+++
> > _______________________________________________
> > cisco-nsp mailing list  real_name)s@puck.nether.net
> > http://puck.nether.net/mailman/listinfo/cisco-nsp
> > archive at http://puck.nether.net/pipermail/cisco-nsp/
> >
>
> _______________________________________________
> cisco-nsp mailing list  real_name)s@puck.nether.net
> http://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/