Auvik Network Management (ANM) Reviews

We used it for network monitoring and network health. We had it deployed at all of our sites. We are an MSP, and we've got about 30 different managed clients. All of them had an Auvik collector at each site to monitor the network for changes or infrastructure health. We have an RMM solution for remote monitoring and management of our workstations and servers, but that tool doesn't monitor network infrastructure. 

Its monitoring and management functions are very easy to use. With some of the other solutions, their built-in database of OID markers isn't great, and you need to manage all of your own MIBs. With a lot of competitors, if a device isn't in its catalog, we need to go and add it to the catalog ourselves, which is a big challenge, whereas Auvik has a phenomenal database behind it, and it is generic, which is another benefit of Auvik. It's not vendor dependent. So, whether you're using Cisco switches, Ubiquiti switches, NetGear switches, TP-Link devices, Hyper-V or VMware, FortiGate firewalls, or Barracuda firewalls, Auvik typically supports them. It has very broad support.

Its integrations are exceptional. The multitenancy in it is also phenomenal. It's very easy to jump from one client to another while also keeping those clients separate. So, if you have someone who is only managing a couple of sites, that's all they can see. They can't see everything else, but someone with a little bit more access can see all of the sites. Being an MSP, we have a lot of different sites that we're accessing. When we have a co-managed environment, a tech for client A can go in and see all the information relating to client A, but they won't be able to see anything for client B.

The time that it has saved is almost impossible to measure. For example, we had a client, and their firewall had failed. We picked up a new firewall. We were going to go set it up, but the last backup that we had on the client's server was from a year and a half prior. It was well out of date, and it was missing a lot of the recent changes. With Auvik, we were able to go in and download the latest backup and restore it instantly. It has saved all those hours that we would have spent troubleshooting or finding missing rules, as well as the management time of having a tech periodically go in and do all of those backups. Because the whole system is automated, it's very hard to measure how much time we saved, but it is a lot of time.

It is the best in class for visualizing the network mapping/topology of the organizations we were monitoring. It is extremely intuitive. One of the big things is everything is all color-coded. So, whether a connection is layer one or layer three, it is very easily highlighted with a blue line versus a gray line. If it is wired versus wireless, there is a solid line versus a dotted line. All of the device types have their own category associated with them. So, if you're looking for a firewall, you just look for the red dot, and you can pick that up pretty easily. If you're looking for a switch, you look for the orange dot. Finding devices on it is very intuitive.

They also had a great feature of being able to collapse and group some of the devices. If you had ten security cameras connected to one switch, rather than having ten little black dots on it, it was able to group them into one item saying security cameras, and you can click on it and expand. It's something that I didn't think about that much when I was using the product because it seemed normal and intuitive. Moving away to a different product that doesn't have the same mapping level or the same features has made the switch a little bit more difficult. You can still get there at the end of the day where you can find the devices, but it is just not as easy.

It was absolutely helpful in reducing repetitive, low-priority tasks through automation. That goes back to things like backups. The fact that it would automatically go through and do the backups, and we didn't need to spend the time to go through and check that was phenomenal. The remote internet connection checks were very useful. ISPs can be very difficult to work with when you're trying to discuss service or packet loss or interruptions. Rather than telling the ISP " We're experiencing this issue," the reports coming out of Auvik gave us a great ability to go to the ISP and say, "Hey, here's some more data. We're dropping packets at such and such rate." Auvik gives you historical benchmarks and reports, and because we already have got the history of it, to troubleshoot, the ISP doesn't have to start gathering reports from that point.

If you have a client that has two locations and a data center, Auvik can group all of those collectors into one client, and you can have a larger view of all three locations and how they interact with each other in one overarching network map, whereas Domotz splits it into three separate locations. Domotz is great in the sense that you get one flat rate per site, but what it won't do is that it won't integrate those sites together. They would be three separate agents that need monitoring within Domotz.

The remote access feature was very useful. If a client's server was offline, we didn't need to VPN in or go to the site to turn on the servers. Auvik gave us the ability to turn on the server remotely without having to go anywhere. It saved us time on that side of things. Over the four years that we were working with it, on average, it has saved us about 150 hours.

Auvik has a phenomenal granular access model where you can even make your own custom role. If you have a co-op student and you want them to only have read access, that's easy to set up. If there is a more experienced person, but they're only allowed certain sites, it is very easy to restrict their access.

Auvik's SSO integration is one of the best I've ever seen. When we were first adopting SSO, Auvik was the first vendor we integrated it with because Auvik was able to get SSO set up where it's one per user or per tech. It's not a big bang migration, and you can have a trial with a couple of techs first, and if it works, roll it out to more.

We had integrated Auvik into ITGlue. When we're onboarding a new client, rather than having to manually add each device into ITGlue, after Auvik has scanned the network and picked up all the devices, we can import all the devices from there. From an accuracy standpoint, being able to import devices saved us from the manual entry and saved us from user errors, such as mistyping a map address or something else.

It definitely reduced the mean time to resolution. The spanning-tree notifications from it were helpful. We've had a couple of instances where a client found a cable that they thought was just loose, and they were being helpful by plugging it in somewhere, which created a loop on the switch. We got to know about it from Auvik. We knew which port it was plugged into and what the solution was to fix it instantly. It reduced our mean time to resolution to about a quarter of the time. We were able to fix things that would've taken an hour to resolve in 10-15 minutes.

Auvik is phenomenal for network monitoring as well as for other functionalities such as remote access or backups. A really cool feature that it has is that it takes a backup of all of the configurations automatically. Auvik periodically, most probably on a daily basis, logs into all the switches and firewalls that you have on-site to see if there is a change, and when there is a change, it does a new backup of the device. It logs changes for you. If you start experiencing some issues, you can go back to those logs to say, "Oh, there is a change made last week, Thursday," and with Auvik, you can just roll back to that snapshot nicely and quickly.

Its UI is really intuitive. It's really easy to get a hold of it. It's very easy for non-technical people to understand. One of our problems with some of the competitors is that they've got a fairly grayscale UI. It sounds very pedantic, but the color scheme of Auvik made identifying which devices were which and how they were connected to each other easy. It was a very useful feature that is underrated. 

Another feature that worked really well for us was the remote access tool. If we needed to log into one of the network devices, we didn't have to jump on a server, workstation, or local device, or connect through a VPN. Auvik was able to give us direct UI access to any device on the network.

It is amazing in keeping device inventories up-to-date. It mostly keeps them up to date as things change. There were a couple of hiccups where a device would get replaced and the mapping would break, and we'd have to go in and fix the mapping. It was with devices that Auvik couldn't fully discover or devices that would change frequently, such as cell phones or other devices on the network that are dynamic and change all the time. The integration would just show up with an IP address and a MAC address. There was no other information in them, which wasn't very helpful. They were the devices that Auvik wasn't able to discover fully. If they had full SNMP or SSH credentials and Auvik knew what the device was and it was matched correctly in Auvik, then Auvik could push it through.

It is not at all cheap. We migrated to Domotz because of its pricing.

We used it for about four years, and we just migrated away from it.

