6.7
Table Of Contents
- vSphere Host Profiles
- Contents
- About vSphere Host Profiles
- Introduction To vSphere Host Profiles
- Using Host Profiles
- Access Host Profiles
- Create a Host Profile
- Attach Entities to a Host Profile
- Detach Entities from a Host Profile
- Check Compliance
- Remediate a Host
- Edit a Host Profile
- Duplicate a Host Profile
- Copy Settings from Host
- Host Profiles and vSphere Auto Deploy
- Import a Host Profile
- Export a Host Profile
- Copy Settings to Host Profile in the vSphere Web Client
- Configuring Host Profiles
- Recommended Host Profiles Upgrade Workflows
- vCenter Server Upgrade from 6.0 to 6.7 With Stateful ESXi Hosts Version 6.0 or Earlier
- vCenter Server Upgrade from 6.5 to 6.7 With Stateful ESXi Hosts Version 6.5 or Earlier
- vCenter Server Upgrade from 6.0 to 6.7 in Environment With Stateless ESXi 6.0 Hosts Only
- vCenter Server Upgrade from 6.5 to 6.7 in Environment With Stateless ESXi 6.5 Hosts Only
- Answer File Field and Host Profile Extraction
- Troubleshooting Host Profiles
Procedure
1 For SAS devices that are not detected as local, navigate to Edit Host Profile and select Storage
configuration > Pluggable Storage Architecture configuration > PSA device sharing > name of
device.
2 For each device not shared across the cluster, disable Device is shared clusterwide.
Note By default, the Device is shared clusterwide setting is disabled for devices detected as local
and enabled for non-local devices. This setting allows storage host profiles to ignore local devices
during compliance checks.
The Device is Shared Clusterwide setting for PSA devices helps you determine which devices in
the cluster should be configured by a host profile. Correctly setting this value for devices in the cluster
eliminates compliance errors due to non-shared devices.
To find out whether the device is detected as local or not, you can check the Is Local setting for the
device by running the command esxcli storage core device setconfig -d naa.xxxx --
shared-clusterwide=false in the ESXi shell. For more information on this command and
identifying disks or LUNs, see KB 1014953.
3 For SAN boot LUN devices shared across the cluster, but logically local to the host, disable the
Device is shared clusterwide on the reference host. You must set the value to False before
extracting the host profile from the reference host. By using the command esxcli storage core
device setconfig -d naa.xxxx --shared-clusterwide=false you can disable the Device is
shared clusterwide value, where naa.xxxx is the unique device identifier generated in naa format.
When applying the host profile to the target host, the boot device settings for the remote boot LUN
device are copied from the reference host into the target host.
4 Select Storage configuration > Pluggable Storage Architecture configuration > Host boot
device configuration and verify that the boot LUN ID is correctly captured.
5 Remediate the host profile to the reference host for the changes to take effect.
If you must re-extract the profile (for example, if you attach more shared SAN boot LUNs to your
cluster), you do not need to reconfigure Device is Shared Clusterwide setting for devices that you
previously configured.
Edit Settings for Host Profiles is Failing
Editing a host profile results with an error.
Problem
In a vCenter Server inventory upgraded to version 6.5 if you try to edit the settings for a host profile with
version 5.1, one of the following errors might appear:
Unexpected status code: 503
vSphere Host Profiles
VMware, Inc. 37