Population of VMware storage topology (mapping between Drive C: -> VMware Datastore)

Population of VMware storage topology (mapping between Drive C: -> VMware Datastore)

Dear all,

We would like to see population of VMware storage topology that will include population of mapping between Drive C: down to VMware datastore. 

The change should most probably touch both VMware Topology by VIM as well as Resources by Shell/WMI.



Tags (3)
ISSC Super Contributor.
Super Contributor.

Hello Dmitry,

I don't think it's possible to do this directly through these jobs, as the Vmware Topology is not aware of logical things directly in OS like filesystems, and the shell/wmi jobs cannot see VMware datastores since they run on the OS (maybe through vmware-tools ? But i'm not sure).

An "easier" way could be to use enrichments rules to do the link, but you may also need to use the "logical volume" CI to match corresponding hard disks (these are linked to datastores CI).
The problem is that Filesystems CIs are only linked to the node so they have to be matched with something else.

Best regards,
Yann Pingot

Micro Focus Expert
Micro Focus Expert
Status changed to: Waiting for Votes

Thank you for sharing your idea! It’s open for comments and kudos, and we’re looking forward to input from the community. Once there is enough community traction, it will be further reviewed by the product team

ViauJoc Respected Contributor.
Respected Contributor.


@ISSC is right, there are no discovery modules out-of-the-box that links the storage elements discovered in the OS (Disk Device, Logical Volume, Filesystem) and those discovered by VIM.

We were able to do this by creating a new discovery module called "OS Storage by Shell". What this discovery does is creating a Dependency relationship from the Disk Device (ex: \\.\PHYSICALDRIVE0) and the Logical Volume from VMware discovery (ex: "Hard Disk 1"). We have noticed that each vmdk file in a VMware VM will create a matching Disk Device in Windows, so we just created a relationship using the sequential number of each disk Windows "PHYSICALDISK0" -> VMware "Hard disk 1", and so on. Then, the discovery creates a relationship between the Windows logical volumes and the Windows disk device. So, in short, the missing links are mostly on the Disk Device in the Windows CIs.

In order to achieve an end-to-end discovery from the Filesystem in a virtual machine down to the SAN Storage Unit, we had to use 4 different discovery modules:

  1. Host Resources and Applications by Shell
  2. OS Storage by Shell (our new discovery module)
  3. VMware topology by VIM
  4. Storage Devices Topology by CIM (which we customized to add the relationship between the Disk device on VMware host and the LUN on SAN)

Our module has been created to work both on Windows and Linux. It works by running shell commands in OS (wmic, Powershell, lsblk, fdisk, ...).

We had to create the module "OS Storage by Shell" and customize "Devices topology by CIM" because there are missing relationships in the out-of-the-box discoveries, such as the one you are referring to, especially for linking CIs discovered by one module to another discovered by another module.

OS Storage2.png

It took us more than a year to patch all the missing links in the discovery,  we worked step by step. We would be happy to share our work with MF in order to make the UCMDB/UD product better.

@stx9 is our expert developer who created the discovery scripts. He is also the author of the discovery script for Pure Storage SAN which was announced as a new feature in content pack 30.


ViauJoc Respected Contributor.
Respected Contributor.

We were able to add the relationship you are referring to by developing a new discovery module called "OS Storage by Shell", which works both on Windows and Linux. The module works with UD by sending commands such as wmic, PowerShell, lsblk, fdisk and then parsing the output. The two key missing links are:

  • From the Logical Volume (ex: "\\?\Volume{...}") to Disk Device (ex: \\.\PHYSICALDRIVE0) in the OS
  • From the Disk Device in the OS (ex: \\.\PHYSICALDRIVE0) to the Logical Volume in VMware (ex: Hard disk 1)

The diagram below shows and end-to-end view from the Filesystem of a Windows virtual machine to the SAN volume, all done with auto-discovery. In order to achieve this, we implemented four (4) discovery modules.

We would be happy to share our discovery module and help improve UD and uCMDB. @stx9 is our expert developer who wrote the "OS Storage by Shell" discovery and who also tweaked other discovery modules in order to get this result.

OS Storage2.png


bnadon Super Contributor.
Super Contributor.

Jocelyn, great explanation of what that discovery module does.

@Bill_Dyck - this is another one of the module we developed for storage discovery.

Micro Focus Expert
Micro Focus Expert

First of all, I am in awe of what you've done - great job!  I'll be reaching out to you all offline to see what can be done.

Fisher_01 Contributor.

This is a lot of great work our company would be very interested in using this capability for our VMWare discovery topology.

Acclaimed Contributor.. Dima Gomel Acclaimed Contributor..
Acclaimed Contributor..

Thanks a lot for all your great work!

The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.