As a virtualization specialist, I am here to provide an in-depth analysis of the recent announcements made by VMware regarding the End of Availability (EOA) of two of their flagship products: vCloud Networking and Security (vCNS) and NSX for vSphere 6.1.x. These developments are crucial for any organization using these solutions, and it is essential to understand the implications and potential options.
Firstly, let us take a closer look at the EOA of vCNS. The product will reach its end of availability on September 19, 2016, which means that support will no longer be available, and there will be no further updates or patches. While the product will continue to function, using it at your own risk may lead to unforeseen consequences, especially when dealing with critical infrastructure. This news might be challenging for existing vCNS customers who are not service providers or have not yet explored NSX-v.
The EOA of NSX-v 6.1.x, on the other hand, may come as a surprise to some, but it is not entirely unexpected. The product will reach its end of availability on October 15, 2016, and like vCNS, support will no longer be available, and there will be no further updates or patches. However, the good news is that NSX-v customers can easily upgrade to a newer version, such as 6.2.x, which offers enhanced capabilities and features.
One of the significant caveats for existing vCNS customers who are not service providers is the cost difference between vCNS and NSX-v. In most cases, vCNS was part of the general vSphere/vCloud editions and bundles, whereas NSX-v is a more comprehensive and feature-rich solution that comes with a higher price tag. This cost difference can be challenging for some customers to justify, especially if they do not require all the features offered by NSX-v.
To address these concerns, there have been talks about VMware releasing an NSX-Lite version, which would satisfy the gap that exists between current customer requirements of vCNS features vs. the comprehensive nature of the NSX-v feature set. However, no official announcements have been made regarding this potential offering.
In terms of upgrading from vCNS to NSX-v, there are a few options available. Existing vCNS customers can upgrade directly to NSX-v 6.2.1 or later to avoid any regression in functionality. Additionally, VMware has released an additional whitepaper for vCAT SP that provides guidance on upgrading vCNS to NSX in vCloud Director environments. This whitepaper is a valuable resource for those looking to make the transition to NSX-v.
In conclusion, the EOA of vCNS and NSX-v 6.1.x marks the beginning of a new era for network and security solutions in the virtualization space. While the end of support for these products may present challenges for some customers, there are options available to ensure a smooth transition. With the potential release of an NSX-Lite version and the continued development of NSX-v, the future of networking and security in virtualized environments looks bright. As always, I will continue to monitor these developments and provide updates as more information becomes available.