5.3.10 Release Notes

General

Version 5.3.10 of the Everpure vSphere HTML Remote 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 with VMware.

Important notices regarding the vSphere Client Plugin:

• 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 here.

• Release notes for Everpure's VMware Appliance (OVA) can be found at this page. Everpure's remote vSphere plugin can be updated independently of the appliance. The VMware appliance can be downloaded here. The installation guide for the remote vSphere plugin can be found here

What's New

• TMAN-19770: AC vVols Support (with Purity//FA 6.6.11 and higher)
• TMAN-20780: Upgrade Storage Provider - Allows existing registered FlashArray VASA Providers to be have their storage providers upgraded.
• TMAN-20734: Improved error messages for the Register Storage Provider workflow.
• TMAN-20513: Virtual Machine Manager - Shows all virtual machines associated with a given array.
• TMAN-20144: NFS Capacity and Performance Charting - Available at a Virtual Machine and NFS Datastore level.
• TMAN-19906: Full Certificate Registration Support - Supports latest vSphere registration flow, and allows importing of custom certificates to the plugin

Fixed Issues

• TMAN-19146 and TMAN-20062: Mark offline arrays as unresponsive - should improve performance when one or more arrays in an environment are unreachable / offline
• TMAN-20900: Destroy vVols Datastore did not always clean up the Protocol Endpoint
• TMAN-21023: Capacity views showed error in Evergreen//One environments
• TMAN-21009: Create Datastore: vVols Storage Containers are displayed in VMFS Storage selection Page
• TMAN-20905: Undelete VM: Can not select a host since there are no hosts populated in the compute resource tree.
• TMAN-20801: Incorrectly uses outdated cache for datastore view
• TMAN-20791: vSphere Plugin should allow for creating a vVol datastore without a quota.
• TMAN-20731: Unable to load compute resources with NVMe-FC
• TMAN-20450: auto-pgroup is listed as an option when choosing pgroup for vmfs datastore creation
• TMAN-20442: NVMe-FC: Unable to find host during VMFS datastore creation
• TMAN-20391: Custom policy input get removed during policy calculation
• TMAN-20192: VM undelete fails with error name must be between 1 and 63 characters.
• TMAN-20179: Quota policy showing empty in summary
• TMAN-20173: Destroy datastore from plugin destroy(s) the NFS policy associated with it.
• TMAN-20167: vVols Replication Manager - Test Failover target selection fails as "An unknown error occurred."
• TMAN-20164: Export Policy showing SMB policy (for NFS)
• TMAN-20061: vSphere Plugin should not list a nested directory as virtual machine
• TMAN-19868: Container without any protocol assigned should be present to both iSCSI and NVMe list

Technical Improvements

• TMAN-18923: Create Datastore Refactor and workflow consolidation
• TMAN-20474: Various Security Updates
• TMAN-18929: REST 2 Conversion