Probe discovery problem

[Joakim E]

Hi,

We're having issues with probe discovery in OC inventory where not all probes are visible for a number of robots. For instance, some robots only show vmware probe in the inventory but are in fact deployed with other probes like cdm, logmon and processes. And some robots only show cdm probe but other probes are deployed as well. Has anybody seen this behaviour? We're on UIM 23.4.1.

[Rajesh Banuka]

Hi Joakim,

The OC inventory screen shows the probe list only if you configure the probe to collect any QOS. Did you create any profile from IM/AC/MCS on the probes (processes or logmon) not appearing in the list. You may cross verify the QOS list on the device on metric views or PRD or SLM. 

Rgds,

Rajesh B

[Joakim E]

Hi Rajesh!

Yes, we are getting QOS metrics for the cdm probe, metrics seen in performance report designer. But the cdm probe is not showing in the inventory for some hosts. What could the problem be?

[Rajesh Banuka]

Hi Joakim,

This could be an issue with mismatch of CI_METRIC_ID with that of CI. 

Could you please verify for one of the device has wrong monitoredby list returning all the QOS records from below query.  Replace <server_name> with actual server name. 

SELECT DISTINCT d.cs_id, cs.name, qd.probe FROM s_qos_data qd JOIN cm_configuration_item_metric cim ON cim.ci_metric_id = qd.ci_metric_id
JOIN  cm_configuration_item ci ON ci.ci_id = cim.ci_id
JOIN  cm_device d on d.dev_id = ci.dev_id
JOIN CM_COMPUTER_SYSTEM cs ON cs.cs_id = d.cs_id
WHERE cs.name = '<server_name>'

If the list doesn't return proper QOS list for the probes, please follow the KB to fix the issue. The step 4.c will help reset the CI_METRIC_ID issue. 

https://knowledge.broadcom.com/external/article/45476/troubleshooting-missing-data-in-uim.html

Rgds,

Rajesh B

[Joakim E]

Thanks Rajesh,

You're right, it seems like a ci_metric_id mismatch. The query only returns one of the probes installed for the servers in question.

I'm checking the KB but in step 4.c there is this command "UPDATE S_QOS_DATA SET ci_metric_id = NULL WHERE probe = '<probe name>';". This command will affect all robots with the probe installed? Is that really what we want?

Regards

Joakim

[Rajesh Banuka]

Hi Jaokim,

I would suggest to run only on problematic robots. Please apply additional filter including robot condition with problematic list of robots.

SELECT * FROM S_QOS_DATA WHERE  probe = '<probe name>' and  robot IN ( '{robot1}', '{robot2}' )

Rgds,

Rajesh B