Uploaded image for project: 'ZABBIX FEATURE REQUESTS'
  1. ZABBIX FEATURE REQUESTS
  2. ZBXNEXT-1620

Discovery action to add SNMP interface (when no snmp can be discovered - traps only)

XMLWordPrintable

    • Icon: New Feature Request New Feature Request
    • Resolution: Unresolved
    • Icon: Minor Minor
    • None
    • None
    • Server (S)

      Native support of snmp traps in the 2.0 is really cool but I don't understand one thing. Why there has to be a snmp interface to be able to create snmp trap type items?
      There are many devices that don't have snmp daemon running but are capable of sending traps. Zabbix can find them by using network discovery (ping) when there is a separate management network for such devices, but template containing snmp trap items cannot be linked due to the lack of the proper interface. Simply because discovery by ping does not create snmp interface on host.
      I have also considered the possible workarounds - using api to create the snmp interfaces with my custom script, or to route 161 port to some host that has snmp daemon and add some dummy snmp discovery check.

      But it would be nice to be able to create snmp trapper items also directly on the agent interface or better yet to be able to create snmp interface (even if the host does not answer to snmp requests) as a discovery action.

            Unassigned Unassigned
            arli Arli
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: