Branch: refs/heads/master
Home:
https://github.com/tribe29/checkmk
Commit: 85c7406f5d72cdc0a4fdc5f126ecfbe7de6ab2c8
https://github.com/tribe29/checkmk/commit/85c7406f5d72cdc0a4fdc5f126ecfbe7d…
Author: Lars Michelsen <lm(a)tribe29.com>
Date: 2020-12-07 (Mon, 07 Dec 2020)
Changed paths:
A .werks/11752
M cmk/base/checkers/snmp.py
M cmk/base/config.py
M cmk/base/default_config/base.py
M cmk/gui/plugins/wato/check_mk_configuration.py
M cmk/gui/watolib/__init__.py
M tests/unit/cmk/gui/watolib/test_rulespecs.py
Log Message:
-----------
11752 FIX Management board: SNMP bulk walk can now be configured
SNMP Management boards were previously contacted with different SNMP settings.
SNMP management boards on non-SNMP hosts always used SNMPv1 (no bulk walk)
while SNMP management boards of hosts that are also monitored with SNMP,
inherited the bulk walk option from the host.
With Checkmk 2.0 it is now possible to explicitly configure this setting using
the ruleset "Management board SNMP using bulk walk (enforces SNMP v2c)".
Sites created with Checkmk 2.0 or newer will automatically use SNMPv2 and bulk
walks for all SNMP management boards. For compatibility reasons the behaviour
of existing sites is kept as initially described. However, in case your devices
support SNMPv2 and bulk walks, it is highly recommended to use it, for performance
reasons. In case you want to change to SNMPv2, you can create a rule without
condition in the ruleset "Management board SNMP using bulk walk (enforces SNMP
v2c)" to switch the default to SNMPv2 and bulk walks.
Change-Id: I9d80789a8ccefcbbdb4a0753f0c386e5238a517b