Fortra's Intermapper vs vRealize Network Insight comparison

"It's a nice graphical interface, a nice map, that relates Layer 1 to Layer 3, virtually instantly, to the Helpdesk support staff. It provides a default place to get critical information so we can deploy our staff."

"It's all today portal-based which is a good feature for us."

"The most valuable features are its: log history, real-time monitoring capabilities, accuracy - the number of false positives is very low, and the mapping features."

"What is really cool about HelpSystems InterMapper is that because of its SNMP base, you can integrate all different makes and models on the same map. You, of course, can have more than one map, but you have an option to have visibility into the entire network from one centralized system. You can monitor IPs, routers, radios, DC power plants, and UPS. You can do it all from one network management and monitoring solution. That's what really makes HelpSystems Intermapper great. Another great thing about HelpSystems InterMapper is that you can really bundle different probes under one device. You can have a bundled device. You can monitor the physical status of a host based on the IP availability. You can also monitor services and actually see if anything happens. You can quickly determine whether it is the application layer, host layer, or network layer. HelpSystems Intermapper gives such a unique representation of a network. Ever since we started using HelpSystems InterMapper, we don't have to document everything in a detailed format and store it somewhere. Right now, it is really a combination of network topology, network monitoring, and network analyzing. So, in my opinion, it is awesome. When you have your SNMP topology defined, you don't require a dedicated NMS engineer to manage your system, which is another great thing about HelpSystems InterMapper. I see how our operators get so excited by having the ability to map a device or interface and connect interfaces together. HelpSystems InterMapper is also very operator friendly; not just user friendly, but also operator friendly. This is a unique feature, and it works really great."

"The gradual way the Network Insight shows you all the relevant information about your networks. It's pretty good. You can really dig deep deep inside and see where the problem is, where it comes from, what you have inside, how did you configure it. Also, it has alerts so you can have pretty much quite a big overview about your network. This is really something good."

"It is user-friendly. It's pretty simple to deploy and to run. It gives you pretty easy-to-understand reports, very graphically intense, so you can visualize what's going on in your network."

"It's 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, so that helps. The first day you're in there you can start building actual queries."

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

"We haven't had any complaints about the stability of the solution or heard of any issues. None of our clients have mentioned running into bugs or glitches. There haven't been crashes."

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

"What's valuable to us is the ability to get a view into the virtual space, which is something we haven't had before. Before, it was done by collecting from network endpoints and extrapolating into the virtual environment. Now it's coming directly from the virtual environment."

"It allows you to see traffic that you couldn't otherwise see, which is traffic within your Layer 3-bounded network, meaning east-west traffic. It's hard to get that any other way."

"I'd love to see more of the network management side of it coming back into it. If we were able to run scripts to bounce ports on switches, that would be great. It's asking a lot, but it's actually very doable because I do it through scripting into other products. If we could incorporate that directly into Intermapper, that would be fantastic."

"They can do a better job with SLA reporting. It does some basic reporting, but it really doesn't offer the ability to monitor devices by groups, customers, or carrier to give an overall health performance of specifically-defined environments. That's where HelpSystems Intermapper could have done a better job. I would love to see advanced SLA monitoring and reporting in this solution. They already have a lot of ingredients. They already have SNMP polling. It is really about what people are looking for from SLA monitoring, especially someone who looks at the network topology. You want to see your endpoints. You want to see half of your endpoints by simply analyzing ICMP or SNMP-based availability of your endpoints. Having an ability to define your group and how you bring devices into your group would be a huge benefit."

"It's a smaller solution so tools are not as advanced as you would find in a larger solution"

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

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

"The solution can be improved by making it more compatible with other brands, allowing for better integration."

"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'd like to see better support for being able to search the hardware NetFlow data. It ingests fairly well, but you can't tell, in a lot of cases, what source the data came from. I'd like to see more support for picking specific sources. That way you could really make a compelling use case. There are also some difficulties where it can't exactly trace the path between source and destination but if you hit the reverse flow on the same search it shows the entire path."

"There is room for improvement as not all cases are getting resolved, and we often do not get L3 support directly, having to go through L1 and L2, resulting in delays that usually are a headache for us."

"After Broadcom acquired VMware, I would rate their support at five or less in many cases. It's difficult to find necessary documentation, open tickets, and get support."

"While it's not exactly a feature, what normally happens when we are trying to look at the VM flow portion is - although Network Insight does have options to integrate a few physical switches into it - we can't really get an end-to-end flow of the network. We might be using a few switches that are not supported by Network Insight. That is where they can improve, in the support for more physical switches and network devices."

"It reduces costs. It takes something that may be challenging and makes it more usable and visual by being able to bring in tools, seeing what their impact is, such as microsegmentation and application rationalization, and seeing it quickly."

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

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

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

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

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

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

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