ldap_response device FQDN rather than Robot name
ldap_response is creating a separate device in CM_COMPUTER_SYSTEM when discovered. Which then means multiple entries for the same server in the UMP. 1 entry for the robot and all other probes and another entry for 1 ldap_response QoS metric. How to fix ldap_response so that is does not get discovered with FQDN, and uses robotname instead.
1) Confirmed that active correlation rule in discovery_server is "IP Address" only in your environment. 2) Change the ldap_response probe configuration as follows. We changed "IP Address" for LDAP host definition. 3) Clear niscache in robot where ldap_response is running. 4) Remove FQDN device entry from CM_COMPUTER_SYSETM table.We used discovery_server callback "remove_master_devices_by_cskeys" 5) Empty "ci_metric_id" column in S_QOS_DATA table for ldap_response metric data. Update S_QOS_DATA set ci_metric_id = NULL where probe = 'ldap_response' and robot = 'XXX' 6) Restart the data_engine probe. 7) Restart the ldap_response probe.
If the symptom remains then verify to delete FQDN (long name) entry (cs_id) via "remove_master_devices_by_cskeys" callback.
It should be most of the ldap_response QOS metrics are now under the shortname host.
Was this information helpful?