All of its use cases helped a lot. If we're increasing network performance, we're cutting the risk down on our SLAs. We're increasing performance in the network. 

By doing dependency mapping, it makes migrations more efficient. There are less outages that require engineers to spend additional hours troubleshooting the migration failures. In addition, any way that we can use to maximize our distributed firewall rule policies, policies left, and CPU calculations on the servers increase the overall efficiency and performance of the cluster itself.

It has helped improve our organization by directing the network traffic using SDN.

vRNI can trace the flow of each and every packet and it is easy for us to troubleshoot all the issues that we do have with the networking. We can trace down the packet to a point where it has been dropped.

It has reduced the time to value, increased performance, and allowed us to more easily manage networks and gain deeper visibility. I see this product as most effective in the troubleshooting area. Every time I try to troubleshoot something it minimizes my troubleshooting time to about one-tenth of what it would otherwise take me.

It shows the customer what's going on their network. The product makes it much easier to show the customer the needs of their network virtualization. This is interesting because a network admin thinks they know what's going on in their network, but they don't.

We format the network flows with the customer for certain times. After that, we can see what their needs, sizing, etc.

It allows me to really represent network data in a way that management, and non-network engineers, can understand. That makes it easier for me to make my point.

It hasn't improved the way our organization functions, yet. It's only been in for two or three months and we're still trying to figure out the best way to pull the data out so that we can start building those firewall rules. But we anticipate that, once that time comes, it will cut massive amounts of time in the process of building those rules.

Instead of gathering so many resources, such as, multiple system engineers, network engineers, and search engineers, now it's all in one shop. One person can actually troubleshoot the issue without bringing in so many people. The troubleshooting time has been greatly reduced.

For the people who know how to use it, it's easily manageable. We want to increase the technical knowledge of the personnel who handle these types of things. I don't think we're there yet. But the few who use it, what it brings to the table has definitely helped us move forward.

It allowed us to set up NSX and to do microsegmentation, without all of the pain points of having to determine each port and each IP address that needed to have access, and which ones needed to be blocked.

It also sped up our time to value. It brought the time it took to implement way down to a number of days, instead of a number of weeks.

It improves efficiency. Sometimes, to implement a project we have a bottleneck which takes a lot of time in dealing with the network team. But now, with NSX deployed and Net Insight there, we can troubleshoot any issues proactively. It helps us get things deployed very quickly.

It has reduced time to value.

We see about a 20 - 25 percent increase in performance, because of this solution.

In terms of more easily managing networks and improving the visibility, that's the best side of this product, and we're enjoying it. It helps us to manage the network easily.

It has definitely helped us to meet compliance rules by assuring that all traffic is going to where it's supposed to go. It can be used to report that you are in compliance, as well as helping you get into compliance. We use it on an ongoing basis to show our clients in our cloud that traffic is not going to them that isn't supposed to be. We have customers that have to be assured that our environment is safe for them, and it gives them that confidence, that knowledge. We retain customers longer.

It has reduced time to value for sure because it would be very hard to do this any other way. We would have to sniff packets, and that's just very labor intensive.

It has given us much better insight into how we're deploying and how we perform after we deploy. It has also definitely helped to reduce time to value, and definitely helped provide deep visibility.

We tend to rely on vROps for the monitoring aspect, the performance piece of it, but that's because we're particularly focused on capacity right now. I expect to run the two in parallel when we're in a more operational model, where I will have the day-to-day folks deeply involved. Right now, it's still primarily run by engineers.

Right now, since the PoC, in the environment that we're using it on, for troubleshooting any issues that come up, or in the case of the microsegmentation, it's very valuable because it has allowed us to add firewall rules that were specific to what we needed, and not the extra firewall rules that other people thought we needed.

It has allowed us to easily take the physical environment and bring it into virtual and then put together the firewall rules that were needed, not necessarily firewall rules that everybody thought we needed, which were already in the old firewalls. We were able to do that much quicker doing it this way, rather than trying to weed out all the rules that didn't necessarily need to be there.

Troubleshooting-wise, we did have a problem in the environment and it made it easier to find the actual issue, the real issue, not something that we thought was the issue.

We're in a huge NSX implementation right now and trying to understand each application. vRNI's been very helpful in helping us protect each one of those applications.

Previously, we had no idea how the dataflow worked. We knew how all the applications and servers worked, but we never knew how the dataflow was happening. vRNI provides more insight into the dataflow.

It definitely saves times because we are not using this for performance monitoring and not really for monitoring for troubleshooting.

We're only at the evaluation stage but the benefit we're looking for is to speed the production deployment of the applications in a microsegment environment. We would love to get to that ring of Zero Trust but we're just not there today.

It has really tightened down the security. That was something that we were lacking.

