Document Network Connectivity

Cable documentation will be part of a comprehensive physical network design and should include a P2P cable matrix/schedule. The P2P matrix defines the logical connections between any two ports as well as the physical distance between the port pairs. This will ensure that all interconnects are properly accounted for and will facilitate an efficient and error free deployment.

Note

Document the planned and later the actual topology of the configuration. Be sure to keep the documentation updated reflecting any changes to the planned topology.

Point-to-Point Cable Map

The P2P cable map is a comprehensive document consisting of a list of all cables to be implemented, a source and destination and bundling matrix describing every cable end point, and labeling information. There should be a map that expresses for each server or switch, the rack in which it is located and its exact position in the rack. Also, for each server type a map should be included explicitly showing the location of the port. This is particularly important for hosts with multiple network interfaces. From this map, cable lengths and bundling strategy can be determined.

It is important to review this map thoroughly to ensure it is correct. Incorrect cable lengths can lead to issues in system deployment and lead to long delays if cables need to be reordered. System owners should consider consulting with network experts to ensure their P2P map is correct.

Constructing Cable BOM

While planning the cable implementation various intricacies of the logical and physical design will dictate the sourcing of many different cables of different lengths and types. Key cable features including length, cable type, and cable connector must be determined. This step should be given the proper time and attention to ensure it is done correctly. Determining physical cable lengths from the P2P map can be difficult because of any number of factors that affect how cables are installed. Ordering cables that are too short will cause a delay in system deployment to reorder the right cables. While conservative estimates of cable length can prevent this issue, managing the extra cable can be challenging and lead to long-term cable maintenance issues.

Labeling Information

Many different naming conventions exist, and large cable deployments rely heavily on good practices. It is critical that all cluster elements have unique names to ensure all are connected per the design.

The cable labeling then should reflect at least:

  • Designations representing origin components and destination components.

  • Including the port the cable should connect to.

  • Cable type and length details.

  • And the BSN (see: Approach and Methodology).