VSphere populate devices feature letting user generate device connections based on VShere inventory results.
There is a set of conditions when the device might be skipped from being populated from VSphere inventory. Here the list of basic criteria when the device might get ignored from being populated.
Glossary
Set of definitions required to describe the criteria.
|
ServerId |
servers dedicated UUID (guaranteed by VMWare to be unique per cluster) |
|
GuestId |
VMs dedicated UUID (guaranteed by VMWare to be unique per cluster) |
|
Guest unique ID |
the Server ID combined with the Host ID |
|
HostName |
expected DNS name of a guest |
|
IP |
expected IP address of a guest |
|
Name |
VM name |
|
ElementName |
internal name of VSphere resource assigned to a VM |
Criteria
- If Guest ID not present, population of a device will be skipped.
- If there is already and OS connection that has equal "Guest unique ID", the population of a device will be skipped, otherwise a new device will be created.
- If HostName is defined but a machine with this DNS name is already defined - the population of a device will be skipped, otherwise a new device will be created.
- If IP is defined but a machine with this IP address is already defined - the population of a device will be skipped, otherwise a new device will be created.
- For ElementName and Name, first the "ping" will be sent to given value and only in case of its success population attempt will be made.
The guest uniqueness check includes newly generated inventory guests.
Comments