2025-W12 Release - March 22nd, 2025

Auvik Alerting 2.0 Improvement

• When editing alert definitions with changes that don’t directly impact the triggering of an alert, users now have the option to not clear existing triggered alerts.

Improved Page Load Performance for All Alerts

• As part of our ongoing scalability initiatives, we’ve significantly enhanced the performance of the ‘All Alerts’ page. These improvements reduce the time it takes to load alert data—delivering a noticeably faster and smoother experience, especially for customers with large alert volumes.

• To ensure optimal usability even with high alert counts, we now prioritize loading the most recent 25,000 alerts first, allowing you to start interacting with the latest data immediately. The remaining alerts are then progressively loaded in the background.

• This change ensures that even during periods with large volumes of alerts, you can access critical information faster and with minimal delay.
  

Fortigate API - We’ve improved our retry logic and addressed an internal bug for the Fortigate API so that the collector can handle a lack of API responses better.

Incorrect Device Identification – MacBooks were mistakenly identified as APC UPS devices, leading to erroneous offline alerts and incorrect device classifications.

Cisco Nexus Switch Model Misidentification – Nexus 5600 series switches were erroneously identified as Nexus 6000 series due to incorrect model mapping, which was corrected.

Cloud Ping Check Service Issues – The 5-second interval option for cloud ping checks was removed to prevent performance degradation.

Fortinet Access Points Generating Excessive Alerts – Fortinet FP231F access points erroneously triggered "network element offline" alerts due to a flaw in the consolidation process.

VMware Components, Device Components and VPN Tunnel Status alerts evaluated the items device-wide. They have been split out into individual items for alerting purposes. This will be fixed on March 25th.

Upcoming Feature: BGP Route Neighbor Monitoring (Beta Release - April)

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.

This will be available in beta starting in April for Cisco devices, with general availability planned in future releases. In the beta, the neighbor state tables will appear on supported devices 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.

Identifications

• (11) L2 and L3 Switch(es)

  • Vendor(s): Linksys, Sodola, TP-Link, Allied Telesis, Phoenix Contact, HP, Arista, Netgear, FS

• (7) Access Point(s)

  • Vendor(s): Netgear, Meraki, Cambium, Aruba, H3C

• (2) Router(s)

  • Vendor(s): UfiSpace, OneAccess

• (2) Firewall(s)

  • Vendors(s): Fortinet

• (5) Printer(s)

  • Vendor(s): FUJIFILM, Samsung, Sharp, Océ Technologies