check-circle-line exclamation-circle-line close-line

vCloud Director Extender 1.1 Release Notes

vCloud Director Extender | 19 APR 2018 | Build 8244143

Check for additions and updates to these release notes.

What's in the Release Notes

These release notes cover the following topics: 

What's New

vCloud Director Extender 1.1 provides the following new features:

  • Support for vCenter Server 5.5 U3 to enable migration of on-premise VMs to a cloud provider environment.
  • Test cutover after a warm migration that allows consistency check of the target VMs by powering them on and running the necessary tests.
  • Warm migration with seed enables offline transfer of VMDK files as seed images to a target cloud and import of the seed images to the cloud. Using seeds reduces the time to perform initial transfer of the VMDK files and benefits the migration of large VMs or on-premise data centers with low WAN connectivity.
  • Multiple appliance configurations that allows DC extension for more than one virtual data center. 
  • Generating a support bundle to aid when you are troubleshooting vCloud Director Extender issues. For more information, see vCloud Director Troubleshooting.

Operational Limits

The following operational limits are discovered through rigorous testing of different migration scenarios. 

Number of deployments:

vCloud Director Extender can scale up to 20 CX connectors, each one of them installed on a separate on-premises vCenter Server 5.5 U3, 6.0 or 6.5 instance, and a single Cloud Continuity Manager installed on the Service Provider side.

Warm migration:

• You can migrate up to 50 virtual machines in multiple jobs from single or multiple on-premises vCenter Server to a cloud provider.

Cold migration:

• You can migrate up to 300 virtual machines in multiple jobs from single on-premises vCenter Server to a cloud provider.

• You can migrate up to 1500 virtual machines in multiple jobs from multiple on-premises vCenter Servers to a cloud provider.

• You can migrate up to 100 virtual machines concurrently from one single on-premises vCenter Server to a cloud provider via API.

L2 VPN network extensions:

The following operational limits are discovered by performing L2 VPN network extensions on a standard switch.

• You can perform up to 5 L2 VPN network extensions from a single on-premises vCenter Server to a single cloud provider.

• You can perform up to 20 L2 VPN network extensions from multiple vCenter Server to a single cloud provider.

For more information, see the vCloud Director Extender 1.1 User's Guide.

Supported Browsers 

vCloud Director Extender is compatible with the current and last major revision of browsers. It was tested and supports:

Windows 10

  • Google Chrome 65.0.3325.181 (Official Build) (64-bit)
  • Mozilla Firefox 47.0.2

Coexistence with vCloud Availability

Tenant Side

vCloud Extender 1.1 and vCloud Availability 2.x can be installed and operate together on the same on-premise vCenter Server. However, you can either replicate VMs using vCloud Availability 2.x or migrate them using vCloud Director Extender. For more information, see Cannot migrate VMs protected by vCloud Availability for vCloud Director 2.x.

Service Provider Side

vCloud Extender 1.1 and vCloud Availability 2.x can be installed and operate together on the same vCloud Director instance. However, you can either replicate VMs using vCloud Availability 2.x or migrate them using vCloud Director Extender. For more information, see Cannot migrate VMs protected by vCloud Availability for vCloud Director 2.x.

Upgrade

There is no direct upgrade path to vCloud Director Extender 1.1. To deploy and configure vCloud Director Extender 1.1 in an environment where version 1.0 is already deployed, you must uninstall your existing vCloud Director Extender and deploy a new vCloud Director Extender 1.1.

Product Documentation

In addition to the current release notes, you can use the vCloud Director Extender User's Guide to learn more about the product.

Resolved Issues

  • When trying to extend an L2 network using NSX 6.4, you receive a NumberFormatException: For input string: "Bad Request" error message

    When you initiate an L2 network extension based on NSX 6.4, the network extension fails with a NumberFormatException: For input string: "Bad Request". The Activity Task Detail window for the vCloud Director Edge Gateway shows the following error details:

    Invalid L2vpn server password configured in sites mcloudext-peersite-4. Password length must be at-least 12 characters and at-max 63 characters. It must contain mix of alphabets with both upper case and lower case, numbers and at-least one special character. Password must not contain username as substring. Character must not consecutively repeat 3 or more times., error code 16566.

    This issue is resolved in this release.

  • The network performance is limited due to the type of the network adapter

    You might experience a degraded network performance due to the default type of network adapter used for deploying the Replication Manager and the Replicator.

    This issue is resolved in this release.

