ViPR 2.2 - Add vCenters and ESX/ESXi Clusters to ViPR

Table of Contents

Overview

This article provides ViPR System and Tenant Administrators the ViPR support requirements, and prerequisite information to prepare vCenters for ViPR integration, the steps to add the host to ViPR, the optional steps to manage the ESXi host initiators that will be used by ViPR, and the ESXi clusters.

This article is part of a series

You can add a vCenter to ViPR at anytime. If, however, you are setting up the virtual data center for the first time, complete the steps described in Step by Step: Setup a ViPR Virtual Data Center.

Back to Top

Support and configuration requirements

Your vCenter must meet the following support and configuration requirements to successfully integrate with ViPR

Support requirements

For supported versions, see the EMC ViPR Support Matrix on the EMC Community Network (community.emc.com).

vCenter role requirements

The role, which will be used by ViPR to access vCenter, must have at least the following privileges enabled:

Datastore privileges:
  • Allocate space
  • Browse datastore
  • Configure datastore
  • Remove datastore
Host privileges:
  • CIM
  • CIM interaction
  • Configuration

Back to Top

Add vCenter to ViPR

System Administrators and Tenant Administrators can add a vCenter to ViPR.

Before you begin

ViPR allows a vCenter to be added twice if the IP address is used once, and then the hostname is used to add it again.

The following steps describe how to add a vCenter to ViPR using the ViPR UI.

To use the REST API to add a vCenter to ViPR see Add vCenter and ESX/ESXI Clusters to ViPR Using the ViPR REST API.

Procedure

  1. Select Physical Assets > vCenters.
  2. Click Add.
  3. Enter a vCenter Server name.
  4. Add the host or IP address.
  5. Add the port used for communication between the ViPR virtual appliance and the vCenter Server.
  6. Enter the credentials for an account that has administrator privileges.
  7. Check the status of the Validate Connection on Save checkbox.
    If you leave this box checked, ViPR will check that it can connect to the host before saving the host details. If validation fails you will not be allowed to save the host details.
    If some of the information, such as the user credentials, are incorrect, but you still want to save the information you have entered, uncheck the box. The host will fail discovery, however, you can edit the host details later and, once corrected, it will be successfully discovered.
  8. Click Save.
Back to Top

Network configuration requirements for vCenters

After a host is added to ViPR, configure the networks if required before using the host in a service.

Fibre Channel

IP

Add the ESX/ESXi ports to an IP network.

ViPR can discover the ports of IP connected storage systems and hosts , but it cannot discover the paths between them, so it is necessary to create IP networks, and then add the host, and storage system ports, which will be provisioned together, to the same IP network.

If creating a network for a virtual array that will be used for file system exports to an ESXi cluster, add all ESXi server IP interface addresses (Management IP, vMotion IPs, and any other IP VMNIC visible in vCenter) per cluster.

iSCSI

Hosts that use ViPR services with the iSCSI protocol must have their iSCSI ports logged into the correct target array ports before they can be used in the service.

Back to Top

ESX/ESXi initiator, and port configuration

Once the vCenter has been added to ViPR, configure the ESX/ESXi host initiators, or ports as required.

Back to Top

Deregister host initiators

Deregistering a host initiator leaves the host initiator in the ViPR assets, but makes it unavailable to use in any VIPR service operations.

Before you begin

Only host initiators, currently not in use in a ViPR export, can be deregistered.

Procedure

  1. Open the Host Initiators page.
    1. Select Physical Assets > Hosts.
    2. Locate the row for the host, and click the Initiators button in the Edit column.
  2. Check the box in first column of the row with the host initiator to deregister.
  3. Click Deregister.
Back to Top

Add ESX/ESXi ports to an IP network

If adding ESX/ESXi hosts to provision over an IP network, the ports must be added to the IP network.

Before you begin

  • IP Networks are created by System Administrators. Tenant Administrators cannot configure IP networks or add host ports to the network.
  • Add all ESX/ESXi server IP interface addresses (Management IP, vMotion IPs, and any other IP VMNIC visible in vCenter) per cluster when creating a network for a virtual array that will be used for file system exports to an ESX/ESXi cluster.

Procedure

  1. Select Physical Assets Networks page.
  2. If the Network is already created, click the name from the list of networks.
    If the Network is not created, create it:
    1. Click Add IP Network.
    2. Enter the network Name.
    3. Select the storage systems to include in the network.
  3. Under the IP Ports table, click the Add to manually add the host ports, or click the Add arrow, and select Add Host Ports to select from the discovered ports.
  4. Enter or select the host ports to use in the IP network.
  5. Click Save.
Back to Top

View ESX/ESXi Clusters

ESX/ESXi clusters can be viewed Physical Assets > Clusters page.

Before you begin

ESX/ESXi clusters are automatically discovered with vCenter. Hosts cannot be added or removed from ESX/ESXi clusters from ViPR.

Procedure

  1. Select Physical Assets > Clusters.
  2. If in a multi-tenancy environment, select the Tenant.
  3. Locate the cluster that will be edited in the list of clusters.
  4. Click Edit Hosts in the right column in the same row as the cluster to view the list of ESX/ESXi hosts in the cluster.
Back to Top