ViPR 2.1 - Add EMC VMAX and EMC VNX for Block Storage to ViPR

Table of Contents

Overview

ViPR System Administrators can learn about ViPR support requirements, prerequisite information to prepare VMAX and VNX for Block storage systems for ViPR integration, and the steps to add the storage to ViPR.

This article further describes:

This article is part of a series

You can add storage to ViPR at anytime. If, however, you are setting up the virtual data center for the first time, complete the steps described in Step by Step: Setup a ViPR Virtual Data Center.

Back to Top

SMI-S and storage system configuration requirements

ViPR communicates to the VMAX and VNX for Block storage arrays through the SMI-S provider.

For supported versions, see the EMC ViPR Support Matrix on the EMC Community Network (community.emc.com).

Back to Top

SMI-S provider provider configuration requirements

You will need the following information to validate that the SMI-S provider is configured as required for ViPR, and to add the storage systems to ViPR:

  • SMI-S provider host address
  • SMI-S provider credentials (default is admin/#1Password)
  • SMI-S provider port (default is 5989)

Before adding VMAX or VNX for Block storage to ViPR, login to your SMI-S provider to ensure SMI-S meets the following configuration requirements:

  • The host server running Solutions Enabler (SYMAPI Server) and SMI-S provider (ECOM) differs from the server where the VMAX service processors or VNX for Block storage processors are running.
  • The storage system is discovered in the SMI-S provider.
  • When the storage provider is added to ViPR, all the storage systems managed by the storage provider will be added to ViPR. If you do not want all the storage systems on an SMI-S provider to be managed by ViPR, configure the SMI-S provider to only manage the storage systems that will be added to ViPR, before adding the SMI-S provider to ViPR.
    Note Image
    Storage systems that will not be used in ViPR, can also be deregistered, or deleted after the storage provider is added to ViPR For more details, see Deregister or delete the storage systems that ViPR will not manage.

  • The remote host, SMI-S provider (Solutions Enabler (SYMAPI Server) and EMC CIM Server (ECOM)) are configured to accept SSL connections.
  • The EMC storsrvd daemon is installed and running.
  • The SYMAPI Server and the ViPR server hosts are configured in the local DNS server and that their names are resolvable by each other, for proper communication between the two. If DNS is not used in the environment, be sure to use the hosts files for name resolution (/etc/hosts or c:/Windows/System32/drivers/etc/hosts).
  • The EMC CIM Server (ECOM) default user login, password expiration option is set to "Password never expires."
  • For VNX, the SMI-S provider host needs IP connectivity over the IP network with connections to both VNX storage processors.
  • For VMAX, the SMI-S provider host is able to see the gatekeepers (six minimum).

Back to Top

VMAX storage system configuration requirements

You prepare the VMAX storage system before adding it to ViPR as follows.

  • Create a sufficient amount of storage pools for storage provisioning with ViPR (for example, SSD, SAS, NL-SAS).
  • Define FAST policies.

    Storage Tier and FAST Policy names must be consistent across all VMAX storage systems.

  • It is not required to create any LUNs, storage groups, port groups, initiator groups, or masking views.
  • After a VMAX storage system has been added and discovered in ViPR, the storage system must be rediscovered if administrative changes are made on the storage system using the storage system element manager.
  • For configuration requirements when working with meta volumes see EMC ViPR support for meta volumes on VMAX and VNX arrays.

Back to Top

VNX for Block storage system configuration requirements

You prepare the VNX for Block storage system before adding it to ViPR as follows.

  • Create a sufficient amount of storage pools or RAID groups for storage provisioning with ViPR.
  • If volume full copies are required, install SAN Copy enabler software on the storage system.
  • If volume continuous-native copies are required, create clone private LUNs on the array.
  • Fibre Channel networks for VNX for Block storage systems require an SP-A and SP-B port pair in each network, otherwise virtual pools cannot be created for the VNX for Block storage system.

Back to Top

Add VMAX or VNX for Block to ViPR

Before you begin

Only System Administrators can add storage to ViPR.

The following steps describe how to add the storage system to ViPR using the ViPR UI. To use the REST API to add the storage system to ViPR see the Add VMAX and VNX for Block Storage to ViPR Using the REST API article.

Procedure

  1. Select Physical Assets > Storage Providers.
  2. Click Add.
  3. Type the storage system name.
  4. Select the SMI-S type.
  5. Type the host IP address.
  6. Enable if the storage provider will use SSL.
  7. Leave the default or type the port.
  8. Enter SMI-S user credentials. The credentials must have storage system administrator privileges.
  9. Click Save.
    • The Storage Provider page displays the SMI-S provider.
    • The Storage Systems page displays the storage systems discovered with the storage provider.
    • A green check bock in the status row indicates that ViPR has successfully discovered the storage system.

After you finish

After a VMAX storage system has been added and discovered in ViPR, the storage system must be rediscovered if administrative changes are made on the storage system using the storage system element manager.

Back to Top

Deregister or delete the storage systems that ViPR will not manage

When you add a storage provider to ViPR you add all the storage systems managed by the provider to ViPR. Once a storage system is added to ViPR it is automatically discovered and registered. Registered storage systems are available for ViPR to use and manage.

If you want ViPR to manage only some of the storage systems discovered with the storage provider, you can deregister or delete the storage system from ViPR.

Deregister or delete storage systems from ViPR

  1. In the Admin Mode, select Physical Assets > Storage Systems.
  2. Select the box in the storage system row.
  3. Click Deregister to keep the storage system in ViPR, and make it unavailable to use as a ViPR resource.

    Or, click Delete to remove the storage system from ViPR.

Back to Top

ViPR storage system configuration

You can perform optional configuration steps on the storage system resources after the storage system is discovered in ViPR. The configuration steps are not available until the resources are discovered and registered in ViPR.

Once the storage system is discovered you can configure the following resources:

Back to Top

Define the storage system resource allocation limit

By default, storage systems are configured with unlimited resources that ViPR can use. You can set resource limits, which define the amount of storage in the storage system that is available for use by ViPR.

Procedure

  1. Select Physical Assets > Storage Systems.
  2. Click the storage system name in the Storage System table.
  3. In the Edit Storage System page, disable Unlimited Resource Allocation setting.
  4. Specify the maximum number of volumes ViPR is allocated for provisioning on this storage system. The amount must be 0 or higher.
    The Resource Limit value is a count of the number of volumes allowed to be provisioned on the storage system.
  5. Click Save.
Back to Top

Deregister storage pools

By default, all discovered storage pools are available for provisioning in ViPR. To make storage pools unavailable to ViPR for provisioning, deregister them.

If a storage pool becomes unavailable on the storage system, the storage pool remains in the list of available ViPR storage pools. You must deregister the storage pool manually in ViPR to ensure ViPR does not use it as a resource when a service operation is executed.

Procedure

  1. Select Physical Assets > Storage Systems.
  2. Locate the row for the storage system in which the pools reside.
  3. In the Edit row, click Pools.
  4. Check the row for each pool that you want to make unavailable to ViPR for provisioning.
  5. Click Deregister.
Back to Top

Set the storage pool utilization limits

Storage pool utilization limits enable you to define the maximum amount of storage that ViPR can use from a storage pool, the maximum number of volumes that ViPR can provision from a storage group, and the maximum subscription percentage for thin pool provisioning.

Procedure

  1. Select Physical Assets > Storage Systems.
  2. Locate the row for the storage system where the pools reside.
  3. In the Edit row, click Pools.
  4. Click the pool name.
  5. Change the maximum utilization percentage.
    The default is 75%.
  6. For thin pool provisioning, set a maximum snapshot percentage.
    The default is 300%.
  7. Enter a numeric value for the volume limit available to ViPR to provision from this storage pool.
    By default, there is no limit on the amount of a storage pool that can be used by ViPR.
    The Resource Limit value is a count of the number of volumes allowed to be provisioned using the selected storage pool.
  8. Click Save.
Back to Top

Deregister storage ports

By default, all storage ports are available for provisioning in ViPR after ViPR discovers the storage system. To make storage ports unavailable to ViPR for provisioning, deregister them.

Procedure

  1. Select Physical Assets > Storage Systems.
  2. Locate the row for the storage system where the port resides.
  3. In the Edit row, click Ports.
  4. Check the row for each port that you want to make unavailable to ViPR for provisioning.
  5. Click Deregister.
Back to Top

Data protection configuration

ViPR supports EMC RecoverPoint and SRDF protection.

EMC RecoverPoint

ViPR supports RecoverPoint protection for VMAX, and VNX for Block storage.

RecoverPoint is added to ViPR from the ViPR UIPhysical Assets > Data Protection page.

For complete details see:

EMC SRDF

ViPR supports SRDF protection for VMAX storage.

ViPR discovers the SRDF protection with the storage system. If the storage system has been configured with SRDF, you configure the ViPR virtual arrays, and virtual pools for SRDF protection as required.

For more details see:

Back to Top

SAN Switch configuration for block storage systems

After the storage system is added to ViPR, configure the SAN switches before adding the storage systems to a virtual array.

Fibre Channel

Add the corresponding SAN Switch from the ViPRPhysical Assets > Fabric Manager page. When a SAN switch is added to ViPR, the Fibre Channel networks (Brocade Fabrics or Cisco VSANs), are automatically discovered and registered in ViPR. Additionally, through discovery of the SAN switch topology, ViPR discovers, and registers the host initiators for hosts on the network, and identifies which storage systems are associated with the SAN switch.

Refer to Add Fabric Managers and SAN Networks to EMC ViPR for more information.

iSCSI

For Storage Systems that use ViPR services with the iSCSI protocol, the iSCSI host ports must be logged into the correct target array ports before they can be used in the service.

Back to Top