| Data centre infrastructure design cabling distances and space planning |
| Monday, 24 September 2007 11:19 | |||
|
Siemon looks at how cabling can affect data centre design
When designing and laying out a data centre, understanding best practices as well the pros and cons for each type of data centre is critical. The TIA 942 data centre guidelines are very specific that horizontal and vertical cabling should be run accommodating growth, so that these areas do not have to be revisited. It is also specific about equipment not being directly connected unless it is specifically required by the manufacturer. This is also inline with other standards documents that such as ANSI/TIA/EIA 568-B that design for opens systems architecture. So the question is raised: what is the best way to do this for a 10Gb/s environment? All copper channels are based on a worst case, 100 meter, 4 connector model. ISO/IEC 24764 (draft), TIA-942, ISO/IEC 11801 Ed2.0 and recommendations from electronics manufacturers suggest that any fixed portion of the channel be a minimum of 15 m (50 ft.) in these models. While some shorter lengths may be supported in other portions of the channels, there is a requirement in zone distribution and consolidation points for this minimum distance. When moving to 10Gb/s electronics, the 15m minimum will likely exist for all horizontal cables due to recommendations from electronics manufacturers. The 15m length is also dictated by signal strength issues, as your signal is strongest in those first 15m which can create issues with two connectors in close proximity. By providing at least 15m to the first connection point in the channel, you are allowing the attenuation to reduce the signal strength at the receiver or between components. In order to achieve the 15 m distance, two options exist: either provide space in the pathway to take up the distance or create service loops under the floor. Service loops should not be a loop, but rather a loosely configured figure 8. Bear in mind that the additional cable will consume more pathway space. Copper distances for Augmented category 6A twisted pair cabling are limited to 100m for all channels with the exception of 10GBASE-T running on category 6/class E cabling. This distance for these channels will be limited to roughly 55 m depending upon the scope of potential mitigation practices to control alien crosstalk. It should be noted that the purpose of TSB 155 is to provide parameters for the qualification of existing Cat 6/Class E applications for use of 10GbaseT, TSB 155 should not be used for designing new installations Fibre channel lengths vary based on the grade and type of fibre, type of interface. Understanding these limitations will assist in the design and layout of the data centre space. If you are utilizing 10GBASE-CX4 or Infiniband, you are distance limited to a maximum of 15m. The following chart summarizes the distances for all 10G applications and their associated cabling systems. The MDA (Main Distribution Area) is considered the core of the data centre, connectivity will be needed to support the HDA (Horizontal Distribution Area). Following TIA-942 recommendations and utilizing EDA’s (Equipment Distribution Areas) and ZDA’s (Zone Distribution Areas) we would like to present four design options for consideration. Option One is to run all fibres and copper from the core to a distribution area (which is similarly situated), to the fibre from the horizontal distribution areas serving the Equipment Distribution Areas. This provides a central area for patching all channels. Another advantage is that all ports purchased for active gear can be utilized. With the ability to use VLANs, networks can be segmented as needed. In other scenarios, entire blades are likely dedicated to a cabinet of servers. However, if there are insufficient server NICs to utilize all ports, then the idle port become a costly inefficient. For instance, if a 48 port blade was dedicated to a cabinet at location XY12, but there were only 6 servers with two connections each, then 36 ports were paid for and maintenance is being paid on those ports to remain idle. By utilizing a central patching field, the additional 36 ports can be used as needed elsewhere in the network thereby lowering equipment and maintenance costs. Option Two is to place patch panels in server cabinets that correspond directly to their counterparts in the switch cabinets. In this scenario, switch blades/ports will be dedicated to server cabinets. This may be easier from a networking perspective, but may not provide the best usage of all ports in the active electronics. Extra ports can be used as spares or simply for future growth. However, if an enterprise is planning to implement blade technology where server density may decrease per cabinet, this may not be a cost effective option. For the switch cabinets, the type of copper cabling chosen will be a significant factor due to the increased UTP cable diameters required to support 10GBASE_T. In reality, cabinets and cabling (both copper and fibre) are changed far less frequently than the active electronics. But with the new category 6A UTP cable‘s maximum diameter of .354 inches (9.1mm), pathways within the cabinets may not provide enough room to route cable and still provide the stability necessary. It is always recommended that percent fill calculations be addressed with the cabinet manufacturer. Moving the patch panels to adjacent locations or implementing a lower switch density may be required. While moving switches into open racks with adjacent patch panels provides a solution, this is only recommended if proper access security processes exists and some form of intelligent patching or other monitoring system is used so that network administrators can be notified immediately of any attempt to access switch ports. Option Three consists of providing consolidation points for connections. These can be either connecting blocks or patch panels. This allows for a zoned cabling approach, but may lead to higher moves, adds and changes costs. They do, however provide for quite a bit of reconfiguration options, particularly in two pair applications. It is also difficult to design within the parameters of a 4 connector channel when using Zone distribution. The other disadvantage to the consolidation point model is that the changes take more time than swapping a patch cord if the pair count changes. Depending on the location of the consolidation point, there may be additional risks from loss of static pressure, ending up with more than 4 connectors in a channel, or harming existing channels during changes. A final option is to have all server cabinets and switch cabinets in a row, terminating to a single patching field for the row, rather than to a central location. Core connections from the MDA are brought into this patching field. This option can work well in ISP or other environments where cross department/customer functionality is not desirable or tolerated. This option provides a bit of best of both worlds in that there will be some spare ports, but also the floor tiles will not have to be lifted to perform MAC work. While this is very similar to the first option, the segmentation can make it easier for network administrators and physical plant technicians to coordinate efforts. Additionally this style of design also provides for flexibility in the every changing environment of Shrinking and Expanding storage requirements over time Whichever cabling choice or space option is made, the key step is planning. Siemon has resources to assist in the layout and planning or just as a second pair of eyes for any project. For more information, and additional resources got to www.siemon.com.
|




