VMware Validated Design 6.1 | 06 OCT 2020
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 6.1
- VMware Software Components in the Validated Design
- What's New
- Updated Upgrade
- Life Cycle of the VMware Software Components
- Caveats and Limitations
- Deployment of the Management Domain with VLAN-Backed Networks
- Documentation Delivery Log
- New Resolved Issues
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, the detailed design, and the deployment guides provide instructions about configuring a dual-region SDDC.
VMware Validated Design is 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 an individual product or purpose, a VMware Validated Design is a holistic approach to design, encompassing many products in a full stack for a broad set of use case scenarios in 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 VMware Validated Design. Designing with a VMware Validated Design ensures that future upgrade and expansion options are available and supported.
VMware Validated Design 6.1 is based on a set of individual VMware products with different versions that are available in a common downloadable package.
The products included in VMware Validated Designs participate in the VMware's Customer Experience Improvement Program ("CEIP"). Join the CEIP because this program provides us with information used to improve VMware products and services, fix problems, and advise you on how best to deploy and use our products.
Details regarding the data collected through CEIP and the purposes for which it is used by VMware are set forth at the Trust & Assurance Center at http://www.vmware.com/trustvmware/ceip.html. To join or leave the CEIP for the products that are part of VMware Validated Design, see the documentation for each product.
Before you deploy or upgrade the SDDC, review the release notes of the software components that are used in this validated design.
|Product Group and Edition||Product Name||Product Version||Release Notes|
|VMware Cloud Foundation Enterprise||VMware Cloud Foundation||4.1*||VMware Cloud Foundation 4.1 Release Notes|
|VMware vSphere Enterprise Plus||ESXi||7.0 Update 1*||VMware ESXi 7.0 Update 1 Release Notes|
|vCenter Server||7.0 Update 1*||VMware vCenter Server 7.0 Update 1 Release Notes|
|VMware vSAN Standard or higher||vSAN||7.0 Update 1*||VMware vSAN 7.0 Update 1 Release Notes|
|vSAN Witness Appliance||
7.0 Update1 *
Download the appliance from its location on My VMware.
|VMware NSX Data Center Advanced or higher||NSX-T Data Center||3.0.2 *||VMware NSX-T Data Center 3.0.2 Release Notes|
|VMware Workspace ONE Access||VMware Workspace ONE Access||3.3.2||VMware Identity Manager 3.3.2 Release Notes|
|VMware vRealize Suite Lifecycle Manager||vRealize Suite Lifecycle Manager||8.1 Patch 1|
|VMware vRealize Operations Manager Advanced or higher||vRealize Operations Manager||8.1.1 *||vRealize Operations Manager 8.1.1 Release Notes|
|vRealize Operations Management Pack for VMware Identity Manager||1.1||VMware vRealize Operations Management Pack for VMware Identity Manager 1.1 Release Notes|
|vRealize Operations Management Pack for Storage Devices||8.0||VMware vRealize Operations Management Pack for Storage Devices 8.0 Release Notes|
|VMware vRealize Log Insight||vRealize Log Insight||8.1.1||vRealize Log Insight 8.1.1 Release Notes|
|vRealize Log Insight Content Pack for NSX-T||Updated 3.9|
|vRealize Log Insight Content Pack for Linux||2.1|
|vRealize Log Insight Content Pack for Linux - Systemd||1.0|
|New vRealize Log Insight Content Pack for vRealize Suite Lifecycle Manager 8.0.1+||1.0*|
|New vRealize Log Insight Content Pack for VMware Identity Manager||2.0*|
|VMware vRealize Automation Advanced or higher||vRealize Automation||8.1 Patch 2 *|
|*||Updated from the earlier release of VMware Validated Design|
VMware makes available patches and releases to address critical security and functional issues for several products. Verify that you are using the latest security and express patches or hotfixes for a given component available by using SDDC Manager after deploying VMware Validated Design. Scalability and functionally tests for individual patches, express patches, or hotfixes are not typically performed against VMware Validated Design. If a patch must be applied to your environment, follow the VMware published practices and VMware Knowledge Base articles for the specific patch. If an issue occurs during or after the process of applying a patch, contact VMware Technical Support. If after applying a patch, the new product version no longer adheres to the bill of materials, or interrupts the upgrade to the next published version of the design, you must continue to follow the upgrade path to a version of the design that includes this product version.
VMware Marketplace and in-product marketplace store only the latest versions of the management packs for vRealize Operations Manager and the content packs for vRealize Log Insight. The software components table contains the latest versions of the packs that were available at the time this VMware Validated Design was validated. When you deploy the VMware Validated Design components, it is possible that the version of a management or content pack on VMware Solution Exchange and in-product marketplace is newer than the one used for this release.
For information on the life cycle of the VMware software components in this VMware Validated Design, see Life Cycle of the VMware Software Components.
VMware Validated Design 6.1 provides a list of new features:
- Updated Bill of Materials that incorporates new product versions.
- VMware Validated Design uses vRealize Suite Lifecycle Manager in VMware Cloud Foundation mode.
vRealize Suite Lifecycle Manager in VMware Cloud Foundation mode is integrated with SDDC Manager for automated deployment of vRealize Suite products in synchronization with the SDDC inventory and connection to deployed workload domains.
- Planning and Preparation Workbook now contains a sizing section and the naming convention that is used in VMware Validated Design 6.0.x and 6.1.
Use the sizing section for determining the compute and storage resource requirements for your management domain according to the scale of your SDDC deployment.
- VMware Validated Design now supports vSAN witness traffic separation for setups with multiple availability zones.
The vSAN witness traffic is placed on the management network and the requirement to have jumbo frames between the availability zones and witness site is no longer present.
- Starting with this release, vSphere Distributed Switch Health Check is not enabled anymore because the distributed switch configuration required for NSX-T leads to generation of irrelevant warnings.
- SDDC startup and shutdown guidance for both VMware Cloud Foundation and VMware Validated Design.
For more information, see the VMware Validated Design Documentation page.
This VMware Validated Design release is available only in English.
This VMware Validated Design guarantees that product versions in the VMware Validated Design 6.1, and the design chosen, are fully compatible. Any minor known issues that exist are described in this release notes document.
To install and configure an SDDC according to this validated design, follow the guidance in Deployment of the Management Domain in the First Region, Deployment of a Virtual Infrastructure Workload Domain in the First Region, Deployment of a vSphere with Tanzu Workload Domain in the First Region, and Deployment of Cloud Operations and Automation in the First Region.Upgrade documentation.
This VMware Validated Design version is based on one or more VMware products whose versions eventually reach the End of Support Life (EOSL) stage as described by the VMware Lifecycle Policies.Тhose versions are no longer generally supported by VMware. In such a case, upgrade to a later version by using the upgrade procedures in the VMware Validated Design Upgrade documentation.
If you are using an earlier version in your environment, upgrade your environment according to the following scenarios:
|The version of VMware Validated Design that you are using has already entered the EOSL stage but the next VMware Validated Design version is still supported.||Apply the VMware Validated Design Upgrade documentation to bring the VMware environment to a fully supported state|
|The version of VMware Validated Design that you are using and the next version have both already entered the EOSL stage||Because the VMware Validated Design Upgrade documentation supports upgrade only from one release to the next one, the transition across multiple releases might be complex. Contact a VMware sales representative to plan and perform a custom upgrade procedure with the assistance of VMware Professional Services.|
For more information about current and expired product releases, refer to the VMware Lifecycle Product Matrix
- The SDDC configuration in this release includes a single region with two availability zones.
VMware Validated Design 6.1 has been developed with design objectives that included multi-region and disaster recovery use cases. At the time of this release, because of architecture limitations in some of the products within the SDDC stack, providing prescriptive guidance that would meet the full set of design objectives for extending a VMware Validated Design deployment to a second region is not possible.
- Upgrade guidance from VMware Validated Design 5.1.1 to VMware Validated Design 6.0.x and VMware Validated Design 6.1 is not available.
- The migration coordinator of NSX-T Data Center covers partially the SDDC topology in this design.
- At the time of publishing this design, a direct migration path from vRealize Automation 7.6 to vRealize Automation 8.1 is not available.
- Use of a shared NSX-T Manager cluster for multiple workload domains is not implemented.
vRealize Automation 8.1 does not support adding more than one workload domain that shares an NSX-T Data Center instance, for example, many:1:many. You can associate one NSX-T cloud account to only one vCenter Server cloud account.
Consolidated SDDC architecture is not available for this release.
For best support of vSphere with Tanzu workload domains, SDDC Manager is configured to apply ESXi patches and updates by using vSphere Lifecycle Manager baselines.
To provide a user-friendly object naming across the SDDC, to deploy workload domains, you call the SDDC Manager API with a JSON specification instead of using the SDDC Manager user interface.
rainpole.iotop-level domain replaces
vSphere with Tanzu supports limited use of
.localas a top-level domain.
- Мulti-tenancy for vRealize Automation is not enabled.
- Using the vRealize Log Insight Content Packs for vRealize Automation and vRealize Orchestrator is not part of the design.
Earlier versions of VMware Validated Design include vRealize Log Insight Content Packs for earlier versions of vRealize Automation and vRealize Orchestrator. At the time of publishing this design, content packs for vRealize Automation 8.1 and vRealize Orchestrator 8.1 are not available.
You configure the initial integration of vRealize Automation with virtual infrastructure workloads domain manually instead of using the vCenter Server Quickstart option in vRealize Automation.
When adding an NSX-T cloud account, the Quickstart uses the default admin user for NSX-T Manager from the SDDC Manager inventory. You are unable to pass a service account that is managed by Workspace ONE Access because of a design limitation.
The QuickStart assumes the use of native virtual machines templates but this design uses the integration with the vSphere Content Library because vSphere Content Library provides native replication and versioning of common virtual machine templates across workload domains.
- You enable the vSAN stretched cluster in the management domain and a virtual infrastructure workload domain by using the SDDC Manager API. The names of the distributed port groups for Availability Zone 2 that are created by SDDC Manager derive from the names of the distributed port groups for Availability Zone 1, introducing deviation from the naming convention in this VMware Validated Design.
- VMware Skyline is not supported. At the time of publishing this design, VMware Skyline is not interoperable with NSX-T Data Center.
- VMware Site Recovery Manager and VMware vSphere Replication are not in scope of this release because of the limitations in multi-region support.
In VMware Validated Design 6.1, you connect Workspace ONE Access and the vRealize Suite products to virtual network segments in NSX-T Data Center. This approach provides support for BGP-based dynamic routing for improved mobility and security of the management applications. As an alternative, you can use VLAN-backed network segments with static routes in NSX-T Data Center. See VMware Knowledge Base article 80864.
The VMware Validated Design documentation is published in several iterations. On the release date, the core documents that introduce VMware Validated Design and provide guidance on the SDDC design, planning, and deployment are published live. The remaining documents are released in groups until the entire set is compliant with the Bill of Materials of the VMware Validated Design release.
|20 OCT 2020||
|06 OCT 2020||
All documentation is available on the VMware Validated Design Documentation page.
- Updated You are unable to update NSX-T Data Center in the management domain or in a workload domain with vSAN principal storage because of an error during the NSX-T transport node precheck stage
In SDDC Manager, when you run the upgrade precheck before updating NSX-T Data Center, the NSX-T transport node validation results with the following error.
No coredump target has been configured. Host core dumps cannot be saved.:System logs on host sfo01-m01-esx04.sfo.rainpole.io are stored on non-persistent storage. Consult product documentation to configure a syslog server or a scratch partition.
Because the upgrade precheck results with an error, you cannot proceed with updating the NSX-T Data Center instance in the domain. VMware Validated Design supports vSAN as the principal storage in the management domain. However, vSAN datastores do no support scratch partitions. See VMware Knowledge Base article 2074026.
Workaround: Part of the guidance so that you can complete the upgrade process following a single documentation source. See Prepare for Updating NSX-T Data Center in the Upgrade documentation.
- Updated BGP validation during automated deployment of the management domain or a workload domain fails
During bring-up of the management domain by using VMware Cloud Builder or deployment of a workload domain by using SDDC Manager, the BGP validation step fails.
BGP peering is not established on the VLANs for Uplink 1 and Uplink 2 because the mapping between the Uplink1 and Uplink2 port groups on the distributed switch for the domain and the physical adapters on the hosts is reversed. Uplink1 is assigned to vmnic1 and Uplink2 to vmnic0. As a result, the traffic from Uplink 1 is sent to the top of rack switch for Uplink 2 and from Uplink 2 to the top of rack switch for Uplink 1.
Workaround: Part of the guidance so that you can complete the deployment process following a single documentation source. See Change the Allocation of Host Network Adapters to the Distributed Uplink Port Groups for the Management Domain in Region A in Deployment of the Management Domain in the First Region, Change the Allocation of Host Network Adapters to the Distributed Uplink Port Groups for the Virtual Infrastructure Workload Domain in Region A in Deployment of a Virtual Infrastructure Workload Domain in the First Region, and Change the Allocation of Host Network Adapters to the Distributed Uplink Port Groups for the Virtual Infrastructure Workload Domain in Region A in Deployment of a vSphere with Tanzu Workload Domain in the First Region.