NEW! View OID monitor history
You can now store and view the history of OID (object identifiers) monitor in your device - a highly-voted idea in the Idea Portal.
Auvik will start collecting the historical values for OID monitors from Feb 1:
- For numeric monitors, a graph is shown.
- For string monitors, a table of all values or a table of updates is available.
With OID monitor history, you can troubleshoot transient issues to reduce time to resolution or observe trends for proactive planning. For more details, see this article.
IMPROVED! Device identification
We’ve improved device identification for 40 switches, 8 firewalls, 7 L3 switches, 7 routers, 5 access points, and printers including: switches from Asante Intracore, Cisco (Catalyst and SR), ConneXium, D-Link, Edgecore (FS and L3), EnGenius, Extreme Networks, Hirschmann RSPL, HP Aruba Networks, Huawei, Juniper QFX, Korenix, Nortel BES series, Ruckus ICX, TP-Link, and TRENDnet, routers from AdTran, Cisco ISRv, and Vanguard, firewalls from Cisco FirePOWER, D-Link, and Fortinet, access points from H3C and Fortinet, Allan Bradley PLC controllers, and printers from AccurioPress, Canon with Galaxy UPSes, HP, Ineo, Konica, and Sharp.
FIXED! Default gateway
We’ve fixed the issue with the creation of default gateway internet connections based on invalid IPv4 routes.
HEADS UP! Netgate pfSense billing changes
Auvik will classify pfSense devices as firewalls as we provide full firewall functionality on them. This change will affect all existing pfSense devices, starting Jan 29.
If you do not want these devices to be billable, they must be unmanaged. Changing the device type will not change if it’s charged as a billable device.
HEADS UP! AdTran billing updates
Auvik is changing the setting for AdTran Total Access 900 and 900e Series devices from the current default device type of a Router or VoIP Switch to a Telecommunications device by default. This change will be effective on Jan 29, 2022.
NOTICE! Removal of Cisco Meraki API v0 support
In preparation for Cisco's scheduled sunset of v0 API in February, we're automatically transitioning all of our monitoring to v1 API. There is no action required from customers. If you are interested to know more, read this Cisco support article.