ViPR 2.1 - EMC ViPR deployment readiness checklist
Table of Contents
See also ViPR on Commodity installation readiness checklist for items that are specific to ViPR Commodity.
Refer to the EMC ViPR Support Matrix for the specific models and versions supported.
Identify and confirm preconfiguration requirements for the storage systems in the data center to be used by ViPR.
Refer to the EMC ViPR Support Matrix for exact models supported.
- Identify the storage pools in the data center to be used by
You can put a subset of an array's storage under the control of ViPR.
- Identify the switches to be used by
ViPR, confirm preconfiguration requirements, and collect credentials.
Adding switches to ViPR will discover the storage topology of the VSAN or fabric.
Cisco and Brocade are supported. Refer to the EMC ViPR Support Matrix for specific models.
For Cisco, obtain credentials for an account that has admin privileges on the switch.
Brocade uses its own SMI-S Provider.
- Collect array credentials, IP address, and port for VNX file, Isilon, and NetApp.
When you add VNX file, Isilon, XtremIO, or NetApp storage to ViPR, you need to provide credentials for an account with administrator privileges on the array.
- Identify or deploy an SMI-S provider for VMAX and VNX (block).
SMI-S credentials, IP address and port are needed when VMAX storage and VNX block are used by ViPR. Refer to the EMC ViPR Support Matrix for supported SMI-S versions.
- Identify a vCenter Server and ESXi on which to deploy the
ViPR is deployed as a vApp. Refer to the EMC ViPR Support Matrix for supported vCenter Server and ESXi versions.
- Collect credentials to access the vCenter Server.
Deploying ViPR with vSphere Client requires credentials for an account that has privileges to deploy the OVA on the vCenter Server.
Verify that the ESXi has sufficient resources for ViPR vApp deployment.
Refer to "Deployment requirements" and "VMware requirements" in the EMC ViPR Support Matrix.
Note that there are lower minimum CPU and memory requirements for ViPR Controller in version 2.1.
- Collect credentials for VNX File onboard SMI-S Provider.
VNX File has an SMI-S Provider that runs on its Control Station.
Identify an IP to act as the virtual IP for Controller VMs.
In addition to the 3 or 5 Controller VMs, ViPR uses a virtual IP by which REST clients and the UI access the system. The address can be IPv4 or IPv6.
Note that in dual mode, all controllers and VIPs must have both IPv6 and IPv4 addresses.
In a configuration that uses ViPR data services, only IPv4 addresses are supported.
- Identify and configure a load balancer for ViPR Data Service VMs.
A separate load balancer (not included) is required for Data Service VMs.
Identify an authentication provider and related attributes.
ViPR validates added users against an authentication server. To use other than the built-in user accounts, you need to specify an Active Directory or LDAP server and related attributes.
Identify two or three DNS servers.
Two or three DNS server IPs need to be supplied during ViPR initial setup.
Identify two or three NTP servers.
Two or three NTP servers need to be supplied during ViPR initial setup.
For each ViPRController VM, collect: IP address, IP network mask, IP network gateway, and optionally IPv6 prefix length and IPv6 default gateway.
You need this information when deploying the Controller VM OVA.
For ViPR Data Service nodes, collect: IP address, IP network mask, IP network gateway. These addresses must be IPv4 only.
You need this information when deploying the Data Service nodes.
Obtain EMC license.
Obtain the license authorization code (LAC, usually emailed from EMC) and apply it at the EMC License management web page to obtain a .lic file. After deployment, upload the .lic file using the UI, CLI or API.
- Deploy the ViPR Controller vApp.
- Log in to the ViPR UI.
Open https://ViPR_virtual_ip in a supported browser to proceed with site-specific configuration, infrastructure, and provisioning operations.
- Deploy the
ViPR Data Service VM.
Refer to the steps in Install and Configure EMC ViPR Data Services (object storage).