Ad Widget

Collapse

« cannot read from session: Bad parse of ASN.1 type »

Collapse
This topic has been answered.
X
X
 
  • Time
  • Show
Clear All
new posts
  • Takaya
    Junior Member
    • Jan 2024
    • 7

    #1

    « cannot read from session: Bad parse of ASN.1 type »

    Hello,

    I have a Zabbix 7.0.6, proxies in passive mode, I'm using items with SNMP agent, devices configured in SNMPv3 SHA1 AES1 and I'm encountering an issue on some devices. I have an alert on each item of the device that says : « cannot read from session: Bad parse of ASN.1 type » (Images below). When I interrogate directly the OIDs from the proxy, I've got an immediate result and when I test the item I also have a result. I either use a group of proxies or a proxy directly and sometimes I solve the issue by affecting an other proxy but I still have devices that can't work. (of course I've restarted zabbix-proxy service, zabbix-server proxy, removed the equipment, imported it back ...)
    Click image for larger version

Name:	image.png
Views:	1353
Size:	105.0 KB
ID:	496605



    Click image for larger version

Name:	image.png
Views:	1435
Size:	38.2 KB
ID:	496604​​


    Would you have any idea of how to solve this issue ? Is this an already known issue ?

    Thank you !
  • Answer selected by Takaya at 13-01-2025, 09:36.
    Takaya
    Junior Member
    • Jan 2024
    • 7

    I've found the issue. The problem comes from the monitored device. It's engine ID is not unique on your network. Two devices, at least, share the same. You can retrieve the engine through a SNMP test using get[1.3.6.1.6.3.10.2.1.1.0]. You can generate an unique engine ID on your network equipments on CLI or GUI, this accepted on cisco, arista, alcatel ...

    Comment


    • TechPulse_98
      TechPulse_98 commented
      Editing a comment
      You just made my day. Thank you very much!
  • TechPulse_98
    Junior Member
    • Oct 2024
    • 2

    #2
    I have the exact same problem since I switched from SNMPv2c to SNMPv3. I have a mixture of proxies and proxy groups and use sha1 and aes128. Randomly some devices encounter this error, they do not resolve by themselfes, however if i manually execute them, they recover. Help would be greatly appreciated.

    Comment

    • Takaya
      Junior Member
      • Jan 2024
      • 7

      #3
      I've found the issue. The problem comes from the monitored device. It's engine ID is not unique on your network. Two devices, at least, share the same. You can retrieve the engine through a SNMP test using get[1.3.6.1.6.3.10.2.1.1.0]. You can generate an unique engine ID on your network equipments on CLI or GUI, this accepted on cisco, arista, alcatel ...

      Comment


      • TechPulse_98
        TechPulse_98 commented
        Editing a comment
        You just made my day. Thank you very much!
    Working...