Migrating VMware VCloud Director vApps across Distributed Virtual Switches

A fascinating topic is how to migrate VMware VCloud Director vApps from one distributed virtual switch to another. Recently from the acquaintance of one of their field consultants, Aleksander Bukowinski, they have received a abundant procedure to overcome the possible service disruptions due to such a move. Aleksander has also authored a whitepaper on this topic that will soon be accessible for their audience in VMware partner Central. The paper also covers in detail an appended use case with Cisco Nexus 1000V and offers Power Shell and API call samples.

Confide in connectivity mode, they can have five different types of vApps in vCD: directly connected, routed, connected to routed vApp networks, abandoned and bound. The migration process would not require shutting down the vApps while the migration happens but rather could accomplish brief network interruption in case the VMs are connected to a vCloud Director Edge Gateway or no interruption at all if the VMs use abandoned networks with no assurance to the edge.

Requirements  

 The following requisite are required to perform the migration:

  • VMware VSphere 6.x (enables cross- DVS VMware vSphere vMotion, which is insistent for the online migration process)
  • Sustained VMware vCloud Networking and security versions.
  • Financed vCloud Director Versions.
  • Supported vSphere Power CLI versions.

Preparation

To get ready for the migration, a new allocated virtual switch and a new vSphere cluster must be strengthen. The target cluster must have access to the same networks and data stores as the source cluster. The same port groups from the source DVS must be created on the target DVS to keep the configuration identical and all the networks should be carefully mapped between the two clusters. For networks based on VXLAN the virtual wire ID is identical between the DVSs. The usage of VMware vCenter Server tags to label the source pools of the cluster would streamline the selection process of the right resources. If you want to know more about the VMware VCloud Director vApps  , you can join VMware training at Getprotech .Getprotech provides the best VMware training in Delhi

To prepare for the migration the following steps must be taken:

  1. Substitute the vCloud Director and vCenter Server databases and record all configuration information.
  2. Develop a new vSphere cluster. Make sure that the target cluster has acquired to the same networks (VLANs) and data stores as the source cluster.
  3. Develop a new DVS and connect it to the VMware ESXi hosts in the target vSphere cluster.
  4. Create a target cluster for VXLAN in the VMware CNS Manager.
  5. Prepare a new Provider VDS on the target vSphere cluster in vCloud Director.
  6. Prepare new external networks in vCloud Director based on port groups prepared on the target DVS.
  7. Amalgamate the target Provider VDC with the source one, making sure that the target provider VDC is primary.
  8. Attenuate the source vSphere cluster resource in vCloud Director. This step will stop vCloud Director from accessorizing  Objects in the source vSphere cluster.
  9. Start the vApp migration process based on vApp types.

Migration Procedure

 Directly connected vApps have VMs with networks directly associated to vCloud Director external networks without any edge Gateway. They can then be migrated online without any consideration about network interruption. To migrate the steps are as follows:

  1. Facilitate the source vSphere cluster resource in vCloud Director. This step is appropriate to allow changing networks in VMs. It only execute to VMs with directly connected Org networks.
  2. Edit the vApp in vCloud Director and add new Org networks graphed to external networks created on the target DVS. The target networks will change the source networks later on.
  3. Apply vSphere vMotion to migrate VMs that are part of the vApp to the target cluster and choose the exact port group on the target DVS. This activity can only be done using VMware vSphere web users.
  4. Analyze the VMs in the vApp and change networks assignment to the target networks. If DHCP mode is not in use and IP Address endurance is needed, select Static – manual mode and enter the IP addresses.
  5. Add and after abolish an additional empty disk drive to every VM in the vApp. This will activate vCloud Director Database records to be refurbished.
  6. Abolish the source external networks from the vApp. Because the vApp is functioning, you can’t abolish them through the vCloud Director User interface. However one can use vCloud API or vSphere Power CLI instead.
  7. Debilitate the source vSphere cluster resource pool in vCloud Director.

Routed vApps has assurance from the edge Gateway and as such might acquire network disconnection during the migration with a duration based on the service configured on the edge. To migrate the steps are as follows:

  • Make sure that the source vSphere cluster resource is confined in vCloud Director.
  • Apply vSphere vMotion to migrate \the VMs that are part of the vApp to the target cluster. Choose the exact port group on the target DVS and resource pool on the target vSphere Cluster.
  • Annotate the Edge Gateway. Choose configure Services and save the NAT static routing and VPN service configuration. Go to edge gateway properties and take a note of the Sub Allocate IP Pools and IP settings.
  • Edit the NAT static routing and VPN services configuration from the Edge Gateway.
  • Remove the Edge Gateway properties and change the source external networks with the target external networks.
  • After the Edge Gateway redeploy operation is complete change the services and apply the NAT, static routing and VPN services again. Assign the sub allocate IP Pools and check IP settings in the Edge Gateway properties screen. The application of these configurations will end the external connectivity outage phase.
  • Add and after amputate an additional empty disk drive for every VM in the vApp. This will activate vCloud Director Database records to be updated.

Fenced vApps use case is similar to the previous case. The VMs does not connect to vApps networks but rather to Org networks and the connection uses NAT through a dynamically formed Edge Gateway. Even in this case the VMs must be moved between VXLANs and may be experience connectivity disruptions.

vApps with VMs connected to isolate vApps networks does not have external connectivity. They all are connected to VXLAN based isolated networks and therefore no networks changes are required after the migration. To migrate the steps are as follows:

  • Make sure that the source vSphere cluster resource is confined in vCloud Director.
  • Apply vSphere vMotion to migrate VMs that are part of the vApp to the target cluster. Choose the exact port group on the target DVS and resource pool on the target vSphere cluster. This operation can only be done using vSphere web users.
  • Add and abstract an additional empty disk drive for every VM in the vApp. This will cause vCloud Director Database records to be updated.

Post Migration Tasks

After all current vApps and templates have been migrated to the target DVS and Target vSphere cluster, the source vSphere cluster can now be demilitarize from the vCloud Director. The steps are as follows:

  1. Authenticate that the source vSphere cluster resource is decrepit in vCloud Director.
  2. Make sure that all the migrated VMs have been update by adding and removing a disk drive in vCloud Director.
  3. Abstract the vSphere cluster resource pool in vCloud Director.
  4. Make sure all source networks have in detached from vApps.
  5. Detach Org VDC networks that are applicable to networks based on the source DVS.
  6. Detach external networks that are based on the source DVS.
  7. Attenuate and abolish any storage policies that use data stores that are accessible only on the source cluster.

 

 

 

 

 

Leave a Reply

Your email address will not be published. Required fields are marked *