Service Mapping - Host Detection Failed due to incorrect IP - Unable to Resolve

[Tom104]

Hi All,

I've an issue with a Service Map that's running based on Discovery of TCP Endpoints.

I've tried to manually add a connection, but have entered the wrong IP Address for the host.

This has then thrown an error stating 

Service Mapping triggered the horizontal discovery to find the host 10.XX.XX.XXX, because this host was not in the CMDB. The horizontal discovery failed. See discovery status for more info.

I've since updated the IP Address on the entry, however the discovery keeps trying to find the invalid IP I first entered, and I can find no way to remove the manual connection as it hasn't resolved.

Does anyone know of a way to remove a manual connection that hasn't resolved, or, how to amend this so that it actually tries to find the new address?

[glennguzzo]

This usually requires the Network Adapter or CI IPs to be populated to determine whether the CI is in the CMDB.   Look at how these are discovered.

[Nilanjan1]

Hello, 

May I know where  you tried to add the connection manually? Is it the dependency map?

Regards

Nilanjan

[glennguzzo]

The question is about the usage of TCP endpoints in a Service Map using this approach, and not via the dependency map.  https://docs.servicenow.com/en-US/bundle/sandiego-it-operations-management/page/product/service-mapping/reference/connection-suggestions-list.html