From 29df4e2eca223d65567b8830b378f5751c334dda Mon Sep 17 00:00:00 2001
From: thl-cmk <thl-cmk@outlook.com>
Date: Wed, 29 Sep 2021 18:58:48 +0000
Subject: [PATCH] Update checkpoint_vsx_system
---
checkman/checkpoint_vsx_system | 69 +++++++++++++++++-----------------
1 file changed, 34 insertions(+), 35 deletions(-)
diff --git a/checkman/checkpoint_vsx_system b/checkman/checkpoint_vsx_system
index 08ef898..23e6b2a 100644
--- a/checkman/checkpoint_vsx_system
+++ b/checkman/checkpoint_vsx_system
@@ -1,45 +1,44 @@
-title: Dummy check man page - used as template for new check manuals
-agents: linux, windows, aix, solaris, hpux, vms, freebsd, snmp
+title: Check Point VSX gateway state monitoring
+agents: snmp
+azthor: thl-cmk[at]outlook[dot]com
catalog: see modules/catalog.py for possible values
license: GPL
distribution: check_mk
description:
- Describe here: (1) what the check actually does, (2) under which
- circumstances it goes warning/critical, (3) which devices are supported
- by the check, (4) if the check requires a separated plugin or
- tool or separate configuration on the target host.
-
+ This plugin monitors the state of Check Point VSX gateways.
+ With default settings the VSX system gets {critical} if the H/A state is other than activ/standby,
+ the SIC trust is not established or the policy type is not active. The monitoring state becomes
+ {warning} if the policy name or the H/A state is differnet from discovery time. All this states are
+ configurable via WATO.
+
item:
- Describe the syntax and meaning of the check's item here. Provide all
- information one needs if coding a manual check with {checks +=} in {main.mk}.
- Give an example. If the check uses {None} as sole item,
- then leave out this section.
-
-examples:
- # Give examples for configuration in {main.mk} here. If the check has
- # configuration variable, then give example for them here.
-
- # set default levels to 40 and 60 percent:
- foo_default_values = (40, 60)
-
- # another configuration variable here:
- inventory_foo_filter = [ "superfoo", "superfoo2" ]
+ The system name.
perfdata:
- Describe precisely the number and meaning of performance variables
- the check sends. If it outputs no performance data, then leave out this
- section.
+ This plugin adds the following perfdata:
+ connections (count)
+ connections peak (count)
+ packets processed/s
+ packets dropped/s
+ packets accepted/s
+ packets rejected/s
+ bytes accepted/s
+ bytes dropped/s
+ bytes rejected/s
+ loggs send/s
inventory:
- Describe how the inventory for the check works. Which items
- will it find? Describe the influence of check specific
- configuration parameters to the inventory.
-
-[parameters]
-foofirst(int): describe the first parameter here (if parameters are grouped
- as tuple)
-fooother(string): describe another parameter here.
+ By default the inventory will discover {Virtual Systems}. Via WATO you can change this to discover also
+ the {VSX Gateway} itself, {Virtual Switches} and {Virtual Routers}.
+
+parameters:
+Here you can define all the monitoring states.
+ excample (default) parameters:
+ {
+ 'state_sic_not_established': 2, # SIC trust is not established
+ 'state_ha_not_act_stb': 2, # H/A state is other than activ/standby
+ 'state_policy_not_installed': 2, # policy type is not active
+ 'state_policy_changed': 1, # policy name changed
+ 'state_ha_changed': 1, # H/A state changed
+ }
-[configuration]
-foo_default_levels(int, int): Describe global configuration variable of
- foo here. Important: also tell the user how they are preset.
--
GitLab