Known Issues

  • You cannot migrate VMs with vCloud Director Extender 1.1 if these VMs are already protected by vCloud Availability for vCloud Director 2.x

    When you have both vCloud Director Extender 1.1 and vCloud Availability for vCloud Director 2.x installed and operating in the same deployment, an attempt to migrate one or multiple VMs protected by vCloud Availability for vCloud Director fails with an Already replication enabled error message.

  • Home dashboard for monitoring the health status of migration tasks, the status and the throughput of the L2 VPN Tunnel is showing incorrect data

    The L2 Tunnel throughput data on the monitoring home dashboard is showing incorrect information due to a known limitations of NSX.

    Workаround: The Tunnel throughput data should be ignored.

  • You cannot delete a vCloud Director Extender Replicator after it was activated if the Replicator configuration is not correct

    If a vCloud Director Extender Replicator configuration is already activated but its configuration is not correct, for example contains an unresolvable URL, deleting the Replicator fails with an Error during Replicator deletion error message.

    Workaround: To work around the issue, you can delete the Replicator manually by following the steps below.

    1. Log in to the vSphere Web Client and delete the Replicator virtual machine.
    2. Delete the entries for the Replicator from the vCloud Extender database.
    3. Log in to the vCloud Director Extender On-Premise Appliance if the Replicator is at the Tenant side or the vCloud Director Extender Cloud Appliance if the Replicator is at the Service Provide side over SSH.
    4.  Log in to the vPostgres database of the Extender appliance by running the following command:

    password=`grep -w password /opt/vmware/mobility-service/conf/connconfig.yaml | awk -F':' '{print $2}' | tr -d "[[:space:]]" | tr -d "\'"` && export PGPASSWORD=$password && /opt/vmware/vpostgres/current/bin/psql mobility_db mobility_db

           5. Run an SQL query to find the ID of the Replicator you want to delete.

    SELECT id FROM h4replicator WHERE json::TEXT LIKE '%10.162.20.47%';

           6. Run a delete SQL statement to remove the database entry for the Replicator.

    delete from h4replicator where id = 'replicator_id';

  • If you are logged in to the vSphere Web Client as root, you cannot initiate vCloud Director Extender operations

    If you log in to the vSphere Web Client as root, you cannot initiate any vCloud Director Extender operations by using the vCloud Director Extender Plug-in.

    Workaround: To work around this issue, log in to the vSphere Web Client as a administrator@vsphere.local.

  • Unregistering the vCloud Director Extender Plug-in does not remove the com.vmware.cloudextender extension from vCenter Server Managed Object Browser (MOB)

    After unregistering the vCloud Director Extender Plug-in from the vSphere Web Client, the com.vmware.cloudextender extension remains active in the vCenter Server MOB. 

    Workaround: To work around this issue, you must manually remove the vCloud Director Extender Plug-in extension from the vCenter Server MOB.

    1. In a web browser, log in to the vCenter Server MOB URL https://vcenteripaddress/mob as a local administrator.
    2. Click Content.
    3. Click ExtensionManager. Under ExtensionList table you can find the com.vmware.cloudextender extension.
    4. In the Methods table, click UnregisterExtension.
      A new UnregisterExtension window opens.
    5. In the Value text box, enter com.vmware.cloudextender and click Invoke Method.
    6. Close the UnregisterExtension window.
    7. To verify that the extension is removed, refresh the MOB window. After the MOB refresh the com.vmware.cloudextender extension is removed from ExtensionList.
    8. Restart the vSphere Web Client.
  • During a Warm migration with a Preloaded Seed, the vCloud Director Extender dashboard does not display the powered off target VM

    When you initiate a Warm migration with Preloaded Seed, the Select a seed drop-down menu in the vCloud Director Extender Plug-in UI does not show the target seed VM, even though it is powered off.

    Workaround: Тo work around this issue, refresh the vCloud Director Extender Plug-in UI in the browser and wait for a few minutes until the target seed VM appears in the Select a seed drop-down menu.

  • During a Warm migration with a Preloaded Seed, the vCloud Director Extender dashboard is displaying both powered off and powered on seed VMs

    When you initiate a Warm migration with Preloaded Seed, the Select a seed drop-down menu is displaying both powered off and powered on seed VMs. This issue occurs due to a known vCloud Director API limitations.

    Workaround: To work around this issue, refresh the web browser with the vCloud Director Extender Plug-in, and wait for 5-6 minutes until the target seed VM is listed in the Select a seed drop-down menu.