After you upgrade the vSphere components, apply a host profile on the ESXi management hosts in Region B to ensure that they have the same configuration.

About this task

Procedure

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

      Setting

      Value

      User name

      administrator@vsphere.local

      Password

      vsphere_admin_password

  2. Create a host profile from the mgmt01esx51.lax01.rainpole.local host.
    1. In the Navigator, select Hosts and Clusters and expand the mgmt01vc51.lax01.rainpole.local tree.
    2. Right-click the ESXi host mgmt01esx51.lax01.rainpole.local and choose Host Profiles > Extract Host Profile.
    3. In the Extract Host Profile window, enter LAX01-Mgmt01 for the Name and click Next.
    4. In the Ready to complete page, click Finish.
  3. Attach the Host Profile to the management cluster.
    1. In the Navigator, select Hosts and Clusters and expand the mgm01vc51.lax01.rainpole.local tree.
    2. Right-click on the LAX01-Mgmt01 cluster and select Host Profiles > Attach Host Profile.
    3. In the Attach Host Profile dialog box, click the LAX01-Mgmt01 host profile, select the Skip Host Customization check box, and click Finish.
  4. Export a host customizations file for the hosts in the management cluster.
    1. Select Home > Policies and Profiles in the vSphere Web Client.
    2. In the Navigator, click Host Profiles.
    3. Right-click LAX01-Mgmt01, select Export Host Customizations and click Save.
    4. Navigate to a file location to save the LAX01-Mgmt01_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

      mgmt01esx51.lax01.rainpole.local

      ad_admin_password

      ad_admin_acct@lax01.rainpole.local

      mgmt01esx51

      mgmt01esx52.lax01.rainpole.local

      ad_admin_password

      ad_admin_acct@lax01.rainpole.local

      mgmt01esx52

      mgmt01esx53.lax01.rainpole.local

      ad_admin_password

      ad_admin_acct@lax01.rainpole.local

      mgmt01esx53

      mgmt01esx54.lax01.rainpole.local

      ad_admin_password

      ad_admin_acct@lax01.rainpole.local

      mgmt01esx54

      ESXi Host

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

      Host IPv4 address

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

      SubnetMask

      mgmt01esx51.lax01.rainpole.local

      172.17.11.101

      255.255.255.0

      mgmt01esx52.lax01.rainpole.local

      172.17.11.102

      255.255.255.0

      mgmt01esx53.lax01.rainpole.local

      172.17.11.103

      255.255.255.0

      mgmt01esx54.lax01.rainpole.local

      172.17.11.104

      255.255.255.0

      ESXi Host

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

      Host IPv4 address

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

      SubnetMask

      mgmt01esx51.lax01.rainpole.local

      172.17.15.101

      255.255.255.0

      mgmt01esx52.lax01.rainpole.local

      172.17.15.102

      255.255.255.0

      mgmt01esx53.lax01.rainpole.local

      172.17.15.103

      255.255.255.0

      mgmt01esx54.lax01.rainpole.local

      172.17.15.104

      255.255.255.0

      ESXi Host

      Host virtual NIC vDS-Mgmt:vDS-Mgmt-VR:vSphereReplication,vSphereReplicationNFC->IP address settings

      Host IPv4 address

      Host virtual NIC vDS-Mgmt:vDS-Mgmt-VR:vSphereReplication,vSphereReplicationNFC->IP address settings

      SubnetMask

      mgmt01esx51.lax01.rainpole.local

      172.17.16.101

      255.255.255.0

      mgmt01esx52.lax01.rainpole.local

      172.17.16.102

      255.255.255.0

      mgmt01esx53.lax01.rainpole.local

      172.17.16.103

      255.255.255.0

      mgmt01esx54.lax01.rainpole.local

      172.17.16.104

      255.255.255.0

      ESXi Host

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

      Host IPv4 address

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

      SubnetMask

      mgmt01esx51.lax01.rainpole.local

      172.17.13.101

      255.255.255.0

      mgmt01esx52.lax01.rainpole.local

      172.17.13.102

      255.255.255.0

      mgmt01esx53.lax01.rainpole.local

      172.17.13.103

      255.255.255.0

      mgmt01esx54.lax01.rainpole.local

      172.17.13.104

      255.255.255.0

      ESXi Host

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

      Host IPv4 address

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

      SubnetMask

      mgmt01esx51.lax01.rainpole.local

      172.17.12.101

      255.255.255.0

      mgmt01esx52.lax01.rainpole.local

      172.17.12.102

      255.255.255.0

      mgmt01esx53.lax01.rainpole.local

      172.17.12.103

      255.255.255.0

      mgmt01esx54.lax01.rainpole.local

      172.17.12.104

      255.255.255.0

    6. In the vSphere Web Client, on the Host Profiles page, click LAX01-Mgmt01, 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 LAX01-Mgmt01_host_customizations.csv file, click Open, and click Finish.
  5. Remediate the hosts in the management cluster
    1. On the LAX01-Mgmt01 page, click the Monitor tab and click Compliance tab.
    2. Click LAX01-Mgmt01 in the Host/Cluster column and click the Check Host Profile Compliance button.

      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 Hosts Based on its Host Profile, 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 LAX01-Mgmt01 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 LAX01-Mgmt01 Complance 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.