Skip to main content

Configuring the Network on Windows Server with Hyper-V on the ADVANCE Gen 3 Servers

Stephanie R.
Updated

Learn how to configure the network in Windows Server with Hyper-V.

ADVANCE Gen 3 servers can be configured via vRack (through the use of Additional IPs) or via virtual MACs. If you plan on using virtual MAC addresses, please follow this guide.

 

Requirements

NOTE: No virtual MACs should be applied to additional IPs in the OVHcloud Control Panel.
NOTE: The limit on public bandwidth capacity in every location is set to 5Gbps (egress, per region, per vRack network).

 

Contents

Step 1: Add the server and Additional IP to a vRack
Step 2: Installing the Hyper-V and RRAS roles
Step 3: Create the virtual switch in Hyper-V Manager
Step 4: Configure your VM

 

Instructions

Step 1: Add the server and Additional IP to a vRack

You can add your server and Additional IP block to a vRack using the OVHcloud Control Panel. Use the following links to see how:

 

Step 2: Installing the Hyper-V and RRAS roles

Go to the Server Manager and open the Dashboard, then click on Add roles and features.

hypervscale7.png

Go through the Wizard until you reach the Server Roles section and select Hyper-V and Remote Access.

hypervscale8.png

Next, proceed to the Virtual Switches subsection of Hyper-V and select the adapter of the private interface of the server.

You can find this adapter by opening up cmd and using the ipconfig command. The result you need should have a 169.x... address or will not be tied to the server's public IP.

DS_network_hyperVadvanced01**.jpeg

DS_network_hyperVadvanced02**.PNG

Next, proceed to the Role Services subsection of Remote Access and select Routing.

hypervscale10.png

Finally, proceed to the Confirmation section, select Restart the destination server automatically if required, and click Install.

 

Step 3: Create the virtual switch in Hyper-V Manager

We will need to create a virtual switch for the VMs.

First, open the Hyper-V Manager and click on Virtual Switch Manager.

hypervscale22.png

On this page, make sure you have External selected and click Create Virtual Switch.

hypervscale23.png

Now, give your switch a name, choose your network adapter, then click Apply and then OK.

hypervscale24.png

You are now ready to create your VM and configure its network.

 

Step 4: Configure your VM

Once you create your VM, go to the settings, select Network Adapter from the left-hand menu, and click Advanced Features.

Set the MAC address to Static and enter the MAC address of the virtual switch.

DS_confignetwork_windows_hyper-v_scale-hg05.png

Set the Static IP address inside your VM to the Additional IP address.

DS_confignetwork_windows_hyper-v_scale-hg06*.png

Your VM should now have internet access.

DS_confignetwork_windows_hyper-v_scale-hg07.png

 

Configure a usable IP address

For vRack, the first, penultimate, and last addresses in a given IP block are always reserved for the network address, network gateway, and network broadcast respectively. This means that the first usable address is the second address in the block, as shown below:

51.81.3.240 # Reserved: network address
51.81.3.241 # First usable IP
51.81.3.242
51.81.3.243
51.81.3.244
51.81.3.245 # Last usable IP
51.81.3.246 # Reserved: network/default gateway
51.81.3.247 # 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 255.255.255.248.

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.

 

Windows-19 VM network configuration

In this example, enter one of the usable IP addresses in your block as the IP address and the second to last IP in your block as the Default gateway.

DS_confignetwork_windows_hyper-v_scale-hg04.png

 

Configuration example of a client VM on Ubuntu

Create a vrack.yaml file under /etc/netplan/vrack.yaml.

Content of the file /etc/netplan/vrack.yaml:

network:
        version: 2
        ethernets:
                eth0:
                        dhcp4: no
                        addresses:
                                - 192.xxx.xxx.16/32
                        nameservers:
                                addresses:
                                        - 213.186.33.99
                                        - 8.8.8.8
                        routes:
                                - to: 0.0.0.0/0
                                  via: 100.64.0.1
                                  on-link: true

For the netplan configuration changes to take effect, you must reboot the VM or run this command:

sudo netplan apply

 

Go further

For more information and tutorials, please see our other Dedicated Servers support guides or explore the guides for other OVHcloud products and services.

Related articles