Appliance Requirements
- To upgrade from versions 3.4.1 and older to 3.4.2 and newer, a new OVA will need to be deployed. Please Everpure VMware Appliance: GPG Key Expiry for more information.
- The OVA must be deployed on vCenter Server 6.5 U3 or higher.
- For online deployments, the OVA must have access to Pure1 to support appliance and application upgrade queries and tasks with
puresw.- Specifically access to
deb.cloud-support.purestorage.comvia port 443 is required.
- Specifically access to
- For offline deployments, you will need to download a supplemental iso to install the Remote vSphere Plugin.
- The OVA is deployed with 4 vCPU and 8 GB of Memory. The vSphere Environment will need to support a VM of that size.
- One application (vSphere Plugin, VM Analytics collector, VMware Cloud Manager) can be deployed to each instance of an OVA but multiple OVAs can be deployed in the same environment without issue.
- The applications that run on the OVA run as a Docker container. Docker has its own bridge network configuration, with the default being a 172.17.0.1/16 for IPv4 and 2001:db8:1::/64 for IPv6. If your internal network configuration overlaps with this default, you must change the Docker bridge network via the fields in the OVA deployment wizard to avoid IP address conflicts.
- When the OVA's operating system needs to be updated, the OVA will need to be upgraded first in order to see the remote vSphere plugin upgrade options. When running puresw list If your target version vSphere plugin version is not visible but the OVA says it can be upgraded, upgrade the OVA first.
- Network diagram:
What's New?
- Support for static IPv6 networks
- Currently, VM Analytics Collector is the only application that supports IPv6. Other applications will only work with IPv4.
- Switching between IPv4 and IPv6 is not allowed after deployment without redeploying the appliance.
Known Issues
- When deploying the OVA to vCenter Server 7.0 U2 or higher a warning will display that the certificate is untrusted. This is not an issue with the OVA certificate signing, but rather VMware changed the certificate validation process to only approve certificates signed by Authorities in the vCenter's Trusted Root store. See VMware's KB on the matter for more information.