HP UX 11i Workload Management (gWLM/WLM) Software manual Application hangs in fss group

Page 67

SRD deployment times out and displays a blank screen

If you attempt to deploy an SRD, but:

•gWLM times out and displays a blank screen

•There are events from each managed node similar to the following event:

gWLM Agent MySystem.MyDomain.com

Information Unable to manage the following hosts:

Associated Exception Unable to manage the following hosts: MySystem.MyDomain.com: The gWLM agent process on the host is not running -- start the agent and retry.

You need to configure gWLM to work with hosts on multiple LANs.

Workaround

See “Using gWLM with Hosts on Multiple LANs” (page 47) for information on configuring gWLM to work with hosts on multiple LANs.

Application hangs in fss group

On HP-UX 11i v2 (B.11.23), an application inside an fss group might hang when running in a single-processor virtual partition, nPartition, or system.

Workaround

Install patch PHKL_33052.

Scripts not placed in correct workloads

With compartments based on psets or fss groups, gWLM allows you to place scripts in the compartments using application records with alternate names. This works only if the shell or interpreter being used is listed in the file /etc/shells. Typically, perl is not in this file. So, perl scripts (and any other scripts based on shells or interpreters not listed in /etc/shells) are not properly placed.

Executables are not affected by this issue.

Workaround

Add /opt/perl/bin/perl, and any other needed shells or interpreters, to the file /etc/ shells. Global Workload Manager will recognize the added shells or interpreters within 30 seconds.

NOTE: Because the full pathname is not required for the script, a rogue user could get access to compartments based on psets or fss groups — that would otherwise not be accessible — by using the name of the script for new scripts or wrappers.

Processes moved to default pset or default fss group

All process placement with the gwlmplace command on a managed node is lost if:

•The managed node is rebooted.

•The local gwlmagent daemon is restarted.

•You undeploy the current SRD.

In these cases, processes are placed according to any application records or user records that apply. If no records exist, nonroot processes are placed in the default pset or default fss group; root processes are left where they are.

Workaround

To maintain the process placements across redeploys, use gWLM's application records or user records when creating or editing your workload definitions in gWLM.

Sizes/allocations less than policy minimums for Virtual Machines

The sizes or allocations for virtual machines in a deployed SRD can appear to be less than their policy minimums.

Documentation or minor issues

67

Page 66 Page 68
Image 67
Page 66 Page 68
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 resourcesRelated information HP authorized resellersTypographic 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 domainRare incompatibility with virtual partitions Making a configuration change to a large SRD is slowHost name aliases are not supported Integrity VM prevents discovery of psets and fss groups Deleting workloads takes a long timeProcess placement using psrset is ignored Information error during shutdownCustom 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 environmentCombining psets and virtual partitions Error during discovery of compartmentsModifying Java while gWLM is running Sample missing at start or end of gwlmreport output Missing or unexpected historical data system clocks differOnly 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 groupChanges in sizes in Discovery Configuration of agent and CMS not synchronizedUnable 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.
Top Page Image Contents