From: shiran guez (shiranp3@gmail.com)
Date: Wed Sep 26 2007 - 17:51:18 ART
BGP is not a regular Routing Protocol and it is not used to make IGP routing
decisions.
when you enable BGP peering it is not enabling any network advertisements,
only network statement or redistribution will announce advertisements, also
the routing table is build from the longest prefix match.
mean that if you have a BGP route to 192.168.0.0 and you have a RIP route to
192.168.1.0 then the RIP route will overtake the BGP
Routing Desion is based on:
1) Longest Match
2) Admin Distance
3) Connected
4) IGP
5) EGP
6) Floating Static
So as you can see the EGP is almost the last resort in the decision making
process.
On 9/26/07, Gregory Gombas <ggombas@gmail.com> wrote:
>
> I'm seeing the following quirk in a production network:
>
> BGP-->
> RIP-->
> RTRA----------RTRB
>
> Router A is directly connected to router B and is sending the same
> routes via RIP and eBGP.
> Router B is also redistributing the RIP routes into BGP (but filtered
> from sending back to A)
>
> When you look at the route table on RouterB, it shows the routes as RIP
> routes!
> You would think the eBGP learned routes would be preferred because of
> lower AD.
> But when I look at BGP table it shows the route originated locally and
> thus preferred over eBGP learned route.
> When I clear ip route the route is then shown as a eBGP route in the
> routing table and BGP route table does not show the locally originated
> route!
>
> Just wondering if anyone else has seen this...
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
-- Shiran Guez MCSE CCNP NCE1 http://cciep3.blogspot.com
This archive was generated by hypermail 2.1.4 : Sat Oct 06 2007 - 12:01:16 ART