SolarWinds ipMonitor vs vRealize Network Insight comparison

"The most valuable feature is the availability of end devices."

"IPAM is used for IP address reservation and tracking, helping us easily identify live IP addresses."

"The initial setup is very straightforward and it is easy to add nodes."

"IPAM is used for IP address reservation and tracking, helping us easily identify live IP addresses."

"The most valuable feature is the visualization, as it is really handy to be able to classify network objects with applications and see the interaction between them."

"If you are going to implement NSX, it's a great tool."

"The most valuable feature is the profiling of the applications for micro-segmentation... 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."

"We get proper reporting on different aspects such as utilization and health monitoring reports, including throughput details and network latency, and there are many things we can obtain from there."

"We're a smaller company so 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, and 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."

"The solution helps reduce time to value, increase performance, provide deep visibility, and easily manage networks."

"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."

"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 solution does not include enough features and has some performance issues."

"The licensing cost is high compared to open source tools."

"The licensing cost is high compared to open source tools."

"The solution does not include enough features and has some performance issues."

"In terms of room for improvement, customer education is number one."

"I would like to see more interoperability on the firewall and low balancer sides."

"vRNI needs more remediation where it hooks into NSX."

"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."

"I rate it a seven out of ten, only because it doesn't have all the vendors - at least the switch vendors - in there."

"I would like to see more reporting features, more dashboards."

"Support could be much better. They do not do a good job of finding issues."

"I want to see more in terms of microsegmentation. As of now, I can see the rules, but they are not in a readable format that I can convert to microsegmentation and can fit into NSX Manager."

"The solution is a bit expensive because the annual license does not include new features that are priced as add-ons."

"I rate vRealize Network Insight's pricing a seven point five out of ten."

"Cost always has room for improvement, you could always make it cheaper. But I think it's a good value for what you pay for it."

"The solution has helped us to reduce time, increase performance, reduce costs, and even easily manage networks. We are probably seeing 10 to 20 percent labor savings because we are able to be very specific and focused on what we want to do. It ends up saving the customer money and makes us be more efficient on our cost deliveries."

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

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

"The solution has reduced the time that we spend on other products. For example, with NSX, we were able to quickly find things that we would normally spend days trying to figure out."

"It's a little expensive, but for what you're getting out of the product, you often see the trade-off. It depends on the type of licensing you have. It might be a little too pricey for some."

"We have spent less time investigating network flows, so it is absolutely cost-effective."