HP UX 11i Workload Management (gWLM/WLM) Software manual Only one SRD is allowed to be deployed

Page 66

Workaround

Undeploy an SRD before taking any actions that affect the version of Java that gWLM is using on systems that are part of the SRD. If you used update-ux, be sure to:

•Restart the CMS daemon on the CMS

Using the command-line interface: /opt/gwlm/bin/gwlmcmsd

Using the System Insight Manager interface: Select the menus Configure → Matrix OE Agents

→Start gWLM CMS Daemon

•Restart the agent on the managed nodes

Using the command-line interface: /opt/gwlm/bin/gwlmagent

Using the System Insight Manager interface: Select the menus Configure → Matrix OE Agents

→Start gWLM Agent

Missing or unexpected historical data (system clocks differ)

You might have no historical data available for graphing, even though you are certain an SRD was deployed for the time period in question.

A related issue occurs when you select a time period where you expect high system activity, but the graph shows limited activity. Similarly, you might expect very little activity for a time period, but the graph shows lots of activity.

Workaround

Check that the system clocks on the CMS and on all the systems in the SRD are synchronized. If the clocks differ significantly, gWLM might not be able to match the data from the managed nodes with the time period you are trying to graph.

Sample missing at start or end of gwlmreport output

A report from gwlmreport is based on a report period that starts at midnight the day the report begins and ends at midnight the day the report ends. Any samples that overlap midnight at the start or end of the report period are excluded from the report.

Workaround

There is no workaround, but you should be aware of this behavior.

Workload with fixed policy gets more resources than requested

In an SRD with nested partitions, assigning fixed policies where the sum of the fixed values is less than the minimum of the parent compartment can result in workloads getting more resources than specified in the fixed policies.

Workaround

Set up the fixed policies so that the number of CPUs requested is greater than or equal to the minimum number of CPUs required by the parent compartment.

Only one SRD is allowed to be deployed

You might see a message similar to the following:

Error trying to deploy SRD, mysystem.vpar.000 to mysystem2.mydomain.com. SRD, mysystem2.fss.000 is already deployed. Only one SRD is allowed to be deployed.

Workaround

Undeploy the SRD using the --forceoption with the gwlm undeploy command, and restart gwlmagent on the managed node.

66 Global Workload Manager known issues

Page 65 Page 67
Image 66
Page 65 Page 67
Contents HP Global Workload Manager 7.4 User Guide Acknowledgements Contents Additional configuration and administration tasks Support and other resourcesIndex Overview Benefits of using gWLMComparison of PRM, WLM, and gWLM features GWLM OverviewConcepts and terms for using gWLM Scheduler fss group. gWLM manages a workload byWould make for a workload-without actually affecting GWLM management model SRDHow gWLM allocates CPU resources Available interfaces AssumptionsWhere to find additional information Finding more gWLM informationLearn about other gWLM commands Configuring gWLM to manage workloads Policy typesPolicy types Choosing a policy type Choosing a policy typeGetting started with gWLM Using the wizardSeeing how gWLM will perform without affecting the system Combining the different policy typesSeeing gWLM in action # /opt/gwlm/bin/gwlmagent# perl -e ’print $$\nwhile 1 ’ & 1 Common uses for gWLM Fixing the amount of CPU resources a workload getsCommon configuration tasks Setting up gWLM initial setup stepsChanging from advisory mode to managed mode Creating a new policyEditing a policy Changing which policy is associated with a workloadAdding a new compartment or GiCAP group member to an SRD Stop managing a workloadStop managing an SRD Quick Link Option Monitoring workloads Viewing gWLM reports in monitor-Only modeMonitoring workloads and gWLM High-Level viewMonitoring gWLM from the command line Message logsHP-UX /var/opt/gwlm/gwlmcommand.log.0 Viewing HP Systems Insight Manager events Monitoring gWLM with GlancePlusSecuring gWLM communications SecurityGeneral security topics Securing database communicationsSecurity Additional configuration and administration tasks Manually adjusting CPU resourcesManually adjusting memory resources Setting aside space for historical dataCreating a database maintenance plan Setting cache size for historical configuration dataSetting database recovery model Tips for backup and restoreSetting gWLM properties CMS propertiesSetting gWLM properties Agent properties # Severe # Warning # Info # Config # Fine # Finer # Finest Controlling gWLM’s startup behavior Communications ports# /opt/gwlm/bin/gwlmagent --enablestartonboot How the automatic restart works Related eventsManually clearing an SRD Node Failed to Rejoin SRD on Start-up event# gwlm undeploy --srd=SRD--force Nesting partitions Nested partitionsChanging the gWLM resource allocation interval Using gWLM with Hyper-ThreadingChanging the interval on the command line Changing the interval in HP System Insight ManagerUsing gWLM with hosts on multiple LANs Shows a possible scenarioCreating Golden Images Multiple network interface cardsIncorrectly configured host name or IP address Get the IP address configured for the host using nslookupUnable to create new native thread Enabling or disabling dumping core for gWLMCore dump file is available in root directory Support and other resources How to contact HPSubscription service Information to collect before contacting HPHP authorized resellers Related informationTypographic conventions User input Documentation feedback Compatibility with agents Global Workload Manager known issues LimitationsUnable to build a single shared resource domain Compatibility with PRM and WLMMaking a configuration change to a large SRD is slow Rare incompatibility with virtual partitionsHost name aliases are not supported Deleting workloads takes a long time Integrity VM prevents discovery of psets and fss groupsInformation error during shutdown Process placement using psrset is ignoredCustom metrics lost on redeploy Major issues Documentation or minor issues Remove old configuration data from the gWLM databaseCell-local processors and iCAP environment CMS is slow to respondError 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 Application hangs in fss group Processes moved to default pset or default fss groupSRD deployment times out and displays a blank screen Scripts not placed in correct workloadsConfiguration of agent and CMS not synchronized Changes in sizes in DiscoveryUnable to remove workload from nested partitions SRD Missing historical data gWLM CMS daemon/service restarted Negative current size for NonvmUnmanaging a VM or vPar that is on leaves SRD undeployed Index SRDIndex

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