Discovery capability for a hybrid VMWare Cloud on AWS (SDDC)?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-01-2022 07:48 AM
We have recently started leveraging VMware Cloud on AWS for our Software Defined Data Center environment. We normally leverage Discovery to discovery the VMWare vCenter details and it works great. However we are not able to complete the discovery process on the VMware VMC environment.
Any assistance would be greatly appreciated.
https://docs.vmware.com/en/VMware-Cloud-on-AWS/index.html
Regards,
Phil
- Labels:
-
Discovery
-
Multiple Versions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-04-2022 05:50 AM
Hi Phil, I have the same need as you.
No doc found, only Idea on community that I subscribe.
https://community.servicenow.com/community?id=view_idea&sysparm_idea_id=43e8cf851bc545d0ccc253da234bcbcb&sysparm_idea_table=x_snc_com_ideation_idea&sysparm_module_id=enhancement_requests
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-06-2022 09:20 AM
We were able to resolve the issue and we now have the VMWare Cloud (VMC) service being actively discovered. The effort took surprisingly less effort but did require some pre-work to understand what the discovery process currently does for the default VMWare discovery.
Below are the key notes I used to implement this solution:
- Current Process:
- VMware on premises and VMware Cloud (VMC) leverage the same vCenter API.
- Shazzam looks for open ports, specifically for VMware on-premises, 443 (https) and 5480 (vmapp_https)
- Discovery uses port 5480 to look confirm VMware services are running
- Then leverages port 443/https to launch and run the vCenter API for data
- Runs VmWarevCenterDatacentersProbe for details
- The issue is that the VMware Cloud environment blocks port 5480. Therefore a work around is required.
- Update IP Services
- Create secondary IP Service for vmapp_https on port 443
- Set Shazzam to look for vmapp on port 443 also,
- Update the Discovery Definition -> Port Probe for vmapp to include the previously created IP service in the “Triggered By Services” section.
- Create a new VMware account using the format account@domain.com
- Documentation: https://docs.servicenow.com/bundle/paris-it-operations-management/page/product/discovery/task/t_Clas...
Note: I did not have to modify the Functionality Definition as I used the existing vmapp port
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-01-2022 12:30 AM
Hi Phil,
Good day. We got this requirement to implement the VMware Cloud discovery(AWS). Since you have already successfully completed this deployment, Can you please share step by step configuration steps to follow.
Looking forward towards your kind response. Thanks in advance.
Regards,
Anitha.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-15-2024 08:47 AM
Hi @phil50 ,
Thanks for these steps. I have followed your instructions but the probe results doesn't return anything. I do see a warning about nmap not being installed on the mid server. Is nmap required to be installed on the mid server for this discovery?