Racks, layout & cabling plant

Cabinets & frames

The cabinet as a mechanical product: mounting standard, size, load and seismic ratings, bonding, and the airflow parts it carries. PDU selection and busbar are on Power, containment design on Cooling, GPU rack forms on AI Factory, and floor loading and building seismic design on Facility. The mounting and TIA standards are paywalled, so the figures here come from OEM pages and trade press and are marked where secondary. Sources checked 5 Oct 2026.

Mounting standards

EIA-310 (19-inch). The enterprise default: 19 in (482.6 mm) mounting width, 1U = 1.75 in (44.45 mm), and a repeating three-hole pattern per U (Schneider FAQ FA158600). Almost every enterprise server, switch, and storage shelf fits it.

OCP Open Rack (ORv3). The main non-EIA alternative: a 21 in internal width, a 48 mm “OpenU”, and a 48 V DC busbar with blind-mate power shelves, with adapters for 19 in gear (ATEN ORv3 product page). It changes power distribution as much as mechanics, so treat it as a platform decision with Power and AI Factory, not a cabinet option.

Height, width and depth

Open two- and four-post frames suit distributor patching where airflow is not managed per cabinet. Colo providers may discourage them for active equipment (see Colo fit-out).

Load ratings

A single “weight rating” hides four different numbers. They are not interchangeable, and a seismic rating is usually far lower than the static one (Belden).

Compare vendors on the same rating type and test basis, and ask which standard and safety factor sit behind each number. Check the floor as well as the cabinet: floor loading and the delivery route are on Facility.

Seismic anchorage and bracing

Building code, seismic design category, and the anchorage design are on Facility: Seismic. What this page owns is the cabinet side: a cabinet seismic rating (for example GR-63-CORE Zone 4, or local approvals such as the OSHPD pre-approval listed on the CPI page) applies only with the anchorage the test used. On a raised floor that means a seismic stand or bracing to the slab, not the floor tiles (raised floor vs slab). Overhead tray and ladder rack need bracing too.

Bonding

Bond each cabinet to the telecommunications bonding backbone with a rack bonding conductor and paint-piercing hardware, per ANSI/TIA-607 (current revision). The grounding electrode system and the electrical ground are on Power.

Airflow parts on the cabinet

The cabinet owns the parts that stop bypass air: blanking panels in every open U, brush strips where cables pass, side-panel seals and pass-throughs, top and bottom seals, and floor grommets. Containment as a cooling design, including aisle doors and roofs, is on Cooling. Some colo providers make blanking and containment mandatory from day one (see Colo fit-out).

Cabinets design / build / manage

Design

• Fix the mounting standard (EIA-310 or ORv3) per row before ordering
• Specify width per position (800 mm minimum for distributors) and depth for the deepest device plus rear managers and PDUs
• Specify static, rolling, and (for integrated racks) dynamic ratings separately; add a seismic rating with its anchorage on seismic sites

Build

• Anchor exactly as the seismic test specified, and bond each cabinet before any equipment is powered
• Fit blanking, brush strips, and side seals at install, not after the first hot-spot alarm

Manage

• Track loaded weight per cabinet against its static rating, and against its seismic rating where that applies
• Re-check anchorage and bonding after a cabinet is moved

Rows, aisles & switch placement

Where cabinets stand and where switches sit, as a layout and cable-volume question. Switching architecture, switch count, and oversubscription are on Network: Fabric design. The room itself and its floor loading are on Facility. Containment is on Cooling. Sources checked 5 Oct 2026.

Aisle orientation and clearances

Face cabinet fronts toward each other across cold aisles and rears toward each other across hot aisles, so no cabinet draws another’s exhaust. On a raised floor, align cabinet fronts or rears with tile edges so perforated tiles can be lifted in the cold aisle. Take front and rear clearances from the current TIA-942/TIA-569 text and local egress code, and widen them where loaded cabinets or long servers must be moved in.

ToR, MoR, EoR or centralized

The same fabric can be cabled four ways. Each moves the patching and the cable volume to a different place.

DAC reach. Passive copper reach shrinks as lane speed rises. At the next lane rate, passive DAC may not reach an adjacent cabinet or a MoR or EoR switch, so those links become active copper, AOC, or optics (reach figures on Network: DAC, active copper, and AOC). Do not plan cross-cabinet server links on passive DAC beyond the current generation without checking.

The placement fixes the link lengths, which feed the optics choice on Network: Optics. Decide placement and plant together, then hand network a length per link class.

Growth headroom