It was probably one of the best ever. I went to school with three other guys. When we graduated, three of them went to work for Auvik support. Full props to the support team. They are phenomenal. I would rate them an eight out of ten. There's always room for improvement. I do wish that they had more open-source pfSense support. There were a couple of things that I was hoping would come out as features but they didn't.

Positive

We didn't have a solution in place. Auvik was our initial solution, but now, we have migrated away from it to Domotz because of pricing. What really triggered it for us was that our firewall of choice is pfSense, which is open source. Auvik, by default, would categorize pfSense as a Linux server, which is essentially what it is. We would then manually categorize it as a firewall. Firewalls are on the list of billable devices for Auvik. However, we weren't being billed for them because Auvik was originally categorizing them as Linux servers. When we were onboarding the product, we mentioned this to our account manager, and we told him that none of our firewalls are being categorized as billable devices. The account manager at the time said that it was a bank error in our favor, and because they were not able to categorize it properly, they were not going to bill us for those devices.

We then costed out our offering with it and had that set with all of our clients. Recently, Auvik was able to fix that bank error, which essentially doubled all of our prices. This makes for a very hard conversation to go to clients and say that we need to double our prices to them because our vendor has doubled our prices. That was a challenge. 

I'm okay if you're going to double our prices, but the support for pfSense, for which they weren't billing us before, is fairly limited. With most of the firewalls, if you have site-to-site VPNs, they show up on the network map as a site-to-site VPN or remote access VPN. Auvik will monitor the usage on those to say, "You have 10 remote access connections, and everything is okay, or you're up to 50 people connecting remotely, and you're starting to get degraded service." All of these additional firewall monitoring features weren't available on pfSense, which was fine because they weren't billing us for it. Now that they wanted to start billing us for these devices, I had asked them if we were going to get support for all of these additional features. They said no because they are not looking to expand their pfSense development. That was frustrating. So, it basically came down to whether we double our costs and pass that onto all of our clients, or whether we look for an alternative, such as Domotz, that doesn't have as many features and is not as pretty in a sense, but it halves our cost. So, we ended up halving our costs instead of doubling them.

As part of onboarding, we got talking with some of the Domotz dev team, and all of the features that were missing have been added as feature requests. We're working with their engineering team to implement some of the features that are not quite there yet.

It was significantly easier than onboarding Domotz. Virtually, every alert or trigger that we could have wanted was built in by default. We didn't have to set up custom alerts, custom triggers, or their base alerting standards. In fact, if anything, it was too much. We had to turn off some of the alerts that were misfiring or not a hundred percent accurate, but there was nothing that we wanted that we couldn't get out of the box.

Its setup was easier. Everything was a lot easier. Even onboarding of new devices was easier. Auvik would identify them a lot easier. Our current solution is a lot more finicky and has more manual elements to it. It's definitely something that Auvik was better at.

Its time-to-value is instant. Before we even onboarded the product, we could see the value in it just from the demo.

Auvik is definitely one of the more expensive platforms. It is not cheap at all. If cost is an issue, Auvik isn't on the table at all, but they do have a fantastic solution for the cost. If budget isn't a concern, they are probably the market leader.

We migrated away from it to a competitor called Domotz because of pricing. Auvik bills per what they call a billable device, which is a firewall, a switch, and a controller. All of those count as billable devices. Domotz, as an alternative, bills per site. It's a flat fee for the whole site. So, whether you've got 3 switches or 10 switches, it's the same cost.

Auvik's premium product has a couple of other features with regard to NetFlow and some of the traffic analysis on that side. They've also got Syslog now in their premium product. However, we found their premium product to be fairly expensive. The whole product is very expensive, even for their standard offering. So, to bump up to premium, it's a lot more expensive. We trialed it for a bit. It was very useful but not worth the extra cost.

In terms of comparing Auvik’s cloud-based solution versus on-prem network monitoring solutions, it is a tricky balance because while the Auvik database and the backend are all cloud-based, you still have an on-premise collector doing some of the management for you. The management of it is cloud-based, but there is an on-premise component to it. There are some alternatives, such as PRTG or Zabbix. They're all on-premise alternatives, but they are very much a pain to manage, particularly when you have multiple sites and multiple clients. Having the backend cloud-based is very useful. However, that's a feature that they share with Domotz. Domotz is cloud-based in the same way.

Overall, I'd give Auvik a seven out of ten. Tech-wise, it's a ten, but its pricing is a very big barrier to adoption.

Our use cases would be mapping our network automatically, monitoring events to get stats and trends, spotting any impending issues before they get noticed by our users so we can address them, and doing device reconfiguration. 

Auvik automatically updates network topology. Our network team members in our operations all dig it. It is just something that makes finding devices easy, e.g., if you don't necessarily remember where it is, the IP, and so on. Especially if something needs to be reconfigured, it makes it really easy to go to the LAN or network in question, find the device, remotely get into it, and then make whatever necessary changes.

The goal is to have Auvik help us put out fires before people or end users even know that there is a problem. That hasn't really happened that much, other than power outages where we can get somebody en route, which makes us look like we know what we are doing.

It is kind of a toss up between its nice interface and ease of deployment. 

It is pretty easy to use for the type of product that it is and what its use case is. Anyone who is going to use such a thing generally should have a fair bit of knowledge about networking, devices, etc. 

Auvik is excellent when it comes to its network discovery capabilities. It has good stats. We can look at our network and visually see what is going on, if there are any issues, and just the entire topography of how it is laid out. It generates the network map automatically, so that is not something we have to go do. It just lets you see things, maybe not necessarily at a glance, but close to it. 

We were able to trim down and get a decent signal-to-noise ratio on notifications and events, because these devices generate a ton of telemetry. Otherwise, it's like things are always crying, "Wolf!" That has been a problem, not just in this niche, but other categories as well. If you get too much stuff that isn't anything to look at, then you will quit looking at it.

The automation of the network mapping enables junior network specialists to resolve issues directly, freeing up senior-level team members to perform higher-value tasks. They can see if it is something as simple as a power issue in a wing of a building. This lets them pick the low hanging fruit. Then, if a configuration needs a more skilled person, they can easily escalate it.

There are a couple things that you need to do, and then Auvik provides automated, out-of-the-box device configuration backups. It backs up the configurations, and that has been awesome, which makes it possible and practical. Otherwise, it is really difficult because we would then have to go from device to device, get it to spit out its config, copy it to the clipboard, paste it to a file, and organize it all. That is all now automatic, which is great.

Generally, once stuff gets configured, it is fine. Previously, it was a matter of remembering to get the copy of the config and save it someplace. Depending upon the workload, sometimes that got put on the back burner. Now, because of this solution's automatic, out-of-the-box device configurations, I don't worry about it.

I would like firmware/software updates for hardware, for at least switches and routers. I already have the feature request in, and it is on their list of things to try and do. Cisco stuff has been notoriously and historically kind of a pain to do, and that is what we use primarily. So, that would be a wonderful thing to get, as it is a device-by-device process. It would be nice to be able to get through that at least in a less fiddly way. It is a pretty manual process now.

We have been using it for a little less than a year.

It is very stable. We have had one very minor incident with logins. They had that resolved in 15 minutes to half an hour, tops.

