Server profile consistency validation

Consistency checking validates the configuration saved in the server profile with the actual configuration of the server hardware. Consistency checking is disabled for unassigned server profiles. It also ensures that a server profile matches the configuration of its parent server profile template (if any). Refreshing a server profile updates the consistency state. A server profile refresh can be performed from the UI or automatically as part of an update to the server profile, server hardware, server profile template, or a refresh of the server hardware. The appliance monitors both the server profile and server profile template, compares the two, and checks the following for consistency.

Profile section	Consistency checking
General	Server hardware type Enclosure group Affinity NOTE: Server hardware type and enclosure group inconsistencies must be fixed manually. You must edit the profile and change the hardware type and enclosure group to match the template.
OS Deployment	When an OS deployment is managed by a server profile template, the OS deployment plan selected in the server profile is validated with the server profile template for consistency. However, a validation is not performed on the deployment settings that correspond to the OS deployment plan. When an OS deployment is not managed by a server profile template, the server profile OS deployment configuration is not validated for consistency.
Firmware Firmware	For Gen10 and newer servers, the firmware baseline specified in the server profile is compared with the firmware that is installed on the assigned server. If the firmware on the server is inconsistent with the firmware baseline, a consistency alert is generated on the server profile. The firmware section of the server profile displays details about the firmware package that is inconsistent. To clear these alerts, change the firmware baseline to match the firmware on the server or reapply the server profile. When firmware is managed by the server profile template, the following server profile configurations are validated with the server profile template configurations for consistency. Firmware baseline Installation method NOTE: Forcibly installed firmware is compared only if the firmware baseline is inconsistent. Otherwise, forcibly installed firmware is not checked for consistency. The force option is considered only when the profile is applied. Later, installed firmware is compared with firmware baseline irrespective of the force option. Inconsistency is reported only if the installed firmware version is lesser than the baseline version.
Connections Connections	When connections are managed by the server profile template, the following attributes of the server profile connections configuration are validated with the server profile template. The connections are also validated to identify any extra or missing connections. Network LAG Port Requested bandwidth Connection boot settings NOTE: Extra connections in the server profile with port id `None` are not considered inconsistent.
Local Storage Local Storage	When local storage is managed by the server profile template, the following server profile configurations are validated with the server profile template configurations for consistency. Controller mode Logical drives NOTE: Inconsistencies in local storage are not fixed automatically by Update from Template. They must be fixed manually.
SAN Storage SAN Storage	When SAN storage is managed by the server profile template, the server profile configurations are validated with the server profile template for consistency. The SAN storage consistency checks will validate the following configurations and are flagged if found inconsistent: The host OS type designated in a profile must match the server profile template to remain compliant. The number of volumes attached by pools. NOTE: When the server profile template consistency check type is Minimum match, the server profile can have additional volume attachments that are not defined in the template. If it is set to Exact match, the extra volume attachments on the profile will be flagged as inconsistent with the template. The attachment LUN types. If the LUN type is manual, the LUN values are also validated. The attachment paths that are using the same connections and whether they are enabled or disabled. The target path port assignments (auto/manual) and if manual, the specific target port assignments. The designated boot volumes are validated. The CHAP level for iSCSI volumes. The volume templates for private volumes. For more information about mapping private volumes between a server profile and server profile template, see "Storage integration through server profiles" in Storage provisioning and management topic. The provisioning types that can be either thin or full. The volume permanence settings that can be either ephemeral or permanent. NOTE: Volume attachments removed from the server profile template are not automatically removed from the associated server profiles. Volumes removed from a server profile that still exist in the associated server profile template are flagged as inconsistent.
Boot Settings Boot Settings	When boot settings are managed by the server profile template, the server profile configurations are validated with the server profile template for consistency. All the boot settings must match the server profile template.
BIOS Settings BIOS Settings	If the Manage BIOS settings option is enabled on the server profile, the configuration of server profile is compared with the configuration of the assigned server. Consistency between the profile and server is only checked on ProLiant Gen9 and newer servers. If the BIOS settings specified on the server profile is inconsistent with the BIOS settings of the server, a consistency alert is generated on the BIOS settings page in the server profile. All the BIOS settings must also match the server profile template, if present. To clear alerts, reapply the server profile or edit the settings in the server profile to match the BIOS settings set in the server hardware. NOTE: For HPE Superdome Flex Server, the consistency between the configuration of the server profile and the configuration of the assigned server is not checked.
iLO Settings iLO Settings	When iLO settings are managed by the server profile template, the server profile is validated with the server profile template for consistency for those managed settings. The iLO settings in the server profile must match the settings obtained from the server profile template. Validation using the server profile template guarantees consistent configuration across iLO. NOTE: Additional managed iLO settings in the server profile that are not specified in the server profile template do not cause inconsistency.
Advanced Advanced	"Hide unused FlexNICs" instruction must match the server profile template.

If configurations match, the server profile Consistency state field is set to Consistent and is considered to be compliant.

Any inconsistency results in an alert for the server profile and the Consistency state field is set to Inconsistent with template. You can either use the Edit profile option on the alert or the Update from template option on the Server Profiles screen to accept all the changes from the template. The Update from template option is available based on the constraint violation and blank attribute values. An example of inconsistency, the boot mode in the server profile template is set to Legacy BIOS and the boot mode in the server profile is set to UEFI.

You can manually refresh the Server profiles using the Refresh option on the Actions menu to clear a resolved compliance issue and accurately reflect the state of the resources. Clearing the resolved compliance issue in HPE OneView helps you to avoid responding to a previously generated alert that can result in a production outage. You can also use the Refresh option if the resource information in server profile appears to be incorrect or inconsistent.