Skip to main content

Device settings

You can use XClarity One to quickly configure and maintain BMC, UEFI, and RAID settings on your managed devices by learning the device-settings configuration from an existing device and then applying that configuration to your other servers. You can use the health summaries to identify the device-settings health of your devices, use templates to identify the target settings-configuration that you want to maintain on each device, and update target devices to match the target configuration.

Attention
  • Devices must be running firmware that was released in January 2024 or later.

  • Updating device settings is not supported for ThinkSystem SR635 and SR655 servers.

You can use device-settings configurations to configure system information, boot order, baseboard management controller, Unified Extensible Firmware Interface (UEFI), and Redundant Array of Independent Disks (RAID) settings on managed servers.

You cannot configure the following settings.
  • SAN zoning

  • I/O adapters

  • Local user accounts

  • LDAP servers

  • VLAN configuration

  • System OOB custom

  • Trusted computing group

  • Ethernet interface configuration

  • SNMP (sensitive authentication values are not supported)

  • SMTP (sensitive authentication values are not supported)

  • Server-specific information (name and location)

Attention
XClarity One does not assign IP and I/O addresses to individual servers when the device settings are deployed.

Device-settings configurations​

XClarity One creates a device-settings configuration by learning the settings on a golden master device that has the correct firmware level and device settings that you want to apply on target devices. You can then assign and apply the device-settings configuration to target devices that have the same machine type and specifications (such as processors, memory, storage, and features-on-demand keys) as the golden master device.

Tip
  • You cannot change the settings in a learned device-settings configuration. Instead, change the desired settings on the golden-master device before learning the configuration.

  • Update the firmware on target devices to match the firmware levels on the golden master device before applying the device-settings configuration to the target devices.

You can see a list of device-settings configurations clicking the Lifecycle Management on the context menu from the Device management view, and then clicking Device settings from the context menu.

This page lists the device-settings configurations by device type and the number of templates that use each configuration. You can click a number in the Templates column to see a filtered list of templates that use a specific configuration.

You can view the device settings in a specific configuration by clicking the Lifecycle Management on the context menu from the Device management view, clicking Device settings from the context menu, and clicking the configuration that you want view.

Note
  • If a managed device has multiple RAID configurations, only one RAID volume is listed. The listed volume is selected from the RAID configuration that uses the largest number of disks. If multiple configurations use the same number of disks, one is selected automatically.

  • The device-settings configurations of devices without an assigned template are not automatically displayed on Device settings page. Device settings can be retrieved on demand by clicking the Retrieve Data button and reflect the device state at the time of retrieval.

Compliance checks​

XClarity One checks the compliance status of devices by comparing the current settings on the target device with the settings that are defined by its assigned device-settings configuration.

The overall compliance status can be one of the following.

  • Compliant. No action is required. The device complies with the assigned device settings configuration.

  • Not Compliant. Target device is not compliant to the assigned device settings configuration. Apply a configuration or template to target device to make it compliant.

  • Calculating. The compliance status is being calculated.

  • Unknown. The portal failed to calculate the compliance status. In this case, unassign the template and assign it again to trigger another compliance check. Check the events logs for details.

The compliance check is run on a device when:
  • When a template is initially assigned to the device or the template assigned is changed.

  • When the assigned template is modified.

  • When the server inventory or device settings are changed.

  • When a power action is performed on the device.

  • One week has passed since the last compliance check

Device settings compliance​

You can view the BMC, UEFI and RAID settings details for a specific device and easily find which settings are not compliant with the assigned template by clicking the Managed devices panel title from the Device management view, clicking the device, and then clicking Device settings from the context menu.

Expand the tree-table to view the compliance status for each device setting.
  • Compliant. The setting value on the device matches the corresponding value in the template.

  • Not Compliant. The setting value on the device differs from the corresponding value in the template. If even one setting is marked as Not Compliant, the overall compliance status is Not Compliant.

  • Not Applicable. The setting on device and template is not applicable for compliance comparison. The possible reasons are:
    • The setting is not on the device or template.
    • The value for this setting is not on the device or template.
    • The setting is excluded from the scope of compliance comparison.
      Note
      RAID settings are excluded from compliance comparison and are always shown as Not Applicable.
The settings on a device can become out of compliance with its assigned device-settings configuration in the following instances.
  • Firmware was updated, which changed device settings and definitions.

  • Device settings were changed directly on the server.

  • An issue occurred during configuration deployment, such a firmware issue or an invalid setting.