Error message Failed to collect data for monitor from HP_3PAR probe

Products

• DX Unified Infrastructure Management (Nimsoft / UIM)
• Unified Infrastructure Management for Mainframe
• CA Unified Infrastructure Management SaaS (Nimsoft / UIM)

Issue/Introduction

HP_3PAR probe is failing to collect data.

Error message from hp_3par logs:

Aug 03 07:40:32:305 [Data Collector - 1, hp_3par] stdout: 07:40:32.305 [Data Collector - 1] ERROR tgraph2.TGraph2 - Attempting to add vertex that already exists.id: '/ar:idsProbe:ur-3par01:PORTS|0:2:2:.CtdDisplayAttribute'

Aug 03 07:40:32:305 [Data Collector - 1, hp_3par] hp_3parInventoryUnexpected error encountered while attempting to add PORTS 'ur-3par01:PORTS|0:2:2' to inventoryAttempting to add vertex that already exists.id: '/ar01:PORTS|0:2:2:.CtdDisplayAttribute'
Aug 03 07:40:32:305 [Data Collector - 1, hp_3par] java.lang.IllegalArgumentException: Attempting to add vertex that already exists.id: '/ar:idsProbe:ur01:PORTS|0:2:2:.CtdDisplayAttribute'
 at tgraph2.TGraph2.addVertex(TGraph2.java:43)
 at com.nimsoft.ids.ctd.graph.CtdGraphBase.addVertex(CtdGraphBase.java:130)
 at com.nimsoft.ids.ctd.graph.CtdGraphProbeConfiguration.addDisplayAttributes(CtdGraphProbeConfiguration.java:475)
 at com.nimsoft.probe.storage.hp3Par.sdk.Inventory.addComponent(Inventory.java:278)
 at com.nimsoft.probe.storage.hp3Par.sdk.Inventory.addManagedElement(Inventory.java:251)
 at com.nimsoft.probe.storage.hp3Par.sdk.Inventory.addArrayManagedElement(Inventory.java:243)
 at com.nimsoft.probe.storage.hp3Par.sdk.Inventory.populateGraph(Inventory.java:219)
 at com.nimsoft.probe.storage.hp3Par.sdk.Inventory.update(Inventory.java:133)
 at com.nimsoft.probe.storage.hp3Par.sdk.Hp3ParSession.updateInventory(Hp3ParSession.java:126)
 at com.nimsoft.probe.common.ctd.CtdSession.doInventoryUpdate(CtdSession.java:253)
 at com.nimsoft.probe.common.ctd.ProbeDataCollector.executeSessionUpdateInventory(ProbeDataCollector.java:952)
 at com.nimsoft.probe.common.ctd.ProbeDataCollector.execute(ProbeDataCollector.java:234)
 at com.nimsoft.vm.collector.DataCollector.run(DataCollector.java:146)
 at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
 at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
 at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
 at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
 at java.lang.Thread.run(Thread.java:748)
 
Aug 03 07:40:33:861 [BulkSender Monitor, hp_3par] Sent NimAlarm C, severity=4, message==Failed to collect data for monitor '0:2:2.Availability'. Updated value will not be available., subsystem=5.5, suppressionid=-1540412481, source=null and received confirmation id VL69319626-41507
Aug 03 07:40:33:861 [BulkSender Monitor, hp_3par] Sent NimAlarm D, severity=0, message==usdal-str-3par01 is now responding, subsystem=2.10.2.1, suppressionid=usdal-str-3par01, source=usdal-str-3par01 and received confirmation id VL69319626-41508
Aug 03 07:40:33:861 [BulkSender Monitor, hp_3par] Sent NimAlarm D, severity=4, message==Failed to collect data for monitor '2:0:2.Availability'. Updated value will not be available., subsystem=5.5, suppressionid=-1666280641, source=null and received confirmation id VL69319626-41509

subsystem=5.5 is invalid so udata mapping for source doesn't happen. This results in the alarm having the robot IP address for the alarm host name instead of the profile. 

 

Cause

-Probe compatibility

Environment

Release : 20.3

Component : UIM- HP_3PAR

Resolution

1. Save probe attached on this KB
2. Deploy the HP_30par-1.2.4-T9.zip from your local drive to the UIM Server Local Archive.
3. Deploy HP_30par-1.2.4-T9.zip from the Archive folder to the robot.