VMware

VMware vCloud Connector Release Notes

vCloud Connector 2.5 | 19 JUN 2013 | Build 1182929 (Server), 1182928 (Node)

Updated 23 SEP 2013

What's in the Release Notes

The release notes cover the following topics:

New Features

  • Performance Improvements for Copy
    vCloud Connector 2.5 features a new path-optimized copy mechanism that provides a higher copy speed and lower storage requirements.
  • Choice of Data Transfer Protocols for Copy
    vCloud Connector 2.5 allows you to select between HTTP(S) and UDT for data transfer, depending upon your needs. UDT is a reliable, high-speed data transfer protocol based on UDP. UDT offers higher speeds for transfer over high-latency, high-bandwidth networks.
  • Offline Data Transfer to vCloud Hybrid Service
    The Offline Data Transfer feature enables offline migration of large amounts of data from your private VMware vSphere or VMware vCloud Director based datacenter to the VMware vCloud Hybrid Service.

Accessing the UI

The vCloud Connector UI is no longer available at the vcloud.vmware.com web site. Use vCloud Connector as a plug-in in the vSphere Client.

Supported Browsers

  • Internet Explorer 8, 9
  • Firefox 15, 16
  • Chrome 22, 23

Supported Platforms

  • vSphere 4.0, 4.1, 5.0, 5.1, and 5.5
  • vCloud Director 1.5, 5.1, and 5.5
  • vCloud Networking and Security 5.1.2 and 5.5

Documentation

Known Issues

Installation and Configuration

Server tab in the Server Admin Web console and Node tab in the Node Admin Web console display a blank page
If you are using Firefox 15 or a higher version, when you select the Server tab in the vCloud Connector Server Admin Web console, a blank page appears. A blank page also appears when you select the Node tab in the vCloud Connector Node Admin Web console.
Workaround
Use a different browser to log in to the vCloud Connector Server and Node Admin Web consoles.

Node or server screen loads for a long time or node cannot be registered with server
After you install and power on a vCloud Connector node or server, or restart it, when you log on to its Admin Web console and click on the Node tab (for the node) or Server tab (for the server), the screen continues to load for a long time. You might also be unable to register the node with the server.

The following error appears in the log file:
Caused by: liquibase.exception.LockException: Could not acquire change log lock.
Workaround

  1. Log in to the node or server console as admin. The default password is vmware.
  2. Log in to the node or server database.
    For the node, type the following command: psql hcs postgres
    For the server, type the following command: psql hcs1 postgres
  3. Type the following command: select * from databasechangeloglock;
    The status in the locked column displays t.
  4. Update the locked status to 'false': update databasechangeloglock set locked='false';
  5. Verify the status: select * from databasechangeloglock;
    The status in the locked column now displays f.
  6. Exit the database: \q
  7. Restart the tomcat service.
    For the node, type the following command: /etc/init.d/hcagent-tomcat restart
    For the server, type the following command: /etc/init.d/hcserver-tomcat restart
    When prompted, enter the password vmware.
  8. Log out of the node or server console.

Copy

Cannot copy from vCloud Director 5.5 to vCloud Director 1.5
You cannot copy a vApp or vApp template from a vCloud Director 5.5 cloud to a vCloud Director 1.5 cloud. The copy task fails with the following error:
"Validation failed for the OVF file you provided: Fatal: Line/char 26/34: cvc-complex-type.2.4.a: Invalid content was found starting with element 'vcloud:IpScopes'. "
Workaround
None. Copying from a vCloud Director 5.5 cloud to a vCloud Director 1.5 cloud is not supported.

Checkpoint restart not supported if node is restarted during copy
If you restart the vCloud Connector node associated with the source or destination cloud while copy is in progress, you get the following error:
"Connection refused."
Checkpoint restart is not supported in this case.
Workaround
Copy the object again.

Cannot use UDT protocol across two firewalls
If your environment has two firewalls between the source and destination vCloud Connector nodes, you cannot use the UDT protocol to copy data. UDT copy occurs over a dynamically-generated port on the source node and port 8190 on the destination node (or, when you copy between a private cloud and a public cloud, between a dynamically-generated port on the private cloud node and port 8190 on the public cloud node). Any firewall rules must allow for this type of connection for data transfer. In an environment with two firewalls, this type of connection is not possible.
Workaround
None.

UDT copy from a private cloud to a public cloud fails sometimes
In low bandwidth networks, when you copy a large virtual machine or vApp from a private cloud to a public cloud using the UDT protocol, copy might fail. The progress bar displays 30% for a long time, then the copy task fails.
Workaround
In the source and destination vCloud Connector nodes, set properties to configure a smaller UDT packet size.

  1. Log in to the node console as admin.
    The default password is vmware.
  2. Open the /usr/local/tcserver/vfabric-tc-server-standard/agent/webapps/agent/WEB-INF/spring/appServlet/management.xml file in a text editor.
  3. Search for property name="udtProperties".
  4. Edit the following:
    udt_pkt_size: Packet size of UDT packets. The default value is 1048576 KB. For low bandwidth networks, set the value in the following range: 1024-1048576 (1KB to 1MB)
    udt_snd_buf_size: Buffer size of UDT at the source. The default value is 10485760 KB. The value must be greater than udt_pkt_size. The recommended value is approximately 10 times the value of udt_pkt_size.
    udt_rcv_buf_size: Buffer size of UDT at the destination. The default value is 10485760 KB. The value must be greater than udt_pkt_size. The recommended value is approximately 10 times the vaue of udt_pkt_size.

