vRealize Network Insight Reviews

We are using vRealize Network Insight to map all the connections between the servers.

The vRealize Networking site meets our expectations, especially since it allows you to add servers manually. For example, if you have a CSV file, you can upload it manually on the network side and establish relationships between physical servers and virtual servers.

The automation collects all the relationships between servers, allowing us to visualize these relationships and organize the migration into waves. We're using it to create waves—wave one, wave two, wave three—so we can migrate groups of servers simultaneously from one domain to another.

Since Broadcom acquired VMware, it has been experiencing challenges. Many sales processes are not well defined.

They can show a little bit more information because vRealize Network Insight is virtual and is looking or searching for a virtual environment. They can show a little bit more details about the relationship.

I rate the solution’s scalability a nine out of ten.

The initial setup is easy.

I rate the initial setup a nine out of ten, where one is difficult and ten is easy.

ROI is really about reducing the time it takes to map your network. For example, you can have just one person discover your entire network with a few clicks and start monitoring communication between servers. The ROI comes from using fewer people and less time to map your network.

The sales team often complains about the cost whenever we need to quote vRealize Network.

One key advantage of using it is that if your infrastructure includes VMware servers, it’s very easy and straightforward to deploy and start collecting data, especially if your environment is fully virtualized. However, suppose your environment is a mix of virtual and physical servers. In that case, getting detailed information about your physical servers within the vRealize Networking site can be challenging.

Overall, I rate the solution a nine out of ten.

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.

The most valuable feature for me is the different views that you can get when selecting an application or a VLAN. It shows you the traffic flows. It gives you a visual representation of something that, in text, just may not make as much sense.

That is valuable to me because, from my perspective, I don't own any of the applications, so I don't know how they would communicate normally. This gives me a little insight into which servers interact with what else in the environment and it helps me to maintain them in a more appropriate manner. I can see who's tied to what, and whether or not they're critical.

It's also user-friendly. It's similar to the GUI that most VMware products are moving to, and the consistency across those makes it easy to switch from one product to another. Also, the search bar at the top is plain text and it helps you, it guides you along with your search query, and that helps. The first day you're in there you can start building actual queries.

When we talk about those micro-segmentation rules, there's an Export function. It is very macro-segmentation oriented instead. So if you choose an application, it will find the tiers within that application and say that it's communicating on, say, port 80 to a separate VLAN. There might be 200 machines in that other VLAN. You don't want to open port 80 at all of them. So we need a lot more granularity in those suggested firewall rules. It's a good start, but it's still going to require a lot more work on our side to actually make it a real rule, instead of what it's trying to do with the macro rule.

I would like to see better micro-segmentation rules. That's key for me. That's our primary use case for it at this point. We might add others in the future but, at this point, that's what we need, and we're not quite getting it.

It has been rock solid. We have never had an issue with stability.

We haven't had to scale it, which is surprising, because with almost all of the other VMware products that we use, we have scalability issues. This solution seems to handle it better than most of their other products.

Tech support has been great. We even get access to the BU when we have questions about the API. We're very satisfied with it. 

We did not have a previous solution. We have a project to migrate from legacy networks into NSX-T. This solution was installed to facilitate that move, so that we can get there. It was recommended by our VMware TAM Services and by some of the engineers who were working for NSX-T.

The most important criteria when selecting a vendor are access to information, whether it's documentation, knowledge-base articles, or tech support; and stability. There is nothing more frustrating than having to touch the product frequently to make sure that it's up and running for you.

The initial setup was very easy. The deployment is just OVAs and it is really small, really fast to deploy. Just make 'em talk to each other and everything's happy.

If we can get it to provide those firewall rules it will literally save hundreds of man-hours, if not thousands of man-hours. So the ROI would be huge. But we're not quite there. When we get there, I anticipate the ROI will be much better.

I want to say it's a 10 out of 10. If they fix that micro-segmentation thing it will absolutely be a 10. Right now it's about an eight out of 10. I think it's just a big jump. If they can fix that micro-seg, that means so much more to me, so I would give it that extra boost for that. But the usability of it, how nice the interface is, those are great. If they improve the API that might get us to a nine, but if they get the micro-seg, I'll give them the other two points.

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.

