VMware

vCloud Director 5.6.4 for Service Providers Release Notes

vCloud Director 5.6.4 for Service Providers | 12 FEB 2015 | Build 2496071

Last updated: 27 FEB 2015

What's in the Release Notes

The release notes cover the following topics:

What's New in this Release

  • Increased upgrade support: Added upgrade support from vCloud Director 5.5.2 and 5.5.2.1 to vCloud Director 5.6.4 for Service Providers. Upgrading from vCloud Director 5.6.3 for Service Providers to vCloud Director 5.6.4 for Service Providers is also supported
  • Increased guest operating system support: vCloud Director has added support for the following guest operating systems.
    • Red Hat Enterprise Linux 7
    • Ubuntu 14.04
    • SUSE Linux Enterprise Server 12
    • CentOS 6.5
    • CentOS 7
    • Oracle Linux 6.5
    • Oracle Linux 7

System Requirements, Installation, and Upgrade

For information about system requirements and installation instructions, see the VMware vCloud Director Installation and Upgrade Guide.

For interoperability information, see Interoperability Matrix, Upgrade Path and Configuration Maximums.

Documentation

To access the full set of vCloud Director 5.6 documentation, go to the vCloud Director Documentation page.

Resolved Issues

This release resolves issues in the following areas.

General Issues

  • The fix-scheduler-data command is not displayed on the cell-management-tool help page
    The fix-scheduler-data command for the cell-management-tool fixes Quartz scheduler data. This command is not displayed on the cell-management-tool help page. This issue is resolved in vCloud Director 5.6.4.

  • vCloud Director services fail to start when Verify vShield Manager certificates is enabled
    After you enable Verify vShield Manager certificates in vCloud Director general settings, vCloud Director services fail to start. This issue is resolved in vCloud Director 5.6.4.

  • Datastores are inaccessible after being moved to storage pods
    After you move a datastore to a storage pod in vCenter Server, the datastore is inaccessible from vCloud Director. This issue is resolved in vCloud Director 5.6.4.

  • Provider virtual datacenter sometimes loses access to datastores and storage pods after moving a datastore into or out of a storage pod
    When you move a datastore into or out of of a storage pod, the provider virtual data center using the pod might lose access to the datastore or pod. This issue is resolved in vCloud Director 5.6.4.

  • Attempts to download media files from a public catalog fail
    When you attempt to download a media file from a public catalog, the download operation fails. This issue is resolved in vCloud Director 5.6.4.

  • Duplicate storage data entries take up organization virtual data center storage space
    When you move a virtual disk from one datastore to another, vCloud Director does not properly delete the data entry for the virtual disk from the originating datastore. This duplicate entry continues to take up storage space on the datastore, reducing the amount of available storage on the organization virtual data center. This issue is resolved in vCloud Director 5.6.4.

  • vCloud Director displays 0 GHz CPU allocation used for pay-as-you-go organization virtual data centers
    The vCloud Director Web console incorreclty displays 0 GHz as the CPU allocation used for pay-as-you-go organization virtual data centers that have resources guaranteed set to 0. This issue is resolved in vCloud Director 5.6.4.

  • vCloud Director displays incorrect CPU used for elastic Allocation Pool organization virtual data centers
    When an elastic Allocation Pool organization virtual datacenter is backed by multiple resource pools and the percentage of resources guaranteed for the organization virtual data center is changed, the vCloud Director Web console displays an incorrect CPU Total Allocated Capacity for organization virtual data centers. This issue is resolved in vCloud Director 5.6.4.

  • vCloud Director does not validate the load balancer virtual server IP when the load balancer is added through service insertion
    When you add a load balancer using service insertion, vCloud Director does not validate the virtual server IP of the load balancer. In vCloud Director 5.6.4, you can enable validation using a configuration parameter.

  • Host preparation for stateless ESXi hosts fails
    When you attempt to prepare a stateless ESXi host, the operation fails with an error message similar to the following.

    Found an older version 5.1.0.799577 of vCloud Director agent on this stateless host 192.0.2.0. Upgrade the host boot image with latest version 5.5.0.1296072. Consult the documentation on how to add the agent to the image catalog.

    This issue is resolved in vCloud Director 5.6.4.

  • Users with the right to add a template to a catalog cannot overwrite a template unless they have the right to edit a catalog enabled
    When a user has the right to add a template to a catalog enabled, the user can only overwrite an existing template if they also have the right to edit a catalog enabled. This issue is resolved in vCloud Director 5.6.4

  • Changes to a vApp template made using the overwrite option in a published catalog do not sync to subscribed catalogs
    When you modify a vApp template using the overwrite option in a published catalog, the changes are not reflected in subscriptions to the public catalog. This issue is resolved in vCloud Director 5.6.4.

  • Attempts to download vApp templates from a shared catalog fail
    When you attempt to download a vApp template from a catalog that is shared from another organization, the operation fails. This issue is resolved in vCloud Director 5.6.4.

  • Load balancer configuration changes sometimes do not appear in vCloud Director
    When you change the load balancer configuration at the same time that you edit the load balancer in the vCloud Director Web console, vCloud Director does not record the changes to the load balancer configuration, and the load balancer configuration appears different in vCloud Director than it does in vShield Manager. This issue is resolved in vCloud Director 5.6.4.

  • Deleted users are not marked as stranded after LDAP synchronization
    When vCloud Director automatically synchronizes user and group information with the LDAP server, deleted users are not marked as stranded. This issue is resolved in vCloud Director 5.6.4.

  • ISO files uploaded with .flp extension when .iso is not specified
    When you upload an ISO file and do not include the .iso extension in the file name, vCloud Director uploads the file with a .flp extension. This issue is resolved in vCloud Director 5.6.4.

