Difference: Configuring CensorNet for SNMP monitoring ( vs. 1)

Synopsis: Configuring CensorNet for SNMP monitoring

Although CensorNet has the ability to issue alerts to administrators if resource thresholds are triggered (e.g. low disk space) some power users might prefer to use their existing SNMP management tool to monitor, report and alert about the status of the CensorNet server.

The following instructions will walk you through the steps to install the SNMP tools on the CensorNet server which will provide the OID's you need to manage CensorNet via your third party monitoring tool.

1: Log in as root, then install the SNMP daemon and the SNMP toolkit:

    root@censornet:~# apt-get update
    root@censornet:~# apt-get install snmp snmpd

2: Edit the snmpd defaults file to allow access from your network:

root@censornet:~# nano /etc/default/snmpd

Find the following line:

    SNMPDOPTS='-Lsd -Lf /dev/null -u snmp -I -smux -p /var/run/snmpd.pid 127.0.0.1'

and change it to:

    SNMPDOPTS='-Lsd -Lf /dev/null -u snmp -I -smux -p /var/run/snmpd.pid 0.0.0.0'

Hold CTRL + X then CTRL + S to save the file.

3: Delete the existing snmpd.conf file

root@censornet:~# rm /etc/snmp/snmpd.conf

4: Create a new snmpd.conf file

root@censornet:~# nano /etc/snmp/snmpd.conf

Paste in the following:

    rocommunity public

    proc  squid
    proc  CNv4
    proc  postgres

    disk  /

Hold CTRL + X then CTRL + S to save the file.

5: Restart the snmp daemon

  root@censornet:~# /etc/init.d/snmpd restart

6: You should now be able to monitor the server using the following OID's.

    15 Minute Load Average: 1.3.6.1.4.1.2021.10.1.3.3
    Check CNv4 Service is alive: 1.3.6.1.4.1.2021.2.1.100.2
    Check Squid Service is alive: 1.3.6.1.4.1.2021.2.1.100.1
    Check PostgreSQL is alive: 1.3.6.1.4.1.2021.2.1.100.3 
    Check free disk space on first partition (in %): 1.3.6.1.4.1.2021.9.1.9.1
    Check free memory (in kB): 1.3.6.1.4.1.2021.4.11.0
    Check System Uptime: 1.3.6.1.2.1.1.3.0

-- TimLloyd - 05 Mar 2010