Thread Info
Options
Suggested
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 Issue with EngineID not populated but the service is running

Edouard Fazenda

Dear Sophos Community,

I have noticed that sometimes after reboot of the firewall or upgrade of the firewall sophos, the SNMP Server on the firewall is not populated the EngineID, so SNMP V2 is working without any issue as it does not need Engine ID , but SNMPv3 the Engine ID is required , so my monitoring is failling to query the device using SNMPV3

I need to restart the service SNMP from the Advanced Shell on the Sophos Firewall  using this command : service snmpd:restart -ds nosync

I am running the latest Firmware.

I think there is a bug on the SNMPd Server maybe the version of 5.9.3 has an issue with that.

Could it be cool to have this fixed :)

Have a nice day

Best Regards. Edouard Fazenda.



This thread was automatically locked due to age.
  • 0

    Hello,

    I may recommend you open a support case to have this further checked and investigated. 

    Kindly share with us the caseID once you have it. 

    Regards,

    Raphael Alganes
    Global Community Engineer, Support & Services
    Are you a Sophos Partner? | Product Documentation | @SophosSupport | Sign up for SMS Alerts
    If a post solves your question, please use the 'Verify Answer' button.

    The award-winning home for Sophos Support videos! - Visit Sophos Techvids

    • 0

      I do not exactly understand your issue, but SNMP triggered me. Just yesterday, we've noticed 2 of our v21 Firewalls were no longer accessible from our Network Monitoring via snmpv3 since we've rebooted them a few days ago as a regular maintenance task. Other firewalls were fine.

      snmpd.log was not showing unexpected things, service was running.

      Restarting the service from CLI did not fix it either.

      What fixed it was to re-apply the SNMP config from the GUI.

      after that the machines were read again by our monitoring system.

    • +1

      Hi  

      This is a known bug and has been fixed in v21MR1. 

      Thanks,

      • 0

        One of our Sophos XGS (HA Active-Passiv) with SFOS v21.0.0 GA did have the same issue with SNMPv3 "Unknown engine ID".

        Restarting the snmpd service fixed it.

        It did happen after switching from Active to Passive HA Node.