HP-UX Workload Manager A.03.04.xx Release Notes for HP-UX 11i v1, HP-UX 11i v2, and HP-UX 11i v3 HP Part Number: B8843-90045 Published: November 2009 Edition: 2.
© Copyright 2000-2009 Hewlett-Packard Development Company, L.P Legal Notices The information contained in this document is subject to change without notice. Hewlett-Packard makes no warranty of any kind with regard to this documentation, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose.
Starting with version A.03.00, HP-UX Workload Manager uses libxml2, the XML C parser and toolkit developed for the Gnome project at MIT. Though it is written in the C language, a variety of language bindings make it portable to other environments. It is licensed under the agreement available at /opt/wlm/lib/README.libxml2. The version of libxml2 that HP-UX Workload Manager uses is libxml2 2.6.10.
Table of Contents 1 Announcement................................................................................................................9 2 New in this version......................................................................................................11 3 Known problems and workarounds ..........................................................................13 System panic when PRM is enabled; install failure in absence of PRM when certain kernel patches are present.......................
Installation procedure ..........................................................................................................................25 Using the swinstall Graphical User Interface (GUI)..................................................................34 5 Patches and fixes in this version ................................................................................37 6 Software availability in native languages ................................................................39 7 Security....
List of Tables 4-1 4-2 4-3 4-4 4-5 Verified software configurations...................................................................................................22 HP-UX 11i v1 (B.11.11) general support patches..........................................................................26 HP-UX 11i v2 (B.11.23) general support patch..............................................................................26 HP-UX 11i v1 (B.11.11) patches for WLM........................................................
1 Announcement HP-UX WLM A.03.04 runs under the following HP-UX operating systems and hardware: Operating Systems Hardware HP-UX 11i v1 (B.11.11) HP 9000 servers HP-UX 11i v2 (B.11.23) HP 9000 servers and HP Integrity servers HP-UX 11i v1 (B.11.11) and HP-UX 11i v2 (B.11.23) Servers combining HP 9000 partitions and HP Integrity partitions; in such environments, HP-UX 11i v1 (B.11.11) supports HP 9000 partitions only HP-UX 11i v3 (B.11.
2 New in this version This section lists the new or changed functionality for WLM A.03.04. WLM A.03.04 supports HP-UX 11i v1 (B.11.11), HP-UX 11i v2 (B.11.23), and HP-UX 11i v3 (B.11.31). • • • WLM now supports IPv6. Change in wlmd -p behavior: When managing with both wlmd and wlmpard, if you use wlmd -p, you must also use wlmpard -p. WLM now accepts user names that contain only numbers.
3 Known problems and workarounds This section discusses problems and workarounds. System panic when PRM is enabled; install failure in absence of PRM when certain kernel patches are present Issue On HP-UX 11i v1, a system panic problem occurs when Process Resource Manager (PRM) is enabled. In addition, WLM installation fails when certain core kernel patches are present and PRM is absent. Workaround Install the version A.01.00.00.
Temporary Instant Capacity (TiCAP) expires while WLM is managing nPartitions Issue WLM manages nPartitions using its wlmpard daemon. Assume wlmpard is started on a system that has Temporary Instant Capacity in use. If that temporary capacity expires, wlmpard will still be able to deactivate cores without any problems. However, wlmpard may attempt to activate cores based on the expired capacity. These attempts will fail because the temporary capacity no longer exists.
# 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.
modifications have not yet completed. They can take longer than 120 seconds. When the modifications have been made, WLM will honor the shutdown request. You can verify the shutdown has succeeded by using the ps command (if necessary, issue your shutdown command again). In addition, check the messages in /var/opt/wlm/msglog. Unable to get CPU allocation due to number of processes Issue WLM provides a workload group its allocation on a system by granting the group its allocation on each core.
GlancePlus may not correctly identify processes’ PRM groups Issue On some systems, GlancePlus would not correctly identify processes’ PRM groups. WLM uses these PRM groups as its workload groups. On these systems, GlancePlus would report all processes as belonging to the PRM_SYS group (ID 0). As a result, the WLM glance_prm data collection script could not be used to track application (APP) metrics for a PRM group of processes. Workaround This issue is fixed in GlancePlus C.03.35.00.
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.
Processes in transient FSS groups appear unexpectedly in other workload groups Issue A deployed WLM configuration that has transient_groups set to 1 and contains FSS transient group candidates from time-to-time contains an FSS group called _IDLE_. As needed, WLM moves the jobs of the transient groups to _IDLE_, where they get the minimum of CPU and memory resources. The internal identifier for group _IDLE_ is picked by WLM on the fly (taken from the pool of unused identifiers).
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.
4 Compatibility information and installation requirements 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.
Table 4-1 Verified software configurations Software package Version on HP-UX 11i v1 (B.11.11) Version on HP-UX 11i v2 Update Version on HP-UX 11i v3 2 (B.11.23) (B.11.31) PRM C.03.04 C.03.03.01 C.03.04 Processor Sets A.01.00.00.07 The PSET version included with HP-UX The PSET version included with HP-UX Serviceguard A.11.15 (HP recommends using A.11.17 or later) A.11.17 A.11.17 HP Systems Insight C.05.02 Manager C.05.02 C.05.01 Instant Capacity (iCAP) for use in nPartition management B.
NOTE: Do not use GlancePlus to change PRM allocations. WLM controls PRM. Compatibility with HP Integrity Virtual Machines WLM supports HP Integrity Virtual Machines (Integrity VM). You can run WLM both on the Integrity VM Host and in an Integrity VM (guest), but each WLM runs as an independent instance.
Compatibility of psrset and PSETs When WLM is managing PSETs, do not use the psrset command to change settings. Compatibility with PRM As of version A.03.01, WLM no longer includes PRM in the bundle. As a result, upgrading WLM no longer triggers a reboot. WLM will run only with PRM C.03.00 or later. If PRM C.03.00 or later is already on the machine where you are installing or upgrading WLM, you can continue to manage FSS and PSET-based workload groups just as if PRM had been installed with WLM.
Compatibility with Java To run the WLM GUI (wlmgui) or wizard (wlmcw), Java Runtime Environment version 1.5 or later is required. For PRM-based configurations, these interfaces require PRM C.03.00 or later. To take advantage of the latest updates to WLM, use the latest version of PRM (C.03.02 or later). Installation procedure If you are installing WLM from the quarterly Application Release (AR) media, use the procedure in this section to minimize system reboots.
1. Verify that HP-UX is up-to-date HP suggests that as part of your systems’ ongoing maintenance and support, the systems be kept up-to-date through the HP IT Resource Center’s Support Plus program. This program delivers quarterly patch bundles via the web and as part of the quarterly AR media. To register, go to the following location: http://itrc.hp.com Select the patch/firmware database link and register to create an account and log in, as instructed.
• HP IT Resource Center (http://itrc.hp.com) Refer to the “maintenance/support” link. • HP Technical Documentation (http://docs.hp.com) Refer to the HP-UX 11i v1 topics “Installing and Updating” and “Patch Management”. 2. (Optional) Configure long hostnames Ensure the NodeHostNameXpnd bundle is installed if you want to use long host names on HP-UX 11i v2 or v3. Configure long host names as described below.
4. Determine what patches are needed a. Check the following data to determine what patches are suggested for WLM: If you plan to use the WLM configuration wizard, the wlmgui command, or wlminfo’s interactive mode GUI (-i), all of which depend on Java (Java Runtime Environment version 1.5 or later is required), refer to the following location for patch information: http://www.hp.com/go/java In addition, running these utilities with PRM-based configurations requires PRM C.03.00 or later.
# /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.
b. Create a directory for the depot: # mkdir /tmp/wlm_depot c. d. Place any patch bundles you downloaded in Step 1 (GOLDQPK11i or HWEnable11i) in /tmp/ if they are not already there. Check each of the patch bundles. # /usr/sbin/swlist -d @ bundle_path For example, check GOLDQPK11i as follows: # swlist -d @ /tmp/GOLDQPK11i_11.11.depot The output should include lines similar to the following lines: GOLDAPPS11i B.11.11.0312.4 Gold Applications Patches for HP-UX 11i v1, December 2003 GOLDBASE11i B.11.11.
• • expsmooth utility from the WLM BEA WebLogic Server Toolkit (WebLogicTK) wlmcert utility and secure network communications and perl is not available at /opt/perl/bin/perl: • If perl is not already installed, add it to your depot from the quarterly Application Release (AR) media using the following swcopy line: # swcopy -s mount_path perl \* @ /tmp/wlm_depot where mount_path is the path to the quarterly AR media. • k. l.
Also shut down any running instances of the WLM global arbiter: # /opt/wlm/bin/wlmpard -k 9. Install patches and install/upgrade WLM NOTE: The procedure below explains installation using the command-line version of swinstall. For information on using the swinstall GUI, refer to the section “Using the swinstall Graphical User Interface (GUI)” (page 34). WLM is bundled as B8843CA, which contains the products Workload-Mgr, WLM-Monitor, and WLM-Dev tools.
NOTE: Starting with WLM A.03.01, WLM no longer requires a reboot. The autoreboot option need no longer be set to true to satisfy requirements of the HP PRM kernel-building fileset PRM-Sw-Krn.PRM-KRN. Consequently, the SD-UX Interactive User Interface no longer prompts for an OK to reboot. Installing from the media NOTE: Installing without the benefit of a depot may cause unnecessary reboots. For information on reducing reboots, see Step 5 on creating a software depot.
12. (Optional) Install files for integration with HP Systems Insight Manager If you plan to use WLM with HP Systems Insight Manager, install the fileset CMSConfig.WLMB-CMS-Tools on the CMS. This fileset is available from the depot /var/opt/mx/depot11 on the host where WLM has been installed. If you are installing this fileset on a CMS that has WLM installed, the installation will fail if the fileset is not compatible with (does not have the same revision string as) the installed WLM. 13.
NOTE: If this was the first time you installed WLM and you have not previously installed PRM, be sure to edit the file /etc/rc.config.d/prm to set the following variables as indicated: PRM_CONFIG=0 PRM_RMTCONF=0 These settings prevent PRM and its remote configuration daemon from starting automatically at reboot. (The PRM remote configuration daemon is not useful with WLM and does not need to be started.
5 Patches and fixes in this version There were no patches or fixes to previous releases to include in WLM A.03.04.
6 Software availability in native languages The manpages are available only in English. The release notes and user’s guide are available in English and Japanese.
7 Security This section highlights security items you should be aware of. Relationship between host name and SSL certificates SSL certificates are created when you install WLM. This enables WLM to run in secure mode within the system on which it is installed. As of version A.03.01, when you start WLM using the “/sbin/init.d/wlm start” script, the script uses secure mode by default.
• • • Rely—only to the extent that you trust your intranet—on the monitoring information from wlmgui to decide on a course of action. The WLM GUI sends data to wlmcomd over the network without verifying the recipient. Each connection to wlmcomd represents a separate process on the system. As such, each connection consumes resources, such as open file descriptors, a process ID, memory, and so forth. A large number of connections could result in denial of service.
8 Available manuals Several related manuals are available. These manuals can be accessed at http://docs.hp.com. They are also available for order. Specific WLM information can be found in: • HP-UX Workload Manager User’s Guide (B8844-90014) The release notes for each version of WLM can be found at http://docs.hp.com. The user’s guide is available in /opt/wlm/share/doc/.
9 WLM toolkits Hewlett-Packard provides integration toolkits to simplify integrating Workload Manager with major third-party applications. The toolkits are made available on the web as they are developed. Also, they are bundled with the subsequent Workload Manager release. To download toolkits, visit the Workload Manager web page: http://www.hp.
10 Providing feedback • Email your feedback to the WLM and WLM Toolkit development teams at the following address: wlmfeedback@rsn.hp.com • For a forum with other WLM users, visit the IT Resource Center’s forum for HP-UX Workload/Resource Management: http://forums.itrc.hp.com/cm/ • For the latest patch information, white papers, and documentation, visit the Workload Manager web page: http://www.hp.
11 Training HP offers a course in HP-UX resource management using WLM. For information, including a course outline, visit: http://www.hp.com/education/courses/u5447s.
*B8843-90045* Printed in the US
