
ViPR deployment files
ViPR Controller is available as an OVA file that you can download from the ViPR product
page on support.EMC.com.
File Description
- -
vipr-<version>-
controller-2+1.ova
For Controller virtual appliance deployment. One VM can go down
without affecting availability of the virtual appliance.
vipr-<version>-
controller-3+2.ova
For Controller virtual appliance deployment. Two VMs can go
down without affecting availability of the virtual appliance.
Recommended for deployment in production environments.
vipr-<version>-dataservice.zip For Object Data Service deployment.
vipr-<version>.img For environments where upgrade via an img file is needed, such
as at restricted sites.
ViPR deployment properties for Controller VMs
A ViPR Controller VM has configurable properties that you set during deployment.
Property name in
vSphere Client
Key name Description
- - -
Server
n
IP address network_
n
_ipaddr One IPv4 address for public network. You
will supply one IPv4 address for each of
the Controller VMs you are deploying.
Each VM requires a unique, static IPv4
address in the subnet defined by the
netmask.
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
network_vip IPv4 address used for UI and REST client
access.
See also the restriction in Avoiding
conflicts in network virtual IP
addresses on page 21
Network netmask network_netmask IPv4 netmask for the public network
interface.
IPv4 default gateway network_gateway IPv4 address for the public network
gateway.
Public virtual IPv6
address
network_vip6 IPv6 address used for UI and REST client
access.
Deployment Steps
20 EMC ViPR 1.1.0 Installation and Configuration Guide
Kommentare zu diesen Handbüchern