There is almost no maintenance required from our staff. Compared with other solutions that I have used, the level of maintenance affecting my operations is much better with Auvik. I feel like I can trust it a little more than some of the things that I configured myself. I just never had the time to polish those other solutions out the way that they really needed to be done.

I haven't run into any issues with it. I suspect it could handle multiples of more devices than we have in our network. It doesn't seem to break a sweat. Hopefully, they have enough scalability on their end that it won't impact us unless other customer stuff impacts us.

The technical support has been great.

We have used different open source things, like Nagios, but they were just so configuration heavy. We basically got rid of them. We didn't have anything in a while prior to getting this solution, but now we have Auvik. I do kind of miss having that early warning system, but I just didn't have the time to configure anything, because that is a very non-trivial thing for a lot of those systems. Having sufficient time to be able to spend on it, that was really the problem. This alleviated that completely.

I happened to run across an ad somewhere, and it's like, "Hey, I want to look at that. If this solution is half as good as it claims to be, this might be for us," and if it was at a reasonable cost.

The deployment was very simple. The network discovery accuracy was great. Other systems like this that I have worked with required a lot of configuration. This did not take much effort at all. The initial deployment was quick. We had something kind of up and running in an hour, if that long.

Auvik has decreased our mean time to resolution. Luckily, we have a pretty stable network; we don't have a lot of issues. However, it can be trivial to just get to a device. For example, if we have to change a port setting or something on a switch from a printer to a phone or VLAN assignments, it is now quick and easy. Assuming everything goes well once you get to the device, it probably cuts the, "What was that device IP?" thing down by 80%.

We have saved more in time and efficiency than any hard monetary savings.

It took us just a few days to get a return on value from the whole implementation.

The pricing is by device. We have 75 devices, which is a little more than we really need. With school and volume discounts, it is still a little over $16,000 annually. Our WiFi access points are not being billed, but all our switches and routers are. 

Usually, I'm cheap. We are a school so I have to be cheap. Therefore, when there is an open source solution, I am usually reluctant to look at commercial things. Now, with a little more leadership support as well as technology becoming more mission-critical than ever before, it is part of the deliverable to produce an educated student. So, they are willing to invest more. It wasn't crazy expensive, but in the past, it would've been a hard sell. 

In addition to Auvik, I also looked at SolarWinds and HPE OneView, which was breathtakingly expensive. We mostly went with Auvik because of its ease of use for non-technical people. The ease of its configuration and deployment was big. Those were huge factors. We have added so much technology of all sorts in the last year or two that mental bandwidth has become an issue. For example, how much time can I even hope to spend on a given project, which might suffer greatly from mental interruptions.

This solution has stopped me from looking at other stuff. 

I don't want to really add any more complexity to our environment, but if we do, it'll get picked up and mapped automatically. So, once we get the device online and configured, it will just show up.

Auvik has been really handy. I really can't say enough good things about it. I have just been really impressed with the quality of the product, support, and training. It just works well.

I see a lot of value in Auvik. I was really happy with it very early on. I would rate this solution as 10 out of 10. I can't say enough good things about this solution.

We're in the healthcare industry and in our organization we have what we call a "backup machine" to be used in emergency scenarios. Should there be a brownout or internet service provider disruptions or any major catastrophe, we can move digital charting to paper charting for a certain duration of time. We have the Auvik probe installed on those backup machines, and it sends feedback back to the main Auvik dashboard where we monitor such things as ISP latency, devices on the network, and certain network elements like switches and access points.

We also have a probe sitting in one of the servers in the data center and it performs a similar function, helping us review our network infrastructure within the data center and to see where potential bottlenecks are, at what times of day, and to analyze trends.

We use it for basic troubleshooting as well because you can see everything on the network within a particular facility. At sites that don't have Cisco Meraki within the building, we use Auvik to isolate which ports' devices are connected to and for general troubleshooting. If, for example, an uplink port on one of the switches goes out, we can see, "Oh, that was port 26. Please switch it to port 25." We can duplicate configurations from one port to the next port and make sure that the facility is up and online.

It's been a very useful tool for us.

We can automate alerting systems based on certain criteria. For example, if a switch is undergoing high CPU usage or access points show high CPU or memory usage, we'll get the alerts for those and address them accordingly.

Auvik also sends us a text message whenever one of the internet circuits goes down, as we have a main fibre circuit at every building and a coaxial backup. That helps us ease the burden in switching over the necessary connections or the tunnels back to our centralized data center.

In addition, the network discovery capabilities are very insightful, coming from our previous situation where we had absolutely nothing. They have made us aware of certain switches within certain parts of the building that we may not have known existed. They have also helped because in our industry we're built by acquisitions. Oftentimes, we find an acquisition has an IDF and MDF in a particular building. With Auvik installed, we might find there are two more switches around that building. Sometimes these switches can be in the ceiling, but even being able to isolate what port they're connected to, disconnecting them, and finding where these items are has been extraordinarily helpful to us.

The solution has ultimately improved the response time of our help desk team when troubleshooting issues. It has also helped to identify older equipment when doing a refresh. We've been able to find 100-meg switches and old Cisco switches that are in places that we didn't anticipate they would be. We have also been able to isolate key pieces of the infrastructure within a building, pieces that needed to be replaced to provide a more friendly user experience.

Another benefit is that the automation of network mapping enables our level-one network specialists to resolve issues directly, and frees up senior-level team members for more important tasks. Our level-ones have read-only access, but that allows them to see the different topologies, see where things are connected, and then help facilitate a solution, either remotely or with the help of onsite personnel. It's kind of like having Cisco Meraki insight without actually having Cisco Meraki. While we only use Cisco Meraki gear at our HQ location, which provides us a high level of insight within one portal, Cisco Meraki is fairly expensive and it's not something that we can afford to put into every building. Auvik provides us with all the features that Cisco Meraki might have to offer within one pane of glass. 

The solution also automatically updates network topology, although it requires SNMP to be enabled on a particular network device. So when we're provisioning things that are going out, we have to pre-program that information into the switch and make sure everything is compatible. But once it's in place, it provides us the same level of insight that the previous network device did.

Also, in the cases where we've used it for resolving issues, it has reduced our MTTR. We're using it more as an insight tool. We don't have a lot of network-related issues within the environment, but in the instances that we have used it for resolution, it has helped us resolve the issues a lot quicker, on the order of 40 percent quicker.

It helps us to put out fires before end-users even know there is a problem, especially when it comes to internet service provider latency on a particular circuit. It alerts us to high bandwidth usage or increased latency and allows us to flip the connections from fibre to coax in anticipation, and then dispatch a fiber technician to resolve the issue on the primary line. All that can be done without any user noticing an impact at the facility level.

We use Auvik's TrafficInsights feature in the data center, but not the facility level. TrafficInsights is really the most beneficial within the data center because that's where high bandwidth is going and that's where it's most important to know exactly what's going on at all times. It shows us network bandwidth usage without the need for expensive, in-line traffic decryption, and with the projects that we currently have on our plate, that's incredibly important. We're currently transitioning data centers right now, and being able to isolate what traffic is going where and what's taking up the most bandwidth helps us put in certain traffic shaping rules. If something were to potentially impact at the facility level, we can get ahead of the curve and make the appropriate changes as necessary.

