Discovery of vCenter fails
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-26-2018 01:40 AM
Hi,
We are doing POC of Discovery and when trying to do a vCenter discovery it only manages to create the vCenter CI:
Hovering the cursor over 'Details' under 'Issues' says "No credentials found for types SSH Password, SSH Private...".
And under the Discovery Log tab we see a more than 7.000 warnings saying "Controller is empty for FC Port....":
So similar warnings as described in this other community thread (no solution):
https://community.servicenow.com/community?id=community_question&sys_id=60aeba65db58dbc01dcaf3231f961977&view_source=searchResult
We are running Jakarta Patch 8B, but I get the same result in my developer instance running Kingston patch 4.
We have created the VMware credentials using vCenter read-only credentials ('Test credential' is successful).
Regards,
Kristian
- Labels:
-
Discovery

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-01-2018 11:18 PM
Everything seems to be in order, i would create a HI.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-07-2018 12:15 AM
I just realized that we are using something called "vmware platform services controller (PSC)" for vmware authentication.
As I understand our vmware guy this means that vCenter will respond with a different IP address than the one Discovery intially connects to.
Has anybody successfully connected with Discovery to vCenter with "vmware platform services controll (VPS)" enabled?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-07-2024 11:01 AM
Hello, Have you got past the issue I did few test case we are working now and see the same issue. Could you provide the steps taken to fix this as I'm unable to find any relevant articles.
Thanks,
Rakesh
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-07-2018 02:53 AM
Hi klautrup,
Before discovering there is two things we need to check,
1- if your vcenter is in cloud then create a service account & discover.
2. If your vcenter is in your domain then go to the below method as mentioned.
If you are discovering through below method please vcenter credentials & update discovery credentials,
for discovering Vcenter, Go to navigation- type Vcenter-New- fill out all the information which is all is necessary.
please find below screenshot.
Please Refer the document regarding the port knowledge.
Regards,
Gitika