Reserve the floor positions, pathway capacity, and distributor panel space for planned growth on day 1. Adding trunks later is easy; adding tray and distributor cabinets in a live hall is not.

Layout design / build / manage

Design

• Choose switch placement with network (fabric design), then size pathways and distributor cabinets for it
• Lay out hot and cold aisles and reserve growth positions in every row

Build

• Set out rows to the drawing and check clearances before cabinets are anchored

Manage

• Place new equipment to the plan; do not let growth positions fill ad hoc

Pathways & separation

How cable gets between cabinets and rooms. Power pathways and busway are on Power. The underfloor plenum as an air path is on Cooling. Raised floor vs slab as a building decision is on Facility. Separation distances are deliberately not published here until checked against the standard text. Sources checked 5 Oct 2026.

Overhead vs underfloor

Neither is right everywhere. On slab, overhead is the only option. On a raised floor kept for air supply, moving data cable overhead is common; check the fire-code and plenum rating of cable in each space.

Tray and fill

Use a dedicated fiber raceway or a separated tray for fiber, so copper and power bundles do not crush it, and keep to the manufacturer’s bend radius at every drop. Design tray fill to the limit in TIA-569 or the manufacturer’s guidance, and leave capacity for growth.

Separation of power and data

Separate power and data per TIA-569 (current revision), ISO/IEC 14763-2, or EN 50174-2. TIA-942 once carried its own data-center separation table; from 942-A it refers to TIA-569 instead (J. Jew, TIA-942 editor, cablinginstall 2010). Required distances depend on circuit count and rating, whether the power cable is shielded, and whether a bonded metallic tray or barrier separates them. Use divided or separate trays, and cross power at right angles where the paths must meet.

Penetrations

Seal every floor cutout with brush seals or grommets, and firestop every penetration of a fire-rated wall or floor with a listed system. Leave spare sleeves for growth so later work does not break the firestop.

Pathways design / build / manage

Design

• Decide overhead or underfloor with cooling and facility, then size tray for the switch placement and growth
• Route power and data in separate or divided pathways per TIA-569 / EN 50174-2

Build

• Brace overhead tray on seismic sites; bond metallic tray
• Seal floor cutouts and firestop wall penetrations before handover

Manage

• Remove abandoned cable and audit tray fill at each major change

Structured cabling plant

The passive fiber and copper plant: topology, media, trunks, panels, testing, labeling, and records. This page owns the plant; Network: Optics owns the transceivers, reaches, DAC/AOC, and application loss budgets that run on it. The hand-off between the two is a per-link record of fiber type, connector type and count, end-face (APC/UPC), polarity method, length, designed loss, and, for singlemode, connector reflectance. Short-reach singlemode (DR/FR) budgets depend on reflectance as well as loss (Network: Optics budgets). The rooms the plant connects are on Facility; cross-connect ordering is on Network: Edge. TIA and ISO/IEC cabling standards are paywalled, so many figures here come from OEM and trade sources and are marked. Sources checked 5 Oct 2026.

Topology

TIA-942 structures the cabling as a hierarchical star. Backbone cabling runs from the entrance room (ER) to the main distribution area (MDA), and from the MDA to any intermediate (IDA) and horizontal (HDA) distribution areas. Horizontal cabling runs from the HDA, optionally through a zone distribution area (ZDA), to the equipment distribution area (EDA) in the cabinet rows. The areas as rooms and zones are described on Facility: Distribution areas. In a single-room data center of a few rows, an MDA plus row-level patching is typical; an IDA is rare and ToR designs often drop the HDA.

What TIA-942-C (May 2024) changed for the plant, per trade-press summaries:

• Any TIA-568.3-compliant optical connector is allowed at connections other than the equipment outlet, which opens distributors to very-small-form-factor (VSFF) connectors such as MDC, SN, and CS
• LC and MPO are still required at the equipment outlet
• Horizontal and backbone fiber cabling: two fibers minimum
• Single-pair balanced cabling is recognized, and wireless access points get at least two Cat 6A runs
• Edge data-center content from 942-B-1 is incorporated

Sources: TIA press release, 9 May 2024 (confirms new media and connectivity requirements, new cabling and minimum cabinet width requirements, and the edge data-center content, without details); cablinginstall, Nov 2024, Data Center Frontier, Feb 2024.

