Server Room & Rack Planning Guide

This is an original planning guide. It is not a vendor manual, an official standard, or legal advice. Example addresses use documentation ranges. Review every command before you paste it.

A room is power, cooling, and a path for cables

A server room plan is a rack elevation, a power budget, a cooling path, and a way for humans to work. It is not a photograph of equipment in a cupboard. If you cannot stand in front of the rack, read the label, and remove one device without unplugging the neighbour, the elevation is wrong.

Power and cooling are the same watts. Electricity that enters a device leaves as heat, plus a little that leaves as light or as a signal on a cable. Plan cooling from the power you expect the room to draw, not from the number of floor tiles. Redundant power supplies only save you when they are plugged into different sources. Two cords in one PDU are one failure.

Air has a direction. Equipment that breathes front to back wants a cold front and a hot back. Mixing those in one aisle makes every device reheat its neighbour. Blanking panels are part of that, not decoration. A gap in the front of the rack is a hole in the plan.

The rack tools on this site add units and sketch an elevation from numbers you type. They do not visit the room. A measured current on the PDU beats a nameplate total. Use the nameplate to size the circuit before you buy, then measure before you declare the rack full.

Four racks as arithmetic, not as a purchase order

a mixed compute rack with 42 rack units, 18 devices at about 250 watts each, is 4500 watts of nameplate load. At 230 volts that is about 19.6 amps before diversity, and about 15345 BTU per hour if you use 3.41 BTU per hour per watt as a planning conversion. Nameplate is not measured load. Diversity means the devices will not all sit at nameplate. Measure a similar rack before you believe a small number. Cooling has to remove what the rack actually turns into heat, which is nearly all of the electrical power that stays in the room. A rack that draws 4500 watts needs a cooling path for 4500 watts, not a hope that the building air conditioning noticed. Leave blank units for cable and for airflow. Filling all 42 units because the spreadsheet allowed it produces a rack you cannot patch and cannot cool. Keep a patching field and a gap the vendor's airflow drawing asked for.

a dense storage or GPU rack with 42 rack units, 8 devices at about 800 watts each, is 6400 watts of nameplate load. At 230 volts that is about 27.8 amps before diversity, and about 21824 BTU per hour if you use 3.41 BTU per hour per watt as a planning conversion. Nameplate is not measured load. Diversity means the devices will not all sit at nameplate. Measure a similar rack before you believe a small number. Cooling has to remove what the rack actually turns into heat, which is nearly all of the electrical power that stays in the room. A rack that draws 6400 watts needs a cooling path for 6400 watts, not a hope that the building air conditioning noticed. Leave blank units for cable and for airflow. Filling all 42 units because the spreadsheet allowed it produces a rack you cannot patch and cannot cool. Keep a patching field and a gap the vendor's airflow drawing asked for.

a network and patch rack with 42 rack units, 24 devices at about 120 watts each, is 2880 watts of nameplate load. At 230 volts that is about 12.5 amps before diversity, and about 9821 BTU per hour if you use 3.41 BTU per hour per watt as a planning conversion. Nameplate is not measured load. Diversity means the devices will not all sit at nameplate. Measure a similar rack before you believe a small number. Cooling has to remove what the rack actually turns into heat, which is nearly all of the electrical power that stays in the room. A rack that draws 2880 watts needs a cooling path for 2880 watts, not a hope that the building air conditioning noticed. Leave blank units for cable and for airflow. Filling all 42 units because the spreadsheet allowed it produces a rack you cannot patch and cannot cool. Keep a patching field and a gap the vendor's airflow drawing asked for.

a branch cabinet with 24 rack units, 10 devices at about 200 watts each, is 2000 watts of nameplate load. At 230 volts that is about 8.7 amps before diversity, and about 6820 BTU per hour if you use 3.41 BTU per hour per watt as a planning conversion. Nameplate is not measured load. Diversity means the devices will not all sit at nameplate. Measure a similar rack before you believe a small number. Cooling has to remove what the rack actually turns into heat, which is nearly all of the electrical power that stays in the room. A rack that draws 2000 watts needs a cooling path for 2000 watts, not a hope that the building air conditioning noticed. Leave blank units for cable and for airflow. Filling all 24 units because the spreadsheet allowed it produces a rack you cannot patch and cannot cool. Keep a patching field and a gap the vendor's airflow drawing asked for.

Circuits, PDUs, and what redundant means

A circuit should be sized so the expected load sits well under the breaker, not on it. A breaker that trips at the peak is not a monitoring system. Leave headroom for inrush and for the next device. If you do not know the local electrical rule, stop and ask someone who does. This page is not an electrical code.

