vRealize Network Insight Reviews

With vRealize Network Insight, I handle virtual virtualization products, particularly with VMware, focusing on Hypervisor and VSAN. I deal mostly with governments, agencies, and medium to large enterprises.

I find that the interface of most VMware products is very similar, which I consider an advantage due to its ease of use compared to other tools like Splunk. The integration with Veeam is also significant. One of the biggest problems with VMware NSX is logging, and vRealize Network Insight helps by providing comprehensive logs.

We use it for network troubleshooting, to provide some capacity reports, and to help generate rules for NSX microsegmentation.

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.

The tool's ease of configuration and use and the availability of information and artifacts through professional services and the web are key factors that customers find valuable.

The IT infrastructure industry is expected to evolve towards a hybrid cloud model in the next five to ten years. In this model, most of the customer's resources reside on-premise within a private cloud setup, such as VMware. Another segment operates within public cloud environments like Azure and AWS, and a portion remains in traditional data centers.

There should be seamless interoperability between public and private clouds. AWS and VMware need to work together to make it possible. Whether users interact with on-premise infrastructure or configure resources in the public cloud, the user experience must be seamless. 

We use the solution for NSX-T Manager and the customer wanted to have the firewall rules in order to achieve micro-segmentation. To analyze their environment, we use vRealize Network Insight which provides us with all the firewall rules for traffic to and from. This is why we use vRealize Network Insight.

The best feature of this application is its ability to capture everything within the same application, as well as capture all the traffic. Essentially, the solution is capable of capturing anything that happens outside of the network port.

vRealize is used to help our development team by producing detailed reports of the network flow and layout. This includes details like the TCP network keys and the RTT.

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

I'm a consultant. I'm consulting and setting it up for my clients. I don't have one running in my environment.

Its use cases include:

• Deeper analytical insights into network traffic.
• Ability to troubleshoot network performance issues within the environment.
• NSXT, micro-segmentation recommendations after a thirty to sixty-day learning period to remove redundant firewall rules, make more efficient firewall rules, and then bring down the individual limits, i.e, the limits on how many firewall rules you can have on a vNIC. 

I also like them to use it for dependency mappings as part of migration projects and figure out everything is talking to what and ensure that we have them all in a consistency group replicating consistently. When we fail them over, bring them up in the proper order they need to be brought up in. Those are just a few of these cases.

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.

We are attempting to discover legacy network transactions and convert them to micro-segmentation rules with NSX-T.

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.

Our primary use case for the solution is to monitor the end-to-end network aspect of our environment. The performance is really good. We don't have any delays or the like. It gives us really good performance.

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.