Basic installation steps

Each

BMC Defender Agent for Unix/Linux

package distributed on the BMC Electronic Product Download (EPD) website consists of individual .tar.gz files. Each file includes the name of the platform distribution, for example, RHEL, for Red Hat Enterprise Linux.

The basic installation procedure is as follows:

1. Download the installation files from the BMC Electronic Product Download (EPD) website. Your ability to access product pages on the EPD website is determined by the license entitlements purchased by your company.

2. On the target system, copy the tar.gz file, downloaded from the Windows platform above, to the directory that the BMC Defender directory created (typically either the /opt directory or the /usr/local directory).
   You can use a web browser or standard binary ftp.
3. Gunzip the tar.gz file, and then extract files using tar -xvf. For the ZUSS agent, extract files using tar -xvfo.
   This step creates the BMC Defender directory, which contains all the agent files for the platform.

4. Using a text editor, modify the CO-logmon.cnf file and specify the IP address of BMC Defender Server. 

   Warning

   Note

   You might sometimes miss this required step, and the default address of 127.0.0.1 might not work. The destination for syslog messages must be specified as part of the initial configuration.

5. Start the CO-logmon process, and optionally configure the CO-logmon process to start as a background process on the platform.
   You can typically accomplish this by editing the /etc/rc.local file, or by creating an /etc/rc.d startup script, depending on the particular target operating system.

   Warning

   Note

   The CO-logmon process does not fork and, by default, runs in the foreground. Therefore, you must specify an ampersand (&) character as part of the command invocation, to make this a background process.
   

   Even as a background process, the CO-logmon application can be terminated by the system if the parent shell process is terminated. To start the CO-logmon application on the command line, use the Unix no hang up command, nohup, with the following example command line:

   nohup ./CO-logmon </dev/null > /tmp/co-logmon.log 2>&1
6. Optionally, repeat step 4 and step 5 to install the CO-fmon file integrity monitor process.
   That is, using a text editor, modify the CO-fmon.cnf and specify the IP address of BMC Defender Server, and then start the CO-fmon process as a background process. 

The CO-logmon or CO-fmon programs can now run. On startup, each sends a single syslog message to the configured destination host. Check the host to verify that a message was correctly sent and received. No other steps are needed to install and start the program.