TrueSight Operations Management - NetApp Storage Monitoring

Release Notes v3.2.01

Home  Previous  Next

What's New

Support for Data ONTAP API v8.3.x.
The new configuration variable retryDiscoveryAfterNTimes was added to set the maximum number of retries when the discovery fails.

Changes and Improvements

New monitor types were created for Cluster Mode to better differentiate them from the 7-mode ones.
To provide better hardware detection in multiple-channel scenario, hardware instance names and IDs have been modified for power supplies, fans, voltages, and temperatures.
The collectionHubHeapSizeMax configuration variable is now set by default to 1024 megabytes.
Alert Actions:
Different types of PATROL events can now be triggered.
Event messages have been improved to provide more meaningful information.
Specific PATROL Events triggered upon failures now also specify the alert origin (ApplicationClassName.ObjectID.ParameterName).

Fixed Issues

The monitoring solution stopped collecting data when the collection status was failed.
Negative values were sometimes reported for attributes of the NetApp Ethernet Port monitor type (cluster mode).
In cluster mode, the monitoring solution failed to retrieve the SnapMirror status.
Warnings are no longer triggered  for zeroed disks.
An exception could occur:
when discovering disks in cluster mode.
when discovering volumes in cluster mode.
when discovering qtree.
when discovering quota in 7-mode.
when collecting disk information in 7-mode and caused the collect to fail.
when the value for an aggregate was null.


Known Issue

Java 1.8 uses TSL instead of SSLv3 which prevents the monitoring solution to connect to Data ONTAP. To use TrueSight Operations Management - NetApp Storage with Java 1.8, you will have to first enable TLS. For more information, please refer to the NetApp documentation.