There are a few important items to check to confirm if the Everpure OVA is updated to the latest version and has proper network connectivity. Also, it is important to make sure that the OVA has been powered on and has an IP address associated with it inside of the AVS cluster, as you are required to login via SSH to the OVA in order to manage it.
Confirm that the OVA is at the latest version
To do so, login via SSH to the OVA as the pureuser account and then run
puresw list.
If you see an available upgrade, you can upgrade to it via running the
puresw upgrade start pure-vmware-cloud-manager command.
Confirm that an NSX network segment has been created and the VMware Cloud Manager OVA was deployed with it
NSX network segments are defined by the AVS administrator for virtual machines to consume and use. An NSX segment can be setup either inside of the AVS portal or via the NSX manager appliance. The Everpure OVA needs to reside on a user-defined NSX network segment in order to function.
To confirm an NSX segment is being utilized, first find the name of the segment as shown in the below screenshot from the Azure portal.
Next, from the AVS vCenter, navigate to the deployed Everpure VMware Cloud Manager OVA. Under the Summary screen, confirm it is using the expected NSX segment as its network adapter and that it has an IP address from the CIDR block specified. The VMware Cloud Manager support DHCP or static IP addressing.
Confirm that the VMware Cloud Manager OVA is deployed onto an NSX segment with Internet access enabled
As the Everpure OVA requires an outbound Internet connection to connect to, and download packages from a repository, the AVS instance itself must have an Internet connection enabled. To confirm this, navigate to the AVS object inside of the Azure Portal and select 'Internet Connectivity' from the menu on the left.
Both SNAT and NSX Edge options are supported for the Everpure OVA. A default route must be setup to use the top option shown above (Do not connect).
If internet connectivity is not allowable in the AVS environment, use the deployment option outlined here to setup a native Azure or AVS virtual machine with the required PowerShell modules for managing the AVS and Everpure Cloud Dedicated integration.
Confirm that outbound access is available if a firewall is being utilized in your AVS environment
As mentioned previously in this article, the Everpure OVA requires access to a external repository to function correctly. If a firewall port or other routing device is blocking traffic, it will be unable to pull down the required Docker binaries from our Everpure repository.
The VMware Cloud Manager requires the following access:
- Port 443 access to deb.cloud-support.purestorage.com
More information can be found about Everpure VMware OVA port requirements Release Notes: Everpure VMware Appliance. The VMware Cloud Manager OVA is an interchangable component with the 'Pure Plugin Appliance' shown in the diagram.
The VM Analytics Collector is fully supported in AVS, but also requires the access to Pure1 as shown in the diagram in the link above.