What do your people do when the network goes down?

You advoid it in the first place by building in layers of redundancy in your network. Use multilpe providors, physical paths, routing protocols and common sense network design.
 
Definitely try and avoid it, or spend an utter amount of time rolling eyeballs when managers gather around a brainstorm flipchart of what happened, what will be done (excludes spending money), how can we prevent it from happening again (excludes spending money or accusations of not spending money) and what to tell the customer of what really didnt cause it to happen.
 
Normally everyone comes over and asks what happend to the internet... Or about 100 people come over and try and get involved as obviously we need to answer all of their questions instead of being able to fix the problem....
 
Sit back and wait for my boss to fix it seeing as its usually him that breaks it, I might go for a cigarette if I'm feeling adventurous.
 
Not a lot at our office - carry on as normal, the internet isn't integral to what we do. It does make using the MSDN library a pain though - means i have to get up and find the CDs with it on!

The electric on the other hand.... when the electricians want to turn the power off to install a new consumer unit then we're all stood around twiddling our thumbs until it's sorted.

Nothing exciting like chair races though...i must remember to suggest that next time.
 
The internet might not be, but what about your internal network?

Even then it isn't really - the office has a total staff of 5, 4 software engineers - we work on local copies, version managed by SVN plus a hardware engineer / admin.

The network consists of a Cisco switch, draytek router and one server :p

Nice and simple.

Although its quickly going to get complicated what with the new filestore, VOIP system and i want to put in a net install system as we often do system builds for clients.
 
Back
Top Bottom