Regardless of what type of data center you may find yourself having to deal with, there are several things I've learned over the years that will dramatically reduce the pain and frustration you'll have in implementing, maintaining and troubleshooting that data center. So, whether you are one of the lucky ones working for a profitable dot com, or you are in the corporate world supporting hundreds (or thousands) of users, or even if you're responsible for the IT needs of a small organization with only 15 employees, read on! You just may find the cure for your data center blues.

Plan, Plan, Plan: Did I Mention that You Should Plan?
Everybody readily agrees with the notion that one should plan things out before actually implementing. Yet it rarely happens. Take this quick test to see how your data center stacks up:

1. Do you have a documented data center design plan, and does it reflect what's really in your data center?
2. If someone were to disconnect all the cables, how easy would it be for you to properly reconnect everything?
3. Quick, no peeking: How many servers do you have? How many switches? How many electrical circuits?
4. You've just been told the company needs four more servers for research and development. Again, without peeking, do you know where you would put them? Do you have available switch ports for them? Enough electrical capacity?

My data center consultations involve many more questions, but the majority of companies that I've worked with fail at least three of the above.

Neatness Counts!
Often times, I find myself looking at the front of a row of server cabinets, and it looks quite impressive. Server after server mounted securely in the racks, LEDs glowing. But then I walk around to back of the cabinets, and it's a whole different ball game. Cables everywhere. Nothing's labeled. Obvious "temporary" fixes that were never made permanent (like Ethernet cable spanning several cabinets that is so taut you could pluck it like a guitar string).

OK, not all data centers start out as spider web of cables: they get that way as fires are put out. I know that sometimes you have to solve problems as quickly as possible, and that in these situations you may not have the time to do things nice and neatly. That's what maintenance windows and redundant systems are for!

Be Consistent
This is a broad category. It applies to how you route cables and what brand of equipment you use. Here are my suggestions in this area:

• Stick with one manufacturer for network infrastructure. I'm talking the Layer 2 -3 stuff: switches and routers (please don't tell me you still use hubs in your data center!). Ideally, you should use managed devices: One reason I like Cisco so much is I can configure and manage all my devices using the same interface. Other manufacturers also offer this (3Com, Extreme, etc.).
• Use one server manufacturer. This may not be possible, but unless there is a compelling reason to use a different brand, stick with one. Taking this concept a step further, also try to stick with a particular model line. It makes thing a lot easier if all your servers take the same type of hot-pluggable drive or use the same power supply.
• Network cables come in a variety of colors and lengths -- take advantage of the variety. For example, use blue cables for all internal LAN connections, red cables for all Internet connections and green cables for all DMZ connections. As for length, you want cables to be just a bit longer than what is required to reach the server or other device in its fully extended position.
• Design and use a cable routing scheme. I like to route all network cables on the left side of the cabinet, for example, and power and KVM cables on the right.
• Use consistent naming conventions. Lots of debate on this one. Do you use server names like "luke," "darthvader," "hansolo," and "deathstar"? Or do you take the mnemonic approach: "xyzctl01," "xyzsql03," "xyzapp11" (the first domain controller, the third SQL server, and the 11th application server in the xyz domain, respectively)? It's not as exciting, but the mnemonic approach makes managing and troubleshooting much easier.
  

Label, Label, Label
You can pick up one of those battery-operated tape label machines for under a hundred bucks. And an extra fine point Sharpie (perhaps the best tool you can bring to a data center) is just a couple of bucks. Get these tools, and don't be afraid to use them!

Let's start with the tape labeler:

• Every server should have its name, IP address(es) and MAC address(es) clearly labeled on both the front and back.
• If you are using KVM switches (and you better be!) you'll also want to indicate which switch box and port number the server is connected to.
• If there is more than one NIC card on a server, each NIC should be labeled ("Data Center LAN" and "Internet LAN" for example).

Now it's time for the Sharpie:

• Uniquely identify every network cable. I like to use the rack or cabinet identifier combined with a ordinal number. Be sure to label both sides of the cable.
• On the switch side of the cable, also indicate which switch port (and switch) the cable should be connected to.
• Identify all KVM cables-on both ends! One of the most frustrating things is to not know a mouse cable from a keyboard cable, or what KVM switch port they are connected to. And when you label the ends, mark the "top" of the connector. On rounded cables (like the ubiquitous offerings from Belkin), it makes it easy to know which way to hold the cable as you try to connect it to the server.

Tie Wraps Are Cheap!
Buy plenty of nylon tie wraps (also known as zip ties or cable ties) in various sizes and colors. Use them. Use them to keep net work cables routed properly. Use them as strain relief for KVM cables (about three inches from the KVM switch loop the mouse and keyboard cables and tie them to the monitor cable-because the monitor cable is screwed into the KVM switch, it will help prevent the mouse and keyboard cables from being yanked out). Use them to temporarily route cables as needed (remember, these things are cheap!).

Make sure you keep a good pair of diagonal cutting pliers on- hand so you can easily cut ties that are no longer needed. Also be sure to not pull ties too tight: You don't want to pinch or otherwise constrict the cable you are tying up.

Use the Right Tool
We already mentioned the diagonal pliers. Your data center tool box should also contain all the other tools you might need. Here's a list you can start with:

• Screwdrivers -- Spend money on good ones, and get two of each kind (this will avoid the, "Hey, let me see that screwdriver when you're done with it." Syndrome). Don't forget the Torx drivers in addition to the Philips and slotted.
• Flashlights -- It can get pretty dark inside a server cabinet.
• Cordless driver/drill -- Don't buy the 18 volt monster drill! A simple (and light) 7.2 volt Black and Decker or Skil is all you need. But do buy extra battery packs, so you can charge one while using the drill.
• Magnetic retrieval tool -- You know, those telescoping metal thingies with a strong magnet on the end (just be extra careful around disk drives!).

If Your Data Center Is in a Co-Location Facility
There are some extra issues you need to deal with if you are renting rack space from another company. First and foremost, make sure everything is clearly and permanently labeled as being your company's property. You should also include a list of contacts with pager numbers, cell phone numbers and e-mail addresses. Any special instructions should also be clearly posted ("Power up the storage array before powering up Server A and Server B," for example).

Don't Sing the Data Center Blues
These suggestions are certainly not comprehensive. There are myriad other issues that you need to address, and each particular installation presents its own unique issues. Start with what I've outlined here, and you'll be well on your way to data center heaven. And if you get stuck, I'll be happy to help you out -- for a fee, of course!