There are a couple of common reasons why Auvik’s cloud ping service might not begin to monitor an Internet connection automatically.
ICMP is blocked
Auvik’s cloud ping service uses ICMP echoes as a “heartbeat test” to determine whether or not the firewall’s WAN interface has a successful connection to the Internet.
It’s common practice for network administrators—and a default setting on many firewalls—to block ICMP echo requests from hosts on the Internet (i.e., from publicly addressable address space).
Therefore, to make use of Auvik’s internet connection check, you’ll need to allow ICMP from Auvik’s ping server IP addresses: 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, and 18.104.22.168.
The firewall isn’t fully discovered
Your Auvik collector is deployed on a LAN. Therefore, it initially only associates your firewall with (possibly one of) its private LAN IP addresses.
Auvik attempts to discover your firewall’s WAN IP address(es) using data returned from SNMP. If we’re can’t retrieve the address, the Internet connection won’t be checked automatically.
Explicitly set up the cloud ping check to ping your firewall’s WAN IP address(es). See the image below for an example where your public static IP address is 22.214.171.124.
If your firewall has multiple WAN IP addresses, you’ll need to create a separate cloud ping service for each.