Skip to content

Commit 437ee28

Browse files
Y0CossY0Coss
authored
Merge pull request #7604 from ovh/ds-vcd-post-migration-COPY
ds-vcd-post-migration-COPY
2 parents 39a9135 + ef7d51a commit 437ee28

21 files changed

+1024
-0
lines changed

‎links/hosted-private-cloud/vmware-vcd

Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,16 @@
1+
- [de-de](https://www.ovhcloud.com/de/lp/vmware-vcd-evolution/)
2+
- [en-asia](https://www.ovhcloud.com/asia/lp/vmware-vcd-evolution/)
3+
- [en-au](https://www.ovhcloud.com/en-au/lp/vmware-vcd-evolution/)
4+
- [en-ca](https://www.ovhcloud.com/en-ca/lp/vmware-vcd-evolution/)
5+
- [en-gb](https://www.ovhcloud.com/en-gb/lp/vmware-vcd-evolution/)
6+
- [en-ie](https://www.ovhcloud.com/en-ie/lp/vmware-vcd-evolution/)
7+
- [en-in](https://www.ovhcloud.com/en-in/lp/vmware-vcd-evolution/)
8+
- [en-sg](https://www.ovhcloud.com/en-sg/lp/vmware-vcd-evolution/)
9+
- [en-us](https://www.ovhcloud.com/en/lp/vmware-vcd-evolution/)
10+
- [es-es](https://www.ovhcloud.com/es-es/lp/vmware-vcd-evolution/)
11+
- [es-us](https://www.ovhcloud.com/es/lp/vmware-vcd-evolution/)
12+
- [fr-ca](https://www.ovhcloud.com/fr-ca/lp/vmware-vcd-evolution/)
13+
- [fr-fr](https://www.ovhcloud.com/fr/lp/vmware-vcd-evolution/)
14+
- [it-it](https://www.ovhcloud.com/it/lp/vmware-vcd-evolution/)
15+
- [pl-pl](https://www.ovhcloud.com/pl/lp/vmware-vcd-evolution/)
16+
- [pt-pt](https://www.ovhcloud.com/pt/lp/vmware-vcd-evolution/)

‎pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd_post_migration/guide.de-de.md

Lines changed: 67 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,67 @@
1+
---
2+
title: "VMware Cloud Director - Setting up your network after vSphere to VCD migration"
3+
excerpt: "Learn how to configure your network after migrating from VMware vSphere to VMware Cloud Director"
4+
updated: 2025-03-04
5+
---
6+
7+
## Objective
8+
9+
This guide explains the necessary steps to configure your environment after migrating from your managed **VMware vSphere on OVHcloud** services to a managed **VMware Cloud Director on OVHcloud** solution.
10+
11+
These modifications are essential to ensure the proper functioning of your virtual machines and networks.
12+
13+
## Requirements
14+
15+
- A [VMware Cloud Director](/links/hosted-private-cloud/vmware-vcd) on OVHcloud solution.
16+
- Being the technical administrator of the managed [VMware vSphere on OVHcloud](/links/hosted-private-cloud/vmware) infrastructure.
17+
- Access to the [OVHcloud Control Panel](/links/manager)
18+
19+
## Instructions
20+
21+
### Step 1: Update virtual machine network settings
22+
23+
After migration, you need to update the network configurations of your `virtual machines (VMs)`.
24+
25+
To set the network configuration to DHCP (**recommended**):
26+
27+
1\. Go to the network settings of each VM.
28+
2\. Change the IP assignment mode to `DHCP`{.action}.
29+
30+
![DHCP setting](images/01-VCD-post-migration.png){.thumbnail}
31+
32+
3\. Make sure the `Guest customization settings`{.action} are set to `Disabled` before modifying the NIC settings.
33+
34+
![Disabled setting](images/02-VCD-post-migration.png){.thumbnail}
35+
36+
### Step 2: Handling the IP addressing bug in VCD
37+
38+
Networks are pre-created with placeholder Gateway CIDRs, as the actual VM subnets are unknown beforehand.
39+
40+
This can lead to IP assignment issues if not addressed post-migration.
41+
42+
#### **Identified issue**
43+
44+
- If a static IP is manually assigned to a VM and does not match the pre-configured `Gateway CIDR`, the assignment will fail.
45+
- You will not be able to create or update a VM with manual IP assignment outside the predefined `Gateway CIDR`.
46+
47+
#### **Solutions**
48+
49+
1\. **Use DHCP mode (recommended)**
50+
51+
- Setting all IP modes to `DHCP` works seamlessly, even if the OS is configured with a static IP.
52+
- This approach is valid for both isolated networks and `VM Networks`*.
53+
54+
![DHCP mode](images/03-VCD-post-migration.png){.thumbnail}
55+
56+
2\. **Create a new network**
57+
58+
- Customers can create a new `network` with the correct subnet.
59+
- This solution works only if the customer has **a single** public IP range.
60+
61+
## Go further
62+
63+
If you need training or technical assistance to implement our solutions, please contact your Technical Account Manager or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for a custom analysis of your project.
64+
65+
Ask questions, give your feedback and interact directly with the team building our Hosted Private Cloud services on the dedicated [Discord](https://discord.gg/ovhcloud) channel.
66+
67+
Join our [community of users](/links/community).

‎pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd_post_migration/guide.en-asia.md

Lines changed: 67 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,67 @@
1+
---
2+
title: "VMware Cloud Director - Setting up your network after vSphere to VCD migration"
3+
excerpt: "Learn how to configure your network after migrating from VMware vSphere to VMware Cloud Director"
4+
updated: 2025-03-04
5+
---
6+
7+
## Objective
8+
9+
This guide explains the necessary steps to configure your environment after migrating from your managed **VMware vSphere on OVHcloud** services to a managed **VMware Cloud Director on OVHcloud** solution.
10+
11+
These modifications are essential to ensure the proper functioning of your virtual machines and networks.
12+
13+
## Requirements
14+
15+
- A [VMware Cloud Director](/links/hosted-private-cloud/vmware-vcd) on OVHcloud solution.
16+
- Being the technical administrator of the managed [VMware vSphere on OVHcloud](/links/hosted-private-cloud/vmware) infrastructure.
17+
- Access to the [OVHcloud Control Panel](/links/manager)
18+
19+
## Instructions
20+
21+
### Step 1: Update virtual machine network settings
22+
23+
After migration, you need to update the network configurations of your `virtual machines (VMs)`.
24+
25+
To set the network configuration to DHCP (**recommended**):
26+
27+
1\. Go to the network settings of each VM.
28+
2\. Change the IP assignment mode to `DHCP`{.action}.
29+
30+
![DHCP setting](images/01-VCD-post-migration.png){.thumbnail}
31+
32+
3\. Make sure the `Guest customization settings`{.action} are set to `Disabled` before modifying the NIC settings.
33+
34+
![Disabled setting](images/02-VCD-post-migration.png){.thumbnail}
35+
36+
### Step 2: Handling the IP addressing bug in VCD
37+
38+
Networks are pre-created with placeholder Gateway CIDRs, as the actual VM subnets are unknown beforehand.
39+
40+
This can lead to IP assignment issues if not addressed post-migration.
41+
42+
#### **Identified issue**
43+
44+
- If a static IP is manually assigned to a VM and does not match the pre-configured `Gateway CIDR`, the assignment will fail.
45+
- You will not be able to create or update a VM with manual IP assignment outside the predefined `Gateway CIDR`.
46+
47+
#### **Solutions**
48+
49+
1\. **Use DHCP mode (recommended)**
50+
51+
- Setting all IP modes to `DHCP` works seamlessly, even if the OS is configured with a static IP.
52+
- This approach is valid for both isolated networks and `VM Networks`*.
53+
54+
![DHCP mode](images/03-VCD-post-migration.png){.thumbnail}
55+
56+
2\. **Create a new network**
57+
58+
- Customers can create a new `network` with the correct subnet.
59+
- This solution works only if the customer has **a single** public IP range.
60+
61+
## Go further
62+
63+
If you need training or technical assistance to implement our solutions, please contact your Technical Account Manager or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for a custom analysis of your project.
64+
65+
Ask questions, give your feedback and interact directly with the team building our Hosted Private Cloud services on the dedicated [Discord](https://discord.gg/ovhcloud) channel.
66+
67+
Join our [community of users](/links/community).

‎pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd_post_migration/guide.en-au.md

Lines changed: 67 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,67 @@
1+
---
2+
title: "VMware Cloud Director - Setting up your network after vSphere to VCD migration"
3+
excerpt: "Learn how to configure your network after migrating from VMware vSphere to VMware Cloud Director"
4+
updated: 2025-03-04
5+
---
6+
7+
## Objective
8+
9+
This guide explains the necessary steps to configure your environment after migrating from your managed **VMware vSphere on OVHcloud** services to a managed **VMware Cloud Director on OVHcloud** solution.
10+
11+
These modifications are essential to ensure the proper functioning of your virtual machines and networks.
12+
13+
## Requirements
14+
15+
- A [VMware Cloud Director](/links/hosted-private-cloud/vmware-vcd) on OVHcloud solution.
16+
- Being the technical administrator of the managed [VMware vSphere on OVHcloud](/links/hosted-private-cloud/vmware) infrastructure.
17+
- Access to the [OVHcloud Control Panel](/links/manager)
18+
19+
## Instructions
20+
21+
### Step 1: Update virtual machine network settings
22+
23+
After migration, you need to update the network configurations of your `virtual machines (VMs)`.
24+
25+
To set the network configuration to DHCP (**recommended**):
26+
27+
1\. Go to the network settings of each VM.
28+
2\. Change the IP assignment mode to `DHCP`{.action}.
29+
30+
![DHCP setting](images/01-VCD-post-migration.png){.thumbnail}
31+
32+
3\. Make sure the `Guest customization settings`{.action} are set to `Disabled` before modifying the NIC settings.
33+
34+
![Disabled setting](images/02-VCD-post-migration.png){.thumbnail}
35+
36+
### Step 2: Handling the IP addressing bug in VCD
37+
38+
Networks are pre-created with placeholder Gateway CIDRs, as the actual VM subnets are unknown beforehand.
39+
40+
This can lead to IP assignment issues if not addressed post-migration.
41+
42+
#### **Identified issue**
43+
44+
- If a static IP is manually assigned to a VM and does not match the pre-configured `Gateway CIDR`, the assignment will fail.
45+
- You will not be able to create or update a VM with manual IP assignment outside the predefined `Gateway CIDR`.
46+
47+
#### **Solutions**
48+
49+
1\. **Use DHCP mode (recommended)**
50+
51+
- Setting all IP modes to `DHCP` works seamlessly, even if the OS is configured with a static IP.
52+
- This approach is valid for both isolated networks and `VM Networks`*.
53+
54+
![DHCP mode](images/03-VCD-post-migration.png){.thumbnail}
55+
56+
2\. **Create a new network**
57+
58+
- Customers can create a new `network` with the correct subnet.
59+
- This solution works only if the customer has **a single** public IP range.
60+
61+
## Go further
62+
63+
If you need training or technical assistance to implement our solutions, please contact your Technical Account Manager or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for a custom analysis of your project.
64+
65+
Ask questions, give your feedback and interact directly with the team building our Hosted Private Cloud services on the dedicated [Discord](https://discord.gg/ovhcloud) channel.
66+
67+
Join our [community of users](/links/community).

‎pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd_post_migration/guide.en-ca.md

Lines changed: 67 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,67 @@
1+
---
2+
title: "VMware Cloud Director - Setting up your network after vSphere to VCD migration"
3+
excerpt: "Learn how to configure your network after migrating from VMware vSphere to VMware Cloud Director"
4+
updated: 2025-03-04
5+
---
6+
7+
## Objective
8+
9+
This guide explains the necessary steps to configure your environment after migrating from your managed **VMware vSphere on OVHcloud** services to a managed **VMware Cloud Director on OVHcloud** solution.
10+
11+
These modifications are essential to ensure the proper functioning of your virtual machines and networks.
12+
13+
## Requirements
14+
15+
- A [VMware Cloud Director](/links/hosted-private-cloud/vmware-vcd) on OVHcloud solution.
16+
- Being the technical administrator of the managed [VMware vSphere on OVHcloud](/links/hosted-private-cloud/vmware) infrastructure.
17+
- Access to the [OVHcloud Control Panel](/links/manager)
18+
19+
## Instructions
20+
21+
### Step 1: Update virtual machine network settings
22+
23+
After migration, you need to update the network configurations of your `virtual machines (VMs)`.
24+
25+
To set the network configuration to DHCP (**recommended**):
26+
27+
1\. Go to the network settings of each VM.
28+
2\. Change the IP assignment mode to `DHCP`{.action}.
29+
30+
![DHCP setting](images/01-VCD-post-migration.png){.thumbnail}
31+
32+
3\. Make sure the `Guest customization settings`{.action} are set to `Disabled` before modifying the NIC settings.
33+
34+
![Disabled setting](images/02-VCD-post-migration.png){.thumbnail}
35+
36+
### Step 2: Handling the IP addressing bug in VCD
37+
38+
Networks are pre-created with placeholder Gateway CIDRs, as the actual VM subnets are unknown beforehand.
39+
40+
This can lead to IP assignment issues if not addressed post-migration.
41+
42+
#### **Identified issue**
43+
44+
- If a static IP is manually assigned to a VM and does not match the pre-configured `Gateway CIDR`, the assignment will fail.
45+
- You will not be able to create or update a VM with manual IP assignment outside the predefined `Gateway CIDR`.
46+
47+
#### **Solutions**
48+
49+
1\. **Use DHCP mode (recommended)**
50+
51+
- Setting all IP modes to `DHCP` works seamlessly, even if the OS is configured with a static IP.
52+
- This approach is valid for both isolated networks and `VM Networks`*.
53+
54+
![DHCP mode](images/03-VCD-post-migration.png){.thumbnail}
55+
56+
2\. **Create a new network**
57+
58+
- Customers can create a new `network` with the correct subnet.
59+
- This solution works only if the customer has **a single** public IP range.
60+
61+
## Go further
62+
63+
If you need training or technical assistance to implement our solutions, please contact your Technical Account Manager or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for a custom analysis of your project.
64+
65+
Ask questions, give your feedback and interact directly with the team building our Hosted Private Cloud services on the dedicated [Discord](https://discord.gg/ovhcloud) channel.
66+
67+
Join our [community of users](/links/community).

‎pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd_post_migration/guide.en-gb.md

Lines changed: 67 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,67 @@
1+
---
2+
title: "VMware Cloud Director - Setting up your network after vSphere to VCD migration"
3+
excerpt: "Learn how to configure your network after migrating from VMware vSphere to VMware Cloud Director"
4+
updated: 2025-03-04
5+
---
6+
7+
## Objective
8+
9+
This guide explains the necessary steps to configure your environment after migrating from your managed **VMware vSphere on OVHcloud** services to a managed **VMware Cloud Director on OVHcloud** solution.
10+
11+
These modifications are essential to ensure the proper functioning of your virtual machines and networks.
12+
13+
## Requirements
14+
15+
- A [VMware Cloud Director](/links/hosted-private-cloud/vmware-vcd) on OVHcloud solution.
16+
- Being the technical administrator of the managed [VMware vSphere on OVHcloud](/links/hosted-private-cloud/vmware) infrastructure.
17+
- Access to the [OVHcloud Control Panel](/links/manager)
18+
19+
## Instructions
20+
21+
### Step 1: Update virtual machine network settings
22+
23+
After migration, you need to update the network configurations of your `virtual machines (VMs)`.
24+
25+
To set the network configuration to DHCP (**recommended**):
26+
27+
1\. Go to the network settings of each VM.
28+
2\. Change the IP assignment mode to `DHCP`{.action}.
29+
30+
![DHCP setting](images/01-VCD-post-migration.png){.thumbnail}
31+
32+
3\. Make sure the `Guest customization settings`{.action} are set to `Disabled` before modifying the NIC settings.
33+
34+
![Disabled setting](images/02-VCD-post-migration.png){.thumbnail}
35+
36+
### Step 2: Handling the IP addressing bug in VCD
37+
38+
Networks are pre-created with placeholder Gateway CIDRs, as the actual VM subnets are unknown beforehand.
39+
40+
This can lead to IP assignment issues if not addressed post-migration.
41+
42+
#### **Identified issue**
43+
44+
- If a static IP is manually assigned to a VM and does not match the pre-configured `Gateway CIDR`, the assignment will fail.
45+
- You will not be able to create or update a VM with manual IP assignment outside the predefined `Gateway CIDR`.
46+
47+
#### **Solutions**
48+
49+
1\. **Use DHCP mode (recommended)**
50+
51+
- Setting all IP modes to `DHCP` works seamlessly, even if the OS is configured with a static IP.
52+
- This approach is valid for both isolated networks and `VM Networks`*.
53+
54+
![DHCP mode](images/03-VCD-post-migration.png){.thumbnail}
55+
56+
2\. **Create a new network**
57+
58+
- Customers can create a new `network` with the correct subnet.
59+
- This solution works only if the customer has **a single** public IP range.
60+
61+
## Go further
62+
63+
If you need training or technical assistance to implement our solutions, please contact your Technical Account Manager or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for a custom analysis of your project.
64+
65+
Ask questions, give your feedback and interact directly with the team building our Hosted Private Cloud services on the dedicated [Discord](https://discord.gg/ovhcloud) channel.
66+
67+
Join our [community of users](/links/community).

0 commit comments

Comments
 (0)