IBM DS6000, DS8000 Series KM for PATROL

Release Notes v1.3.01

Home  Previous  Next

What's New

Alert Actions:
Different types of PATROL events can now be triggered
Event messages have been improved to provide more meaningful information.
In order to optimize the monitoring on large environment, users can now customize the discovery and the collect processes timeouts by using two new configuration variables: discoveryOperationTimeout and collectOperationTimeout.

Changes and Improvements

The System Output Window (SOW) messages generated by IBM DS6000, DS8000 Series KM for PATROL are now saved in the SEN_I68_debug_km_*.log debug file when the debug mode is activated.
Reinitializing the KM now also removes all the oldInstances.dat files.
The password algorithm encryption is now handled by the PATROL Agent.
The iQN (iSCSI Qualified Name) is now handled for host mappings. When available, IQNs are displayed in the Hosts parameter of the SEN_I68_VOLUME application class.
Specific PATROL Events triggered upon failures now also specify the alert origin (ApplicationClassName.ObjectID.ParameterName).

Fixed Issues

Java Settings - User Selection: the username entered in the "Java Settings" dialog box was not properly saved in the configuration.
IBM DS6000, DS8000 Series KM for PATROL could not be loaded when using a version of the PATROL Agent lower than v.9.5. This issue is now fixed.
IBM DS6000, DS8000 Series KM for PATROL has been modified to properly handle the discovery and the collect processes with java 1.8.
The conversion method used to calculate units for some duration-based parameters has been improved to report accurately on the actual collected data.
To avoid unnecessary duplicates, the Fiber Ports are no longer reported by the Hosts parameter of the SEN_I68_VOLUME application class, but are still listed in the Paths parameter.