From: Michael Snyder (msnyder@xxxxxxx)
Date: Tue Jul 23 2002 - 01:06:55 GMT-3
I use tags a lot with the redistributions I do. In fact the only place
I don't use them is incoming rip and igrp routes. Anytime I have routes
coming out of rip or igrp I use distribution lists to the same effect.
I don't know why, but having a rip or igrp route donors seems to really
mess up tagging operations, even with protocols that support tagging
like eigrp or ospf.
Anyway, getting back to my question.
I noticed that some protocol operations product tags. When BGP is the
donor, the receiving protocols seem to have tags matching the AS of the
BGP.
I just saw another example tonight. When I did a default-information
originate in ospf, the resulting external route got tagged equal to '1',
which seems is the same as the process ID.
router ospf 1
router-id 0.0.0.2
log-adjacency-changes
redistribute static
default-information originate metric 20 metric-type 1
OSPF Router with ID (0.0.0.2) (Process ID 1)
Type-5 AS External Link States
Link ID ADV Router Age Seq# Checksum Tag
0.0.0.0 0.0.0.2 1144 0x80000004 0x64B6 1
My question is, what's up with this volunteer tagging? Are there any
hard rules on this behavior, or is it a special case by special case
basis?
Any tricks to use this behavior to our advantage, any pitfalls to watch
out for?
Thanks in Advance,
Michael
This archive was generated by hypermail 2.1.4 : Sat Sep 07 2002 - 19:36:39 GMT-3