From: Chuck Larrieu (chuck@xxxxxxxxxxxxx)
Date: Sat Feb 03 2001 - 17:31:41 GMT-3
Have you ever experienced this one:
Complex scenarios, multiple routing protocols, complex redistribution. You
ping from place to place and you are successful. Or maybe partially
successful ( .!!!. for example )
So you troubleshoot. And in the course of troubleshooting, you do some more
tests, and your tests are successful, or sometime unsuccessful. You check
your configurations, your redistribute statements, your route-maps. Things
appear to be what they should be. Test some more. Failure test some more
from different places. Routes are here but not there.
My long winded way of getting around to a phenomenon I am calling
"artifact" - where something seems to be wrong in a routing table or two as
a result of the long history of changes being made. This is particularly
evident, it seems, in protocols such as OSPF and EIGRP, where only changes
are propagated. Something as simple as a clear ip route * on a particular
router ends the problem.
So my question to the group: how do you deal with "artifact"? For those who
have been through the lab, or through ECP1 or ASET, what is your advice
about this kind of concern? What have your mentors suggested as a practice?
Do you make it a habit to issue "clear ip route * " and "clear ip cache"
after making routing related changes, no matter how minor?
Chuck
63 days and counting
A long shot at passing is better than no shot.
Right now that's all I got to get me through,
So I gotta believe!
( paraphrased from Kathy Baille / Baille and the Boys
a song from several years ago )
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:28:35 GMT-3