US Liquid Cooling editorial · Reviewed · 3 min read
A liquid-cooled server does not become a complete cooling installation when its hoses are connected. The server needs coolant delivered under suitable conditions, and the heat it produces needs somewhere to go.
A coolant distribution unit, usually shortened to CDU, sits at that interface. Thinking of it as a box of pumps misses the role it plays in connecting IT equipment to a wider cooling system.
Two circuits, one heat-transfer point
In a typical liquid-to-liquid arrangement, a CDU transfers heat between the technology cooling circuit and a facility circuit through a heat exchanger. The fluids remain separate. That separation allows the IT side to be managed for the requirements of its equipment rather than simply exposing it to facility-water conditions.
Vertiv's integration white paper distinguishes the technology cooling system from the facility water system and explicitly describes this separation. The exact boundary and responsibilities should also appear in your project drawings.
What is inside the unit?
Depending on the product, a CDU can combine pumps, a heat exchanger, filtration, instrumentation, and controls. Available features and redundancy arrangements vary. Check the actual model documentation rather than assuming every CDU includes the same protection or control functions.
Useful questions include what is measured locally, what alarms are available, which signals reach the building management system, and how a technician can isolate equipment for service.
The point of that checklist is practical: an alarm that nobody receives is different from an alarm that reliably triggers an operating procedure.
Liquid-to-liquid and liquid-to-air
A liquid-to-liquid unit transfers heat into another fluid circuit. A liquid-to-air unit transfers heat into air, which can be useful where a suitable facility-water connection is unavailable. The latter still adds heat that the surrounding facility must remove.
Vertiv offers products using both architectures. Their existence does not mean they are interchangeable. Identify the intended heat destination before comparing products on capacity or footprint.
Why the kW number needs context
A headline capacity belongs to specified operating conditions. Ask for the temperatures, flow requirements, fluid properties, and approach conditions behind the rating. Then ask whether those conditions match the servers and facility you actually plan to operate.
For example, two quotations might describe units with similar nominal capacity while assuming different facility supply temperatures. Without those assumptions, the purchasing team is comparing labels rather than usable performance.
Get a supported operating envelope and a clear explanation of what changes when conditions move away from the quoted point. Do not fill in missing design assumptions yourself.
Agree on the service boundary
Who supplies the coolant? Who maintains filters? Who responds to a pump alarm? Who owns the connection between the rack and the CDU? Put names or contract roles beside each responsibility before commissioning.
Include the planned behavior during power loss, maintenance, and a single-component fault. Ask the supplier to show how the redundancy arrangement supports the required operating condition, not merely that a spare pump is installed.
What to send a supplier
Provide the supported server configuration, expected load, required coolant conditions, facility cooling information, space constraints, and availability objective. Ask for a marked-up interface diagram with the proposal.
A useful CDU specification begins with the equipment on both sides of the unit. Once those interfaces are clear, its capacity, layout, controls, and service plan become much easier to assess.
Sources & further reading
Explore the company directory → · All liquid-cooling guides →