From: Long Kwok (lkwok@ccieunix.com)
Date: Sun May 29 2005 - 19:31:24 GMT-3
Thanks Tim ,
This is a good one to know as on lab would shit if see this if not
understanding what it is caused by , I have been playing with it and
concur with your posts... The key to remember is ask yourself is the
router I issue the command show ip bgp , learning this prefix from ibgp
peers or ebgp peers , as when looking throughout your bgp peers , you
will be confused as to why some of them don't have r and other do ...
The neighbors that don't have r failures for the specific prefix are
learning the prefix via ebgp peering , the ones that are failing are
learning if via ibgp peerings so there AD will be the worst of all 200 ,
and hence r
Tia Long
-----Original Message-----
From: ccie2be [mailto:ccie2be@nyc.rr.com]
Sent: Sunday, May 29, 2005 3:11 PM
To: Group Study
Subject: FW: RIB Failure
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
gladston@br.ibm.com
Sent: Tuesday, September 14, 2004 5:21 PM
To: ccielab@groupstudy.com
Subject: Re: RIB Failure
========
... just want to know if they represent some thing "not good" (Fail) to
the
lab procters?
========
It is difficult to know that. The best approach in such situation would
be
ask the proctor.
There were Discussions about this topic (RIB failure) on the recent
past.
As a summary, RIB Failure is normal behavior when IGP and iBGP announces
the
same route. There are other cases where RIB Failure represents a
problem.
I run on this on DOiT scenario. A groupstudy fellow also posted that
there
is a InternetworkExpert scenario where this occurs.
Generally, you do not need to take care of it on the lab, but if that
bothers you, check with the proctor.
This archive was generated by hypermail 2.1.4 : Fri Jun 03 2005 - 10:12:03 GMT-3