Installation and Upgrade Issues

  • Attempts to upgrade from vCloud Director 5.5.2 or 5.5.2.1 to vCloud Director 5.6.3 for Service Providers fail
    When you attempt to upgrade from vCloud Director 5.5.2 or 5.5.2.1 to vCloud Director 5.6.3 for Service Providers, the upgrade fails during database upgrade. This issue is resolved in vCloud Director 5.6.4.

  • vCloud Director displays some catalogs' status as Unknown after you upgrade vCloud Director from version 5.1.x to version 5.5.2
    After you upgrade vCloud Director from version 5.1.x to version 5.5.2, vCloud Director displays the status of some catalogs that were present before the upgrade as Unknown and displays those catalog names highlighted in gray. This issue occurs when the catalog has existed for longer than the activity log of vCloud Director, and the task might have been deleted from the database resulting in a catalog status of unknown. This issue is resolved in vCloud Director 5.6.4.

  • vCloud Director sometimes fails to reconnect to vCenter Server after you upgrade vCloud Director to version 5.6.3
    After you upgrade vCloud Director to version 5.6.3, vCloud Director fails to reconnect to vCenter Server if any virtual machines on vCenter have sparse disks. This issue is resolved in vCloud Director 5.6.4.

  • vCloud Director web client does not display vApps for some organizations after upgrading vCloud Director to version 5.6.3
    After you upgrade vCloud Director to version 5.6.3, the vApps list for some organizations fails to load in the vCloud Director web client with an error similar to the following.

    [ cfa5968d-d5e6-484c-bab8-46dd10bb685e ] could not execute query - Data truncation

    This issue is resolved in vCloud Director 5.6.4.

Networking Issues

  • Edge gateways displayed for an external network when the network is not connected to Edge gateways
    When you click the Gateways tab for an external network that is not connected to Edge gateways, the vCloud Director Web console displays all Edge gateways on the system. This issue is resolved in vCloud Director 5.6.4.

  • SSL certificate validation for vShield Manager fails
    When the system enforces certificate validation for SSL communication between vCloud Director and vShield Manager, SSL certificate validation for vShield Manager always fails, resulting in communication failure between vCloud Director and vShield manager. This issue is resolved in vCloud Director 5.6.4.

  • vCloud Director displays 0 GHz CPU allocation used for pay-as-you-go organization virtual data centers
    The vCloud Director Web console incorreclty displays 0 GHz as the CPU allocation used for pay-as-you-go organization virtual data centers that have resources guaranteed set to 0. This issue is resolved in vCloud Director 5.6.4.

  • DCHP settings for a routed vApp network are not preserved when the parent network is modified
    When you modify the parent network of a routed vApp network, the DHCP settings of the routed vApp network are lost. This issue is resolved in vCloud Director 5.6.4.

  • vCloud Director does not allow you to reuse IP addresses that are no longer in use in the sub allocation pool of an Edge gateway
    When you try to assign an IP address that was previously used by a virtual machine to the sub allocation pool of an Edge gateway, the operation fails with an error message stating that the IP address is already in use. This issue is resolved in vCloud Director 5.6.4.

  • vCloud Director does not validate the load balancer virtual server IP when the load balancer is added through service insertion
    When you add a load balancer using service insertion, vCloud Director does not validate the virtual server IP of the load balancer. In vCloud Director 5.6.4, you can enable validation using a configuration parameter.

  • Trying to assign a NAT IP to a vApp routed network set to manual fails
    When you try to assign a NAT IP to a vApp routed network with a NAT rule set to manual, the operation fails with the following error message.

    Invalid IP address for external network

    This issue is resolved in vCloud Director 5.6.4.

  • Virtual machine network is re-customized after moving the virtual machine from one vApp to another
    After moving a virtual machine from one vApp to another vApp in the same organization, the virtual machine's network is re-customized when the virtual machine is powered on. This issue is resolved in vCloud Director 5.6.4.

  • Default gateway set for multiple virtual machine NICs after selecting Change SID during guest customization
    When you select Change SID during guest customization for a virtual machine with multiple NICs, vCloud Director assigns a default gateway to all NICs on the virtual machine instead of only on the primary NIC. This issue is resolved in vCloud Director 5.6.4.

