5.3.0 Release Notes

General

Version 5.3.0 of the Everpure vSphere HTML Client Plugin supports vSphere (vCenter and ESXi) version 6.7U3 and later and Purity version 6.1.x and later.

Users can upgrade to this version of the plugin via deploying the Everpure VMware Appliance. This version is certified by VMware.

What’s New

• Starting in vSphere 8.0, VMware no longer supports local plugins to be installed in vCenter (Everpure vSphere Plugin versions 4.5.2 and below). Please use the remote versions of Everpure's vSphere plugin (Everpure vSphere Plugin versions 5.0.0 and above). For more information please refer to this VMware KB.
• This version of the plugin uses the VMware Remote Plugin Architecture
  • More information on the VMware Remote Plugin Architecture can be found here.
  • More information on why Everpure is using this can be found Why Everpure is Deprecating the Local vSphere Plugin in Favor of the Remote vSphere Plugin.
• Release notes for Everpure's VMware Appliance (OVA) can be found at Everpure VMware Appliance Release Notes. Everpure's remote vSphere plugin can be updated independently of the appliance. The VMware appliance can be Everpure VMware Appliance Quick Reference .
• pureplugin unregister now has a --force option to be used if the previously connected vCenter is no longer accessible
• Destroy a vVol Datastore
• Edit a vVol Datastore
• Registering the VASA Providers with the Everpure vSphere Plugin
• IPv6 support added in register storage providers workflow
• Authenticating a Pure1 Connection - Plugin Managed Keys

Fixed issues

• TMAN-18814: Protocol filter was not functioning in the host connections view
• TMAN-14239: Allow import of vVol volumes from linked vCenters

Known issues

• If an array's management ports were accessible upon adding the array to the vSphere plugin and later became inaccessible, loading certain windows in the vSphere plugin might take greater than 10 minutes. To workaround this issue there are currently two options:
  1. Wait until the array list populates in the vSphere plugin screen and remove the inaccessible array
  2. If the vSphere environment has only had Pure's remote plugin installed, un-registering the plugin and registering it again should clear out the array connections that existed and the existing accessible arrays can be added back
  • Pure is currently evaluating options to improve this situation in TMAN-19146