I can not get PRTG to connect to my Sonicwall Firewall using SNMPv3.
I've configured the MD5 Authentication Key and AES Privacy Key the same on the device and the monitor. I've attempted it with using the Sonicwall Engine ID as the context name, and without a context name but that did not help.
Article Comments
Hello there,
we appreciate your contact.
The context name should only be necessary if you have multiple virtual routers or firewalls. In most cases, working with a blank context name is enough.
I encourage you to download our latest SNMP Tester, run it on the PRTG Host (or host of the Remote Probe), and perform the "Read Device Uptime" test against the target device, it will allow you to easily test different credential combinations.
Once you've confirmed the correct SNMP V3 credentials, enter them in PRTG. Due to an existing bug/issue in PRTG I strongly advise you to restart the "PRTG Probe Service" on the relevant PRTG Probe after updating or configuring SNMP V3 credentials in PRTG.
Please let me know how it goes.
Best Regards,
Luciano Lingnau [Paessler Support]
Nov, 2018 - Permalink
Hello there,
we appreciate your contact.
The context name should only be necessary if you have multiple virtual routers or firewalls. In most cases, working with a blank context name is enough.
I encourage you to download our latest SNMP Tester, run it on the PRTG Host (or host of the Remote Probe), and perform the "Read Device Uptime" test against the target device, it will allow you to easily test different credential combinations.
Once you've confirmed the correct SNMP V3 credentials, enter them in PRTG. Due to an existing bug/issue in PRTG I strongly advise you to restart the "PRTG Probe Service" on the relevant PRTG Probe after updating or configuring SNMP V3 credentials in PRTG.
Please let me know how it goes.
Best Regards,
Luciano Lingnau [Paessler Support]
Nov, 2018 - Permalink