Host name for TCP/IP network services
TCP/IP network services such as NIS, DNS, and the /etc/hosts
file must be configured to return the fully qualified host name (for
example: HostName.ibm.com). Define the fully qualified host name after
the dotted decimal host address value and before the short host name
in the /etc/hosts.
Use of fully qualified path names
Because of the wide variety of UNIX operating systems and possible user environments,
use fully qualified path names when entering a directory during the
installation process (do not use pattern-matching characters).
Multiple network interface cards
When more than one network interface card (NIC) exists
in the computer on which the monitoring server is
installed, you need to identify which NIC to use when specifying the monitoring server name
and host name.
Installing into an NFS environment
IBM supports installing IBM Tivoli Monitoring in
NFS environments. Using NFS, you can concentrate your software and
data in a specific location, minimizing maintenance, administrative
overhead, and disk space.
Installing into Solaris zones
There are limitations that must be taken into consideration
when installing into zones that share resources.
Architecture and product codes
On UNIX and Linux operating systems, some IBM Tivoli Monitoring files
are placed in directories whose paths include a code for the platform
architecture.
File descriptor (maxfiles) limit on UNIX and Linux systems
The monitoring server and Warehouse Proxy Agent can
use a large number of file descriptors, especially in a large environment.
On UNIX and Linux systems, the maximum number of file descriptors
available to a process is controlled by user limit parameters.
Installing into an existing installation
Installing components or agents in an existing CANDLEHOME or
installation directory is supported as long as the user ID used to
run the installation is always the same.