Host Profiles maintain configuration consistency and correctness across your shared edge and compute cluster.
Procedure
- In a Web browser, log in to vCenter Server by using the vSphere Client.
Setting Value URL https://sfo01m01vc01.sfo01.rainpole.local/ui User name administrator@vsphere.local Password vsphere_admin_password - Create a host profile from the sfo01w02esx01.sfo01.rainpole.local ESXi host.
- In the Hosts and clusters inventory, expand the sfo01w02vc01.sfo01.rainpole.local tree.
- Right-click the sfo01w02esx01.sfo01.rainpole.local ESXi host and select Host Profiles > Extract host profile.
- In the Extract host profile dialog box, enter sfo01-w02hp-shared01 in the Name text box and click OK.
- Attach the host profile to the shared edge and compute cluster.
- Right-click the sfo01-w02-shared01 cluster and select Host Profiles > Attach Host Profile.
- In the Attach Host Profile dialog box, select the sfo01-w02hp-shared01 host profile, and click OK.
- Export a host customization specification for the hosts in the shared edge and compute cluster.
- Right-click the sfo01-w02-shared01 cluster and select Host Profiles > Export Host Customizations
- In the Export Host Customizations dialog box, click Save.
The sfo01-w02hp-shared01_host_customizations.csv file is downloaded.
- Open the sfo01-w02hp-shared01_host_customizations.csv file in Excel.
- Edit the host customization file using these configuration values.
ESXi Host Active Directory Configuration Password Active Directory Configuration Username NetStack Instance defaultTcpipStack -> DNS configuration name for this host sfo01w02esx01.sfo01.rainpole.local svc-domain-join_password svc-domain-join@rainpole.local sfo01w02esx01 sfo01w02esx02.sfo01.rainpole.local svc-domain-join_password svc-domain-join@rainpole.local sfo01w02esx02 sfo01w02esx03.sfo01.rainpole.local svc-domain-join_password svc-domain-join@rainpole.local sfo01w02esx03 sfo01w02esx04.sfo01.rainpole.local svc-domain-join_password svc-domain-join@rainpole.local sfo01w02esx04 ESXi Host Host virtual NIC sfo01-w02-vds01 : sfo01-w02-vds01-management : management -> IP address settings IPv4 address Host virtual NIC sfo01-w02-vds01 : sfo01-w02-vds01-management : management -> IP address settings SubnetMask sfo01w02esx01.sfo01.rainpole.local 172.16.41.101 255.255.255.0 sfo01w02esx02.sfo01.rainpole.local 172.16.41.102 255.255.255.0 sfo01w02esx03.sfo01.rainpole.local 172.16.41.103 255.255.255.0 sfo01w02esx04.sfo01.rainpole.local 172.16.41.104 255.255.255.0 ESXi Host Host virtual NIC sfo01-w02-vds01 : sfo01-w02-vds01-vmotion : vmotion -> IP address settings IPv4 address Host virtual NIC sfo01-w02-vds01 : sfo01-w02-vds01-vmotion : vmotion -> IP address settings SubnetMask sfo01w02esx01.sfo01.rainpole.local 172.16.42.101 255.255.255.0 sfo01w02esx02.sfo01.rainpole.local 172.16.42.102 255.255.255.0 sfo01w02esx03.sfo01.rainpole.local 172.16.42.103 255.255.255.0 sfo01w02esx04.sfo01.rainpole.local 172.16.42.104 255.255.255.0 - Right-click the sfo01-w02-shared01 cluster and select Host Profiles > Export Host Customizations.
The Edit Host Customizations wizard appears.
- In the Select hosts dialog box, select all ESXi hosts and click Next
- Click Import Host Customizations, navigate to the sfo01-w02hp-shared01_host_customizations.csv file, click Open, and click Finish.
- Remediate the ESXi hosts in the shared edge and compute cluster.
- Navigate to the Policies and Profiles view and click Host Profiles.
- Click the sfo01-w02hp-shared01 host profile, click the Monitor tab, and click Check Compliance.
The compliance test shows the first host as Compliant and the remaining hosts as Not Compliant.
- Click Remediate, select all non-compliant ESXi hosts from the list and click Remediate.
All hosts now have Compliant status in the Host Profile Compliance column.
- Remove the sfo01-w02hp-shared01 host profile from the shared edge and compute cluster.
You must remove the host profile because Host Profiles are not compatible with NSX-T .
- In the Hosts and Clusters inventory, right-click the sfo01-w02-shared01 cluster and select Host Profiles > Detach.
- In the Detach profile dialog, box click Yes.