Hardware Sentry KM for PATROL

Release Notes for v1.7.01

Home  Previous  Next

Changes and Improvements

The DegreesBelowWarning parameter of the MS_HW_CAPACITYREPORT class now triggers a warning when it reaches zero.
In the following classes, alert thresholds used an artificial limit value of 999999 which has been changed to 2^31 - 2 (2,147,483,646):
MS_HW_LOGICALDISK / ErrorCount
MS_HW_MEMORY / ErrorCount
MS_HW_OTHERDEVICE / Value
MS_HW_PHYSICALDISK / ErrorCount
MS_HW_ROBOTICS / ErrorCount
MS_HW_TAPEDRIVE / ErrorCount
MS_HW_TEMPERATURE / Temperature
MS_HW_VOLTAGE / Voltage

Fixed Issues

Hardware Sentry KM was not properly handling command return outputs that length exceeded 1 million characters resulting in the inability to create the corresponding instances.
An empty StatusInformation parameter was displayed even when no status was actually collected for Disk Controllers.
Cisco UCS instance names: Display names have been modified to better identify the monitored devices and to improve the integration of Hardware Sentry into BMC ProactiveNet Performance Management.
Voltage monitoring: Voltage values of -50V are now properly collected and displayed in the Console.
CPU monitoring: A discovery issue prevented the product from collecting CPU information on the first collect, resulting in error messages. Collects were properly performed afterwards
NetApp Filers: Hardware Sentry KM was not collecting global fan, temperature and power supply status from older versions of NetApp filers.
IBM VIO Servers monitoring: The connector for monitoring IBM VIO Servers failed to correctly identify the detection criteria.