We have deployed vRealize Network Insight in two or three environments for our customers' NSX implementations. It helps us in creating the network architecture and planning before deploying NSX. We use Network Insight to gather data and determine firewall rules and communication between virtual machines.

So far, vRealize Network Insight is helping us to decide on architecture and NSX networks for our customers.

One of the valuable features of Network Insight is its ability to provide detailed information about east-west traffic within the data center. With this product, we can precisely identify communication patterns between virtual machines within our data center, whether it's east-east or east-west communication.

There is room for improvement when it comes to pricing because we pay here in Brazil, and all the costs are based on the dollar. Our currency is a bit weak at the moment. It becomes a little expensive to buy this kind of product.

vRealize Network Insight has good technical support. It's really good support.

Positive

The initial setup is very easy. It's an easy setup, like plug-and-play. It's just a matter of deploying the virtual appliances and making a few configurations to start collecting data. The hardest part is analyzing the data, but the network consultants help us with reports to determine the filters we need to apply on the NSX firewalls.

Only one person is required for maintenance. We have just one analyst who knows how to handle vRealize Network Insight, and it's okay. We don't need additional personnel because our customers have small environments. So, we don't require a whole team of two or three, or four people to work with vRealize Network Insight.

I saw some ROI. Our customer teams have been able to spend less time on operational duties, vRealize Network Insight allows them to accomplish more with the same number of people on their teams. I do know that they are saving time.

I would rate the pricing a six out of ten. vRealize can improve and lower the price a little. Here, in Brazil, we have a distributor between the reseller and the manufacturer, and this distributor has a significant impact on the final cost of the product. But I do believe that they can lower it a bit. It's always a good choice to lower something, especially prices. 

Overall, I would give vRealize Network Insight a nine out of ten. 

We currently use it to find specific defects in our network flows. We're trying to streamline all our virtual needs with respect to network flows.

The primary use case is to make sure that we disperse our dollars in the right sense; that we use it the way we're supposed to use it, optimally. The idea is to understand how it works and do more of it and eliminate things that don't make sense.

In terms of performance, so far so good. Nobody is complaining.

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 enables us to understand what is happening in the VDI space and respond to things that don't work.

It's intuitive and very user-friendly, but we probably have to train our technical team, or the IT staff who are plugging into it regularly, on how to optimize its use. VMware probably needs to come in and train and we need good documentation.

I had a meeting with the technical account manager, and I brought to his attention that the lack of access to documentation on best practices is something that we need to address. That's something that he said he is working on. We have a meeting tomorrow and he is going to bring all of us onto the same page and, hopefully, that issue can be resolved. I came in to make sure that we can harden our security infrastructure, especially when it comes to VMware. And one of the things that I learned recently was that there are so many documents that we don't have access to regarding the use of VMware. My technical account manager promised me that the documentation will be provided to whomever needs access to it.

I don't think downtime is a problem. However, stability is still in question because I don't think we have tested it to the core. We have not rolled it out to as many people as we wish we could. But so far, for the few that we have rolled it out to, performance and stability are acceptable to management.

We can see that it is scalable, but once again we're not there yet. We need to do more testing to confirm that it is actually scalable.

I love what we can do with this and I love everything it gives to us.

I rate it a nine out of ten because I don't see users complaining a lot. For what we need, for the most part, we get it. It's not 100 percent, it's not like something we distributed to the whole organization. But I'm sure the CIO will want to do that when we can. 

We used it for our VDI solution to track down all of the network beginning and endpoints.

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.

The most valuable feature for us is that insight into what our network is really doing - it's a fairly complex network. Not having to go through thousands of lines of network configuration to find firewall ports that were open or closed, for various ports, was very valuable.

It went out and found everything we need very quickly. It did everything we needed it to do.

