VMware® vCloud® Air™ Hybrid Cloud Manager™

Release Notes

Version 1.0 Update 1

November 26, 2015

Revised December 4, 2015

Contents

About Version 1.0 Update 1

New or Changed Features

Fixed Issues

Open Issues

About Version 1.0 Update 1

VMware® vCloud® Air™ Hybrid Cloud Manager™ 1.0 Update 1 is a maintenance release to address issues in version 1.0. Version 1.0 Update 1 does not have any infrastructure changes, but some implementation details have been upgraded.

TOP

New or Changed Features

Version 1.0 Update 1 does not have any infrastructure changes, but some implementation details have been upgraded.


Layer 2 scale out now supported. The user interface has changed to support configuring multiple Layer 2 Concentrator virtual appliances.

When configuring an L2 Concentrator, you can choose to route traffic through the Hybrid Cloud Gateway so the L2C can masquerade behind the HCG and share its IP address. This allows you to have all three appliances use a single IP address for ease of deployment.

Alternatively, you can choose to configure the L2C with a different IP address, and as of this release, you have the option to install multiple L2 Concentrators to support scale out. If you choose L2C scale out deployment, you must assign each concentrator a different IP address.

The typical reason for this configuration is to maximize your data center resources, and increase speed by separating the migration path from the datapath. For example, if you have multiple vLANs you might choose to configure an L2C for each vLAN. In this architecture the L2Cs maintain the data path(s) for host-to-host communication but continue use the Hybrid Cloud Gateway for internal communication and management tasks. This feature is most beneficial if you have secure, high-speed lines, such as a Direct Connect connection.

This feature is fully explained in the VMware® vCloud® Air™ Hybrid Cloud Manager™ Installation and Administration Guide.

TOP

Fixed Issues

This section lists known problems in version 1.0 that are fixed in version 1.0 Update 1.


In version 1.0, the Migration wizard "Select destination network" page accommodated only one vNIC connection.

For VMs with multiple vNICs, only the first vNIC attached to the designated network, and the remaining vNICs arbitrarily connected to other networks. The workaround was to wait for the migration to complete, then manually reconfigure the vNICs to connect to the correct network.

The user interface has been upgraded so you can configure the destination networks for multiple vNIC connections.


Linked Mode for vCenter 6.0 was not supported in version 1.0. The Web Engine would shut down because it couldn't verify certificates from the Platform Services Controller.

Version 1.0 Update 1 supports Linked Mode for vCenter 6.0, as well as Linked Mode for 5.5 U1, 5.5 U2, and 5.5 U3.


The following behaviors represent fixes since the last release:

TOP

Open Issues

This section describes known issues in the current release.


The User Interface options for network stretch and un-stretch might not be updated when an active stretch/un-stretch operation is going on for a given Distributed PortGroup (dvPortGroup).

The Unstretch option might be enabled in the UI while a stretch/unstretch task is in progress.

Workaround

Wait for the operation to complete before performing any other hybridity operation on the same Distributed PortGroup.


The migration wizard occasionally displays negative values for the Available vCloud Air virtual datacenter resources (CPU / RAM).

Available vDC resources (CPU / RAM) are occasionally listed with negative values.

Workaround

Please ensure that the target vDC has available resources in vCloud Air prior to migration. Any incorrect values in the migration wizard can be safely ignored.


Cancelling a migration task is not supported.

Once a migration job is initiated, it cannot be cancelled. The UI task cancel option does not work.

Workaround

None.


VM name cannot have special characters.

If the VM name contains special characters the migration might fail. The following characters are not allowed: ~ ` ! @ # $ % ^ & * ( ) + = { [ } ] | \ : ; " ' < , > . ? /

Workaround

Rename the VM.