Note: The following instructions also apply in general to most UniFi devices. The exception to this is the UDM / UDM-Pro which does not officially support SNMP via the UI. Workarounds require SSH access and manual editing of snmpd.conf.
1. Confirm UniFi Controller Configuration
- Log in to your UniFi Controller (UniFi Network Application).
- Navigate to:
Settings > System > SNMP - Ensure SNMPv1/v2c or SNMPv3 (as needed) is enabled.
- Validate the community string (e.g.,
public) or SNMPv3 credentials. - Save and apply any changes.
Note: SNMP is global in UniFi—there is no per-device SNMP toggle.
2. Validate the Switch Status
- Go to Devices > USW-<switch type> in the UniFi Controller.
<switch type> is the name of the switch.
For example a UniFi USW 24 PoE switch would be listed as USW-24-PoE
- Confirm the switch is:
- Adopted and online
- Running firmware version 4.0.42 or newer (recommended for SNMP support)
3. Test SNMP Locally
From a monitoring station (e.g., Auvik or a CLI machine), test with:
For SNMPv2c:
snmpwalk -v2c -c public <switch IP>
For SNMPv3:
snmpwalk -v3 -l authPriv -u snmpuser -a SHA -A authpass -x AES -X privpass <switch IP>
If the command times out or fails:
- Ensure UDP port 161 is open.
- Verify no ACLs/firewalls are blocking SNMP from your source IP.
4. Verify SNMP settings and switch status
UniFi generally manages SNMP from the UniFi Network Application or controller. There is typically no separate SNMP configuration toggle on each adopted switch. After changing the controller-level SNMP settings, allow the switches to reprovision.
Confirm that each affected switch is:
- Adopted and online in the UniFi controller
- Fully provisioned after the SNMP change
- Using the expected management IP and VLAN
- Reachable from the Auvik Collector on UDP port 161
SNMPv2c
Confirm that the SNMP community string configured in UniFi exactly matches the SNMP credential configured in Auvik. Use a read-only community string where supported.
SNMPv3
UniFi may use fixed SNMPv3 settings depending on the UniFi Network Application version. In supported configurations, confirm that Auvik uses:
- The same SNMPv3 username configured in UniFi
- SHA for authentication
- AES-128 for privacy
- The same password for both authentication and privacy, where UniFi provides only one password field
Test SNMP from the Collector network
If the device still reports incomplete data or does not respond, test SNMP from the Auvik Collector or a system with the same network path.
For SNMPv2c:
snmpwalk -v2c -c <community> <switch_management_ip> 1.3.6.1.2.1.1For SNMPv3:
snmpwalk -v3 -l authPriv -u <user> -a SHA -A <password> -x AES -X <password> <switch_management_ip> 1.3.6.1.2.1.1Successful output containing values such as sysDescr and sysName confirms basic SNMP reachability and authentication.
If basic SNMP succeeds but LLDP, LAG, interface, or topology data is incomplete, verify that the switch firmware and UniFi Network Application version expose the required MIB data. After making changes, allow several polling cycles for Auvik to refresh the device inventory and topology.
5. Check Device Logs via SSH
SSH into the switch:
ssh ubnt@<switch IP>
Once connected:
View SNMP process:
ps | grep snmp
Look for SNMP errors in logs:
cat /var/log/messages | grep snmp
If no SNMP process is running, the controller may not have pushed the SNMP config. Try force provisioning from the controller.
6. Review Auvik Integration
In Auvik:
- Go to the device page for the USW-24-PoE.
- Under Discovery Settings > SNMP, re-test credentials.
- Confirm the correct:
- SNMP version
- Community string or SNMPv3 credentials
If SNMP fails, Auvik will log the error—look for authentication errors or timeouts.
6. Additional Considerations
- No SNMP per-device toggle in UniFi—if global SNMP is disabled, no switch will respond.
- SNMP support may be limited in early firmware—update if necessary.
To restart SNMP:
sudo /etc/init.d/snmpd restart