By now we had an Overview of DataCenter; we learnt about Racks, Cables and its labeling too. We will go in-depth about few concepts for Power, Cooling, and HVAC in future along with learning technologies like Blade Enclosures, Virtualization and SAN Storage. But first, since now you might notices what you have in your datacenter, lets capture it first. Documenting your datacenter is the most important phase in your datacenter deployment. It’s important when it comes to Managing your Datacenter.
I have seen people capturing Server Implementation Plans (SIP), Network Implementation Plans (NIP) and Standard Operation Procedures (SOP) for New Deployments, but where is the mapping of this information to actual physical deployments. You may an inventory available with you where you have your rack location against your server/storage/switch equipment, but can visualize your datacenter with that? In a way that I give you the information in excel sheet, and you are new to your company and something goes wrong; now I need your assistance to walk-in to the datacenter and check if the cables connections are fine for a particular setup; so you think you can do that with your current available information? Imagine the time you would lose in tracking it even though you have labels in your datacenter. You know time=$$$ right!! So I suggest, invest sometime in making it how you visual it so that you don’t have single point of failure in absence of people who deployed it.
I believe you are convinced by now that why you need to create datacenter documentation. So let’s talk about what need to be captured (suggested) in this document and what you need for that.
To Be Captured:
1. Overview: It’s like a summary of your datacenter, how it looks. I prefer to mention who designed the document and who owns the document along with who reviewed and approved the document as important information to be mentioned in the beginning itself. It’s give a level of confidence on the document. Like I mentioned, this shows how it looks don’t jumble the position of equipment, racks and their location within. It should be like a photo as it looks.
2. Power: I believe it’s a good practice to mention the current operating power and max requirement specification based on engineering design. You would need assistance of your local maintenance guyz to measure operating power in peak hours. Suggest you to take max noted in one week or you can take average as well. As per my experience, usually 3 phased power is used in a datacenter. In this example, R-Red, B-Blue and Y-Yellow is named as three phases and its consumption across a rack. You need to notice on the total power available in a circuit and its consumption.
3. Network LAN: Next comes the Network connections, ISL and bandwidth usage presentation. I would suggest to make one more sheet to represent the IP subnet used in individual racks along with number of ports. This comes handy when doing a root cause analysis in case of network break-down.
4. Storage SAN: Storage connections are usually tricky and gets messy if your datacenter goes scalable on-demand without proper planning. It is suggested to give a visualization of how storage connections are made across racks and then a logical presentation of ISL connections. Its comes handy when troubleshooting performance issues.
5. Server Connections: I always to show case a cable connection within a rack and it should be pasted or available as reference material with critical deployments. Imagine you had to remove cable connection for maintenance or replacement of any components and cables get swapped? This is suggested for deployments in a rack.
6. Setup Configuration: This is a brick level logical presentation of your deployments; where you map how your physical infra (Server, Storage, Network and most important Applications) exist in different layers. I have seen this in Server Implementation Plans (SIP) but not sure if everyone provide the detailed information about the deployments every-time like physical rack information, Management IP etc. Sharing some examples below:
7. Contact Information (Disaster Run-Book): This section should always come either first or last, preferred last though. This should mention the on-call IT team members name and contact information along with respective areas of expertise like Windows, VMware, Server, Storage, Network or domain of ownership like Power, Cooling, Space etc. This comes handy and becomes a reference in case of Disaster. You can also mention Vendor support information like Contract IDs, Support Numbers, Account Managers Info etc so that you don’t have to search it everytime.
What You Need:
8. Visio: When it comes to tools, Microsoft Visio is the best one I have seen. You would need stencils to give a real picture of your datacenter. Generic ones should be avoided or should be used only for logical explanations like routing/firewall setups, but what if you need to show actual physical connections? I have seen many usual stencils available on Visio-cafe (ask Google); rest you can ask the vendor for it, they usually provide it as free of cost. Note that there are certain open-source tools available, but they may or may not give the precision to show-case your datacenter. I may be biased, but I am just a fan of Visio.
9. Information: Apart from tools information is most important. It may be available like a document for setups or like an excel sheet for inventory. Make sure you validate the inventory before you actually deploy it. Most important, you need to make sure this information is kept up to date.
10. Owner, Reviewers & Approvers: To make sure you have the proper information and its mapped as is; Get it reviewed from your peers (Important). See if they have any comment or suggestion or doubts before you actually publish it. What’s the use of it, if they don’t understand it. Like I mentioned before, its less technical document but more logical document. Owners are required to keep information up to date and approvers are required so that this can be use a standard reference documents and can be published.
There are couple of tools available which easy your work for making automatic diagram via environment discovery like HP SAN Visibility (free), VMware Maps (free) and some other third party tools. However, you would need to consider the pros and cons that comes with these tools like support limitation, cost, credentials or access requirements etc. Adding to it no tool shows you rack placement.
Any more questions? please write back or comment here. There are more things to share..
P.S.: I understand the example was given using small deployments, but it may look tedious when it comes to bigger deployments. Yes! It will be, if done by one man army J suggested to divide the work with respective areas of expertise or domain to make it easy, which can be later complied together.