IBM SVC KM for PATROL

Release Notes for v1.1.00

Home  Previous  Next

What's New

The new TimeSinceLastActivity parameter reports the number of days since the last read or write operation has been observed on the monitored LUN.

The new TimeSinceLastStatisticsUpdate parameter reports the number of minutes since a new statistics file was created on the cluster.

Changes and Enhancements

The Debug mode was modified to ensure BPPM 9.x compatibility.

It is now possible to disable the validation tests of the JRE used by the KM to run Java code and therefore force the KM to use a non-Sun or non-Oracle JRE. To disable the validation test, set the /SENTRY/SEN_SVC/disableJRECheck variable in the PATROL Agent's configuration. Warning: Apache JRE is not supported.

Reporting

Reports Scheduling: Activity and LUNs Mapping Table reports can now be generated every day at a specific time. The information, retrieved as a text file, can later be used by other tools such as BMC Capacity Optimization.

Two new reports are available: Per Host Storage Allocation and Per LUN Storage Allocation. They report on the volume of storage respectively allocated to each monitored host and LUN.

LUNs Mapping Table:

A sorting order can now be specified.

The size of the LUNs is now displayed to allow administrators to know how much storage is being allocated to each host.

KM Commands

The KM Commands menu has been reorganized.

The "Restore Device Monitoring" KM command was renamed "Restore Monitoring". The user interface was also simplified to reduce the number of operations required to restore the monitoring of a component.

 

Fixed Issues

Some special characters were not supported in a password, leading to the product not being able to connect to the IBM SVC System.

Devices still appeared in the console after using the Remove Device Monitoring feature.

The Restore Monitoring KM command lists devices to restore even when the SMI-S Provider was removed from the monitored environment.

On UNIX AIX systems, the IP address resolution was incorrectly interpreted. This problem prevented the KM to proceed with the discovery and the collect processes.