After you use it for a little while you become accustomed to it but the layout doesn't feel very intuitive. You have to dig around and find the exact place where you can find the information, where you can actually see your east-west traffic, etc. 

I would like them to bring that information more to the forefront, instead of having to find it.

Once you have learned how to use everything, it becomes easy to use.

It was very stable. In bringing it up we did not have any issues.

I have not been able to get an accurate impression of the scalability. We only use it across one network. It's a large network, so it seems to have scaled for that. I don't know how it would scale for something even larger than what we have currently.

We actually had a technician on site. He was very quickly able to get with the other levels of technical support to get answers for us to any questions he was not able to answer.

We ended up going with VMware and a VDI solution and this product was a recommendation alongside of that. We looked at it and it looked like it would do the job.

The initial setup was very easy to do. But we did have the technician there, walking us through the whole process. He was familiar with it. But it was not that difficult of a setup.

We have not had the opportunity to upgrade to a newer version.

It prevented us from having to spend about $5,000,000 on new desktops and laptops. It cut that down to about a quarter of that price.

Because it looked like it would do the job, we didn't look at anything else.

I would rate this product an eight out of 10. I might give it a higher rating if we used it more. We used it for a period of time and then we stopped using it. There was nothing wrong with it, we just didn't use it enough to see it as a 10 out of 10.

The most important criterion when selecting a vendor is finding one who will actually give what is promised.

I use the solution for virtualization and monitoring purposes.

The reports, insights, and add-ons where it's monitoring at a specific time on daily reports. For example, it shows when we can use customized reports at any time for any request raised.

It just needs to be more reliable and more accurate. At some point, there are some things where it does not match properly. I guess they have released the newer version of the solution, but I have not tried it yet.

I guess it's an old solution I am using. However, It seems fine for the time being. But if you allow me some time to test an issue from the newest version, I guess it could be good for me.

I have been using vRealize Network Insight for four years. I am a customer of vRealize Network Insight.

I believe that a couple of years ago, I contacted technical support due to some issues with vRealize Network Insight, and it was resolved immediately. Technical support was helpful.

The initial setup was straightforward.

All VMware products are expensive. So, vRealize Network Insight is expensive.

We need other metrics that could be useful for monitoring purposes. So, we need a solution with parameters and metrics. Overall, I rate the solution a nine out of ten.

For this product, we wanted to introduce NSX into our environment. Previously, we were using all Cisco, so we wanted to try Network Insight to find the vulnerabilities in our environment and whether our environment was compatible with NSX. That was the premier objective in using this product.

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 gives us the workflow. If we deploy NSX it shows us how the workflow will flow in the organization, what the roadblocks are, and what we need to do to overcome those hurdles. When we run this product, it gives us reports which describe problems with physical switches. We work with the network team to get them all resolved.

It's very intuitive. The GUI is very effective. It's a very good product, it's very easy to explore.

Log Insight from VMware is similar to what Network Insight does. If it had some kind of plugins with vSphere, more effective plugins with Horizon View or other VMWare products, if it had interconnectivity, I think it would be more effective than it is today.

It's stable.

We can add more appliances. It's easily scalable.

Initially, we had to use a lot of technical support because nobody had much expertise. But eventually, we developed expertise. We had to call support to get things done. Now, if there are any complex issues, we get into support calls.

We have upgraded it, we applied one patch. It was easy because it's appliance-based, so we just got the pack and uploaded it.

We have ROI data, but it's confidential so I cannot disclose it. But overall, we have had a very good experience. We have had a good return on investment on this. It's a very good product.

Cost-wise it's reasonable, maybe because we have all VMware products under one umbrella, so they have given us a good discount. But overall, it's very efficient and rich in features.

We considered Cisco and we considered some other small vendors, as well as Palo Alto. But eventually, because we are a VMware shop and our entire team was working with VMware, we went with this product.

I rate it a nine out of ten. I'm a little bit skeptical, I never give a ten. But otherwise, in the next release, if they made it more intuitive - it's definitely intuitive - but if there were some more features and it let us know about east-west traffic as well, that would be more helpful.