Configuring the network on ESXi on the High Grade & SCALE ranges

Find out how to configure the network on VMware ESXi on the High Grade & SCALE ranges

Last updated 9th May 2022


On the High Grade & SCALE ranges, it is not possible to manage Additional IPs in bridged mode (via virtual MACs). It is therefore necessary to configure Additional IPs in routed mode or via the vRack.

To date, the documentation only covers the solution via the vRack.

This guide explains how to configure the network on VMware ESXi.



On these server ranges, there are 4 network cards. To get all the bandwidth, aggregates must be created. Our documentation is based on these card aggregates.

However, ESXi does not support LACP natively. Therefore, no redundancy will be available. You will also be unable to use all of your server’s network cards’ bandwidth.

There's currently a known issue with the ESXi graphical user interface and performing these steps in the interface will result in a non-working configuration. It is absolutely necessary to apply this configuration using the command line interface in SSH.

Additional IP via vRack

First, add your public block of IP addresses to the vRack. To do so, go to the Bare Metal Cloud section of your OVHcloud Control Panel and open the vRack menu.

Select your vRack from the list to display the list of eligible services. Click on the IP block you want to add to the vRack and then click the Add button.

Original configuration

esxi diagram

In this example:

  • the public interfaces are vmnic2 and vmnic3;
  • the private interfaces are on vmnic0 and vmnic1.

A first vSwitch exists but only has a vmnic2 interface.

Check that your configuration is similar. You can access information on MACs and public or private interfaces in your OVHcloud Control Panel or via the OVHcloud API.


You need to:

  • create the aggregate on the public vSwitch
  • create the vSwitch for the vRack
  • create a port group
  • create VMs using the new port group as the network interface.

Configure ESXi

You will need to follow the next steps in command mode (shell) instead of the ESXi GUI.

Creating the aggregate in LACP mode on the vSwitch that carries the public interfaces
[root@localhost:~] esxcli network vswitch standard uplink add --uplink-name=vmnic3 --vswitch-name=vSwitch0
[root@localhost:~] esxcli network vswitch standard policy failover set -l iphash -v vSwitch0


esxi diagram

Creating vSwitch and vRack aggregation on private interfaces
[root@localhost:~] esxcli network vswitch standard add --vswitch-name=vRackvSwitch
[root@localhost:~] esxcli network vswitch standard uplink add --uplink-name=vmnic0 --vswitch-name=vRackvSwitch
[root@localhost:~] esxcli network vswitch standard uplink add --uplink-name=vmnic1 --vswitch-name=vRackvSwitch
[root@localhost:~] esxcli network vswitch standard policy failover set -l iphash -v vRackvSwitch


esxi diagram

VM configuration

The VMs must have the new portgroupvRackvSwitch port group in the network interface.

esxi diagram

Creating a port group for the new “vRackvSwitch” vSwitch
[root@localhost:~] esxcli network vswitch standard portgroup add --portgroup-name=portgroupvRackvSwitch --vswitch-name=vRackvSwitch

Configure a usable IP address

In the case of vRack, the first address and the last two addresses in a given IP block are always reserved for the network address, its gateway and its broadcast address respectively. This means that the first usable address is the second address in the block, as shown below: # Reserved: network address # First usable IP # Last usable IP # Reserved: network gateway # Reserved: network broadcast

To configure the first usable IP address, you must edit the network configuration file as shown below. In this example, we use a subnet mask of

The subnet mask used in this example is appropriate for our IP block. Your subnet mask may differ depending on the size of your block. When you purchase your IP block, you will receive an email notifying you of the subnet mask to use.

Configuration example of a client VM on Debian

Content of the file /etc/network/interfaces:

auto lo ens18
iface lo inet loopback
iface ens18 inet static

Go further

Join our community of users on

Did you find this guide useful?

Please feel free to give any suggestions in order to improve this documentation.

Whether your feedback is about images, content, or structure, please share it, so that we can improve it together.

Your support requests will not be processed via this form. To do this, please use the "Create a ticket" form.

Thank you. Your feedback has been received.

These guides might also interest you...

OVHcloud Community

Access your community space. Ask questions, search for information, post content, and interact with other OVHcloud Community members.

Discuss with the OVHcloud community

In accordance with the 2006/112/CE Directive, modified on 01/01/2015, prices incl. VAT may vary according to the customer's country of residence
(by default, the prices displayed are inclusive of the UK VAT in force).