Installing the vSphere Plugin with the Everpure VMware Appliance

Overview

Review the release notes for the vSphere Plugin and the Broadcom compatibility guide for version requirements and other details.

The Everpure Plugin for the vSphere Client provides the ability for VMware users to have insight into and control of their Everpure FlashArray. The Everpure plugin extends the vSphere Client interface to include environmental statistics and objects that underpin the VMware objects in use and to provision new resources as needed.

Deployment Type

Requirements

• Online and Offline Everpure Appliance OVA Requirements
  • 4 vCPUs and 8GB Memory
  • 3.6GB datastore space thin provisioned / 40GB datastore space thick provisioned
  • Supported to be deployed on vCenter 6.7 U3 (VMware does not certify remote plugins on vCenter version 6.7, but remote plugins are supported on 6.7 U3+)
  • Certified and supported on vCenter 7.0+
  • Single static IP address on management network (or DHCP scope) required
  • Access to the Everpure FlashArray's management interface that will be used with the Remote Plugin via port 443
  • Access to the vCenter Server where the Remote Plugin extensions will be registered via port 8443 and 443
    • 443 outbound from the OVA and inbound for the vCenter
    • 8443 outbound from the vCenter and inbound for the OVA
  • The remote vSphere plugin runs on Everpure's OVA as a Docker container. Docker has its own bridge network configuration, with the default being a 172.17.0.1/16 subnet and 172.17.0.1 is the gateway. If your internal network configuration overlaps with this default, you must change the Docker bridge network via the fields in the OVA deployment wizard (step 11 in the Online Deployment Procedure) to avoid IP address conflicts

    • When providing the the subnet in the deployment wizard ensure that the IP is in the format "x.x.x.1" and not "x.x.x.0". The deployment wizard uses the docker subnet field to set both the docker networking subnet but also the gateway as well

  • Networking requirements diagram can be found in the Release Notes: Everpure VMware Appliance
• Everpure vSphere Plugin Requirements
  • IP address or FQDN of vCenter
    Note:

    A remote plugin OVA instance may only be registered against a single vCenter instance or a set of vCenters that are in enhanced linked-mode. With linked-mode, the plugin must be registered against every vCenter instance that is linked. Non-linked vCenter instances each require their own Everpure VMware appliance. Multiple Everpure VMware appliance VMs (OVA) can be deployed to a single vCenter instance; only a single Everpure vSphere plugin deployment can be registered to a vCenter.

    Note:

    A unique folder will be created in vCenter to store individual FlashArrays. It is important that these folder names are not changed or modified. More information on vCenter Folders used with the vSphere Remote plugin can be found here: vSphere Plugin: vCenter Folder Usage.

• Online Everpure Appliance OVA Requirements
  • Access to deb.cloud-support.purestorage.com via port 443 for appliance installations, application upgrades, queries and tasks with puresw
• Offline Everpure Appliance OVA Requirements

  • Ability to download, mount and maintain the supplemental iso with the Everpure VMware appliance VM

Download Location

The Pure VMware Appliance is an OVA that can be downloaded from here. You will need to download the OVA for both online and offline deployments.

Note: If you get an error deploying the OVA, disable PROXY in the vcenter settings.

Note: If the OVA is downloaded to a Windows machine, examine its Properties by right-clicking on it to check if it is marked as "Blocked". If it is, please check the "unblock" box under Security.