ViPR 2.2 - Configure multipathing for third-party block storage

Table of Contents

Overview

ViPR System Administrators can learn the necessary information to configure multipathing for third-party block storage.

ViPR uses the OpenStack Block Storage (Cinder) service to support third-party block storage systems that are not supported natively. Throughout this document, wherever third-party block storage is mentioned, it refers to OpenStack Block Storage (Cinder), unless otherwise noted.

ViPR supports multipathing on third-party block storage only for Fibre Channel.

Back to Top

Configuration requirements

Before configuring multipathing for third-party block storage, validate that the environment meets the following requirements.

To configure multipathing for third-party block storage, you must have at least two paths from the host to the storage system and at least two storage ports on the storage system.

OpenStackCinder requirements

ViPR requirements

Back to Top

Create a storage port using the ViPR UI

Create a third-party block storage system port.

Before you begin

Only System Administrators can create storage ports.

Ensure that you have the correct port WWN.

The following procedure describes how to create the storage port using the ViPR UI.

Procedure

  1. Select Physical Assets > Storage Systems.
  2. From the list of storage systems, select the third-party block storage system to which to add storage ports.
  3. In Edit, click Ports to see the list of ports that are available. If no ports were created, a single dummy or unusable port displays.
  4. Click Add to enter the new port information.
  5. Click Save.

Results

The newly added port displays in the list of ports.

Back to Top

Create a storage port using the ViPR CLI

Create a third-party block storage system port.

Before you begin

Only System Administrators can create storage ports.

Ensure that you have the correct port WWN.

The following procedure describes how to create the storage port using the ViPR CLI. The EMC ViPR CLI Reference provides more information.

Procedure

  1. List the storage systems.
    viprcli storagesystem list
    Note the last three digits of the serial number of the storage system to which the storage port needs to be added.
  2. Create the storage ports.
    viprcli storageport create -portname|pn portname -pid wwn_of_the_port -transporttype|tt transport_type -systemtype|st storage_type -serialnumber|sn serialnumber
  3. List the storage ports for the storage system to ensure that the new storage port created successfully.
    viprcli storageport list -sn serialnumber -t storage_type
Back to Top

Discover storage ports dynamically

The alternative to creating storage ports manually is to discover multiple storage ports dynamically by performing an export or attach volume operation to a host.

While discovering multiple storage ports dynamically is supported, create storage ports manually when possible.

Procedure

  1. Create a new single storage port or modify the existing dummy storage port by modifying its WWN to the correct and valid WWN of a storage port of the storage system.
  2. Create a virtual array and then select the Automatic type of SAN Zoning.
    Automatic allows ViPR to automatically create the required zones in the SAN fabric when a provisioning request is made in this virtual array.
  3. Add a virtual network for the virtual array in which the storage system port displays.
    The storage system displays as an associated entity in virtual array.
  4. Create the virtual pool by associating it with the created virtual array.
    1. Select FC as the protocol type.
    2. In SAN Multi Path, set the minimum and maximum paths and the paths per initiator to 1.
      All matching pools of storage system display.
    3. Save the virtual pool.
  5. Create a project in which you want to assign the new resources.
  6. Create a volume resource using the Service Catalog or CLI.
  7. Export the newly created volume to the host.
  8. Verify that the volume export is successful in Resources > Volumes > Volume.
    Because the host to which volume has been exported has multiple paths to storage system, the initiator to target mapping data from the export response should contain one initiator to multiple storage ports mapping. Any new storage ports apart from the one that was discovered in the initial discovery will get added to storage system.
Back to Top