How to monitor MailCleaner with SNMP

MailCleaner comes in with a dedicated MIB that can be accessed at https://[your mailcleaner]/admin/downloads/MAILCLEANER-MIB.txt

This SNMP MIB gives access to daily counts and statistics as long as system status such as spool level, processes status, versions, etc…

[Deprecated] Old configuration (pre 2012)

First, you'll need to open the system firewall in order to let your monitoring system to access the snmp daemon.
Go to the administration interface, under ConfigurationExternal Access.
Then add the ip address or network of your monitoring system in the “SNMP access” field (multiple ip addresses or networks should be separated with ”:”, do not include spaces !).

Actually a known bug prevent the system to add the hosts in the snmpd configuration, so wou'll have to open it manually like this:

echo "USE mc_config; UPDATE snmpd_config SET allowed_ip='0.0.0.0';" | /usr/mailcleaner/bin/mc_mysql -m
/usr/mailcleaner/etc/init.d/snmpd stop; sleep 2
/usr/mailcleaner/etc/init.d/snmpd start
    

Then configure your snmp client to get informations. Here are the few more traps provided by MailCleaner:

  • extOutput.1 (1.3.6.1.4.1.2021.8.1.101.1) : number of filtered messages (integer)
  • extOutput.2 (1.3.6.1.4.1.2021.8.1.101.2): number of spams detected (integer)
  • extOutput.3 (1.3.6.1.4.1.2021.8.1.101.3): number of bytes filtered (integer)
  • extOutput.4 (1.3.6.1.4.1.2021.8.1.101.4): number of viruses detected (integer)
  • extOutput.5 (1.3.6.1.4.1.2021.8.1.101.5): processes status (boolean list e.g: |1|1|1|1|1|1|1|1).
    Definition and order of processes (0 = down, 1= running):
    • incoming MTA (critical)
    • queuing MTA (critical)
    • outgoing MTA (critical)
    • Web GUI (not critical)
    • antispam/antivirus process/filtering engine (critical)
    • master database (not critical)
    • slave database (critical)
    • firewall (not critical)
  • extOutput.6 (1.3.6.1.4.1.2021.8.1.101.6): spools status, number of messages in queues (integer list, e.g.:|190|4|26)
    Definition and order of spools:
    • incoming : incoming MTA. Messages can be stored here on massive attacks, or when the MailCleaner is used as an outgoing relay for your network.
    • filtering: main engine spool. Messages are stored here when processed by the engine. Less than 300 messages is normal because messages are NOT deleted here until process if completly finished). More messages can be an indication that your system is getting a little bit busy at the time.
    • outgoing: outgoing MTA. MEssages are stored here when they cannot be delivered immediatly (temporary failure of destination host)
  • extOutput.7 (1.3.6.1.4.1.2021.8.1.101.7):system load (load) (float list, e.g. |5.29|3.79|3.55)
    Definition and order of loads:
    • 5 minutes: 5 last minutes average
    • 10 minutes:10 last minutes average
    • 15 minutes: 15 last minutes average dernières minutes
  • extOutput.8 (1.3.6.1.4.1.2021.8.1.101.8): disk partitions usage (list of string, e.g. |/|32%|/var|35%)
  • extOutput.9 (1.3.6.1.4.1.2021.8.1.101.9): system memory usage (integer list, e.g. |2068628|177144|1951888|1936572)
    Definition and order of usages:
    • total physical memory
    • free physical memory
    • total swap memory
    • free swap memory
  • extOutput.10 ((1.3.6.1.4.1.2021.8.1.101.10): all daily counts (integer list)
    Definition and order of counts:
    $total_bytes|$total_msg|$total_spam|$percentspam|$total_virus|$percentvirus|$total_content|$percentcontent|$total_clean|$percentclean
    • number of bytes filtered
    • number of messages filtered
    • number of spams detected
    • spam percentage
    • number of viruses detected
    • viruses percentage
    • number of dangerous content detected
    • dangerous content percentage
    • number of clean messages
    • clean messages percentages
documentation/snmp_monitoring.txt · Last modified: 2013/05/13 10:00 by olivier1
 
 
 
Recent changes RSS feed Valid XHTML 1.0 Valid CSS