From: Silvio Nunes (silvio_98@hotmail.com)
Date: Tue Nov 18 2003 - 19:39:52 GMT-3
Hi Michael,
Consider the following situation:
|
|
|.........(EIGRP-AS1) R2
(OSPF).......|
R4 (RIP)...... R7(EIGRP-AS1).......|
|
|
|..............(OSPF) R1
|........(EIGRP-AS1) R3
(OSPF) ...... |
|
|
I configured this topology with your template, but is not working properly
for this situation:
In this case, R2 and R3 get the route advertised from RIP as next-hop R1,
this is because these routes have administrative distance 170 and OSPF 110.
With your strategy, is there another way without modify OSPF Admin Distance
or with distribute-list ?
I configured route-maps on R2 and R3, with TAGs for EIGRP and OSPF.
Regards,
>From: "Michael Snyder" <msnyder@revolutioncomputer.com>
>Reply-To: "Michael Snyder" <msnyder@revolutioncomputer.com>
>To: <ccielab@groupstudy.com>
>CC: "'Daniel Sheedy'" <dansheedy@gmx.net>
>Subject: RE: Tags and Redistributing
>Date: Tue, 18 Nov 2003 09:53:53 -0600
>
>Been doing this awhile.
>
>
>This the template I use. The first statement blocks what I don't want.
>The second statement sets everything that was allowed in to a new tag
>value, for later use.
>
>--------------------------------------------------
>
>route-map into_core deny 5
> match tag 222
>!
>route-map into_core permit 10
> set tag 111
>
>--------------------------------------------------
>
>
>route-map into_core deny 5
> match tag 111
>!
>route-map away_from_core permit 10
> set tag 222
>
>--------------------------------------------------
>
>
>Two way tagging away from core isn't always necessary away from the core
>igp, but tagging into the core is necessary.
>
>Use different tags for different igp's, for example.
>
>R1 - rip to ospf tags 111 & 222
>
>R5 - eigrp to ospf tags 333 & 444
>R6 - eigrp to ospf tags 333 & 444
>
>Note I used the same tags, because it was the same eigrp as touching the
>ospf igp
>
>R8 - isis to ospf tag 555 (into ospf)
>
>(note) I only tagged incoming isis2ospf because isis doesn't seem to
>like tags. On the other hand, I can block 555 from going back into
>isis.
>
>
>In summary, now ospf has tags 111, 333, 555 in the core igp, and is
>blocking the 111 tag from going into rip, the 333 tag into either eigrp,
>and the 555 tag from going into isis. Any value not blocked, is set to
>a new tag on the other side.
>
>For example
>
>Anything that makes it into rip is tagged 222, and into eigrp 444.
>
>Which is also blocked from going back into ospf at the respectful
>routers.
>
>
>
>
>
>
>
>
>!
>
>-----Original Message-----
>From: Daniel Sheedy [mailto:dansheedy@gmx.net]
>Sent: Tuesday, November 18, 2003 7:35 AM
>To: ccielab@groupstudy.com
>Subject: Tags and Redistributing
>
>Hi Guys,
>
>I've been doing some research into Tags and Redistribution. I am using
>them
>to prevent routing loops, and have a little question in regards this.
>If i
>do a 'match tag X' while redistributing, do I need to also do a 'set tag
>X'
>or does the tag stay with the route through the redistributions?
>
>Thanks
>
>Daniel Sheedy
>
>_______________________________________________________________________
>Please help support GroupStudy by purchasing your study materials from:
>http://shop.groupstudy.com
>
>Subscription information may be found at:
>http://www.groupstudy.com/list/CCIELab.html
>
>_______________________________________________________________________
>Please help support GroupStudy by purchasing your study materials from:
>http://shop.groupstudy.com
>
>Subscription information may be found at:
>http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Fri Dec 12 2003 - 12:29:14 GMT-3