Practical tools for system, network, security, and operations administrators.

NET-C0191 · Physical Layer, Cabling & Data Center

UPS Sizing and Runtime Explained

Size a UPS for the load you listed, and write the runtime you actually need.

Updated 25 October 2026 · How-To

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.

What this hour is for

A UPS estimate is watts and minutes. The calculators draft runtime or size from numbers you type. They do not see the rack. A nameplate wattage is not the same as the draw you measured, and you should say which one you used.

List what must stay up: the network core, or a single switch, not the whole building by accident. Cooling and monitors are loads too if you included those plugs.

Runtime is for a clean shutdown or a generator start. It is not an infinite design. Write the minutes you need and why.

This page does not tell you to work inside a live UPS. Mains is dangerous. The estimate stays on paper.

The change you can finish

Apply nothing during the writing of the note. When the lab window opens, it is one change on the device named in the ticket. Read the draft, then the device, then decide.

Rollback is the file or the revision you saved first. You do not invent a rollback after the only copy is gone.

  1. List the devices and the watts.
  2. Say measured or nameplate.
  3. Write the minutes required.
  4. Draft a size.
  5. Exclude loads you did not mean.
  6. Do not open a UPS.

Mistakes that outlive the command

UPS Sizing and Runtime Explained goes wrong in a small set of ways. The list is here so the ticket can forbid them before the window.

Decisions to write down

One decision for UPS Sizing and Runtime Explained: The device list is explicit. Watts are labeled measured or nameplate. Minutes are a number. The draft is labeled a draft. And no cover was removed.

Checks before you call it done

Confirm this before you call the change done: The list is in the ticket. The runtime reason is a sentence. Double counting was checked. No electrical work was done. And a qualified person owns any install. If one of those fails, stop.

Watts and minutes, on paper.
Do not open a live UPS.

Before you leave the device

UPS Sizing and Runtime Explained ends when the hostname on the device matches the hostname in the ticket. If it does not, you are on the wrong box. Stop. A command that succeeded on the wrong box is not progress.

The draft stays a draft until a person has read the names in it. A generator does not log into the device and does not know which interface is the uplink. You delete a line that names a device, a zone, or a prefix you did not write down.

0.0.0.0/0 is not kept because a sample included it. A source you can say is the source you keep. 192.0.2.0/24, 198.51.100.0/24, 203.0.113.0/24, and 2001:db8::/32 are documentation. They belong in the note. They are not prefixes you type onto a production device because they appeared in a draft.

prompt-for-this is a reminder that a secret is missing. It is not a password, a key, a community string, or a pre-shared key you save in the ticket or in git. The real secret stays in the store.

One change is the window. A VLAN and a routing protocol and a VPN do not share it. If two things move and the result is wrong, you will not know which one did it. The next feature waits for its own page.

If the same step fails twice, stop for the day. The failure is the result. Adding a forum command beside a half-applied config produces a device nobody can rebuild. Restore the copy you took first.

A second person reads the device name and the change aloud. If they cannot find them in the ticket, the note is not done. Silence is not agreement. Then leave the device alone.

This page is a planning guide. It is not a vendor manual, not an official standard, and not a permission to touch a network you do not administer. The pillar guide owns the wider design. This page owns one lab proof.

Tools for this guide

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

More in this cluster

The pillar for this page, and the next published pages filed with it.