- Getting started
- Selecting a collector type
- Virtualization platforms for the OVA and scripted collector
Note: The 32 bit Auvik Collector is being decommissioned. For more information, click here.
Getting started
Using Auvik starts with installing the Auvik collector using an OVA, bash script or Windows service on a network. Before you can start the Auvik collector, you must first do a few things.
- If you are an Auvik customer, add a new client.
- If you're not an Auvik customer, register for a trial.
- Have a host ready to deploy the collector on.
Selecting a collector type
Auvik currently has four main types of collectors OVA , bash script install, Windows and the Docker Container. The Windows version has two options to that may be used to deploy it: either by using the Windows Installer or downloading the executable and running it from the command line.
The Auvik OVA, Bash script, and Windows install options of the collector can only be run on an x86 / x64 processor. The new Docker container version can be run in a multitude of environments. This includes internal emulation on environments like Kubernetes.
At any time, you may sign in to your Auvik account and access a new client to see the types of installation options that are available.
Windows Service:
The Windows service can be installed on any Microsoft Windows desktop running a 64-bit version of Windows 10 Version 22H2 or higher or any server running a 64-bit version of Windows Server 2016 or higher. For more information on OS End of Service and the Auvik Collector, click here.
The system should have at least one CPU, 2GB of RAM, and 8GB of available disk space. Larger installations will require greater resources with a minimum of 4 CPU threads, 8GB of memory, and 8GB of free space. Even greater CPU and memory allotments may be needed when deployed to environments where the collector may encounter 2,000 devices or over 9,000 interfaces (Interfaces may be virtual or physical) If the Windows machine is performing any other critical functionality, resourcing should be increased to address those needs also. Be aware the Windows service will bind to ports 21 and 69. We recommend you install the service on a system that doesn’t already have services bound to these ports.
OVA file import:
Download an Open Virtual Appliance (.ova) file by clicking Download the collector from the installation wizard. Once the download is done, you’re ready to import the collector into your preferred virtualization platform.
Bash script install:
The bash script option is for advanced users who know how to install Ubuntu. Create a new blank virtual machine (local server or cloud environment), then complete the remaining steps.
Note: The OVA and scripted Auvik collectors require a minimum of one virtual CPU, 2GB of RAM, and 8GB of disk space. This minimum requirement should be adjusted upward if the collector is to be deployed to a larger environment. A four-threaded CPU with 8GB of RAM and 8GB of disk space may be needed for these larger environments. Even greater CPU and memory may need to be deployed to environments where the collector may encounter 2,000 devices or more or over 9,000 interfaces (Interfaces may be virtual or physical).
Docker Container (Beta):
The Docker container version of the collector is available for different types of hardware and software environments beyond just the x86/x64 intel-based architecture. Since the nature of the Docker containers themselves are to be base code that take advantage of the host machine/software. You will want to make sure the host machine follows the same guidelines that the other collectors follow
Note: The OVA and scripted Auvik collectors require a minimum of one virtual CPU, 2GB of RAM, and 8GB of disk space. This minimum requirement should be adjusted upward if the collector is to be deployed to a larger environment. These larger environments may need a four-threaded CPU with 8GB of RAM and 8GB of disk space or more..
Virtualization platform options for the OVA and scripted collectors
To deploy the Auvik OVA or scripted collector, you need a supported virtualization platform ready. Desktop virtualization platforms such as Oracle VirtualBox, VMware Fusion, or VMware Workstation are fine for quick use, but aren’t recommended or supported for enterprise implementations. Below are the virtualization platforms and host operating systems Auvik supports:
|
Virtualization Platforms |
Host Operating Systems |
|
Commercial cloud* (e.g., Amazon AWS EC2, Microsoft Azure) |
N/A |
|
Microsoft Hyper-V* |
Windows Server |
|
Citrix Xen* |
N/A |
|
VMware ESX / ESXi 6.5 and above |
NA (barebones hypervisor) |
* Supported only for bash script installation
The collector is intended to only be used in a LAN type network given both the probing methods used as well as the unsecured nature of some of the protocols.
There are additional deployment implications to consider before setting up an Auvik collector. For more detail, see Auvik deployment strategies.
If you have any questions about your collector installation, please contact Auvik support.
