VMware Validated Design for Software-Defined Data Center 2.0 Release Notes

Updated on: 12 SEP 2016

VMware Validated Design for Software-Defined Data Center 2.0 | 21 JUL 2016

Check for additions and updates to these release notes.

What's in the Release Notes

The release notes cover the following topics:

About VMware Validated Design for Software-Defined Data Center 2.0

VMware Validated Design provides a set of prescriptive documents that explain how to plan, deploy, and configure a Software-Defined Data Center (SDDC). The architecture and the detailed design are dual-region ready, and the deployment guide provides instructions about configuring a single region.

VMware Validated Designs are tested by VMware to ensure that all components and their individual versions work together, scale, and perform as expected. Unlike Reference Architectures which focus on individual products, a VMware Validated Design is a holistic approach to design, encompassing many products in a full stack for a particular use case scenario such as building an SDDC.

This VMware Validated Design supports a number of use cases and is optimized for integration, expansion, day 2 operations, as well as future upgrades and updates. As new products are introduced, and new versions of existing products are released, VMware continues to qualify the cross-compatibility and upgrade paths of the VMware Validated Designs. Designing with a VMware Validated Design ensures that future upgrade and expansion options are available and supported.

VMware Validated Design for Software-Defined Data Center 2.0 features the following VMware products:
  • ESXi
  • vCenter Server Appliance
  • Virtual SAN
  • NSX for vSphere
  • vRealize Operations Manager
  • vRealize Automation
  • vRealize Orchestrator
  • vRealize Log Insight
  • vRealize Business for Cloud
  • vSphere Data Protection

For detailed information about the SDDC model that is supported in this validated design, the full list of products, content packs, plug-ins, and versions, see the Introducing the VMware Validated Design for SDDC documentation.

What's New

VMware Validated Design for Software-Defined Data Center 2.0 provides the following new features:
  • Updated Bill of Materials that incorporates all new product versions, in particular the inclusion of vRealize Automation 7.0
  • Enhanced dynamic routing design that optimizes the management and tenant workloads
  • A streamlined vRealize Log Insight installation process
  • Greatly simplified network architecture of the management pod
For more information, see the VMware Validated Design for Software-Defined Data Center 2.0 page.

Internationalization

This VMware Validated Design release is available only in English.

Compatibility

This VMware Validated Design guarantees that product versions in the VMware Validated Design for Software-Defined Data Center 2.0 document, and the design chosen, are fully compatible. Minor known issues exist and are described in this release notes document.

Installation

To install and configure an SDDC according to this validated design, follow the guidance in the VMware Validated Design for Software-Defined Data Center 2.0 documentation. For product versions, product download information, and guides download, see the VMware Validated Design for Software-Defined Data Center 2.0 page.

Caveats and Limitations

To install vRealize Automation, you must open certain ports in the Windows firewall. This VMware Validated Design instructs that you disable the Windows firewall before you install vRealize Automation. It is possible to keep Windows firewall active and install vRealize Automation by opening only the ports that are required for the installation. This process is described in the vRealize Automation Installation and Configuration documentation.

Known Issues

The known issues are grouped as follows.

vCenter Server
  • Heavy access of the Platform Services Controller Appliance 6.0 causes VMware Identity Management Service to crash

    The vCenter Server Web client becomes inaccessible and produces the following exception:

    HTTP Status 500 - Request processing failed; nested exception is java.lang.IllegalStateException: BadRequest

    Workaround: See VMware Knowledge Base article KB 2144070

Virtual SAN
  • Virtual SAN datastores run out of disk space unusually fast due to thick provisioned OVA and OVF files

    When deploying OVA and OVF files on Virtual SAN datastores, the vSphere Web Client provides thick provisioning for virtual machine disks.
    As a result, datastores can quickly run out of disk space.

    Workaround: See VMware Knowledge Base article KB 2145798.

vSphere Data Protection
  • The vSphere Web Client stops responding when you attempt to connect to the vSphere Data Protection appliance version 6.1.2

    An issue in vSphere Data Protection version 6.1.2 prevents the vSphere Data Protection plug-in in the vSphere Web Client from connecting to the vSphere Data Protection appliance if the appliance uses a distributed switch for networking.

    Workaround: Contact VMware Technical Support.

  • After you restore a Platform Services Controller appliance, you might not be able to enable the Bash shell or some services might not be started

    After you restore a Platform Services Controller appliance, you might encounter one or more of the following issues:

    • If you run the shell.set --enabled True command to enable the Bash shell on a restored Platform Services Controller virtual appliance, the following error might appear:

      Command> shell.set --enabled True
      Unknown command: 'shell.set'
      Command> shell
      Shell is disabled

       
    • Running the psc_restore script fails to restore the Platform Services Controller. Not all services of Platform Services Controller start, synchronization with the partner Platform Services Controller fails, and so on.

    Workaround: Restore the Platform Services Controller from another restore point in vSphere Data Protection.
     

