From: ccie2be (ccie2be@nyc.rr.com)
Date: Mon Apr 04 2005 - 11:54:48 GMT-3
Hi Jongsoo,
As Eric said, there are a number of reasons to reboot your routers during
the lab.
Here are a few I can recall:
1) Some config changes don't take effect until the next reboot e.g.
changing the system mtu on the 3550's.
2) Getting rid of dynamically mapped 0.0.0.0's when doing f/r config.
3) Making correct config's work when they currently don't. For example,
sometimes a correct config won't work if you did the config in the wrong
order - 1 specific example of this is ppp over ATM but I've seen many
others.
4) Finding problems
5) Clearing out a random IOS problem.
So, there are several very compelling reasons to reboot your routers and
switches during the lab.
That said, given the time it takes for a reboot, rebooting shouldn't be done
willy nilly nor on all routers.
Here's my idea of what would be a good time to reboot.
If, after configuring f/r, you have dynamic maps to 0.0.0.0 which you're not
allowed to have. Just reboot the f/r related routers.
If, after configuring something else and it doesn't work but you're almost
positive you've done the config correct.
After completing the IGP portion of the lab reboot all routers and switches.
If this is just before the lunch break so much the better. If you've
finished the IGP portion of the lab and still have some time left to do
other things, do some other things first but then reboot before going to
lunch.
After you've completed the lab and are about to go back and double check
your work.
Others may have different ideas about this and I would be interested to know
their opinions as well.
HTH, Tim
This archive was generated by hypermail 2.1.4 : Tue May 03 2005 - 07:54:52 GMT-3