TrafficInsights also helps show where our system is experiencing performance issues, because we're using fibre optics within the data center as the backbone for everything. Whenever we're moving virtual machines, it helps isolate which ports are experiencing the most usage. We correlate the ports that are used to the host machines themselves and determine what virtual machines are reliant on the host that's using the most bandwidth, and we then see what services are impacted from there. TrafficInsights enables us to prepare ourselves to minimize end-user performance impact. We make changes based on what we see through TrafficInsights. It's a useful feature for doing exactly that. It allows us to maintain a steady level of performance within the data center.

There are also the automated, out-of-the-box device configuration backups which have saved me quite a few times. The ability to back up a configuration from a firewall and have it housed in one central location where we can get the backup config and restore it to a new device, should a firewall or a switch blow out, decreases our restore time significantly. We don't have to figure out which rules, traffic shaping, or port-forwarding were on the switch, or what was on the firewall. We confidently know that the backup being pulled from Auvik is the most recent one.

Typically, before we had Auvik, when a firewall went out, it would take us a full day or a day and a half to turn around another firewall, to make sure it would be plug-and-play. With Auvik, that time has been reduced to a few hours. That's what it takes to procure the actual equipment and get it sent out, because we just pull the backup, restore it, and send the equipment out. No one from our networking team is then working, via tickets, to discover what was on the device previously. It's all in one place. If it's local, we have the building up and running within two hours of equipment configuration.

It's hard to say how much the device configuration backup saves us because every scenario is different. But if we're paying someone $45 an hour, instead of 12 hours of their time we're only using four hours of their time.

The alerting feature has been a very key piece for us, especially in the data center because we manage it ourselves. It gives us special insights into how certain projects and migrations are impacting the center of our operations, out in the field. Within the data center, we have an RDS farm that all the users from the facility connect to. Whenever something may be slow, we can look at the alerting and it helps us troubleshoot whether the issue is at the facility level or at an infrastructure level.

Also, the audit logs it provides are very detailed and can be tailored to our needs within the organization for things like management audit logs and user activity. The TrafficInsights have been really helpful.

The deployment of the probe onto a particular device could be improved. That usually requires one of our level-two people to step in from the help desk team. It would be much better if it were a click-and-go deployment. What I would like to see in particular is the ability to download an MSI builder for a probe for a particular building. We would simply double-click and install it onto the machine and have it work. Having to roll through with the entire API key is a little time-consuming.

I have been using Auvik for about two years now.

We've never had issues with it until recently when we started to see a lot more maintenance come up because the dashboard might be unavailable. But its uptime is about 99 percent.

Scalability is dependent on cost because they charge by network elements. In some of the nursing homes we handle, it's very cost-effective because they only have three switches, a firewall, and about 20 access points. But in larger facilities that have three or four IDFs, it becomes a little bit more costly because you have the additional switches and access points.

Since we don't have a lot of networking issues within the building itself, Auvik is being used as a general guidance tool, and to help the level-one help desk technicians troubleshoot a couple of things a little bit quicker, figure out where items are attached, and help the onsite maintenance director swap a cable or something of that manner. Our use of Auvik will be expanded based on acquisitions. If we bring on a new nursing home, we'll configure all the equipment into our network ahead of time and it will be plug-and-go. We'll just pay for the additional licensing for the network devices.

The first couple of times that I tried to get in contact with the tech support, they were very responsive. With every third-party vendor, wait-times can vary, but the tech support has always been good. I have recently noticed a little bit of a slower response time.

One thing that would be nice would be for them to reach out to us once in a while to check in and see how things are going, rather than only being reactive. A little bit more of a proactive approach would help. Outside of that, I haven't had any issues with their support or their customer team.

Overall, I would rate their tech support at nine out of 10.

We used to use OpenNMS for WAN connectivity purposes but with Auvik we were able to replace that. As far as backups go, we used to use an in-house-built solution for automating an SSH protocol into the firewalls and doing manual backups from there. But that took time to maintain. Auvik has consolidated those two things in one place. And the additional features of network insights for an entire facility is something that we didn't previously have. Auvik is saving us $3,000 to $4,000 per year in licensing costs.

The initial setup was pretty straightforward. From start to finish, it took us about five days to have the entire environment up and running. We're a fairly small team. For organizations that have more dedicated team members, such as a NOC team and a server team, it would probably be a lot faster. But we were all filling in for those roles.

Our implementation strategy was simply to make sure that we had the different sites built out within the Auvik collector, entering in the IP information for each site, and then installing the probe facility by facility.

There was a time where it was a little confusing to get set up, but Auvik really helped to bridge that gap in knowledge by providing training to our end-users, meaning me or someone on our help desk team. They gave us more in-depth information and helped us to really understand the product features and to ensure that we were using everything to the best of its capabilities within our circumstances.

We have 10 users of Auvik: three system administrators, two level-two help desk technicians, and about five level-one help desk technicians. As a cloud-based solution, once it's deployed, unless we're making certain IP schema changes, it doesn't require much maintenance at all from our staff. On occasion, a backup machine needs to be replaced and we have to reinstall the probe. But outside of that, it's really click-and-go. The Auvik probe will pick up on a new subnet too. It's all available within the dashboard itself. You can literally turn off the old subnet and turn on the new one and begin scanning those elements just like they were before.

We did it on our own.

We've seen ROI in terms of the time that Auvik has saved us in the instances where we've had configurations that needed to be cloned, for example. I don't want to say the product is stale, rather it's insightful. You get from it as much as you want to get out of it. For us, the insights, manageability, and troubleshooting go a long way because we're saving man-hours.

When it comes to time-to-value, the setup time is fairly easy and the network discovery is very helpful. 

Because we had nothing previously, it's a very valuable tool. Having everything in one place, enabling our teams to react faster, decreasing the time to resolution, as well as identifying weak places within the infrastructure—it's hard to put a value on all that it gives us.

It has saved us a considerable amount of money, given that everything had to be done manually before, such as FaceTiming with a member of the facility and trying to get a physical view of a particular issue. Just having a central pane of glass that easily identifies various pieces of information goes a long way. We're saving tech time which can ultimately then be better spent supporting the organization and end-users. As far as infrastructure planning and rip-and-replace go for certain network technologies, it's provided much better insight and we can plan for which network switches actually have to be replaced. There are cost savings there because if we've got gig switches here and we're only looking to replace 100-meg switches, we can really drill down and know what we need ahead of time, going into a particular building, when we redo some infrastructure.

The solution is billed per network device, so there are devices that are not subject to billing in your environment, such as dumb switches because they have no higher reporting protocols. If you do have those, Auvik won't report on them in the same way. It won't give you port-based or traffic-based analyses.

There are no costs in addition to the standard licensing fees.

We initially looked at SolarWinds and, thankfully, we didn't go with that product. Its setup time and configuration were pretty extensive and we never fully finished it after putting about 10 days' worth of time into it. As much as I'd like to say some good things about SolarWinds, it really wasn't for us because of the lack of communication and support that I got from them in helping to set things up. Ultimately, we steered away from that product.

The biggest pro for Auvik is its ease of deployment. It was as easy as I've personally seen a setup of this type of solution to be. It has an abundance of features and functionality. The only con is that the install is a little bit more tech-intensive as far as time goes.

