From: Timothy Ouellette (timoue@xxxxxxxxx)
Date: Fri Feb 22 2002 - 06:58:27 GMT-3
Team,
Was working on BGP backdoor on routerb. Routera is advertising the
3.3.3.0/24 via eigrp 23 to routerb (the _____ representing Ethernet).
Routera is also advertising that same prefix via ebgp to routerb (the
=== marks represent the serial link). No biggie, so I threw the
network 3.3.3.0 mask 255.255.255.0 backdoor) command on routerb and
Voila, routerb decided to use the route learned via eigrp (ad=90)
rather than the route learned via ebgp (ad=20).
___Eigrp 23___
| |
3.3.3.0/24---routera======routerb
(ebgp)
I then decided I was going to play around with redistribution. So I
made routea stop advertising that 3.3.3.0/24 prefix to routerb via
ebgp. No problem, routerb still knew about 3.3.3.0/24 via its
Ethernet. I went into the bgp 2 process on routerb and did a
redistribute eigrp 23. After about 90 seconds, I didnt see the
3.3.3.0/24 route in routerbs bgp table. I though what the and looked
for any typos (considering Ive been studying for 11 hours so far) but
didnt see any. I did however see that I forgot to take out the
backdoor statement from the previous exercise. I took that out and
about 15 seconds later I got this message (after turning on debugging of
course)
BGP(0): nettable_walker 3.3.3.0/24 route sourced locally
So I took a look in the bgp table and saw
r2#sh ip bgp
BGP table version is 16, local router ID is 22.22.4.1
Status codes: s suppressed, d damped, h history, * valid, > best, i -
internal
Origin codes: i - IGP, e - EGP, ? - incomplete
Network Next Hop Metric LocPrf Weight Path
*> 3.3.3.0/24 25.25.25.3 409600 32768 ?
My question is, is this a bug that if you have that backdoor in there,
BGP will not redistribute? The only thing I changed in my config was
that line and then it worked.
While I study, Im compiling a list of gotchas I need to remember for
BGP. Anyone else done this, maybe we can compare notes?
Thanks team!
Tim
This archive was generated by hypermail 2.1.4 : Thu Jun 20 2002 - 13:46:30 GMT-3