vRealize Network Insight Reviews

For us, it's for a security tool, to analyze flows and network traffic and to try to progress along the path of microsegmentation.

In terms of monitoring network flows, if we're trying to set up microsegmentation rules in our distributed firewall, we'll say, "Okay, let's just start with a case." We'll try to isolate an app, and isolate all the network traffic there. We'll analyze it, validate or do discovery using vRNI, and then set up the appropriate rule.

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 have the real-time updates that we can see, so that's been pretty valuable. The mapping is really good, so that has also been a pretty good feature for us.

It's somewhat user-friendly but some of the data that's presented is not always clear. But that's like any tool. You just have to get used to using it.

The stability is great. There is no problem with it.

The scalability is fine.

We invested in NSX, so we wanted a tool that would give us visibility into that virtual layer.

When selecting a vendor what's important for us is whether they are able to fulfill the requirements that we have defined in our business case.

There's no real advice. You'll know if you need something like this or not. You don't just purchase it and then hope for the best. You have a use case for it.

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.

Our primary use case is to use it do design and for troubleshooting the future.

We have had the product for three weeks now.

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

It is still in our lab environment.

• Its open design.
• Figure out what's being used in our environment.
• Building roles.

The product is slightly complex use, while still being user-friendly. It could use more training modules, as it is not a straightforward product.

It is pretty stable.

The technical support has been good so far.

We've owned NSX for three years and now starting to deploy it, which is why we went with vRNI. We did not even consider another solution to go with it.

The initial setup was simple. It took about an hour.

They are coming onsite in about two weeks.

It's an expensive product because we have a lot of nodes. 

They should include the product in NSX because it's important to have it for deployment.

Do the training before purchasing. Research the product and its competitors.

Most important criteria when selecting a vendor: technical knowledge. They need to understand their product.

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.

We want to use it for the basics, checking out traffic flows. One of the main reasons we got it was that we have a new mobile application, and we'd like to track all the traffic between the different layers: DMZ layer, database layer, app layer.

The most valuable feature is being able to easily see the path that the VM traffic is taking, what ports are in use.

It's pretty much user-friendly, but it could always be friendlier. Anything that would make it easier would be helpful.

So far, it has been pretty stable.

As far as I know, the scalability is good.

We have not had to use technical support yet.

Make sure you check out the demo, make sure you have enough time to check out the demo, run it in your environment for a while, and study up as much as you can on it.