A special Fortigate Check_MK plugin 2.3.1

Those of you who are suffered by the issue with duplicated service description, which is caused by a conflict of two different named checks: one built-in in Check_MK starting from 1.2.8 and one of mine.

This special version has other service descriptions and check names. The functionality is the same as in the version 2.3.

You can download the Check_MK package at the temporary place.

Update: After Robert had reported that the new version didn’t work under 1.2.8 and 1.4 versions of Check_MK, I have figured out that the plugin didn’t work (ran into an exception) because of a change between the versions 1.2.6 and 1.2.8 of Check_MK: the global variable nagios_state_names was renamed to core_state_names. Therefore I’ve created an updated version and am waiting for a confirmation, if this new version is working.

New Check_MK checks for DELL N-series switches


I have just uploaded a new package onto Check_MK Exchange. The package contains 2 checks for DELL N1500, N2000 and N3000 series switches. They check CPU utilization and RAM usage using SNMP requests. The checks have been created under 1.2.6 version of Check_MK and support this version.

After a verification by Check_MK staff the package can be downloaded from Check_MK Exchange web site.


Hermann Maurer

Fortigate Check_MK plugin updated to 2.3

Once again I have uploaded a new version of the Fortigate Check_MK plugin to Check_MK Exchange. The new version 2.3 got a new check called fortigate-wlan-info. This check is intended to display the following information about the usage of Fortiinet Access Points (FAP), connected to the monitored Fortigate:

  • Number of active FAPs
  • Numer of missed FAPs or those in down state
  • Numer of mobile clients connected to all FAPs

The new check has a Perf-O-Meter as well as an adjusted PNP4Nagios template.

The new vesion of the plugin can be (hopefully soon) downloaded from Check_MK Exchange.

Fortigate checks for Check_MK updated to 2.2.4

Hi there,

the only change is related to the check fortigate_mem. I have changed the evaluation of the parameters in the check. Now it’s possible to set warning and critical values in WATO. The old version did’t work and raised an exception.

I have uploaded the new version to Exchange of Check_MK. It should become available shortly.


Hermann Maurer

Retain changes in Netscaler 10.5 after reboot

If you have to do with Citrix Netscaler 10.5, you might have needed to change something on the installation, for example customize the layout of the authentication page. If you don’t take care a special way, your change will disappear after the next cold reboot of Citrix Netscaler. Continue reading

Monitoring Exchange 2013 mailbox databases with Check_MK

I confirm: the old check created some time ago (see this article) doesn’t work for Exchange 2013 installations. It seems to be be caused by significant changes on Powershell calls or cmdlets. I am having some troubles to get rid of the issue because I stepped away of Exchange business some time ago. A friend of mine is helping me to make the script working and I’ll hopefully publish a new version for Exchange 2013 very soon.

Stay tuned.

yum useful commands

To get a list of availale updates

yum -v check-update

To get a transaction list of last updates

yum -v history list

To get a list of changes during a transaction

yum history info <transactionID>

To remove obsolete kernel packages without questions

package-cleanup –oldkernels -y

Monitoring Citrix Netscaler with Check_MK

Hey there,

it’s at the time to share my experiences with the monitoring of Citrix Netscaler with Check_MK (below called CMK).

The so-called innovation release of CMK 1.2.7i contains some checks for Netscaler that are based on SNMP: Continue reading