UDT copy fails with a "Could not connect" or "Bind failed" error
UDT copy might fail with a "Could not connect" or "Bind failed" error when the vCloud Connector nodes associated with the source and destination clouds are registered to the vCloud Connector server using fully qualified domain names (FQDN).
Workaround
Use FQDNs with proper entries in the DNS server so that the FQDNs get resolved to the correct address for UDT copy to work.

UDT copy fails with a "Server does not exist" error when FQDNs are used
UDT copy might fail with a "Server does not exist" error if you are using FQDNs for the vCloud Connector nodes and server. When the UDT service is enabled with FQDN, the server address gets resolved to the loopback address (127.0.0.1) instead of the static IP address with which the node is associated. The UDT service starts running on 127.0.0.1:8190 and cannot be reached on its FQDN or IP address.

You can use the following command in the vCloud Connector node console to check for this issue:
netstat -aun
The command returns the following:

"udp 0   0   127.0.0.1:8190   0.0.0.0:*"
Workaround
  1. Log in to the vCloud Connector node console as admin. The default password is vmware.
  2. In the /etc/nsswitch.conf file, change the hosts entry from
    hosts: files dns
    to
    hosts: dns files
  3. Restart the node.
  4. Enable UDT.
  5. Use the following command again:
    netstat -aun
    The command should return the following:
    "udp   0   0   IPaddress:8190 0.0.0.0:*" 

Network information not retained when you copy a vApp or export it with the Offline Data Transfer feature
When you copy or export a vApp or vApp template from a vCloud Director cloud, the vApp's internal network configuration is not retained in the destination cloud. The vApp is always deployed in the destination cloud in fenced mode with a direct connection to the organization network.

Deploy

Cannot deploy from a template if cloud is added with vApp User role
If you add a vCloud Director cloud to vCloud Connector using a vApp User role, you cannot deploy vApps from templates. You get the following error:
"Access is denied."
Workaround
Use a different user role to add the cloud.

Offline Data Transfer

Template with multiple virtual machines is not retained in catalog after import
When you use the Offline Data Transfer feature to export data to vCloud Hybrid Service, if you export a template that has multiple virtual machines and you select the Deploy and Keep in Catalog options for it while exporting, when the data is imported the template is deployed but it is not retained in the destination catalog.
Workaround
None.

UI

Suspend command is unavailable in vCloud Connector 2.5 for virtual machines on vSphere 4.0 clouds
In the vCloud Connector 2.5 UI, the Suspend icon is disabled when you click on a powered-on virtual machine that is on a vSphere 4.0 cloud.
Workaround
None.

Cannot see virtual datacenters when a node is registered with the server using system administrator credentials (vCloud Director only)
If you register a node associated with a vCloud Director cloud with the vCloud Connector server using system administrator credentials, you cannot see any of the virtual datacenters or their contents in the UI. Only catalogs and templates are visible.
Workaround
Do the following:

  1. In the Browser panel, expand the cloud.
  2. Reload each organization by right-clicking and selecting Reload.
  3. For vCloud Director 5.1.2 clouds, if all content is still not displayed after you have reloaded the organizations, collapse the tree and reload the cloud.

Content Sync

Cannot preserve all metadata in published vApp templates
When you subscribe to a published vCloud Director catalog, metadata in the templates is preserved depending upon the credentials with which the clouds containing the published catalog and subscription catalog are registered with vCloud Connector. To preserve all metadata entries, register the clouds with system administrator credentials.
Workaround
If you cannot register the cloud with system administrator credentials, use organization administrator credentials instead. This will not preserve all metadata entries but will preserve the entries that have Read-Write access. For more information on how metadata is preserved during Content Sync, see Using vCloud Connector.

All templates in subscription folders or catalogs deleted if "Remove entities if deleted at publisher" option selected
If you select the Remove entities if deleted at publisher option while subscribing to a published folder or catalog in the Content Library, a template should only be deleted in your subscription folder or catalog when it is deleted in the published folder or catalog.
However, all templates in the subscription folder or catalog are deleted in the following cases if the Remove entities if deleted at publisher option was selected:

  • If you unsubscribe from the published folder or catalog.
  • If the published folder or catalog is unpublished from the Content Library.
  • If the cloud containing the published folder or catalog is deleted from vCloud Connector.
The templates are deleted at the next polling interval.
Workaround
If you do not want templates in your subscription folder or catalog to be deleted, do not select the Remove entities if deleted at publisher option while subscribing to a published folder or catalog.

Delay before subscription tasks are updated
After you use the Subscribe command to subscribe to a folder or catalog in the vCloud Connector Content Library, there might be a delay before the task is updated.
Workaround
Refresh to see the updated task status.

Content Sync does not pick up a vApp template with modified metadata
If you modify the metadata of a vApp template in vCloud Director, vCloud Connector Content Sync will not detect it as a modified vApp template and synchronize it to subscription catalogs.
Workaround
Copy the existing template to a new template in the published catalog and Content Sync will pick it up.

Documentation

Incorrect URL for documentation center in vCloud Connector server and node console
In the vCloud Connector server and node consoles, the URL for the vCloud Connector 2.5 Documentation Center is incorrect.
Workaround
Use the following URL for the vCloud Connector 2.5 Documentation Center:
http://pubs.vmware.com/hybridcloud-25/index.jsp