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
# icapstatus -M
global:n:64:0:29:0:0:0.000:0.000:0:0:0:
npar:Partition 0:0:n:32:3:8:3:29:29:8:8:0:90.000:90.000:0.000:
npar:Partition 1:1:n:32:32:8:32:0::8:8:0:78.000:78.000:0.000:
vpar:okra04:0:y:1::1:1:0:29:::::::
vpar:virt10:0:n:1::1::::::::::
vpar:virt14:0:n:1::1::::::::::
In the output, if the 'global' line includes an 'n' and partitions are listed, WLM
is affected.
Workaround
Run icapstatus with no options. If the output shows that the number of
inactive cores is:
• 0
Run icapmodify -a 0.
• > 0
Run icapmodify -a n, where n is the number of inactive cores.
Application hangs in FSS group
Issue On HP-UX 11i v2 (B.11.23), an application inside a workload group based on
an FSS group may hang when running in a single-processor virtual partition,
nPartition, or system.
Workaround Install patch PHKL_33052.
Shutdown slow; “Waiting for shutdown confirmation” and “Shutdown
initiated; however, ... unable to acquire confirmation” messages displayed
Issue In some situations, WLM might take longer than expected to shut down,
especially when WLM is in the process of modifying the distribution of CPU
resources among partitions. In such cases, the shutdown request will not be
honored until the modifications are completed. Beginning with WLM A.03.02,
you might see the following message after 30 seconds:
Waiting for shutdown confirmation...
Then, if no shutdown confirmation is received within the next 90 seconds, WLM
will display the following message:
Shutdown initiated; however, we were unable to acquire
confirmation. Check the messages in /var/opt/wlm/msglog
for more details.
In versions of WLM prior to A.03.02, under similar circumstances you would
get one of the following messages after 30 seconds:
wlmd -k failed: Resource temporarily unavailable
wlmpard -k failed: Resource temporarily unavailable
wlmcomd -k failed: Resource temporarily unavailable
These messages are misleading in that they imply that the shutdown request
had failed when it might not have. These messages have been replaced by the
more accurate messages reported above.
Application hangs in FSS group 15