search cancel

self-monitoring hp_3par alarms are generated without the met_id and dev_id

book

Article ID: 244433

calendar_today

Updated On:

Products

DX Unified Infrastructure Management (Nimsoft / UIM) CA Unified Infrastructure Management On-Premise (Nimsoft / UIM)

Issue/Introduction

Self-Monitoring alarms hp_3par probe (v1.25) instances are generated without a dev_id and met_id

Example:
Failed to collect data for monitor 'cage1.Operator Panel State. Update value will not be available

Example of error in hp_3par log:
[Data Collector - 1, hp_3par] Data point lookup failed for '"ESC:DCI:TOR_3PAR_AZ6_WY20:DCI|ifc-0|DC|cage1"."ESHState"', attempting to use raw data value
[Data Collector - 1, hp_3par] Failed to collect data for monitor 'ifc-0.ESH State'. Updated value will not be available.
[Data Collector - 1, hp_3par] (38) , Lookup failed for value of monitor '"ESC:DCI:TOR_3PAR_AZ6_WY20:DCI|ifc-0|DC|cage1"."ESHState"'. GUI will not display current value or severity. Will try again next polling cycle.
 at com.nimsoft.probe.common.ctd.CtdSession.setMonitorValueInGraph(CtdSession.java:782)


Environment

Release : 20.3

Component : UIM- HP_3PAR

Resolution

Self-monitoring alarms will not have any dev_id and met_id as no value is collected.

Available options:

Option 1: A nas pre-processing rule can be use to exclude such alarms. See url below

https://techdocs.broadcom.com/us/en/ca-enterprise-software/it-operations-management/ca-unified-infrastructure-management-probes/GA/alphabetical-probe-articles/nas-alarm-server/nas-im-configuration/the-nas-auto-operator-tab.html#concept.dita_68181394ea354dade5c0e878c25c3babd80ca6a3_ThePreProcessingRulesTab

Option 2: Disable the suspect monitor in the alarm from the template if none of them are being collected.
Example of QOS_DISK_CAGE_OPERATOR_PANEL_STATE, QOS_DISK_CAGE_INTERFACE_CARD_OPERATIONAL_STATE...

Use the query below to check if a specific QOS is collected from any of the hp_3par sources

SELECT *
FROM [S_QOS_DATA] AS def
JOIN [S_QOS_SNAPSHOT] AS snap ON snap.table_id = def.table_id
AND snap.[sampletime] > dateadd(hour, -1, getdate())
AND probe = 'hp_3par' and qos = 'QOS_DISK_CAGE_OPERATOR_PANEL_STATE'


Use the query below to check QOS collected for the hp_3par probe and see if QOS reported in alarms is listed

SELECT distinct qos
FROM [S_QOS_DATA] AS def
JOIN [S_QOS_SNAPSHOT] AS snap ON snap.table_id = def.table_id
AND snap.[sampletime] > dateadd(hour, -1, getdate())
AND probe = 'hp_3par

Option 3: Submit an enhancement request so feature on adding device information for such alarms can be considered in future releases

https://knowledge.broadcom.com/external/article/12135/how-to-raise-an-enhancement-request-for.html

https://knowledge.broadcom.com/external/article/34730/how-to-submit-an-idea-feature-request-to.html