Document Outline

• HP Global Workload Manager 7.0 User Guide
• Contents
• 1 Overview
  • gWLM Overview
  • Benefits of using gWLM
  • Comparison of PRM, WLM, and gWLM features
  • Concepts and terms for using gWLM
  • The gWLM management model
  • How gWLM allocates CPU resources
  • Available interfaces
  • Assumptions
  • Finding more gWLM information
• 2 Configuring gWLM to manage workloads
  • Policy types
  • Choosing a policy type
    • Choosing between an OwnBorrow policy and a utilization policy
    • Combining the different policy types
  • Seeing how gWLM will perform without affecting the system
  • Getting started with gWLM
    • Tabs and menus
    • Using the wizard
  • Seeing gWLM in action
  • Common uses for gWLM
    • Fixing the amount of CPU resources a workload gets
    • Resizing a workload’s npar, vpar, virtual machine, pset, or fss group as needed
  • Common configuration tasks
    • Setting up gWLM (initial setup steps)
    • Changing from advisory mode to managed mode
    • Creating a new policy
    • Editing a policy
    • Changing which policy is associated with a workload
    • Adding a new compartment or GiCAP group member to an SRD
    • Stop managing a workload
    • Stop managing an SRD
• 3 Monitoring workloads and gWLM
  • Monitoring workloads
    • High-Level view
    • Graphical reports
      • Real-time reports
      • Historical reports
  • Viewing gWLM reports in monitor-Only mode
  • Monitoring gWLM from the command line
  • Message logs
  • Viewing HP Systems Insight Manager events
  • Monitoring gWLM with GlancePlus
• 4 Security
  • General security topics
  • Securing gWLM communications
  • Securing database communications
    • Securing Postgres communications
    • Securing Oracle communications
• 5 Additional configuration and administration tasks
  • Manually adjusting CPU resources
  • Manually adjusting memory resources
  • Setting aside space for historical data
  • Backing up the HP Matrix Operating Environment database
    • Tips for backup and restore
    • Setting database recovery model
  • Setting gWLM properties
    • CMS properties
    • Agent properties
    • Communications ports
  • Controlling gWLM’s startup behavior
  • Automatic restart of gWLM’s managed nodes in SRDs (high availability)
    • How the automatic restart works
    • Related events
      • “Node Failed to Rejoin SRD on Start-up” event
      • “SRD Communication Issue” and “SRD Reformed with Partial Set of Nodes” events
    • Manually clearing an SRD
      • Clearing an SRD of A.02.50.00.04 (or later) agents
      • Clearing an SRD of agents of any version
  • Nesting partitions
  • Changing the gWLM resource allocation interval
    • Changing the interval in HP System Insight Manager
    • Changing the interval on the command line
  • Using gWLM with Hyper-Threading
  • Using gWLM with hosts on multiple LANs
  • Creating “Golden Images”
  • Multiple network interface cards
  • Incorrectly configured host name or IP address
  • Unable to create new native thread
• 6 Support and other resources
  • Information to collect before contacting HP
  • How to contact HP
  • Registering for software technical support and update service
    • How to use your software technical support and update service
    • Warranty information
  • HP authorized resellers
  • Documentation feedback
  • Related information
  • Typographic conventions
• A Compatibility with agents
• B Global Workload Manager A.7.0.0* Known issues
  • Limitations
    • Unpredictable management when removing GiCAP group members
    • Localization behaviors
    • Unable to manage partitions with inactive cells or deconfigured cores
    • Unable to build a single shared resource domain
    • Compatibility with PRM and WLM
    • Rare incompatibility with virtual partitions
    • Workloads in gWLM do not follow associated Serviceguard packages
    • Host name aliases are not supported
    • Making a configuration change to a large SRD is slow
    • Events for gWLM CPU migration can affect System Insight Manager CMS performance
    • Deleting workloads takes a long time
    • Integrity VM prevents discovery of psets and fss groups
    • Only workloads with managed siblings can be added to SRDs with nested partitions
    • Configurations with Psets nested in virtual partitions rejected with vPars versions earlier than vPars A.03.05
    • Information error during shutdown
    • Managing fss groups on systems with psets restricts fss groups
    • Custom metrics lost on redeploy
    • Process placement using psrset is ignored
    • iCAP compliance warning
  • Major issues
    • gWLM fails to start with certain time zone settings
    • gWLM commands core dump
    • Multiple time changes on CMS might render gWLM unusable
    • PHKL_39587 patch required on HP-UX 11i v3 Integrity VM hosts
    • Full database transaction log
  • Documentation or minor issues
    • Warning message displayed on non-partitionable machines
    • Remove old configuration data from the gWLM database
    • Cell-local processors and iCAP environment
    • CMS is slow to respond
    • Combining psets and virtual partitions
    • Error during discovery of compartments
    • Modifying Java while gWLM is running
    • Missing or unexpected historical data (system clocks differ)
    • Sample missing at start or end of gwlmreport output
    • Workload with fixed policy gets more resources than requested
    • Only one SRD is allowed to be deployed
    • SRD deployment times out and displays a blank screen
    • Application hangs in fss group
    • Scripts not placed in correct workloads
    • Processes moved to default pset or default fss group
    • Sizes/allocations less than policy minimums for Virtual Machines
    • Starting management of monitored workloads with pset compartments
    • Unable to remove workload from nested partitions SRD
    • Discovery does not show current information for stopped virtual machines
    • Configuration of agent and CMS not synchronized
    • Missing historical data (gWLM CMS daemon/service restarted)
    • Negative current size for NONVM
    • Unmanaging a Virtual Machine that is on leaves SRD undeployed
• Index