EHC 4.1: ESXi Host Migration Process (vCenter Host Migration with ViPR Export Groups)

This procedure details the steps to execute in order to remove an ESXi host from a source ViPR Export Group and add to an existing target Export Group.

Note: this procedure applies to ViPR 3.0 and below, ViPR 3.5 introduces a more automated procedure which I intend to cover in a future post.

Host Removal – remove ESXi Host from a ViPR Export Group

Please ensure the current ViPR configuration is in a known good state before proceeding and that the ViPR database is edited where required to bring it in synch with the live environment. Contact DellEMC support to assist with any ViPR database remediations required.

Note: Ensure the version of SMI-S complies with the EHC ESSM stated version.

The following steps detail the procedure for removing a host from a vSphere ESXi cluster in vCenter and utilizing the ViPR CLI to remove the same host from the cluster Export Group. Continue reading

ViPR Controller – Ingest V(x)Block UCS Boot Volumes

The following provides guidance in a scenario where your ESXi host boots from SAN, for example this is the standard configuration for Cisco UCS blades included in a Vblock/VxBlock. These boot volumes will most likely have been created outside of ViPR Controller, thus it will be a requirement to perform an ingestion of these volumes prior to performing any host migration procedures, for example moving a UCS ESXi blade to another cluster in vCenter.

Note: by not performing the ingestion will result in the removal of the Boot volume from the ESXi host masking if you are initiating the migration process utilizing ViPR commands (more on this later). Continue reading

ViPR Controller: Exporting VMAX3 LUN fails with Error 12000

This ‘Error 12000’ maybe encountered while exporting a VMAX3 LUN from ViPR Controller as a shared datastore to a specific ESXi Cluster. This issue arises in scenarios where for example the ESXi hosts already have independent Masking Views created, but no dedicated ESXi Cluster Masking View (Tenant Pod in EHC terms).

You may ask the question why each host has its own dedicated masking view?: Think Vblock/VxBlock with UCS, where each UCS ESXi blade server boots from a SAN-attached boot volume presented from the VMAX array (Vblock/VxBlock 700 series = VMAX). Further detail can be found here on how the specific functioning Masking Views are configured on a Vblock/VxBlock:


Key point: dedicated Masking views are required for VMware ESXi boot volumes in addition to Cluster Masking Views for shared vmfs datastores. Continue reading

ViPR Controller -Configuring AD Authentication

The default built-in administrative accounts may not be granular enough to meet your business needs, if this is the case then adding an authentication provider such as Active Directory which we highlight as part of this configuration allows you to assign users or groups to specific roles.

The example configuration provided here was part of an Enterprise Hybrid Cloud solution. Continue reading

EMC ViPR Controller: Storage-Related Ports

The following list and diagram details the respective storage-related TCP ports that ViPR uses to communicate with a particular EMC Storage product. If  a firewall is present between the ViPR Controller and the associated Storage system then it may require a specific ruleset to allow the required communication between the ViPR controller and the array.

  • VMAX Block (via SMI-S) – 5989
  • VMAX File – 443
  • VNX Block (via SMI-S) – 5989
  • VNX File – 443
  • VPLEX MGMT Controller – 443
  • RecoverPoint – 7225
  • Isilon – 8080
  • ScaleIO – 22
  • XtremIO XMS – 443

ViPR - Storage Connectivity Ports


Reference:  EMC® ViPR® Controller Version 2.4 Security Configuration Guide