vCenter Discovery
vCenter Discovery
Implementing ServiceNow’s Vcenter Discovery to uncover all the VMware resources, and they found themselves at a bit of a loss on where to begin!
They scoured the ServiceNow community in search of articles, blogs, or threads related to ServiceNow’s Vcenter Discovery that could provide them with the insight needed to kick-start the Vcenter discovery process. Unfortunately, to their dismay, they came up empty-handed.
Requirements:
1) Figure out on which host the Vcenter is hosted meaning on windows or linux.IP
2) Then get the IP address of the host and credentials for the host.
3) You also need Readonly credentials for the VMware vCenter.
4) Port which should be open on this machines is 9443 and 5480
5) If this is hosted on windows then windows creds are enough to discover that vCenter.
6) Run a quick discovery on this IP to check if we are able to discover this or not.
7) If yes then create scheduled and add IP address to schedule and you are done.
If any error please trouble shoot.
By Ashutosh Munot
A. vCenter Discovery
ImagesDescription
see
How to install Mid Server on Windows/ Como instalar o MID Server em Windows?
01. Install MID Server
02. Create vCenter Instance in sercicenow
03. create a discovery schedule 04. create a discovery schedule
By Liju John
B. vCenter tables — where can i find
Discovery load information in “VMware vCenter Instance” <cmdb_ci_vcenter>
And that table extends from Application <cmdb_ci_appl> and that extends from Configuration Item <cmdb_ci>
And now By Sohail Khilji
Step 1# (Requirements)
Check if all the Given IP are reachable and ports are opened. You would need Source IPs (Usually it will be midserver IP), Destination IPs (All the IP of vCenter which needs to be discovered). Ports to be opened: 9443,5480,443 and if any other custom ports exist must be opened.
Step 2# (Validating Creds and Ports)
Acquire the Credential’s which are required for ServiceNow vCenter discovery and configure them in ServiceNow. You can navigate to ‘Credentials’ module under ‘discovery’ module and click on ‘new’ button > you’ll have interceptor asking to choose a type of credentials. Choose ‘VMware Credentials’.
Note: The credential type depends on the type of Virtual Machine (SSH / Win). Windows Credentials are not required when you have a valid VM Credentials. (This is not true in all the cases).
If you use a domain account to access vCenter, specify the domain with the user name in the credential record in one of the supported formats, such as Domain\UserName. The VMware credentials must have read-only role and License Admin privilege in vCenter.
Validating Creds: Once done, Save the record and validate the credentials by clicking on the ‘validate creds’ in related links. Use a valid IP (Destination IP) and Port (443) In the popup to validate the creds.
Validating Ports: To make sure the ports are opened you can login to mid server and do the telnet command with IP and mentioned port to make sure the connections are open for communication.
Step 3#
Once the Connection and Creds are validated you can create a discovery schedule by navigating to > Discovery > Discovery Schedules.
Click on New > and Populate the below highlighted fields info:
Name: Name the discovery schedule with a proper standard
Discover: choose ‘Config Item’
Mid Server selection Method: ‘Based on existing infra config, choose the option’ > for vCenter discovery choose Configuration item.
Mid server: Choose a mid-server for which you have requested port opening.
Location: decide the location and choose from the reference field.
Time : When to run the schedule choose a time.
Once filled with all the above info, Submit the record.
Step 4#
Open the discovery schedule which was created and you would find few related lists as below, Click on New.
Update the ‘Discovery IP range’ form as below and save the record which will show a related list.
Once saved, on the related list tab ‘Discovery Range item IPs’ > click on new > and enter the list of IPs that you have or which you need to discover. Save the record.
Step 5#
Now, navigate back to the ‘discovery schedule’ module which you created there you would find the IPs been related to the created schedule (refer image below). Now you are all set to run the discovery.
Step 6#
Now click on the related links > Discover Now. The Discovery for this schedule must run now if you have configured it all right.
how to servicenow vCenter Discovery
…Time for Results…
You can track the progress and the process of your discovery in the ‘Discovery status’ and ‘Discovery Result’ tabs. All the discovered VM’s will be updated in ‘cmdb_ci_vcenter’ table.
LinkedIn >
