ViPR 2.1 - Install EMC ViPR Controller

Table of Contents

Install EMC ViPR Controller

This article describes how to deploy the EMC ViPR Controller virtual appliance and perform the initial setup steps.

Back to Top

Prerequisites and procedure

This section describes the prerequisites and the step-by-step procedure for installing the ViPR controller virtual appliance.

Before you begin

Procedure

  1. Download a ViPR OVA file from the ViPR product page to a temporary directory.
  2. Start the vSphere Client and log in to the vCenter Server on which you will be deploying the virtual appliance.
  3. From the File menu, select Deploy OVF Template.
  4. Browse to and select the ViPR OVA file located in the temporary directory you created earlier.
  5. On the OVF Template Details page, review the details about the appliance.
  6. Accept the End User License Agreement.
  7. Specify a name for the appliance.
  8. Select the host or cluster on which to run the virtual appliance.
  9. If resource pools are configured (not required for ViPR), select one.
  10. If more than one datastore is attached to the ESX Server, select the datastore for your appliance.
  11. Select a disk format:
    • Thick Provision Lazy Zeroed
    • Thick Provision Eager Zeroed (recommended for production deployment)
    • Thin Provision
  12. On the Network Mapping page, map the source network to a destination network as appropriate.
    (If you are running vSphere Web Client, you can disregard the "IP protocol: IPv4" indicator; it is part of the standard screen text. In fact this deployment is used for both IPv4 and IPv6.)
  13. Enter values for the properties.
    Note that when entering IP addresses, you must enter values for the IPv4 properties, or IPv6 properties, or both (if dual stack), according to the mode you need to support.
    Server n IPv4 address
    Key name: network_n_ipaddr
    One IPv4 address for public network. Each Controller VM requires either a unique, static IPv4 address in the subnet defined by the netmask, or a unique static IPv6 address, or both.
    Note than an address conflict across different ViPR installations can result in ViPR database corruption that would need to be restored from a previous good backup.
    Public virtual IPv4 address
    Key name: network_vip
    IPv4 address used for UI and REST client access. See also how to avoid conflicts in network virtual IP addresses
    Network netmask
    Key name: network_netmask
    IPv4 netmask for the public network interface.
    IPv4 default gateway
    Key name: network_gateway
    IPv4 address for the public network gateway.
    Server n IPv6 address
    Key name: network_n_ipaddr6
    One IPv6 address for public network. Each Controller VM requires either a unique, static IPv6 address in the subnet defined by the netmask, or a unique static IPv4 address, or both.
    Note than an address conflict across different ViPR installations can result in ViPR database corruption that would need to be restored from a previous good backup.
    Public virtual IPv6 address
    Key name: network_vip6
    IPv6 address used for UI and REST client access. See also how to avoid conflicts in network virtual IP addresses
    IPv6 prefix length
    Key name: network_prefix_length
    IPv6 prefix length. Default is 64.
    IPv6 default gateway
    Key name: network_gateway6
    IPv6 address for the public network gateway.
  14. Power on the VM.

    If you made a mistake specifying IP addresses, netmask, or gateway, the VM may fail to boot up and you will see a message in the console. You can power off the vApp at this point, fix the IP values, and power on vApp again. (Don't rename ViPR VMs; renaming them is not supported.)

  15. Wait 7 minutes after powering on the VM before you follow the next steps. This will give the ViPR services time to start up.
  16. Open https://ViPR_virtual_ip with a supported browser and log in as root.
    Initial password is ChangeMe.
    The ViPR_virtual_IP is the ViPR public virtual IP address, also known as the network.vip (the IPv4 address) or the network.vip6 (IPv6). Either value, or the corresponding FQDN, can be used for the URL.
  17. Browse to and select the license file that was downloaded from the EMC license management web site, then Upload License.
  18. Enter new passwords for the root and system accounts.
    The ViPR root account has all privileges that are needed for initial configuration; it is also the same as the root user on the Controller VMs. The system accounts (sysmonitor, svcuser, and proxyuser) are used internally by ViPR.
  19. For DNS servers, enter two or three IPv4 or IPv6 addresses (not FQDNs), separated by commas.
  20. For NTP servers, enter two or three IPv4 or IPv6 addresses (not FQDNs), separated by commas.
  21. For Extra Node IP addresses, enter IP addresses or subnets (e.g. 10.1.2.0/24) for data service or commodity nodes, separated by commas.
  22. Select a transport option for ConnectEMC (FTPS (default), SMTP, or none) and enter an email address (user@domain) for the ConnectEMC Service notifications.
    If you select the SMTP transport option, you must specify an SMTP server under SMTP settings in the next step. "None" disables ConnectEMC on the ViPR virtual appliance.
    In an IPv6-only environment, use SMTP for the transport protocol. (The ConnectEMC FTPS server is IPv4-only.)
  23. Specify an SMTP server and port for notification emails (such as ConnectEMC alerts, ViPR approval emails), the encryption type (TLS/SSL or not), a From address, and authentication type (login, plain, CRAM-MD5, or none).
    Optionally test the settings and supply a valid addressee. The test email will be from the From Address you specified and will have a subject of "Mail Settings Test".
    If TLS/SSL encryption used, the SMTP server must have a valid CA certificate.
  24. Finish.
    At this point ViPR services restart (this can take several minutes).

After you finish

After installation, the ViPR UI is open to the dashboard, in Admin mode. Refer to Step by step:Set up an EMC ViPR virtual data center to configure ViPR.

Back to Top