A network nightmare can happen to anyone at any time, but there are ways to minimize the impact or avoid the nightmare all together.
The best way to avoid such catastrophes is to be as proactive as possible when designing and maintaining your network. Being prepared for the worst can save you when the worst does eventually happen.
So what are some of the ways to avoid network nightmares? Let’s explore.
Don’t you hate walking into a new job where the last IT guy quit and didn’t have anything written down? You’re possibly inheriting a rat’s nest or a hodge-podge of random equipment! Now you have to figure it all out from the ground up.
What if you are the only IT admin in your company and all of a sudden have a heart attack? You need to ensure that another admin can come in and fill your shoes while you are out.
So what types of things should you document?
I’ve seen some messy server rooms over the years, and that’s the one room you don’t want to keep unorganized.
Keeping things organized helps with troubleshooting network issues, working quicker and more efficiently, and can help with using your space more efficiently. If you have cables running all over the place and equipment mounted in odd locations or hanging by the ethernet cable, it’s time to get organized.
One way to get confused or make your life miserable at work is to use any random piece of equipment that you can find. Sure it only costs 20 bucks but there’s probably a reason why it’s so cheap!
Try to get equipment from the same manufacturer to help with warranty tracking and troubleshooting. Plus you might run into compatibility issues using different equipment manufacturers.
Can you imagine trying to keep all of the warranty information straight if every single computer in your organization is made by a different manufacturer? What a nightmare!
Have you ever heard the phrase “If you’re going to do something, do it the right first time’”? How about a major upgrade to the network?
Don’t hodgepodge something together at the last minute just because the boss wants you to get it done. Make sure you plan it out and do it right the first time. No one wants to redo their work, so why put yourself through that?
If you have a major upgrade coming up, think about the other opportunities you might have to upgrade another piece of equipment and save yourself some time in the future.
If you’re getting rack mounted servers but currently don’t have a rack, purchase a rack at the same time and save yourself from having to mount them later down the road. I know it sounds silly but I’ve actually seen people purchase rack mounted servers without having a rack and they end up lying on the floor until they purchase the rack.
Another example would be to rewire some of the equipment in your server room during your major upgrade to accommodate the new equipment.
Maintenance is a crucial part of keeping your network going strong. Here are a few tips on how to do things right:
All of the little things count when you have a large network to take care of. Finding issues before they become catastrophic can be a life saver. If you let all of the little things go for too long, you might not be able to recover.
I like to have confidence that I can recover the network if needed, but if the small issues go unmonitored, confidence will drop drastically and recovery can be very painstaking.
There are plenty of network nightmares out there to watch out for, but being proactive in your approach can and will save you in the long run.
Bad things are eventually going to happen so being prepared and having confidence in your work can give you piece of mind and relieve the stresses of working in the IT field.
What other ways would you suggest to avoid a network nightmare?
Copyright © Train Signal Inc. All Rights Reserved.
Tyler Says:
February 8th, 2009 at 12:08 pm
“Clarify. Simplify. Implement.
Working through a wide range of projects, our IT team has settled into a consistent project methodology: Clarify, Simplify, Implement.
Clarify: Work with key stakeholders to understand drivers behind the process. Question motives and key assumptions. Turn over all the rocks to see what lies underneath. (In traditional software terms, this is requirements gathering.)
Simplify: Relentlessly question, review and challenge the processes and solution being developed. Drive for consistency. Search for well-known models or applications you can copy. Don’t be afraid to change basic assumptions, where simplicity can be enhanced. Always challenge the value of edge cases and try to eradicate them. Work hard to remove every single process, click, page view, icon, etc until you have something so simple that it feels right to everyone involved. (This is the primary value adding activity for IT.)
Implement: After the requirements are clear, and the solution distilled to its simplest form, start implementing. Do not start with a preconceived solution. Continue to loop through clarify and simplify while performing the implementation. (Use your preferred development methodology, provided it supports constant change and rapid prototyping.)
”
http://www.e-gineer.com/v2/blog/2008/02/clarify-simplify-implement.htm
http://blogs.technet.com/mattmcspirit/archive/2008/11/13/licensing-windows-server-in-a-virtual-environment.aspx
http://www.howtoforge.com/vmware_converter_windows_linux
Clayton Cothren Says:
February 9th, 2009 at 8:45 am
I want to thank you for taking the time to write your article. It put it all into perspective and will give my guys a real ability to prioritize their systems as well as their daily routine t prevent such a disaster. As I have learned from a “Bull Rider” friend of mine; “It’s not IF you get hurt, it’s WHEN and how bad”, so I know systems will fail but being prepared sure makes it easier to get back on your feet. I can use your article and really aid my guys in getting their systems into check as well as their performance on the job by making sure check lists are being used and are fully accounted for before a system fails.
Eric English Says:
February 9th, 2009 at 12:18 pm
Thank you for taking the time to read my article. Tyler has a great alternate strategy for avoiding network nightmares that is very concise and to the point. Thanks Clayton for sharing my article with your co-workers to aid them in getting prioritized and on track to recover if the worst happens.
Thanks again,
Eric English
Tyler Says:
February 9th, 2009 at 2:28 pm
“Clarify. Simplify. Implement” I think works well with the suggestions in your article if you include virtualization and storage area networks and live migration you can have people work while resolving any issues. it does mean extra hardware but mission critical it can stay up.
http://www.microsoft.com/downloads/details.aspx?familyid=E464E255-CDD5-44B2-84E6-3233EAE3F356&displaylang=en
http://home.xtravirt.com/
http://vmware.com/products/srm/
http://vmware.com/products/vi/
http://vmware.com/products/vi/vc/ha.html
part of my personal backup and test strategy does involve p2v backups.
Tyler Says:
February 10th, 2009 at 4:10 pm
Live Migration – Part 1
http://edge.technet.com/Media/Live-Migration-Part-1/