Category Archives: Monitoring

Topics regarding monitoring

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 in 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

Hello,

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.

BR

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.

Cheers

Hermann Maurer

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.

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

Fortigate checks for Check_MK updated to 2.2.3

Hi there,

I’ve updated the package to the version 2.2.3. Please consider updating to the new version some time. The change concerns only the check fortigate_ipsec and corrects a bug, that can cause an issue, when a IPSec tunnel doesn’t exist anymore. In this case the check can disturb the execution of other checks and make it not possible to re-execute the inventory.

The new version 2.2.3 is located as always on the check_mk exchange site.

Best regards

Hermann Maurer

Fortigate checks for Check_MK updated to 2.2.2

Hi there,

again there has been a bug in the OID in the check fortigate_sessions. Or maybe I didn’t create the package carefully enough. Anyway there is a new version 2.2.2 and it’s located as always on the check_mk exchange site. Please consider updating as soon as possible, because the version 2.2.1 collects wrong values.

Best regards

Hermann Maurer

Collect pnp4nagios data in Check_MK distributed environment

Introduction

I hope you enjoy the great monitoring software Check_MK. If you have a big environment with lots of hosts and services distributed over dozen of sites (company locations) , you might have already configured your Check_MK to use the distributed monitoring in WATO. I assume that you have got a master and some slaves. The master in terms of Check_MK is the host, which you are using to configure your whole Check_MK installation and to look at all hosts and services, whilst slaves are those hosts that receive the configuration from the master and which the master gets the monitoring results from.  Distributed monitoring is an extremely nice and powerful feature of Check_MK that allows you to keep your configuration at one place and that takes care on distributing the changes on the configuration to the slaves. Also it’s very easy to connect a new slave to the master site.

Continue reading

Fortigate checks for Check_MK updated to 2.2.1

I’ve just uploaded a new version of the check to Check_MK Exchange site. This is a bug fixing version, is doesn’t contain any new features.

The new version includes a minor bug fix in fortigate_sslvpn check. I corrected the OID used there to get the value of the active SSL VPN sessions. The old versions might show a wrong number of active sessions. Please update the package.