vCenter@ipaddress instead of vCenter@hostname
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-08-2018 11:37 AM
Why are vCenter CIs named vCenter@ipaddress when vCenter is discovered on an appliance? We would rather these CIs be named vCenter@hostname.
- Labels:
-
Discovery
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-12-2020 08:57 AM
I don't think there is, because CI data (items from shazzam) are not passed into the vcenter processing. I agree that it would be better and suggest you put that up on the idea portal so it can get our products team's radar.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-12-2020 12:51 PM
Thanks for the info and I'll add it to the idea portal!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-25-2020 05:18 PM
the vcenter vcsa appliances are linux boxes and absolutely can be discovered. We have fixed this for over 100 of them.
You need to first set the shell on the box ( there is a vmware KB for this) and then create a linux user, and add the required sudo commands. The OS is Photon ( linux derivative) and it discovers just fine. Afterward, you will see vcenter@hostname.
The downside is each time the vcsa appliance is upgraded you will to repeat the steps. It takes 2 or 3 minutes to fix it up.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-02-2020 03:24 PM
Could you share the VMware KB article? It would be good to share with our vCenter team so they can test the changes..
Thank you
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-06-2020 06:34 AM
I have been tasked with the same and have the same issue and questions.
I think I found the KB article: https://kb.vmware.com/s/article/2100508