---
title: "How to Create a VLAN"
description: "OVHcloud sets up a base of 11 VLANs on your vRack."
url: https://docs.us.ovhcloud.com/en/hosted-private-cloud/vmware/create-vlan
lang: en
---
> For AI agents: the complete documentation index is available at https://docs.us.ovhcloud.com/en/llms.txt, the full documentation bundle is available at https://docs.us.ovhcloud.com/en/llms-full.txt.

# How to Create a VLAN

OVHcloud sets up a base of 11 VLANs on your vRack.

**This guide explains how to create additional VLANs.**

## Requirements

- Being an administrative contact of your [Hosted Private Cloud infrastructure](https://us.ovhcloud.com/hosted-private-cloud/vmware/) to receive login credentials
- A user account with access to vSphere as well as the specific rights for Networking (created in the [OVHcloud Control Panel](https://manager.us.ovhcloud.com/#/hub))

## Instructions

In the Hosted Private Cloud solutions, VLANs can be used to isolate private communications between different OVHcloud services that are vRack-compatible (Dedicated Server, Public Cloud instance, etc.).

First, go to your vSphere client's `Networking` view. Deploy the **vrack** folder then `right-click` on the **dVS** ending in _-vrack_ and finally click on `New Distributed Port Group`.

 

Choose a name for your **Port Group**, then click `NEXT`.

 

Then configure the settings recommended by OVHcloud:

- **Port binding**: Static (reserving and assigning the port to a virtual machine)
- **Port allocation**: Elastic (allows the number of ports to be hot-wired)
- **Number of ports**: 24
- **VLAN type**: VLAN (the others are [PVLAN](https://kb.vmware.com/s/article/1010691) and Trunk)
- **VLAN ID**: 21 (knowing that the ID can be configured from 1 to 4096)
- Check the option _Customize default policies configuration_.

When you have made your selections, click `NEXT`.

You have three security settings that can be activated according to your needs:

- _Promiscuous mode_: eliminates any filtering that the VM adapter can perform so that the guest operating system receives all observed traffic on the network.
- _MAC address changes_: when set to **Accept**, ESXi will accept requests to change the effective MAC address to an address other than the initial MAC address.
- _Forged transmits_: affects traffic transmitted from a virtual machine. When set to **Accept**, ESXi does not compare the source and effective MAC addresses.

When you have made your selections, click `NEXT`.

**Note:**

**NOTE: **The most frequent use of these three parameters is the CARP, especially used on **pfSense**.

 

Leave [Traffic shaping](https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.networking.doc/GUID-CF01515C-8525-4424-92B5-A982489BACE2.html) disabled, then click `NEXT`.

 

In terms of load balancing, select _Route Based on IP hash_, which is the best method for redundancy and load balancing.

**Warning:**

**NOTE: **Be careful when configuring the failover order: It is necessary to set the `lag1` uplink to _Active_ (connection between the virtual network and the physical network), otherwise no communication between the hosts will be possible.

When you have made your selections, click `NEXT`.

 

Set `NetFlow` to disabled (traffic flow activity report), then click `NEXT`.

 

Leave the `Block All Ports` value at "No" and click `NEXT`.

 

You will then be presented with a summary of the changes. Click `FINISH` to confirm the creation.

 

Here we can see that **VLAN21** is available and functional.

 

## Go further

Browse all the [VMware on OVHcloud guides](https://docs.us.ovhcloud.com/en/hosted-private-cloud/vmware/landing-page-vmware.md).

Browse the rest of the [OVHcloud US documentation](https://docs.us.ovhcloud.com/en/index.md) for guides on our other products and services.

Learn more about [VMware on OVHcloud](https://us.ovhcloud.com/hosted-private-cloud/vmware/) on the OVHcloud US website.