Filter
Top Products
50 Chapter 2
Installing ITO Agents on the Managed Nodes
General Installation Tips for Managed Nodes
Installation Tips to be Performed on the
Management Server
❏ If you want to stop the configuration and script/program distribution,
for example, if the configuration is invalid, clean the /distrib
directory. This should only be done in an emergency and only after
the ITO management server processes have been stopped.
/var/opt/OV/share/tmp/OpC/distrib
❏ Avoid interrupting the software installation or de-installation process
on managed nodes. Doing so will cause a semaphore file to be left on
the management server, and you will not be able to re-invoke the
installation. In this case, remove the file manually.
/var/opt/OV/share/tmp/OpC/mgmt_sv/inst.lock
If you interrupt the software installation or de-installation on the
managed nodes at the time you are asked for a password, your
terminal settings will be corrupted and any commands that you type
will not be echoed in the terminal. If this happens, you can reset the
terminal by typing the following:
stty echo
❏ Do not de-install any of the management server bits, for example
OVOPC-ORA or OVOPC, if any managed node is still configured and has
the appropriate ITO bits.
❏ Do not de-install the managed node tape images (for example OVOPC-
CLT-ENG/JPN) from the management server, if any managed node of
this type is still configured and has the ITO bits installed on it. If you
do, you will be unable to de- install the ITO agent software using the
ITO GUI.
Installation Tips for UNIX Managed Nodes
General Tips
❏ Make sure that uname(1M) returns the short system name.
❏ The nameservice (/etc/hosts and/or DNS) needs to be set up so
that all name-service operations (like nslookup) are consistently
resolved to the fully-qualified system name. For example, hostname
is not name-service related and may return the short hostname.