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, and this page is available as Markdown at https://docs.ovhcloud.com/en/guides/bare-metal-cloud/dedicated-servers/private-boot.md.
Skip to content

Enable private boot on an OVHcloud dedicated server

View as Markdown

Find out how to boot a Dedicated Server in OLA Full private mode on your vRack, with no public IP or public PXE, from the OVHcloud Console or the API

Objective

By default, an OVHcloud Dedicated Server needs a public IPv4 address and the OVHcloud public PXE (Preboot Execution Environment) servers every time it boots. Private boot lets a server in OVHcloud Link Aggregation (OLA) Full private mode complete its whole boot sequence, from power-on to the iPXE script, on your vRack. The server keeps the same private IP address across reboots, with no static IP configuration in its operating system.

In this guide, you will learn how to:

  • check that private boot is available for your server.
  • enable private boot from the OVHcloud Console, including when your server has no vRack, vRack Services or subnet yet.
  • follow the configuration, and retry it if it fails.
  • modify or disable private boot.
  • enable private boot with the OVHcloud API.
  • use rescue mode or reinstall the server while private boot is in its first release.
Warning

In this first release, rescue mode and OS installation are not available over the private network. To use them, you must temporarily return the server to public boot. See the "Using rescue mode or reinstalling the server" section.

Requirements

You do not need a vRack, a vRack Services or a subnet before you start: the Console lets you order or create each missing resource from the private boot form.

Introduction

Private boot relies on vRack Services, the managed network layer of your vRack. Its DHCP service answers the boot requests that the server sends on its private interface, and gives it the private IP address bound to that interface. Private boot works on an IPv4 subnet without a VLAN (untagged traffic) only.


OVHcloud Console Access

  • Direct link:
  • Navigation path: Bare Metal Cloud > Dedicated servers > Select your server

Instructions

This section explains how private boot works, then walks you through each way of enabling it.

Contents:

How private boot works

When private boot is enabled, the server sends its boot requests (DHCP, then PXE and iPXE) on its private interface. The DHCP service of vRack Services answers them, and the server boots from the private network.

TermDescription
SubnetThe private IPv4 range the server boots into. It must have no VLAN.
Service rangeA block of the subnet, from /27 to /29, reserved for the services that OVHcloud manages, such as the DHCP server. Do not assign these addresses to your machines.
Server-IP associationThe binding between the server's private interface and its IP address in the subnet. Enabling private boot creates it, and deleting it disables private boot. See Manage Server-IP associations in vRack Services.

Checking that private boot is available

The Boot from private network card appears on the server's Connectivity tab only when private boot is available for your OVHcloud account and the server model supports it. If you do not see the card, private boot is not available for this server.

Warning

OLA Full private mode aggregates all the server's interfaces on the vRack and cuts its public Internet connectivity.

When the card is shown but the server is not in OLA Full private mode, the card displays Configure OLA in Full private mode first and its switch is unavailable. Click Configure OLA to aggregate the server's interfaces, as described in Configuring OVHcloud Link Aggregation (OLA). While the OLA change is running, the card shows Switching to OLA Full private, then private boot becomes available.

With the API, list the regions and availability zones where private boot is available. The netboot feature of each region is AVAILABLE, PARTIALLY_AVAILABLE (in some availability zones) or UNAVAILABLE:

Enabling private boot from the OVHcloud Console

  1. Open the Connectivity tab.

  2. In the Boot from private network card, turn on the switch. The form opens. Each field becomes available once the previous one is set.

  3. In the vRack field, select the vRack the server boots from. If the server is already attached to a vRack, that vRack is shown and cannot be changed. If your account has no vRack, click Order a vRack.

  4. In the vRack Service field, select the vRack Services of this vRack in the server's region. If there is none, click Order a vRack Service.

  5. In the Subnet field, select an IPv4 subnet without a VLAN. To use a new range, click Create new subnet. If the subnet has no service range yet, click Configure service range: the subnet page opens in a new tab. The service range is a small part of your subnet (from /27 to /29) that OVHcloud uses to address the services that must exist in your private network to work, such as Service Endpoints or the DHCP server.

  6. Check the Service range, shown once the subnet is selected.

  7. In the IP address field, complete the address the server will boot with. The subnet prefix is pre-filled: enter the last number. The address must meet the rules listed after this procedure.

  8. Check the Resulting path panel, which shows the server, vRack, vRack Services, subnet and IP address.

  9. Click Save and apply.

    If the server is not yet attached to the selected vRack, the Attach a vRack private network window opens. It states that the server's network interface will be attached to the vRack, and that the server will then boot from the subnet with the IP address you chose. Confirm to attach the server and apply the configuration.

