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
# /usr/sbin/swlist [-l patch] patch
where patch is the patch’s tag. For example, to check that patch PHKL_32061 is installed,
use the following command line:
# /usr/sbin/swlist -l patch PHKL_32061
Similarly, if you downloaded patch bundles in Step 1, check the bundles for the patches:
# /usr/sbin/swlist -d patch @ /tmp/bundle_name
If a given patch is not listed, check HP’s IT Resource Center (http://itrc.hp.com) for a
superseding patch, then use swlist to list the superseding patch.
c. Download any missing patches to /tmp.
If any of the required patches are missing (not installed or not in a bundle you
downloaded), download the patches from HP’s IT Resource Center:
Americas/Asia-Pacific http://itrc.hp.com/
Europe http://europe.itrc.hp.com/
NOTE: Do not install these patches at this point.
5. (Optional) Create a software depot to minimize system reboots
Creating a depot is beneficial when you are completing two or more of the following tasks:
• Installing patch bundles (GOLDQPK11i or HWEnable11i)
The patch bundles include kernel patches. Installation of a patch bundle requires a
system reboot.
• Installing PHKL_* patches
The PHKL_* patches are HP-UX kernel patches. Installation of these patches requires
a system reboot.
• Installing/upgrading WLM
The installation or upgrade of WLM requires a kernel rebuild and system reboot.
Completing two or more of the above tasks will cause multiple reboots unless you create a
software depot. With a depot including all the patches, the patch bundles, and WLM, you
can combine the installation steps into a single operation, thereby limiting the number of
installation reboots that must occur.
If you do not mind multiple reboots or your system will not be subject to multiple reboots
because its software is up-to-date, proceed to Step 6.
In order to install these items with a single swinstall(1M) command, all of the related filesets
must be collected into a single software depot distribution directory.
The following steps outline how to create a software depot. The steps use examples showing
how to include the following items in your depot:
• Quality Pack GOLDQPK11i (also known as a patch bundle)
• Patch PHKL_32619
• perl
• WLM
NOTE: To satisfy SD-UX, it may be necessary to copy dependency filesets into this common
depot.
a. Ensure that adequate disk space is available. The size of each patch can be found in its
README text.
Installation procedure 29