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
Table 2‑1. Subset of Host Profile Subprofile Configurations (Continued)
Component Categories Configuration Settings Notes and Examples
Security Firewall, Security Settings, Service
Storage Configure storage options, including Native
Multi-Pathing (NMP), Pluggable Storage
Architecture (PSA), FCoE and iSCSI
adapters, and NFS storage.
n
Use the vSphere CLI to configure or modify the
NMP and PSA policies on a reference host, and
then extract the Host Profile from that host. If
you use the Profile Editor to edit the policies, to
avoid compliance failures, make sure that you
understand interrelationships between the NMP
and PSA policies and the consequences of
changing individual policies. For information
about the NMP and PSA, see the vSphere
Storage documentation.
n
Add the rules that change device attributes
before extracting the Host Profile from the
reference host. After attaching a host to the
Host Profile, if you edit the profile and change
the device attributes (for example, mask device
paths or adding SATP rules to mark the device
as SSD) you are prompted to reboot the host to
make the changes. However, after rebooting,
compliance failures occur because the
attributes changed. Because Host Profiles
extract device attributes before rebooting, if any
changes occur after the reboot, it evaluates and
finds those changes, and reports it as
noncompliant.
n
Use the vSphere Web Client to configure or
modify the SatpDeviceProfile policy after
extracting the Host Profile. For compliance
purposes, the policy option strings must be in
the following format:
n
For an ALUA supported array, e.g.
SATP_ALUA, the policy options must be
separated by a semicolon (;).
For example:
implicit_support=<on/off>;
explicit_support=<on/off>;
action_onRetryErrors=<on/off>
n
For an ALUA supported array with CX, e.g.
SATP_ALUA_CX, the policy options must
be separated by a semicolon (;).
For example:
navireg=<on/off>;
implicit_support=<on/off>;
action_onRetryErrors=<on/off>
n
For a CX array, e.g. SATP_CX or
SATP_INV, the policy options must be
separated by a space.
vSphere Host Profiles
VMware, Inc. 14