|
Important: If you have previously installed the version 3.0.00 of NetApp KM for PATROL, delete the SEN_NAP_<storagesystem-name>_oldInstances-<Hostname-port>.dat file from the PATROL_HOME\lib folder before installing.
What's New
| • | NetApp Filers configured in Cluster-Mode are fully supported by NetApp Filers KM for PATROL. |
| • | The product now integrates hardware monitoring features. |
| • | NetApp Filers are now monitored through the NetApp ONTAP API. Therefore, numerous parameters have been added to better cover all aspects of the NetApp Filers performance and hardware components health. Refer to the Reference Guide for more details. |
| • | LUNs and Volumes Monitoring: it is now possible to disable the monitoring of all the volumes or all the LUNs of a system to limit the number of instances created and therefore reduce the system resource consumption |
| • | NetApp Filers KM for PATROL. allows you to manually acknowledge alerts and reset the ErrourCount parameter of the SEN_NAP_7|C_SIS_VOLUME application class. |
| • | It is now possible to specify which volumes will be monitored or not by using the configuration variables excludeVolumes and includeVolumes. |
| • | It is now possible to generate activity reports for clusters, nodes, controllers, Ethernet and FC ports, Host Adapters, iSCSI, NVRAM, vFilers and volumes. |
| • | The new TimeSinceLastActivity parameter reports the number of days since the last read or write operation has been observed on the monitored LUN. |
| • | The PortCount parameter has been added to the the SEN_NAP_7_STORAGESYSTEM and the SEN_NAP_C_CLUSTER classes to report on the number of ports in these devices. |
Changes and improvements
| • | Application classes have been completely reorganized to better reflect the NetApp Filers internal structure. Refer to the Reference Guide for more details. |
| • | A backup of the PATROL Agent configuration is now performed and saved in the $PATROL_HOME/config directory before a reinitialization of the KM. |
Fixed Issues
| • | The issue that lead to make the product stop operating has been fixed by modifying the method used to discover plexes. |
| • | The NetApp client method 'selectInstances' could not manage non existing key IDs returned by the server, preventing the KM to perform the discovery of the related devices. |
| • | Discovery exceptions are now managed locally and traced in the product debug. |
|
