DX Infrastructure Management

Expand all | Collapse all

How can I determine discovery correlation that cause multiple devices to correlate as one device in USM group is correct

Jump to Best Answer
  • 1.  How can I determine discovery correlation that cause multiple devices to correlate as one device in USM group is correct

    Posted 09-28-2018 09:15 PM

    After running discovery agent to gather information in a network segment on a group of devices I notice that two devices correlated and display a one device in the USM group and all two net_connect metrics were map to into one single host.

    How can I determine discovery correlation that cause multiple devices to correlate as one device in USM group is correct ?

     

    I am running UIM 8.5 , discovery_server and discovery agent version 8.5.



  • 2.  Re: How can I determine discovery correlation that cause multiple devices to correlate as one device in USM group is correct
    Best Answer

    Posted 10-01-2018 02:05 PM

    I would suggest setting the below discovery server loglevel and size.

    Discovery cfg/logs and other sql outputs are missing covering period of robot rediscovery

    DISCOVERY_SERVER LOG:
    1. Set the discovery_server at log level 5, increase log size to 10MB, and increase number of file to retain.

    a. To increase the log size edit the X..\Nimsoft\probes\service\discovery_server\log4j.xml
    change the follow values as shown below:

    <param name="MaxFileSize" value="10242880"/>
    <param name="MaxBackupIndex" value="15"/>

    b. To increase the log level use raw configure for the Discovery_server, set setup loglevel to 5

    2. Deactivate the Discovery_server and delete all discovery_server logs

    3. Activate the Discovery_server

     

    Go into USM and delete the system in question. Make sure NOT to check the boxes to remove data or exlude from discovery.

     

    Restart the robots and then monitor the discovery_Server logs you will see where they are first added back and then correlated and the reason for it in the discovery_server logs.

     

    details on this

    Device Correlation Configuration - CA Unified Infrastructure Management Probes - CA Technologies Documentation 

     

    NOTE:

    make sure to set loglevel back to 0 once done.