The network adapter for recovered VMs change to an E1000 adapter type when using Replication Tracking VMs

Products

• VMware Cloud Director

Issue/Introduction

When you failover or migrate a replication that uses Replication Tracking VMs (RT VMs) from an On-Premises site to a Cloud Director site in Cloud Director Availability (VCDA), the recovered VM is configured with an E1000 network adapter and loses the source VM's network settings.

Environment

VMware Cloud Director Availability 4.x

Cause

This issue occurs because the network adapter type is not captured and set to null when resolving the source VM details in order to create the Replication Tracking VM.

Resolution

This is a known issue affecting Cloud Director Availability 4.x.

This issue is resolved in Cloud Director Availability 4.7.2 available at Broadcom Downloads.

Workaround

To workaround this issue, disable the replication tracking placement solution in the Cloud Director site.

Note: This procedure modifies a configuration file. Ensure to take a backup of the file before proceeding.

1. Navigate to the Cloud Director Availability Portal.
2. Delete the impacted replication.
3. SSH to the Cloud Director Replication Management Appliance and log in as root.
4. Edit the application.properties file for the Cloud service:
   
   vi /opt/vmware/h4/cloud/config/application.properties
   
   
5. Edit the vcd.rt.vms line, set it to false, and save the changes:
   
   vcd.rt.vms=false
   
   
6. In the Cloud Director Availability Portal, navigate to the System Health view.
7. Click Restart Service, and in the pop-up menu select Restart.
8. Once the service has restarted, configure a new replication for the affected VM.

Note: Once you disable RT-VM creation all new replications will be created using independent disks, Converting to RT-VM's will also be disabled. Existing RT-VM replications will not be affected