Page tree

Skip to end of metadata
Go to start of metadata

The minimum supported version for Windows Host Side Linking is Windows 2008.

The Host Side Linking Pattern for Windows is designed to scan a host in order to establish relationships between:

  • Servers or virtual machine’s (hosts) and any external or local storage sources (hard drives).
  • Local file systems hosted on a server (hosts) and the device that provides storage capacity to the file systems.

First, the pattern identifies the different drives and connected storage volumes. It then creates corresponding disk drive nodes in the BMC Discovery environment.

The Host Side Linking Pattern for Windows creates or triggers the following relationships:

  • From host to storage device (local disk drives or storage volumes);
  • From file system to the appropriate storage device (local disk drive or storage volume); 
  • From virtual disks to physical backing devices (drives or storage volumes).

How it Works

The Host Side Linking Pattern for Windows is triggered when a Windows OS is detected on a host. It then performs the following actions:

  1. 1.    The pattern runs WMI queries against the following classes:
    • Win32_DiskDrive: to report on different drive parameters (disk name, serial, size, model, disk port, disk bus, etc.);
    • Win32_DiskDriveToDiskPartition: to retrieve associations between disk drives and partitions;
  1. 2.    The pattern retrieves values from the following registry keys:
    • HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\Scsi\Scsi Port %disk_port%\Scsi Bus %disk_bus%\Target Id %disk_target_id%\Logical Unit Id\ %disk_lun% \SerialNumber: The TPL uses this registry key to get disk serial numbers and disk array types from storage systems or to retrieve their naa_id information;                                                                                           
    • HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\Scsi\Scsi Port %disk_port%\Scsi Bus %disk_bus%\Target Id %disk_target_id%\Logical Unit Id\ %disk_lun% \DeviceIdentifierPage: The TPL uses this registry key to obtain the storage volume’s naa_id information;           
    • HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\Scsi\Scsi Port %disk_port%\Scsi Bus %disk_bus%\Target Id %disk_target_id%\Logical Unit Id\ %disk_lun% \Identifier: The TPL may also use this registry key, based on the value of the storage system’s identifier, to obtain its naa_id.

Note on the Windows VMs running on VMWare:

For Windows systems running on VMware hypervisors, the “UUID” attribute is added to the disk drive attributes to establish a link between virtual disks and physical backing devices (drives or storage volumes).

Occasionally, the disk UUIDs on Windows VMs running on VMware cannot be found when the registry key DeviceIdentifierPage is empty.

In that case, users can force VMware to provide a UUID for the VM's OS by setting the “Disk.EnableUUID” parameter in VM config (this operation requires a full restart of the VM).


Limitations

DAS are not currently supported, except for the local hard drives.

Minimum supported server version is Windows 2008. 

  • No labels