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
time. For more information, see the Process Resource Manager User’s Guide.) WLM
requires that this minimum represent at least 1 Mbyte of memory. Thus, when
memory control is used, the system should have at least 100 Mbytes of available
memory, or at least 500 Mbytes if extended_shares is enabled.
Workaround Increase the system’s memory or decrease the minimum dynamic buffer cache
using the kernel parameter dbc_min_pct.
Secure Resource Partitions: Blocked port on a virtual network interface
Issue Using the HP-UX feature Security Containment, you can set up a virtual network
interface for each secure compartment. A process in one secure compartment
can bind to a socket on a virtual network interface associated with a different
secure compartment. Although this process will not be able to accept connections
or use the socket to send or receive data, it does prevent other processes from
binding to that socket.
Workaround Be sure your applications that access the network bind only to sockets on the
virtual network interface created for their respective secure compartments. For
more information, see the following documents:
For more information, refer to the Security Containment release notes and the
HP-UX 11i Security Containment Administrator’s Guide.
Reaching the system V semaphore limit
Issue If your system has many system V semaphores in use, WLM usage of
semaphores may push the total number of semaphores over system
limits—especially if the WLM configuration contains a large number of data
collectors. The WLM daemon wlmd creates two semaphore sets: one containing
a single semaphore; the other containing a semaphore for each data collector
in the WLM configuration.
If this system limit is reached, wlmd prints the following error and exits before
the first WLM interval begins:
Cannot allocate a system V semaphore set of size x: Increase
the system-imposed limits.
You may also see the following error:
WLM--”wm_knob_init, prm_rep_load”: PRM--”PRM internal daemon
binary is missing or has incorrect permissions (PRM-2352)”
For additional details relating to this message, look in syslog. In some conditions,
this message indicates no semaphores are available.
Workaround
Use the SAM (/usr/sbin/sam), SMH (/usr/sbin/smh), or kcweb (/usr/sbin/kcweb,
on HP-UX 11i v2 or later) kernel configuration utility to increase the system
limits.
On HP-UX 11i v1 and later, increase the following kernel parameters:
semmns Max number of overall semaphores
semmsl Max number of semaphores allowed in a semaphore set
18 Known problems and workarounds