This topic presents known issues in the current release. Some issues remain from previous releases.

If the account you used for cloud registration cannot authenticate, or is locked out because communication has been lost, you must re-register with the cloud.

If the Hybridity and Networking appliance (the management appliance) and the NSP cannot communicate, the password is cleaned up for security reasons. You must re-register with the existing password.

If the password for the account used for cloud registration has changed, you must reauthenticate.

After you upgrade Hybrid Cloud Manager, there is a possibility the Layer 2 Concentrator tunnel and the Hybrid Cloud Gateway tunnel status is "unknown."

After upgrading to 2.0, the Cloud Gateway and high throughput L2C appliances must be redeployed once before using Hybrid Cloud Manager features. Appliances perform as expected after the deployment.

When a stretch or unstretch operation is in progress for a given Network Distributed Port Group (dvPortGroup), the UI does not update.

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

See the following Knowledge Base article for a discussion of what to expect when you unstretch a network: Unstretching a Hybrid Cloud Manager Extended Network.

VMs moved with cross-cloud vMotion must have a hardware version of 9 or higher. Lower versions might fail to migrate. There are two ways to work around the version problem:

Upgrade the hardware version on the virtual machine before attempting vMotion migration. The upgrade triggers a reboot.

Migrate the VM using low-downtime migration.

Once a vMotion job is initiated, it cannot be canceled. Contact vCloud Air VMware Global Support Services if you must cancel an in-flight or scheduled migration.

Stop or reschedule all migrations before performing an update or redeploying an updated appliance.

Migration cannot progress if you reconfigure a VM while a migration is underway. If you accidentally reconfigure a VM during migration, contact VMware Global Support Services (GSS) to abort the migration.

The values for IP Set and MAC Set can be defined in the source and destination text boxes for L3 and L2 rules, respectively. These values must not exceed 218 characters.

If you have multiple VDCs, your policy has a section for each one, and the rules are specific to the VDC. Copying might appear successful, but Hybrid Cloud Manager does not process rules from a different section. Instead, create a rule in the target section.

If the policy that is not properly named, the VM migration succeeds, but the policy silently fails to migrate.

To work around this problem, follow these steps:

1

Log in to the cloud organization and choose the Manage and Monitor tab.

2

Select Organization vDCs.

3

Right-click the vDC, and choose Manage Firewall from the context menu.

4

In the Applied To column, specify the virtual wire or org network for the stretched network, and enable the rule.

Make sure that Retain MAC is checked for vR migration.

This alarm occurs even when "Retain MAC address" is not checked. In fact, there is no conflict. The alarm is most likely when a virtual machine has been migrated several times.

Do not stretch the management network. The management network is the on-premises communication path between the Hybridity and Networking appliance (the management appliance) and the Cloud Gateway or Layer 2 concentrators. Stretching the management network overloads the communication channels automatically established during deployment.

If any appliance is being deployed, do not initiate a migration. Conversely, if a migration is in flight, do not deploy or redeploy any appliance.

Not all license-related features are blocked in the user interface.