HP Virtual Server Environment Management for Integrity Version 4.0 Release Notes

Ensure that the mode attribute for the sharedResourceDomain element is set to
the desired value (Managed or Advisory):
mode="Managed"
—
— Ensure that the interval attribute for the sharedResourceDomain element is
set to the desired value:
interval="x"
— Ensure that the ticapMode attribute for the sharedResourceDomain element
is set to all if you want gWLM to allocate TiCAP when needed:
ticapMode="all"
— Ensure that the workloadReference entries in the compartment definitions are
correct, and adjust the names in the workload definitions themselves. For example,
you might have host.OTHER.2 instead of host.OTHER.
3. Import the file to re-create the SRD:
# gwlm import --file=/tmp/myfile.xml --clobber
Because the SRD was already deployed, the new SRD definition is deployed on import,
taking the place of the original SRD.
• Workloads in gWLM Do Not Follow Associated Serviceguard Packages With the exception
of virtual machines, a workload can be managed by gWLM in only one deployed SRD at a
time. As a result, if a workload is directly associated with a Serviceguard package (using
the selector in the Workload Definition dialog), gWLM can manage it on only one of the
hosts on which it may potentially run. However, management of such a workload may
disrupt the Virtualization Manager and Capacity Advisor tracking of the workload utilization
between cluster members. Thus, it is recommended that you not directly manage a workload
associated with a Serviceguard package.
Workaround For all hosts to which a workload associated with a Serviceguard package
might fail over, you must apply a policy to an enclosing operating system instance (virtual
partition or nPartition). You can use a gWLM conditional policy to change the resource
allocation depending on which packages are present. This enables you to control the resource
allocation of the enclosing operating system instance and still monitor the workload via
Virtualization Manager.
• Host Name Aliases Are Not Supported Host name aliases are not supported by gWLM.
Only canonical DNS host names (fully qualified domain names) are supported.
Workaround Use only canonical DNS names when configuring gWLM through either
HP SIM or an XML file used with the gwlm command.
Major Issues
• Instant Capacity B.11.*.08.03.00.* Incompatible with gWLM Instant Capacity version
B.11.11.08.03.00.* (for HP-UX 11i v1), Instant Capacity version B.11.23.08.03.00.* (for HP-UX
11i v2) and Instant Capacity version B.11.31.08.03.00. (for HP-UX 11i v3) are not compatible
with gWLM.
Workaround Upgrade the gWLM-managed system to Instant Capacity version
B.11.*.08.03.01.*.
• Installing a Newer gWLM Agent on an Older CMS Makes System Unsupported You can
install a newer gWLM agent on a CMS using an earlier version of gWLM. For example, you
can install the A.04.00.07 agent on a system with CMS version A.02.00.00.x. This configuration
is invalid and leaves the VSE Management CMS software unusable. Starting with gWLM
A.04.00.07, the CMS software validates that the agent software version is within the past
two major releases and does not exceed the current release.
Global Workload Manager 39