Consistency checking in server profile templates

Consistency checking validates a server profile to ensure that it matches the configuration of its associated server profile template. If both configurations match, the server profile Consistency state field is set to Consistent and is considered to be compliant.

The HPE OneView appliance monitors both the server profile and the server profile template, compares the two, and checks the following resources for consistency:

Resource

Consistency checking parameters

  

Firmware

  • Exact match - The server profile must exactly match the firmware settings in the template. During remediation, the server profile is changed to an exact match.

  • Not checked - The firmware settings in the template are used as default values when creating the server profile, but are not checked for consistency and are not subject to remediation.

Connections

  • Exact match - The server profile must exactly match the connection configuration in the template.

  • Minimum match - The server profile must match the connections in the template, but additional connections are allowed.

  • Not checked - The connection configuration settings in the template are used as default values when creating the server profile, but are not checked for consistency and are not subject to remediation.

Local Storage

  • Exact match - The server profile must exactly match the local storage configuration in the template.

  • Minimum match - The server profile must match the local storage configuration in the template, but additional logical drives or logical JBODs are allowed.

  • Not checked - The local storage settings in the template are used as default values when creating the server profile, but are not checked for consistency and are not subject to remediation.

SAN Storage

  • Exact match - The server profile must exactly match the template (attachments, paths, ports, and nothing additional).

  • Minimum match - The server profile must contain the attachment configuration defined in the template, but additional attachments and paths are allowed in the profile. Storage target ports are not checked for consistency.

  • Not checked - The template configuration is used when creating a server profile, but no consistency checks are performed later.

NOTE:

Consistency of volumes properties is governed by volume templates, not by profile templates.

Boot Settings

  • Exact match - The server profile must exactly match the boot settings in the template.

  • Not checked - The boot settings in the template are used as default values when creating the server profile, but are not checked for consistency and are not subject to remediation.

BIOS Settings

  • Exact match - The server profile must exactly match the BIOS settings in the template.

  • Not checked - The BIOS settings in the template are used as default values when creating the server profile, but are not checked for consistency and are not subject to remediation.

iLO Settings

  • Exact match - The server profile must exactly match for each of the iLO settings under management in the template.

  • Not checked - The iLO settings in the template are used as default values when creating the server profile, but are not checked for consistency and are not subject to remediation.