From: Cary Anderson (caryande@cisco.com)
Date: Wed Jan 15 2003 - 22:08:28 GMT-3
The tool I like best is to turn on "debug ip routing" on your router to see
the routing loops. You can then do things like increase distance, filter,
etc to fix them quickly. I personally rarely filter on redistribution, as
it slows you down a lot. You can usually tell by looking at the topology if
you need to filer or not.
My 2 cents
-----Original Message-----
From: Jennifer Bellucci [mailto:Jennifer_bellucci@hotmail.com]
Sent: Wednesday, January 15, 2003 3:11 PM
To: Vijay S Jayaraman; ccielab@groupstudy.com
Subject: Re: Mutual redistribution
Hi
Everyone has their own way of doing things. The most reliable method I have
found for myself is to permit only the routes you want and don't let
anything be red un-controlled. That way, your ACL are nice and solid with
little time spent on exactly what you need to filter if any.
Try performing red and speed up the protocol lifetime - hello, keep, spf,
lsa, stuff like that. See what happens and you can see routing loops better
while using traceroute to do a nice check, you will find that sometimes you
can ping the address but the tracroute goes on till 32 or something.
Just a thought.
Jbell
----- Original Message -----
From: "Vijay S Jayaraman" <vjayaram@in.ibm.com>
To: <ccielab@groupstudy.com>
Sent: Wednesday, January 15, 2003 9:33 AM
Subject: Mutual redistribution
> Hi,
> In case I am doing a mutual redistribution at a single point between
> any two routing protocols , do I really ever need to filter the routes
> that
are
> being redistributed for prevention of a loop.....????????
>
> I have never done this and have had no problems till now..... But
> wouldnt want to discover something new during my lab.....
>
> But is there any case where filtering is required in for such a
> redistribution?....what is the normal thing to do??
>
>
> Regards,
> Vijay.
> .
.
This archive was generated by hypermail 2.1.4 : Sat Feb 01 2003 - 07:33:50 GMT-3