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]

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?

[robertgeen]

I've been down this road so many times with similar issues to this. Outside of what Berny has recommended make sure that the ip_address field on the load balancer is set to the mgmt interface IP address. If it isn't it will fail to discover (really there should be a business rule out of the box that auto sets this for Load Balancers). This is probably why it's failing to pick up the right one and why using the management IP might be failing.

Let me know if this helps.

[DuaneNMore]

I have the mgmtIP associated with the load balancer. What is interesting is that this load balancer is in 5 other Business Services and they work just fine; well, at least this part of them works well 😄

I also opened an HI Ticket on this 2 days ago; however other than getting the "Hi I am your support engineer" email I have not gotten on feedback on it.

[robertgeen]

Okay so if they are in other maps and there is no problem there then it's not the issue I mentioned. Have you checked the cmdb_ci_lb_service table to see if the VIP entry is in here? I would start there and if it isn't then that's why it's not finding it and is trying to discover the VIP as if it was a server.

[DuaneNMore · Accepted solution]

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.

[bernyalvarado]

Hi Duane, do you have any further questions? can you please mark one of the responses in this thread as correct so that we can close it?

Thanks,

Berny