When you order a vRack or a vRack Services, or create a subnet, from the form, its progress is shown under the field. The new resource is selected once it is ready.

The IP address must:

  • be a valid address of the subnet;
  • be outside the service range;
  • 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 assigned to another server.

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.

Following the configuration and handling a failure

While the configuration is applied, the card shows Applying private boot configuration… and its status is Pending. The fields are locked until the configuration is applied.

When it succeeds, the status turns Active and a notification confirms that private boot is enabled. The server boots from the private network at its next reboot.

If the configuration fails, the status turns Error and the card states the reason:

MessageWhat to do
The private network configuration could not be applied.Click Retry.
This vRack Service was changed in the meantime.Check the configuration, then click Retry.
This vRack Service is being updated.Wait until the vRack Services is ready, then click Save and apply.
This vRack Service is in error: its previous configuration stays active, but it cannot be changed until OVHcloud support steps in.Contact support.
The configuration could not be applied: this vRack Service went into error while applying it.Its previous configuration stays active, but it cannot be changed until OVHcloud support steps in. Contact support.

If the server was attached to the vRack before the failure, it stays attached, and the card says so. If the attachment is still running, the card asks you to click Save and apply again once it is done.

Modifying or disabling private boot

Once private boot is active, the card shows its configuration, and its switch can no longer be used directly: use Modify to change or disable private boot.

  • Modify: click Modify, change the vRack Services, subnet or IP address, then click Save and apply. The server uses the new configuration at its next reboot.
  • Disable: click Modify, turn off the switch, then click Save and apply. A warning states that the server will boot from the public network at its next reboot. The server's Server-IP association is deleted.

To cancel your changes, click Cancel.

The Connectivity tile of the Overview tab also shows a Private boot row, with an Enable or Disable link that opens the card.

Enabling private boot with the OVHcloud API

With the API, private boot is a configuration of the vRack Services: you add a Server-IP association for the server's interface to the DHCP configuration of a service range. The vRack Services, its IPv4 subnet without a VLAN, and its service range must already exist.

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. If the server is not yet attached to the vRack, attach its interface:

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

  3. Retrieve the checksum and the targetSpec of the vRack Services:

  4. Send the targetSpec back with the association added to the DHCP configuration of the service range, and the checksum you retrieved:

    {
      "checksum": "609cf69014e57abfb3d892133692ac6f",
      "targetSpec": {
        "subnets": [
          {
            "az": "eu-west-gra-a",
            "cidr": "10.0.0.0/24",
            "displayName": null,
            "vlan": null
          }
        ],
        "services": {
          "serviceRange": [
            {
              "cidr": "10.0.0.0/29",
              "subnetCidr": "10.0.0.0/24",
              "serviceEndpoints": [],
              "dhcp": {
                "dedicatedServerInterfaceAssociations": [
                  {
                    "uuid": "f3a6c9e2-0b7d-4c1e-9a58-2d4e6b8c0f13",
                    "ip": "10.0.0.10"
                  }
                ]
              }
            }
          ]
        }
      }
    }
    ParameterRequiredDescription
    checksumYesChecksum returned by the previous GET. The request is refused if the vRack Services changed in the meantime.
    services.serviceRange[].dhcp.dedicatedServerInterfaceAssociations[].uuidYesIdentifier of the server interface, noted in step 2.
    services.serviceRange[].dhcp.dedicatedServerInterfaceAssociations[].ipYesPrivate IP address of the server. It must be in the subnet, outside the service range and any BGP range, not the first or last address of the subnet, and unique in the subnet.

    Keep every other value of the targetSpec as returned by the GET. For the checksum and targetSpec mechanism, see vRack Services - Exposing a Managed Service on your vRack.

  5. Follow the update until the vRack Services is READY:

