Service Mapping fails with ""Service Mapping triggered the horizontal discovery to find the host 192.168.1.1, because this host was not in the CMDB"

DuaneNMore · ‎10-10-2018

I have a service map with an entrypoint https://entrypoint.lmco.com/overt. I attempt to run the discovery and I get the message "Service Mapping triggered the horizontal discovery to find the host 192.168.1.1, because this host was not in the CMDB. The horizontal discovery failed. See discovery status for more info."

entrypoint.lmco.com is not a Server but a VIP on an F5. I have 2 load balancer pool entries (/Common/entrypoint.lmco.com-pool-443, /Common/entrypoint.lmco.com-pool-80). We also have load balancer services on that same load balancer:

/Common/entrypoint-den-vs.lmco.com-redirect 10.1.1.1 80
/Common/entrypoint-den-vs.lmco.com 10.1.1.1 443
/Common/entrypoint-den-vs.lmco.com-redirect 10.1.1.1 80
/Common/entrypoint-den-vs.lmco.com 10.1.1.1 443

Note we have a F5 CLuster so they are listed twice.

In the past ServiceMapping has been able to glean that this is a load balanced service but in this case not.

What is going wrong here?

DuaneNMore · ‎10-11-2018

The problem appears to be some misconfiguration in the F5. In all of the working services there is a load balancer service that has the address of the virtual service associated with it. In my case, the address the entrypoint resolves to (192.168.1.1) is not in the Load Balancer Service table.

Interestingly, the F5 still consumes the connection on the address that is a virtual service.

Anyhow, if I hardcode an address for the Loadbalancer services listed in the original Question, i.e. https://10.1.1.1/overt/ then Service Mapping is able to link the address to a load balancer service and then to a Load Balancer and perform the discovery.

View solution in original post

bernyalvarado · ‎10-10-2018

Hello,

Go to your Service Map and make sure that in the node displaying this error you include the management ip of the load balancer. That can be done by right clicking the node and selecting the option to set management ip.

Thanks,

Berny

bernyalvarado · ‎10-10-2018

One additional advice, make sure you do a quick discovery (horizontal discovery) of your load balancer first.

I hope these advices are of help!

Thanks,

Berny

bernyalvarado · ‎10-10-2018

Oh... and one additional comment, please be aware that Service mapping will display the active load balancer. I understand you claim that you have 2, but normally one is passive while the other is active. Service Mapping is set OOB to show the active one which is the one serving the traffic at that moment.

Thanks,

Berny

DuaneNMore · ‎10-11-2018

We discover our Load Balancers daily; but I did a quick discovery anyhow, it doesn't change the behavior.

I don't know what this statement means in setting up the Service Map "That can be done by right clicking the node and selecting the option to set management ip."

For the 70 other services that are fronted by load balancers, it has always been sufficient to specify the http(s) endpoint for the Web Application Entry Point.