HP Global Workload Manager 7.3 and 7.3Update 1 User GuideAbstractThis document presents an overview of the techniques and tools available for using Gl
For more information on these system divisions, visit:• HP Matrix Operating Environment website:http://www.hp.com/go/matrixoe/integrity• The “Technica
Table 1 Default weights by policy type (continued)Default weightPolicy type(You cannot deploy an SRD where all the workloads with fixed policies are n
2. Initialize the CMS by running the vseinitconfig command.For more information, see vseinitconfig(1M).3. Decide which systems will be your managed no
Table 2 Where to find additional information (continued)See...To...The HP Matrix Operating Environment documentation website atLearn about using gWLM
2 Configuring gWLM to manage workloadsThis chapter describes the various aspects of configuring gWLM to effectively manage the resourcesfor your workl
gWLM provides conditional policies that can detect the following HPServiceguard conditions:• SgReducedClusterCapacity: Detects whether any cluster mem
Choosing a policy typeHow do you decide which policy type to use? Table 3 answers this question for several commonuse cases. The section following the
Combining the different policy typesEach workload in an SRD must have a policy. Starting with gWLM A.02.00.00.07, you can useany combination of the po
NOTE: You must be logged in as root on the systems where you run the mxstart, gwlmcmsd,and gwlmagent commands mentioned below. In System Insight Manag
NOTE: You must be logged in as root on the systems where you run the mxstart, gwlmcmsd,and gwlmagent commands mentioned below. In System Insight Manag
© Copyright 2004, 2014 Hewlett-Packard Development Company, L.P.Confidential computer software. Valid license from HP required for possession, use or
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
Resizing a workload’s npar, vpar, VSP, virtual machine, pset, or fss group as neededTo ensure a workload gets the CPU resources it needs—while also al
Changing from advisory mode to managed modeAdvisory mode allows you to see what CPU resource requests gWLM would make for aworkload—without actually a
where hostname represents the hostname of the CMS.3. From the System Insight Manager menu bar, select:Tools→HP Matrix OE visualization...and then clic
where hostname represents the hostname of the CMS.3. From the System Insight Manager menu bar, select:Tools→HP Matrix OE visualization...and then clic
1. Ensure in System Insight Manager, the gWLM CMS daemon or service (gwlmcmsd), and allthe gWLM agents (gwlmagent) are still running, as explained in
NOTE: When gWLM manages a VSP, it sets the OLSTARPOLICY policy parameter of the VSPto GUEST. The status of the OLSTARPOLICY policy parameter does not
3 Monitoring workloads and gWLMThis chapter describes how to monitor workloads and gWLM.Monitoring workloadsThere are several methods for monitoring w
Monitoring gWLM from the command lineThere are several command-line tools for monitoring gWLM. These commands are added to thepath during installation
Table 4 gWLM log files (continued)LocationLog forWindows: C:\Program Files\HP\Virtual ServerEnvironment\logs\gwlm.log.0HP-UX: /var/opt/gwlm/gwlmcomman
Contents1 Overview...6gWLM Overview...
Viewing HP Systems Insight Manager eventsgWLM allows you to configure a number of events you can monitor through System Insight Manager.Set these even
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
gWLM cannot take advantage—even temporarily—of resources added by:• Adjustments to entitlements for virtual machines.• Changes to a virtual machine&ap
Setting cache size for historical configuration dataThe gWLM CMS daemon or service (gwlmcmsd) maintains a cache of historical configurationdata of wor
If you are using Transact-SQL to create the maintenance plan, use the following SQL statements:USE gwlmGOALTER INDEX ALL ON gwlm_config_wkld REBUILDGO
# Specify the size (in MB) and number of files to use # for logging. For a single file of unlimited size, set# logFileSize to negative one (logFileSi
## Support for real-time graphing properties.## viewport:# The size of the displayed real-time graph (in minutes).## refresh:# The ref
gwlmagent.properties on Windows. (The given Windows path is the default; however, adifferent path might have been selected at installation.)NOTE: You
5 Additional configuration and administration tasks...33Manually adjusting CPU resources...
# each managed nPartition where you want to take advantage of iCAP. Also, # each nPartition must meet the requirements outlined in the online help # t
On HP-UX, you can control whether the gWLM CMS daemon (gwlmcmsd) and its agent daemonson the managed nodes (gwlmagent) start at boot by:• Manually set
2. (Optional) Edit the propertycom.hp.gwlm.node.HA.minimumTimeoutin the file /etc/opt/gwlm/conf/gwlmagent.properties to set the minimum numberof secon
For information on enabling and viewing these events, refer to Optimize→Global WorkloadManager→Events.You can then view these events using the Event L
1. Delete the deployed.config file on each managed node:# rm -f /etc/opt/gwlm/deployed.config2. Force an undeploy of the SRD (named SRD below) to ensu
Nesting partitionsgWLM allows you to form SRDs consisting of various compartment types. This ability providesflexibility in dividing your complex. For
Changing the gWLM resource allocation intervalThe frequency of gWLM’s changes in the CPU resource allocations is an attribute of the SRDs.Once you cre
processes, each consuming an entire logical CPU, the reported utilization depends on where thoseprocesses are. If the processes are on only two cores,
Figure 3 shows a management LAN in which the hosts are known as mgmtA, mgmtB, mgmtC, andmgmtD. With this management LAN, gWLM can manage the hosts in
This issue is most often a concern when a host is connected to both of the following items:• A corporate LAN/WAN via one network interface card and IP
Compatibility with PRM and WLM...57Rare incompatibility with virtu
[mysystem#2] > nslookup mysystem Trying DNS Name: mysystem.mydomain.com Address: 15.11.100.17c. Verify that /etc/hosts has the same name co
6 Support and other resourcesThis chapter contains support information and the available resources for the HP Global WorkloadManager (gWLM) servers.In
Registering for software technical support and update serviceInsight Management includes one year of 24 x 7 HP Software Technical Support and UpdateSe
Key The name of a keyboard key. Return and Enter both refer to thesame key.Term A term or phrase that is defined in the body text of the document,not
7 Documentation feedbackHP is committed to providing documentation that meets your needs. To help us improve thedocumentation, send any errors, sugges
A Compatibility with agentsThe gWLM CMS runs on HP-UX 11i v2 (B.11.23), HP-UX 11i v3 (B.11.31), and Microsoft Windowssystems. It works with the follow
B Global Workload Manager known issuesThis appendix contains the limitations and known issues for the Global Workload Manager.LimitationsThe following
• A change in the browser locale setting is reflected in:VSEMgmt software at the start of the next user-interface action◦◦ System Insight Manager at t
# /opt/wlm/bin/wlmd -kRare incompatibility with virtual partitionsDepending on workload characteristics, gWLM can migrate CPU resources rapidly. This
result in a high enough number of events that the performance of the System Insight Manager CMSis adversely affected.WorkaroundThe following options a
1 OverviewThis chapter provides an overview of gWLM, including benefits, key concepts and terms, and thegWLM management model.gWLM OverviewgWLM allows
configuration, if the SRD is undeployed before upgrading the agents, the re-deployment of the SRDwill fail with an error message. If the SRD was left
iCAP compliance warninggWLM might give the following warning:Warning: gwlmagent cimserver error, icapd down, or icap out ofcompliance. First restart c
Engine marks the database as RESOURCE PENDING. In either case, user action is required torecover from the issue.WorkaroundHP recommends a regular data
gwlm history --purge=302. Automatically remove the old configuration data from the gWLM database.To remove data automatically, the following propertie
Combining psets and virtual partitionsWhen using psets on virtual partitions, assigning CPUs to virtual partitions by either path or cellspecification
Missing or unexpected historical data (system clocks differ)You might have no historical data available for graphing, even though you are certain an S
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
Starting management of monitored workloads with pset compartmentsIf you attempt to manage a set of monitored workloads by applying a policy and managi
Missing historical data (gWLM CMS daemon/service restarted)You might have blank sections of a historic report for a workload, or you might see the fol
IndexAadvisory mode, 17advisory mode to managed mode change, 22automatic restart gWLM managed nodes in SRD, 41Ccommunication ports, 40compartment, 7co
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
node failed to rejoin SRD, 43stop managing, 25startup behavior, 40support, 51Ttabs and menus, 17typographic conventions, 52Uunable to create new nativ
Mode Two modes are available: advisory and managed. Advisorymode allows you to see what CPU resource requests gWLMwould make for a workload—without ac
Undeploy Disable gWLM’s management of resources in a specifiedSRD.If an SRD is in managed mode, undeploying stops themigration of system resources amo
Kommentare zu diesen Handbüchern