It has also given us deep visibility into our network. We can really get down and see all of the traffic within the data center, between the VMs, between the applications, database servers, other application servers, web servers. We can identify everything that is communicating, and we can see it all on one product.

vRNI has improved our organization mostly through our NSX deployment. When we deployed NSX, we were able to watch the flows and create the rules which are normally unseen. When we are going through an application, we have a list of ports (allow or denied rules in NSX). With vRNI, we are able to watch what is happening. If something is not listed or spec'd out by the vendor, but still necessary, like interfaces or engines, we can catch them without causing downtime to the production application when we implemented NSX.

It definitely helps us manage our network. It provides that deep visibility into what is happening with traffic. You usually don't think of where your traffic is coming from (e.g., this server is connect to that server), but you have your authentication level and other flows that you never even think of. This product helps us with the visualization.

We're a smaller company. It automates a lot of the tasks and lets us focus in on building out our own solution. It's quicker, there is less building of manual solutions, and less downtime.

It allows our developers to quickly develop, get provisioning done, de-provisioning, etc; the stuff that you would expect to be able to make it streamlined.

It's very hard to find anything that works this well.

There are two different benefits that we derive out of the tool:

1. The assessment-based approach: When we go in to do services work or we are trying to understand sizing, what we need to deploy from an NSX perspective is an assessment tool. This helps us be very narrow and specific-focused. It allows us to assess and give quotes back very quickly. 
2. We use it in our services practice. Before we go and do any type of NSX services engagement, we use this tool on the customer's site to look at the environment and figure out some of our scoping and how we will scope our services. It allows us to be more efficient and pinpoint around the use case and actual solution.

It's faster access and searchability of the logs for troubleshooting.

It's intuitive and user-friendly. It can be a bit painful to deploy. Product provides excellent overview across physical and virtual networks in your virtual environment . In large organizations where vSphere / SDDC / Private Cloud deployments have thousands of VMs and network segments that product definitely bring significant benefit in terms of monitoring, troubleshooting and granular details of network deployment and traffic of connected devices (physical or virtual ) and last but not least holistic view of your network domain. 

It saves us on our SLA times because we are getting directly to the troubleshooting points. That is one of the main things that we are benefiting from. Whenever we have problems with our environment, we are able to solve them a bit sooner than we might otherwise have been able to. These benefits are directly connected to monetary benefits. It has helped to reduce time to value.

While increased performance depends upon what we are using in our networks, Network Insight is more towards how we actually see the entire network as a whole. Performance is mostly determined by what physical parts we are using in the network. While vRNI does not exactly increase the performance, we can better use the network we do have.

Finally, it provides deep visibility.

To some degree, it has increased performance, helped to more easily manage networks, and provided visibility. It pulls up more of the physical part of the network.

We now have a lot less administration after implementing the new service or removing an old system from our new software-defined data center. It has removed investigation time into ports and server traffic on virtual machines. Thus, it saves time.

Network and management is so much better within this solution and the whole software-defined network when we use NSX. I also manage the NSX firewall which flags the security in NSX. A lot of time is saved when you use this type of software solution for the network. We have moved systems into the new data center and the servers and systems are much faster because of the very low latency between virtual machines.

It has helped us tremendously to be able to easily deploy NSX in our environment with microsegmentation. It has also helped us with time to value. It has helped with network visibility for sure.

It has made the migration to NSX much easier. Most of the sys admins within the smaller silos, they have no idea what ports are needed to run their stuff at all. I am pretty sure the micro-segmentation would never, ever have occurred without it.

The benefits are it gives us insight into our network, which we can't get anywhere else.

It's helping us to scope our firewall rules.

If any VMs have an issue or there is a network issue or slowness or something similar, we can take a look at where the problem is being caused. It doesn't matter if it's a physical or virtual switch.

It gives the visibility that was either broken or there in pieces only. This solution provides a unified view of the whole system, back and forth. It has helped to reduce time to value, increase performance, more easily manage networks, and provide deep visibility.

It helps a lot because, until now, we haven't had the tools to figure out the micro level, VM-to-VM kind of traffic; that was not in the current environment. We could not figure out VM-to-VM communication from the other tools. This is the tool which gives us end-to-end transparency.

It has helped reduce time to value. It helps us to troubleshoot, to know exactly where the problem is.

It hasn't yet changed the way our organization works, but that's our hope.

It helps pinpoint, in the logs and the like, what we need for analyzing and for troubleshooting. It has also provided us with deep visibility.

It has enabled us to set up and do application discovery, as far as network traffic is concerned, and set up the appropriate rules that we need to make sure we're compliant with our security frameworks.

We're able to implement intersects using this tool.

We can see everything going on in NSX and get a good picture of our environment.

It is still in our lab environment.

We are better able to understand our needs for future growth and budgeting purposes.