A device with two power supplies gives you redundancy only when the supplies are on different upstream sources. Those sources might be two PDUs on two circuits, ideally on two distribution paths. Label the cords A and B and label the PDUs the same way. A device with one cord is not redundant because the rack has two PDUs. Plug it into the PDU you would rather keep during a maintenance, and write that down.

UPS runtime is the battery's job for minutes, not for an afternoon. Size it for a clean shutdown or for the generator to start, whichever you actually have. A UPS that is already at 90 percent load has no room for the inrush of a restart. Measure the load. A nameplate sum that exceeds the UPS is a fact, even if the rack has not hit it yet.

Floor loading and fire suppression matter and they are building questions. A rack of disks can weigh more than the raised floor was built for. Do not discover that with the second rack. Ask before the freight elevator trip, not after.

How people have to use the room

Leave a front aisle and a back aisle you can walk. A rack against a wall with a hot exhaust into the wall wastes the rear of every device and blocks the cables. Patch panels belong where the patch can reach the switch without a permanent tangle across the exhaust.

Light and a place to put a laptop matter during an incident. A room with no flat surface becomes a room where people balance a laptop on a live device. Give them a shelf that is not a server.

Label the rack, the PDU, the circuit, and the uplink. The uplink label should match the cable label from the cabling guide. A room plan that renames the rack and not the cable plant creates two buildings. Pick the names once.

Water, drains, and coffee do not belong above or beside the rack. If the room is also a corridor, it is not a server room yet. The door should close. The cooling should be the room's cooling, not a window.

Before you add another device

Add the device's watts to the measured PDU load, not only to the spreadsheet. Confirm both power supplies have a free outlet on different PDUs if the device has two. Confirm the rack units are actually free, including the airflow gap the device needs. Confirm the uplink exists and is labelled. Then add it.

Update the elevation the same day. An elevation that lies is worse than no elevation, because the next person will trust it and pull the wrong device. The builder on this site can redraw the numbers. The truth is the room.

If the cooling alarm is already unhappy, the next device waits. Capacity of the room is the minimum of power, cooling, space, and uplink. The resource you did not check is the one that will stop you.

A worked branch cabinet makes the arithmetic concrete. Ten devices at 200 watts is 2000 watts on paper. At 230 volts that is under 9 amps before diversity, which sounds small until the UPS is a 1500 watt unit and the nameplate already exceeds it. The cabinet does not get a new server until the UPS is larger or the load is measured under the limit. The 24 rack units are not the constraint. The watts are. Write the constraint in the ticket so the next request does not arrive as a rack-unit question.

Cooling for those 2000 watts is 2000 watts of heat, about 6800 BTU per hour using 3.41 as the conversion. A room that was a cupboard with a domestic air conditioner may not remove that continuously. If you cannot name the cooling unit and its rating, you do not yet have a server room. You have a cupboard with equipment in it. Stop adding devices and name the cooling.

The elevation for that cabinet should show the patch panel, the switch, the UPS, and blanking, not ten devices stacked with no gaps. A 1U switch, a 2U UPS, and a 1U patch field already consume units before the servers start. Count those first. The servers get what remains, and what remains may be less than the order you were handed. The elevation is how you say no with a picture.

Measure the PDU load and the UPS load.
Add the new device on paper, including both cords.
Confirm free rack units and the airflow gap.
Confirm a free, labelled uplink.
Confirm cooling headroom.
Install, then update the elevation the same day.

Mistakes that fill a room too early

Summing nameplates and calling the result the measured load, in either direction.

Plugging both power supplies into one PDU.

Filling every rack unit and blocking the exhaust.

A UPS with no runtime target.

No blanking panels and a hot aisle that is also the cold aisle.

An elevation that was not updated after the last install.

A rack the raised floor was not rated for.

Treating this page as an electrical code.

Room checks before the next device lands

Confirm this before you call the change done: Measured PDU amps, not only nameplate watts, are written down. A and B cords land on A and B PDUs. The UPS load after the new device is still inside the runtime you need. Cooling can remove the added watts. The elevation shows the free units you are about to use. The uplink label matches the cable label. There is a front and a back you can stand in. Blanking panels cover the gaps the airflow needs. The circuit identifier is on the PDU. A second person agrees the room is not already the limiting resource. The limiting resource is named: power, cooling, space, or uplink. Nameplate watts were not filed as if they were a measured PDU reading. And the elevation includes patch panels and blanking, not only the new server. If one of those fails, stop.

Tools for this guide

These tools run in the browser on this site. They do not log into your machines.

Cabling & Fiber Optics Guide

Guides in this cluster

These supporting pages belong to this pillar.