Data centre
Server rack
A server rack is equipment in the data centre category. Racks and their contents identified to a documented scheme so a cable can be traced end to end.
Also called: cabinet, 19 inch rack, equipment rack, data rack.
Governing standards
Required artifacts
| Artifact | What it does |
|---|---|
| Service label | A service label is a compliance consumable applied directly to equipment recording a test, a certification, or a next-due date. |
| Asset tag | A durable serialized tag bound to one physical asset for inventory, audit, and inspection history. |
| Engraved nameplate | A rigid engraved plate identifying equipment, a circuit, or a disconnect, readable for the life of the asset. |
Which of these you actually need, and on what cycle, depends on your jurisdiction. We publish that only where we have read the governing clause and can cite it. Where we have not, the page says so rather than guessing.
In stock for server racks
What it is
A nineteen inch cabinet holding servers, switches and PDUs, with front and rear doors, in a room with controlled airflow. Identified by row and position rather than by anything printed on the equipment.
Why it gets inspected
The failure mode is not equipment, it is identity. A rack whose labels have drifted from the asset system means an engineer takes down the wrong machine at two in the morning, and the outage is now twice as long and twice as embarrassing.
What happens on a visit
Audit rather than inspect: walk the rack, scan or read every identifier, reconcile against the asset system, and remove labels for equipment that left. The removal is the part everyone skips.
What drives the tag count
Identifiers have to match the documentation exactly. A rack label that disagrees with the drawing is worse than no label because it sends someone to the wrong cabinet with confidence. Print to the scheme already in the as-builts rather than inventing one at labelling time.
What actually gets tagged, and where it goes
Racks are identified at the rack, and then ports and panels are identified individually within it, so a single rack generates a large number of small labels. Panel and port labels are removed and reapplied at every change, which means an adhesive aggressive enough to survive years is the wrong specification: it damages the panel face when a port is reassigned. Specify removable adhesive on anything that gets re-terminated and permanent only on the rack identifier itself.
What a scan of server racks shows
Structured cabling documentation is accurate on installation day and decays with every subsequent change, because the label is created immediately and the record is updated later, if at all. Binding the identifier to a record at the point the label is produced closes the largest source of that drift. A scan resolves to what the identifier was assigned to and when, which is the correspondence the administration standard is actually about.
Every artifact here is serialised, so the record survives the tag being replaced. The mechanics are on how inspection records work.
Sizing an order for a fleet of server racks
Size from the port count rather than the rack count, which typically multiplies the order by a factor of twenty or more. Order rack identifiers, panel labels and port labels together since they share a scheme, and order generously: running out mid-installation is what produces the handwritten label that never gets replaced and never makes it into the documentation.
Minimum is 100 units and every price is on the page, so a first order can be a test rather than a commitment. Why the minimum is 100, not 2,500.
Inspected on the same visit
A rack, the cables terminating in it and the assets mounted inside it are one identification scheme rather than three. Labelling them in separate exercises is what produces a rack whose ports, cables and equipment use three incompatible conventions. Rack power distribution also ties this to the electrical labelling programme. Order the whole scheme at once so identifiers are contiguous, and size from port and asset counts rather than from rack count, which understates the quantity by an order of magnitude.
Ordering server racks: common questions
How do I size an order for a data room?
From the port count, not the rack count, which typically multiplies the order by twenty or more. Order rack identifiers, panel labels and port labels together since they share a scheme, and order generously: running out mid-installation produces the handwritten label that never gets replaced.
Permanent or removable adhesive?
Removable on anything that gets re-terminated, permanent only on the rack identifier itself. An adhesive aggressive enough to survive years is one that damages the panel face when a port is reassigned, which is a real cost on equipment that gets changed constantly.
Does this replace our cable management database?
No, and for a large installation it should not. It provides a durable link between the physical identifier and a record of what it was assigned to and when. Most sites keep their existing system and use the serialised identifier as the physical anchor into it.