Effective IP address management plays a critical role in ensuring accurate, stable, and reliable monitoring within Auvik. Devices that frequently change IP addresses can lead to gaps in monitoring, missed alerts, and fragmented historical data.
This article outlines recommended IP addressing strategies for devices monitored by Auvik to help ensure consistent visibility and performance across your network.
Why IP Address Stability Matters
Auvik relies on IP-based communication for:
Device discovery and identification
SNMP polling and data collection
Syslog and NetFlow traffic analysis
Alerting and performance monitoring
Historical reporting and device correlation
When a device’s IP address changes unexpectedly:
Monitoring may temporarily fail
Alerts may not trigger correctly
Historical data may become fragmented across multiple device records
Manual intervention may be required to re-link devices
Maintaining stable IP assignments minimizes these risks.
Recommended IP Addressing Strategies
1. Best Practice: Static IP Addresses (Strongly Recommended)
For critical, always-monitored infrastructure, static IP addressing is the preferred approach.
Recommended for:
Auvik Collectors
Firewalls
Managed switches
Routers
Wireless controllers
Key servers and infrastructure systems
Benefits:
Ensures consistent monitoring and alerting
Eliminates risk of unexpected IP changes
Simplifies troubleshooting and device management
Preserves clean, continuous historical data
2. Next Best Option: DHCP with Reservations
In DHCP-based environments, reservations provide a reliable alternative to fully static addressing.
Recommended for:
Wireless access points
Edge network devices
Devices where static configuration is operationally impractical
How it works:
The DHCP server assigns the same IP address to a device based on its MAC address
The device still uses DHCP, but its IP remains stable
Benefits:
Maintains IP consistency without manual configuration on each device
Reduces administrative overhead
Fully supported by Auvik
3. Not Recommended: Dynamic DHCP Without Reservations
Using fully dynamic DHCP for important monitored devices is discouraged.
Risks:
IP address changes can disrupt monitoring
Devices may appear as new or duplicate entries
Alerting and historical data continuity may break
Increased need for manual cleanup or device re-linking
Summary of Recommendations
| Device Type | Recommended Approach |
| Core infrastructure (firewalls, routers, core switches) | Static IP (strongly recommended) |
| Wireless APs and edge devices | DHCP with reservations |
| Non-critical or transient devices | Dynamic DHCP (acceptable) |
| Important monitored devices on dynamic DHCP | Not recommended |
When to Use Each Approach
Use static IPs when stability and continuous monitoring are critical
Use DHCP reservations when operational efficiency is needed without sacrificing stability
Avoid unreserved DHCP for any device that Auvik depends on for consistent monitoring
Related Articles
The following Auvik articles provide additional context for deployment, discovery, and device management:
-
What protocols and ports does the Auvik collector use?
(Reinforces the importance of stable IPs for communication and monitoring)
-
(Covers onboarding and preparation of monitored devices)
-
How to manually link an IP to a device in Auvik
(Useful when IP changes have already caused device duplication or fragmentation)
Conclusion
Consistent IP addressing is a foundational requirement for reliable network monitoring in Auvik.
Whenever possible, use static IP addresses for critical infrastructure and DHCP reservations for edge devices. Avoid relying on dynamic DHCP for important systems to prevent monitoring disruptions and ensure accurate, continuous visibility across your network.