HP Matrix Operating Environment Software - Manual (Page 41)

# secure operating environment.)
#
# NOTE: GWLM_CMS_START=0 prevents automatic use at boot of
# HP Matrix OE visualization and
# HP Capacity Advisor.
GWLM_CMS_START=0
# Set GWLM_AGENT_START to 1 to have the init process start the gWLM agent
# daemon. (HP recommends setting this variable to 1 only when used in a
# secure operating environment.)
GWLM_AGENT_START=0
# Set GWLM_HOME to the location where gWLM is installed.
# Default is /opt/gwlm.
GWLM_HOME=/opt/gwlm
Automatic restart of gWLM’s managed nodes in SRDs (high availability)
Whenever a managed node boots, the node’s gWLM agent attempts to automatically rejoin the
node in its SRD, providing high availability. The only configuration steps you need to perform for
this behavior to happen are:
1.
Ensure the /etc/rc.config.d/gwlmCtl file on each managed node has
GWLM_AGENT_START
set to 1. You can run the following command on each system where
gwlmagent is running to make this change for you:
# /opt/gwlm/bin/gwlmagent --enable_start_on_boot
In the same file, you also need GWLM_CMS_START=1 on the system where gwlmcmsd is
running. However, when you ran vseinitconfig during installation, this change was
automatically made.
2. (Optional) Edit the property
com.hp.gwlm.node.HA.minimumTimeout
in the file /etc/opt/gwlm/conf/gwlmagent.properties to set the minimum number
of seconds that must pass before a managed node considers itself separated from its SRD.
Set this property to ensure that minor network problems do not cause a managed node to
prematurely consider itself separated.
gWLM uses this value only if it is larger than 10 multiplied by gWLM’s allocation interval. For
example, with an allocation interval of 15 seconds, a node can go 2.5 minutes without
communicating with its SRD before the node’s gWLM agent attempts to re-connect with the
SRD.
This feature works best when one managed node is lost at a time or all managed nodes are lost.
NOTE: If a vpar is borrowing cores from other vPars when it loses contact with its SRD, those
borrowed cores might be separated from the SRD. If the vpar might be down for an extended time,
check that the SRD has reformed without that vpar and that it has enough cores to meet its
commitments. If not, try using vparmodify to reclaim some of the cores. (With the vpar down,
you will not be able to modify it locally, and only some versions of HP-UX Virtual Partitions allow
you to easily modify a remote vpar.)
Similarly, if an npar has several active cores (due to Instant Capacity) when it loses contact with
its SRD, you might have to manually size the npar to reclaim those cores for nPars still in the SRD.
For more information, see the Instant Capacity documentation.
How the automatic restart works
When a managed node boots, the gWLM agent (gwlmagent) starts automatically if
GWLM_AGENT_START
is set to 1 in the file /etc/rc.config.d/gwlmCtl. The agent then checks
the file /etc/opt/gwlm/deployed.config to determine its CMS. Next, it attempts to contact
Automatic restart of gWLM’s managed nodes in SRDs (high availability) 41