- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-18-2019 10:02 PM
Hello All,
We are trying to discover Service Mapping .
Since our client have most of their infra on Cloud hence they are using AWS elastic Load Balancer .
Please let me know if anyone have done any such service mapping for their project.
When we trying to discovery the load balancers we are getting below error:
"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. No results returned from probe. Host is active, but unable to classify Port 443 is open, but the host is unreachable with status code 400: Bad Request
Check connectivity from the MID server to the host.
Regards,
Shambo Maitra
Solved! Go to Solution.
- Labels:
-
Service Mapping
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-01-2019 03:02 AM
Hi Dave,
Just saw your comment.
If you haven't got your answers already here it is.
Yes I was able to discover the Load Balancers and we cannot use traditional discovery to achieve this as aws api calls are used to gather information for LB, Cloud DB etc.
Hence , you need to use Cloud Discovery.
Also ask the AWS team provide full access to IAM LB otherwise it won't discover them properly specially the Application Load Balancers.
Also some more bugs there from service now in London version that you may encounter in Service Mapping.
Regards,
Shambo Maitra

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-25-2019 09:17 AM
Hi - Were you able to discover the Elastic LB via traditional discovery? I'm facing a similar issue and the client isn't using cloud discovery (only traditional horizontal disco) and AWS ELB records aren't in CMDB (preventing service mapping from working of course). I suspect cloud-based disco is required to scan *ELB.amazonaws.com LBs.
What did you find? Thanks in advance
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-01-2019 03:02 AM
Hi Dave,
Just saw your comment.
If you haven't got your answers already here it is.
Yes I was able to discover the Load Balancers and we cannot use traditional discovery to achieve this as aws api calls are used to gather information for LB, Cloud DB etc.
Hence , you need to use Cloud Discovery.
Also ask the AWS team provide full access to IAM LB otherwise it won't discover them properly specially the Application Load Balancers.
Also some more bugs there from service now in London version that you may encounter in Service Mapping.
Regards,
Shambo Maitra

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-01-2019 08:37 AM
Thank you Shambo.
I'd arrived at the same conclusion - i.e. cloud disco needed to discovery AWS-based Application LB's. And yes, I'm working w/London & Service Mapping so I'm concerned about the bugs you mentioned may occur. If you have any more detail to share on that, I'd appreciate any tips.
Either way, thanks again for following up.
Dave
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-04-2019 09:45 PM
Hi Dave,
First of all check if the Load Balancer information is getting loaded in ServiceNow by running Cloud Discovery and is it populating the Cloud IP Address for the LBs.
Although we don't use ips during discovery by when we load the url for application service, it tries to perform dns lookup to resolve the host in our case the Load Balancer,
Check cmdb_ci_lb_service form for what you are finding in the system.
After that try to run service mapping , let me know if stuck somewhere and if I know the error , I will help.
Also raise cases with servicenow as those are product bugs.
Regards,
Shambo Maitra