Auvik can detect virtualized pfSense instances, but there are a few caveats and setup steps to ensure accurate detection and monitoring:
Key Points:
-
SNMP Configuration is Critical
Auvik primarily relies on SNMP for device discovery and monitoring. You need to:
-
Enable SNMP on pfSense.
You can enable SNMP from the pfSense web interface by navigating to Services > SNMP, checking Enable the SNMP Daemon and its controls, and configuring the necessary settings.
-
Ensure SNMP is accessible from the Auvik collector (firewall rules, interfaces, etc.).
By default, pfSense blocks SNMP traffic on the WAN interface. You need to create a firewall rule to allow SNMP communication.
- Use SNMPv2 or SNMPv3 as appropriate.
-
-
Virtualization Context
Virtualized pfSense devices may not report some hardware attributes (like physical interfaces) the same way as physical appliances. This might affect:
- Interface labeling and discovery.
This can lead to Auvik classifying the device generically.
-
SNMP Poller(OID) Coverage and MIBs
Auvik may not fully recognize pfSense unless the correct SNMP pollers(OIDs) are exposed. pfSense uses standard FreeBSD MIBs, but custom or limited SNMP pollers(OID) sets can result in generic classification. Ensuring that all relevant SNMP modules are enabled can help Auvik accurately classify and monitor the device.
-
Ensure Device Polling Works
After SNMP setup, verify in Auvik:
- At least one of the device’s IP addresses is pingable from the Auvik collector that’s assigned to scan its network
- The device is responding to SNMP queries on that IP address.
- You can see system info, interfaces, and routing tables.
Use tools to test SNMP communication and ensure the device responds correctly. If needed, you can leverage your Auvik collector’s built-in SNMP poller. Click here for more information.
5. Custom Device Roles (if needed)
If pfSense isn’t auto-identified correctly, you can manually assign a role or label in Auvik to assist with visualization and alerts.