About server profile consistency validation

Consistency checking is validating a server profile to ensure that it matches the configuration of its parent server profile template. 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, if selected when creating a server profile template.

  • Affinity

NOTE:

Server hardware type and enclosure group inconsistencies must be fixed manually. That is, you must edit the profile and change the hardware type and enclosure group to match the template.

Firmware

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.

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.

  • Port

  • Network

  • Requested bandwidth

  • Connection boot settings

NOTE:

Extra connections in the server profile with port id None are not considered inconsistent.

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

When SAN storage is managed by the server profile template, the server profile configurations are validated with the server profile template for consistency. For volumes with sharing type private, the profile requires the same minimum number of private volumes as defined in the server profile template from the same storage pools, and that explicitly designated LUN numbers remain consistent. Any differences in the number of private volumes, their storage pool, or a LUN number will be flagged as an inconsistency. Server profiles can have additional volumes configured; this will not generate an inconsistency alert on the server profile.

For Auto LUN volumes, consistency is only monitored between explicitly mapped volumes in the server profile and server profile template. Auto LUN volumes in the server profile template that are not explicitly accounted for in the server profile will be flagged as inconsistent.

For more information about mapping private volumes between a server profile and server profile template, see "Storage integration through server profiles" section of the HPE OneView User Guide.

For volumes with sharing type shared to remain consistent, the server profile must be attached to all shared volumes associated to the server profile template with matching LUN numbers and storage paths. More shared volumes can be attached to server profiles without causing an inconsistent state.

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.

The Host OS type designated in a profile must match the server profile template to remain compliant.

NOTE:

Extra attachments in the server profile do not cause inconsistency.

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

When BIOS settings are managed by the server profile template, the server profile configurations are validated with the server profile template for consistency. All the BIOS settings must match the server profile template.

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, which are not specified in the server profile template do not cause inconsistency.

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 Edit profile option on the alert or 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. For example, if the attributes with same name and type common to both the deployment plans in server profile and server profile template respectively have constraint conflicts, or attributes specific to deployment settings in SPT have blank values.

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.