See the previous post for more details on usage, the only difference in this version is the SNMP error checking which does not impact usage or installation.

Installation

Place the check_cuda file in the nagios libexec folder along with all your other check plugins.  Don’t forget to
set permissions and ownership as appropriate for your installation.  Version 3 was tested under PHP5 and should work with either 4 or 5 by simply using check_cuda.  Be sure to edit the check_cuda script and set the value of $cuda_firmware (line 10) to either 3 or 4 depending on the firmware version of the Barracdua Spam and Virus firewalls you will be using the plugin to check.

Usage

Usage: check_cuda <host-ip> <community-string> <queue> <warning-threshold> <critical-threshold>

Queue can be either in, out or bounce for firmware version 3 firewalls; for version 4 firewalls the values are
in, out, deferred or latency

Warning and Critical values should be positive integers

Prerequisites

This plugin requires php and php_snmp support (as noted this version has been tested with PHP 5)

Nagios Configuration

Commands

Define commands as shown below:

define command {
command_name Check Barracuda Inbound Mail Queue
command_line $USER1$/check_cuda $HOSTADDRESS$ public in 500 1000
}

define command {
command_name Check Barracuda Outbound Mail Queue
command_line $USER1$/check_cuda $HOSTADDRESS$ public out 500 1000
}

Obviously you will need to change the SNMP community string from public to match your community string. If you wish you could also add a check command to track the bounce/deferred queue and even averagelatency on version 4 firmware. You may also want to use different warning and critical threshold than I did (500 and 1000 respectively). These numbers may not be right for your situation.
Contact Groups

Add a service group like the one below (customizing for your site of course):

# contactgroups Cuda Admins
define contactgroup {
contactgroup_name Cuda_Admins
alias Cuda_Admins
members joe,sally,fred
}

Service Templates

define service {
name Check Barracuda Mail Queue Template
use generic-service
contact_groups Cuda_Admins
register 0
}
Services

Add the service as needed to your hosts, sample shown below:

define service {
service_description Check Barracuda Inbound Mail Queue
use Check Barracuda Mail Queue Template
host_name yourcuda
check_command Check Barracuda Inbound Mail Queue
}

define service {
service_description Check Barracuda Outbound Mail Queue
use Check Barracuda Mail Queue Template
host_name yourcuda
check_command Check Barracuda Outbound Mail Queue
}

Here is an excerpt from the Barracuda version 4 release notes that describes the new OID/Objects and their meanings:

A special note of thanks to Ray who pointed out that the plugin needed an update to support the new firmware and for testing the new version.  Thanks Ray!

The upgrade process was pretty simple, and other than a few annoying items (having to deauthorize the computer in iTunes prior to the upgrade, and having to deinstall ATI drivers) it was mostly painless.  The upgrade did take several hours for me, as I do have a good amount of data (around 130GB).

I had to reinstall Roxio Easy Media Creator suite afterwards to get rid of an annoying messages about the Roxio Cine Player Media Decoder being missing.  Also, the screen seems odd.  The resolution setting is set the same as it was under Vista at 1440×900, but it looks like it has an odd aspect ratio.  I was hoping to install new ATI drivers, but it appears Gateway has NO drivers at all for Windows 7 yet (see screenshot below).

No Windows 7 Drivers

So far the upgrade has been fine other than the look of the screen.  New features are nice, I like the sticky and the fact that sleep mode works, peeking at the desktop, and the photo support for the desktop background and screensaver, but I like stability and reliability even better.  Time will tell if Windows 7 delivers, but so far so good.

The installation remains the same as the original version, and you can find the details here. Dioni’s version adds reporting of sound and video changes to the hardware script, and adds software change reporting (added or removed) via ocssoftware.php.

Don’t forget to change the email addresses in ocshardware.php and ocssoftware.php on lines 15,16 and 17.

Once you are done the related cron jobs are likely to look something like this:

10 * / 1 * * php * apache / usr / share / ocsinventory-reports / ocsreports / ocssoftware.php
10 * / 1 * * php * apache / usr / share / ocsinventory-reports / ocsreports / ocshardware.php