Virtual Machine and vApp Issues

  • New virtual machines sometimes exceed the datastore limit when you deploy multiple new virtual machines simultaneously
    When you deploy multiple virtual machines at the same time, the combined size of the deployed virtual machines might exceed the datastore limit. This issue is resolved in vCD 5.6.4.

  • Virtual machines added from OVF in vCloud Director do not appear in Chargeback Manager
    When you add a vApp from OVF in vCloud Director, the virtual machine created does not appear in the virtual machines list in Chargeback Manager. This issue is resolved in vCloud Director 5.6.4.

  • Attempts to open a virtual machine console on Google Chrome fail
    When you attempt to open a virtual machine console on a Google Chrome browser, the operation fails. The occurs due to the deprication of NPAPI in Google Chrome. vCloud Director 5.6.4 uses WebMKS instead of the VMware Remote Console to open virtual machine consoles in Google Chrome, which resolves this issue.

  • Attempting to set a deployment lease during vApp creation fails
    When you set a deployment lease value during vApp creation, the deployment lease value is not preserved in the new vApp. This issue is resolved in vCloud Director 5.6.4.

  • vCloud Director does not display some organization virtual data center networks during direct vApp network creation
    When you create a direct vApp network by using the vCloud Director Web console, vCloud Director does not display some available organization virtual data center networks. This issue is resolved in vCloud Director 5.6.4.

  • Properties missing in virtual machines deployed from an OVA template
    If you import a virtual machine into vCloud Director from an OVA template, some of the virtual machine properties are lost and do not appear in the imported virtual machine. This issue is resolved in vCloud Director 5.6.4.

  • Unable to select storage policy when importing a virtual machine from vCenter into an existing vApp
    When you import a virtual machine from vCenter Server into an existing vApp, there is no option to select a storage policy for the virtual machine. This issue is resolved in vCloud Director 5.6.4.

  • vCloud Director does not display the runtime lease of a vApp in a partially powered off state
    When a vApp is partially powered off, the vCloud Director Web console does not display the runtime lease for the vApp. This issue is resolved in vCloud Director 5.6.4.

  • Access forbidden error message when attempting to access a shared vApp template
    When you attempt to access a vApp template shared from another organization in vCloud Director, vCloud Director displays an access forbidden error if the source organization downloaded the vApp template by subscribing and syncing to an external catalog. This issue is resolved in vCloud Director 5.6.4.

  • vApp template stop action is not preserved after export from and import into vCloud Director
    When you import a vApp template that was previously exported from vCloud Director, the template's stop action is not preserved in the imported vApp template. This issue is resolved in vCloud Director 5.6.4.

  • Attempts to modify a virtual machine or vApp template imported from vCenter Server or an OVF fail
    When you attempt to modify a virtual machine or vApp that has been imported from vCenter Server or from an OVF, the operations fails with an InvalidDeviceSpec error. This issue is resolved in vCloud Director 5.6.4.

  • Virtual machine time zone set to GMT after Change SID
    When you select Change SID for a virtual machine, the virtual machine time zone is changed to GMT. This issue is resolved in vCloud Director 5.6.4.

  • Autologon for non-administrator incorrectly disabled
    When you have a virtual machine with a Windows operating system in which you have configured a non-administrator user to have the autologon feature enabled, and then you use the vCloud Director user interface or the vCloud API to customize the virtual machine's guest operating system properties and don't enable autologin for administrator, the autologon setting for the non-administrator user is incorrectly disabled. This issue is resolved in vCloud Director 5.6.4.

  • Windows Server 2008, 2008 R2, and 2012 virtual machines ask you to reset the guest operating system password after you customize the virtual machine with SID change and password reset
    When you power on a Windows Server 2008, 2008 R2, or Windows 2012 virtual machine after customizing the virtual machine with SID change and password reset, the guest operating system asks you to reset the password. This issue is resolved in vCloud Director 5.6.4.

  • Virtual machine has an incorrect name after syncing to a published catalog
    When you sync a vApp containing a single virtual machine to a published catalog, the virtual machine in the destination catalog is renamed to match the name of the vApp. This issue is resolved in vCloud Director 5.6.4.

  • Attempting to set the guest operating system password using guest customization on a Windows 2012 guest operating system fails
    When you use guest customization to set a password for a Windows 2012 guest operating system, the guest operating system password is not set. This issue is resolved in vCloud Director 5.6.4.

  • Disconnecting a NIC from the virtual machine properties page of the vCloud Director Web console fails
    When you deselect the Connected check box on a virtual machine's Properties page using the vCloud Director Web console, the NIC remains connected. This issue is resolved in vCloud Director 5.6.4.

  • Attempting to move a virtual machine from a vApp template by using the relocate action API call fails
    When you use the deprecated relocate action API call to move a virtual machine from a vApp template, a Java null value exception about the cvmID value occurs and the relocate action fails. This failure typically occurrs for vApp templates that have been directly imported into vCloud Director.

    This issue is resolved in vCloud Director 5.6.4.

  • Guest customization fails with a Sysprep error
    When you attempt to use guest customization on a virtual machine, the operation fails with the following error message.

    Mount directory C: does not exist

    This issue is resolved in vCloud Director 5.6.4.

  • Attempting to power on a virtual machine with guest customization enabled sometimes fails
    When you attempt to power on a virtual machine with guest customization enabled on a provider virtual data center where one or more ESXi hosts are in standby mode, the operation fails sometimes. This issue is resolved in vCloud Director 5.6.4.

  • Attempting to power on a vApp or a virtual machine created on a storage cluster might fail
    When you attempt to power on a virtual machine or vApp created on a storage cluster in an organization virtual data center that is thin provisioned with storage DRS disabled, the operation sometimes fails with the following error message.

    One or more exceptions have occurred - Unable to perform this action.
    Contact your cloud administrator.

    This issue is resolved in vCloud Director 5.6.4.

  • Virtual machines configured with static IP from a pool sometimes obtain IP addresses through DHCP after the pool is exhausted
    In some cases, virtual machines configured to obtain a static IP address from a pool still obtain addresses through DHCP after the pool is exhausted. This issue is resolved in vCloud Director 5.6.4.

  • vCloud Director incorrectly displays a disk size of 4 MB for virtual disks larger than 2 TB
    When you add a virtual disk larger than 2 TB, the vCloud Director displays the disk size as 4 MB. This issue is resolved in vCloud Director 5.6.4.

  • vCloud Director always lists the installed version of VMware Tools as the current version
    vCloud Director refers to the installed version of VMware Tools as the current version even a newer version of VMware Tools is available. This issue is resolved in vCloud Director 5.6.4.

