Define these routers to production routers...
IS R3 and R4 your "edge routers"?
Where is the point to point link connected?
Are you free for a web meeting at some maintenance window?
Mine don't have fail to and fail back issues?
Thanks,
Joe
----- Original Message -----
From: JB Poplawski [mailto:jb.poplawski_at_gmail.com]
Sent: Tuesday, May 17, 2011 06:45 PM
To: Joseph L. Brunner
Cc: renorider_at_gmail.com <renorider_at_gmail.com>; ccielab_at_groupstudy.com <ccielab_at_groupstudy.com>
Subject: Re: EIGRP<->BGP Redistro Question.
I usually wait a few minutes, however from what I recall it doesn't
ever seem to "fail back".
This is in GNS3.
Basically I have
R1
/ \
R3 R4
| |
R6 ---R7
I'd like this be highly available and automatic. Seems like a pipe
dream. R7 access R6 for local and static routes and vice-versa for
R6. It breaks though (on R3 and R4). The two core routers see things
fine, although the edge still wants to use MPLS.
If I crank EIGRP 10 15 (Less than BGP's 20) whichever BGP process
comes up first "wins" and both sites use that route for transit.
I tried backdoor statements, but then it doesn't advertise those
networks and make them available.
JB
On Tue, May 17, 2011 at 5:38 PM, Joseph L. Brunner
<joe_at_affirmedsystems.com> wrote:
> How long have you waited for it to "fail back" on its own with clearing anything?
>
> During the fail back process, try soft clear in and see if they are coming from the provider mpls bgp session...
>
> Joe
>
>
>
> ----- Original Message -----
> From: JB Poplawski [mailto:jb.poplawski_at_gmail.com]
> Sent: Tuesday, May 17, 2011 06:35 PM
> To: marc edwards <renorider_at_gmail.com>; Joseph L. Brunner
> Cc: ccielab_at_groupstudy.com <ccielab_at_groupstudy.com>
> Subject: Re: EIGRP<->BGP Redistro Question.
>
> Good Call, the Site B router is configured as:
>
> router eigrp 100
> redistribute bgp 65000 metric 1500 10 255 1 1500 route-map settag
> network 4.7.7.4 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 blocktag3
> neighbor 1.4.4.1 remote-as 4323
> neighbor 1.4.4.1 fall-over
> neighbor 1.4.4.1 fall-over bfd
> neighbor 1.4.4.1 allowas-in
> no auto-summary
> !
> route-map settag permit 10
> set tag 4
> !
> route-map settag permit 20
> !
> route-map blocktag3 deny 10
> match tag 3
> !
> route-map blocktag3 permit 20
>
> The problem I run into is that my BGP router learns of the external
> routes via EIGRP at first, those external routes disappear with the
> link dying, and they come back but the router "hangs on to" the bgp
> route. I have to either clear the process or clear the specific route
> to get it to fail back properly.
>
> Anything else you can think of?
> JB
>
> On Tue, May 17, 2011 at 5:19 PM, marc edwards <renorider_at_gmail.com> wrote:
>> 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 - 23:07:10 ART
This archive was generated by hypermail 2.2.0 : Wed Jun 01 2011 - 09:01:11 ART