While using Automated Service Modelling, the modelling stops after hitting a LB with SSL termination

[Aniruudh_Ravishanker]

We are using ASM to model in our environment. On running the ASM using the entry point URL, we notice that the ASM seems to stop at the Load Balancer level.

We learned that this issue is being caused by SSL termination being enabled on the Load Balancer for security purposes. Is there any work around to this issue?

How can we go about using the ASM for modelling?

[popadiyski]

Hey  Aniruudh,

Check the communication logs of the discovery adapters used for the LB. I suspect that it may be SSL error, because the DataFlowProbe hasn't authorized the Certification Authority issuing the LB certificates. If that's the reason you have to just add the certificate to the storage.

Petko

[Aniruudh_Ravishanker]

Hi Petko,

We are able to discover the LB via our Universal Discovery. It is only while trying to use ASM, we are not able to find anything beyond the LB.

We are noticing that the ASM is not able to form a relationship between the Service Connection Point it creates for the LB and LB itself. Only the SCP is created. We are not seeing anything else created by the ASM.

[Keith_Paschal]

Remember you must discover your load balancing environment before running ASM.  It has to have the right layout to be able to traverse those links.

[Aniruudh_Ravishanker]

Hello Keith,

We are able to discover the Load Balancer and its components without issue in our uCMDB.

While using ASM alone we seem to be having this problem.

We also notice that the IP address used to discover the LB in our UD is different from the one ASM is trying to reach. The Ip address ASM tries to reach is a Virtual IP of that LB.

[Keith_Paschal]

I think that is correct.  So long as you have previously discovered the load balancer topoology, ASM should follow the path to the endpoint it detected.  99% of the time the issue is that the load balancer topology isn't what we expect in the ASM job.  Check the tql for 'Load Banacer and Cluster Tunnel Job', which is 'loadbalancer_virtual_endpoint' and make sure you meet that criteria of the TQL.  This is the only way ASM traverses Load Balancers.