A 42U cabinet does not give you 42U of usable space, and the sooner you internalise that the fewer awkward conversations you will have about why the new server does not fit.
This part is the physical frame: what the numbers mean, what holds equipment in, why depth and weight matter more than height, and how to read the diagram that describes it all.
Nineteen inches, and why everything is that wide
The standard is EIA-310. It fixes the width of the equipment's mounting face at 19 inches (482.6 mm) and the vertical pitch at 1.75 inches (44.45 mm), which is one U.
Two things follow that are worth saying out loud, because they trip people up.
19 inches is the front panel width, not the cabinet width. The mounting rails are 19 inches apart at the face; the cabinet around them is wider. Colocation cabinets are typically 600 mm or 800 mm wide externally. That extra 200 mm on an 800 mm cabinet is not wasted — it is the vertical cable management channel down each side, and it is the difference between a rear that you can work in and a rear that is a rat's nest.
U is a pitch, not a box. Equipment is built slightly under its nominal U height so it can slide in without binding. A 1U server is about 44 mm tall, not exactly 44.45. This is why you cannot stack equipment to fill an arbitrary gap: mounting holes only exist at U boundaries.
← ───────── 19" / 482.6 mm mounting face ───────── →
┌─┬──────────────────────────────────────────────────┬─┐
│o│ │o│ ┐
│o│ 1U of equipment │o│ │ 44.45 mm
│o│ │o│ ┘
├─┼──────────────────────────────────────────────────┼─┤
│o│ │o│
│o│ 1U of equipment │o│
│o│ │o│
└─┴──────────────────────────────────────────────────┴─┘
^ ^
└── mounting rail, punched with holes in ┘
repeating groups of three per U
The holes come in groups of three per U, unevenly spaced — a wide gap, then two closer together. That uneven pattern is how you find a U boundary by eye. If a technician mounts something one hole out of alignment, everything above it in the rack is now offset by a third of a U and nothing else will line up. This is a real and common failure, and it is why "start from a marked U" is standard practice.
Square holes, cage nuts, and threaded holes
Three kinds of rail exist and you should know which you have.
Square holes are the modern datacenter default. The hole is a plain square with no thread. You clip a cage nut into it — a small square nut in a springy sheet-metal cage — and then screw into that. The advantage is flexibility: any thread size, any equipment, replaceable if you strip one.
Round threaded holes (usually M6 or 10-32) are older and common in telecom and small office racks. You screw directly into the rail. Simpler, but a stripped thread damages the rack rather than a 20-cent part.
Tool-less rails clip straight into square holes with no screws at all. Most modern 1U and 2U servers ship with these, and they are why racking a server is now a two-minute job rather than a twenty-minute one.
Cage nuts have a correct orientation — they insert from the rear of the rail with the spring clips facing the installer — and they are the single most-cursed component in the building because installing them by hand hurts. There is a dedicated tool. Technicians have one. This is not your problem, but if a ticket comes back saying a cage nut was missing at a given position, now you know what was being asked for.
Rails, and the depth problem
A server does not sit on a shelf. It mounts on a pair of rails that bolt to the front and rear posts, and the server slides onto them.
This means the distance between the front and rear posts must match what the rail kit supports. Rail kits have an adjustment range — commonly something like 610–915 mm — and if your cabinet's post-to-post depth falls outside it, the rails do not fit. Full stop. No amount of effort at the far end fixes it.
Cabinet depths you will see are 600, 800, 1000 and 1200 mm externally, with most datacenter cabinets in the 800–1070 mm range. A 600 mm deep cabinet is a network cabinet — switches and patch panels are rarely deeper than about 400 mm — and it will not take a modern server at all.
Depth is the dimension that actually constrains you, not height. A GPU server or a high-density storage chassis can be long, and once you add the rear cable bend radius and a cable management arm you can run out of cabinet before you run out of U. When you spec a machine for a cage you did not design, the chassis depth and the rail kit's supported range are the two numbers to check first.
Two kinds of rail behave differently. Sliding rails let the server pull forward for service without unracking it, which is what you want for anything with disks you will swap or lids you will open. Static rails are fixed; servicing means unbolting the machine and taking it out, with a second person if it is heavy. Sliding rails usually need a cable management arm and a service loop — deliberate slack in every rear cable so the machine can travel without unplugging itself. If a machine is racked on sliders with cables cut to exact length, it can only be serviced by disconnecting it, which quietly defeats the point.
Weight, and why the bottom of the rack is not free real estate
Cabinets have a static load rating, often in the region of 1000–1500 kg, and floors have their own limit, which in a raised-floor room can be the tighter of the two.
The operational rule is simple and universal: heavy things go at the bottom. A full 4U disk shelf mounted at the top of a cabinet makes it top-heavy, and a top-heavy cabinet on castors is dangerous to move and can tip when a sliding-rail server is pulled fully out of it. Technicians know this. It is worth knowing too, so that when you plan an elevation you put the storage low and the 1U compute high, rather than the other way around.
Blanking panels are not cosmetic
An empty U in the middle of a populated cabinet is a hole between the cold aisle and the hot aisle. Hot exhaust air flows back through it to the front of the rack, gets sucked into the next server's intake, and that server now runs hot for no reason a monitoring dashboard will ever explain.
Blanking panels are blank sheets of metal or plastic that fill unused U positions and stop that recirculation. They cost very little and they are the single highest-return thing in a cabinet.
Two related airflow items in the same family: brush strips or grommets where cables pass through the cabinet floor or roof, and side panels fitted so air cannot bypass between adjacent cabinets. All three do the same job — force air to go through the equipment rather than around it.
If you are ever asked to approve a rack build and you see empty unblanked U positions in the elevation, that is a legitimate thing to comment on.
0U and the vertical space
You will see PDUs described as 0U. That means they mount vertically in the cabinet's side channel rather than horizontally in the 19-inch mounting space, so they consume no U at all. A 42U cabinet with two 0U PDUs still has 42U free.
That side channel is also where vertical cable managers live. It is the reason to pay for an 800 mm wide cabinet rather than a 600 mm one when the cabinet holds servers.
Reading a rack elevation
A rack elevation is the map of what is mounted where. It is what you send when you ask for something to be installed, and what you consult when you ask for something to be touched. It looks like this:
CABINET DC1 / ROW-C / RACK-07 (front view)
┌────┬─────────────────────────────────────────────────────┐
│ 42 │ ░░░ blanking ░░░ │
│ 41 │ patch panel PP-01 (24 x LC duplex, to MMR) │
│ 40 │ switch sw-c07-01 Arista 7050SX 48x10G+4x40G │
│ 39 │ switch sw-c07-02 Arista 7050SX 48x10G+4x40G │
│ 38 │ ░░░ blanking ░░░ │
│ 37 │ srv-web-11 Dell R650 1U │
│ 36 │ srv-web-12 Dell R650 1U │
│ 35 │ srv-web-13 Dell R650 1U │
│ .. │ ... │
│ 04 │ ┌───────────────────────────────────────────┐ │
│ 03 │ │ srv-stor-01 Supermicro 4U 36-bay │ │
│ 02 │ │ (heavy — bottom of rack) │ │
│ 01 │ └───────────────────────────────────────────┘ │
└────┴─────────────────────────────────────────────────────┘
0U left channel: PDU-A 0U right channel: PDU-B
Some conventions to note.
A U position is a location, and it is how you name things to remote hands. "The server at U37" is unambiguous in a way that "the third one down" never is.
Which end is U1 is not universally standardised. The common convention numbers from the bottom up, so U1 is the lowest position — and most cabinets are physically labelled that way on the rail. But it is not a guarantee: some manufacturers and some organisations number from the top down, and NetBox has carried a long-running discussion about supporting both because real deployments do both. So do not assume. Look at how your own cabinet's rails are printed, and match that. If a cabinet is unlabelled, agree a convention with the facility in writing before the first install, and put it in the elevation.
A multi-U device occupies a range and is referenced by its lowest U. The 4U storage box above lives at U1–U4 and you call it "U1".
Front and rear are separate views. Some things — PDUs, rear-mounted patch panels, cable managers — appear only in the rear elevation. If your documentation only has a front view, half the cabinet is undocumented, and that half is the half with all the cables in it.
If you keep this in NetBox or an equivalent DCIM, keep it accurate rather than complete. An elevation that is 60 % filled in but true is worth more than one that is 100 % filled in and eight months stale, because remote hands will act on it.
Labelling
The standard here is ANSI/TIA-606 (currently at revision D), which sets out how to identify cabling infrastructure, and it dovetails with TIA-942, the datacenter standard that divides a facility into functional areas — entrance room, main distribution area, horizontal distribution area, equipment distribution area, and so on.
You almost certainly do not need to implement TIA-606 formally. What you need is the idea behind it: a hierarchical identifier that reads from the outside in. Room, row, cabinet, panel, port. Something like DC1-C07-PP01-14 tells anyone in the building exactly where to stand and what to touch, and it sorts sensibly in a spreadsheet.
The two rules that pay for themselves regardless of standards: label both ends of every cable, and make the label say where the other end is. A cable tail that reads → sw-c07-01 Gi1/0/14 means nobody ever has to trace it by hand.
The five numbers to know about your own cabinet
If you take one thing from this part, make it this list. These are the facts about your cage that you should be able to answer without looking:
- Cabinet identifier — room, row, position, in whatever scheme the facility uses.
- Height in U, and how many are free — plus whether U1 is at the top or the bottom.
- Usable depth, post to post, so you can check a rail kit before you buy a server.
- Power — how many feeds, at what voltage and amperage. Part 2.
- Uplinks — what the cabinet's switches connect to, and how many ports are spare. Part 5.
I could not answer three of those five for my own kit when I started writing this. That is exactly the gap this series exists to close.
Next up: Part 2 — power, A-side and B-side, where the 80 % rule turns a 30 A feed into rather less than 30 A.