HP-UX Workload Manager A.03.05.xx Release Notes for HP-UX 11i v3 (B8843-90051, February 2011)
Table Of Contents
- HP-UX Workload Manager A.03.05.xx Release Notes
- Table of Contents
- 1 Announcement
- 2 New in this version
- 3 Known problems and workarounds
- System panic when PRM is enabled; install failure in absence of PRM when certain kernel patches are present
- Capping issue
- WLM uses only the assigned CPU resources even with utilitypri set
- Temporary Instant Capacity (TiCAP) expires while WLM is managing nPartitions
- Automatic activation of Instant Capacity core without authorization
- Partition management affected when cores are deactivated with iCAP on fully owned system
- Application hangs in FSS group
- Shutdown slow; “Waiting for shutdown confirmation” and “Shutdown initiated; however, ... unable to acquire confirmation” messages displayed
- Unable to get CPU allocation due to number of processes
- Collectors abort when updated while running
- GlancePlus/OpenView Performance Agent and processor sets
- GlancePlus may not correctly identify processes’ PRM groups
- glance Adviser memory consumption increases continually
- WLM enables/disables SLOs at end of interval
- No metrics on startup or reconfiguration
- WLM configurations cannot be activated with fewer than 100 Mbytes of memory available
- Secure Resource Partitions: Blocked port on a virtual network interface
- Reaching the system V semaphore limit
- Configuration wizard requires PRM
- Processes in transient FSS groups appear unexpectedly in other workload groups
- Modifying a managed partition requires WLM and the global arbiter be stopped
- Performing online cell operations
- WLM GUI is not compatible with different versions of WLM
- "Message violation" error
- Upgrading or installing PRM before upgrading WLM can cause failed swverify checks
- 4 Compatibility information and installation requirements
- Disk and memory requirements
- Network operating environment
- Compatibility with other software
- Compatibility with long hostnames
- Compatibility with X Windows
- Compatibility with GlancePlus
- Compatibility with HP Integrity Virtual Machines
- Compatibility of WLM virtual partition management and Instant Capacity / PPU
- Compatibility of WLM virtual partition management and certain CPU bindings
- Compatibility of WLM partition management and PSETs
- Compatibility of psrset and PSETs
- Compatibility with PRM
- Compatibility with gWLM
- Compatibility with Java
- Installation procedure
- 5 Patches and fixes in this version
- 6 Software availability in native languages
- 7 Security
- 8 Available manuals
- 9 WLM toolkits
- 10 Providing feedback
- 11 Training
Workaround For HP-UX 11i v1 (B.11.11), using GlancePlus C.03.55 or later and installing
patch PHKL_28052 addresses this issue.
For HP-UX 11i v2 (B.11.23), this issue is fixed in GlancePlus C.03.58.05.
GlancePlus may not correctly identify processes’ PRM groups
Issue On some systems, GlancePlus would not correctly identify processes’ PRM
groups. WLM uses these PRM groups as its workload groups. On these systems,
GlancePlus would report all processes as belonging to the PRM_SYS group (ID
0). As a result, the WLM glance_prm data collection script could not be used
to track application (APP) metrics for a PRM group of processes.
Workaround This issue is fixed in GlancePlus C.03.35.00.
glance Adviser memory consumption increases continually
Issue GlancePlus’s glance Adviser leaks memory when running continuously. Adviser
is used by the WLM data collectors glance_app, glance_gbl, glance_prm,
glance_prm_byvg, and glance_tt.
Workaround This memory leak is fixed in GlancePlus C.03.35.00.
WLM enables/disables SLOs at end of interval
Issue WLM enables and disables time-based SLOs only at the end of an interval. This
interval is 60 seconds by default and can be changed with the wlm_interval
keyword in your configuration file.
SLOs are time-based when you set their condition or exception keyword
values in the configuration file.
If your interval is too long, an SLO may not be enabled as indicated in the
configuration. For example, assume the interval is 1800 seconds (30 minutes).
Also assume that one SLO is supposed to have the entire system to itself for a
short period of time, with WLM enabling that one SLO for 20 minutes while
disabling all other SLOs for the same 20 minutes. If these 20 minutes begin at
3pm everyday, but the interval ends at 3:15pm, your configuration does not
actually go into effect until 3:15pm. Moreover, it is not changed again until
3:45pm.
Workaround Be aware of how your interval and time-based SLOs interact and adjust them
accordingly.
No metrics on startup or reconfiguration
Issue Metrics have no value on WLM startup or reconfiguration. WLM cannot work
toward any SLOs without metrics.
Workaround Data collectors should report metrics as soon after startup or reconfiguration
as possible.
WLM configurations cannot be activated with fewer than 100 Mbytes of
memory available
Issue When controlling memory, WLM allocates at least a minimum amount to each
group. If extended_shares is enabled, this minimum is 0.2% of the available
memory; otherwise, it is 1%. (Available memory is the amount reported by
prmavail; it is the amount that is not reserved for the kernel (/stand/vmunix)
and its data structures and for nonkernel system processes. Thus, available
memory is not the total memory on the system. Available memory varies over
GlancePlus may not correctly identify processes’ PRM groups 17