ViPR 2.2 - Install ViPR Controller on VMware without a vApp

Table of Contents

Install ViPR Controller on VMware without a vApp

You can use the installer script to deploy ViPR Controller on VMware without a vApp.

This method deploys ViPR Controller as 3 or 5 separate VMs, not as a single multi-VM vApp. Use this method to deploy on VMware vSphere Enterprise Edition with DRS disabled or VMware vSphere Standard/Essentials Edition.

Back to Top

Prerequisites and procedure

This section describes the prerequisites and the step-by-step procedure to use the installer script to install ViPR Controller nodes on VMware without a vApp.

Before you begin


  1. Log in to a Linux or Windows computer that has IP access to the vCenter Server or to a specific ESXi server.
  2. Download vipr-<version> from the ViPR download page on
  3. Unzip the ZIP file.
  4. Open a bash command window on Linux, or a PowerShell window on Windows, and change to the directory where you unzipped the installer.
  5. Run the vipr-version-deployment installer script to deploy ViPR Controller.
    See the table for complete syntax. The following are examples only:
    bash shell:
    ./ --mode install --vip 
    --ipaddrs "" --gateway 
    --netmask --vmprefix "Test221" --acceptalleulas --dm thick 
    --ds "A-ViPR" --vmfolder "ViPR-A" --poweron --net "VM Network"  
    .\vipr- -mode install -vip 
    -ipaddrs '' -gateway  
    -netmask -vmprefix 'Test221' -acceptalleulas -dm thick 
    –ds ‘A-ViPR’  -vmfolder 'ViPR-A' -poweron -net 'VM Network' 
    -targeturi "vi://svtgdomain%5cuser1:user1@vcenterserver.svtg.lab/SVTG/host/SVTG-1/Resources/SVTG"
    If you omit a required option, the installer will enter interactive mode. When you enter a value or values in interactive mode, do not use quotes.
    Note the following differences between PowerShell and bash versions of the installer:
    • Option names for the PowerShell version of the installer are preceded by one hyphen (-) but the bash shell installer requires two hyphens (--)
    • The argument delimiter for PowerShell is the double quotation (") but for bash it is single quotation (').
    • The option name --targeturi is for PowerShell only. On Linux, specify the targeturi value without an option name.
    Option Description
    -mode install Required option. install is the only valid argument.
    -vip Public virtual IPv4 address.
    -vip6 Public virtual IPv6 address.
    -ipaddrs IPv4 address list of each node (3 or 5 addresses separated by whitespace).
    -ipaddrs6 IPv6 address list of each node (3 or 5 addresses separated by whitespace).
    -ipv6prefix IPv6 address prefix length.
    -gateway IPv4 default gateway.
    -gateway6 IPv6 default gateway.
    -netmask Network netmask.

    Optional. Use this option when deploying in multiple ESXi hosts and/or multiple datastores. Indicates the specific ViPR node being deployed by the script.

    For example, when deploying a ViPR Controller 2+1 cluster on multiple ESXi and datastores, you run the installer script 3 times, using different values each time for the options -nodeid, -ds, and -targeturi.

    The order of IP addresses for the -ipaddrs option must be the same each time.

    node 1:

    .\vipr- -mode install -vip -ipaddrs
    "" -gateway -netmask -vmprefix
    "Test123-"  -acceptalleulas -dm thick -net mynetworkname -vmfolder "TestConfig/Test1" -poweron
    -ds "DATA STORE 1" -targeturi "vi://username:password@ESXi_HOST1_url" -nodeid 1

    node 2:

    .\vipr- -mode install-vip -ipaddrs
    "" -gateway -netmask -vmprefix
    "Test123-" -acceptalleulas -dm thick -net mynetworkname -vmfolder "TestConfig/Test1" -poweron
    -ds "DATA STORE 2"  -targeturi "vi://username:password@ESXi_HOST2_url" -nodeid 2

    node 3:

    .\vipr- -mode install -vip -ipaddrs
    "" -gateway -netmask -vmprefix
    "Test123-"  -acceptalleulas -dm thick -net mynetworkname -vmfolder "TestConfig/Test1" -poweron
    -ds "DATA STORE 3" -targeturi "vi://username:password@ESXi_HOST3_url" -nodeid 3
    -vmprefix Prefix of virtual machine name.
    -ds Datastore name.
    -acceptalleulas Accept all end-user license agreements. Optional.
    -dm {thin | thick} Disk format. Use thick for deployment in production environment. Default is thick. Optional.
    -net targetname Set a network assignment.
    -vmfolder folder Target VM folder in VI inventory. Optional.
    -poweron Power on the VM after deployment. Optional.
    -targeturi target-uri Target locator of vSphere. Example: vi://username:password@esxi_host_url

    Typical structure of esxi_host_uri is datacenter-name/host/host-name/Resources/resource-pool. Refer to the VMware OVF Tool User Guide.

    The option name --targeturi is for PowerShell only. On Linux, specify the value without the option name.

    If username requires a backslash (for example, domain\username) use %5c instead of \ (that is, use domain%5cusername)

    -interactive Prompts for user input, one parameter at a time. Do not use delimiters when in interactive mode, that is, no single quotes, no double quotes.
  6. When the installer script indicates successful deployment and the VMs are powered on, open the ViPR UI with a supported browser and log in as root.
    The initial password is ChangeMe.
    The ViPR_virtual_IP is the ViPR public virtual IP address, which is the vip or vip6 value. You can also use the corresponding FQDN for the URL.
  7. Browse to and select the license file that was downloaded from the EMC license management web site, then Upload License.
  8. Enter new passwords for the root and system accounts.
    The passwords must meet these requirements:
    • at least 8 characters
    • at least 1 lowercase
    • at least 1 uppercase
    • at least 1 numeric
    • at least 1 special character
    • no more than 3 consecutive repeating
    • at least change 2 characters (settable)
    • not in last 3 change iterations (settable)
    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.
  9. For DNS servers, enter two or three IPv4 or IPv6 addresses (not FQDNs), separated by commas.
  10. For NTP servers, enter two or three IPv4 or IPv6 addresses (not FQDNs), separated by commas.
  11. 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.)
  12. (Optional) 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.

After you finish

After installation, the ViPR UI is open to the dashboard. At this point, set up an external backup server as described in EMC ViPR Native Backup and Restore Service, then refer to Step by Step: Set Up a Virtual Data Center to configure ViPR Controller.

Back to Top