04-28-2009 07:45 PM - edited 03-04-2019 04:34 AM
Hi, I have router A and B running BGP (5.0.0.0). I have created GRE Tunnel between them working on EIGRP(10.3.1.0).
I have published 10.50.0.0 both in BGP and EIGRP on router A. Now I am seeing EIGRP Tunnel as primary
on Router B. Ideally it should primary as BGP AD-20. Please help.
B>
* 10.50.0.0/16 5.0.0.1 0 65000 65040 i
*> 10.3.1.13 1561600 32768 ?
B>sh ip b 10.50.0.0
BGP routing table entry for 10.50.0.0/16, version 2104
Paths: (2 available, best #2, table Default-IP-Routing-Table)
Not advertised to any peer
65000 65040, (aggregated by 65040 6.0.0.1), (received & used)
5.0.0.1 from 5.0.0.1
Origin IGP, localpref 100, valid, external, atomic-aggregate
Local
10.3.1.13 from 0.0.0.0
Origin incomplete, metric 1561600, localpref 100, weight 32768, valid, sou
rced, best
04-28-2009 08:41 PM
04-29-2009 05:12 AM
Rupesh,
The issue is that you are redistributing EIGRP into BGP on router B. This causes 10.50.0.0/16 to be seen as locally originated on router B (from 0.0.0.0) and to have a weight of 32768, which is preferred over the path received from router A via BGP.
Make sure you do not redistribute EIGRP routes received from router A back to router A via BGP and vice versa.
Regards
04-29-2009 07:46 PM
yes sir. I got the same detail on Cisco site. Thanks for this big help.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide