From: Kenneth Wygand (KWygand@customonline.com)
Date: Thu May 27 2004 - 12:57:18 GMT-3
Here is one feature I've been waiting to see. The tag value is actually
represented by an integer value. I'd like to be able to _increment_ the
tag value during redistribution instead of only being able to remark it.
Now that would make for some _very_ interesting strategies for complex
redistribution because the protocols the route has already "traversed"
could be basically bit-mapped to a unique binary bit (sort of how the
TOS behavior characteristics are set in the TOS value, or how multiple
precedence values can be mapped through a single decimal representation
of a series of binary "switches".)
"If the '8' bit is turned on, this route has passed through EIGRP"
"If the '4' bit is turned on, this route has passed through OSPF"
"If the '2' bit is turned on, this route has passed through ISIS"
"If the '1' bit is turned on, this route has passed through RIP"
Upon redistribution, you can simply "check" your corresponding bit and
see if the route has ever been in your native routing protocol. If not,
redistribute! If it has, throw it away! It's old info!
Of course this can be done through tons of "match" and "set" clauses,
but the amount of configuration increases exponentially as each
additional routing protocol is added. With the ability to increment the
tag value, this solution scales linearly and would work very efficiently
even when having tons of redistribution points using every routing
protocol available!
If you are still with me, you probably now realize how cool this would
be...
Kenneth E. Wygand
Systems Engineer, Project Services
CISSP #37102, CCNP, CCDP, ACSP, Cisco IPT Design Specialist, MCP, CNA,
Network+, A+
Custom Computer Specialists, Inc.
"The only unattainable goal is the one not attempted."
-Anonymous
This archive was generated by hypermail 2.1.4 : Wed Jun 02 2004 - 11:12:18 GMT-3