Overview
If a WAN interface no longer appears under All Internet Connections, Auvik is no longer identifying that interface as an Internet gateway. This is typically caused by changes to routing, gateway discovery, or network topology.
This article outlines the most common causes and the steps you can take to verify your network configuration.
How Auvik Identifies Internet Connections
Auvik uses routing information collected from your network devices to identify Internet connections.
In general, an interface can be identified as an Internet connection when:
- A default route (
0.0.0.0/0) exists on the monitored device. - The default route points to a valid next-hop gateway.
- The gateway device can be discovered and monitored by Auvik.
- The interface is available to be identified as an Internet connection.
If one or more of these conditions change, the interface may no longer appear in All Internet Connections.
Step 1: Verify the Default Route
Check the routing table on your router or firewall to confirm that a default route is still configured.
Depending on your device, you can use commands such as:
| Vendor | Example command |
|---|---|
| Cisco IOS/IOS-XE | show ip route |
| Juniper | show route |
| FortiGate | get router info routing-table all |
| Palo Alto Networks | show routing route |
| Linux | ip route |
Confirm that:
- A default route (
0.0.0.0/0) is present. - The next-hop gateway is the expected address.
- The default route has not recently changed.
If the default route is missing or points to a different gateway, Auvik may no longer identify the original WAN interface.
Step 2: Verify the Gateway Device Is Discovered
If the default route points to another device, verify that Auvik is successfully discovering that gateway.
In Auvik:
- Open Inventory.
- Locate the gateway device.
- Confirm that the device is online and being monitored.
If the gateway device is not present or is no longer communicating with Auvik, the Internet connection may not be displayed.
Step 3: Check the WAN Interface
Open the monitored device in Auvik and review its interfaces.
Verify that:
- The expected WAN interface is present.
- The interface is operational.
- The interface has the expected IP address.
If the interface is down or has been reconfigured, it may no longer qualify as the Internet connection.
Step 4: Review Recent Network Changes
Consider whether any recent changes were made to your network, such as:
- Changing the default gateway.
- Updating routing protocols or static routes.
- Replacing or reconfiguring a firewall or router.
- Renumbering WAN IP addresses.
- Making topology or cabling changes.
Even temporary routing changes can cause Auvik to stop identifying an interface as an Internet connection until the routing information stabilizes.
Step 5: Check for Device Communication Issues
If the router or firewall has recently gone offline or stopped responding to SNMP, Auvik may not have current routing information.
Review:
- Device status in Auvik.
- Recent alerts for the device.
- SNMP connectivity.
- Collector connectivity (if applicable).
If the Issue Persists
If you've completed the checks above and the WAN interface is still missing:
Collect the following information before contacting Auvik Support:
- The name of the affected device.
- The name of the missing WAN interface.
- Approximately when the issue began.
- Any recent routing or network configuration changes.
- A copy or screenshot of the device's routing table showing the default route.
- Screenshots of the device's interface list in Auvik.
Providing this information will help Support determine whether the issue is related to routing, device discovery, or another networking condition.