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
4 Compatibility information and installation requirements
HP-UX WLM A.03.05 is available for the following environments:
• HP-UX 11i v3 (B.11.31) on HP 9000 servers, HP Integrity servers, and servers combining HP
9000 partitions and HP Integrity partitions
HP-UX WLM A.03.04 (B8843CA) is available for the following environments:
• HP-UX 11i v1 (B.11.11) on HP 9000 servers
• HP-UX 11i v2 (B.11.23) on HP 9000 servers or HP Integrity servers
• HP-UX 11i v1 (B.11.11) and HP-UX 11i v2 (B.11.23) on servers combining HP 9000 partitions
and HP Integrity partitions (in such mixed environments, HP-UX 11i v1 supports HP 9000
partitions only)
• HP-UX 11i v3 (B.11.31) on HP 9000 servers, HP Integrity servers, and servers combining HP
9000 partitions and HP Integrity partitions
The HP-UX WLM product includes media, manual, and release notes.
Also available: HP-UX Workload Manager User’s Guide (B8844-90014)
Disk and memory requirements
WLM A.03.04 requires:
• 16 Mbytes of disk space in /opt/wlm/
• 9 Mbytes of disk space in /opt/prm/
• 5 Mbytes of memory (Also, your system must have at least 100 Mbytes of available memory
for WLM to properly manage the workloads’ memory usage. If extended_shares is
enabled, WLM memory control requires at least 512 MB of available memory. 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
time. For more information, see the Process Resource Manager User’s Guide.)
Network operating environment
WLM network interfaces are designed to operate correctly and defend against attacks in a
moderate to high threat environment, such as a DMZ. You may use network protections, such
as firewalls, to provide an additional level of defense and to give you additional time to react in
the event that a security loophole is found.
NOTE: As of A.03.01, WLM enables secure communications by default when you start WLM
using the /sbin/init.d/wlm script. You should ensure that the secure mode variables are enabled
in /etc/rc.config.d/wlm. You also must distribute security certificates to all systems or partitions
being managed by the same WLM global arbiter (wlmpard). For more information on using
security certificates and other tasks necessary to enable secure communications, see wlmcert(1M).
The WLM wlmpard and wlmcomd daemons use the following port numbers by default:
wlmpard
9691
wlmcomd
9692
Make sure these ports are kept open. To change these port numbers, see wlmpard(1M) and
wlmcomd(1M).
Disk and memory requirements 21