Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

How to create a Stretched cluster on a NSX-T Workload Domain on VMware Cloud Foundation on VxRail 3.8 environment (74582)

Last Updated: 9/4/2019Categories: InformationalTotal Views: 2995Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

Theis article describes how to deploy a NSX-T based Workload domain on a VMware Cloud Foundation on VxRail 3.8 environment with a stretch cluster where the management, vMotion, vSAN, and vTEP networks are Layer 2 stretched between both availability zones. While this deployment model is supported it is not the recommended and preferred deployment model.

Prerequisite
Deploying a VSAN stretched Cluster on a NSX-T Workload Domain is not a functionality currently available in VMware Cloud Foundation on VxRail. Below are the prerequisites required to successfully complete this workflow.

Enough VSAN and ESXi licenses : VSAN and ESXi licenses ( CPUs) must be adequate

Naming conventions:

Host group : {Cluster-Name}_primary-az-hostgroup , {Cluster-Name}_secondary-az-hostgroup

VM group: {Cluster-Name}_primary-az-vmgroup

Preferred site: {Cluster-Name}_primary-az-faultdomain

Secondary Site: {Cluster-Name}_secondary-az-faultdomain

Number of ESXi hosts on preferred site/primary-az-hostgroup should be equal to number of hosts on secondary site/secondary-az-hostgroup.

Complete bringup of the environment following the Administration Guide.

Resolution

Deploy a NSX-T workload domain
To deploy a NSX-T workload domain and add required clusters follow these steps.

Deploy and configure Witness host

Deploy the Witness appliance following the VSAN documentation on an environment outside the VMware Cloud Foundation on VxRail rack but with access to the same management and vsan network.

Once the Witness appliance is deployed, access web console of the Witness Appliance and configure Management network and DNS appropriately and enable SSH.

Add the Witness Appliance as a host to the "Workload vCenter" of the VMware Cloud Foundation on VxRail environment as a standard host at the Datacenter level, it should not be part of any cluster.

Once Witness is added as host, access the Host in the vCenter Web Client and navigate to Configure ->Networking -> VMKernel Adapter. Configure the IP address details for vmk1 associated to the proper DVS.

Provide IP routing rules for the VSAN networks for the hosts in AZ1 and AZ2.

Expand a NSX-T enabled cluster
NSX-T enabled cluster is expanded using the expansion procedure from the SDDC Manager. Ensure there are even number of hosts (minimum 6 ) in the cluster so that they can be divided up into AZ1 and AZ2.

Create fault domains and other stretch cluster related configurations
Complete the below steps to enable a stretched VSAN Cluster.

Access vCenter Server Web Client associated with the desired cluster.

Navigate to the vSAN cluster.

Click the Configure tab.

Under vSAN, click Fault Domains.

Click the Stretched Cluster Configure button to open the stretched cluster configuration wizard.

Select the hosts or the fault domain that you want to assign to the secondary domain and click >>.The hosts that are listed under the Preferred fault domain are in the preferred site.

Click Next.

Select a witness host that is not a member of the vSAN stretched cluster and click Next.

Claim the storage devices on the witness host and click Next.

Select one flash device for the cache tier, and one or more devices for the capacity tier.

On the Ready to complete page, review the configuration and click Finish.

Navigate to Configure -> Services and complete the below configurations for the cluster.

In vSphere Availability, Set Admission Control, the Host failures cluster tolerates needs to be set to 50% of the cluster. If the stretched cluster is a total of  8 hosts this value will be 4.

In vSphere Availability -> Advanced Options, set VSAN gateway as isolated address as following:  das.isolationaddress1=<VSAN-GATEWAY-IP-for-preferred-site-hosts>

Navigate to VM/Host Groups and click Add to create two host groups, one for the preferred site and one for the secondary site.

In VM/Host Groups create two VM groups, one to hold the VMs on the preferred site and one to hold the VMs on the secondary site.

In VM/Host Rules the HA settings should respect VM-Host affinity rules during failover.

Navigate to Policies and Profiles and edit the vSAN profile associated with the cluster. In the vSAN panel, under the Availability tab, set the following:

Site disaster tolerance to Dual Site Mirroring (stretched cluster)

Failure to tolerate is set to 1 failure - Raid-1  (Mirroring).

Day-N operations on a Stretched Cluster

Adding host to the stretched cluster.

Removal of a host from the stretched cluster.

Upgrading the stretched cluster through LCM.

Additional ESXi Hosts can be added through the Add Host workflow in the SDDC Manager by following these steps.

Once a host is added to a stretched cluster, follow the below instructions to make the host part of the fault domains.

Once host is added to the stretched cluster, in the vCenter Web Client the cluster will have a critical alarm for  "VSAN Health Alarm "Unexpected number of fault domains". This is generated as the ESXi host that was added is not part of any of the fault domains.

Select Cluster -> Configuration -> Fault Domains.

Select the ESXi host, which is not part of any of the fault domain, click on the "Move to fault domain" icon and select the fault domain the ESXi host should be part of.

Upgrading Stretch Cluster

ESXi hosts that are part of the SDDC Manager inventory, except VSAN Witness Host, will be upgraded through SDDC Manager's LCM functionality.

NSX-T upgrade will also be handled by through SDDC Manager's LCM functionality.

Upgrade the vSAN Witness Host

The Witness appliance upgrade is performed manually outside of the SDDC Manager.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
vRealize Network Insight 3.9 および 4.0 へのアップグレードに必要なアップグレード前のパッチ (71014)

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware Cloud Foundation on VxRail

VMware Cloud Foundation

Related Versions:

VMware Cloud Foundation on VxRail 3.8.x

Take Our Survey

Support Assistant