KNOWLEDGE CENTRE / SERVER CABINETS / BUYING GUIDE

How to Choose a Server Cabinet

A server cabinet needs to fit more than the server. Equipment depth, rack height, power, cabling, airflow and future expansion all need to be considered.

A server cabinet is part of the infrastructure, not simply a metal enclosure. The cabinet should be selected around the equipment that will occupy it and the way the rack will be maintained.

Practical example: planning a 42U equipment rack

42U rack planning example
42U rack planning exampleAlso verify cabinet depth, rails, airflow, PDU position and cable bend radius. TopPatching + switchesMiddleServersSpaceReserved growthBottomHeavy UPS Also verify cabinet depth, rails, airflow, PDU position and cable bend radius.

Also verify cabinet depth, rails, airflow, PDU position and cable bend radius.

Scenario: A rack will contain two servers, a UPS, two switches, patch panels, fibre termination and horizontal cable management.

Heavy equipment such as the UPS is positioned low. Patch panels and switches are arranged to keep patch leads short and serviceable. Space is reserved for growth rather than filling every rack unit immediately. Cabinet depth, rail requirements, PDU position, cable bend radius and front-to-rear airflow are checked before installation.

Decision: A rack plan is a physical infrastructure design, not just a list of U positions.

Common mistakes and selection checklist

Common mistakes

  • Buying a cabinet from rack-unit height alone without checking usable depth and rail requirements.
  • Placing heavy UPS equipment high in the rack or blocking front-to-rear server airflow.
  • Filling every rack unit and leaving no room for cable management or growth.

What happens if you get it wrong?

Equipment may physically not fit, rails may be unusable, servicing becomes difficult, and poor airflow can increase inlet temperatures or cause hot-air recirculation.

Selection checklist

  • Confirm equipment width, depth, rail type and rack-unit requirements.
  • Place heavy equipment low and preserve stable weight distribution.
  • Plan patch panels, switches, cable managers and PDUs before installation.
  • Maintain the intended front-to-rear airflow path and cover unused openings where appropriate.
  • Reserve realistic rack space and power capacity for growth.

Start with the equipment

List the rack-mounted equipment that needs to be installed. Servers, switches, patch panels, UPS equipment, PDUs and other components all consume physical space and affect the rack layout.

Consider rack height

Rack height is commonly expressed in rack units, or U. The available rack height needs to accommodate the equipment installed today while leaving sensible room for future additions.

Check equipment depth

Rack equipment is not all the same depth. The cabinet needs enough usable depth for the equipment, rails, cabling and any required rear clearance.

Plan airflow

Servers and networking equipment generate heat. The cabinet and its equipment layout should allow the intended airflow path to work correctly and should not unnecessarily obstruct equipment ventilation.

Plan power

Power distribution, UPS equipment and power cables need to be considered as part of the rack design. The physical arrangement should leave equipment accessible and cabling manageable.

Think about access

Maintenance becomes easier when the cabinet allows appropriate access to equipment, cabling and power connections. The installation environment should also provide enough space around the cabinet for the intended maintenance work.

  • Rack height required
  • Equipment depth
  • Rails and mounting hardware
  • Airflow and ventilation
  • Power distribution
  • Cable management
  • Physical access
  • Future expansion
Choose the cabinet around the complete rack.

A cabinet that fits the server but not the supporting infrastructure is not a complete rack solution.

Return to Server Cabinets

How to use this information

Confirm the exact product specification, supported configuration and compatibility before ordering. Platform generation, firmware, licences and optional components can change what a product supports.