ID: 11203
Title: Check for unique keys of host labels in ruleset conditions
Component: Multisite
Level: 1
Class: Bug fix
Version: 1.7.0i1
If you used host labels like "my_key:my_value" and "my_key:my_next_value" in
ruleset conditions, the rule was saved with the last "key:value" pair. From now
on you will be warned, if you try to configure the same key for different host
labels.
ID: 11364
Title: if_lancom: Never detect if if64-checks are disabled
Component: Checks & agents
Level: 1
Class: New feature
Version: 1.7.0i1
The check <tt>if_lancom</tt> monitors network interfaces of LANCOM devices
using 64-bit SNMP counters. Since there are devices with broken firmware which
by mistake report that they support 64-bit counters, checkmk offers the rule
"Hosts forced to use 'if' instead of 'if64'". This rule enforces the usage of
the 32-bit SNMP interface check <tt>if</tt> over the 64-bit version.
Up to now, the check <tt>if_lancom</tt> did not fully apply this rule. I.e.,
depending on the device, even if this rule was activated, <tt>if_lancom</tt>
might still have been discovered. With this werk, <tt>if_lancom</tt> is never
discovered if "Hosts forced to use 'if' instead of 'if64'" is activated.
This change might be incompatible for users who activated the rule "Hosts forced
to use 'if' instead of 'if64'". Currently discovered services will continue to
work, however, upon rediscovery, <tt>if_lancom</tt> might be replaced by <tt>if</tt>.
In such cases, users have to further restrict the hosts to which this rule is applied.
ID: 11204
Title: Fixed CSV export of host and service labels
Component: Multisite
Level: 1
Class: Bug fix
Version: 1.7.0i1
Previously, host and service labels in CSV exports were in JSON format. From
now on, labels will be separated by commas for such exports.
ID: 11266
Title: ups_out_load, ups_power: Fix discovery of output lines with zero load resp. power
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.7.0i1
Previously output lines were discovered in the check plugins {{ups_out_load}},
{{ups_power}} if and only if they had a value greater than zero.
Now we use the voltage value in order to decide whether a line is connected or
not.
ID: 11363
Title: if64, if64adm: Monitoring of the admin status <tt>ifAdminStatus</tt> for switch ports
Component: Checks & agents
Level: 1
Class: New feature
Version: 1.7.0i1
The 64-bit version of the interface check for switch ports can be configured
to also monitor the admin status <tt>ifAdminStatus</tt>. If this option is
activated, checkmk uses the check plugin <tt>if64adm</tt> instead of
<tt>if64</tt>. Up to now, only an <tt>ifAdminStatus</tt> of 2 was reported by
setting the port state to <i>9 - admin down</i>. With this werk, the admin
status is now monitored completely separately from the port state. Consequently,
the port state <i>9 - admin down</i> is not available any more.
Previously, the monitoring of the admin state was activated implicitly by configuring
checkmk to discover ports in the state <i>9 - admin down</i> (rule "Network Interface
and Switch Port Discovery"). Now, this is handled in a separate rule: "SNMP Interface
check: Monitor ifAdminStatus (use 'if64adm' instead of 'if64')". If and only if this
rule is activated, the admin status will be monitored, independently of the
configuration in "Network Interface and Switch Port Discovery".
Furthermore, since the admin status is now reported separately from the port state,
it can also be used to configure 1) the discovery of network interfaces (rule "Network
Interface and Switch Port Discovery"), 2) the monitoring state (rule "Network interfaces
and switch ports"). For example, you can make checkmk discover only interfaces with
an admin status of 2 or you can set the monitoring state of all interfaces with an
amdin status of 1 to WARNING. Note that these configuration options only have an
effect if the admin status is actually monitored, i.e., if the new rule mentioned
above is activated.
This change is incompatible for all users who are currently monitoring the admin
status using <tt>if64adm</tt>. These users should follow these steps:
<ul>
<li>Activate the monitoring of the admin status using the new rule "SNMP Interface
check: Monitor ifAdminStatus (use 'if64adm' instead of 'if64')".
</li>
<li>Check the discovery configuration (rule "Network Interface and Switch Port
Discovery"). As mentioned above, the admin state can now be used to further refine the
discovery of network interfaces. On the other hand, the port state <i>9 - admin down</i>
is not available any more, so users might have to adjust their configurations.</li>
<li>Re-discover the services of affected hosts.</li>
<li>Check the monitoring configuration (rule "Network interfaces and switch ports").
Analogously to the discovery configuration, the admin state can now be used to set
the monitoring state of network interfaces and the port state <i>9 - admin down</i>
is not available any more.</li>
</ul>