Authentication OIDC Authentication VNS3 Licensing Access Management Clientpack Generation Installing HTTPS Firewall 2.0 Firewall AWS Specific features Firewall FWSets VNS3 Variables VNS3 Router IPsec Configuration IPsec Parameters VNS3 Peering Mesh Setting Topology Name VNS3 Overlay Network Snapshot Management VNS3 Event Alerting Network Address Translation Traffic inspection SNMP Support VNS3 BGP Configuration Guide Remote Support Resetting VNS3 Upgrading VNS3 Release Notes VNS3 EOL Policy and Milestones IPSec Connection Checklist VNS3 Known Issues VNS3 Specifications VNS3 VPN Client tools VNS3 Control Center VNS3 setup

VNS3 EOL Policy and Milestones

Every Cohesive Networks product has a lifecycle. The lifecycle begins when a product is released and ends when it’s reached end of life (EOL). Cohesive Networks will periodically discontinue VNS3 product versions that reach end of life (EOL) for a number of reasons. These reasons may be due to product line enhancements, changes in industry standards deriving changes in the product, or general market demands.

Knowing relevant dates in this lifecycle helps customers make informed decisions about when to upgrade or make other changes to their topologies. All information updates included on this page are sent to our existing administration customer list. Contact us to be added to that mailing list.

EOL Process

The end-of-life process consists of a series of activities that, once completed, make a product version obsolete. Once obsolete, the product version is not sold or supported.

End of Sale Date

The EOL process is started when Cohesive Networks announces the End of Sale date for a particular product version. The End of Sale date is provided at least ninety (90) days prior to the EOL date. On the End of Sale date the product version is removed from the price list and is no longer available for purchase. Customers have access to the latest product versions at all times.

End of Life Date

On the day of EOL the product version images will be deregistered/removed from the cloud catalog or customer account and will no longer be available for launch (running instances will not be affected) or support.

Upgrade Process

Upgrading to a new version of VNS3 or VNS3:ms requires launching a new instance and applying the running configuration from the old VNS3 instance to the new instance. While VNS3 upgrades from EOL product version is a simple operational procedure, an operational window is usually required. Future version of VNS3 will allow for live upgrades.

VNS3 Versions

The following table describes the end-of-life milestones, and dates for the VNS3 product versions. If you are running a VPN3/VNS3 instance that was launched using a version number not listed, contact support to discuss upgrade paths and availability for chaperoned upgrades free of charge.