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 XGS 3100 SNMP V3 Trap not working

Hello everyone
we are currently testing the shipment of SNMP V3 traps. Unfortunately, we notice that new engine IDs are constantly being sent by Sophos.
Sending the traps with V2C works fine.

I've been testing all morning and looking at the trap receiver with tshark to see what arrives. After entering the EngineID in the snmptrad and triggering a trap on the Sophos again, I get a different EngineID.
Where can I read the EngineID on Sophos?
Another member had the problem 10 months ago, but he was not helped.
community.sophos.com/.../snmp-v3-trap

Greeting
Sascha Bay



This thread was automatically locked due to age.
Parents
  • Hi  Thank you for reaching out to the Sophos community. I have tried to check in the local LAB XG Device to get an engine ID and it remains the same or unique for me. 

    $snmpwalk -v 3 -u vishallabsnmp -l authPriv -a MD5 -A ZZZZZZZZZZZZ -x AES -X BBBBBBBBBBBB 192.168.114.60 1.3.6.1.6.3.10.2.1.1.0
    iso.3.6.1.6.3.10.2.1.1.0 = Hex-STRING: 80 00 1F 88 80 C7 1C 78 2A C0 4B F7 63

    I would suggest logging a support case to check and confirm further in your existing setup to validate and drive the investigation further. Please also share the Support case here for reference if it is already open to work on it.

    Regards,

    Vishal Ranpariya
    Technical Account Manager | Sophos Technical Support

    Sophos Support Videos | Knowledge Base  |  @SophosSupport | Sign up for SMS Alerts |
    If a post solves your question use the 'Verify Answer' link.

  • Hi Vishal,

    thanks for the SNMP Query.

    I'd found the EngineID, but this EngineID is another than i received by TRAPS. We will raise a support ticket.

    Regards

    Sascha

Reply Children
No Data