Remote configuration


The behavior and operation of the CO-logmon and CO-fmon programs are driven by their individual configuration files, which reside in the same directory as each program and have a .cnf suffix. Depending on organizational requirements, you might need to change the configuration file to receive particular messages of interest.

You can manually edit a configuration file and then restart the CO-logmon or CO-fmon program. Doing so requires administrative access to the UNIX platform that is hosting the program and configuration file. This method is the most secure way of implementing a change.

As a special facility, configuration files can also be remotely accessed, downloaded, and uploaded to make automated changes. This method requires various permissions and adaptations described in this section. Specifically, the remote configuration capability is limited by the value of the ListenAuthMode directive within CO-logmon.cnf and CO-fmon.cnf. ListenAuthMode controls and limits remote requests via the source address of the client, the passkey, or both. The most secure ListenAuthMode setting is 3, which requires a valid passkey and requires the client to be at the same IP address as the destination address.

For CO-logmon and CO-fmon, remote configuration capabilities permit a high degree of flexibility, security, and maintainability. The following topics discuss how system installers, administrators, and operations personnel can use these capabilities:

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC Defender Agent for Unix/Linux 6.2