You would need to tag if your routing protocol had no "sense of an external route, learned via redistribution"
The beauty of EIGRP is it knows "external routes" and assigns them an AD of 170, while Internal routes have the AD at 90 (your point to point link).
The tagging is best left for situations where you have...
1. Multiple points of redistribution where the To and From protocols do no treat redistributed route Administrative Distance any differently (think OSPF and RIP)
2. Multiple links per site where optimum routing is not assured and you can EIGRP with tagging with route-maps or offset list functionality to make a decision at each link/router.
So right now I would agree you are setup pretty well. Time to get back to your other studies....
-Joe
-----Original Message-----
From: nobody_at_groupstudy.com [mailto:nobody_at_groupstudy.com] On Behalf Of JB Poplawski
Sent: Tuesday, May 17, 2011 5:26 PM
To: ccielab_at_groupstudy.com
Subject: EIGRP<->BGP Redistro Question.
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:
Received on Tue May 17 2011 - 22:08:12 ART
This archive was generated by hypermail 2.2.0 : Wed Jun 01 2011 - 09:01:11 ART