Stewart Stremler wrote:
It's bad enough when the network goes down and you're forced to work
only on your local subnet or machine until it comes back up, but at
least there's still work to do (proof-read comments, if nothing else).
At contract[-3], the network would collapse every day between 2 and 3 pm,
for at least half-an-hour, up to an hour-and-a-half.
Sounds like you either need to:
a) Fire your network admins and get someone competent
b) Find the piece of hardware responsible for this and eliminate/replace it.
A good corporate network should *not* go down unless there's
catastrophic hardware failure in your core -- and that's what 24/7/4hr
service contracts are for. It's safe to 8/5/NBD stuff that isn't mission
critical (like a distribution switch or something), but you should have
a spare anyways.
I just don't understand how anyone can run a network that constantly
goes down. It's like they're running embedded windows on their switches
or something :D
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
