Add VMAX and VNX for Block Storage to ViPR using the REST API
Table of Contents
This article also describes how the storage is discovered, and registered after it is added to ViPR, and the important REST API calls to manage SMI-S Providers and perform optional configuration steps on the storage after it has been added, and discovered in ViPR.
This article applies to EMC ViPR 2.0.
This article is part of a series
- Authenticate with the ViPR REST API
- Add physical assets to ViPR:
- Create ViPR virtual assets:
- Verify that your SMI-S Provider setup is valid.
- The host server running Solutions Enabler (SYMAPI Server) and SMI-S Provider (ECOM) differs from the server where the VMAX service processors or VNX storage processors are running.
- The VMAX/VNX array is discovered in the SMI-S Provider.
- 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.
- Ensure that 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."
- VNX connection is over the IP network with connections to both VNX storage processors.
- For VNX, the SMI-S Provider host needs IP connectivity.
- For VMAX, the SMI-S Provider host is able to see the gatekeepers (six minimum).
Create a sufficient amount of storage pools for storage provisioning with ViPR on both the VMAX and VNX for block storage systems.
VMAX storage systems
- Create storage pools (for example, SSD, SAS, NL-SAS).
- Define FAST policies.
Storage Tier and FAST Policy names must be consistent across all VMAX systems.
- It is not required to create any LUNs, storage groups, port groups, initiator groups, or masking views.
VNX for Block storage systems
- Create Pools or RAID groups.
- If volume full copies are required, install SAN Copy enabler software on the array.
- If volume continuous-native copies are required, create clone private LUNs on the array.
Storage systems that will not be used in ViPR, can also be deregistered, or deleted after the storage provider is added to ViPR.
Before you begin
The EMC ViPR REST API Reference provides a description and complete list of parameters for the REST API methods used in this article.
- Add the SMI-S Provider by sending a
The request returns a task whose URI can be queried to determine the status of the task such as completion state, any failures, and the start time of the task request.In this example, the SMI-S Provider with the IP address of 192.168.0.0 is being registered.RequestResponse
- Repeat the query of the SMI-S registration task, using the task URL from the response body of the
POST request, until the
message attribute of the task is
Operation completed successfully.
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 network systems (fabric managers) and SAN networks to ViPR for more information.
- 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.