On Mon, Jul 28, 2008 at 12:08 PM, Scott Silva <ssilva@xxxxxxxxxxxx> wrote: <snip> >>> I usually have to do updates like that on the weekends, as I can't depend >>> on >>> a 3AM reboot to be up in the morning when Exec's are in. A reboot I >>> trust, >>> but not the first one after a kernel change. On a weekend I can drive in >>> and >>> see what happened if necessary and switch to a backup router. >>> In our main office I have 2 running side by side and I can log in to the >>> T1 >>> router and change switch ports to swap them. Then a reboot on the router >>> to >>> hasten the MAC changeover. Usually 5 minutes tops. >> >> Thank you for the explanation! I wondered, if you would trust it, to >> come back up, if you scheduled a reboot for 3 A.M. > > I just had a perfect example this morning. One of the routers didn't come > back up after the upgrades and remote reboot yesterday. I had to have > someone at the site powercycle the equipment. Still much easier than having > to drive over there myself. Good that you are very conservative and do not leave the executives without Internet access! :-) I updated our backup IPCop box yesterday. Our IPCop box and our ADSL modem are choke points. The ADSL modem is the only thing we have that we don't have a backup for. _______________________________________________ CentOS mailing list CentOS@xxxxxxxxxx http://lists.centos.org/mailman/listinfo/centos