Skip to content

Commit 077618b

Browse files
committed
feat(win): update documentation for win 2022
1 parent 038be81 commit 077618b

File tree

1 file changed

+47
-6
lines changed

1 file changed

+47
-6
lines changed

pages/elastic-metal/how-to/use-private-networks.mdx

Lines changed: 47 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -155,17 +155,58 @@ You must configure the virtual network interface on each Elastic Metal server yo
155155
<Message type="important">
156156
Two network interfaces display: Your VLAN and `default`. Make sure to keep the default network, otherwise you will lose access to your server via the public internet.
157157
</Message>
158-
7. Click **Start** > **Execute** and type `ncpa.cpl`. Then click **OK** to open the network connection manager.
159-
8. Click on your VLAN network connection and right-click on it to open the menu. Click **Properties** to display the connection properties.
160-
9. Select **Internet Protocol version 4 (TCP/IPv4)** and click **Properties**. A pop-up displays.
161-
10. Click **Use the following IP address** and configure the IPv4 configuration of your Private Network. Then click **OK** to save your configuration.
162-
11. Click **Close** to close the network interface properties.
163158

164-
You completed the configuration of your Private Network on Windows Server 2019.
159+
### Static IP configuration (optional)
160+
161+
<Message type="important">
162+
If you are running multiple virtual machines on an Elastic Metal server, our managed DHCP is not currently able to distribute IP addresses to your virtual machines. We recommend that you use the [IPAM API](https://www.scaleway.com/en/developers/api/ipam/) to book IP addresses for your virtual machines, and assign them manually.
163+
</Message>
164+
165+
1. Click **Start** > **Run** and type `ncpa.cpl`. Then click **OK** to open the network connection manager.
166+
2. Click on your VLAN network connection and right-click on it to open the menu. Click **Properties** to display the connection properties.
167+
3. Select **Internet Protocol version 4 (TCP/IPv4)** and click **Properties**. A pop-up displays.
168+
4. Click **Use the following IP address** and configure the IPv4 configuration of your Private Network. Then click **OK** to save your configuration.
169+
5. Click **Close** to close the network interface properties.
170+
165171
<Message type="tip">
166172
You can use the `ipconfig` command to verify your IP configuration from a command prompt.
167173
</Message>
168174

175+
### Additional configuration for virtual machines running on Hyper-V
176+
177+
If you are running virtual machines with Hyper-V, refer to the Microsoft documentation regarding [Hyper-V and VLANs](https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/deploy/configure-virtual-local-area-networks-for-hyper-v).
178+
179+
<Message type="note">
180+
Since Windows Server 2022, the procedure differs from Windows 2019. LBFO (a Hyper-V switch related to NIC teaming) has been deprecated and replaced by SET (Switch Embedded Teaming).
181+
This change may introduce limitations regarding VLAN assignment for multiple VMs on clusters of Elastic Metal servers.
182+
</Message>
183+
184+
Below is an example of how to connect one Private Network to a virtual machine created by Hyper-V on a Windows Server 2022 host (the Elastic Metal server's operating system).
185+
186+
1. Open a PowerShell terminal and run the following command:
187+
```powershell
188+
Get-NetAdapter
189+
```
190+
<Message type="important">
191+
Do not enable NIC Teaming on the host.
192+
</Message>
193+
This command will display the network interface names. Copy the name of the interface that is "Up".
194+
195+
2. Create a new VMSwitch:
196+
```powershell
197+
New-VMSwitch -Name "SET Team" -NetAdapterName "<NAME OF THE NETWORK INTERFACE>" -EnableEmbeddedTeaming $true
198+
```
199+
200+
3. Create a "custom" resource in the [Private Network](/vpc/how-to/attach-resources-to-pn/).
201+
202+
4. When creating the VM, select the SET switch in the networking creation menu.
203+
204+
5. Copy the MAC address of the VM from the **Network adapter** section of the VM settings, under the **Advanced features** subsection.
205+
206+
6. Change the Virtual Machine settings:
207+
- Go to the "Network adapter" section of the VM in Hyper-V.
208+
- Set the VLAN ID (copy it from the **Private Network** menu in the Elastic Metal server console).
209+
169210
## How to delete a Private Network
170211

171212
<Message type="note">

0 commit comments

Comments
 (0)