vRealize Network Insight Reviews

We're using it for our microsegmentation project. The performance has been good.

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.

I like being able to see the flows coming in and out of the product.

In terms of monitoring network flows, we use it to verify whether or not different servers/applications should be communicating with each other.

It needs to be a little easier to use and to understand the information it's putting out. That would make it more helpful.

If you're not a network person you need to understand things like network policies and concepts. If you gave it to a regular admin, it would be nice if it were easier for them to pick up what is going on, understand the flows and whether or not stuff should be talking to each other, as opposed to just port groups and IP addresses.

Also, if it were more application-aware, more descriptive; if it were able to determine the application that is actually doing the communication, that would be easier. More application information: which user or account it's accessing, is it accessing this application, doing these calls, if it is accessing a script, which script is it accessing. Things like that would provide deeper analytics so I can track what's going on. It would not just be, "These people shouldn't be talking," but who is actually doing these calls.

And it would be good if it could correlate the server and not just a SQL call, but which database, which server, that would be helpful. I would like to see more things along those lines.

It's pretty stable. We haven't had any problems with it.

We don't have any issues with the scalability. The scalability has been fine.

We haven't had to use tech support at all.

We were buying VMware NSX Enterprise as a security solution, to better lock down our environment. vRealize Network Insight was one of the tools they suggested we get, as part of that package, to make the implementation easier.

The most important criteria when selecting a vendor are

• ease of use
• integration
• interoperability
• support
• vendor reputation.

I have been using VMware since v1.5. I know the reputation and the support and that helped a lot. Also, their being the leader in the industry, the direction they have been going, and their forward-thinking, were all part of our decision to go with them. A lot of the other vendors are playing catch-up or they're plugging into the VMware infrastructure, so why would I go to somebody else when I can go with somebody who owns the code?

I set it up. It was pretty straightforward to set up. It was pretty easy, especially compared to some other VMware products.

I have also had the opportunity to upgrade it to a newer version. It was easy. It wasn't bad at all.

We bought a package deal so I can't specify the ROI on just this part of it.

Make sure the solution you're looking at is compatible with what you want to do and that it has future growth to it; not just a pinpoint solution but a solution that is part of a bigger vision. You don't want to buy a product that does just this one thing and then you have to buy another product to do something else. Make sure it has interoperability and integration points with some of your bigger infrastructure.

I would rate vRNI at eight out of 10. It would be a 10 if it could bubble up deeper application and user information.

The way you can view flows inside your network.

We're able to implement intersects using this tool.

Make the GUI easier to use.

I recommend for anyone deploying this solution that you are going to have to get everything to point to that piece of software. So, you get a good rating, thus getting you good data.

It's good. Solid.

It's good.

I haven't used technical support.

We weren't using anything previously. We were going to implement the NSX, so we knew we needed to use this solution.

I was involved in the initial setup. It was pretty straightforward.

In-house.

No one else. Just VMware.

If you are going to implement NSX, it's a great tool. It really helps. The network piece, they should look at that, and see what to do with NSX.

Most important criteria when selecting a vendor: good support.

Going through our logs within the system, it's easier to identify issues. For example, the filtering in order to show correct errors. In addition, the troubleshooting timeframe shortens a lot with our product.

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.

The pricing is steep.

The past two months.

I have had no issues so far, since the deployment. It's been pretty stable.

It is very easy to work with; you can add nodes as you go. As your environment grows, you can add nodes to it, increase it, then scale out.

Technical support is great. They do excellent work. They stay on top of their tickets and support cases. We get updates on a daily basis, so I'm very satisfied with the support.

I was involved in the initial setup and it was straightforward.

We have a temporary in-house person. I recommend having a temporary in-house person.

Turbonomic.

We chose VMware for their product, their environment, and the confidence level of using the product itself.

The way technology works, you've got to catch up. If you're basically staying in a legacy environment, and everything is moving rapidly, you've got to stay ahead of the game.

Most important criteria when selecting a vendor: customer support.

My recommendation: If you're looking to minimize your downtime, your troubleshooting, and the amount of resources being used in order to look at logs and troubleshoot an issue, this is the solution.

Login site gives you the opportunity to collect logs from all of your hypervisors and your virtual servers, then put them all in one location and make them searchable.

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

Better integration into VRB.

We did our due diligence, studied best practices, read the documentation, prepared a plan, presented the plan, and everybody understood what's going to happen.

It is best to have a contingency plan to back out if things go wrong.

Stability is there. A 10 out of 10.

Scalability is about a 10 out of 10.

I have not used technical support for this solution.

I was involved in the initial setup. It was straightforward. It took about 10 minutes.

We used an in-house team.

Dell EMC, Hitachi, and sometimes Microsoft.

We chose VMware because they have one of the better products on the market for what they do: virtualization.

Most important criteria when selecting a vendor is that they're there when you need them.

For someone looking at this solution: Look deep.

Capacity management: the forecasting of capacity.

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

Price. Honestly, the way it's licensed is challenging.

The stability is good.

So far, it's been okay.

It's been good. They are knowledgeable. We can reach the right person.

As we started moving to more critical applications of this infrastructure, we needed to be able to manage it at a higher level than we had been.

For the most part, it was pretty straightforward. Some of the advanced configurations were a little bit more difficult.

In-house.

We used Microsoft for monitoring solutions as well, then VMware. We chose VM because it's more integrated with what we're trying to do with the infrastructure.

The most important criteria for selecting a vendor: Functionality of the product, it's got to work, then responsiveness of the support.

vRNI taught us to troubleshoot issues and help us implement our NSX product. Therefore, it's been one of the most valuable tools of the product.

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.

They are already working on it, which is really nice. It would be the capability of actually identifying certain applications, like SQL, file servers, DNS, AD servers, and making it easier to identify those types of systems.

Stability for vRNI - it just works. We haven't had any issues with it.

The scalability is great. We haven't had any issues with the capability of the machines, NSX, or with the implementations of both.

Personally, I have not called technical support.

I was not involved in the initial setup.

We had an inner engagement, and their engineers highly recommended using the tool, as far as the implementation for NSX.

Before this, we weren't using another solution at all. We're pretty much using VMware for this type of environment.

Support is very important, to be available especially for issues that may be new with the features which we're trying to implement. We tend to request support quite a bit, so support is definitely very important.

I would definitely advise, especially healthcare companies that need to secure their products, NSX using vRNI as their tool. To implement it, I would highly recommend that they invest the time to learn how to use vRNI.

• Provides us a map of what's going on - on our network.
• Allows us to start microsegmentation.

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.

Maybe improve the fonts.

It's really stable.

It's very scalable.

No.

We were not previously doing something else. When we were going to NSX, we knew we needed to do this. This is just part of our movement towards that.

I was involved in the initial setup. It was really straightforward.

In-house.

Look at the following:

• Stability
• Interoperability with what you own
• Price.

For this, really nobody. Just VMware.

If they have VMware, and they're gonna stick with it, then this is probably the tool they want to look at for their network flow.

Just know what your network is and what you intend to do in terms of segmentation. Know your network, know your environment.