ID: 2474
Title: Fixed possible corruption of user datasets (contact, mail, rbn config)
Component: WATO
Level: 1
Class: Bug Fix
Version: 1.2.7i3
When moving user notification rules in an installation where a lot of users
are working with the GUI, it could happen that the file which stores contact,
mail and user rbn configuration (contacts.mk) could corrupt and lead to lost
attributes for all the users.
ID: 2410
Title: ESX / agent_vsphere: Now able to re-use session cookies
Component: Checks & Agents
Level: 1
Class: New Feature
Version: 1.2.7i3
The agent_vsphere now reuses the session cookie as long as possible.
This prevents large amounts of Logon/Logoff messages in the vCenter log.
Whenever the cookie gets invalid the agent starts from the beginning, carries out
a normal login and refreshes the outdated cookie.
ID: 2289
Title: New checks: aix_hacmp_resources, aix_hacmp_services, aix_hacmp_nodes
Component: Checks & Agents
Level: 1
Class: New Feature
Version: 1.2.7i3
The checks aix_hacmp_resources, aix_hacmp_services and aix_hacmp_ndoes monitor the resource groups, cluster services and active nodes of
the HACMP cluster manager. These checks need the check_mk_agent.aix agent.
ID: 2288
Title: check_mk_agent.aix: New sections for HACMP cluster manager
Component: Checks & Agents
Level: 1
Class: New Feature
Version: 1.2.7i3
New sections of the aix agent to monitor resource groups, services and active nodes of HACMP cluster manager.
ID: 2409
Title: AIX DB2 monitoring: the agent plugin now processes all db2 instances in parallel
Component: Checks & Agents
Level: 1
Class: New Feature
Version: 1.2.7i3
The mk_db2.aix plugin now uses a separate cache file for each db2 instance.
This allows parallel processing of all instances at the same time.
The performance of the system should not suffer. It was tested on a system with 50+ db2 instances.
Furthermore the db2 checks will no longer all report UNKNOWN when an instance is stopped.
The instance checks will now go stale (no data was reported) and the db2_version check will
go to CRIT.
The db2_logsizes check now finally works.. There was a typo in the previous checkname.
ID: 2473
Title: cisco_asa_failover: Reworked check to reflect expected primary/secondary states of devices
Component: Checks & Agents
Level: 1
Class: Bug Fix
Version: 1.2.7i3
The check was keeping the current cluster/node states which the devices had during service
discovery as reference state and checks whether or not this state remains and raises an
error when the state changed.
This has been changed now. The state during discovery is not relevant anymore. The check
now looks at the primary/secondary devices and checks whether or not the primary device
is the active one or the secondary has been promoted to be the active one. This should
be clearer for users.
ID: 2286
Title: hp_procurve_cpu, hp_procurve_mem, hp_procurve_sensors: now can monitor HP 2920 Switch Stack
Component: Checks & Agents
Level: 1
Class: New Feature
Version: 1.2.7i3
Now the checks hp_procurce_cpu, hp_procurve_mem and hp_procurve_sensors monitor HP 2920 Switches.
ID: 2472
Title: MSSQL Agent Plugin: Can now be configured to auth as database user
Component: Checks & Agents
Level: 1
Class: New Feature
Version: 1.2.7i3
The mssql.vbs script can now be configured to authenticate as database user
using a configured username / password combination. Previously it was only
possible to authenticate using the system privileges of the user the agent
is running with. This is still the default.
If you need to authenticate as database user, you need to create a file
named <tt>mssql.ini</tt>, or if you need it instance specific,
<tt>mssql_[instance-id].ini</tt>. You need to write the following content
into this file:
F+:mssql.ini
[auth]
type = db
username = monitoring-user
password = mysecretpw
F-: