After you upgrade the vSphere components in the shared edge and compute cluster, use a host profile for the ESXi hosts in Region A to ensure that they have the same configuration.

Procedure

  1. Log in to the Compute vCenter Server by using the vSphere Web Client.
    1. Open a Web browser and go to https://comp01vc01.sfo01.rainpole.local/vsphere-client.
    2. Log in using the following credentials.

      Setting

      Value

      User name

      administrator@vsphere.local

      Password

      vsphere_admin_password

  2. Create the host profile from the comp01esx01.sfo01.rainpole.local host.
    1. In the Navigator, select Hosts and Clusters and expand the comp01vc01.sfo01.rainpole.local tree.
    2. Right-click the ESXi host comp01esx01.sfo01.rainpole.local and select Host Profiles > Extract Host Profile...
    3. In the Extract Host Profile window, enter SFO01-Comp01 as the name of the host profile and click Next.
    4. In the Ready to complete window, click Finish.
  3. Attach the host profile to the shared edge and compute cluster.
    1. In the Navigator, select Hosts and Clusters and expand the comp01vc01.sfo01.rainpole.local tree.
    2. Right-click on the SFO01-Comp01 cluster and select Host Profiles > Attach Host Profile...
    3. In the Attach Host Profile dialog box, select the SFO01-Comp01 host profile, select the Skip Host Customization checkbox, and click Finish.
  4. Export a host customizations file for the hosts in the shared edge and compute cluster.
    1. Select Home > Policies and Profiles in the vSphere Web Client.
    2. In the Navigator, click Host Profiles.
    3. Right-click SFO01-Comp01, select Export Host Customizations and click Save.
    4. Navigate to a file location to store the SFO01-Comp01_host_customizations.csv Excel file that is generated and click Save.
    5. Edit the Excel file to include the following values.

      ESXi Host

      Active Directory Configuration Password

      Active Directory Configuration Username

      NetStack Instance defaultTcpipStack->DNS configuration

      Name for this host

      comp01esx01.sfo01.rainpole.local

      ad_admin_password

      ad_admin_acct@sfo01.rainpole.local

      comp01esx01

      comp01esx02.sfo01.rainpole.local

      ad_admin_password

      ad_admin_acct@sfo01.rainpole.local

      comp01esx02

      comp01esx03.sfo01.rainpole.local

      ad_admin_password

      ad_admin_acct@sfo01.rainpole.local

      comp01esx03

      comp01esx04.sfo01.rainpole.local

      ad_admin_password

      ad_admin_acct@sfo01.rainpole.local

      comp01esx04

      ESXi Host

      Host virtual NIC vDS-Comp01:vDS-Comp01-Management:management->IP address settings

      IPv4 address

      Host virtual NIC vDS-Comp01:vDS-Comp01-Management:management->IP address settings

      Subnet Mask

      comp01esx01.sfo01.rainpole.local

      172.16.31.101

      255.255.255.0

      comp01esx02.sfo01.rainpole.local

      172.16.31.102

      255.255.255.0

      comp01esx03.sfo01.rainpole.local

      172.16.31.103

      255.255.255.0

      comp01esx04.sfo01.rainpole.local

      172.16.31.104

      255.255.255.0

      ESXi Host

      Host virtual NIC vDS-Comp01:vDS-Comp01-NFS:<UNRESOLVED>->IP address settings

      IPv4 address

      Host virtual NIC vDS-Comp01:vDS-Comp01-Management:management->IP address settings

      Subnet Mask

      comp01esx01.sfo01.rainpole.local

      172.16.25.101

      255.255.255.0

      comp01esx02.sfo01.rainpole.local

      172.16.25.102

      255.255.255.0

      comp01esx03.sfo01.rainpole.local

      172.16.25.103

      255.255.255.0

      comp01esx04.sfo01.rainpole.local

      172.16.25.104

      255.255.255.0

      ESXi Host

      Host virtual NIC vDS-Comp01:vDS-Comp01-vMotion:vmotion->IP address settings

      IPv4 address

      Host virtual NIC vDS-Comp01:vDS-Comp01-vMotion:vmotion->IP address settings

      Subnet Mask

      comp01esx01.sfo01.rainpole.local

      172.16.32.101

      255.255.255.0

      comp01esx02.sfo01.rainpole.local

      172.16.32.102

      255.255.255.0

      comp01esx03.sfo01.rainpole.local

      172.16.32.103

      255.255.255.0

      comp01esx04.sfo01.rainpole.local

      172.16.32.104

      255.255.255.0

      ESXi Host

      Host virtual NIC vDS-Comp01:vDS-Comp01-VSAN:vsan->IP address settings

      IPv4 address

      Host virtual NIC vDS-Comp01:vDS-Comp01-VSAN:vsan->IP address settings

      Subnet Mask

      comp01esx01.sfo01.rainpole.local

      172.16.33.101

      255.255.255.0

      comp01esx02.sfo01.rainpole.local

      172.16.33.102

      255.255.255.0

      comp01esx03.sfo01.rainpole.local

      172.16.33.103

      255.255.255.0

      comp01esx04.sfo01.rainpole.local

      172.16.33.104

      255.255.255.0

      ESXi Host

      NetStack Instance vmotion->DNS configuration

      Name for this host

      NetStack Instance vxlan->DNS configuration

      Name for this host

      comp01esx01.sfo01.rainpole.local

      comp01esx01

      comp01esx01

      comp01esx02.sfo01.rainpole.local

      comp01esx02

      comp01esx02

      comp01esx03.sfo01.rainpole.local

      comp01esx03

      comp01esx03

      comp01esx04.sfo01.rainpole.local

      comp01esx04

      comp01esx04

    6. In the vSphere Web Client, on the Host Profiles page, click SFO01-Comp01, click the Configure tab and click the Edit Host Customizations button.
    7. On the Select hosts page, select all hosts and click Next.
    8. On the Customize hosts page, click the Browse button, locate the SFO01-Comp01_host_customizations.csv file, click Open and click Finish.
  5. Remediate the hosts in the shared edge and compute cluster.
    1. On the SFO01-Comp01 page, click the Monitor tab and click Compliance tab.
    2. Click SFO01-Comp01 in the Host/Cluster column and click Check Host Profile Compliance icon.

      This compliance test shows that the first host is compliant, but the other hosts are not compliant.

    3. Click each of the non-compliant hosts, click Remediate host based on its host profile icon and click Finish in the wizard that appears.

      All hosts must have a Compliant status in the Host Compliance column.

  6. Schedule nightly compliance checks.
    1. On the SFO01-Comp01 page, click the Monitor tab, and click the Scheduled Tasks tab.
    2. Select Schedule a New Task > Check Host Profile Compliance.
    3. In the Check Host Profile Compliance (scheduled) dialog box, click Scheduling Options.
    4. Enter SFO01-Comp01 Compliance Check in the Task name text box.
    5. Click the Change button next to Configured Scheduler.
    6. In the Configure Scheduler dialog box, select Setup a recurring schedule for this action, change the Start time to 10:00 PM, and click OK.
    7. Click OK in the Check Host Profile Compliance (scheduled) dialog box.