7.0.8 Insight Remote Support Monitored Devices Configuration Guide

Monitored Devices Configuration Guide
Chapter 13: Configuring OpenVMS Servers
l ALTPRI
l BUGCHK
l CMKRNL
l DIAGNOSE
l IMPERSONATE
l NETMBX
l SYSPRV
l TMPMBX
Grant Cluster Node Access to ELMC Install Directory
The installation package only can install itself on cluster nodes that have access to the target directory
where you choose to install ELMC. Another way to explain this is that the nodes must mount the disk
containing the target directory. This means that an installation might not always place ELMC on all cluster
nodes, since all nodes might not be able to identify the place where ELMC is being installed.
The following illustrate this issue:
l Cluster: All nodes share the same system disk.
Install Node: Any node.
Install Target: The default location SYS$COMMON:[HP...].
Result: ELMC installs itself for all nodes.
l Cluster: All but two nodes share system disk A. The other two nodes share system disk B.
Install Node: A node that uses system disk A.
Install Target: The default location SYS$COMMON:[HP...].
Result: The other two nodes will not have ELMC.
In the previous case, you can install ELMC one more time for the remaining two nodes by running the
install from either node and again choosing the default location of SYS$COMMON:[HP...]. Consider
this a completely separate ELMC installation from the first install on the majority of the nodes.
l Cluster: All but two nodes share system disk A. The other two nodes share system disk B. All nodes
also mount a non-system disk C.
Install Node: Any node.
Install Target: A directory on disk C, specified by you during the installation.
Result: ELMC installs itself for all nodes.
Note: In all cases the installation package also lets you choose only a subset of the nodes that
can see the install location.
HP Insight Remote Support (7.0.8)Page 102 of 248