What's New
• | IBM DS6000, DS8000 Series KM for PATROL is now compatible with BMC ProactiveNet Central Monitoring Administration. This feature is supported by BMC ProactiveNet Performance Management version 9.0.00. |
▪ | FC ports are now listed in the LUNs Mapping Table report. |
▪ | The list of mapped/unmapped LUNs can now be sorted by storage unit. |
▪ | The Per Host Storage Allocation and Per LUN Storage allocation reports, were added to indicate how much storage is allocated to each monitored LUN and Host. |
▪ | 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. |
• | Additional information were added to the product's Infobox. |
• | A connection to a subsystem can now be directly configured from the SEN_I68_SMISPROVIDER_CONT application class. |
• | The new TimeSinceLastActivity parameter reports the number of days since the last read or write operation has been observed on the monitored LUN. |
Changes and Improvements
• | 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_68/disableJRECheck variable in the PATROL Agent's configuration. Warning: Apache JRE is not supported. |
• | The Debug mode was modified to ensure BPPM 9.x compatibility |
KM Commands
• | The KM commands menu has been reorganized. |
• | The “Modify Alert Thresholds” KM Command has been removed from most classes, as the thresholds can now be managed by PATROL administrators in a standard way through the Event Management KM and PCM (or any other method used in their environment). |
• | The Restore Device Monitoring KM Command has been 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
• | The Restore Monitoring KM command lists devices to restore even when the SMI-S Provider was removed from the monitored environment. |
|