The biggest lesson I have learned from using Auvik is that every organization should have something like this. From our perspective, it isn't very expensive, although in smaller organizations it might be considered more of a luxury. But every luxury has its benefits. All the aspects it helps us with make it phenomenal. It's definitely a "need," not a "want."

I would advise making sure you have a very good, thorough count of the SNMP-enabled devices you have within your network. Also, be cognizant of whether you have any non-managed switches because you can't really get visibility into them. 

Also, make sure that you have full control over your network elements within the environment. We had a couple of switches that we had to factory-reset to get back into them, because there were lost credentials. Assuming that your infrastructure and your documentation are good, you really shouldn't run into any terrible issues. If you're sound on documentation, credential handling, and credential guarding, this tool will be very easy for you to implement. And if your infrastructure is pretty sound and everything is consolidated, this will be a phenomenal tool.

I originally purchased Auvik to assist in troubleshooting network issues on the local area network and wide area network. We were having some slowness issues, but they were only in certain segments of the network. I had no tools on-site to help me find where the problem was.

I was able to realize the benefits of Auvik Network Management immediately. I knew I was having network problems. I got it up and running in a day, and I was immediately able to seewhere my issues were.

It does not cover everything I need, but a part of that is because I have not implemented Auvik 100%. I got Auvik up and running far enough to do my troubleshooting, and I then left it while I worked on other major projects. So I still have a lot to learn. I am taking all their classes, and I learn more in every class. My frequent comment is that it is like drinking from a fire hose, but

Auvik is putting the classes online so I can then go back and run it again, open up my Auvik and go through the items covered in class. Going through those training sessions has helped me configure Auvik.

I am 90% positive and 10% negative about its user interface. Most of the time, it is very intuitive, and I can find what I am looking for, but sometimes, it is a struggle. What is awesome is that during the training sessions, the instructors always end with Q&A, and you can ask any question. You do not have to ask a question just about what the training was on. They answer your question, and they always lead me to where I need to be on the interface.

The network map is currently giving me partial visibility. I do not have visibility to my portal to the Internet, but that is partly because I do not have it configured and partly because I am not sure if I want to allow that password access to my firewall.

The network map along with the dashboard gives a real-time picture of your network, but my network map is still messy. I am not sure if it is because it does not have all the permissions yet to do everything it wants to. About half of my devices are stranded in the middle of nowhere, and the other half are connected through multiple connections. A part of that is that Auvik does not have the Ubiquiti stuff down yet, so they do not really know which devices are talking to each other, but it is enough. Especially with the connectors, I can see what device is talking and figure out where my bottlenecks are. It is nowhere near perfect. When they give their training sessions, their network map is beautiful. Mine is pretty chaotic.

Auvik Network Management decreased the mean time to resolution for the initial problem I had.

So far, I have used it only for one initial problem. It helped with that problem.

I like the way that Auvik auto-configures itself to do the mapping. I wish it was a little more accurate, but as soon as you start getting your authentication correct for the different protocols that Auvik uses for discovery, it starts putting together your map for you.

It is not backing up my configurations on much of my network equipment. For some reason, it struggles with Ubiquiti equipment, and it is a known issue. They have a ticket open for it. Some of the issue could be the way Ubiquiti handles authentication. Ubiquiti handles authentication differently. Auvik expects to be able to log in to a device and then go into Config mode, whereas you are already in Config mode when you log into a Ubiquiti device. There is no additional authentication required, so they are having difficulties getting their scripts working on Ubiquiti.

The piece that I would like to see the most is getting those configs backed up. That is my chief complaint. If Auvik can get that work, they would be perfect.

I have been using Auvik Network Management for about seven months.

I contacted Auvik about how often they were down, and their response was they had not been down. They have just been doing maintenance that temporarily takes the system away, so it is not 100% stable yet. It does seem to go down a couple of times a month, but it is never down for long. Usually, they are fixed quite quickly.

We have just a single site with a couple hundred devices. I know that they have very large customers' data centers, so I am assuming that Auvik scales well. 

I am the sole IT person for this facility. It is a school for the intellectually disabled. We are a live-in facility 24/7 and 365 days. I have 300 students and about a hundred staff. I provide support for over an 850-acre campus.

We have just a single site with a couple hundred devices. I know that they have very large customers' data centers, so I am assuming that Auvik scales well. 

I am the sole IT person for this facility. It is a school for the intellectually disabled. We are a live-in facility 24/7 and 365 days. I have 300 students and about a hundred staff. I provide support for over an 850-acre campus.

Positive

I used PRTG. PRTG proved to be too complicated for one person to set up and use. It took too much care in feeding. Auvik is definitely better.

It is a hybrid setup. I have a collector on-site, but all the actual work is done in the cloud.

Its deployment was pretty easy. 

The only additional maintenance is if any equipment comes online and it does not recognize the equipment, you have to go into Discovery and give it the appropriate username and password.

That is the only maintenance required.

I deployed it myself.

The school I work for was founded in 1893 by a private family. It is still run by that same family, and that family dislikes the subscription model. They much prefer to buy equipment and own it, so trying to convince management to use a subscription model for a piece of software was pretty difficult. However, I was able to get Auvik to present it more as a multi-year contract instead of a subscription model. It is something their sales can do for other customers, but I do not think it is something they advertise.

For the size of our school, it is expensive, but I understand the reason behind the pricing. All my servers in the network are monitored by Auvik at no charge. We are only paying for network devices, so I pay for switches, access points, and firewalls, but I do not pay for all my user PCs and MACs, and my servers, which are my critical devices.

You need to understand the permissions required by your different pieces of hardware, especiallyfor different hardware types such as Windows, VMware, your networking hardware, and your Internet interface. You need to have all the permissions ready so that you can set up your Discovery. The hardest thing to get running on Auvik is getting the Discovery set up properly.

Overall, I would rate Auvik Network Management an eight out of ten.

I'm a technical team lead managing other engineers and specialists for several clients. I utilize Auvik for strategic discussions, escalations, and support tickets. I'm on the backend trying to coordinate responses to outages, feature requests, etc. 

We use multiple applications to manage our network. Auvik is our network mapping and discovery tool that creates alerts in our ticketing system. We use ConnectWise Automate and that suite of products for ticketing. It's not like Auvik is a ticketing help desk system with remote control, but it can do just about everything from a monitoring standpoint. We still use AppNeta for board mirroring or finding latency in network traffic.

Auvik is a total package for network discovery that completely meets our needs as a company. I don't see us leaving Auvik for some other network discovery tool. It's a one-stop shop where we can dive into each of our client's networks, and we have quite a few. I don't know precisely how many we have. It's fewer than a hundred, but it's too many to do LAN diagrams in Visio. 

The solution has reduced repetitive low-priority tasks because it collects the SNMP information for us and alerts us when servers go offline. We can see connectivity in the network from a bird's eye view without the need to dive into the firewalls and switches. Auvik saves us from having to create manual diagrams, and I can export all the data about a client's network, so I don't have to gather all of that myself.

Given our number of clients, we would probably need another full-time engineer if someone had to keep track of all of this on their own. It's roughly equivalent to a human working full-time for an entire year. That's one less person we need for all that, and Auvik reduces human error. 