vCloud API Issues

  • vCloud API does not display shared catalogs
    When you browse catalogs by using the vCloud API, shared catalogs and their contents are not displayed. This issue is resolved in vCloud Director 5.6.4.

  • Using the vCloud API or SDK to create a user sometimes results in an error message
    When you create a new user in an organization by using the vCloud API or SDK after that user has been imported to other organizations in the cloud, vCloud Director creates the user, but displays an error message. This issue is resolved in vCloud Director 5.6.4.

  • Attempts to delete a metadata key by using the vCloud API fail if the value of the metadata key element, the key name, contains a colon (:)
    Metadata key names containing colons can be entered in the vCloud Director user interface. However, when using the vCloud API to delete the metadata key that has a colon in its name, the attempt fails. This issues is resolved in vCloud Director 5.6.4.

  • Attempting to retrieve an OrgVdc by using the vCloud API as a vApp user fails
    When you are signed in to vCloud Director as a vApp user and attempt to retrieve an OrgVdc by using the vCloud API, the operation fails with an Internal Server Error message. This issue is resolved in vCloud Director 5.6.4.

  • Delay in fetching a gateway by using the vCloud API
    When you fetch gateway details using the vCloud API, there is a delay before the operation resolves. This issue is resolved in vCloud Director 5.6.4.

  • Request to capture a vApp as a template by using vCloud API fails
    When using vCloud API version 5.1 to capture a vApp as a template, the request fails if the organization does not include any catalogs that are not published. When using vCloud API version 5.1 with vCloud Director 5.6.4, published catalogs are considered for use by a captureVApp operation.

  • Virtual machine network connectivity lost after modifying vApp lease properties by using the vCloud API
    After modifying vApp lease properties by using the vCloud API, virtual machines inside that vApp temporarily lose network connectivity. This issue is resolved in vCloud Director 5.6.4.

  • Description field in NatRuleType is not recognized by vCloud Director
    When you set a description in NatRuleType for an Edge gateway NAT by using the vCloud API, vCloud Director does not record the description. This issue is resolved in the vCloud API for vCloud Director 5.6.4. vCloud Director 5.6.4 also allows you to use the vCloud Director Web console to assign descriptions to SNAT and DNAT rules created at the organization virtual data center level of gateways.

  • Responses to vCloud API requests that involve catalog objects take a long time and sometimes time out
    The time for the vCloud API to construct a response to a call that involves catalog objects increased in vCloud Director 5.5. As a result, clients using such API calls might experience timeouts before the system returns the response to the client. This issue is resolved in vCloud Director 5.6.4.

  • Attempting to move a virtual machine from a vApp template by using the relocate action API call fails
    When you use the deprecated relocate action API call to move a virtual machine from a vApp template, a Java null value exception about the cvmID value occurs and the relocate action fails. This failure typically occurrs for vApp templates that have been directly imported into vCloud Director.

    This issue is resolved in vCloud Director 5.6.4.

