HP Virtual Server Environment Management for Integrity Version 4.0 Release Notes
ERROR: Task 'Secure gWLM Communications' terminating.
This message is displayed when a communications certificate file
hostname-certificate-file has been corrupted or is not valid.
Workaround
1. Delete the hostname-certificate-file specified in the error message from the
following location on the CMS:
— HP-UX:
/etc/opt/gwlm/certs/hostname-certificate-file
— Windows:
C:\Program Files\HP\Virtual Server
Environment\conf\certs\hostname-certificate-file (although a
different path may have been selected at installation)
2. Run the Secure gWLM Communications tool again.
• Setting Policy Weights to Zero Results in Skewed Allocation This issue affects only gWLM
A.02.00.00.x agents.
Policy weights help gWLM determine resource allocations when excess resources exist. With
the weights for all the policies used in an SRD set to the same value, resources should be
allocated evenly to the associated workloads. However, setting the weights to zero for all
the policies in an SRD results in a single workload being allocated all the excess resource.
Workaround Instead of zero, use a weight value of one.
• Workload with Fixed Policy Gets More Resources Than Requested In an SRD with nested
partitions, assigning fixed policies where the sum of the fixed values is less than the minimum
of the parent compartment can result in workloads getting more resources than specified
in the fixed policies.
Workaround Set up the fixed policies so that the number of CPUs requested is greater
than or equal to the minimum number of CPUs required by the parent compartment.
• Convergence Rate and OwnBorrow/Utilization Policies This issue affects gWLM A.02.00.00.x
agents.
The convergence rate value that you (optionally) specify when defining a policy affects only
custom policies. OwnBorrow and utilization policies are not affected.
Workaround There is no workaround. However, this issue is addressed starting in
gWLM A.02.00.01.x agents.
• Custom Metrics Lost on Redeploy Custom policies use metric values that you provide via
the gwlmsend command. If you redeploy an SRD that has a custom policy, the most recent
value for the policy's metric is lost. In this situation, gWLM bases its allocations on the
minimum request specified in the workload's policy. The workload can also receive any
CPU resources that remain after all the policies have been satisfied.
Workaround Update the metric values for all your custom policies immediately after a
redeploy.
• Multiple SRDs Based on Virtual Partitions Can Occur Typically, gWLM does not allow you
to create multiple SRDs based on virtual partitions on a single nPartition or system at the
same time. However, when multiple gWLM users are deploying SRDs at almost the same
time, gWLM might inadvertently allow such multiple SRDs.
Workaround Delete one of the SRDs and then remanage the workloads from the deleted
SRD by placing them in the remaining SRD.
48 Known Issues