From: keith tokash (ktokash@hotmail.com)
Date: Tue Jan 29 2008 - 19:16:20 ARST
I would break step #1 into several sub-steps, and add a step #0.
0. Look at the diagram you just drew with all of your IGPs in colors. Look at
the various points of redist. Try and figure out where loops will occur,
either because of redistribution or simple distance problems.
1. Apply redistribution on a single box. Check the route tables on every box
and make sure you see exactly what you thought you would. Don't redistribute
on the second box until the ramifications of box 1 are fully understood or you
end up spending an entire Saturday chasing your tail (or so I've heard ... :(
).
General connectivity may not prove you are doing it right. If you can do a
"debug ip routing" and not see a bunch of changes, then you're probably loop
free, which is a start. But then you have to go back and re-read the whole
IGP section to make sure you didn't just bugger up your EIGRP requirement to
not advertise smaller than a /23 blah blah blah. Also, for completeness you
want to look at your route tables before ANY redist and make sure you like
what you see.
I don't know anyone who was able to breeze through redistribution right away.
They might *now*, but it took one guy I work with (CCIE R&S) two weeks to
fully get his hands around multiple, mutual redistribution. I guess there's a
savant out there for everything though.
With a few exceptions, secrecy is deeply incompatible with democracy and with
science.
--Carl Sagan
> Date: Mon, 28 Jan 2008 22:00:42 +0100
> From: smart4D@free.fr
> To: ccielab@groupstudy.com
> Subject: strategy for redistribution
>
> Hi,
>
> I am trying to find out a good strategy for what is usually the last
> question of the IGP section : REDISTRIBUTION.
>
> Some people may be able to find immediatly and exactly and exhaustively
> where we are going to have troubles with loops etc. etc.. and where
> redistribution should be done with tools preventing these loops
> (route-map, distance etc..) : but this is not my case.
>
> So I came up with this "strategy" :
>
> 1/ do redistribution on all required routers and/ or switches
>
> 2/ write tcl scripts and / or macros
>
> 3/ run tcl / macros and see where pings are not functioning and "repair"
>
> 4/ run them on all routers annd switches until it all works without any
> "repairing"
>
> Well, I agree there must be a "shorter" & more efficient way.
>
> If you have a constructive and rigurous way, it would be appreciated !
>
> thanks,
> Navid
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Fri Feb 01 2008 - 10:38:02 ARST