SDDC bring up failure via the cloud builder with error: HA Isolation IP Address cannot be blank Invalid parameter: HA Isolation IP Address cannot be blank
search cancel

SDDC bring up failure via the cloud builder with error: HA Isolation IP Address cannot be blank Invalid parameter: HA Isolation IP Address cannot be blank

book

Article ID: 382541

calendar_today

Updated On:

Products

VMware Cloud Foundation VMware SDDC Manager

Issue/Introduction

  • SDDC Bring-up has completed with failure
    Invalid parameter: HA Isolation IP Address cannot be blank Invalid parameter: HA Isolation IP Address cannot be blank
  • Error in /opt/vmware/bringup/logs/vcf-bringup.log
    yyyy-mm-ddThh:mm:ss [bringup,xxxxxxxxxxxxxxxxxxx,yyyy] ERROR [c.v.e.s.o.model.error.ErrorFactory,pool-2-thread-13] [94KVS8] VCF_ERRORS_GENERIC_INPUT_PARAM_ERROR Invalid parameter: HA Isolation IP Address cannot be blank
    com.vmware.evo.sddc.common.core.error.InvalidInputException: Invalid parameter: HA Isolation IP Address cannot be blank
         

Environment

VMware cloud foundation

Cause

The cause for the bring up failure could be varied. 

 For the error "Invalid parameter: HA Isolation IP Address cannot be blank Invalid parameter: HA Isolation IP Address cannot be blank", one of the possible cause is due to vSan, vMotion gateway being blank

Resolution

 

  1. Update vSan, vMotion Gateway value in Bringup XLS or the input json

    • If the vSAN / vMotion network is non-routable and do not have a Gateway address then provide the Management network Gateway as vSAN / vMotion Gateway and skip gateway ping validation by providing the following top level element in the input Json
      "skipGatewayPingValidation": true
  2. Restart the workflow via API
    1. Copy Bringup XLS to the Cloud Builder VM (using a utility like WinSCP, Filezilla etc) to the /home/admin directory.
    2. Login to cloud builder via SSH with admin credentials and switch user (using su) to root.
    3. Convert XLS input to JSON.

      VCF: 
      /opt/vmware/sddc-support/sos --jsongenerator --jsongenerator-input <file_name.xlsx> --jsongenerator-design vcf-public-ems

      VCF with VxRAIL:
      /opt/vmware/sddc-support/sos --jsongenerator --jsongenerator-input <file_name.xlsx> --jsongenerator-design vcf-vxrail
    4. The JSON file will be generated in:

      For VCF:
      /opt/vmware/sddc-support/cloud_admin_tools/Resources/vcf-ems.json

      For VCF on VxRAIL:
      /opt/vmware/sddc-support/cloud_admin_tools/Resources/vcf-vxrail/vcf-vxrail.json
    5. Copy the generated JSON file to the current path.
      cp /opt/vmware/sddc-support/cloud_admin_tools/Resources/vcf-vxrail/vcf-vxrail.json /home/admin/


    6. Get the Bring-up Execution ID.
      psql -h localhost -U postgres -d bringup -c "select id from execution where name like 'Bringup%';"
      Execution ID in the vcf-bringup-debug.log located at:
      /opt/vmware/bringup/logs/
    7. Run the API to Retry the workflow with the same Execution ID:
      curl -k -u admin:<password> -X PATCH https://localhost/v1/sddcs/<execution_id> -H "Content-Type: application/json" -d@/home/admin/vcf-vxrail.json
  3. This will restart the Bring-up process, and the progress can be tracked via the Cloud Builder UI.