2025-W18 Release - May 3rd

• • New
    • BGP Route Neighbor Monitoring

      BGP Route Neighbor Monitoring provides visibility into BGP peer relationships, helping network administrators quickly detect and diagnose connectivity issues. Users can track peer states, monitor state changes, and receive alerts when connections become unstable.

      As part of this beta release, users will gain access to a dedicated BGP monitoring table within the Debug > Routes view, allowing them to filter historical data and analyze peer connection stability over a 30-day period. Additionally, configurable alerts will notify users when key thresholds are breached, such as when a peer connection is lost, transitions too frequently, or remains unstable for extended periods.

      Key Capabilities in Beta

      • BGP Peer Monitoring Table – View real-time and historical BGP neighbor status, including peer IPs, BGP identifiers, connection states, and uptime.

      • State Change Alerts – Get notified when a peer relationship goes down, flaps frequently, or remains unstable.

      • Time-Filtered Data – Review BGP state transitions over a configurable time range to diagnose past incidents.

      In the beta, the neighbor state tables will appear on supported devices, (Cisco and Juniper) and customers will be able to create alerts. We encourage customers to participate in the beta and provide feedback to help shape the final implementation.

  • Improved
    • Server Monitoring Software Inventory
      • This feature provides visibility into the software installed across your server infrastructure, giving you the tools to stay compliant and troubleshoot faster.
      • Alert on High Disk Partition Storage Utilization on Servers
        • You can receive alerts when a disk partition exceeds a customizable storage utilization threshold, helping prevent service disruptions due to full disk partitions. Running out of disk partition space can lead to system crashes, application failures, and data loss. With this new alert, you can get early warnings before a critical threshold is hit, take corrective action, maintain system reliability and reduce time-to-resolution. This will be available on May 7th.
    • Roles & Permissions UI Update
      • We have made few changes to the Roles & Permissions UI that provides a cleaner and more consistent user experience, plus aligns with the under the hood backend improvements (a.k.a V2 Roles & Permissions) that we are making to moderinze our systems. Please note that these backend and frontend changes remain transparent to customers and no further action is required.
        
        What UI Changed and Why?

1. 1. 1. 1. Updated Roles Table Layout

• • • • • Removed: Settings cogwheel, Custom column—previously used to restore or reset roles.

        • This is done to simplify the Role management workflow, using Role templates instead of Reset & Restore previously.

Before	Revised

1. 2. New Look for “Add Role” Screen

• • • Clean, accordion-style sections make it easier to navigate large sets of permissions.
    • Modal replaced by a full-page panel for better visibility and workflow alignment with other parts of Auvik (like alerting).
    • Role Name now clearly marked as required.
    • Improved layout for permission levels with better tooltips—redundant ones (like "No Access – No Access") have been cleaned up.

Before	Revised

3.  Simplified “Edit Role” Permissions View

• • Clean, accordion-style sections make it easier to navigate large sets of permissions. 

Before	Revised

4. Using “templates” to create roles

• • Earlier one had to use the Clone operation, now one can use ‘Role template’ (optional)

  • Enables you to create additional roles faster using the templates and customize further as required

  • Note that templates are available only for the out-of-the-box roles that Auvik ships.

Before	Revised

For more details on managing users and roles, visit our User Management Help Center. If you have questions or feedback, our support team is always here to help.

• Fixed

  • Fortinet Switch Wiring Improvements - We've shipped an improvement for Fortinet Switches (Fortiswtiches) managed by a fortigate firewall. This should drastically improve wiring for customers that have the following:

    1. Fortigate API

    2. CLI enabled for the Fortigate.

  • Improvements will immediately be seen in switch to switch wiring and devices. A good way to know if this is working, check a switch's interfaces to see if MAC addresses appear.
    

  • Tunnel Status Monitoring for Palo Alto - The VPN tunnel alert is based on a tunnel being down or inactive. Auvik was not parsing inactive VPN tunnels. This has been resolved. The table should now update to reflect all tunnels for Palo Alto firewalls.

  • FortiOS API Improvements - We’ve resolved some issues that improve its stability. We also resolved an issue with the test connection functionality.

• Devices

  • Identifications

    • (13) L2 and L3 Switch(es)

      • Vendor(s): Allied Telesis, IMC Networks, BDCOM, RubyTech, Meraki, FS, RAD, TP-Link, Arista

    • (1) Router(s)

      • Vendor(s): Microhard Systems

    • (4) Printer(s)

      • Vendor(s): Konica Minolta, Toshiba, Sharp, Xerox

• • New
    • 14 Day Trial of Endpoint Monitoring and Server Monitoring
    • Alerts 2.0 Trigger Conditions, Device and Interface Properties
    • How to limit flow to a single IP address from a FortiLink device
  • Updated
    • Alerts 2.0: Notification Variables
    • Auvik collector and other system requirements
    • How do I add a Meraki cloud controller?
    • How do I get started with syslog?
    • How do I manage device health check frequencies?
    • Using Alerts 2.0
    • Creating Alerts using Alerts 2.0
    • How do I add, edit or delete user roles?