vRealize Automation
  • vRealize Automation is inaccessible when the NSX for vSphere Edge Load Balancer health monitor is down

    If the NSX for vSphere Edge Load Balancer health monitors in vRealize Automation display a Down status, vRealize Automation becomes inaccessible. You can verify this condition by checking the log file for a failed Pool Status with error code 304.

    Workaround: Reboot the secondary vRealize Automation appliance vra01svr01b.

  • vRealize Automation multi-machine VM provisioning request fails with an insufficient resources error

    A multi-machine provisioning request in vRealize Automation fails with the following error message:

    Error processing [PowerOn], error details: [] - Insufficient resources.

    This issue occurs if during a previous delete request the vRealize Orchestrator Plug-In for NSX failed to delete the VXLANs after deleting the associated NSX Edge. As a result, the plug-in did not release all resources associated with the delete request.

    The vRealize Automation logs show the following error:

    VSM response error (841): virtualwire-xxx resources are still in use.

    Workaround: See VMware Knowledge Base article KB 2143951.

  • vRealize Automation large inventory data collections for vCenter Server might fail if your vSphere cluster contains a large number of objects

    If you plan to use a VMware vSphere cluster that contains a large number of objects, such as 3000 or
    more virtual machines, modify the manager service configuration file with larger values. If you do not modify this
    setting, large inventory data collections might fail.

    Workaround: Modify the default value of the ProxyAgentBinding and maxStringContentLength in the ManagerService.exe.config file.

    1. Open the ManagerService.exe.config file in a text editor. By default this file resides at C:\Program Files (x86)\VMware\vCAC\Server.
    2. Locate the binding name and readerQuotas lines in the file.
      <binding name=”ProxyAgentServiceBinding” maxReceivedMessageSize=”13107200”>
      <readerQuotas maxStringContentLength=”13107200” />
      
      Note: Do not confuse these two lines with the similar lines with the binding name ProvisionServiceBinding.
    3. Replace the values assigned to the maxReceivedMessageSize and maxStringContentLength attributes with a larger value. How much larger depends on how many objects you expect your vSphere cluster to contain. You can increase these values by a factor of 10 for testing.
    4. Save your changes and close the file.
    5. Restart the vRealize Automation manager service.
  • vRealize Automation converged blueprint provisioning request fails

    The converged blueprint provisioning request fails with the error message: Internal error in processing component request: org.springframework.web.client.ResourceAccessException: I/O error on POST request.

    Workaround: None.

  • vRealize Automation converged blueprint provisioning request might fail due to a failure to create a logical switch

    The converged blueprint provisioning request fails with the error message:
    [Error code: 44010 ] - [Error Msg: Error executing vRealize Orchestrator workflow [VSM response error (800): Error creating network vxw-dvs-23-universalwire-3087-sid-27281-DBN-e6878823-acde-4c5f-8b15-8d5f7a25ea10 - Error while waiting for the portgroup to be created.. (Workflow:Create logical switch / Scriptable task (item1)#4)]]

    Workaround: None.

vRealize Operations Manager
  • You might not be able to access vRealize Operations Manager from the vSphere Web Client in the case of many simultaneous requests for access

    vRealize Operations Manager does not register with vCenter Server with the virtual IP (VIP) address that is allocated on the load balancer but with the address of an individual node from the analytics cluster. As a result, when you start the vRealize Operations Manager user interface from the vSphere Web Client, the vSphere Web Client redirects you to this node instead of to the load-balanced VIP.

    The access to the vRealize Operations Manager user interface is not load-balanced if you launch it from the vSphere Web Client. The node to which the vSphere Web Client redirects you might become overloaded and you might be unable to access vRealize Operations Manager.

    Workaround: Log in to vRealize Operations Manager directly at the VIP address (https://vrops-cluster-01.rainpole.local) instead of from the vSphere Web Client.

VMware Validated Design Content
  • New An attempt to log in to the virtual machine of a vRealize Automation Windows component to install the vRealize Log Insight Agent fails

    According to the vRealize Log Insight Implementation section of the VMware Validated Design Deployment Guide for Region A, when you install the vRealize Log Insight agents, you log in to the vRealize Automation Windows virtual machines by using a user name vrli_admin_user. A user vrli_admin_user is not present in the configuration of the Active Directory in this design and you cannot use this account to log in.

    Log in by using a Windows administrator account.

  • New An attempt to run the psc_restore command on the Platform Services Controller connected to the Management vCenter Server fails

    According to the Backup and Restore Guide, you run the following command to start a restore operation on the Platform Services Controller that is connected to the Management vCenter Server:

    psc_restore -u administrator@vsphere.local -p vsphere_admin_password

    Because administrator@vsphere.local is not a valid account on the Platform Services Controller operating system, the command completes with an error about invalid user credentials.

    Workaround: Run the psc_restore command with the following user credentials:

    psc_restore -u administrator -p vsphere_admin_password