I have developed a script that will check the Mitel system via SNMP to check the current alarm level, if there is an alarm it will then make another SNMP call to the alarm categories table and list the current list of alarms as part of the alert. The script requires the perl module Net::SNMP and can be downloaded from the download section at the bottom of this post.

Usage:

Usage: ./check_mitel.pl hostname [snmp community: Defaults to "public"]
            [snmp port: Defaults to "161"]

Check Command Definition:

define command{
        command_name    mitelalarm
        command_line    $USER1$/check_mitel.pl $HOSTADDRESS$ $ARG1$
}

Service Template Definition:

define service {
        name mitelalarm
        use base
        check_command mitelalarm
        register 0
}

Service Definition (replace “public” with the SNMP Community set on your Mitel controller):

define service {
        use base
        service_description Mitel Alarm Check
        check_command mitelalarm!public
        host_name mitelcontroller1
}

Download:

• check_mitel.pl

I have also been working on Cacti graphs of the Bandwidth management details, more on that early next month .

The solution involves using the check_nt plugin for Nagios and the Nagios pNSClient for windows, the following may work for any one of the Nagios Windows clients but you will have to test it for yourself.

Firstly the check command (Please click the View Source button in the code windows below to see the whole line)

define command{
  command_name    check_exchange_storage_group
  command_line    $USER1$/check_nt -H $HOSTADDRESS$ -p $USER19$ -w 1 -c 0 -v COUNTER -d SHOWALL -l "\\MSExchangeIS Mailbox($ARG1$)\Client Logons","$ARG1$ Logons: %.f"
}

$USER19$ on my installation is set to the port that Nagios Client for Windows uses. You will need to modify this to suit your needs.

Next define a Service Template

define service {
        name check_exchange_storage_group
        use base
        check_command check_exchange_storage_group
        register 0
}

Then define the service for each host you want to monitor

define service {
        use check_exchange_storage_group
        service_description Exch Storage Group - First Storage Group
        check_command check_exchange_storage_group!First Storage Group-Mailbox Store (ARCMAIL)
        host_name arcmail
}

The following line is the important part, this is what tells Nagios which storage group to monitor

check_command check_exchange_storage_group!First Storage Group-Mailbox Store (ARCMAIL)

To find out what you need to put after the ! (Exclamation Point) on the check command line check out your Exchange System Manager

And under “Administrative Group -> <<Admin Group Name>> -> Servers -> <<Server Name>>” should be your storage groups (In most cases it should look very similar to above, it will be different if you have a large Exchange installation).

You need to put the names of the Storage Group and Mailbox store together separated by a dash, the Storage Group name required to function for the installation shown above is:

First Storage Group-Mailbox Store (ARCMAIL)

You need to put the whole name in there otherwise the check command will return critical as it cant find the storage group you are trying to monitor.

That should be all that is required to monitor your individual Exchange Storage Groups. A possible caveat is that when some backup software backs up Exchange it will dismount the storage group and hence cause an alarm, if this is the case you will need to put in some exemption times into your Nagios installation.

My first app will be for a Nagios Pager service that will utilise the Push Notification features just released in iPhone OS 3.0. There will be two versions, Nagios Pager and Nagios Pager Pro. Nagios Pager will be a stand alone application that will talk to a backend service for delivering Push Notifications for Nagios alerts, Nagios Pager Pro will contain all the features of Nagios Pager as well as an iPhone based Nagios client.

The standard version will be released in the App Store for free and the Pro version will be for a small cost. There will also be various access methods for the backend service required for the Apple Push Notification Service (APNS). A free subscription to the backend will allow for one phone to access one nagios backend, while a paid subscription will allow for multiple phones access to multiple backends.

If you are interested in this service or you are interested in entering the beta program let me know via a comment and I will get in contact with you. Stay tuned for more development news.