110 lines
4.7 KiB
HTML
110 lines
4.7 KiB
HTML
|
<!DOCTYPE html>
|
||
|
|
<html>
|
||
|
|
<head>
|
||
|
|
<link rel="Stylesheet" type="text/css" href="style.css">
|
||
|
|
<link rel="alternate" type="application/rss+xml" title="RSS" href="rss.xml">
|
||
|
|
<title>Auvik Trial</title>
|
||
|
|
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
|
||
|
|
<meta name="viewport" content="width=device-width, initial-scale=1">
|
||
|
|
</head>
|
||
|
|
<body>
|
||
|
|
|
||
|
|
|
||
|
|
|
||
|
|
<hr />
|
||
|
|
<p>
|
||
|
|
<a href="index.html">Index</a>
|
||
|
|
<hr />
|
||
|
|
</p>
|
||
|
|
|
||
|
|
<p>
|
||
|
|
last 5 posts
|
||
|
|
<hr />
|
||
|
|
</p>
|
||
|
|
|
||
|
|
<ul>
|
||
|
|
<li>
|
||
|
|
<a href="1700345096-busy-week.html">Busy Week</a>
|
||
|
|
|
||
|
|
<li>
|
||
|
|
<a href="1700104768-new-job-offer.html">New Job Offer</a>
|
||
|
|
|
||
|
|
<li>
|
||
|
|
<a href="1699564352-webhooks.html">Webhooks</a>
|
||
|
|
|
||
|
|
<li>
|
||
|
|
<a href="1699558725-ref-290-submitted.html">REF-290 Submitted</a>
|
||
|
|
|
||
|
|
<li>
|
||
|
|
<a href="1699375988-ref-209-start.html">REF-290: Start</a>
|
||
|
|
|
||
|
|
</ul>
|
||
|
|
<hr />
|
||
|
|
<p>
|
||
|
|
<span id="-Date:"></span><strong id="Date:">Date:</strong> 2023/11/24
|
||
|
|
</p>
|
||
|
|
|
||
|
|
<p>
|
||
|
|
<span id="-Author:"></span><strong id="Author:">Author:</strong> Tristan Ancelet
|
||
|
|
</p>
|
||
|
|
|
||
|
|
<div id="Auvik Trial"><h1 id="Auvik Trial" class="header"><a href="#Auvik Trial">Auvik Trial</a></h1></div>
|
||
|
|
<p>
|
||
|
|
Auvik was providing a 14 day trial to test out their platform.
|
||
|
|
</p>
|
||
|
|
|
||
|
|
<div id="Auvik Trial-The Trial"><h2 id="The Trial" class="header"><a href="#Auvik Trial-The Trial">The Trial</a></h2></div>
|
||
|
|
<hr />
|
||
|
|
<p>
|
||
|
|
I wasn't even aware of what Auvik even was until I came accross a "Use Auvik and win a free Ubiquity Switch" ad. The primary factor for me messing with their paltform was admittedly the free switch.
|
||
|
|
</p>
|
||
|
|
|
||
|
|
<div id="Auvik Trial-Their Platform"><h2 id="Their Platform" class="header"><a href="#Auvik Trial-Their Platform">Their Platform</a></h2></div>
|
||
|
|
<hr />
|
||
|
|
<p>
|
||
|
|
Unbeknownst to me, their platform was akin to something I've just recently been working with at work. A network monitoring server.
|
||
|
|
</p>
|
||
|
|
|
||
|
|
|
||
|
|
<div id="Auvik Trial-LibreNMS: At Work"><h2 id="LibreNMS: At Work" class="header"><a href="#Auvik Trial-LibreNMS: At Work">LibreNMS: At Work</a></h2></div>
|
||
|
|
<hr />
|
||
|
|
<p>
|
||
|
|
At work we use Solarwinds almost exclusively, but recently in the engineering dept we decided to setup our own NMS with <a href="https://www.librenms.org/">LibreNMS</a>. A process that I setup in a <a href="https://git.arcanium.tech/tristan/myscripts/src/branch/master/install-librenms.sh">script</a> for ease-of-use for anyone else wanting to try it. It is an amazing project and I highly praise it for all of the functionality it brings.
|
||
|
|
</p>
|
||
|
|
|
||
|
|
<p>
|
||
|
|
However, there are still some pain points with the project in terms of the network map. When viewing a network map, unless you've grouped up your devices in small enough network groups (doesn't help sometimes) your network map will be presented in a spider-web without any ability to resize or manipulate the map in any way (that makes it easier to read). Although this is where any gripes over LibreNMS starts and ends, as otherwise this is an amazing project that makes monitoring your network much more manageable.
|
||
|
|
</p>
|
||
|
|
|
||
|
|
<div id="Auvik Trial-Auvik"><h2 id="Auvik" class="header"><a href="#Auvik Trial-Auvik">Auvik</a></h2></div>
|
||
|
|
<div id="Auvik Trial-Auvik-Deployment & Setup"><h3 id="Deployment & Setup" class="header"><a href="#Auvik Trial-Auvik-Deployment & Setup">Deployment & Setup</a></h3></div>
|
||
|
|
<hr />
|
||
|
|
<p>
|
||
|
|
Deploying their solution was insanely easy. I took the route of deploying their collector via a docker container (they generate you a docker compose file) on my VM Server, which only took a few minutes to download the necessary images and start it. Very soon after it connected back to their platform and began scanning my internal network.
|
||
|
|
</p>
|
||
|
|
|
||
|
|
<div id="Auvik Trial-Auvik-Operation : Function"><h3 id="Operation : Function" class="header"><a href="#Auvik Trial-Auvik-Operation : Function">Operation : Function</a></h3></div>
|
||
|
|
<hr />
|
||
|
|
<p>
|
||
|
|
Within 10 minutes their collector had mapped out (just about) every single VLAN and network I had running in my homelab (even the vnets running on my VM server). It really suprised me how invasive it was.
|
||
|
|
</p>
|
||
|
|
|
||
|
|
<div id="Auvik Trial-Auvik-Operation : UX"><h3 id="Operation : UX" class="header"><a href="#Auvik Trial-Auvik-Operation : UX">Operation : UX</a></h3></div>
|
||
|
|
<hr />
|
||
|
|
<p>
|
||
|
|
With my experience with Solarwinds, Zabbix and LibreNMS I didn't expect much in the way of UX from Auvik. However, I was plesantly suprised. The UI & UX for their platform was outstanding. Everything is laid out well and everything is formatted in a way that makes everything easy to read.
|
||
|
|
</p>
|
||
|
|
|
||
|
|
<p>
|
||
|
|
For someone that despises Front-End work, I can appreciate the effort they've put into their product.
|
||
|
|
</p>
|
||
|
|
|
||
|
|
<div id="Auvik Trial-Overall"><h2 id="Overall" class="header"><a href="#Auvik Trial-Overall">Overall</a></h2></div>
|
||
|
|
<hr />
|
||
|
|
<p>
|
||
|
|
This is a really high-quality product I would like to use in my own lab, but due to it's black-box nature I wouldn't be ok with using it for my home network.
|
||
|
|
</p>
|
||
|
|
|
||
|
|
</body>
|
||
|
|
</html>
|