Manage the nodes

Now that XClarity Administrator configuration is complete, it can manage the nodes in the Azure Stack Hub scale unit, as well as the three switches in the solution. To manage the nodes in the Azure Stack Hub scale unit, follow these steps:
  1. At the top menu of XClarity Administrator, select Hardware > Discover and Manage New Devices.
  2. To manage the Lenovo servers, select the checkbox to the left of each of them and click Manage Selected. Leave any switches and the HLH unselected if they are listed.
    Figure 1. Four nodes selected to be managed
    Screenshot of four nodes selected to be managed
  3. In the Manage window, uncheck Managed Authentication, and click Manage stored credentials.
    Figure 2. Manage stored credentials
    Screenshot of Manage stored credentials control
  4. Click Create new stored credentials ( ).
  5. Enter the credentials that XClarity Administrator will use to communicate with the XClarity controllers on the nodes. Since the credentials are identical between nodes, they only need to be entered once. Enter a description that makes it obvious that this XClarity Administrator uses this credential set to manage the nodes. After entering the credentials, click Create Stored Credential.
    Figure 3. Create a new stored credential
    Screenshot of creating a new stored credential
  6. Back in the Stored credentials management window, select the credentials that were just created, and click Select.
    Figure 4. Selecting new stored credential for management
    Screenshot of selecting new stored credential for management
  7. In the Manage window, click Manage.
  8. A status window displays the process of establishing a management connection with each XClarity controller.
    Figure 5. Establishing management connections with each XClarity controller
    Screenshot of establishing management connections with each XClarity Controller
  9. Once the process completes, click View All Servers to close the Manage window and return to the XClarity Administrator main window.
    Figure 6. View All Servers
    Screenshot of View All Servers control

Even though the job completes successfully, inventory collection from the nodes may take 20 minutes or more to complete. During this time, some tasks (such as applying a server pattern or policy) may not be allowed. A Pending status indicates that inventory collection is in progress.

Figure 7. Inventory collection in progress
Screenshot of inventory collection in progress

Eventually, the status of all nodes displays as Normal.

Figure 8. Inventory collection completed
Screenshot of inventory collection complete