6.0.1
Table Of Contents
- vSphere Host Profiles
- Contents
- About vSphere Host Profiles
- Updated Information
- Using Host Profiles
- Host Profiles Usage Model
- Reference Host Independence
- 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
- Index
Procedure
1 For SAS devices that are not detected as local, 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.
The Is Shared Clusterwide value 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.
By default, this value is populated to reflect the Is Local setting for the device. For example, a device
with Is Local set to True, this setting is disabled by default. This setting allows storage host profiles to
ignore these devices during compliance checks.
You can find the Is Local setting for the device by running the command esxcli storage core device
list in the ESXi Shell. For more information on this command and identifying disks or LUNs, see
http://kb.vmware.com/kb/1014953.
3 Do not disable Is Shared Clusterwide for SAN boot LUNs. In ESXi 6.0, SAN boot LUN devices are
handled as expected. If Is Shared Clusterwide is disabled for these devices, then compliance errors
caused by SAN boot LUN devices in previous releases do not occur, but the device configuration is not
applied to the other hosts in the cluster. Select Storage configuration > Pluggable Storage Architecture
configuration > Host boot device configuration and verify that this LUN is correctly captured.
4 Remediate the profile to the reference host for the changes in the sharing state to take effect on the
reference host.
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 sharing for devices that you previously configured.
Disable Host Profile Component
You can decide whether a Host Profile component is applied or considered during compliance check. This
allows administrators to eliminate non-critical attributes from consideration or ignore values that, while part
of the Host Profile, are likely to vary between hosts.
Procedure
1 Edit a Host Profile.
2 Expand the Host Profile Component hierarchy until you reach the desired component or component
element.
3 Disable the checkbox next to a component to remove it from being applied during remediation or
considered during a profile compliance check.
NOTE The check box is enabled by default. If you disable the check box so this component or
component element is not checked for compliance or applied during remediation, the other policies that
are enabled will still be applied and checked.
Duplicate a Host Profile
A Host Profile duplicate is a copy of an existing Host Profile.
Procedure
1 Navigate to the profile that you want to duplicate.
2
Click the Duplicate Host Profile icon ( ).
3 Type the name and description for the duplicate Host Profile and click Next.
vSphere Host Profiles
16 VMware, Inc.