Recover from failure while applying the NSX configuration during Convert/Import operation

Products

• VMware SDDC Manager

Issue/Introduction

This issue is found in the following setup / scenario:

• vCenter has 2 or more clusters
• During Convert/Import, some failure occurs during NSX configuration of one of the clusters.
• The failure is such that, on retry also, NSX configuration won't be successful.
• Removing the cluster from the VC and retry will not resolve this issue.

Environment

VCF 9.0

Resolution

We need to execute the following steps to recover from this failure:

For TransportNodeCollection failure on Import:
1.

1. If the failure is because of any host in the cluster, try to resolve the issue with the host or remove the host and then retry the Import workflow.
2. If the above doesn't resolve the issue, then
   1. Remove the cluster from the vCenter.
   2. Since NSX is already deployed, trigger import again through API with useExisting NSX as true and domain-name as the same name given during initial import, Sample spec :
      
      
      curl -k -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" -X POST -d @importRequest.json https://localhost/v1/sddcs/imports
 
importRequest.json : 
    
{
  "vcenterAddress": "VCENTER_FQDN",
  "vcenterSsoUsername": "administrator_SSO_USERl",
  "vcenterSsoPassword": "administrator_SSO_PASSWORD",
  "vcenterRootSshPassword": "VCENTER_ROOT_PASSWORD",
  "skipEsxThumbprintValidation": true,
  "vcenterSslThumbprint": "[VCENTER_SSL_THUMBPRINT]",
  "domainName": "[WORKLOAD_DOMAIN_NAME]",    <------------same domain name as of initial import
  "nsxtSpec": {
    "useExistingDeployment": true,
    "vipFqdn": "NSX_VIP_FQDN",
    "nsxtAuditPassword": "AUDIT_USER_PASSWORD",
    "rootNsxtManagerPassword": "ROOT_USER_PASSWORD",
    "nsxtAdminPassword": "ADMIN_USER_PASSWORD",
    "enableEdgeClusterSync": false,
    "sslThumbprint": "NSX_SSL_THUMBPRINT",
    "nsxtManagers": []
  }
}
      
      
   3. This will identify that the domain is in ACTIVATING state and roll back the domain details, do the discovery again and import will succeed.

 

For TNC failure on Convert:

1. If the failure is because of any host in the cluster, try to resolve the issue with the host or remove the host and then retry the Convert workflow.
2. If the above doesn't resolve the issue, then do the following:
   1. Remove the SDDC Manager vm if deployed if not converting VCF Installer to sddc-manager
   2. Remove the SDDC Manager extension : com.vmware.sddcManager from vCenter.
   3. If the VCF Installer is converted to SDDC Manager, remove the vcf-installer and deploy VCF Installer again.
   4. Trigger the convert from new VCF Installer, choose useExistingDeployment as true for NSX. Environment should be converted successfully with this.