Process detection for process listening on port fails when result does not contain target IP address - Known Error

Process detection for process listening on port fails when result does not contain target IP address Description Issue: Process detection for process listening on port fails when result does not contain target IP address.

This is working as expected; The process needs to be listening on IP Address of target host being Discovered else it's disregarded by Discovery.

Example Successful Discovery:

Discovery of 10.70.234.197 is successful as we get: tcp 0 0 10.70.234.197:1521 0.0.0.0:* LISTEN 68094/tnslsnr tcp 0 0 10.70.234.191:1521 0.0.0.0:* LISTEN 68085/tnslsnr tcp 0 0 10.70.11.211:1521 0.0.0.0:* LISTEN 68085/tnslsnr

The first line shows: tcp 0 0 10.70.234.197:1521 0.0.0.0:* LISTEN 68094/tnslsnr

10.70.234.197 == 10.70.234.197.

Example Failed Discovery:

For 10.70.234.196 we get: tcp 0 0 10.70.234.192:1521 0.0.0.0:* LISTEN 56198/tnslsnr tcp 0 0 10.70.11.212:1521 0.0.0.0:* LISTEN 56198/tnslsnr udp 0 0 127.0.0.1:15211 0.0.0.0:* 58010/asm_lreg_+ASM

And: 10.70.234.196 != 10.70.234.192 10.70.234.196 != 10.70.11.212 10.70.234.196 !=127.0.0.1

Thus Discovery of the Listening Process fails as the IP Addresses are not the Target IP Address being Discovered.

NOTE :

While the behavior is expected, PRB1409378 will address the error message that is logged during Top Down Discovery of an Application Service Map which currently isn't clear on what the actual issue is causing the Service Map Discovery to fail.

The current Error Message states: "Failed to find process on port. No process detected on host."

This issue is fixed in Rome which will add an error message more specific, stating that the issue is due to the process listening on IP Addresses other than the target hosts IP Address.

Updating the Error message will be more clear and will assist our customers with steps to correct the IP Address/Port that application is listening on.

Steps to Reproduce

1) Add the required ssh, snmp or windows credentials for Discovery 2) Create new Application service where running process is listening on a different IP Address than that of the target server hosting the application. 3) Provide the name of application the service and add endpoint url : https:// 4) click on save then view map to find the below error on the endpoint:

Result: "Failed to find process on port. No process detected on host."

Workaround This issue is fixed in Rome:

Please upgrade to the newest release once you're able to.

To Resolve the Error:

The process needs to be listening on the IP Address of the target host that is being Discovered. Please configure the process to listen the IP Address/Interface of the host in order to Discover the process.