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

[Asi Garty]

Cloud discovery uses REST calls to collect you LB data and populates CMDB with the discovered CI.
Then, Based on the discovered CI Service Mapping tries to build service map using any of the  followings:

1. Launch a top-down discovery patterns, where the pattern's main CI type matches the above discovered CIs.

2. Use agent-less protocols to collect traffic form the discovered CI.

In your case none of the 2 options are applicable, that could be related to access, credentials and/or discovery pattern content to match 1.  

Hope this helps, please feel free to share your findings/additional questions.

[Prabu Velayutha]

@Asi Garty @Rahul Priyadars is cloud discovery mandatory to discover F5 load balancer hosted on Azure Cloud for Service Mapping?

[Rahul Priyadars]

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).--> This host may be a windows or Linux host. Seems that From mid server given IP is not reachable and appropriate PORTS are not opened. 

Regards

RP

[pratiksha5]

Try and check the communication with the mid server.  See if the ports are open and credentials are saved. Then try service mapping it should work.