The visibility Auvik provides is critical because it's part of our onboarding process, giving us a high-level overview so long as the client doesn't change the SNMP default values. We can immediately see what a new client is working with as soon as we get off again into their network.

Auvik has improved the team's availability by about 75 percent. Before Auvik, we used a different tool to scan, but it provided only a one-time snapshot of the network, whereas Auvik provides mapping in real-time. 

It's probably one of the first tools we introduce to new hires in our network operations center. Auvik is intuitive and offers hints. You can type a vendor name or an IP, and it's immediately accessible at a high level. Of course, there's depth to the product that takes time to develop. Junior engineers can quickly get a look at it, start learning how SNMP works, or configure it on devices and watch them appear in Auvik.

We use Auvik when we're doing strategic planning for clients. It helps us find servers, hosts switches, correct serial numbers, etc., so we can do warranty lookups and that sort of thing. It's important. We primarily use it for information gathering to see a visual network diagram mapping and get tickets.

It's hard to say that one feature is my favorite, but I like Auvik's ability to map networks using SNMP. It maps the network, so I can look at all the devices and set them to provide alerts or automatically create tickets when outages occur. If clients need it, I can export all of the data into an Excel spreadsheet.

The monitoring and management functions are easy to use. The network visualization is also intuitive. Ease of use is crucial because many of our help desk specialists and entry-level people need to navigate the solution, so it's vital to have simplicity in standard high-level searching. A single integrated platform is essential to stay in line with our best practices.

The search could be slightly more intelligent. If I type in "Dell" and put an extra "L," Auvik doesn't give a suggestion, "Did you mean 'Dell?'" I have to fix that. That's a minor thing.

Also, if I select a specific device and apply it as a search filter, it shows me the device, and I have to click on it to see it at the bottom of the page. Otherwise, it just stays on the discovery. When I close the device, it remains on the switch displaying the diagram. I have to click the home dashboard to get back to the way it was.

When I remove the filter, it should take me back to the home dashboard. After I add a filter, select a device, and apply it as a search filter, I think it should pop up if there's only one. When there's only one device in the filter, I find it somewhat annoying to need to click it to dive into that device. If I remove the filter, I would prefer it return to the home dashboard. It's a minor irritation at times.

I've used Auvik for more than five years, close to eight. 

Auvik is solid. I have never experienced an outage. Auvik has downtime, but they provide notice well in advance. The maintenance window tends to be at times that won't impact me. The most recent maintenance window was on Dec. 3 at 7:00 AM Eastern, which is 4:00 AM Pacific, so it didn't affect me at all.

I don't see a limitation to the scalability.

Before the company adopted Auvik, I used Visio to create my online diagrams by hand.

I wasn't involved in the initial setup, but deploying the collectors is easy. Another person handles the onboarding process, but the network maps are populated within a day or so. I've never heard anyone say, "Hey, it's taking a long time for Auvik to get going." They say Auvik is up, and I see the map is there. 

I rate Auvik 10 out of 10.

We use Auvik to map out networks and to view device health, meaning not just if it's up or down but also if there are any system-generated errors that can be listed via Simple Network Management Protocol (SNMP).

It saves me from having to log into each device through whatever login they may have available to them. It's a single interface for the devices.

It has greatly increased our speed. We don't have to check individual device-specific interfaces for monitoring. It also handles real-time monitoring, as opposed to a daily or hourly check. In some cases, it also allows us to find a device that's in trouble and directly connect to it from the interface. It's a huge time saver, and it does save us a fair amount of leg work.

It has helped to reduce repetitive, low-priority tasks through automation, such as checking on a device and opening and closing tickets for the devices that are in.

We now have a lot more visibility into the networks than we did before. This visibility is very important for our IT teams. The IT team would have a fairly difficult job checking all these different devices manually. In some cases, the work just wouldn't get done if it wasn't being done automatically.

A simple site view with the associated devices populating as things to add to or remove from the network is valuable. It's also nice to have it integrated with our ticketing system to create tickets in certain cases for devices that go down or have some high-level alerts, such as high CPU or overtemperature.

It's pretty easy to use its monitoring and management functions. There's a wizard that's involved when you first start it up and then you can pick. The initial network sets itself up and then you can add networks if they are available to the devices being monitored. Its ease of use is fairly important. There are some other monitoring tools that we have available to us, but they're agent-based. We can't load an agent on a switch or a router or something like that. We need some sort of SNMP interface to detect those errors. Otherwise, they would go unnoticed.

It's pretty intuitive. As soon as you pull up the site, the map comes right up. You can expand or contract different device types. In many cases, it will attempt to interrogate the device and find out what device type it is, but sometimes, you may have to set it yourself.

For the most part, it's great for visualizing the network mapping/topology for our organization. However, when complex VLAN networks are involved, sometimes, the picture can get a little cloudy. It would definitely be nice if there was some way of choosing a VLAN to view or something like that. They should definitely improve the handling of multiple networks and VLANs. I do know that the information has been gathered, and I know it's possible to give different looks. There could be a layered approach to the VLANs where you can take the default VLAN or you can toggle a switch and show, for example, a security camera VLAN or a voice-over IP VLAN. It would be nice to be able to have it pull up the information relevant to a particular network. 

The GUI map view could potentially be adjusted so that we can manipulate it without necessarily having it resize every time we adjust the screen. There should be a single focused view. Currently, it resizes every time I move this bar that has the information underneath it. Sometimes, that's after me zooming in on a particular piece, which makes it difficult to find my place again.

I have been using Auvik for at least a year. I'm a senior engineer for an MSP, and I use the Auvik system on a daily basis. 

Auvik's stability is great. They do run regular maintenance, and they always have an announcement about the maintenance ahead of time.

Its scalability is great. You're not limited to a number of devices, etc. Your only limitation is whether or not it can see the networks that you're trying to track. Because this is a cloud-based solution, it wouldn't be good for somebody who has an isolated network or something that's not on the internet. Other than that, whether you've got 5 workstations on the small network with 1 switch and 1 router, or if you've got 6 switches, 30 telephones, 7 printers, and 18 access points, it shows them all irrespective of whether it's a big one or a small one. The pricing on it is based on the devices. A small network is going to have a smaller cost than a larger organization.

It's deployed across multiple clients that we have. Each one of our nine different sites is a different client. Of those clients, none of them has two sites. So, it's not necessary that we have multiple site issues. We have nine sites and nine clients.

Normally, we have been just speaking to the sales team. So, contacting the sales rep is something that we've done, but there is a knowledge base that is fairly fantastic. They have it set up for a bunch of different device types from different manufacturers. You can see how to configure them so that they're sending the right information to Auvik. Each one of them gives step-by-step guides on how to integrate that device with Auvik.

There is obviously technical support, but I have not had to use it, which is great. The support is available right from the interface. You just go to the website, and they give you the phone number, and there you go. It would be fairly easy. You can do it through a message or through their phone number.

Their sales support is fairly techy. They are not just managers. They know their devices and their software. I would rate the support provided by their sales engineers at least an eight out of ten. They were easily able to answer any of my questions. However, not a whole lot of questions came up because the product pretty much runs itself. There are how-to guides on adding the capabilities of new devices. If there's a router, a firewall, or something else, there are instructions on how to configure it to connect to Auvik.