Known Issues

The following issues are known to occur in this release of vCloud Director.

  • Organization virtual data center cannot be modified after modifying memory or CPU allocation fails
    When you attempt to modify the memory or CPU allocation of an allocation pool or reservation pool organization virtual data center to a number greater than the maximum allowed allocation, the operation fails. If you attempt to modify the organization virtual data center after such a failure, the operation fails with the following error.

    The given value of memory allocation for OrgVdc is too hight to be accomodated

    Workaround: Log out of vCloud Director and log back in.

  • Numeric overflow database error in vCloud Director when storage of an organization virtual data center exceeds 2048 TB
    If the storage of an organization virtual data center is 2048 TB or greater, the vCloud Director Web client might display a numeric overflow database error when you attempt to perform any of the following actions in vCloud Director.
    • View the Media list
    • Deploy a new vApp in an organization
    • Move a vApp to a different organization virtual data center
    • Add an object to a catalog
    • Upload an OVA, OVF, or media file in an organization

  • Host agent upgrade fails if the vCloud Director system name contains non-ASCII characters
    When you upgrade a vCloud Director system with non-ASCII characters in its name from an earlier version to version 5.5.1, the host agent upgrade fails.

    Workaround: Unprepare the host to remove the host agent, then prepare the host agent again.

  • Non-ASCII characters in VPN tunnel names appear as garbage characters in remote organizations
    When you assign a name to a VPN tunnel that includes non-ASCII characters, the non-ASCII characters in the name appear as garbage characters when you view the VPN tunnel from another organization. The VPN tunnel continues to function normally.

    Workaround: Do not use non-ASCII characters in VPN tunnel names.

  • Edge gateways cannot be created or updated with a pool server or virtual server that has non-ASCII characters in its name
    When you attempt to create an edge gateway with a pool server or virtual server that has non-ASCII characters in its name, the operation fails. When you change the name of a pool server or virtual server to include non-ASCII characters, any Edge gateways associated with the pool server or virtual server cannot be updated.

    Workaround: Do not use non-ASCII characters in the names of pool servers or virtual servers that are used for Edge gateways.

  • vApp template names cannot include only non-ASCII characters
    vCloud Director displays the error message Invalid computer name: Computer name can only contain alphanumeric characters and hyphens, and must not contain only digits. if you use only non-ASCII characters in a vApp template name.

  • In locales other than English, object lists can be filtered only by columns that contain user-generated content
    When you use vCloud Director in locales other than English, the filter function on object lists only works when you filter using columns that contain user-generated content, such as Name or vApp Name.

  • Some localized messages appear in English on Red Hat Enterprise Linux and CentOS 6.x
    On Red Hat Enterprise Linux and CentOS 6.x, some vCloud Director cells do not detect the correct locale at first start up or when the operating system is rebooted, which causes some messages to appear in English.

    Workaround: Manually restart the cell by running the command /opt/vmware/vcloud-director/bin/vmware-vcd restart.

  • Repeated prompts to install the VMware Client Integration Plug-in appear when importing a file into a catalog or opening a virtual machine console from a Windows account that contains non-ASCII characters
    When you attempt to import a file into a vCloud Director catalog or open a virtual machine console from a Windows account that has non-ASCII characters in its name, vCloud Director prompts you to install the VMware Client Integration Plug-in. This happens even when the plug-in is already installed.

    Workaround: Log in to the Windows administrator account or a user account that contains only ASCII characters in its name, and upload the file or open the virtual machine.

  • Attempts to use a network backed by a vCloud Network Isolation network pool fail
    When you attempt to use a network backed by a vCloud Network Isolation network pool, the operation fails. This occurs because new installations of vCloud Director no longer push the host agent to ESX by default.

    Workaround: After adding a vCloud Network Isolation network pool, re-prepare the hosts on vCloud Director.

    1. In the vCloud Director Web client, click the Manage & Monitor tab and click Hosts in the left pane.
    2. Right-click the host name and select Prepare Host.
    3. Type a user name and password and click OK.
  • Attempts to power on a vApp in an allocation pool organization virtual data center when the provider virtual data center has multiple resource pools sometimes fail
    When you create an allocation pool organization virtual data center on a provider virtual data center that is attached to multiple resource pools, only virtual machines placed on the first resource pool can successfully power on.

    Workaround: Enable elastic allocation pools.

    1. In the vCloud Director Web client, click the Administration tab and click General in the left pane.
    2. Select Allow allocation pools to be elastic and click Apply.
  • Virtual machine usage graph displays an incorrect time stamp for the first data point
    The first data point on a virtual machine usage graph always displays a time stamp of between 20 seconds and five minutes before the second data point, regardless of when the first data point is actually collected.
  • Attempts to disconnect a NIC from a powered on virtual machine fail
    When you request a hot disconnect of a NIC by using the UI or API, the request fails with a message similar to the following.

    The attempted operation cannot be performed in the current state (Powered on).

  • A virtual machine's popped-out console displays a blank screen with disconnected status when using the Google Chrome or Mozilla Firefox browsers and the virtual machine's name uses non-ASCII characters
    When you are using the Google Chrome or Mozilla Firefox browser and you pop out a virtual machine's console from the vCloud Director Web Console, the console might display a black screen and disconnected status if the virtual machine's name contains non-ASCII characters.

    Workaround: Use Microsoft Internet Explorer browser to open the virtual machine's console.

  • Attempts to upload an OVF sometimes fail
    When creating a vApp by uploading an OVF package, sometimes the deployment fails with a namespace error.

    Workaround: Upload the OVF into vCenter Server, and then in vCloud Director import the OVF from vCenter Server into a catalog as a vApp template.

  • Attempts to upload or download an OVF or configure joint IPSEC VPN on Google Chrome fail
    When you try to use the vCloud Director Web Console in the Google Chrome browser to perform an OVF upload or download operation, or configure joint IPSEC VPN, a message might appear saying that the operation is not supported in your browser.

    Google Chrome no longer supports OVF upload/download due to the removal of the NPAPI support within Chrome.

    Workaround: To perform OVF upload or download operations, use the VMware OVF Tool. The OVF Tool and its User Guide are available on the OVF Tool Documentation page.

    Instead of configuring IPSEC VPN jointly, configure them separately. See Create a VPN Tunnel to a Remote Network.

  • Deprecated Link element in an AdminOrg element
    Beginning with vCloud API version 5.6, the following Link, which is returned in an AdminOrg element, is deprecated.

    <Link
    rel="task:create"
    href="https://.../api/tasksList/{id}"
    type="application/vnd.vmware.vcloud.task"/>

    The value of the type attribute in this Link is incorrect. The Link will be removed in a future release of vCloud Director. Beginning with vCloud API version 5.6, a new Link with the correct type attribute is also returned in an AdminOrg element.

    <Link
    rel="task:create"
    href="https://.../api/tasksList/{id}"
    type="application/vnd.vmware.vcloud.task+xml"/>

    Client applications should replace references to the deprecated Link with references to its replacement.