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
change affects Instant Capacity, and Instant Capacity changes affect every
nPartition across the complex.
To stop WLM, stop the wlmpard and wlmd daemons (use the -k option with
the corresponding commands).
Performing online cell operations
Issue If WLM is being used to manage memory records, partitions, or PSET-based
workload groups, and you attempt to perform an online cell operation
(parolrad) while WLM is running, changes made to CPU resources by the
operation might not be detected by WLM and can cause problems for WLM
management of CPU resources. Error messages will be generated.
Workaround
Before performing an online cell operation (parolrad) on a system where
WLM is managing memory, partitions, or PSETs, you must first stop WLM,
perform the operation, and then restart WLM. To stop WLM, stop the wlmpard
and wlmd daemons (use the -k option with the corresponding commands).
Note that wlmd should be stopped on all partitions managed by WLM.
You can check the status of online cell operations by using parolrad -m
command.
WLM GUI is not compatible with different versions of WLM
Issue
If you attempt to use the WLM GUI (wlmgui) with a version of WLM that
differs from the version the GUI is associated with, the following message is
displayed:
The WLM product running on <hostname> and this tool are
incompatible.
The version of the WLM GUI must match the version of the WLM product that
it manages.
Workaround Either upgrade WLM to the version of the WLM GUI you are using, or use an
earlier version of the WLM GUI that matches the version of WLM that your
GUI will manage. Note that multiple versions of the WLM GUI can be installed
on a Microsoft Windows PC.
"Message violation" error
Issue You see an error of the following form in /var/opt/wlm/msglog:
06/25/08 13:06:36 [E] (p19463) Message violation.
This error occurs when two different versions of WLM attempt to communicate
with each other.
Workaround Ensure all the hosts being managed together have the same version of WLM.
Upgrading or installing PRM before upgrading WLM can cause failed
swverify checks
Issue If you install or upgrade to the latest version of PRM (C.03.02 or later) on a
system with WLM A.03.00 or earlier, WLM will fail swverify checks.
Workaround To ensure that WLM works properly on a system with PRM C.03.02 or later,
upgrade WLM to A.03.02 or later. When upgrading WLM A.03.00 or earlier,
upgrade WLM prior to upgrading PRM.
20 Known problems and workarounds