The Cloudvision On-Premises solution has two software components: CloudVision Portal Software (CVP) and CloudVision Appliance Software (CVA). The Software Release Policy and Life Cycle defines the various phases of development and support to guide customers in transitioning to newer versions of the product based on the milestones in the life cycle. Arista Networks will support each major software release train of CloudVision Portal and the CloudVision Appliance Software for up to 24 months from the general availability date for a particular train. The following diagram depicts the release phases and the Arista TAC support mapping across this timeline.
- Major release with new features and functionality
- Active maintenance releases for bug fixes as needed
- TAC support available
- Ongoing TAC support
- Software upgrade required for bug fixes
The following table depicts the CloudVision Portal release support matrix, including the timelines for each major software train (based on the 24 month life cycle policy) and includes the current state of support for each train.
The following table depicts the CloudVision Appliance Software (CVA) release support matrix, including the timelines for each major software train (based on the 24 month lifecycle policy) and includes the current state of support for each train.
*The CloudVision Appliance was recently added to the Lifecycle policy. Because of this, Release 6.0 remains active for an extended period.
For assistance with software upgrades, please refer to the CloudVision Appliance Quick Start Guides: DCA-250-CV DCA-300-CV DCA-350E-CV or contact Arista Networks Support by emailing support@arista.com.
EOS Support Lifecycle in CloudVision (On-Premises and Cloud Service)
Each CloudVision on-premises release has a minimum and maximum supported EOS release, as specified in the release notes. This also applies to CloudVision as-a-Service.
When an EOS train goes end of support, we do not explicitly remove support from CloudVision, however we stop testing newer CloudVision releases against that EOS train. While most CloudVision features will likely continue to work against the now unsupported EOS train, that support is best effort. Upgrading the EOS devices through CloudVision to reach a supported EOS release is supported, and is the recommended path.
To assist with customer migration of EOS on devices, CloudVision supports an EOS train for at least 12 months after the train’s end-of-support date, as reflected in this table.
The Expected End of Support in CloudVision dates provide guidance for CloudVision as-a-Service and on-premises releases.
For more information on EOS lifecycle information, please refer to: https://www.arista.com/en/support/product-documentation/eos-life-cycle-policy.