2025-W37 Release - September 13th

Improved

• VPN Tunnel Status Handling

  We’ve improved how Auvik handles VPN tunnel status when devices stop reporting data. Previously, if we stopped receiving status information, the tunnel would disappear from view, which could prevent alerts from triggering. With this update, tunnels without incoming data will now be shown in an “unknown” state instead of being removed. Stale tunnels will be automatically cleaned up after a week.

• Improvements to Auvik’s Autotask PSA Inventory Sync

  We’re launching a suite of enhancements to Auvik’s integration with Autotask PSA—designed to improve accuracy when syncing devices.

  • What’s New:

    • Smarter Matching with Existing Configuration Items:

      • You now have the option to consider Configuration Item Status, Product, Configuration Item Category and Configuration Item Type when matching Auvik devices to existing configuration items in Autotask PSA.

      • This helps prevent updates to the wrong configuration items and ensures more accurate mapping between systems.

    • Optional Activation of Matched Configuration Items:

      • You can also choose to automatically set the status to active for configuration items matched to Auvik devices during the sync. This ensures that valid, in-use devices are not overlooked due to outdated status settings in Autotask PSA.

    • Optional Deactivation of Deleted Devices:

      • You can now configure the integration so that when a device is deleted in Auvik, the associated configuration item in Autotask PSA is automatically marked as inactive. This helps keep your PSA inventory clean and accurate without manual cleanup.

  You can configure these options in the Inventory tab when you edit your Autotask PSA integration.

  This will be available on September 11th.

• Collector Installation Issues on Ubuntu 22.04 / 24.04 – Fixed

  We identified an issue with the Debian package for collectors on Ubuntu 22.04 and 24.04, where an invalid binary could prevent the collector from connecting to the Auvik cloud. Also the install was failing because update-grub isn’t installed by default on Debian 12 (it’s just an alias for grub-mkconfig), and on Raspberry Pi devices, grub isn’t used at all—causing the process to break without proper checks. This resulted in collectors either

  • failing to appear on the site after installation or

  • repeatedly flapping between Running and Not Running states

• Fix:
  An updated Debian package has been published, and the scripted installer now uses this fixed version. New installations should no longer encounter issues on Ubuntu 22.04 or 24.04. We’ve tested Debian package successfully on

  • Ubuntu 22.04

  • Ubuntu 24.04

  • Debian 12 x86_64

  • Debian 12 Raspberry Pi

  Action Required (for existing installs):
  If you’ve experienced this issue, please re-install the updated Debian package. The following commands can help recover a broken install:
  
  sudo dpkg --configure -a 
sudo apt update 
sudo apt upgrade auvik-agent

  This ensures you are pulling the latest available packages from the repository.

• Meraki Integration Test Connection Handling

  We’ve updated the “Test Connection” feature so it now runs through the same Collector-based process used by real production connections. The change has been implemented in the backend to route test requests through the Collector, with added safeguards to match both successful and failed connection scenarios.

• Empty Device Name Sync Issues

  We’ve fixed an issue where devices without assigned names—including the default Device@IP format—could cause inventory sync failures with Autotask, ConnectWise, and ServiceNow. This typically happened when a device had no IP address, preventing the assignment of a default name.

Coming Soon

• Improvement to Cloning in Alerts V2: Option to Detach Sites from the Original Alert Definition

  We’ve enhanced the alert cloning experience in Alerts V2 to help you better manage alert coverage across your sites—faster and with less manual work.

  Now, when you clone an alert definition, Auvik will ask if you’d like to remove the selected sites from the original alert definition. If you choose “Detach,” those sites will be removed from the original, and the cloned alert definition will apply only to them.

  This improvement simplifies a previously manual task, saving time and reducing the chance of configuration errors when segmenting alert behavior across sites.Devices

• Identifications

  • (17) L2 and L3 Switch(es)

    • Vendor(s): Duxbury, Juniper, ADVA, PLANET, Transition, HP, LANCOM, Allied Telesis, Meraki, BDCOM, United

• OSPF Neighbor Metrics & Alert Guide
• Enable SNMP and Login for Ubiquiti UniFi Controller
• Troubleshooting Configuration Backups in Auvik
• How does Auvik's Remote Support for servers and workstations
• What Auvik Handles vs. What Customers Need to Manage

• How many syslog messages can a site send to Auvik
• Configure Auvik for inventory sync to Autotask PSA
• How to install the Auvik collector from a bash script
• How do I add a Meraki cloud controller?
• Configuring Aruba Central to work with Auvik
• How do I troubleshoot issues with my Auvik Microsoft Teams integration?
• Troubleshooting Fortinet device API credentials
• Intercom SaaS Ops Integration
• Creating Alerts using Alerts v2
• Creating Alert Notifications using Alerts v2
• How to configure NetFlow on MikroTik RouterOS devices