vCenter@ipaddress instead of vCenter@hostname

Ronald Lucas
Tera Contributor

‎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:
0 Helpfuls
  • 2,166 Views
14 REPLIES 14

VivekSattanatha
Mega Sage
Mega Sage

‎01-08-2018 11:33 PM

Hi Ron,



The reason is OOB ServiceNow does not discover the vCenter appliance. I haven't seen anyone wrote custom probe to discover the appliance. Also, I don't think the current VMware probe can bring the vCenter hostname.



So it's your skill to write custom probe for the appliance.



Regards,


Vivek


0 Helpfuls

doug_schulze
ServiceNow Employee
ServiceNow Employee
In response to VivekSattanatha

‎01-10-2018 10:13 AM

Vivek, Actually we do discover appliances, we would find them through the vmapp port probe!


0 Helpfuls

VivekSattanatha
Mega Sage
Mega Sage
In response to doug_schulze

‎01-10-2018 07:42 PM

Hi Doug,



Through Vmapp port I thought we can discover only the vCenter. I have discovered vCenter from the appliances. Is it possible to discover the host appliance also?



Usually, we will get SSH error right? Sometime before I got appliance credential from the team and tried to discover but still it failed. Then I logged into the appliance with credential and shell itself looked different. The usual Linux commands didn't work in there.



Regards,


Vivek


0 Helpfuls

doug_schulze
ServiceNow Employee
ServiceNow Employee
In response to VivekSattanatha

‎01-10-2018 08:08 PM

Vivek, you are absolutely correct, we would just be discovering the vCenter setup. Nothing about the actual hardware that it's running on.   But as you mention these devices do not have common shells that we can talk to.   Appliances , puropsely built so only some folks have access...what ya gonna do ...