Uploaded image for project: 'ZABBIX BUGS AND ISSUES'
  1. ZABBIX BUGS AND ISSUES
  2. ZBX-8145

SNMP getbulk (combining varbinds): detection of success/failure not clear

XMLWordPrintable

    • Icon: Incident report Incident report
    • Resolution: Duplicate
    • Icon: Minor Minor
    • None
    • 2.2.3
    • Server (S)
    • Linux "Ubuntu 12.04.4 LTS"

      Since ZBXNEXT-98 implemented, i have some problems due to my particular SNMP device does not cooperate properly with Zabbix's Artificial Intelligence, in part of success/failure detection of combined SNMP retrieval.
      Please read more here: https://www.zabbix.com/forum/showthread.php?t=45001
      I use microcontroller device and assembler SNMP stack, code is available here http://bdyssh.ru/?p=988
      But looks like most uC-based simple SNMP stacks not capable with bulk answers. Example is another code, http://code.google.com/p/agentuino/ where this fact is not clearly stated, but 'limitations' looks like there is no place for 2nd variable (153-64-64-20 bytes).
      My device answers with 1 variable when requested more than one, Zabbix (probably) treat that fact as successful answer, and continues bulk requests, so half of data is lost.
      Possible solutions:
      1. Make bulk requests optional (as i comment at ZBXNEXT98). This is strongly most preferable, because not only immediately solve my issue and other possible related problems, but also, as can be seen at forum thread, will stop to introduce other problems, which are not related with proper detection at all. It is also most simple and quick and not affect other installations.
      2. Make Zabbix's Artificial Intelligence more smart.
      3. Turn all SNMP stacks for low-RAM devices to be compatible with current Zabbix behaviour: not sure if it possible at all.
      Thank you so much.

            Unassigned Unassigned
            jpka jpka
            Votes:
            3 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: