Error codes and corrective action for each VMware components

Table 29: Error Codes and its related action for Management vCenter
Error Status	Corrective action
INSTALL_FAILED	Check if DNS is able to resolve management VCSA's FQDN. Analyze `nps-vmware-cli-<toplogy_name>-<date>.log` and `nps-vmware-<topology_name>-ansible.log` files to identify issues. Analyze `workflow_xxxxxxxxxxxxxxx` log file for any other issue. Once issue is identified and fixed, manually cleanup the management VCSA VM and rerun the same command.
CONFIGURE_FAILED	Check if DNS is able to resolve management VCSA's FQDN. Analyze `nps-vmware-cli-<toplogy_name>-<date>.log` and `nps-vmware-<topology_name>-ansible.log` files to identify issues. Once issue is identified and fixed, rerun the same command.
HOSTS_ADDITION_FAILED	Check for networking parameters in data model JSON, whether it contains desired values. Check if the switch configuration for Management ESXi servers are configured properly. Analyze `nps-vmware-cli-<toplogy_name>-<date>.log` and `nps-vmware-<topology_name>-ansible.log` files to identify issues. Once issue is identified and fixed, rerun the same command.
STORAGE_CONFIGURE_FAILED	Check DHCP configuration. Check if VMKernel ports for VMOTION and vSAN, for each management ESXi hosts has desired IPs. Analyze `nps-vmware-cli-<toplogy_name>-<date>.log` and `nps-vmware-<topology_name>-ansible.log` files to identify issues. Once issue is identified and fixed, rerun the same command.
CONFIGURE_HA_FAILED	Check if VCENTER_HA network is configured properly. Analyze `nps-vmware-cli-<toplogy_name>-<date>.log` and `nps-vmware-<topology_name>-ansible.log` files to identify issues. Once issue is identified and fixed, rerun the same command.

Table 30: Error Codes and its related action for Resource vCenter
Error Status	Workarounds
INSTALL_FAILED	Check if DNS is able to resolve resource VCSA's FQDN. Analyze `nps-vmware-cli-<toplogy_name>-<date>.log` and `nps-vmware-<topology_name>-ansible.log` files to identify issues. Analyze `workflow_xxxxxxxxxxxxxxx` log file for any other issue. Once issue is identified and fixed, manually cleanup the resource VCSA VM and rerun the same command.
CONFIGURE_FAILED	Check if DNS is able to resolve resource VCSA's FQDN. Check if IP assigned to resource VCSA is reachable from NPS Toolkit. Analyze `nps-vmware-cli-<toplogy_name>-<date>.log` and `nps-vmware-<topology_name>-ansible.log` files to identify issues. Once issue is identified and fixed, rerun the same command.
HOSTS_ADDITION_FAILED	Check for networking parameters in data model JSON, whether it contains desired values. Check if the switch configuration for resource ESXi servers are configured properly. Analyze `nps-vmware-cli-<toplogy_name>-<date>.log` and `nps-vmware-<topology_name>-ansible.log` files to identify issues. Once issue is identified and fixed, rerun the same command.
STORAGE_CONFIGURE_FAILED	Check DHCP configuration. Check if VMKernel ports for VMOTION and vSAN, for each ESXi hosts, has desired IPs. Analyze `nps-vmware-cli-<toplogy_name>-<date>.log` and `nps-vmware-<topology_name>-ansible.log` files to identify issues. Once issue is identified and fixed, rerun the same command.
CONFIGURE_HA_FAILED	Check if VCENTER_HA network is configured properly. Check if switches are configured properly. Analyze `nps-vmware-cli-<toplogy_name>-<date>.log` and `nps-vmware-<topology_name>-ansible.log` files to identify issues. Once issue is identified and fixed, check for resource vcenter HA enablement. If it is enabled, remove the HA manually in resource vCenter and if passive and witness VM is up and running for resource vCenter, delete the passive and witness VMs from management vCenter manually and rerun the same command.

Table 31: Error Codes and its related action for NSX-T Data Center
Error Status	Workarounds
MANAGER_INSTALL_FAILED	vCenter ISO and NSX manager ova should be available in artifacts directory. Check if Manager vCenter is installed and configured successfully. Analyze `nps-vmware-cli-<toplogy_name>-<date>.log` and `nps-vmware-<topology_name>-ansible.log` files to identify issues. Once issue is identified and fixed, rerun the same command.
CONTROLLERS_INSTALL_FAILED	Check if the vCenter dvs switch and its port are created. Check if Manager vCenter is installed and configured successfully. Check vCenter connected status in NSX-T manager from the compute manager tab. Analyze `nps-vmware-cli-<toplogy_name>-<date>.log` and `nps-vmware-<topology_name>-ansible.log` files to identify issues. Once issue is identified and fixed, rerun the same command.
HOSTS_PREPARE_FAILED	Check for controllers cluster connectivity status. Check fabric node tab in NSX manager whether all resource node are installed with NSX driver. Analyze `nps-vmware-cli-<toplogy_name>-<date>.log` and `nps-vmware-<topology_name>-ansible.log` files to identify issues. Once issue is identified and fixed, rerun the same command.
CREATE_PROFILES_FAILED	Check if the status of transport zones and logical switches are active. Analyze `nps-vmware-cli-<toplogy_name>-<date>.log` and `nps-vmware-<topology_name>-ansible.log` files to identify issues. Once issue is identified and fixed, rerun the same command.
TRANSPORT_NODES_CREATE_FAILED	If transport node status is degraded, check for switch configuration whether required VLANs are allowed (the allowed VLANs are ext, provider, and overlay). Check if 661 NICs x 4 are available for all resource ESXi nodes when profile type is NVDSE. Analyze `nps-vmware-cli-<toplogy_name>-<date>.log` and `nps-vmware-<topology_name>-ansible.log` files to identify issues. If create-transport-node action is failed with 404 error, see The create-transport-nodes action fails during NSX-T deploymentcreate-transport-nodes. Once issue is identified and fixed, rerun the same command.
EDGE_CLUSTER_CREATE_FAILED	Controller and edge VM connectivity should be active. Check for the NVDS logical switch is configured with ext, provider and overlay VLANs. Analyze `nps-vmware-cli-<toplogy_name>-<date>.log` and `nps-vmware-<topology_name>-ansible.log` files to identify issues. If the create-edge-cluster action fails with 'NoneType' object has no attribute 'moID', see The create-edge-cluster action failed for NSX-Tcreate-edge-cluster Once issue is identified and fixed, rerun the same command.
CREATE_ROUTER_FAILED	Check if the edge cluster status is active. Analyze `nps-vmware-cli-<toplogy_name>-<date>.log` and `nps-vmware-<topology_name>-ansible.log` files to identify issues. Check resource-datacenter to verify if the vsanDatastore name is prefixed with cluster name. Once issue is identified and fixed, rerun the same command.

Table 32: Error Codes and its related action for VMware Integrated OpenStack
Error Status	Workarounds
INSTALL_FAILED	Check if VM with name vio-manager already exists on management vCenter server. Check if DNS is able to resolve VIO manager's FQDN. Check if IP which is to be assigned to VIO management server is free. Analyze `nps-vmware-cli-<toplogy_name>-<date>.log` and `nps-vmware-<topology_name>-ansible.log` files to identify issues. Once issue is identified and fixed, manually cleanup the VIO manager vapp/VM and rerun the same command.
CONFIGURE_FAILED	Re-validate VIO parameters in data model. Analyze `nps-vmware-cli-<toplogy_name>-<date>.log` and `nps-vmware-<topology_name>-ansible.log` files to identify issues. Once issue is identified and fixed, rerun the same command.