If the proper AVS Run Command libraries are not available, the Everpure VMware Cloud Manager OVA is too far out of date or PowerShell modules are not updated to the latest version, that can lead to Run Command script failures and the customer will not be able to make storage-level administrative changes against their AVS and Everpure Cloud Dedicated storage instances.
This can potentially lead to outages if datastore capacity is full, lack of an ability to restore to an Everpure Cloud Dedicated snapshot, and/or the inability to provision new VMFS volumes and other errors.
To resolve several issues with the Azure AVS Run Command, follow these steps outlined below.
Confirm AVS VMFS Run Command Library is Present
If the customer's AVS instance is not showing the VMFS Run Command library in the portal, has otherwise not been assigned the appropriate version of the AVS Run Command VMFS library or the Everpure AVS and Everpure Cloud Dedicated combined module has not been properly loaded, the Run Command scripts may fail.
The first item to check is to confirm that your AVS instance has the correct VMFS Run Command library assigned to it. AVS Run Command script access can be gated by certain Azure features, which we will also cover in this section.
To check the presence of the correct AVS VMFS Run Command library, navigate to the AVS instance within the Azure portal. From the menu on the left, select Run Command. The list of available Run Command libraries will appear.
The version of the Microsoft.AVS.VMFS libraries that may be visible in the customer's AVS
instance can vary. For the AVS and Everpure Cloud Dedicated integration, we have hard-coded to only
use certain versions of the Microsoft.AVS.VMFS library in order to ensure a consistent
feature sent and end-user experience. If you need to update to the latest version, you should request Microsoft to install latest version of Microsoft.AVS.VMFS on your AVS instance.
If none, or incorrect versions of the
Microsoft.AVS.VMFS libraries are shown within the Azure portal, the next step is to confirm that the proper Azure Preview feature has been enabled. These commands can be easily checked and verified by launching a Cloud Shell from the Azure Portal. To check for feature registration, run the following two command lines from the Azure CLI to confirm that the correct features have been registered against your Azure subscription:
az feature register -
-subscription
{subscription-id} -
-namespace
Microsoft.AVS -
-name
earlyAcccess
az feature register -
-subscription
{subscription-id} -
-namespace
Microsoft.AVS -
-name
scriptingPreview
If the preview feature has been successfully registered, yet the Microsoft.AVS.VMFS libraries are not appearing in the portal, open a support ticket with Microsoft. You will need to provide your AVS ExpressRoute ID in the ticket and request that the AVS VMFS Run Command libraries are added to your AVS instance.
Review Run Command Run Execution Status for Errors
A useful tool to help determine why failures or other anomalies for Run Command execution attempts are occurring can be found from the AVS instance inside of the Azure portal. From AVS, navigate to the Run Command menu item on the left. Once the menu is open, select the Run Command Execution Status tab on the top. From there, you can review individual Run Command executions and clicking into each of them will show additional level of details around why a failure may have occurred.
You can get more in-depth information around why a failure has occurred via clicking on an execution instance and reviewing the details as shown below.
For the following example, this would need to be resolved by opening a ticket with Azure support for resolution.
Update AVS Run Command PowerShell modules to the latest version
The next item to check is to confirm that you have installed the latest version of AVS Run Command PowerShell modules. There are different steps for updating PowerShell modules in case you are using Everpure VMware Cloud Manager OVA or running PowerShell form an Azure VM or AVS VM.
Please follow this guide on how to update PowerShell modules within OVA or Azure/AVS VM.
Failed to install PowerShell modules
In scenarios where Everpure OVA cannot be used, there is an alternative way to configure integration from an Azure VM or AVS by manually installing PowerShell modules into the hosted VM (see this page for details).
In case you are hitting errors when installing or running PowerShell modules, please follow the steps outlined below to uninstall and reinstall all required modules. An example of an error when running a PowerShell module might be:
Failed to connect: Could not load file or assembly 'InternalVimService50.Wcf, Version=8.3.0.399, Culture=neutral, PublicKeyToken=null'. The system cannot find the file specified.Please note that at minimum PowerShell version 7 is required.
1) Uninstall PureStorage.CBS.AVS PowerShell module:
Uninstall-Module -Name PureStorage.CBS.AVS -AllVersions -Force2) Uninstall and reinstall VMware.PowerCLI, and Az PowerShell modules:
Uninstall-Module -Name Az -AllVersions -Force
Uninstall-Module -Name VMware.PowerCLI -AllVersions -ForceInstall-Module -Name Az -Repository PSGallery
Install-Module -Name VMware.PowerCLI -Repository PSGallery3) Install and import the required PowerShell modules for the joint integration between AVS and Everpure Cloud Dedicated:
Install-Module Microsoft.AVS.Management -RequiredVersion 7.0.133 -Force -Repository PSGallery
Install-Module PureStorage.CBS.AVS -Repository PSGallery
Import-Module -Name PureStorage.CBS.AVS -Force