HP Matrix Operating Environment Software - Manual (Page 63)

For HP-UX 11i v1, use version B.11.11.01.03.01.01 or later.
For HP-UX 11i v2 on HP 9000 servers, use version B.11.23.01.03.01.01 or later.
For HP-UX 11i v2 on HP Integrity servers, use version B.11.23.01.04 or later.
You can find the nPartition Provider at the following locations:
•
The quarterly AR CD starting May 2005
• The Software Depot website: http://software.hp.com
Modifying Java while gWLM is running
gWLM does not support any actions (including the use of update-ux) that remove, overwrite,
or otherwise modify the version of Java that gWLM is using in a managed node or CMS that is
part of a deployed SRD.
Workaround
Undeploy an SRD before taking any actions that affect the version of Java that
gWLM is using on systems that are part of the SRD. If you used update-ux, be sure to:
•
Restart the CMS daemon on the CMS
Using the command-line interface: /opt/gwlm/bin/gwlmcmsd
Using the HP SIM interface: Select the menus Configure
→ Configure VSE Agents → Start
gWLM CMS Daemon
• Restart the agent on the managed nodes
Using the command-line interface: /opt/gwlm/bin/gwlmagent
Using the HP SIM interface: Select the menus Configure
→ Configure VSE Agents → Start
gWLM Agent
Missing or unexpected historical data (system clocks differ)
You might have no historical data available for graphing, even though you are certain an SRD
was deployed for the time period in question.
A related issue occurs when you select a time period where you expect high system activity, but
the graph shows limited activity. Similarly, you might expect very little activity for a time period,
but the graph shows lots of activity.
Workaround
Check that the system clocks on the CMS and on all the systems in the SRD are
synchronized. If the clocks differ significantly, gWLM might not be able to match the data from
the managed nodes with the time period you are trying to graph.
Sample missing at start or end of gwlmreport output
A report from gwlmreport is based on a report period that starts at midnight the day the report
begins and ends at midnight the day the report ends. Any samples that overlap midnight at the
start or end of the report period are excluded from the report.
Workaround
There is no workaround, but you should be aware of this behavior.
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.
Only one SRD is allowed to be deployed
You might see a message similar to the following:
Error trying to deploy SRD, mysystem.vpar.000 to mysystem2.mydomain.com.
SRD, mysystem2.fss.000 is already deployed. Only one SRD is allowed to
be deployed.
Documentation or minor issues 63