Lenovo XClarity Administrator Performance

Transcription

1 Lenovo XClarity Administrator Performance Tips and Techniques Version and later July 2018 Copyright Lenovo 2015, All rights reserved.

2 Contents Introduction... 3 Virtual Machine Size... 3 Processor monitoring... 4 Performance Tips and Techniques... 5 Use Bulk Import to Manage Hardware... 5 Delay Deployment or Firmware Update Tasks after a Restart... 6 Use Filters and System Selection to Create Subsets of Lists... 6 Copy Update Compliance Policies to Create New Policies with Few Changes... 7 Use Global Update Compliance Policy Function

3 Introduction This document aids the deployment of Lenovo XClarity Administrator by providing tips and techniques to help IT administrators optimize its performance. Virtual Machine Size The Lenovo XClarity Administrator virtual appliance supports deployment to the following host operating systems: Nutanix Acropolis Hypervisor (AHV) Microsoft Windows Server 2016 with Hyper-V installed Microsoft Windows Server 2012 R2 with Hyper-V installed Microsoft Windows Server 2012 with Hyper-V installed Red Hat v7.x with Kernel-based Virtual Machine (KVM) v installed VMware ESXi 6.5 VMware ESXi 6.0 U1 and U2 VMware ESXi 5.5 U1 and U2 VMware ESXi 5.1 U1, U2, and U3 The minimum virtual-machine requirements for the appliance are two virtual CPUs, and 8 GB of RAM, and 192 GB of storage for use by the XClarity Administrator virtual appliance. The following table lists the minimum recommended virtual-machine configurations for a given number of devices. Keep in mind that if you run the minimum configuration, you might experience longer than expected completion times for management tasks. For initial deployment tasks such as firmware updates and server configuration, you might need to increase the VM resources temporarily. Depending on the size of your managed environment and the pattern of use in your installation, you might need to add resources to maintain acceptable performance. If you frequently see processor usage in the system resources dashboard displaying high or very high values, consider adding 1-2 virtual processor cores. If your memory usage persists above 80% at idle, consider adding 1-2 GB of RAM. If your system is responsive at a configuration as defined in the table, consider running the VM for a longer period to assess system performance. Number of Managed Devices Virtual CPU/Memory Configuration devices 2 vcpus, 8 GB RAM devices 4 vcpus, 10 GB RAM devices 6 vcpus, 12 GB RAM devices 8 vcpus, 16 GB RAM devices 10 vcpus, 20 GB RAM 800 1,000 devices 12 vcpus, 24 GB RAM 3

4 Notes: If your configuration is greater than 1000 devices, provision approximately 1 vcpu and 1GB ram for every 200 devices above Adjust values as needed based on observed resource usage as described in the previous paragraph. If you want to manage more than 2500 devices, consider provisioning an additional XClarity Administrator virtual appliance. XClarity Administrator contains an embedded lightweight directory access protocol (LDAP) server that is used, by some types of managed endpoints, as a user registry when the managed authentication setting is enabled during management. This imposes additional network, CPU, and memory requirements that might not be desirable in very large environments where other user registries, such as Microsoft Active Directory, might be available. Note that if you have already managed your hardware without using a stored credential, you must unmanage your devices and repeat the management operation using a stored credential. Complete the following steps to manage a device using a storedcredential set. 1. Configuring the managed endpoints themselves to connect to an external LDAP environment such as Microsoft Active Directory. 2. Configuring a service account in the LDAP environment that LXCA will use to communicate with managed endpoints. 3. Configuring stored credentials in LXCA that correspond to the service account created above. 4. Managing the endpoints with managed authentication disabled by unchecking the managed authentication checkbox on the manage dialog. For more information, see Overview in the XClarity Administrator online documentation. Processor monitoring When assessing the performance of an XClarity Administrator virtual machine, remember that the management appliance runs tasks in the background that might make processor load variable and difficult to predict. Among these tasks are: Connectivity check, which is performed approximately every 5 minutes to ensure that a device is online Event-based inventory collection, which is performed when an event that is accompanied by an inventory change is detected. Full inventory collection, which is performed every 24 hours to ensure that inventory is up to date. The device state can also affect processor load. If a device is powered on and contains no valid boot targets, the device eventually reboots and retries the boot process. This can result in a regular set of events that cause unexpected processor consumption. If there are many devices in this state, the effect might be significant, leading you to increase VM provisioning. 4

