When the VMware NDI file is processed, it places information into the HardwareValue, HardwareProperty, and HardwareObject tables. This data is then moved from the inventory database during the reconciliation process. Once both the VMware NDI file and the guest/virtual machine’s NDI file are imported, they’re entered into the inventory database, where most of the data is stored within the HardwareProperty table. Host machines typically have a separate serial number under the VMWARE_BIOS class. The UUID value for each guest/virtual machine is normalized and used as a serial number with the prefix 'VMWare- '. One property, ElementName, is the computer name of the guest and contains a UUID.
Each guest has a separate VMWARE_VMComputerSystem class with multiple properties. The VMware NDI file also contains information about each guest. This class includes a UUID (Universal Unique Identifier). The VMware NDI file contains data about the host machine under the VMWARE_ESXComputerSystem class for ESX hosts. When the vCenter rule runs within your estate, it generates VMware NDI files for each vCenter and each ESX server. This file generates as part of the normal inventory process. You can generate this file by querying the vCenter API while running a created vCenter rule. The VMware NDI file from the host machine. To link a host to a guest machine (virtual machine) while using vCenter, there are two required parts: To obtain correct license position, especially with IBM PVU data, the virtual machines within your vCenter estate must be allocated to the correct host. This article covers how FlexNet Manager Suite links guest machines to hosts using the FlexNet Agent and the vCenter discovery and inventory rules created within the FlexNet Manager Suite user interface.
0 kommentar(er)
