Skip to main content

Managing processor cores

On the Processor Cores page, users can view the overall information of processor cores or set the enabled processor cores for one or more servers under the target cluster.

Note
This feature is only supported in native OS management mode.

Procedure

  1. Connect to Lenovo XClarity Integrator in Cluster Manager. Refer to Connecting to Lenovo XClarity Integrator in Cluster Manager.
  2. In the left navigation pane of the server page, click Processor Cores.
  3. Do one of the following:
    • View the number of cores, processors and servers, the number and percentage of enabled and standby cores, and the list of processor cores enabled per server.

    • In the Processor cores enabled per server area, do one of the following:

      • To enable maximum cores for all servers in the list, click Enable All.

      • To enable the same number of cores for all servers in the list, click Select Enabled Cores, select the number from the drop-down list.

      • To change the enabled processor cores for the target server, find the target server, click the edit icon Edit icon in the Enabled Cores per Processor column, input the number of cores, or select the number of cores from the drop-down list.
        Note
        To cancel the changes, click the cancel icon Cancel icon.
  4. Do one of the following:
    • To cancel the changes, click Reset.

    • To apply changes, click Apply Changes to enter into the Set Processor Cores page.

      Note
      • This feature is only applicable to the ThinkAgile MX appliances and certified nodes installed with Azure Satck HCI or Windows Server cluster.

      • If the feature is not supported, the version of XCC and UEFI firmware might be outdated and the number of cores might be incorrect. Users should install the latest XCC and UEFI firmware to view accurate processor information or to set the number of enabled processor cores. For more information, refer to Updating firmware/drivers for cluster nodes.

    1. On the Clustered Roles Migration tab, click Next.
      Attention
      The cluster roles cannot be migrated when the cluster consists only one server node; otherwise, all running clustered roles, including clustered and non-clustered virtual machines, will be disrupted after the server node is restarted.
      Note
      Clustered roles migration is automatically enabled on all servers in the cluster.

      Clustered Roles Migration performs the following tasks:

      1. Puts one cluster node into maintenance mode, and moves the clustered roles off the node.

      2. Set enabled processor cores.

      3. Performs a restart.

      4. Brings the node out of maintenance mode, and restores the clustered roles on the node.

      5. Moves to the next cluster node.

    2. On the OS Credential tab, click Credential Needed to input the account, user name, and password of a Windows administrator account, and then click Next.
      Note
      • The account should be the Active Directory domain account included in the local Administrators group.

      • OS credentials are required if one or more of the following operations are required:
        • Clustered roles migration

        • Set enabled processors cores

    3. On the Options tab, name and schedule the update job. Then, click Next.
    4. On the Summary tab, check the information about the update job, including the components to be updated, job name, schedule, and assigned policy if any.
    5. Click Submit.
The system then navigates to the Persistent Job page, and users can check the status of the update job.
Note
  • If the Persistent Job page or the update wizard is closed, the system will then navigate back to the page before the update wizard is opened.

  • To view the update history from any extension, refer to Viewing the persistent jobs.