I have never racked a server. I have opened a lot of tickets asking someone else to - which is the normal shape of this job now, and it works right up until the facility emails you a sentence made entirely of acronyms.

Eight parts on the physical layer a Linux engineer actually has to reason about, plus an on-ramp: racks, power, cables, out-of-band access, switch placement, cross-connects, and how to write a remote hands ticket that comes back done the first time. Not a datacenter design course - the subset you need to describe your own hardware accurately and direct the people who touch it.

Part 0 is the on-ramp - skip it if you already know what a demarc is. If you are here mid-task, go straight to the cheat sheet.

0 Part 0: The vocabulary (start here) Demarc, A-side, DAC, BMC, cross-connect. The five nested boxes a datacenter is made of, and the words that describe them. 1 Part 1: Anatomy of a rack U and rails and cage nuts, why depth constrains you more than height, and how to read a rack elevation. 2 Part 2: Power, A-side and B-side Why a 30 A feed gives you 24 A, why redundancy halves it again, and every connector from C13 to L21-30P. 3 Part 3: Cables, optics and transceivers DAC, AOC or transceiver. Multimode or singlemode. LC or MPO. Choosing correctly, by distance. 4 Part 4: Out-of-band access The second computer inside your server: iDRAC, iLO, IPMI, Redfish, serial consoles - and why a BMC must never face the internet. 5 Part 5: Where the switches live Top of rack versus end of row, leaf-spine, and the oversubscription ratio that explains your unexplained slowness. 6 Part 6: Leaving the cage Demarc, Meet-Me Room, cross-connects and LOA-CFAs. Direct connect, transit, peering and 95th-percentile billing. 7 Part 7: Directing remote hands The ticket template, the standard jobs written out in full, and how to verify the work rather than the report. 8 Part 8: The cheat sheet Every number, connector, command and rule from the series on one page.