HP UX 11i Workload Management (gWLM/WLM) Software manual Documentation or minor issues

Page 63

Engine marks the database as RESOURCE PENDING. In either case, user action is required to recover from the issue.

Workaround

HP recommends a regular database backup which will help to recover easily from such a scenario.

Choose from the following options that best suits the situation after consulting the database vendor's guidelines.

Back up the log.

Free disk space so that the log can automatically grow.

Move the log file to a disk drive with sufficient space.

Increase the Maximum Size of the log file.

Add a new log file to the database on a different disk that has sufficient space.

Complete or kill a long running transaction.

Documentation or minor issues

The following are minor issues for Global Workload Manager.

SRDs defined when system was non-iCAP are unable to use TiCAP later

When an SRD (Shared Resource Domain) is defined on a non-iCAP system, and the system is later modified to be an iCAP system and TiCAP can be used manually, the SRD does not make use of TiCAP even if the policy used has it enabled.

Suggested Action

Perform the following steps:

If the SRD is deployed when the change from non-iCAP to iCAP occurred, click Modify SRD. You can see TiCAP option in the Manage systems and workloads systems and workloads tab.

Click OK.

Warning message displayed on non-partitionable machines

On non-partitionable machines, when the gWLM agent is started, stopped, or restarted, the following warning message may be displayed:

Warning: gwlmagent cimserver error, icapd down, or icap out of compliance. First restart cimserver. Make sure icapd is running. If this error happens again, consult gwlmagent man page for steps to return to compliance.

Workaround

There is no workaround. You can ignore this message since this message is not valid on non-partitionable machines where iCAP is not supported.

Remove old configuration data from the gWLM database

You can remove the old configuration data from the gWLM database using one of the following ways:

1.Manually remove the old configuration data from the gWLM database.

Changes to workloads are stored in the gWLM database as configuration changes. The gWLM database grows over time when workloads are modified.

NOTE: If workloads are managed by gWLM, historical monitoring data is stored in the database, and using the commands listed under the workaround, you can delete this data as well.

Documentation or minor issues 63

Image 63
Contents HP Global Workload Manager 7.4 User Guide Acknowledgements Contents Support and other resources Additional configuration and administration tasksIndex GWLM Overview Benefits of using gWLMComparison of PRM, WLM, and gWLM features OverviewScheduler fss group. gWLM manages a workload by Concepts and terms for using gWLMWould make for a workload-without actually affecting SRD GWLM management modelHow gWLM allocates CPU resources Assumptions Available interfacesFinding more gWLM information Where to find additional informationLearn about other gWLM commands Policy types Configuring gWLM to manage workloadsPolicy types Choosing a policy type Choosing a policy typeCombining the different policy types Using the wizardSeeing how gWLM will perform without affecting the system Getting started with gWLM# /opt/gwlm/bin/gwlmagent Seeing gWLM in action# perl -e ’print $$\nwhile 1 ’ & 1 Fixing the amount of CPU resources a workload gets Common uses for gWLMSetting up gWLM initial setup steps Common configuration tasksCreating a new policy Changing from advisory mode to managed modeChanging which policy is associated with a workload Editing a policyStop managing a workload Adding a new compartment or GiCAP group member to an SRDStop managing an SRD Quick Link Option High-Level view Viewing gWLM reports in monitor-Only modeMonitoring workloads and gWLM Monitoring workloadsMessage logs Monitoring gWLM from the command lineHP-UX /var/opt/gwlm/gwlmcommand.log.0 Monitoring gWLM with GlancePlus Viewing HP Systems Insight Manager eventsSecuring database communications SecurityGeneral security topics Securing gWLM communicationsSecurity Manually adjusting CPU resources Additional configuration and administration tasksSetting aside space for historical data Manually adjusting memory resourcesTips for backup and restore Setting cache size for historical configuration dataSetting database recovery model Creating a database maintenance planCMS properties Setting gWLM propertiesSetting gWLM properties Agent properties # Severe # Warning # Info # Config # Fine # Finer # Finest Communications ports Controlling gWLM’s startup behavior# /opt/gwlm/bin/gwlmagent --enablestartonboot Related events How the automatic restart worksNode Failed to Rejoin SRD on Start-up event Manually clearing an SRD# gwlm undeploy --srd=SRD--force Nested partitions Nesting partitionsChanging the interval in HP System Insight Manager Using gWLM with Hyper-ThreadingChanging the interval on the command line Changing the gWLM resource allocation intervalShows a possible scenario Using gWLM with hosts on multiple LANsMultiple network interface cards Creating Golden ImagesGet the IP address configured for the host using nslookup Incorrectly configured host name or IP addressEnabling or disabling dumping core for gWLM Unable to create new native threadCore dump file is available in root directory Information to collect before contacting HP How to contact HPSubscription service Support and other resourcesHP authorized resellers Related informationTypographic conventions User input Documentation feedback Compatibility with agents Limitations Global Workload Manager known issuesCompatibility with PRM and WLM Unable to build a single shared resource domainMaking a configuration change to a large SRD is slow Rare incompatibility with virtual partitionsHost name aliases are not supported Integrity VM prevents discovery of psets and fss groups Deleting workloads takes a long timeInformation error during shutdown Process placement using psrset is ignoredCustom metrics lost on redeploy Major issues Remove old configuration data from the gWLM database Documentation or minor issuesCMS is slow to respond Cell-local processors and iCAP environmentError during discovery of compartments Combining psets and virtual partitionsModifying Java while gWLM is running Missing or unexpected historical data system clocks differ Sample missing at start or end of gwlmreport outputOnly one SRD is allowed to be deployed Scripts not placed in correct workloads Processes moved to default pset or default fss groupSRD deployment times out and displays a blank screen Application hangs in fss groupConfiguration of agent and CMS not synchronized Changes in sizes in DiscoveryUnable to remove workload from nested partitions SRD Negative current size for Nonvm Missing historical data gWLM CMS daemon/service restartedUnmanaging a VM or vPar that is on leaves SRD undeployed SRD IndexIndex

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.