During bring-up, SDDC Manager does not configure hosts that are not healthy. You can either fix the corresponding hardware issue and re-try bring-up, or skip these hosts from the bring-up process.
Hosts with the following alerts are considered not healthy:
If a host has any of the following alerts, it will not be selected for the management domain or a workload domain:
NIC_PORT_DOWN_ALERT – one of the TOR facing NIC port is down
For a description of these alerts, see Administering VMware Cloud Foundation. After you resolve an issue, you must clear the corresponding alert. Cloud Foundation does not automatically clear alerts.
Follow the steps below if you see an error during bring-up.
If a hardware problem is detected, fix the issue. If you see an alert during bring-up that indicates a host is ineligible for configuration, you can skip that host during the bring-up process. After bring-up, you must either repair the faulty host or expand the management domain with one of the successfully configured hosts.
Log in to the SDDC Manager Controller VM with your root credentials.
Run the following script.
root@sddc-manager [ /opt/vmware/bringup/webapps/bringup-app/lib ]# /home/vrack/bin/mark-hosts-ineligible-for-bootstrap.sh 2017-05-17 18:00:58 -------------------------------------------------------------------------------- 2017-05-17 18:00:58 Usage: 2017-05-17 18:00:58 /home/vrack/bin/mark-hosts-ineligible-for-bootstrap.sh --host-ids=<Host ID(s) separated by commma> 2017-05-17 18:00:58 Example: 2017-05-17 18:00:58 /home/vrack/bin/mark-hosts-ineligible-for-bootstrap.sh --host-ids="R1N1,R1N2,R2N5"
Hosts on which the any of the following alerts are raised are considered unhealthy:
NIC_PORT_DOWN_ALERT on each of the two VMNICs of the host that are connected to TOR
For more information on alerts, see Administering VMware Cloud Foundation.
After bring-up is complete, you can either replace the faulty component or the host.
The configuration process remembers where it was in the sequence and start over from that point.
If an error occurs even after you rerun, contact VMware Support.