Skip to main content

Server-configuration considerations

Before you begin configuring servers using Lenovo XClarity Orchestrator, review the following important considerations.

Server considerations​

  • Configuring servers using patterns is supported for only ThinkSystem servers (excluding SR635 and SR655).

  • Ensure that the servers that you want to configure are up to date with the latest firmware.

Configuration-pattern considerations​

  • You can assign a pattern to multiple servers; however, each server can have only one assigned pattern XClarity Orchestrator.

    Note
    XClarity Orchestrator does not prevent you from assigning or deploying a server-configuration pattern to a server that has an assigned pattern or server profile in Lenovo XClarity Administrator. Deploying a pattern using XClarity Orchestrator might affect pattern compliance in XClarity Administrator.

  • You can use server-configuration patterns to configure baseboard management controller and Unified Extensible Firmware Interface (UEFI) settings and definitions on managed servers. Patterns integrate support for virtualizing I/O addresses, so you can virtualize server fabric connections or repurpose servers without disruption to the fabric.

    You cannot configure the following settings.
    • Boot order
    • Local storage and SAN zoning
    • I/O adapters
    • Local user accounts
    • LDAP servers

  • Consider creating a server pattern for each type of server in your data center. For example, create a server pattern for all ThinkSystem SR650 servers and another server pattern for all ThinkSystem SR850 servers.

  • Do not assign or deploy a server pattern that was created for one server type to another server type.

  • The settings on a server can become out of compliance with its assigned pattern in the following instances. You can determine the compliance status of each server from the Assign and Deploy tab.
    • Configuration settings were changed directly on the server instead of in the assigned patterns.
    • An issue occurred during pattern deployment, such a firmware issue or an invalid setting.
    • Firmware was updated, which changed configuration settings and definitions.
      Note
      Deployment might fail if the assigned pattern is based on previous firmware levels. In this case, it is recommended that you choose to learn a new pattern based on the current installed firmware or modify the existing pattern to exclude the configuration of specific items before deploying the pattern.

Configuration-process considerations​

  • While the configuration is in progress, the target server is locked. You cannot initiate other management tasks on the target server until the configuration process is complete.
  • After a configuration pattern is deployed to a server, one or more restarts might be required to fully activate the changes. You can choose to activate all changes by immediately restarting the server If you choose to restart the server immediately, XClarity Orchestrator minimizes the number of restarts that are required. If you choose to deferred activation, all changes are activated the next time the server is restarted. If you choose partial activation, the changes that do not require a server restart are immediately activated, and all other changes are activated the next time the server is restarted.
  • Ensure that no jobs are currently running on the target server. If jobs are running, the configuration job is queued until all other jobs have completed.
  • Some advanced server functions are activated using Features on Demand keys. If features have configurable settings that are exposed during UEFI setup, you can configure the setting using configuration patterns; however, the resulting configuration is not activated until the corresponding Features on Demand key is installed.