I modified the package some weeks ago, The new version includes a check for temperature of each unit in a stack. I have uploaded the package to Check_MK Exchange site lately. It should become available after the verifitcation soon,
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.
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.
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
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.
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.
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.
In some distributed environments and with a lot of configured users and connection to Microsoft active directory configured in Check_MK times to distribute the changes from the master to all slave sites grow up strongly. Check_MK distributed monitoring uses Apache web server acting as reverse proxy. Sometimes one of Apache web server’s instances doesn’t return data within a pre-defined time range. In such cases you can get the error like this while trying to replicate your slave with the master site:
I had to configure OMD/Check_MK version 1.2.4p3 to use LDAPS to connect to Windows domain controller. The operating system on the host running OMD/Check_MK is CentOS 6.5 x64.
OMD provides some very useful commands to manage sites. Execute “omd help” as root to see all possible commands.