Discovery: Virtual Servers vs Virtual Machine Instance

kmlutz
Kilo Contributor

Hello All,

 

We have recently rolled out Discovery to our production environment.   We are starting with our main data centers and mostly targeting infrastructure items such as servers.

 

We are comparing the results from Discovery to our homegrown CMDB.

 

One thing we have noticed relates to "virtual" servers and vCenter.

 

In our homegrown system, the team has entries listed as virtual servers but when Discovery collects the data on these entries - they are listed only as a Virtual Machine Instance and have no record in the virtual server class.

 

I have reviewed the WIKI and it seems like it may have to do with how these servers are created within vCenter...possibly because a template is used to "build" this entries.

 

Can someone provide a specific distinction between a virtual server and virtual machine instance and how Discovery makes that distinction?

 

Thanks.

16 REPLIES 16

I would check to see if they have matching uuid's thats how we pair the VMs/ESX up to the compute hosts

Hi doug,

 

can you please ellaborate on UUID thing. I am not sure what needs to be checked in this.

we match up the UUID of the instance and the server which it would be the serial number.  These two matching we 'should' create the relationship.

If I consider UUID as Serial number, I can see the Serial number in Server record but not in vmware_instance record . And thats same for those where we are getting the relatiosnhip and where we don't.

The Serial number for a Particular server is like :

vmware - 00 11 22 33 44 55 66 77-88 99 aa bb cc dd ee ff 

and Correlation id in VMware instance is 

00 11 22 33 44 55 66 77-88 99 aa bb cc dd ee ff

I believe that's the UUID in vmware instance. But where we are getting matches , it is matching the numeric part and where we are not getting relatioship there also , the numberic part is matching.

 

Please assist. Kindly excuse me if I am really missing some easy stuff here.