Unable to complete a Stretched Cluster Workflow for a Workload Domain using an L2-stretched Network for vSAN

Products

• VMware Cloud Foundation

Issue/Introduction

This article provides instructions on how to complete a Cloud Foundation stretch cluster workflow when using L2 stretched network for vSAN.

Symptoms:

Unable to complete the Stretched Cluster Workflow for a Workload Domain
 

The following errors are seen in SDDC Manager
 

Error - Message: null value in entry: das.isolationaddress0=null
 

The following errors are seen in /var/log/vmware/vcf/domainmanager/domainmanager.log
 

Error -[{"key":"das.ignoreInsufficientHbDatastore","value":"true"},{"key":"das.ignoreRedundantNetWarning","value":"true"},{"key":"das.includeFTcomplianceChecks","value":"fal
se"},{"key":"das.iostatsInterval","value":"0"},{"key":"das.isolationaddress1","value":"172.16.2.1"},{"key":"das.respectVmVmAntiAffinityRules","value":"true"}

 

Error - VALIDATE_HA_ADVANCED_OPTIONS_FAILED Postvalidtion HA advanced options failed for cluster {0}
com.vmware.evo.sddc.orchestrator.exceptions.OrchTaskException: Postvalidtion HA advanced options failed for cluster {0}

Environment

VMware Cloud Foundation 3.0.x

Cause

The Stretched Cluster Workflow for a VI Workload Domain expects two das.isolation addresses to complete successfully, when L3 is used for the vSAN network we use the default gateway of the vSAN Network from each Availability Zone.  However when L2 is used only a single default gateway is available.

Resolution

Edit the Postgres Database to add a second das.isolation address

 

1 .Use the vcf account to connect to the SDDC Manager over Secure Shell (SSH)

 

ssh [email protected]

 

2. Switch to the root user

 

su –

 

3. Connect to the Postgres Database to temporarily modify the host gateway field.  This field is added to the Postgres Database during the Cloud Foundation Bring-up procedure, modifying this field will not update the default gateway on the ESXi hosts. 

 

Note: This IP Address must be accessible from the vSAN Network.

 

psql -U postgres -h localhost

\c platform

select gateway from host;

gateway
--------------
172.16.11.1 
172.16.11.1 
172.16.11.1 
172.16.11.1 

(10 rows)

platform=#update host set gateway='172.16.11.253';

platform=# \q

 

4. Open the SDDC Manager UI and restart the Stretched Cluster Workflow task

 

5. Once the Stretched Cluster Workflow task has completed successfully, repeat Step 3 to change the gateway back to its original setting (172.16.11.1).