ISO/IEC status (fast-changing). ISO/IEC JTC 1/SC 25/WG 3 told IEEE 802.3 in March 2026 that ISO/IEC 11801-5 (data centre cabling) is being revised for AI and hyperscale data centers and is at working-draft stage; that ISO/IEC 14763-2 will update its MPO polarity, pinning, and angle guidance; and that an amendment to ISO/IEC 14763-3 (fibre testing, 2024 edition) adds MPO breakout-link testing and MPO-16 reference connectors, with its first working draft circulated in April 2026 (SC25/WG3 liaison to IEEE 802.3, Mar 2026).

Fiber media

Choose the media per link class (in-row, row to MDA, MDA to ER, building to building), not once for the whole site. Multimode (OM4, OM5) and singlemode (OS2) trade reach and future speed headroom against optic cost and power; that comparison belongs to Network: Optics, so make the choice jointly. What this page fixes is the fiber type, the fiber count per trunk with spares, and the designed loss of each link. Note that some colo providers now offer only singlemode cross connects (see Network: Edge), which pushes the cage-to-MMR link class to OS2.

Designed loss. Build each link’s designed loss from standard component allowances, then hand it to network to check against the application budget. Do not publish application budgets here.

In a data hall the connectors dominate, not the fiber: by these allowances a 50 m multimode link with two mated pairs designs to 0.15 dB of fiber plus 1.5 dB of connectors at 850 nm. Compare the designed loss with each optic’s channel budget on Network: Optics budgets. Multimode budgets are tight, so cassette-based links with several mated pairs may need low-loss components. Every cassette or patch field adds a mated pair. If you design to a low-loss component vendor’s figures instead, use their maximum, not typical, values and record which you used.

MPO trunks, cassettes and polarity

Trunk base. Choose a fiber count per connector that the optics roadmap on Network: Optics can consume without stranding fibers. Base-8 trunks map cleanly onto 8-fiber parallel optics. 16-fiber MPO (MPO-16, angled) interfaces serve 8-lane optics, and Y-harnesses break an MPO-16 out to two MPO-8. One OEM range offers MPO-16 angled trunks from 8 to 288 fibers (Corning LAN-2495; Corning–Arista cabling guide). Which MPO each optic presents (fiber count, MPO-12 or MPO-16, APC or UPC) is listed on Network: Optics PMDs; note that multimode MPO-16 modules are angled (APC) too, so APC is not a singlemode-only property. Base-12 remains common in installed plant. “MTP” is one manufacturer’s brand of MPO-compatible connector; this page says MPO.

Polarity. TIA-568.3-E (Sep 2022) keeps Methods A, B, and C and adds universal Methods U1 and U2. Both use Type-B trunks, A-to-B duplex cords, and the same MPO-to-LC modules at both ends; U1 uses key-up-to-key-down adapters and U2 key-up-to-key-up. Because standard singlemode MPO connectors are angled (APC), U1 also works for singlemode, and Siemon gives that as the reason to prefer U1 there (Siemon, Oct 2022). Pick one method for the site, write it into the as-built, and buy every trunk, module, and cord to it. Parallel-optic MPO channels (SR4, DR4, SR8, DR8) also need an end-to-end lane check that each Tx fiber lands on the matching Rx, separate from the duplex polarity method.

Pinning and end-face. A mated MPO pair needs one pinned and one unpinned connector, and angled (APC) and flat (UPC) end-faces must not be mated. MPO-16 is keyed differently from MPO-12 and does not intermate with it, so mixed-generation plant needs harnesses or conversion cords, not adapters. Specify pinning, end-face, and fiber count per component in the bill of materials.

Copper

Copper remains in the plant for management and BMC ports, out-of-band networks, building systems, and low-speed links. Structured copper is a 90 m permanent link inside a 100 m channel per TIA-568.2-D; Cat 6A is the usual category for new data-center copper. In-rack direct-attach copper and active cables are transceivers, not plant, and stay on Network: DAC, active copper, and AOC. Management network design is on Network: OOB.

Patch panels and cable management

• Density vs access. High-density panels (MPO, VSFF) save U but are harder to work in. Size density to the fingers that will patch it, not the catalog maximum.
• Angled vs flat panels. Angled panels feed cords straight into vertical managers and can remove horizontal managers; flat panels with horizontal managers are easier to label and trace.
• Managers. Size vertical managers for the full cord count at build-out, keep fiber and copper in separate managers or channels, and hold the manufacturer’s minimum bend radius.
• Slack. Store trunk slack in a slack manager or tray, not coiled in the cabinet. Order pre-terminated trunks to measured lengths.
• Diversity. Do not land both paths of a redundant pair, or both management circuits, on the same panel; the management case is on Network: OOB.

Testing and certification