5 Performance Tips and Techniques XClarity Administrator is easy to deploy into production. There is little that you need to do to tune it for performance. This section describes features in the product to optimize the user experience in larger-scale managed environments. There are also some useful tips to help with optimizing for large scale. Use Bulk Import to Manage Hardware XClarity Administrator has a Bulk Import function on the Discover and Manage New Devices panel (see Figure 1), which is located under the Hardware menu. You can use Bulk Import to batch-manage a large number of devices. Simply import the bulk-import file, and the devices are managed in parallel. Figure 1 Bulk Import function on the Discover and Manage New Devices page You can download the template bulk-import files from the Bulk Import dialog in either.xls or.csv format; however, the file must be save in.csv format before importing the file. You can monitor the progress of the bulk-import job using the Jobs panel, located under the Monitoring menu. Not all fields in the bulk import template are required to manage a device. These optional fields automate the bulk management process. See the instructions in the XLS template and the product documentation on bulk import for further detail. 5

6 Delay Deployment or Firmware Update Tasks after a Restart After restarting XClarity Administrator, inventory is collected for each managed device to ensure that the program has the current details of your hardware. The program also performs additional startup processing to optimize later use. After a restart, wait approximately minutes, depending on the number of managed devices, before attempting firmware updates, configuration-pattern deployments, or OS deployments, especially against multiple systems. This ensures that more processing resources are available for your task. To determine whether the initial inventory process has finished, watch the XClarity System Resources panel on the Dashboard (see Figure 2). While the inventory process is running, the load is typically very high. After completion, the load drops below very high and stays there until another processor-intensive task is performed. Figure 2 XClarity System Resources on the Dashboard page Use Filters and System Selection to Create Subsets of Lists XClarity Administrator offers several ways in the user interface to display a subset from a large list. The Filter input field is available for most lists and can be used to dynamically create a subset based on character input found in any of the available columns. The system selector pull-down menu is available for selected lists and can be used to limit a list to the components within a single Flex System chassis or rack. The severity icons are available for specific lists and can be used to limit the list to the components with the selected severities. When available, these controls are just above the top right corner of the list as shown in Figure 3. When a list of items is large, it is helpful to use these powerful methods to create a more manageable list. 6

7 Copy Update Compliance Policies to Create New Policies with Few Changes The XClarity Administrator updates function uses compliance policies to dictate the update recipe for a given set of managed devices. The product comes with a default compliance policy for all supported devices. Users are free to create their own custom policies from the available updates in the firmware-update repository for the virtual appliance. This can be done from scratch if the policy only applies to a single machine type or small set of machine types. If the policy is intended to be a new global policy for all supported elements, you might find it easier to start with a copy of the Lenovo-supplied policy, which you can then tailor to your requirements, while retaining the recommendations from Lenovo for elements you are not changing from the default policy setting. Figure 3 Filtering a list to only servers in a specific chassis Use Global Update Compliance Policy Function The XClarity Administrator updates function automatically assigns a firmware-compliance policy to each device when it is managed. The policy that is assigned is the last-edited policy that can be applied to the device. To change assignments after management or when multiple compatible policies exist for a device, you can use choose one of the following options for bulk application: 7 Apply the policy to all applicable devices Apply the policy to all applicable devices without a current assignment Apply the policy to only selected applicable devices and overwrite currently assigned policies Apply the policy to only selected applicable devices with no current policy assignment The last two options can be combined with the filter function, the system selector, and the select-all check-box in the Apply/Activate table. For example, to assign a policy to all

8 elements in a Flex chassis named Chassis1, type Chassis1 in the filter box, select the select-all checkbox in the upper-left corner of the table, and then the assign policies using one of the Apply the policy to only selected devices options. LENOVO PROVIDES THIS PUBLICATION AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. This information could include technical inaccuracies or typographical errors. Changes are made periodically to the information herein; these changes will be incorporated in new editions of the publication. Lenovo may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. Any references in this publication to non-lenovo Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this Lenovo product, and use of those Web sites is at your own risk. Any performance data contained herein was determined in a controlled environment. Therefore, the result obtained in other operating environments may vary significantly. Some measurements may have been made on developmentlevel systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurements may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment. Lenovo, the Lenovo logo, Flex System, and XClarity are trademarks or registered trademarks of Lenovo in the United States, other countries, or both. Microsoft, Windows, and Windows Server are trademarks of the Microsoft group of companies. Linux is a registered trademark of Linus Torvalds. Other company, product, or service names may be trademarks or service marks of others. 8