Reference Architecture: Rack Layout
Purpose: For platform engineers, provides standard rack configurations, server placement, and labeling conventions.
Overview
Consistent rack layout reduces cabling errors, simplifies maintenance, and ensures adequate airflow. This document defines the standard rack configuration for openCenter deployments, covering U-space allocation, device placement, and labeling.
Rack Specifications
| Specification | Minimum | Recommended |
|---|---|---|
| Height | 42U | 42U |
| Width | 600 mm (24 in) | 600 mm or 750 mm |
| Depth | 1000 mm (42 in) | 1070 mm (42 in) or 1200 mm (48 in) |
| Weight Capacity | 900 kg (2,000 lbs) | 1,360 kg (3,000 lbs) |
| Mounting | 4-post, square-hole | 4-post, square-hole, tool-less |
| Example Models | APC NetShelter SX 42U, Rittal TS IT 42U | Same, with side panels and roof fan tray |
Use 1070 mm or deeper racks for servers with cable management arms. Shallow racks (800 mm) do not accommodate modern 2U servers with rear cable routing.
Standard Rack Layout (42U)
This layout supports a single-rack openCenter deployment with 4 hypervisor hosts, 1 management host, and networking.
| U Position | Device | Height | Notes |
|---|---|---|---|
| U42 | Blanking panel | 1U | Top of rack — reserve for future |
| U41 | OOB Management Switch | 1U | 1 GbE for BMC/IPMI |
| U40 | ToR Leaf Switch 02 | 1U | 25 GbE data network |
| U39 | ToR Leaf Switch 01 | 1U | 25 GbE data network |
| U38 | Horizontal Cable Manager | 1U | Patch cables from switches |
| U37 | Blanking panel | 1U | Airflow separation |
| U35-U36 | Hypervisor Host 04 | 2U | Expansion / future growth |
| U33-U34 | Hypervisor Host 03 | 2U | |
| U31-U32 | Hypervisor Host 02 | 2U | |
| U29-U30 | Hypervisor Host 01 | 2U | |
| U28 | Horizontal Cable Manager | 1U | Server-side patch cables |
| U27 | Blanking panel | 1U | Airflow separation |
| U25-U26 | Management Host 01 | 2U | vCenter, bastion |
| U24 | Blanking panel | 1U | |
| U1-U23 | Available | 23U | Future expansion |
PDUs mount vertically in zero-U space (left and right rear posts). They do not consume U-space.
Multi-Rack Layout
For deployments spanning multiple racks, distribute roles across racks for fault isolation:
| Rack | Contents | Purpose |
|---|---|---|
| Rack 1 | 2x Hypervisor Hosts, 1x Management Host, 2x Leaf Switches, 1x Spine Switch | Primary compute + network |
| Rack 2 | 2x Hypervisor Hosts, 2x Leaf Switches, 1x Spine Switch | Secondary compute + network |
| Rack 3 (optional) | Storage array, backup appliance, additional hosts | Shared storage + DR |
Place spine switches at the top of each rack or in a dedicated network rack, depending on cabling distance and fiber budget.
Placement Rules
- Switches at the top. Minimizes cable runs from servers to ToR switches.
- Heaviest equipment at the bottom. Servers and storage arrays go in the lower half for rack stability.
- Cable managers between device groups. Place 1U horizontal cable managers between switch and server sections.
- Blanking panels in every unused U. Prevents hot air recirculation from rear to front. Missing blanking panels measurably increase inlet temperatures.
- Leave expansion space. Reserve at least 25% of U-space for future growth.
Labeling Conventions
Every device, port, and cable must be labeled. Use a consistent scheme across all racks.
Device Labels
Format: <site>-<rack>-<role><number>
| Example | Meaning |
|---|---|
| DC1-R01-HV01 | Data Center 1, Rack 01, Hypervisor Host 01 |
| DC1-R01-LF01 | Data Center 1, Rack 01, Leaf Switch 01 |
| DC1-R01-MG01 | Data Center 1, Rack 01, Management Host 01 |
| DC1-R01-OOB01 | Data Center 1, Rack 01, OOB Management Switch 01 |
Port Labels
Format: <device>:<interface>
| Example | Meaning |
|---|---|
| DC1-R01-HV01:NIC0 | Hypervisor Host 01, NIC port 0 |
| DC1-R01-LF01:Eth1/1 | Leaf Switch 01, Ethernet port 1/1 |
Rack Labels
Attach a printed label to the front and rear of each rack at eye level showing:
- Rack ID (e.g., DC1-R01)
- Row and position
- Power circuit IDs (Feed A, Feed B)
- Emergency contact
Airflow Orientation
All equipment must face the same direction within a rack:
- Front (cold aisle): Air intake
- Rear (hot aisle): Exhaust
Verify airflow direction for each device before installation. Some network switches have port-side exhaust while others have power-side exhaust. Mixing airflow directions defeats hot/cold aisle containment.
Weight Distribution
| Component | Approximate Weight |
|---|---|
| 2U Server (fully loaded) | 25-35 kg (55-77 lbs) |
| 1U Switch | 5-10 kg (11-22 lbs) |
| Vertical PDU | 10-15 kg (22-33 lbs) |
| Full rack (4 servers + switches + PDUs) | 200-250 kg (440-550 lbs) |
Verify that the data center floor supports the per-tile weight. Standard raised floor tiles support 450-680 kg per tile.
Considerations
- Seismic bracing: In earthquake-prone regions, bolt racks to the floor and install seismic bracing kits per local building codes.
- Hot/cold aisle containment: Verify that rack dimensions and door configurations are compatible with the containment system.
- Rear door heat exchangers: For high-density racks (> 10 kW), consider rear-door heat exchangers as an alternative to increasing room-level cooling.
- Asset tracking: Photograph each rack front and rear after installation. Update the rack diagram whenever equipment changes.
- Fire suppression: Verify clean-agent fire suppression (FM-200, Novec 1230) rather than water-based sprinklers.