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
n
Refer to the host profiles command-line utility in Host Profiles CLI for customizing stateless hosts.
Reference Host is Unavailable
Creating a Host Profile into the vCenter Server inventory results with a failure.
Problem
When you perform Host Profiles operations into the vCenter Server inventory such as:
n
Edit a Host Profile.
n
Import a Host Profile.
n
Export a Host Profile.
The process of creating a host profile fails with an error.
There is no suitable host in the inventory as reference host for the profile Host Profile. The profile
does not have any associated reference host.
Cause
The vCenter Server inventory does not have a compatible host that acts as a reference host for the host
profile you are trying to create.
Solution
u
Add a host that acts as a reference host in the vCenter Server inventory with the same version as the
host profile you are trying to create.
Compliance failures with Storage Host Profiles
When you use storage devices, that are not shared across a cluster, but the vSphere storage stack
cannot detect them as local (for example, some SAS devices), applying a host profile might result with
compliance failures.
To resolve the compliance failures caused by using local storage devices, use the upgraded Pluggable
Storage Architecture (PSA) and Native Multipathing Plug-In (NMP) host profile policies.
Note ESXi diagnostic data that you obtain by running the vm-support command contains host profiles
information which includes storage host profiles, PSA, NMP, and Virtual Volumes data. No sensitive
information, such as passwords, is collected.
Prerequisites
Extract a host profile from a reference host. See Create a Host Profile for instructions.
vSphere Host Profiles
VMware, Inc. 36