---
title: "Manage Server-IP associations in vRack Services"
description: "Find out how to bind a Dedicated Server's private interface to a persistent IP with vRack Services DHCP and netboot, from the OVHcloud Console or the API"
url: https://docs.ovhcloud.com/en/guides/network/vrack-services/server-ip-associations
lang: en
lastUpdated: 2026-11-20
---
> For AI agents: the complete documentation index is available at https://docs.ovhcloud.com/en/llms.txt, the full documentation bundle is available at https://docs.ovhcloud.com/en/llms-full.txt.

# Manage Server-IP associations in vRack Services

## Objective

A Server-IP association binds the private interface of a Dedicated Server to an IP address of a [vRack Services](https://docs.ovhcloud.com/en/guides/network/vrack-services/global.md) subnet. The DHCP and netboot service of vRack Services then gives the server the same address at every boot, and lets it boot from the private network. Associations are what [private boot](https://docs.ovhcloud.com/en/guides/bare-metal-cloud/dedicated-servers/private-boot.md) relies on: creating an association enables private boot on the server, and deleting it disables private boot.

**This guide explains how to create, modify and delete Server-IP associations, from the OVHcloud Console or with the OVHcloud API.**

**Warning:** Modifying or deleting the association of a server that boots from the private network changes the address it boots with, or makes it boot from the public network at its next reboot.

## Requirements

- A [vRack Services](https://docs.ovhcloud.com/en/guides/network/vrack-services/global.md) attached to a [vRack](https://www.ovhcloud.com/en-gb/network/vrack/), with an IPv4 subnet without a VLAN and a service range.
- A [Dedicated Server](https://www.ovhcloud.com/en-gb/bare-metal/) that supports [private boot](https://docs.ovhcloud.com/en/guides/bare-metal-cloud/dedicated-servers/private-boot.md), in the same region as the vRack Services, attached to its vRack, with OVHcloud Link Aggregation (OLA) enabled in **Full private** mode.
- Access to the "OVHcloud Console", or OVHcloud API credentials (see [First Steps with the OVHcloud APIs](https://docs.ovhcloud.com/en/guides/manage-and-operate/api/first-steps.md)).

**Tip:** To enable private boot on a single server, you can also start from its `Connectivity
` tab: the private boot form creates the association, and the vRack, vRack Services or subnet it needs. See [Enable private boot on an OVHcloud dedicated server](https://docs.ovhcloud.com/en/guides/bare-metal-cloud/dedicated-servers/private-boot.md)
.

***

### OVHcloud Console Access

- **Direct link:** "vRack Services"
- **Navigation path:** "Bare Metal Cloud" > "vRack Services"

***

## Instructions

This section lists the rules an association address must follow, then explains how to manage associations from the Console or the API.

### IP address rules

The IP address of an association must:

- be an IPv4 address of the subnet;
- be outside the service range, which is reserved for the services that OVHcloud manages;
- be outside the BGP range of the subnet, if it has one;
- not be the first or last address of the subnet, which are reserved;
- not be already used by another association.

Each server can have only one association. OVHcloud only checks the addresses it manages: make sure no other machine in your vRack already uses the address, for example a machine with a static IP address.

### Managing associations

#### OVHcloud Console

Select your vRack Services.
Open the "Subnets" tab and click the subnet. Its page shows the **DHCP & Netboot (Server-IP Association)** card, which lists each association with its **Server name** and **IP address**.
You cannot add an association while the subnet has no service range, is tagged with a VLAN, or belongs to a vRack Services that is not attached to a vRack: the card says which condition is missing. Actions are also unavailable while the vRack Services is being updated.
**Create an association**
1. Click "Add a Server-IP Association". The **Create a Server-IP Association** panel opens, with the **Subnet** shown.
2. In the **Associated server** field, select the server. The list only shows the servers in the same region as the vRack Services, attached to its vRack, in OLA **Full private** mode, and with no association yet.
3. In the **Associated IP address** field, enter the server's IP address.
4. Click "Add a Server-IP Association".

The server boots from the private network, with this address, at its next reboot.
**Modify an association**
1. In the list, open the actions menu of the association, then click "Modify".
2. In the **Modify Server-IP Association** panel, enter the new IP address. The server cannot be changed.
3. Click "Modify".

The server uses the new address at its next reboot.
**Delete an association**
1. In the list, open the actions menu of the association, then click "Delete".
2. In the **Delete Server-IP Association** window, click "Delete".

The IP address is released, and private boot is disabled on the server: it boots from the public network at its next reboot.

#### OVHcloud API

Associations are part of the vRack Services configuration: each one is an entry of `dedicatedServerInterfaceAssociations`, in the DHCP configuration of the subnet's service range.

**Warning:** The `dhcp` block of a service range and the `az` field of a subnet only exist from revision 2026-06 of the OVHcloud API v2. If your account still uses revision 2025-01, send the `X-Schemas-Version: 2026-06` header with the `GET` and `PUT` calls below: a `PUT` in revision 2025-01 cannot carry the `dhcp` block, and omitting it removes the DHCP configuration of the service range, which stops private boot for every server bound to it.

1. List the server interfaces that can be associated with the vRack Services. Note the `uuid` of the server's interface:

   `GET /vrackServices/resource/{vrackServicesId}/eligibleDedicatedServerInterfaces`

2. Retrieve the `checksum` and the `targetSpec` of the vRack Services:

   `GET /vrackServices/resource/{vrackServicesId}`

3. Send the `targetSpec` back with your change to `services.serviceRange[].dhcp.dedicatedServerInterfaceAssociations`, and the `checksum` you retrieved:

   `PUT /vrackServices/resource/{vrackServicesId}`

   | Action                | Change in `dedicatedServerInterfaceAssociations`                   |
   | --------------------- | ------------------------------------------------------------------ |
   | Create an association | Add an entry `{"uuid": "<interface uuid>", "ip": "<IP address>"}`. |
   | Modify an association | Change the `ip` of the entry.                                      |
   | Delete an association | Remove the entry.                                                  |

   Keep every other value of the `targetSpec` as returned by the `GET`. A complete request body is shown in the "[Enabling private boot with the OVHcloud API](https://docs.ovhcloud.com/en/guides/bare-metal-cloud/dedicated-servers/private-boot.md#api)" section of the "Enable private boot on an OVHcloud dedicated server" guide, and the `checksum` and `targetSpec` mechanism in the "[vRack Services - Exposing a Managed Service on your vRack](https://docs.ovhcloud.com/en/guides/network/vrack-services/global.md)" guide.

4. Follow the update until the vRack Services is `READY`:

   `GET /vrackServices/resource/{vrackServicesId}`
In the `currentState` of the vRack Services, each association shows whether netboot is active (`netboot`). The `dhcpConfigurationStatus` of the service range is `READY`, or `DRAFT` with the reason `MISSING_DEDICATED_SERVER_INTERFACE_ASSOCIATIONS` when its DHCP configuration has no association.

## Go further

[Enable private boot on an OVHcloud dedicated server](https://docs.ovhcloud.com/en/guides/bare-metal-cloud/dedicated-servers/private-boot.md)

[vRack Services - Exposing a Managed Service on your vRack](https://docs.ovhcloud.com/en/guides/network/vrack-services/global.md)

For training or technical assistance implementing our solutions, contact your sales representative or visit our [Professional Services](https://www.ovhcloud.com/en-gb/professional-services/) page to request a quote and have your project analysed by our experts.

Join our [community of users](https://community.ovhcloud.com/).
