Collection of CheckMK checks (see https://checkmk.com/). All checks and plugins are provided as is. Absolutely no warranty. Send any comments to thl-cmk[at]outlook[dot]com

Skip to content
Snippets Groups Projects
Commit 29df4e2e authored by thl-cmk's avatar thl-cmk :flag_na:
Browse files

Update checkpoint_vsx_system

parent 97da1c28
No related branches found
No related tags found
No related merge requests found
title: Dummy check man page - used as template for new check manuals title: Check Point VSX gateway state monitoring
agents: linux, windows, aix, solaris, hpux, vms, freebsd, snmp agents: snmp
azthor: thl-cmk[at]outlook[dot]com
catalog: see modules/catalog.py for possible values catalog: see modules/catalog.py for possible values
license: GPL license: GPL
distribution: check_mk distribution: check_mk
description: description:
Describe here: (1) what the check actually does, (2) under which This plugin monitors the state of Check Point VSX gateways.
circumstances it goes warning/critical, (3) which devices are supported With default settings the VSX system gets {critical} if the H/A state is other than activ/standby,
by the check, (4) if the check requires a separated plugin or the SIC trust is not established or the policy type is not active. The monitoring state becomes
tool or separate configuration on the target host. {warning} if the policy name or the H/A state is differnet from discovery time. All this states are
configurable via WATO.
item: item:
Describe the syntax and meaning of the check's item here. Provide all The system name.
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" ]
perfdata: perfdata:
Describe precisely the number and meaning of performance variables This plugin adds the following perfdata:
the check sends. If it outputs no performance data, then leave out this connections (count)
section. 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: inventory:
Describe how the inventory for the check works. Which items By default the inventory will discover {Virtual Systems}. Via WATO you can change this to discover also
will it find? Describe the influence of check specific the {VSX Gateway} itself, {Virtual Switches} and {Virtual Routers}.
configuration parameters to the inventory.
parameters:
[parameters] Here you can define all the monitoring states.
foofirst(int): describe the first parameter here (if parameters are grouped excample (default) parameters:
as tuple) {
fooother(string): describe another parameter here. '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.
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment