About the Virtual Infrastructure Discovery Job

The following sections provide conceptual information for the Virtual Infrastructure Discovery Job.

Capabilities by environment

Use the Virtual Infrastructure Discovery Job to perform the following tasks:

Environment	Task
VMware Solaris IBM	Discover and register virtual machines, nonglobal zones, or LPARs that are available on the selected targets. *Imports four properties for virtual machines, non-global zones, and LPARs (Entity ID, Entity Manager, Entity Container and Entity Type). Updates all the properties of all discovered virtual machines, nonglobal zones, or LPARs (if you selected the update virtual infrastructure option).
VMware environments only	Discover unregistered virtual machines on the datastores of the selected targets. Retrieves all the virtual machines registered in the vCenter and then retrieves all the virtual machines from the datastores attached to the data centers. The difference between these two lists reveals the virtual machines which are not registered with any ESX host on that vCenter. Discover unregistered templates on the datastores of the selected targets. Auto-remediate option - registers the discovered unregistered virtual machines in the vCenter; upon successfully registering the virtual machines in the vCenter, automatically registers the virtual machines in BMC Server Automation. Import lifecycle properties - imports three lifecyle properties for virtual machines (OWNER, EXPIRY_DATE, LOCATION) \|

Environment

Task

VMware
Solaris
IBM

Discover and register virtual machines, nonglobal zones, or LPARs that are available on the selected targets.
*Imports four properties for virtual machines, non-global zones, and LPARs (Entity ID, Entity Manager, Entity Container and Entity Type).
Updates all the properties of all discovered virtual machines, nonglobal zones, or LPARs (if you selected the update virtual infrastructure option).

VMware environments only

Discover unregistered virtual machines on the datastores of the selected targets.
Retrieves all the virtual machines registered in the vCenter and then retrieves all the virtual machines from the datastores attached to the data centers. The difference between these two lists reveals the virtual machines which are not registered with any ESX host on that vCenter.
Discover unregistered templates on the datastores of the selected targets.
Auto-remediate option - registers the discovered unregistered virtual machines in the vCenter; upon successfully registering the virtual machines in the vCenter, automatically registers the virtual machines in BMC Server Automation.
Import lifecycle properties - imports three lifecyle properties for virtual machines (OWNER, EXPIRY_DATE, LOCATION) |

The Virtual Infrastructure Discovery Job also creates or populates the following extended server properties:

Property type	Property Name	Supported for
Virtualization class properties created
CPU	VIRTUAL_ENTITY_NO_OF_CPUS*	VMware Solaris zones IBM LPARs
Memory	VIRTUAL_ENTITY_MEMORY_IN_MB*	VMware Solaris zones IBM LPARs
OS	VIRTUAL_ENTITY_GUEST_OS*	VMware IBM LPARs
Resource pool	VIRTUAL_ENTITY_RESOURCE_POOL*	VMware Solaris zones
Tools installed	VMWARE_TOOLS_STATUS*	VMware
Datastore	VMWARE_DATASTORE*	VMware
Cluster	VMWARE_CLUSTER*	VMware
Server properties populated
IP Address	IP_ADDRESS	VMware Solaris zones IBM LPARs
FQ_HOST ( Fully Qualified domain name of the entity )	FQ_HOST	VMware IBM LPARs

When setting up the Virtual Infrastructure Discovery Job, ensure that you have listed all of the host servers (vCenter servers, global zones, or AIX servers) in your environment as Targets for the Job. To accurately capture the entire virtual infrastructure, you must include all of the host servers.
If you have asset management information available for your virtual infrastructure (for example, you capture specific information about the assets, such as location or owner), you can leverage that information by creating a mapping file and employing that mapping file in the Virtual Infrastructure Discovery Job. For more information, see Creating-the-server-lifecycle-properties-mapping-file.