How to Upgrade AVS Host and Capacity Monitor Functions

This article outlines how to upgrade the AVS Host and Capacity Monitoring functions.

Azure VMware Solution (AVS) and Everpure Cloud Dedicated feature two optional monitoring functions:

AVS Host Monitor: Automates AVS ESXi host addition and/or replacement with Everpure Cloud Dedicated.
Capacity Monitor: Automatically expands an Everpure Cloud Dedicated array when a capacity threshold is reached.

Important: Do not use Capacity Monitor function with the Automatic Capacity Upgrade enabled.

CAUTION:

Please note that starting from Purity//FA version 6.8.7 and higher, this function is deprecated and Everpure Cloud Dedicated Automatic Capacity Upgrade feature should be used. For more details on this feature, read this guide.

These functions can be deployed into a single Azure Function or run independently. This article outlines how to upgrade these monitoring functions. Everpure frequently releases updates to these functions that introduce new capabilities and bug fixes, so it's important to update them regularly.

Updating the functions require providing the original deployment information, If you have the original deployment information you can follow option A. If you do not have that information and need to retrieve it first, then go to option B.

Attention: When using Deploy-PCBSCapacityMonitor command, it can fail at first time run with the error similar to

Code: DeploymentFailed) - { "Code": | "BadRequest", "Message": "Encountered an error (InternalServerError) from host runtime."

. The error is under investigation, to solve this issue, please re-run the same command again.

Option A: If You Have the Original Deployment Information Saved

Re-run the same Deploy-PCBSAVSMonitor and/or Deploy-PCBSCapacityMonitor command(s) you used during the initial deployment:

For the AVS Host Monitor Function: Execute the following command, replacing placeholders and sample values with your specific information from the previous step:

Deploy-PCBSAVSMonitor -AVSCloudName "yourAVSName" -AVSResourceGroup "yourAVSResourceGroupName" -MonitorResourceGroup "avs-monitor" -MonitorResourceGroupRegion "eastus" -VNetName "vnet-useast" -VNetResourceGroup "vmware-useast" -VNetSubnetAddress "172.16.70.0/24" -VNetSubnetName "subnet-avsfuncappzuhizsevcn6va"

For the Capacity Monitor Function: Execute the following command, replacing placeholders and sample values with your specific information:

Deploy-PCBSCapacityMonitor -MonitorResourceGroup "capacity-monitor" -MonitorResourceGroupRegion "westus2" -VNetName "vnet-uswest2" -VNetResourceGroup "vmware-uswest2" -VNetSubnetAddress "172.17.18.64/28" -VNetSubnetName "avs-cbs-Monitor"

This will update the function to the latest code.

Note:

If both the host monitor and capacity monitor instances are running within the same Azure Function, you will need to run both deployment commands to update each one individually.
It may take 1–2 hours for the required dependencies for the upgraded Azure Function to download and become active.

Option B: If You Need to Retrieve the Deployment Information

Retrieve the Monitor Configuration Information.

For the AVS Host Monitor Function: Run the following command, replacing "avs-monitor" with your Monitor Resource Group name:

Get-PCBSAVSMonitor -MonitorResourceGroup "avs-monitor"

Example output:

MonitorArrays                    : {172.16.65.4}
MonitorResourceGroupName         : avs-monitor
MonitorRegion                    : eastus
MonitorVnetName                  : vnet-useast
MonitorVnetResourceGroupName     : vmware-useast
MonitorVnetRegion                : eastus
MonitorVnetProvisioningState     : Succeeded
MonitorSubnetName                : subnet-avsfuncappzuhizsevcn6va
MonitorSubnetAddressPrefix       : {172.16.70.0/24}
DefaultRunCommandTimeoutInMinute : 10

For the Capacity Monitor Function: Run the following command, replacing "capacity-monitor" with your Monitor Resource Group name:

Get-PCBSCapacityMonitor -MonitorResourceGroup "capacity-monitor"

Example output:

DefaultUtilizationThreshold  : 80
MonitorArrays                : {172.17.20.27, 172.17.20.28}
MonitorResourceGroupName     : capacity-monitor
MonitorRegion                : westus2
MonitorVnetName              : vnet-uswest2
MonitorVnetResourceGroupName : vmware-uswest2
MonitorVnetRegion            : westus2
MonitorVnetProvisioningState : Succeeded
MonitorSubnetName            : avs-cbs-Monitor
MonitorSubnetAddressPrefix   : {172.17.18.64/28}

Upgrade the Monitor Functions:

For the AVS Host Monitor Function: Execute the following command, replacing placeholders and sample values with your specific information from the previous step:

Deploy-PCBSAVSMonitor -AVSCloudName "yourAVSName" -AVSResourceGroup "yourAVSResourceGroupName" -MonitorResourceGroup "avs-monitor" -MonitorResourceGroupRegion "eastus" -VNetName "vnet-useast" -VNetResourceGroup "vmware-useast" -VNetSubnetAddress "172.16.70.0/24" -VNetSubnetName "subnet-avsfuncappzuhizsevcn6va"

For the Capacity Monitor Function: Execute the following command, replacing placeholders and sample values with your specific information:

Deploy-PCBSCapacityMonitor -MonitorResourceGroup "capacity-monitor" -MonitorResourceGroupRegion "westus2" -VNetName "vnet-uswest2" -VNetResourceGroup "vmware-uswest2" -VNetSubnetAddress "172.17.18.64/28" -VNetSubnetName "avs-cbs-Monitor"

Note: It may take 1–2 hours for the required dependencies for the upgraded Azure Function to download and become active.