ViPR 2.2 - EMC ViPR deployment readiness checklist
Table of Contents
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 the storage you plan to add to ViPR.
When you add VNX File, Isilon, XtremIO, VNXe, or NetApp storage to ViPR, you need to provide credentials for an account with administrator privileges on the array. For VNX File, collect credentials for the VNX File onboard SMI-S Provider. VNX File has an SMI-S Provider that runs on its Control Station.
- For supported block storage, additionally identify an element manager and storage provider host.
- For VCE Vblock storage, collect the URL of the compute image; for the Vblock compute system itself, you need the system's credentials, IP address, port, and the VLAN identifier of the private network to be used by ViPR for OS installation.
- Identify an VMware or Hyper-V instance on which to deploy
Refer to the EMC ViPR Support Matrix for supported versions.
- Collect credentials to access the VMware or Hyper-V instance.
Deploying ViPR Controller credentials for an account that has privileges to deploy on the VMware or Hyper-V instance.
Verify that the VMware or Hyper-V instance has sufficient resources for ViPR Controller deployment.
Refer to the EMC ViPR Support Matrix.
Identify 4 IP addresses (for a non-production deployment) or 6 IP addresses (for a production deployment). The addresses are needed for the ViPR Controller VMs and for the 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.
Identify an authentication provider and related attributes.
ViPR validates added users against an authentication server. To use accounts 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 reliable and well synchronized 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 ViPR Controller.
- To prevent data loss, identify an FTPS server for storing ViPR Controller backups remotely. You need the URL of the FTPS server and credentials for an account with read and write privileges on the FTPS server. Plan for 6 GB per backup initially, then monitor usage and adjust as needed.
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 ViPR UI, CLI or API.
Download the ViPR Controller deployment files from support.EMC.com and deploy. For the deployment procedure refer to the Install EMC ViPR Controller article for your virtual platform.
- 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.