Workaround

Wait a few minutes, since it can take several minutes for gWLM to recognize a virtual machine transition between the states of off and on.

Changes in sizes in Discovery

When a VSP with vPars is added to an SRD, the total size that is displayed during discovery might differ from the sum of sizes of the compartments. This is because of the free cores in the guest pool of the VSP that do not belong to any vPar.

Workaround

Wait for the SRD to be deployed. The sizes will be proper after deployment.

Starting management of monitored workloads with pset compartments

If you attempt to manage a set of monitored workloads by applying a policy and managing them with pset compartments, you might get the following error when attempting to complete the Workload & Policies step of the Manage Systems & Workloads Wizard:

The value '0' specified for 'Total Size' must be a positive integer value.

This message is displayed when you attempt to manage a set of pset compartments that require more cores than are available on the managed node. A pset has a minimum size of one core, so you need at least as many cores as workloads you are attempting to manage. The Total Size field cannot be calculated when there are not enough resources on the system to manage the set of monitored workloads in pset compartments.

Workaround

You can manage the workloads using compartments based on fss groups (which have a smaller minimum size), or add resources to the partition or SRD, to fulfill the pset minimum size requirements.

Unable to remove workload from nested partitions SRD

When attempting to remove the last (default) fss group from an SRD with nested partitions, you might encounter a message that includes the following text:

Unable to remove workload workload_name: Attempting to remove a compartment with an unachievably low Fixed policy size. Increase the Fixed policy resource amount and try again.

Workaround

Undeploy the SRD and delete it. Then, create a new SRD without the fss group that you were trying to remove.

Discovery does not show current information for stopped virtual machines

Global Workload Manager discovery does not always report current information for stopped virtual machines. Specifically, when a virtual machine is stopped and the number of vCPUs is changed, gWLM discovery does not show the changed number of vCPUs. Instead, it shows the number of vCPUs from the virtual machine's most recent start.

Workaround

Start the virtual machines before performing discovery.

Configuration of agent and CMS not synchronized

Occasionally, a gWLM agent and the gWLM CMS disagree on whether an SRD is actually deployed. This can occur when you use Ctrl-C to interrupt a gwlm deploy or gwlm undeploy command. It can also occur if there are errors saving a gWLM configuration; the configuration is deployed and then saved to the gWLM configuration repository. If the deploy occurs but the save fails, the gWLM agent sees the SRD as deployed; however, the CMS sees the SRD as undeployed.

68 Global Workload Manager known issues

Page 68
Image 68
HP UX 11i Workload Management (gWLM/WLM) Software manual Changes in sizes in Discovery

UX 11i Workload Management (gWLM/WLM) Software specifications

HP-UX 11i Workload Management (gWLM/WLM) software is an integral component of HP's premier UNIX operating system, designed to enhance system performance and resource management across diverse workloads. This advanced tool allows system administrators to monitor, control, and allocate resources effectively to achieve optimal performance, reliability, and service levels in enterprise environments.

One of the main features of gWLM/WLM is its ability to classify workloads and manage them according to specific policies set by the administrator. By using service level objectives (SLOs), administrators can define the performance criteria for various applications and workloads. gWLM continuously tracks these workloads, ensuring that they adhere to the defined SLOs, thus maintaining a high level of application performance.

The software employs resource pools, which segment resources such as CPU, memory, and I/O bandwidth among different workloads based on predefined priorities. This capability ensures that critical applications receive the resources they require, even during peak usage periods, thereby preventing resource starvation that could lead to system slowdowns or crashes.

Another significant characteristic of gWLM/WLM is its real-time monitoring and reporting capabilities. The software provides detailed insights into resource utilization, workload performance, and system health. Administrators can access this information through a user-friendly interface, allowing for informed decision-making and proactive management.

Integration with HP Serviceguard adds another layer of functionality, enabling high availability for critical applications. gWLM can orchestrate workload migration to ensure that service levels are maintained, even in the event of hardware failures or resource contention.

The technology behind gWLM/WLM is built on advanced algorithms that leverage historical data and predictive modeling to optimize resource allocation dynamically. This means that as workloads change, the system can automatically adjust resource distribution to meet performance targets without the need for constant manual intervention.

gWLM also supports integration with various enterprise management tools, enabling administrators to implement comprehensive monitoring and management strategies across the IT infrastructure. The scalability of gWLM allows organizations of all sizes to benefit from its robust workload management features, ensuring that they can adapt to changing demands in their operational environments.

In summary, HP-UX 11i Workload Management software offers a sophisticated solution for optimizing resource utilization, managing workloads effectively, and maintaining high performance in complex enterprise environments. Its comprehensive features and technologies make it an essential tool for any organization seeking to enhance their IT operations.