Acceptance package. Accept the plant on a test report for every link, keyed to the link’s label, with the reference method, limits, and tester calibration date. Manufacturer system warranties usually require certification results from an approved installer, so agree the format before installation starts.

Labeling

ANSI/TIA-606-D, the administration standard, was approved for publication in Q3 2021 (CommScope Standards Advisor, Q4 2021). Secondary summaries describe classes of administration by complexity and unique identifiers for spaces, pathways, cables, termination hardware, and bonding, linked to records. In practice:

• Choose the administration class and identifier scheme at design and use it in drawings, labels, test results, and DCIM
• Label both ends of every cable and every panel port before testing, so each test result carries the identifier
• Use labels rated for the environment that will survive re-patching

As-built records

The as-built is the plant’s source of truth. Hand it over with the plant and keep it current. It should hold:

• Panel and port maps, trunk identifiers and fiber counts, connector types, and the polarity method
• Per-link length, designed loss, end-face (APC/UPC), and, for singlemode, connector reflectance (the hand-off to Network: Optics budgets)
• Test results (OLTS, OTDR, copper) keyed to identifiers
• Pathway routes and fill
• Cross-references to the circuit, cross-connect, and LOA records on Network: Edge and the console and management port map on Network: OOB

DCIM holds the live copy (Ops). Every move, add, or change goes through change control, is re-tested, and updates the record before the ticket closes.

Cabling plant design / build / manage

Design

• Fix fiber type, trunk base, and fiber count per link class with network, from the optics roadmap on Network: Optics; include spare fibers
• Choose one polarity method for the site, and specify pinning and end-face for every component
• Calculate designed loss per link from component allowances and give network the length, loss, end-face (APC/UPC), and, for singlemode, connector reflectance per link class (Optics budgets)
• Set the TIA-606 administration class and identifier scheme

Build

• Inspect and clean every connector before mating (IEC 61300-3-35)
• Certify fiber to Tier 1 (OLTS) at minimum, and Tier 2 (OTDR) for backbone, trunks, and tight loss budgets; verify MPO polarity end to end
• Certify copper permanent links to their category (for example Cat 6A)
• Label every cable and port before testing; accept the plant on test results plus the as-built

Manage

• Keep as-built cabling records current, cross-referenced to cross-connect and console records
• Run moves, adds, and changes under change control, and re-test after each
• Audit records against the floor periodically

Colo cage fit-out

Onsite you lay out the room freely. In colo you fit out a cage or cabinets inside the provider’s grid and rules. The site-level divergence is on Facility; cross connects on Network: Edge; contracted kW and rack PDUs on Power; provider cooling limits on Cooling; cage access control on Security. Provider rules are provider-specific and change; one provider is used as an example, not a norm. Sources checked 5 Oct 2026.

Onsite vs colo

Provider rules: one example

Equinix’s customer installation guidelines (Equinix, undated page) show how far provider rules reach into the fit-out:

• New cage deployments must include hot- or cold-aisle containment from day one, with self-closing doors, infill panels, and blanking
• Every open U must be blanked; brush strips where cables pass; side panels kept with pass-throughs
• Open cabinets and two- or four-post racks are discouraged for active equipment
• Cable management must not block airflow; airflow non-conformances carry a remediation deadline and can affect SLA claims
• Inter-cabinet cabling is ordered through the customer portal; where shared space has no side pass-throughs, an intra-customer cross connect is needed
• Customers may not use overhead infrastructure in shared areas; raised-floor entries need brush seals or grommets
• Provider staff connect rack PDUs (detail on Power); combustible packing is not allowed in the white space

Other providers differ. Get the provider’s install guide before designing the cage, and design the plant to it.

The demarc as the plant boundary

In colo your plant ends at the demarc panel in your cage. Everything beyond it, back to the meet-me room, is the provider’s cross connect: ordered by you against the Z-side LOA, installed and tested by the provider (Network: Edge). Size the demarc panel for the cross connects you expect over the contract. Make it OS2 with the provider’s connector and end-face, since some large providers offer only singlemode cross connects (cited on Network: Edge), and record each cross-connect ID against its panel and port in your as-built.

Colo fit-out design / build / manage

Design

• Get the provider’s install guide and hall grid before drawing the cage
• Design containment, blanking, and pathways to the provider’s rules from day one
• Decide which inter-cabinet cabling you install and which the provider must

Build

• Use the provider’s approved installers where required; certify and label to your own standard regardless
• Record provider cross-connect IDs against demarc panel ports at turn-up

Manage

• Track provider rule changes and airflow audit findings
• Reconcile your as-built with the provider’s cross-connect inventory