How can we help?

Auvik collector deployment strategies

Follow

There are a few key steps to bringing a network onboard with Auvik. But before we dive into onboarding, let’s figure out the best way of deploying Auvik based on the network architecture and resources you have available.

First, do you operate your own data center or co-location facility, and do you have a Layer 3 tunnel into some or all of your sites?

Note: You can modify active collectors, and switch between single and multi-site collectors at any time. This doesn’t affect your Auvik subscription because Auvik’s pricing isn’t based on collectors.

  • Deployment options
  • Single collector
    • Deploying dedicated hardware
  • Multi-site collector

Deployment options

Whether you choose a single or multi-site collector, your options are similar. For more detail on installation options, see What installation options are available?.

Single collector

The Auvik collector is a lightweight, Ubuntu-based distribution that acts as a data collector and remote management proxy for your networks.

A single collector can be deployed for each group of inter-reachable subnets. If you have network segments that aren’t interconnected, you can deploy a collector for each siloed network segment. There’s no limit to the number of collectors you can run in parallel.

Regardless of the platform you deploy the collector on, the minimum requirements for the single collector are:

  • 2 vCPU
  • 4GB RAM
  • 16GB disk space

You can deploy a single collector on a hypervisor, on bare metal, or in a container. A single collector is managed at the site in Auvik.

Deploying dedicated hardware

For smaller sites or those with strict security requirements, deploying Auvik alongside existing infrastructure may not be possible.

As a result, some of our users want a box they can plug into for initial network discovery and ongoing monitoring. Since the Auvik collector is Linux-based, it can be deployed on low-powered hardware with an x86 / x64 processor. Typically we see people use:

  • Low-powered home theatre PC (HTPC) hardware
  • Micro-PCs, like the Intel NUC

The Auvik collector firmware can’t currently be deployed on ARM-based platforms like the Raspberry Pi, but something similar sized but x86 based is great.

Multi site collector

You may have a data center or co-location facility that provides a central point of Layer 3 reachability into your managed sites. In such an environment, deploying a dedicated instance of the Auvik collector for every managed site leads to high resource utilization on your hypervisor, or increases the number of bare metal boxes you’re shipping out.

In this case, you have the option to deploy a shared collector, a single instance of Auvik that maps and monitors multiple sites.

The amount of resources required for the multi site collector are proportional to the number of shared sites. At a minimum, we recommend dedicating the following resources to a shared collector:

  • 2 vCPUs
  • 4GB RAM
  • 16GB disk space

Just like the single collector, the Auvik multi collector can be deployed on a hypervisor, on bare metal, or in a container.

If you have any questions about your deployment strategy, please contact Auvik support.

Was this article helpful?
4 out of 5 found this helpful
Have more questions? Submit a request