It requires manual downloading and uploading of files to share information between tools.But don’t just take our word for it. In addition, vRNI is not well-integrated into NSX, which makes the task of moving from visibility to policy a long and complex process. This leads to more complexity and significantly more time to achieve results. So, a true hybrid infrastructure requires multiple products from VMware, and the need to synchronize policy across them. This requires a separate product, vRealize Network Insight (vRNI). In addition, it is a best practice in any microsegmentation project to first start with visibility to map flows and classify assets where policy will be applied. This means NSX-V for ESXi hosts, NSX-T for bare-metal servers, and NSX-Cloud for VMware cloud hosting. VMware NSX requires multiple tools to cover the entire hybrid data center environment.
The following are some of the key pitfalls to avoid when considering NSX. While the evolution to NSX-T was a step in the right direction for VMware strategically, there are a number of limitations that continue to limit NSX’s value and effectiveness, particularly when compared to specialized microsegmentation solutions like Guardicore Centra. However, NSX-T remains limited by feature gaps when compared to both NSX-V and other microsegmentation solutions, including Guardicore Centra. As a result, NSX-T is a much more viable offering than NSX-V now that hybrid cloud and cloud-only deployment models are growing in popularity. It is decoupled from VMware’s proprietary hypervisor platform and incorporates agents to perform microsegmentation on non-VMware platforms. NSX-T (NSX “Transformers”) was designed to address the use cases that NSX-V could not cover, such as multi-hypervisors, cloud, containers and bare metal servers. So, given the large number of organizations embracing the cloud, interest in NSX-V is waning. The 2019 RightScale State of the Cloud Report in fact shows that 94% of organizations use the cloud - with 28% of those prioritizing hybrid cloud – with VMware vSphere at 50% of private cloud adoption, flat from last year.
It is only applicable for VMware virtual machines, which leaves a coverage gap for organizations whose use a hybrid infrastructure model. As the name suggests, NSX-V is designed for on-premises vSphere deployments only and is architected so that a single NSX-V manager is tied to a single VMware vCenter Server instance. NSX-V (NSX for “vSphere”) was the first incarnation of NSX and has been around for several years now. Also, regardless of which product variant an organization is considering, there are several potential pitfalls with NSX that are important to understand and consider before proceeding with deployment. Although many security and virtualization experts have written about the differences between the two offerings, including speculation on whether or not these two solutions will merge into a single offering, we think we offer a unique perspective on some of the differences, and what to pay attention to in order to ensure segmentation projects are successful. And specifically, we get a lot of questions from customers about the difference between VMware’s two offerings in this space, NSX-T vs NSX-V. One of the common comparisons we get is to VMware NSX. This is expected, and, in fact, welcome, as we will take on any head-to-head comparison of Guardicore Centra to other products for microsegmentation. While working with many customers on segmentation projects, we often get questions about alternative products to Guardicore.
0 kommentar(er)
