[afnog] afnog Digest, Vol 51, Issue 26

Global One Solution malabow at gmail.com
Tue Jun 24 17:48:38 UTC 2008


Frank,

What ever your BGP table should be on your Routing table,  Can you please
send me or the group show ip bgp x.x.x.x and show ip route x.x.x.x so we can
compare. just to understand your set up.

You are running IBGP  let's say

CE1--uknown----PE1-----IX(IBGP)-----PE2

PE1 is sending let's say 172.12.1.0/24 and let's assume CE1 is the
originator.
CE1<>PE1 protocol is static (this is just assumption)
PE1 redistrubite 172.12.1.0/24 or announces via network statement
PE2 receives the route,
PE2 installs it's Local-RIB, which is seen in the BGP table. PE2 is learning
172.12.1.0/24 from PE1 ONLY. so there is no RIB failure.

Also I think you meant to say the RIB is not on the table but the BGP RIB is
there, because FIB is CEF, so make sure you have CEF enable.

Refreshment for BGP decision process:

1) Adj-RIB-in: Stores unprocessed routing information that has been learned
from updates received from peers. The routes contained in Adj-RIB-in.
2) Loc-RIB:  Contains the routes that the BGP speaker has selected by
applying its local routing policies to the routes contained in Adj-RIBs-In.
3) Adj-RIBs-Out: Contains the routes that the BGP speaker advertises to its
peers.


Buzz me offline, i can set up a quick lab and test your set up.

Here is something you can do to see where it's failing:

a) create a ACL for 172.12.1.0/24
b) debug ip routing <ACL>
c) clear ip route 172.12.1.0

This should tell you more why the route is not on RIB table

Please also provide us the IOS version and the platform.


Thanks,



On Tue, Jun 24, 2008 at 8:00 AM, <afnog-request at afnog.org> wrote:

> Send afnog mailing list submissions to
>        afnog at afnog.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>        http://afnog.org/mailman/listinfo/afnog
> or, via email, send a message with subject or body 'help' to
>        afnog-request at afnog.org
>
> You can reach the person managing the list at
>        afnog-owner at afnog.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of afnog digest..."
>
>
> Today's Topics:
>
>   1.  route in rib, not in fib - why? (Frank Habicht)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Tue, 24 Jun 2008 17:44:40 +0800
> From: Frank Habicht <geier-lists-afnog at tih.co.tz>
> Subject: [afnog] route in rib, not in fib - why?
> To: afnog at afnog.org
> Message-ID: <4860C208.4040904 at tih.co.tz>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> Hi all,
>
> new peer at our IX has this prob:
> at border router to uplink, they get the ~60 routes from iBGP from their
> other router (at IXP place) correctly.
>
> "show ip bgp" shows them (sorry for old syntax - dont have their "show
> version " (yet)).
>
> but (!):
>  "show ip route" does only show the 4 connected and static routes
> :-(
> What could be wrong?
>
> and that (show ip route) is also how the packets behave.
>
> I hope the subject summarises correctly.
>
> Sorry to be very vendor C specific ;-)
> let me know if you need more info.
> (but the box isnt under my control)
>
> Frank
>
> snippets from config:
>
> version 12.4
>
> interface FastEthernet0/1
>  description ...............
>  bandwidth 512
>  ip address 192.168.x.161 255.255.255.252 secondary
>  ip address n.n.n.n m.m.m.m
>  duplex auto
>  speed auto
> !
> router bgp <priv-ASN>
>  no synchronization
>  no bgp log-neighbor-changes
>  network s.o.m.e mask n.e.t.224
>  neighbor 192.168.x.162 remote-as <priv-ASN>
>  neighbor 192.168.x.162 soft-reconfiguration inbound
>  no auto-summary
> !
> ip classless
> ip route ................
>
>
>
> ------------------------------
>
> _______________________________________________
> afnog mailing list
>
> End of afnog Digest, Vol 51, Issue 26
> *************************************
>



-- 
Liban Mohamed
Global One Solution
www.globalonesolutions.net
malabow at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://afnog.org/pipermail/afnog/attachments/20080624/75b1dd66/attachment-0002.html>


More information about the afnog mailing list