What is our primary use case?
We use it as our network management tool and configuration backup utility.
How has it helped my organization?
It's made us a lot more aware of the network side. A lot of MSPs traditionally have been more server/workstation oriented, with some firewall-related activities, but when you bring in the network, it allows you to bring all that full circle and troubleshoot network issues more easily. And in the same way that a backup is important for a server, a backup is important for a switch or a firewall. If you lose one of those, you don't want to have to rebuild from scratch. Auvik provides that configuration backup.
The configuration backup has helped reduce repetitive tasks. With network, there's not as much daily touch as there is with PCs. The automation has primarily been around backing up devices and alerting on down devices.
It has also helped with visibility into remote distributed networks. As an MSP, most of our customers are remote networks for us. Auvik allows us to manage their networks, whether they're local or in the UK or anywhere else. We're able to manage those networks much better via this tool. It helps our network engineers focus on those networks.
In addition, it helps keep device inventories up to date. That aspect helps a lot because people don't have to always worry about whether somebody added a switch or an access point. It scans each day and sees new devices. While that doesn't save us time on a recurring basis, whenever we need to provide a report, we don't have to manually gather the information. We're able to print it out and provide it, rather than having to do manual counts. But that's on-demand and not frequent.
We have absolutely seen a reduction in our mean time to resolution for network issues, using Auvik. For instance, if an alert comes through that a server is down, and we're also getting information that a switch or a firewall is down as part of that, we immediately know we don't need to troubleshoot the server. The server is down because those network devices are down. It allows us to get right to where the problem is, versus having to work our way back and that cuts out a lot of troubleshooting time.
If we get an alert that an AP is down and a firewall is also down, it may just be that the AP is not able to report back because the firewall is not up to allow it to. That's where it saves us a lot of time. It allows us to look at root cause better. When you're looking at that map and you see three things with red alert banners on them, you know which one is the closest point out to the internet and that you need to look there first, versus what's behind it.
What is most valuable?
The network management piece has been the most advantageous. First, it alerts us about network devices that are under duress or having issues. Second, it has historical data. That allows us to go back, if, for instance, a switch is having problems, and see if it is something that trends at a certain time of the day or a certain day of the week.
For what we use it for, Auvik provides us with a single integrated platform because it ties into their ticketing system. That is very important. The more touchpoints that people have to interact with, the less likely they are to interact. Trying to get it down to as few panes of glass as possible becomes an important piece. We previously used multiple applications for managing our network, and switching to Auvik has saved our organization a good bit of time, day-to-day. It has saved us the equivalent of half an FTE.
It's also the best that we have found for helping to visualize network mapping/topology. It does a great job of that, hands-down. The mechanism that it uses to learn about the network seems to be more robust than some of the others. The interface is very clean and sleek. It discovers devices well and the relationships between them, and the general aesthetic of the portal presents that information. It gathers more data than most and it presents it wrapped up in a really pretty way. Others can draw out a diagram, but they're just not as elegant as Auvik.
The network visualization is intuitive. It classifies devices accurately and presents the links and the relationships well. Plus, if something isn't discovered the way you think it should be, it gives you the ability to manually adjust it. For example, sometimes wireless bridges don't really present well. They don't show a link between them. You have the ability to go in and make that association manually so that it presents correctly on the map.
For how long have I used the solution?
I've been using Auvik for a little over three years.
What do I think about the stability of the solution?
The stability is strong. They announce maintenance well in advance and it's not frequent. We haven't had many issues. I don't recall that it just went down all of a sudden. Typically, it's only down around maintenance windows.
What do I think about the scalability of the solution?
It scales well. We've put large networks on it.
How are customer service and support?
The solution's technical support is good. We didn't have to interact with it a lot, but when we did, they were able to answer the questions.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
We used PRTG from a German company called Paessler, but it did not provide configuration backup, so we used a different application to provide the configuration backup. We had to use two products to do that function before. That was part of the reason we switched to Auvik. Bringing everything into one application, and that application being able to integrate with our ticketing system, were the two big reasons.
How was the initial setup?
The initial setup was very straightforward. If you have intermediate networking skills you will be comfortable doing it.
We were able to implement Auvik out-of-the-box, meaning it was immediately available for use without intervention. When we signed up, we were able to download the agents to put on each remote site and begin scanning and gathering data. Once we decided to go with Auvik, we were instantly able to go with it. Within 15 minutes, after the Auvik code was implemented, our network mapping began to populate.
Within about an hour or two, depending on the size of the network, the map was pretty well displayed. For larger networks—we have some networks that are 1,000 nodes—it might take several hours for it to scan, discover, and learn the relationships. It asks you to authorize networks that it finds. You may initially tell it to scan a network, but based on that network being scanned and the devices on it, it learns that there are other subnets out there. You have to approve those for it to scan them as well. That's why larger networks could take several hours and up to a day or so.
What about the implementation team?
We did it all in-house and it required three people. They were primarily split up between
- networking components: switchers, routers, and wireless infrastructure
- server/workstation infrastructure
- integrations, such as ticketing.
What was our ROI?
Auvik helps us, but as I mentioned, it's a lot more for point-in-time needs. If a switch is down and we need to get information on the alert and possibly pull the backup to put on a replacement device, or if somebody needs an inventory, we can pull a report. Those are very moment-oriented.
I can't talk about time-to-value over days, months, or years, but once you set it up, it takes care of itself. It scans the network for new devices. Once you stand the product up and have it connected to your ticketing system, it's just a matter of using it when you need to use it.
What's my experience with pricing, setup cost, and licensing?
Auvik is not cheap. They've done a great job, it's a developed product, but you pay for it. When you compare, it's definitely in the upper tier of pricing.
Auvik has two price points. One is their Essentials license, and the other is their Performance license which includes flow data.
For example, you may have a network with 10 switches and a firewall, and you really only want flow data going through the firewall. Auvik requires you not only to put the device you want under a Performance license, but all of the other network devices that are billable devices have to go to that same Performance license. It gets expensive in a hurry, so we haven't taken a Performance license with them for that main reason. If we need to do flow data, we'll use a different product. I wish they allowed you to only license the devices you needed to have Performance.
Which other solutions did I evaluate?
We looked at Traverse Network from Kaseya. It was very similar to Auvik in terms of capabilities, but we thought Auvik was more polished. It seemed to be further down the road as far as how well it had been implemented.
And Auvik's cloud-based solution, when compared with on-prem network monitoring solutions, is better. It's hard to monitor something on the network locally because if you lose your internet connection, it can't report out, which is pretty important. That's why we like it more than on-premises solutions.
What other advice do I have?
It's an easy user interface to work with. They've done a good job with the GUI and how to navigate it. That's not of huge importance to us because a lot of us have been doing network management for close to two decades. That means we've used a lot of tools and we are very familiar with them. But for entry-level techs, it's easier because they can do some things without knowing a lot of what we've had two decades to learn. It makes people with less experience much more comfortable using it.
The solution's automation hasn't had that much of an impact because a lot of our frontline people don't have to interact with it on a daily basis. They use it for point-in-time troubleshooting. It's not a huge help on that side. It's mainly the networking engineers, who would have to do things through other systems manually, whose time is saved.
From a product perspective, it's a 10 out of 10. It's just that you pay for the product. It costs a lot compared to others.
The biggest issue is that if you need NetFlow, where you can actually see more information about the packets that are traversing the network, you probably need to work through your cost model first. Auvik is not going to be the cheapest out there, not even close. It's going to be, by far, the more expensive solution. If that is a strong need of yours, it may not be the best solution. It does NetFlow really well, just like everything else it does. It presents it well. But the pricing model makes it a very expensive proposition to do the Performance licenses.
Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.