5.3.7 Release Notes

Release Notes for VMware Solutions
Audience
Public
Content Type
Release Notes
Technology Integrations
VMware
Source Type
Documentation

Release: March 2024

General

Version 5.3.7 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 with VMware.
Note: * The remote plugin is supported with vSphere 6.7 U3 and later by Everpure, but is only certified by VMware for 7.0 and later. VMware does not certify remote plugins on releases prior to 7.0.

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.

Fixed issues

  • [TMAN-20361] - NVMe-vVols support was added with vSphere Plugin release 5.3.6. To support this feature some additional queries were added to check the status of the unique NQN used for NVMe-vVols. An issue was discovered in the instances where ESXi hosts were configured for NVMe-oF for VMFS but did not have ESXi hosts configured for NVMe-vVols. The issue would cause failures in plugin requests with an error that NVMe-vVols NQNs were not configured. This issue is fixed in this release

  • [TMAN-20301] - There is a feature in the vSphere plugin that allows users to rename volume groups for either vVols based VMs or for general volume groups. An issue was discovered that caused this feature not to work when volume groups were in Pods. This issue is fixed in this release.

Known issues

  • [TMAN-19146] - 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.