The Host Side Linking pattern for ESX(i) is designed to establish relationships between:
- ESX(i) server and any external (Storage Volumes on the remote SAN system) or local storage sources (hard drives).
- Local file systems hosted on a ESX(i) host (datastore) and the device(s) that provides storage capacity to the file systems.
- Virtual host and physical device(s) providing storage capacity to it (storage volumes, physical disk drives).
- For the virtual Disk Drives on the hosted virtual hosts, pattern creates links to the actual physical device(s) providing storage capacity (storage volumes, physical disk drives)..
Pattern also creates disk drive nodes for the local disk drives.
The first illustration below shows a discovered ESX(i) host with the external storage volumes and internal virtual disk drives:
The second illustration below shows virtual disk drives on a virtual host running Windows and its link to the physical storage device (Storage Volume):
How it works
The Host Side Linking pattern for ESX(i) pattern triggers upon a host creation or confirmation, where that the OS type attribute matches regex “VMware ESXi?” (i.e. VMware ESX & ESXi hosts). The pattern then identifies the different disk drives and/or connected storage volumes and creates corresponding disk drive nodes in the BMC Discovery environment.
The Host Side Linking Pattern for ESX(i) creates the following relationships:
- From ESX(i) host to any appropriate storage device (internal disk drive or external storage volume);
- From the local file system (datastore) to the appropriate storage device;
- From the virtual disk drives on the virtual host(s) to the appropriate storage device.
- From the virtual host itself to the related storage device(s) (this relationship isn't shown in UI).
The execution of the pattern may stop if:
- the access method used to discover the host is different from “via vCenter” or “via vSphere”;
- the pattern was not able to find the Hostinfo node for the triggered host;
- the query to the “config.storageDevice.scsiLun” property table fails.
The current version of the Host Side Linking for ESX(i) pattern requires the following scanning order to be strictly followed to ensure collection of all available information in a single pass:
- Scanning of the storage system providing storage to the hosts.
- Scanning of the virtual host(s).
- Scanning of the ESX(i).
The Host Side Linking Pattern for ESX(i) needs to launch queries to the following property tables:
The pattern may stop if the query to config.storageDevice.scsiLun has failed.