Introduction
If a device appears offline in Auvik but is still accessible from your workstation, the issue is often related to communication between the Auvik collector and the device rather than the device itself. This article outlines common causes of device reachability issues and the recommended troubleshooting steps.
Symptoms
A device is displayed as Offline in Auvik, but you can:
- Ping the device from another system.
- Access the device's web management interface.
- Confirm that the device is powered on and operational.
Common Causes
Device reachability issues can occur for several reasons, including:
- Required management protocols, such as ICMP, are blocked or rate-limited.
- Firewall rules or access control lists (ACLs) block communication between the Auvik collector and the device.
- The Monitored IP configured in Auvik does not match the device's current management IP address.
- Duplicate IP addresses on the network cause inconsistent connectivity.
Resolution
Step 1: Test Connectivity from the Auvik Collector
Run a ping test from the Auvik collector to the device's management IP address:
ping <device_ip>If the ping is unsuccessful, the collector cannot reach the device, and the issue is likely related to network connectivity rather than Auvik.
Depending on the collector, you can log in to the collector's shell by following the steps in this artilce: Diagnose issues using discovery scanning with the Auvik collector?
Step 2: Verify Firewall and Network Policies
Ensure that no firewall rules, ACLs, or security policies are preventing communication between the collector and the device.
Confirm that ICMP traffic is permitted between the collector's IP address and the device's management interface. If your environment uses additional management protocols for monitoring, verify that they are also allowed.
Step 3: Verify the Monitored IP Address
Open the device details in Auvik and verify that the Monitored IP matches the device's current management IP address.
If the monitored IP is incorrect, update the device configuration or resolve the underlying addressing issue before continuing.
Step 4: Check for Duplicate IP Addresses
Duplicate IP addresses can cause devices to appear intermittently online or offline.
Review the following on the network infrastructure:
- ARP tables
- MAC address (CAM) tables
- DHCP lease information, if applicable
Resolve any IP conflicts before rescanning the device in Auvik.
Additional Considerations
If the device responds to pings from another workstation but not from the Auvik collector, compare the network path between each source and the device. Differences in VLANs, routing, firewall policies, or security controls may prevent the collector from reaching the management interface.
Summary
When a device appears offline in Auvik, begin troubleshooting from the perspective of the Auvik collector. Verify that the monitored IP address is correct, confirm the collector can successfully ping the device, ensure network policies allow communication, and check for duplicate IP addresses. In most cases, these steps identify the underlying cause of device reachability issues.
Assumptions
- An Auvik collector is deployed and responsible for monitoring the affected device.
- The device is expected to respond to ICMP echo requests.
- The collector has a valid network path to the device's management interface under normal operating conditions.