ID: 2781
Title: Fix role handling of "Custom Links" snapin in case of adapted roles
Component: Multisite
Level: 1
Class: Bug Fix
Version: 1.2.7i4
If you have defined you own roles then a user had not correctly been mapped
to <tt>user</tt>, <tt>guest</tt> or <tt>admin</tt> when selecting the right
portions of the custom links in the snapin. This has been fixed. Thanks to
Molchanov Alexander.
ID: 2848
Title: Fixed cleanup of old autocheck files of cluster hosts
Component: Core & Setup
Level: 1
Class: Bug Fix
Version: 1.2.7i4
The autocheck entries of clustered services were stored in
[cluster].mk autocheck files in past versions. Current versions
are now storing the autochecks in the node specific files.
The old [cluster].mk files were not cleaned up during discovery
leading into duplicate autochecks entries. As these files were
never updated again, they could result in unwanted services on
the cluster hosts. This could be fixed manually by removing the
[cluster].mk autocheck files via command line.
The current version is now cleaning up the files during discovery.
ID: 2779
Title: Fix moving of folders
Component: WATO
Level: 2
Class: Bug Fix
Version: 1.2.7i4
This fixes the error message <i>Cannot move folder: A folder with this name
already exists in the target folder.</i>
ID: 2803
Title: netapp_api_volumes: clustered volumes now longer show the current node name in the service description
Component: Checks & Agents
Level: 1
Class: New Feature
Version: 1.2.7i4
Previously, the volume checks went UNKNOWN on a cluster failover.
The service description for clustered volumes has changed from <i>"{node}.{volume_name}"</i> to <i>"{volume_name}"</i>.
ID: 2841
Title: emcvnx_writecache: the check monitors the write cache state of the storage processors of an EMC VNX Storage System
Component: Checks & Agents
Level: 1
Class: New Feature
Version: 1.2.7i4
ID: 2865
Title: fortigate_memory_base: added check for fortigate firewall memory usage
Component: Checks & Agents
Level: 1
Class: New Feature
Version: 1.2.7i4
The fortigate_memory check uses data provided by a more "generic" fortinet mib, this one uses the
fortigate mib. Apparently a device provides only one of the two mibs so there shouldn't be a
collision.
ID: 2840
Title: barracuda_mail_latency, barracuda_mailqueues, barracuda_system_cpu_util: new checks for Barracuda SPAM Firewall Appliance
Component: Checks & Agents
Level: 1
Class: New Feature
Version: 1.2.7i4
These checks monitor the active and deferred mail queues, the mail latency and the system cpu utilization
of a Barrcuda SPAM Firewall Appliance.
Moreover the barracuda_mailqueues check reports the incoming and daily sent mails.