[checkmk-commits] added manpage

Module: check_mk Branch: master Commit: 1348e34fed8b6c595179ce4dab65fee20fc72a9c URL: http://git.mathias-kettner.de/git/?p=check_mk.git;a=commit;h=1348e34fed8b6c… Author: Simon Betz <si(a)mathias-kettner.de> Date: Mon Jul 17 14:03:23 2017 +0200 added manpage Change-Id: Ib267770dce3f33d766445a26af937c8a3f41732b --- checkman/f5_bigip_cluster_status.v11_2 | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) diff --git a/checkman/f5_bigip_cluster_status.v11_2 b/checkman/f5_bigip_cluster_status.v11_2 new file mode 100644 index 0000000..6dd8ee9 --- /dev/null +++ b/checkman/f5_bigip_cluster_status.v11_2 @@ -0,0 +1,21 @@ +title: F5 Big-IP: active/active or passive/active cluster status +agents: snmp +catalog: hw/network/f5 +license: GPL +distribution: check_mk +description: + The check queries the MIB tables of F5 BIG-IP loadbalancers (local traffic managers) to identify + if the cluster correctly runs in an {active/active} or an {active/passive} setup. + You can configure the expected behaviour via a WATO rule. + It will issue a warning if the cluster setup differs from the expected setup. + This check is expected to be run on cluster hosts, since it evaluates the state of multiple nodes. + If you run this check on a cluster node, it will raise no warning if the cluster node state + differs from {active}. + + Since version 11.2 you are able to configure the node states. Default values are: + unknown will be treated as UNKNOWN, offline as CRIT, forced offline as CRIT, + standby as OK and active as OK. + +inventory: + Creates on service +