Configure MIB for Linux

The ColdFusion Server MIB Agent uses the Dynamic Module approach of UCD-SNMP 4.2. To use the MIB Agent on your Linux system, you must make sure that UCD-SNMP 4.2.1 or higher is installed on your system. Then the ColdFusion Server 5 installation must be run to include the MIB option. For details about installing ColdFusion Server 5, refer to the book Installing and Configuring ColdFusion Server.
 

When you install the MIB Agent, the ColdFusion Server 5 installation asks whether you want to replace the current snmpd.conf with a version of snmpd.conf that will make ColdFusion MIB information accessible.  If you answer Yes, the current copy of snmpd.conf in /etc/snmp is renamed to snmp.conf_original, and the ColdFusion version of snmpd.conf is inserted into /etc/snmp.  If you answer No, a file called snmpd.conf_macromedia is placed into /etc/snmp.  You then have to merge the content from snmpd.conf_macromedia into snmpd.conf to make ColdFusion MIB information accessible.

 

After ColdFusion Server 5 installation, if you want to get ColdFusion runtime statistics, display the Debug Options page of the ColdFusion Administrator and activate the Enable Performance Monitoring option. Restart the ColdFusion Server after you change this option.

 

In addition, if you want to use HTTPS, a different Web server name, or a different port to access the Web document root for ColdFusion MIB information, you can modify the content of /usr/lib/btcats/database/mib.properties file. This file usually contains a single entry, such as http://maine. In this example, maine represents the name of the local host, and http://maine represents the Web document root directory for the ColdFusion MIB information. To use HTTPS, a different Web document root (maine1) and port (459) simply edit the entry to https://maine1:459.

 

If you want to add additional hosts to receive trap messages, take these steps:

  1. Stop the SNMP process by entering the following command as root:

    /etc/rc.d/init.d/snmpd stop

     

  2. For each server that is to receive trap messages from the local host, add the following line to /etc/snmp/snmpd.conf:

    trapsink server1.macromedia.com public


    where server1.macromedia.com is the name of the destination server, and public is the name of the community under which the trap messages are sent. Make sure that the destination server, such as server1.macromedia.com, is configured to receive traps from the specified community, such as public.

    Warning:
     Make sure that the following line does not appear in snmpd.conf more than once:

    dlmod allaire /usr/lib/btcats/program/allaire_mib.so  

     

  3. Start the SNMP process by entering the following command as root:

    /etc/rc.d/init.d/snmpd start

Related topics