In the currentState of the vRack Services, the association shows "netboot": true once private boot is active. To disable private boot, send the targetSpec without the association.

Using rescue mode or reinstalling the server

In this first release, the rescue environment and the OS installation are still delivered over the public network. While the server is in OLA Full private mode, its boot mode cannot be changed: the Console displays "Cannot change boot mode: no public network interfaces are enabled on this server."

To boot the server in rescue mode or to reinstall it, temporarily return it to public boot:

Warning

From the OLA reset until OLA is back in Full private mode, the server is reachable on its public interface again. Plan this operation during a maintenance window.

  1. Note the subnet and IP address shown in the Boot from private network card, then disable private boot, as described in the "Modifying or disabling private boot" section. Disabling it deletes the server's Server-IP association.
  2. On the Connectivity tab, in the OVHcloud Link Aggregation (OLA) card, click Reset, then Confirm. While the reset runs, the Boot from private network card shows Resetting OLA to default mode.
  3. Run the operation: Rescue mode, then Reboot, or Reinstall.
  4. When the operation is complete, configure OLA in Full private mode again.
  5. Enable private boot again, as described in the "Enabling private boot from the OVHcloud Console" section. You can select the same subnet and IP address.

After a rescue boot, the network configuration of the operating system is unchanged. After a reinstallation, configure the link aggregation in the new operating system again, as described in Configuring OVHcloud Link Aggregation (OLA).

Warning

From the OLA reset until OLA is back in Full private mode, the server is reachable on its public interface again. Plan this operation during a maintenance window.

Private boot limitations

The first release of private boot has the following limitations.

LimitationDetails
Rescue mode and OS installationNot available over the private network. Return the server to public boot temporarily, as described in the "Using rescue mode or reinstalling the server" section.
OLA Full private onlyPrivate boot needs all the server's interfaces aggregated on the vRack.
IPv4 subnet without a VLANA subnet configured with a VLAN cannot be used for private boot.
Shared subnetA subnet used for private boot can only be shared between Dedicated Servers: a subnet already used by another service, such as a Service Endpoint, cannot be used.
Compatible servers and regionsHigh Grade Gen 2 or later, Scale Gen 2 or later, Advance Gen 3 or later, in a region where private boot is available. The card is not shown on other servers.
Subnet sizeA vRack Services subnet is a /23 or /24 IPv4 range. A vRack Services can host up to 3 subnets.
Address checksOVHcloud only checks the addresses it manages, not machines with a static IP address in your vRack.

Troubleshooting private boot

The table below lists the most common issues when you enable private boot.

IssuePossible causeSolution
The Boot from private network card does not appearThe server model does not support private boot, or private boot is not available for your accountCheck the availability of private boot.
The switch is unavailableThe server is not in OLA Full private mode, or private boot is already activeClick Configure OLA, or use Modify on an active private boot.
No subnet can be selectedThe vRack Services has no IPv4 subnet without a VLAN, or its subnet has no service rangeClick Create new subnet or Configure service range.
The configuration failsTemporary error, or the vRack Services changed or is in errorSee the "Following the configuration and handling a failure" section.
The server still boots on the public networkThe server has not rebooted since private boot was enabledReboot the server.
The server no longer boots from the private networkIts Server-IP association was deleted or modified in vRack ServicesCheck the association in vRack Services, as described in Manage Server-IP associations in vRack Services.

Go further

Manage Server-IP associations in vRack Services

Understanding link aggregation on dedicated servers

Configuring OVHcloud Link Aggregation (OLA)

Manage your server reboot with the OVHcloud Link Aggregation feature

How to activate and use rescue mode

vRack Services - Exposing a Managed Service on your vRack

Join our community of users.

Was this page helpful?