| Tips on implementing a data center cabling infrastructure |
|
|
|
|
This is the first of a two-part series on data center cabling. Read the second tip on network cable types for your data center. When you walk into most data centers, the first thing admins apologize for is the cabling mess. It should be simple -- just plug in a cable between the server and the network switch. Yet "spaghetti" hangs out of cabinets, blocks the air under raised floors and drapes overhead like tangled snakes. We know how it got this way, but we're not sure why. Is this chaos an inevitable result of ever-changing technology? More importantly, is there any way to do data center cabling correctly? This two-part series addresses three major challenges of deciding on and implementing a data center cabling infrastructure: topology, quantity and cable type. Data center cabling topology Three fundamental methods are used for data center cabling:
Let's eliminate point-to-point cabling right away. That's how data centers have been wired for years, causing messes we still see. Point-to-point means running individual cables or patch cords under the floor, overhead (with or without cable trays) or through the racks and cabinets for every connection needed. Cables are often made on site, or any available patch cord is used. Old cable is rarely removed or labeled, making it very difficult to be traced or even found, resulting in the "rat's nest" familiar to data center workers. Servers and patch panels create enough cable chaos, but when high density network switches are installed in shallow, legacy cabinets, the mess is worse. In short, point-to-point just doesn't work anymore. Considering end-of-row cabling End-of-row consolidation also makes adding new hardware easy; just plug in short patch cords from each server to its cabinet patch panel and then plug short cords into the server access switch in the consolidation rack. Only two short patch cords are needed for each connection, and they're easy to install and find later. Similarly, the access switch is patched to the core network via the fiber cable, so the entire installation involves just simple patching. "End-of-row" consolidation minimizes the number of patch cord lengths that need to be stocked, and makes documentation straightforward since every panel is labeled and easy to trace, particularly if patch cords are color coded. Furthermore, because few cord lengths are needed, there's no excuse for leaving old, long, lower-performance cords lying around. This helps avoid using incompatible patch cords that degrade system performance. Weighing the top-of-cabinet route The alternate approach is used when blade servers include their own chassis switches. In this case, we need only the fiber connectivity back to the core. So the same fiber infrastructure from each cabinet can support either consolidation option. There might even be "hybrid" installations where the entire chassis is still consolidated through the on-board switches, but you still want individual connections from each blade. In short, the common fiber infrastructure can serve any high-speed design. Picking the most appropriate data center cabling method The storage network, which has used fibre channel connectivity for years, has generally been cabled similarly to top-of-cabinet. Fiber runs from cabinet patch panels to matching patches for storage director switches in the storage area network (SAN) area of the data center. But this requires a second complete cabling infrastructure from each cabinet -- not particularly cost-effective. The newest direction is Fibre Channel over Ethernet (FCoE), which enables SAN connections utilizing the same topology and fiber paths as the transport network. FCoE can reduce physical cable quantities, increase bandwidth requirements and consolidate network and SAN management. As FCoE is still emerging, not every manufacturer's equipment is compatible. And, as with the network cable approach, deciding how to cable storage is dependent on the hardware connectivity requirements and other factors. It is likely, however, that FCoE will be supported universally soon. |