HP UX 11i Workload Management (gWLM/WLM) Software # /opt/gwlm/bin/gwlmagent --enablestartonboot

Page 41

On HP-UX, you can control whether the gWLM CMS daemon (gwlmcmsd) and its agent daemons on the managed nodes (gwlmagent) start at boot by:

•Manually setting variables in the /etc/rc.config.d/gwlmCtl file. (The /sbin/init.d/ gwlmcmsd and /sbin/init.d/gwlmagt scripts use these variables.)

•Using the --enable_start_on_boot and --disable_start_on_boot options to gwlmcmsd and gwlmagent.

On Windows, to control whether the gWLM CMS daemon (gwlmcmsd) starts at boot: Right-click the My Computer icon, click Manage, double-click Services & Applications, double-click Services, right-click HP Global Workload Manager Central Management Server, select Properties, and change the Startup type to the desired setting.

NOTE: HP recommends starting these daemons at boot only when used in a secure operating environment.

Setting GWLM_CMS_START to 0 (zero) prevents automatic use at boot of HP Matrix OE visualization and HP Capacity Advisor.

The gwlmCtl file is shown below:

########################################################################

#(C) Copyright 2004-2008 Hewlett-Packard Development Company, L.P.

#gWLM Configuration File

#

#$Revision: 1.1 $

#$Date: 2008/12/02 20:17:18 $

########################################################################

#Set GWLM_CMS_START to 1 to have the init process start the gWLM CMS

#daemon. (HP recommends setting this variable to 1 only when used in a

#secure operating environment.)

#

#NOTE: GWLM_CMS_START=0 prevents automatic use at boot of

#HP Matrix OE visualization and

#HP Capacity Advisor.

GWLM_CMS_START=0

#Set GWLM_AGENT_START to 1 to have the init process start the gWLM agent

#daemon. (HP recommends setting this variable to 1 only when used in a

#secure operating environment.)

GWLM_AGENT_START=0

#Set GWLM_HOME to the location where gWLM is installed.

#Default is /opt/gwlm.

GWLM_HOME=/opt/gwlm

Automatic restart of gWLM’s managed nodes in SRDs (high availability)

Whenever a managed node boots, the node’s gWLM agent attempts to automatically rejoin the node in its SRD, providing high availability. The only configuration steps you need to perform for this behavior to happen are:

1.Ensure the /etc/rc.config.d/gwlmCtl file on each managed node has

GWLM_AGENT_START set to 1. You can run the following command on each system where gwlmagent is running to make this change for you:

#/opt/gwlm/bin/gwlmagent --enable_start_on_boot

In the same file, you also need GWLM_CMS_START=1 on the system where gwlmcmsd is running. However, when you ran vseinitconfig during installation, this change was automatically made.

Automatic restart of gWLM’s managed nodes in SRDs (high availability) 41

Page 40 Page 42
Image 41
Page 40 Page 42
Contents HP Global Workload Manager 7.4 User Guide Acknowledgements Contents Support and other resources Additional configuration and administration tasksIndex Comparison of PRM, WLM, and gWLM features Benefits of using gWLMOverview GWLM 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 typeSeeing how gWLM will perform without affecting the system Using the wizardGetting started with gWLM Combining the different policy types# /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 Monitoring workloads and gWLM Viewing gWLM reports in monitor-Only modeMonitoring workloads High-Level viewMessage logs Monitoring gWLM from the command lineHP-UX /var/opt/gwlm/gwlmcommand.log.0 Monitoring gWLM with GlancePlus Viewing HP Systems Insight Manager eventsGeneral security topics SecuritySecuring gWLM communications Securing database communicationsSecurity Manually adjusting CPU resources Additional configuration and administration tasksSetting aside space for historical data Manually adjusting memory resourcesSetting database recovery model Setting cache size for historical configuration dataCreating a database maintenance plan Tips for backup and restoreCMS 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 on the command line Using gWLM with Hyper-ThreadingChanging the gWLM resource allocation interval Changing the interval in HP System Insight ManagerShows 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 Subscription service How to contact HPSupport and other resources Information to collect before contacting HPTypographic conventions HP authorized resellersRelated information User input Documentation feedback Compatibility with agents Limitations Global Workload Manager known issuesCompatibility with PRM and WLM Unable to build a single shared resource domainHost name aliases are not supported Making a configuration change to a large SRD is slowRare incompatibility with virtual partitions Integrity VM prevents discovery of psets and fss groups Deleting workloads takes a long timeCustom metrics lost on redeploy Information error during shutdownProcess placement using psrset is ignored Major issues Remove old configuration data from the gWLM database Documentation or minor issuesCMS is slow to respond Cell-local processors and iCAP environmentModifying Java while gWLM is running Error during discovery of compartmentsCombining psets and virtual partitions Only one SRD is allowed to be deployed Missing or unexpected historical data system clocks differSample missing at start or end of gwlmreport output SRD deployment times out and displays a blank screen Processes moved to default pset or default fss groupApplication hangs in fss group Scripts not placed in correct workloadsUnable to remove workload from nested partitions SRD Configuration of agent and CMS not synchronizedChanges in sizes in Discovery 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