I want to share some information with the masses to 1) see if anyone else experiences the same issues and 2) if our 7 step resolution approach works for other.
We have struggled for countless hours trying to get QOS data, typically from net_connect and VMware probes, to correlate. For example in the UMP search, you may see two instances of the same device. In other instances, you may see net_connect QOS but no VMware probe QOS and vice versus.
We have opened numerous cases and eventually come to a resolution. After working through all these cases, I have compiled a list of actions that seem to work for us:
***Note: It's unfortunate, but making host file entries has made a HUGE difference. I hear that correlation is much better in 8.51 as there is more control within discovery_server to configure what is used for correlation.
Following these 7 steps, we have successfully correlated QOS data in UMP. I hope others, who have run into these same issues, have the same results.
UIM 8.4 SP2
Discovery_server probe 8.42-DevCor-SNAPSHOT
Hey Brett, do you have any plans to upgrade in the future? As mentioned in the UIM 8.5.1 release notes, there is increased functionality in the 8.51 discovery_server build.
"Discovery_server v8.51 contains improved default device correlation logic and allows for a high degree of correlation customization."
Check out this page here to see the new Device Correlation Configuration. That's a very helpful page that goes over correlation and how the new 8.51 discovery_server handles devices.
I think, moving forward, you'll see fewer instances of these types of scenarios.
Thank you very much for sharing this in the community. It is very helpful.
BAT - niscache cleanup & robot ID reset
This is my sample script which automates similar job.
Thanks for the response Phillip, we do plan on upgrading. However, until then, this process has been working for us.