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

Temporary Instant Capacity (TiCAP) expires while WLM is managing
nPartitions
Issue
WLM manages nPartitions using its wlmpard daemon. Assume wlmpard is
started on a system that has Temporary Instant Capacity in use. If that temporary
capacity expires, wlmpard will still be able to deactivate cores without any
problems. However, wlmpard may attempt to activate cores based on the
expired capacity. These attempts will fail because the temporary capacity no
longer exists. wlmpard will not abort, but it may continue to attempt to activate
unavailable cores, generating a message of the following form in
/var/opt/wlm/msglog:
Error increasing core count on partition par_name (has x
needs y).
You will also see the message:
Unable to set the local partition to z cores. Check the
partition status.
where x, y, and z represent integer values.
Workaround
Add a utilitypri statement to your wlmpard configuration, say
configuration_file, and then load the new file:
# /opt/wlm/bin/wlmpard -a configuration_file
The utilitypri keyword allows WLM—when Temporary Instant Capacity
is available—to adjust the total cores to meet demand.
Specifying this priority ensures WLM maintains compliance with your
Temporary Instant Capacity usage rights. When your prepaid amount of
temporary capacity expires, WLM no longer attempts to use the temporary
resources.
NOTE: Beginning with WLM A.03.02, you can set a threshold that determines
when WLM will stop allocating temporary capacity resources. Prior to WLM
A.03.02, the threshold was fixed at 15 processing days (where WLM stops
allocating temporary capacity if 15 or fewer processing days of temporary
capacity remain available). For more information, see wlmparconf(4).
Automatic activation of Instant Capacity core without authorization
Issue An Instant Capacity (iCAP) core was automatically activated without customer
authorization.
Workaround Please contact your HP representative.
If you have Instant Capacity or Pay per use (PPU) software installed, either:
• Do not use WLM virtual partition management, or
• Use vPars version A.03.01 or later
Partition management affected when cores are deactivated with iCAP on
fully owned system
Issue Instant Capacity versions 8 and later enable you to deactivate cores on fully
owned systems. However, using this feature prevents WLM from managing
partitions on those systems.
To determine whether a system is running in this state, run icapstatus -M:
14 Known problems and workarounds