Important note about SSL VPN compatibility for 20.0 MR1 with EoL SFOS versions and UTM9 OS. Learn more in the release notes.

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

Sophos Firewall: v19.5 MR2: Feedback and experiences

Release Post:   Sophos Firewall OS v19.5 MR2 is Now Available  

The old V19.5 MR1 Post: Sophos Firewall: v19.5 MR1: Feedback and experiences 

To make the tracking of issues / feedback easier: Please post a potential Sophos Support Case ID within your initial post, so we can track your feedback/issue. 



This thread was automatically locked due to age.
Parents
  • This release appears to have broken our SNMPv3 monitoring.

    We use AES Encryption and MD5 Authentication (because that is the only combination that fits with our monitoring software) and since upgrading, we can't connect.

    I have tried deleting and recreating the settings on each end but it didn't fix it. For the moment we have changed to SNMPv2 monitoring.

  • Hi   Was this upgrade from 19.5MR1 to MR2? There is no known change in SNMP for 19.5MR2 from 19.5MR1. Dev team would like to investigate this more. Is it possible to share the device access id in private message to me /  . Also share the snmp config and remote command that is tried to check the connectivity. If access id not possible not , these log files may help  to start investigation - /log/snmp.log /log/syslog.log /log/csc.log , along with config -Shrikant

  • Yes the upgrade was from 19.5MR1 to MR2. Although there may have not been any changes in SNMP, clearly there have been changes in Administration access so something may have got unintentionally broken amongst those changes.

    For some reason, I have no option to message Avinash Aathreya but I can message ShrikantSophos. How would you like to proceed?

Reply
  • Yes the upgrade was from 19.5MR1 to MR2. Although there may have not been any changes in SNMP, clearly there have been changes in Administration access so something may have got unintentionally broken amongst those changes.

    For some reason, I have no option to message Avinash Aathreya but I can message ShrikantSophos. How would you like to proceed?

Children
  • Yes  - Please message me ie   . Will have it checked.

  • Hi   - We tested the migration from 19.5MR1 to 19.5MR2. Used a free SNMP Tool to retrieve sample OID which works without issues. As discussed over Live debugging session, pls help us with the snmpd logs & Packet capture (pcap) outputs for further analysis.

    Attached screenshot of FWVersion read across MR1 & MR2 for your reference.

  • I replied to your PM in some detail but when I 'sent' it, I got the message that I couldn't sent to you and all my text was lost Rage

    I used the same tool as you to test SNMPv3 and it worked. So I tried the tool I had been using previously, and that worked. So I switched our monitoring software back to SNMPv3 and that worked! I haven't made any changes since our debugging session on Friday.

    Last night I rebooted the XGS and our monitoring software to check that everything still worked, and it does. I have setup new credentials for SNMPv3 (as I had shared the previous credentials with you by email) and that worked fine too.

    It is very frustrating to have no idea of what the issue was but clearly there is nothing further we can do now. Hopefully it was just a 'one off' problem and that is the end of it.

    Thanks for your assistance with this.

  • Hey Jason, 

     Glad to know that the problem is resolved on your end. Agree its annoying when things start working w/o changes/ root causing. Feel free to reach out in case you run into the issue again. Also, you now have the debugging tips which I hope will be handy for any problems in future.

    Thanks,

    Avinash