Skip to main content
Pure Technical Services

vSphere Plug-in Shows Array as Non-compatible

Currently viewing public documentation. Please login to access the full scope of documentation.

Problem

Occasionally the vSphere plug-in will show the array being in a non-compatible state.  The root culprit of this is due to the fact that the security token that is generated can become invalid after a change in the configuration of the array.  One example of this would be an SSD reset, or a Purity upgrade. 

Here is an example of Pure-b3 showing as non-compatible. 

Solution

To correct this you will need to select the array and click on the edit button.  Then provide all the necessary credentials for vSphere to log into the array and request a new security token:

v_plug02.png

Click save and the vSphere web client will now be able to administer the array.  It should now show as 'true'

v_plug03.png