HP-UX Workload Manager User's Guide

Managing SLOs across partitions
Recommendations, requirements, and restrictions
Chapter 7 257
Recommendations, requirements, and
restrictions
To successfully manage WLM SLOs across partitions, observe the
following:
• HP recommends running WLM global arbitration in secure mode.
If you do not run WLM global arbitration in secure mode, a rogue
user could manipulate the communications, resulting in one or more
partitions being granted an incorrect number of cores. To enable
secure communications, set up security certificates and distribute
them to all systems or partitions being managed by the same WLM
global arbiter (wlmpard). For more information, see “Securing WLM
communications” on page 244 and wlmcert(1M).
Assuming you have completed the required steps for setting up and
distributing security certificates, WLM global arbitration runs in
secure mode by default when you use the /sbin/init.d/wlm script to
start WLM. (If you upgraded WLM, secure mode might not be the
default. Ensure that the WLMPARD_SECURE_ENABLE variable in
/etc/rc.config.d/wlm is enabled.) You can also activate global
arbitration in secure mode by using the -s option with the wlmpard
command. HP recommends using secure communications. If you
must disable secure communications, use global arbitration only on
trusted local area networks. For more information on enabling or
disabling secure communications, see “Securing WLM
communications” on page 244.
For information on using global arbitration with firewalls, see
wlmparconf(4).
• When running WLM within an Integrity VM (guest), do not use
Instant Capacity, Pay per use, and vPar integration.
Such integration is not supported when running WLM within an
Integrity VM at that level. However, an Integrity VM will take
advantage of cores added to the Integrity VM Host by Pay per use
(PPU), Instant Capacity (iCAP), and Temporary Instant Capacity
(TiCAP). When running WLM on an Integrity VM Host, use a strictly
host-based configuration.