But, says Yazz, "Since the Cisco was rebooted there were no logs to look at."
You fell into the classic "Windows" trap.. this is what I tell the Jr. tech guys here when one of the servers goes wonky: "If it doesn't work, there is a reason; something is wrong. Rebooting will not fix the problem."
WTF!
Any halfway decent Network Ops (of which I'm in charge of one) have syslog servers for all their stuff. Often one uses som sort of smart agent checking thoses logs, like CiscoWorks or DFM. (Or handwritten in Perl, like for our firewall logs.)
BTW, 6509:s are pretty good stuff, we have a few here at The Big Hospital. And believe me, you don't wan't any network downtime here...can you say "dead people are cool"?
"We live in the lovely quiet and dark."
- John Varley
Slashdot Mirror
But, says Yazz, "Since the Cisco was rebooted there were no logs to look at."
You fell into the classic "Windows" trap.. this is what I tell the Jr. tech guys here when one of the servers goes wonky: "If it doesn't work, there is a reason; something is wrong. Rebooting will not fix the problem."
WTF!
Any halfway decent Network Ops (of which I'm in charge of one) have syslog servers for all their stuff. Often one uses som sort of smart agent checking thoses logs, like CiscoWorks or DFM. (Or handwritten in Perl, like for our firewall logs.)
BTW, 6509:s are pretty good stuff, we have a few here at The Big Hospital. And believe me, you don't wan't any network downtime here...can you say "dead people are cool"?
"We live in the lovely quiet and dark." - John Varley