DX Infrastructure Manager - UIM - Hitachi probe creating a lot of Self Monitoring Alarms
search cancel

DX Infrastructure Manager - UIM - Hitachi probe creating a lot of Self Monitoring Alarms


Article ID: 144262


Updated On:


DX Unified Infrastructure Management (Nimsoft / UIM)


After enabling hitachi probe, the customer is seeing a huge number of alarms as follow:


Release : 9.2.0

Component : UIM - HITACHI


A Self-Monitoring alarm will trigger when an Automonitor generation failed, Static monitor failed or Data collection failed.

Here is an example of the alarm in hitachi probe:

Failed to collect data for monitor 'LU (XXX.XXX.XXX.XXX:LU|2071|ARRAY|VSP G600.441979).Total Capacity'. Updated value will not be available.

In vmware probe, it is possible to manage the Self Monitoring alarms, as described in next technical document:


Those keys, however will not work with hitachi probe.


Engineering is aware the keys will not work with hitachi probe, as a defect has been open to report it. They will evaluate whether these keys can be made available for hitachi probe too.
As a workaround you may create a nas pre-processing rule to discard the Self Monitoring alarms:

File type: exclude
hostname: <robot hostname>
probe: hitachi
message: /Failed to collect data for monitor/

Additional Information

Hitachi probe, Revision History