This section details some deployment considerations which will affect the configuration, operation, and the quality of the data that you can obtain using BMC Atrium Discovery.
Process to Communication Mapping (LSOF)
BMC Atrium Discovery uses the lsof command to map processes to network communications on some UNIX-like operating systems. This enables Reasoning to accurately map software applications that span multiple hosts.
Some organizations choose not to install lsof and other diagnostic tools on their UNIX systems. If lsof is not installed on your UNIX systems you will not be able to relate the communication to processes on those systems.
Do not use pfiles in Solaris Zones -- Potential Data Loss
The lsof utility cannot obtain process communication information from the local zone in Oracle Solaris operating systems. Performing a search on the Internet shows possible workarounds using pfiles. Using pfiles can result in data loss on the Solaris host. Oracle highlights the danger of using pfiles in the warnings section of their own documentation.
You should configure the NTP service on the Community Edition Virtual Machine. This is of particular importance if it will be involved in consolidation. If you do not configure NTP, the appliance time can drift backwards, preventing the datastore from validating itself. This in turn prevents the system from restarting. See Configuring the NTP client for more information.
Solaris 8 and
In Solaris 8 there are two
In all versions of Solaris other than 8, there is a single binary and a symbolic link.
The default path statement set by BMC Atrium Discovery ensures that
/sbin/ifconfig is called first. In Solaris 8 this is the incorrect version,
/usr/sbin/ifconfig must be run to obtain the correct information. To ensure this is the case, edit the
ifconfig discovery script to specify the full path to