Configuring other devices and applications

The other procedures in this section deal with only a few of the most common network devices and are a small subset of the devices that BMC Supports. Other popular devices supported by BMC Defender include (but are not limited to) Juniper, Nortel, 3Com, Netscreen, Snort and other equipment and software vendors, all of which provide syslog capability with their produces.

On Windows platforms, you can configure the Windows Agent log file monitor capability (for more information, see BMC Defender Agent for Windows) to tail any arbitrary streaming log file. This provides special application for monitoring such applications as Windows VPN, and Windows IIS. 

Additionally, many Windows applications can be configured to report status and error information to the Windows Application log that is then relayed to BMC Defender Server by the Windows Agent like any other event log message. These applications include IIS, MS Exchange, McAfee, Oracle, and MS SQL.

On UNIX platforms, you can configure a simple Perl script to tail streaming log files, such as the Apache server logs. An instance of such a Perl script is available under the Resources section of the BMC Defender Server. Additionally, you can configure the cron facility to send syslog messages in response to certain periodic system tests configured by a root administrator.

Note

BMC Defender receives SNMP Trap information in addition to syslog information. You can configure the SNMP agent of any capable device to send SNMP Traps to the BMC Defender Server at port 162. These traps appear as regular syslog messages within BMC Defender and are processed exactly like any other received message.

By default, SNMP Traps are assigned a facility of network and are assigned a severity as dictated by the BMC Defender SNMP Trap. For more information, see BMC Defender SNMP Trap Monitor adapter. 

 

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