Re: EIGRP<->BGP Redistro Question.

From: marc edwards <renorider_at_gmail.com>
Date: Tue, 17 May 2011 15:19:00 -0700

Your eigrp statement at both sites is specifying only 3.6.6.3 as
interface 0.0.0.0 is exact match. Are both sites interfaces set with
3.6.6.3? Let us know.

Thanks,

Marc Edwards - DCNISS
http://reno-ccie.blogspot.com

On Tue, May 17, 2011 at 2:25 PM, JB Poplawski <jb.poplawski_at_gmail.com> wrote:
> Good afternoon,
>
> I'm attempting to implement a solution and am labbing it up on GNS3.
> Hopefully someone has some insight, I've chased my tail for awhile
> here.
>
> I have two sites connected via BGP to an MPLS cloud. Each site has
> static routes that the other site needs access to. Everything works
> great now. I'm getting a point to point between the two and I'm going
> to run into a problem. My static routes are EIGRP External and my BGP
> routes getting redistro-ed into EIGRP as external as well. On initial
> bootup everything works well. Each site goes through their respective
> BGP -> MPLS cloud for remote access to the other sites. For the local
> networks it goes across the point to point link. If I kill that point
> to point, everything fails over to local BGP router. Site A goes
> through MPLS to Site B. If I bring that point to point back. All of
> the internal routes get re-learned via EIGRP and work like a champ.
> All of the external static routes will continue to go through the
> local BGP router and not over the Point to Point.
>
> My configs are here:
> ____________________________________________________________
> Site A
> router eigrp 100
> redistribute bgp 65000 metric 1500 10 255 1 1500 route-map settag
> network 3.6.6.3 0.0.0.0
> distance eigrp 10 20
> no auto-summary
> !
> router bgp 65000
> no synchronization
> bgp log-neighbor-changes
> redistribute eigrp 100 route-map blocktag4
> neighbor 1.3.3.1 remote-as 4323
> neighbor 1.3.3.1 fall-over
> neighbor 1.3.3.1 fall-over bfd
> neighbor 1.3.3.1 allowas-in
> no auto-summary
> !
> route-map settag permit 10
> set tag 3
> !
> route-map settag permit 20
> !
> route-map blocktag4 deny 10
> match tag 4
> !
> route-map blocktag4 permit 20
> ____________________________________________________________
> Site B
> router eigrp 100
> redistribute bgp 65000 metric 1500 10 255 1 1500 route-map settag
> network 3.6.6.3 0.0.0.0
> distance eigrp 10 20
> no auto-summary
> !
> router bgp 65000
> no synchronization
> bgp log-neighbor-changes
> redistribute eigrp 100 route-map blocktag4
> neighbor 1.3.3.1 remote-as 4323
> neighbor 1.3.3.1 fall-over
> neighbor 1.3.3.1 fall-over bfd
> neighbor 1.3.3.1 allowas-in
> no auto-summary
> !
> route-map settag permit 10
> set tag 3
> !
> route-map settag permit 20
> !
> route-map blocktag4 deny 10
> match tag 4
> !
> route-map blocktag4 permit 20
>
>
> I'm thinking I need to tag the routes when I intro them to EIGRP, but
> not really sure what that gets me. Any advice or direction would be
> great. I was thinking about EEM or something, but wasn't sure where
> to even begin with that. It seems easy enough, One EIGRP with two BGP
> exit points, but I keep chasing my tail.
>
> Any help/pointers are appreciated,
> JB
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html

Blogs and organic groups at http://www.ccie.net
Received on Tue May 17 2011 - 15:19:00 ART

This archive was generated by hypermail 2.2.0 : Wed Jun 01 2011 - 09:01:11 ART