Azure Application load balancer discovery in Service Mapping

[Nimmi1]

I need some clarity here. In my instance currently "XYZ" azure application load balancer is getting discovered using API based discovery. Related is present in Cloud Load Balancer and Cloud IP Address Class.

But in service map i am getting error like it is not in CMDB.

 Failed to identify the CI Type of the process listening on port 443 on host xx.xx.xx.xx . Please review the discovery log for further details. Handle Error xx.xx.xx.xx .

Service Mapping triggered the horizontal discovery to find the host xx.xx.xx.xx, because this host was not in the CMDB. The horizontal discovery failed. xx.xx.xx.xx is not a reachable host (no response to target ports scanned by MID).

What should we check in this scenario.

TIA

Nimmi

[Nimmi1]

As i mentioned, node is getting discovered on Subscription based Discovery but it was failing on service mapping discovery.

We raised CASE with SNOW support and got to know that it was not working because of some issue with one of the Script Include. After fixing that it is getting identified in Map as well.

Thank you.

[Abbas Abidi1]

Azure Load Balancers are only discovered as part of Top-Down Service Mapping, not Horizontal Discovery. 

You can find the IP address and the port number of your load balancer in the cmdb_ci_lb_service table if the Cloud Load balancer is discoverable through Azure Cloud Discovery.

Then you can discover Azure Load Balancers in Service mapping by simply adding a TCP Entry point and specifying the IP Address of the Load Balancer and the Port Number.