Positive

I have, but they belonged to certain ticketing systems, such as HP OpenView, etc. HP OpenView comes into play if you only have one network to manage. Currently, I've got nine different networks under Auvik, and for me, it's a switch between them. It's as simple as just dropping down a box and looking at the next one. However, because it's integrated with my ticketing API, I don't necessarily have to drill down into it. I'll receive tickets for certain devices that are having issues.

It was very straightforward. There was some hand-holding that they needed to do for us in order to integrate it with our ticketing system, but so far, setting up Auvik, starting a new site, and having that site inventoried and discovered has been mostly wizard-based. So, it's not difficult. You probably don't even need to be familiar with the technology to set it up.

We implemented it out of the box, but there are checkpoints where you authorize networks to be scanned. There is a stop there, but it's not too big a deal.

It probably took about two hours to set everything up for the first client, and then after that, each additional client would be about half an hour.

Auvik had a sales team that assisted us in the initial setup. In terms of the staff involved, I and the owner of my franchise company were there. He didn't need to be there. He just wanted to be there.

It doesn't require any maintenance from our side.

It saves me time on a daily basis. So, there's a great time-to-value. A fair amount of my time has been spared using this tool.

Its licensing is very fair. The devices that stand to gain the most benefit from this product are the ones that are billed. In the case of routers, switches, and firewalls, I won't necessarily have the ability to put a management agent on them to gather errors and activity logs. This type of solution is a requirement for me to properly monitor and manage these devices. The devices that aren't being billed are workstation servers, etc. For those devices, I can put agents on them to monitor their health. It has a fair billing structure. Additionally, the billing seems to only happen for devices that I have linked to my ticketing API, in such a way that I could stand a benefit from it.

To someone comparing network monitoring solutions but concerned about pricing, I would say that when comparing with other applications, they need to check if the other solutions are able to integrate with their ticketing system APIs. They also need to check how many device types they expect to log into during any one of their days, in order to get a true look at the device health of the networks that they have under them.

I did know of one other option available, but we did not evaluate or entertain any others before we went with Auvik. It was presented to us as a trial, and we were simply impressed.

The best advice is to make sure that all the devices that you want to come up in the map view have been properly configured to send their SNMP data to the collector.

Auvik helps to keep device inventory up to date, but typically, we do device inventory in a different way. It's nice to be able to validate the inventory, but in most cases, inventories are handled by different tasks. Auvik is invaluable for taking the initial inventory for a new client, but normally, we would go with a different inventory process, and we would use this to validate that going forward. It helps with the building of the inventory, and it helps to validate the inventory as it progresses.

I would rate Auvik at least an eight out of ten.

We use Auvik to monitor configurations, devices, and discovery.

Our staff has a much easier time managing devices, networks, and configurations. We're in the middle of a project involving a full-blown switch replacement. There are about 80 switches, and we can grab configurations quickly and easily. Our staff doesn't have to worry about configuration backups or look in 10 different places for logins to hit a switch or firewall. Auvik discovers rogue devices that happen to be on the network, which saves us time and stress. It makes our lives easier.

Auvik saves us a lot of time. For example, for configuration backups, we used RANCID. It's been around forever, it's free, and it's open-source, but there's no support. It would take a lot of time to stand up to the three to ten different solutions, which would be required to get what Auvik gives us out-of-the-box. The amount of time it would take, the number of sites, the networks, and the cloud or on-premises environment would vary from company to company. If it's a 10-person company, standing up those solutions would be a little bit easier. If it's a 3,000-person company, it could take months to get everything correctly stood up. Auvik is a click-and-go solution. It has easily saved us hundreds of hours.

The solution affects our IT team's visibility into our remote and distributed networks globally. If there's a network problem, it's normally given to a network engineer or somebody who at least knows what they're doing. With Auvik, each of our staff members has access to it. They can make changes according to their best judgment. It helps a lot of our staff understand basic networking, VLANs, trunks, and how networks are laid out. If somebody says, "Port 12 on Switch 2," they can find it.

The automation has a positive impact on our IT team's availability. It saves us time, and our team is more available to help with other tasks.

Tasks that would take hours now take minutes, especially if somebody doesn't have a lot of knowledge or skill set. Auvik doesn't turn someone into a full-blown network architect or engineer, but for people who wouldn't necessarily know how to crawl around on the command line or do discovery, everything is in front of them and they're able to set it up.

We've been able to delegate low-level tasks to our junior staff. Right now, someone is manually doing around 50 switches, four core switches, and a firewall deployment by leveraging Auvik. He's had very minimal network experience prior to this, but he's learning about the network, port, and VLAN through Auvik.

We have seen a reduction in our meantime to resolution. Between the alerting and the ability to leverage Auvik to find it, fix it, and roll it back, we've cut down our response time by at least half, if not more. We haven't needed to keep track of that metric because we hit the ground running with Auvik. At my last company, the amount of time we spent on issues was insane. There were meetings on an almost daily basis about why people were spending so much time on network-related issues.

For example, we had a major customer that was down for over a week and a half due to a network issue, and they weren't pleased about it. It happened again after we started using Auvik, and I was able to identify the issues with Auvik within five minutes and resolve it within ten. The amount of time it took to resolve the issue went down from a week and a half to 15 minutes.

All of the features are valuable, but the ability to remote into anything, whether it's a terminal or a browser, is really big for us. It makes things a lot easier day-to-day. It keeps track of all the firewall or switch configurations, so if anybody makes changes, we can roll back and have an alert on it. Discovery has been useful.

It's easy to use Auvik's monitoring and management function. We can roll out a site in under 15 minutes, so it's up and working right away.

The solution's ease of use has been very important to our operations.
We have a lot of tool sets, so we don't want to spend a lot of time deploying and tinkering with it. Auvik is a click-and-done solution, so there's minimal effort involved.

Auvik provides a single integrated platform, which is pretty important to our organization. Everything is one pane of glass. We don't want to have 20 different portals for 20 different customers because managing each one individually would be a nightmare scenario. It's a lot of overhead. It's pretty useful in general, but it's also incredibly important because the more time we spend managing those tasks, the less time we have for everything else.

Auvik helps to visualize the network mapping and topology for our organization. It's just there, so we don't really think about it. It makes it very easy. As it discovers, it draws out the map. We can see where things flow and what they're connected to. We can answer all kinds of questions like, "What happens if I unplug this," or "Where is this machine, generally speaking?" We've used it to hunt down everything from rogue devices to a missing laptop. Thanks to the topology view, we were able to see which AP it was connected to.

Customers like to see what their network looks like. They may think they have a tiny network, but they actually have 500 devices that are just sitting on their network in a 20-person company. It helps them understand that we're actually doing something and not just saying that the network has a problem. It's good for visualization and for keeping track of where offices are located so we don't need to commit it fully to memory.

It's very important to us that visibility helps our IT team focus on our networks. We want our staff to be aware of the network, what's on it, and how to manage it. We've used it as a learning tool. It discovers everything. One of our guys wants to get more into networking, and we said, "All right, go into here, go to this switch, get all of the port configurations, and figure out how to apply it to the new stuff," because they're not the same. It's a manual process, so he's learned more about networks and networking in the past week than he has ever been exposed to before.

