Check manual page of datapower_fs

Installation
Check_MK - The official handbook Installation on a Linux server Installation of a virtual appliance Detailed Installation Instructions Getting Started with Monitoring Check_MK Versions Check_MK version update

Monitoring
Basic Principles of monitoring with Check_MK The user interface Host and service views Dashboards Commands Acknowledging problems Scheduled downtimes Performance data and graphing

Configuration
Configuring Check_MK Monitoring agents Host Administration Services host and service parameter Users, roles and permissions Time periods Notifications

Further Articles
Monitoring Linux Monitoring of VMWare ESXi Monitoring ORACLE databases Catalog of Check Plug-ins Datasource programs Local checks Monitoring instances (sites) Managed Services Edition Distributed Monitoring NagVis Integration of LDAP/Active Directory The event console Availability Automatic agent updates Alert handlers Reports Check_MK over HTTPS Check_MK's extension packages (MKPs) Regular expressions in Check_MK Check_MK on the command line Livestatus Livestatus: Command reference Web-API Web-API: Command reference Check_MK's simulation mode Kerberos The Check_MK micro core (CMC) CMC's files and directories Migration to the CMC Special characteristics of the CMC

Further Articles

Implementing extensions
Guidelines for coding check plug-ins

The Check_MK Appliance
Quick start guide for Check_MK rack1 cma_rail1_quick_start Quick start guide for Check_MK virt1 Hardware of Check_MK rail2 cma_rack1_hardware Setting up with VirtualBox Setting up with VMware ESX Basic configuration Administrating monitoring instances Administrating Check_MK versions Firmware installation Device settings Remote access via SSH Protecting web access via SSL Device control Backup Mounting network file systems Failover cluster SMS notifications Diagnostics RAID administration Management interface Service & support

The Check_MK Appliance

Miscellaneous
Copyright information

IBM Datapower Filesystems

This check monitors the state of filesystems on IBMs Datapower Gateways supporting the DATAPOWER-STATUS-MIB. It reports the filesystem utilization.

The usual limits for filesystem usage can be set and the state of a service is determined from these limits.

There are four possible filesystems on a datapower network with the following names: Encrypted, Unencrypted, Internal, Temporary.

One service is created for each of the four possible filesystems found.