This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

SNMP Stops Responding

We have about a dozen XG's deployed. Most of them are physical with a couple of VMs as well. I have a LibreNMS server configured to monitor all of our client firewalls which has worked very well with the SonicWALLs that we support and seemingly fine with SFOS 17.0.6 or 17.0.8.

Things changed when I started upgrading to 17.1.1 MR-1. We started getting false positives that the firewall was down, usually it would fail a single check, then the subsequent check 5 minutes later would succeed and report the XG was online. Checking the firewall itself and discussing with our clients we could confirm that the firewall had never actually gone down. This was a relatively minor nuisance, but needed resolved. On it's release I upgraded a couple of the XGs to 17.1.2 MR-2 which appeared to resolve the problem on those two devices so I started upgrading all of the 17.1.1 MR-1 devices to 17.1.2 MR-2.

Fast forward to today, I have 7 of our XGs running 17.1.2 MR-2. Four seem to behave normally and three of those randomly stop responding to SNMP completely. A reboot fixes the problem but isn't a practical fix for obvious reasons. The three that I have trouble with are a mix. One XG125, one XG135, and a Hyper-V VM. The firewalls continue to work normally and respond to pings, but LibreNMS shows them down and attempts to snmpwalk from the NMS server time out. I haven't found anything helpful in the logs so far.

I'm curious if anyone out there has seen SNMP issues with the 17.1.x releases or might have any insight into what's going on here. Thanks!



This thread was automatically locked due to age.
Parents Reply Children
  • Thank you for the follow-up. Of the three problematic 17.1.2 MR2 firewalls we have in production I have only updated one to 17.1.3 MR3, which I did yesterday morning (10/04/2018). Thus far that unit has been behaving significantly better. The UI is much more responsive and for the past 24 hours I have not lost SNMP monitoring, so I am hopeful.

    I will coordinate upgrades on the two remaining problematic firewalls ASAP and update this post. If I do experience continued issues with either of the units I will follow the steps laid out in https://community.sophos.com/kb/en-us/132863 as requested.

     

    Thanks again!

  • Quick update. About 45 minutes ago the first firewall that I updated to 17.1.3 MR3 (on 10/4 as mentioned above) just caused our monitor to display a message that it rebooted (it didn't) and has completely stopped responding to SNMP queries again. Also the web UI is almost unusable, frequently hangs with the spinning wheel and sometimes page refreshes kick me back to the login screen.

    Looks like we don't have a true fix on our hands yet in 17.1.3 MR3. I'll look into the Advisory KBA that posted above and get back to you all.

  • You'll have to call support to apply a hotfix to MR3 to solve the Garner related issues. I've had them patch 10+ firewalls and so far they've been okay.