Auvik helps us keep device inventories up to date. It's helpful to know when the software ends and what the last support dates are.

The higher-level and more experienced guys on our team have been able to delegate simpler tasks to our help desk and people who don't have 10 years of experience with network engineering. It frees up our team, and it helps our less-skilled employees get a hands-on education, which is usually the best way.

Sometimes it's a little bit slow to load, but I can't think of anything else that could be improved.

I have used this solution for two years, in my previous company and now in my current organization. 

We have never needed to use technical support.

We previously used multiple applications for managing our networks. We used Device42 for asset management, discovery, and collection. We also used an RMM and SolarWinds.

There are no other solutions that do what Auvik does. Other solutions can get very convoluted. You could have a monitoring solution, a configuration backup solution, a Syslog server, a SIM, and a Device42 or something similar to track hardware life cycles.

Auvik has packaged everything into one solution. I remember thinking, "No one really does everything the right way." The more you see a solution smash different facets into one product, the more you think, "There's no way they can do everything really well." Auvik does what it says it will do. It meets all expectations. The monitoring is just as good, if not better than a dedicated monitoring solution. Cisco is happy to charge you boatloads of money to do Syslog and configuration backup, but Auvik does it out-of-the-box.

The icing on the cake is all the integrations. You can throw it into Teams or into a ticketing system. We've used other solutions, but for the rest of my career, Auvik will be the default solution that we use.

I deployed Auvik myself. It only took 15 minutes to set up. After giving some credentials and installing a collector, it started up immediately. We had usable information within half an hour and fully discovered networks within a couple of hours. It was insanely easy.

We're a little bit different from most organizations because we include what Auvik does in our monthly fee for our customers. Technically, we're definitely making money. We don't actually break it down and say, "We made $500 on Auvik this month," but as soon as we have a customer, we're making money, and part of that is thanks to Auvik.

Auvik's pricing isn't astronomical. Auvik is extremely fair in how they break down a billable device versus something that isn't, especially compared to PRTG, which charges for a number of sensors. Auvik makes it really easy to understand that you aren't going to get billed for certain things. They're cutting themselves short, in my opinion, but I've never had to worry about pricing from Auvik. It's always been very affordable.

We evaluated five other direct competitors of Auvik. Essentially, we did our due diligence and put it through the paces. We did a demo and a trial.

I would rate Auvik as 10 out of 10. 

I see absolutely no point in an on-prem monitoring solution anymore. If the collector goes offline and something is down at the site, you know that you're looking at a very minimal amount of issues: either the firewall just burst into flames or the ISP is down. Because everything is in the cloud and we're able to see it 24/7/365, I wouldn't deploy an on-premises monitoring solution anywhere.

Auvik is the best piece of software we have used across the board because of the value it offers, especially compared to what it costs and the value it adds to the organization. I've worked for major companies like ESG, Abiomed, and Akamai. I wish I knew about Auvik earlier in my career because it would've made my life a million times easier as a systems administrator, systems engineer, and architect.

We use it for our clients that have managed network services. We monitor their networks to see if there are any anomalies or unknown devices, and we use it for troubleshooting as needed.

One of the benefits is the insights into the network. We had one client that was having tons of issues. We put Auvik on there and we were able to isolate the problem to one device, remove it, and everything is now working well.

It has helped with visibility into remote and distributed networks, globally. For those clients that pay for the service, it allows us to see their networks, see what's going on, and sometimes even see an issue before the client knows and calls us, and that is what we want.

We have also seen a reduction in mean time to resolution, of about 10 to 20 percent, depending on what the issue is.

I like the traffic insights. That really helps to see what's using your bandwidth.

The monitoring and management functions, while there is a little bit of a learning curve, are pretty easy. Once you get it, it's straightforward and easy to go forward with. That's very important because we don't have time to sit around and try to figure out how to use it, looking at tutorials. It's pretty intuitive and their support is really great too if we have any issues.

And the fact that it provides a single, integrated platform for our organization is important as well. Having 50 different accounts to log into would make things difficult at times.

The overall intuitiveness of the network visualization is great. It makes it easy to see everything and easy to follow and pinpoint what's going on.

The visualization of network mapping is good. The only complaint would be that VLANs don't necessarily show up as a regular LAN does. They do show up, but there is some manual tuning you have to do to make that look perfect. That's kind of the nature of how VLANs work, so I don't think there's anything they can really do to help make that better. Still, it does at least pick up devices that are on there, and tries to connect it all, but it doesn't always do a good job.

Also, it doesn't help keep device inventories up to date. It doesn't have any updating features.

It has been three years since I started using Auvik.

It's reliable. We haven't had any issues with it. We haven't had any downtime because the server wasn't available, or anything like that. It's definitely worth it.

It seems to scale really well. When we first started, we just had three clients in there. Now we have it on all 35 of our clients, and some of them have multiple sites. They're not all fully configured, but at least we have the agent on them and we're getting data already. I just need to go into each one and set up the SSH and SNMP settings, but that's no big deal.

It's deployed into our managed network clients who have anywhere from three workstations all the way up to over 300 devices on the multiple VLANs.

Their technical support is a 10 out of 10. They have direct support within the platform via a chat and they'll walk you through anything and give you the guidance you need. And their email support is great as well, if you have to escalate something. They'll even do a Zoom call with you if they're not able to resolve it by email or chat. They don't leave you hanging.

Positive

We didn't use any solution previously. We just used an ad hoc network scan to try to find issues, but that doesn't really give you a great view of everything.

I'm the one who does the deployments. The setup is straightforward. It's complex in the sense that you have to connect each device and configure its SNMP or SSH settings, but it's pretty straightforward overall.

Depending on the network, within 30 seconds to two minutes, max, the network mapping starts to populate after implementing the collector. It's pretty quick.

It doesn't require much maintenance. Once you get everything set up, unless you introduce new devices, you don't really have to mess with anything.

We did our initial implementation with the Auvik trainer. He helped us onboard clients and gave us training. Our experience with him was good. He was really knowledgeable and helped us out as we needed it.

Initially, it was me and our CEO involved in the implementation, but he passed it off to me after the first couple. And of course, we have had Auvik's help with it as well.

Time-to-value from Auvik has been the troubleshooting of that one client I mentioned, just by itself. We spent countless hours onsite trying to figure out what was going on, doing our own tests with freeware, but we weren't able to isolate the issue until we installed Auvik. If we had done that from day one, it would have taken three hours for the setup, instead of that ticket taking 22 hours of work. It's a big benefit.

Auvik's pretty good in terms of pricing. It can get pricey if you have multiple managed devices, but if it's just a simple network with only one or two firewall walls and smart switches, it's reasonable.

The one client that we had issues with has 15 managed devices. That client is pretty expensive, but it's worth it.

Our eyes were set on Auvik, based on reviews from peers.

It's not really replacing any tasks. Rather, it's a good tool to see if the network is down. We have others that do the same thing, but Auvik is more for investigating issues.

My advice is to take your time. Make sure that the credentials are correct when you input them. Go through their guide on setting up WMI for Windows workstations to get better results. Just don't rush it and get good data.