Installation Tips For Dec Alpha Nt Managed Nodes - HP -UX B6941-90001 Administrator's Reference Manual

• The installation script checks if the IP address which is used for the
ITO installation is tied to the boot, service, or standby interfaces, and
issues a warning if this is the case. However, the installation proceeds
nonetheless.
• If you select automatic start of ITO agents, the file /etc/inittab is
also updated so that the clinit entry remains the last one - as is
required by HACMP.
• After successful installation of the ITO agent, the IP alias appears in
the /var/lpp/OV/conf/OpC/nodeinfo file in the field
OPC_IP_ADDRESS.
• The following line is added to the opcinfo file during installation
process:
OPC_NAMESRV_LOCAL_NAME <hostname>
where <hostname> is the name of the host configured with the IP
address used for the installation of the ITO agent. If this IP address
changes, this line should be changed accordingly. Note that this line
must be present in order to ensure that the IP address is the same in
the context of both ITO and ANS (ITO's Advanced Network Security
extension). This ensures that the same hostname is used by all
security functions that require <hostname> as their argument (e.g.
secret key generation). If this keyword is not present, ANSE functions
retrieve hostname from the RPC runtime, which is often different
from the hostname used for ITO installation, and the ANSE functions
will fail.
Installation Tips for DEC Alpha NT Managed
Nodes
For general information, see "Installation Tips for Windows NT Systems"
on page 99. Note the following important points:
path names differ only in the architecture name, for example:
• ...ms/intel/nt
• ...ms/alpha/nt
Fileset is: OVOPC-CLT-ENG.OVOPC-ANT-CLT
After entering Label and Hostname in the Add Node window, ITO
looks up and retrieves the following values:
Chapter 2
Installing ITO Agents on the Managed Nodes
General Installation Tips for Managed Nodes
61