In ESM, you can map OpenStack managed components to their respective IPStoragePath by using two ways:

  1. The EMC VNX storage array is discovered on the ESM server through EMC M&R. Then, the ESM server maps the OpenStack components on to the relevant IPStoragePath.

  2. If the EMC VNX storage array is not discovered on the ESM server through EMC M&R, the user needs to add the following types as part of the “VolumeTypes” configurations:

    • pool_name – The VNX storage array pool name that is configured as part of the storage_vnx_pool_names attribute value on the cinder.conf file.

      • san_ip – The IP address or fully qualified name of the active storage processor of the VNX storage array that is configured as part of the san_ip attribute on the cinder.conf file.

      • san_secondary_ip – The IP address or fully qualified name of the secondary storage processor of the VNX storage array that is configured as part of the san_secondary_ip attribute on the cinder.conf file.

        With these configurations, the ESM server can map the relevant volume and server (virtual machine) on to the IPStoragePath.

        Note:

        When both the options are available, ESM gives priority to the information available through EMC M&R.