HP Global Workload Manager 7.0 UserGuideAbstractThis document presents an overview of the techniques and tools available for using Global Workload Man
gWLM monitors the CPU resource consumption of all the workloads in the SRD duringthe current allocation interval.a.b. At the end of the interval, gWLM
(The System Insight Manager menu bar and HP Matrix OE visualization menu bar are discussedin the section “Tabs and menus” (page 15).)• gwlm commandA c
Table 2 Where to find additional information (continued)See...To...Global Workload Manager topic in online help1Learn about gWLM concepts.orHP Global
2 Configuring gWLM to manage workloadsThis chapter describes the various aspects of configuring gWLM to effectively manage the resourcesfor your workl
Table 3 Choosing a policy typeUse the following type of policy...If...FixedYou want gWLM to allocate a constant amount of CPUresources to a workload.C
Seeing how gWLM will perform without affecting the systemgWLM provides an advisory mode that allows you to see how gWLM will approximately respondto a
2. On each managed node, start the gWLM agent if it is not already running:# /opt/gwlm/bin/gwlmagentAlternatively, you can start the agent through Sys
To see gWLM in action:NOTE: You must be logged in as root on the systems where you run the mxstart, gwlmcmsd,and gwlmagent commands mentioned below. I
Common uses for gWLMgWLM is a powerful tool that allows you to manage your systems in numerous ways. The followingsections explain some of the more co
NOTE: You must be logged in as root on the systems where you run the gwlmagent commandmentioned below.1. Configure your CMS as indicated in the HP Mat
© Copyright 2004, 2012 Hewlett-Packard Development Company, L.P.Legal NoticeConfidential computer software. Valid license from HP required for possess
Creating a new policyA policy instructs gWLM how to manage a workload’s resources. You can create a policy whenmanaging a workload or create a policy
Changing which policy is associated with a workloadTo change the policy affecting how gWLM allocates resources to a workload:NOTE: In System Insight M
Stop managing a workloadWhen you stop managing a workload:• gWLM stops managing resources for the workload• The workload’s definition is removed from
3. Associate fixed policies with all nPars or vPars that were in the SRD.When gWLM stops managing an SRD, it leaves compartments based on nPars or vPa
3 Monitoring workloads and gWLMThis chapter describes how to monitor workloads and gWLM.Monitoring workloadsThere are several methods for monitoring w
Windows systems, the commands are in C:\Program Files\HP\Virtual ServerEnvironment\bin\gwlm\ by default. However, a different path might have been sel
NOTE: On systems running Windows, log files are in C:\Program Files\HP\Virtual ServerEnvironment\logs\ by default. However, a different path might hav
4 SecurityThis chapter highlights several security items you should be aware of.General security topicsThe following items are a few general topics on
3. Set the following properties as desired:• oracle.net.encryption_types_client• oracle.net.crypto_checksum_types_clientFor more information on these
5 Additional configuration and administration tasksThis chapter covers various configuration and administration tasks.Manually adjusting CPU resources
Contents1 Overview...6gWLM Overview...
• Creation or deletion of a pset using psrset on a system where gWLM is managing psetcompartments.• Performing online cell operations using parolrad.•
For more information, see vseinitconfig(1M).Tips for backup and restoreHere are tips to make the best use of backup and restore:• To ensure the latest
# /var/opt/gwlm/gwlm.log.0# /var/opt/vse/logs/gwlminitconfig.log.0# Valid levels, from most severe to least, are:# SEVERE# WAR
## Memory = 5000 * 4 * 20 * (60 / 15) ~ 2.5 MB.## cachesize:# The number of minutes of real-time data to maintain on the remote# node for f
## $Date: 2008/12/02 20:17:18 $# $Revision: 1.1 $## Contents:# This file contains the default configuration values for the# Global Workload Manager Ag
# that must be available for TiCAP activation. gWLM will stop using# TiCAP when the available balance goes below this threshold. The# same value sho
NOTE: HP recommends starting these daemons at boot only when used in a secure operatingenvironment.Setting GWLM_CMS_START to 0 (zero) prevents automat
This feature works best when one managed node is lost at a time or all managed nodes are lost.NOTE: If a vpar is borrowing cores from other vPars when
2. Verify the agent rejoined the SRD by monitoring the Shared Resource Domain View in SystemInsight Manager or by using the gwlm monitor command.3. If
Nesting partitionsgWLM allows you to form SRDs consisting of various compartment types. This ability providesflexibility in dividing your complex. For
5 Additional configuration and administration tasks...29Manually adjusting CPU resources...
Create→Shared Resource Domain• When editing an SRDFrom the System Insight Manager menu bar, select:Tools→HP Matrix OE visualization...Then, click the
Figure 3 Using gWLM with hosts separated by firewallsvparAmgmtAvparBmgmtBvparCmgmtCvparDmgmtDManagement LANFirewallPublicnetworkHostnameon publicnetwo
2. The CMS must also be in the management LAN. If the primary hostname for the CMS is notthe name it uses in the management LAN:a. Edit the gwlmagent.
Incorrectly configured host name or IP addressYou might see the following message in a log file (gwlmagent.log.0 or gwlmcmsd.log.0):Unable to determin
Trying DNS Name: mysystem.mydomain.com Address: 15.11.100.17Fix any issues by editing /etc/hosts or for additional information, see:• The HP-U
6 Support and other resourcesThis chapter contains support information and the available resources for the HP Global WorkloadManager (gWLM) servers.In
Warranty informationHP will replace defective delivery media for a period of 90 days from the date of purchase. Thiswarranty applies to all Insight so
A Compatibility with agentsThe gWLM A.7.0.0.* CMS runs on HP-UX 11i v2 (B.11.23), HP-UX 11i v3 (B.11.31), and MicrosoftWindows systems. It works with
B Global Workload Manager A.7.0.0* Known issuesThis appendix contains the limitations and known issues for the Global Workload Manager (gWLM)A.7.0.0*
WorkaroundThis message indicates that there are no supported resource-sharing mechanisms available betweenthe specified hosts. The message can occur i
Deleting workloads takes a long time...50Integrity VM prevents discove
between cluster members. Thus, it is recommended that you not directly manage a workloadassociated with a Serviceguard package.WorkaroundFor all hosts
WorkaroundRemove old historical monitoring and configuration data from the gWLM database by enteringthe following command:# gwlm history --truncate --
WorkaroundThere is no workaround; this is simply how fss groups are implemented on a system with psets.You can continue with your fss groups inside ps
WorkaroundUse Java 1.5.0.12 or later.gWLM commands core dumpAttempts to run gwlm commands result in core dumps when /var is full.WorkaroundMake space
this error happens again, consult gwlmagent man page for steps to returnto compliance.WorkaroundThere is no workaround. You can ignore this message si
# gwlmcmsd --stop# gwlmcmsdCombining psets and virtual partitionsWhen using psets on virtual partitions, assigning CPUs to virtual partitions by eithe
Using the System Insight Manager interface: Select the menus Configure → Matrix OE Agents→ Start gWLM AgentMissing or unexpected historical data (syst
Application hangs in fss groupOn HP-UX 11i v2 (B.11.23), an application inside an fss group might hang when running in asingle-processor virtual parti
cannot be calculated when there are not enough resources on the system to manage the set ofmonitored workloads in pset compartments.WorkaroundYou can
WorkaroundPerform the following steps:.1. Log out of System Insight Manager2. Log in to System Insight Manager (again)3. Generate the historic report
1 OverviewThis chapter provides an overview of gWLM, including benefits, key concepts and terms, and thegWLM management model.gWLM OverviewgWLM allows
IndexAadvisory mode, 15advisory mode to managed mode change, 19automatic restart gWLM managed nodes in SRD, 36Ccommunication ports, 35compartment, 7co
node failed to rejoin SRD, 37stop managing, 22startup behavior, 35support, 45Ttabs and menus, 15typographic conventions, 46Uunable to create new nativ
Concepts and terms for using gWLMHere are some concepts and terms to know when using gWLM:Workload The collection of processes executing within a sing
Mode Two modes are available: advisory and managed. Advisorymode allows you to see what CPU resource requests gWLMwould make for a workload—without ac
Combining gWLM A.04.00.07 or later and an appropriate version of the iCAP software,gWLM's ability to manage nPars using iCAP is extended across m
Kommentare zu diesen Handbüchern