No announcement yet.

Zabbix 1.8.1 - Discovery SNMPv2

  • Filter
  • Time
  • Show
Clear All
new posts

    Zabbix 1.8.1 - Discovery SNMPv2

    Hello all,

    I am currently trying to discover a network of Cisco switches using the auto-discovery feature in Zabbix 1.8.1 but without success. I have tried the ICMP discovery and that works, it finds all the devices in a given network.

    But SNMPv2 returns absolutely nothing. Just to be sure, here is the /tmp/zabbix-server.log output when I start the server:

    21672:20100223:071858.020 Starting zabbix_server. Zabbix 1.8.1 (revision 9702).
     21672:20100223:071858.020 **** Enabled features ****
     21672:20100223:071858.020 SNMP monitoring:       YES
     21672:20100223:071858.020 IPMI monitoring:       YES
     21672:20100223:071858.020 WEB monitoring:        YES
     21672:20100223:071858.020 Jabber notifications:  YES
     21672:20100223:071858.020 ODBC:                   NO
     21672:20100223:071858.020 SSH2 support:           NO
     21672:20100223:071858.020 IPv6 support:           NO
     21672:20100223:071858.020 **************************
     21673:20100223:071858.028 server #1 started [DB Cache]
     21682:20100223:071858.030 server #10 started [Trapper]
     21683:20100223:071858.031 server #11 started [Trapper]
     21684:20100223:071858.031 server #12 started [ICMP pinger]
     21685:20100223:071858.031 server #13 started [Alerter]
     21686:20100223:071858.031 server #14 started [Housekeeper]
     21686:20100223:071858.031 Executing housekeeper
     21687:20100223:071858.032 server #15 started [Timer]
     21689:20100223:071858.032 server #17 started [Node watcher. Node ID:0]
     21691:20100223:071858.033 server #18 started [HTTP Poller]
     21672:20100223:071858.033 server #0 started [Watchdog]
     21680:20100223:071858.055 server #8 started [Trapper]
     21674:20100223:071858.057 server #2 started [Poller. SNMP:YES]
     21676:20100223:071858.057 server #4 started [Poller. SNMP:YES]
     21675:20100223:071858.057 server #3 started [Poller. SNMP:YES]
     21677:20100223:071858.058 server #5 started [Poller. SNMP:YES]
     21679:20100223:071858.058 server #7 started [Trapper]
     21681:20100223:071858.058 server #9 started [Trapper]
     21688:20100223:071858.062 server #16 started [Poller for unreachable hosts. SNMP:YES]
     21695:20100223:071858.062 server #21 started [Escalator]
     21692:20100223:071858.062 server #19 started [Discoverer. SNMP:YES]
     21694:20100223:071858.062 server #20 started [DB Syncer]
     21678:20100223:071858.087 server #6 started [Poller. SNMP:YES]
     21686:20100223:071900.552 Deleted 0 records from history and trends
    And here is the SNMPv2 discovery configuration:

    IP Address range:
    Delay: 600 (for testing purposes)
    Type: SNMPv2 agent
    Port: 161
    Community: MyCommunity
    OID: .

    I have tested my parameters using the snmpget command successfully. However, unlike the ICMP discovery, absolutely nothing happens in the Monitoring>Discovery screen and nothing appears in the server log.

    What am I doing wrong?

    Thanks for any help!

    Zabbix 1.8.1 - Discovery SNMPv2 Continued

    Ok, I did some further testing, I validated that the discovery process actually takes place, using the command tcpdump, I managed to verify that the server actually did an snmp sweep using the configuration I gave it and here is an example of a successful SNMP query:

    09:46:49.360139 IP >  C=MyCommunity GetRequest(28)  system.sysObjectID.0
    09:46:49.367948 IP >  C=MyCommunity GetResponse(37)  system.sysObjectID.0=[|snmp]
    So given that the zabbix server does its job, sweeps the IP range and gets confirmed snmp responses, why doesn't it show up in the Monitoring>Discovery screen?

    Could anyone point me a direction? /tmp/zabbix-server.log isin't much help right now...

    Thanks for any input!


      Found something...maybe

      Hello all,

      I switched the debug level of the server to 4 in the zabbix-server.conf file and restarted the zabbix server. I noticed something that seems off:

       In process_check()
       24398:20100223:104843.660 process_check() port:161
       24398:20100223:104843.660 In discover_service()
       24398:20100223:104843.660 In get_value_snmp() key:'' oid:''
       24398:20100223:104843.660 In snmp_open_session()
       24398:20100223:104843.660 SNMP [[email protected]:161:161]
       24398:20100223:104843.660 End of snmp_open_session()
       24398:20100223:104843.660 Standard processing
       24398:20100223:104843.660 In snmp_normalize(oid:
       24398:20100223:104843.660 End of snmp_normalize():
       24398:20100223:104843.660 In get_snmp(oid:
       24398:20100223:104843.668 Status send [0]
       24398:20100223:104843.668 AV loop OID [] Type [0x06] 'OID: SNMPv2-SMI::enterprises.9.1.359'
       24398:20100223:104843.668 End of get_snmp():NOTSUPPORTED
       24398:20100223:104843.668 In snmp_close_session()
       24398:20100223:104843.668 End of snmp_close_session()
       24398:20100223:104843.668 End of get_value_snmp():NOTSUPPORTED
       24398:20100223:104843.668 Discovery: Item [] error: OID [] value has unknown type [0x06]
       24398:20100223:104843.668 End of discover_service():FAIL
       24398:20100223:104843.668 Query [txnlev:1] [begin;]
       24398:20100223:104843.668 In update_service() ip:'' port:161 status:1
       24398:20100223:104843.668 In register_service() ip:'' port:161 key:''
       24398:20100223:104843.668 Query [txnlev:1] [select dserviceid,dhostid,status,lastup,lastdown,value from dservices where dcheckid=18 and type=11 and key_='' and ip='' and port=161]
       24398:20100223:104843.668 End of register_service()
       24398:20100223:104843.668 End of update_service()
       24398:20100223:104843.668 Query [txnlev:1] [commit;]
      But we can see that it did get a response (OID: SNMPv2-SMI::enterprises.9.1.359). Seems something it messing up the closing of the discovery process. But as shown in the server log in my first post, the SNMP components do start and are enabled.

      Any ideas?



        Got it! Disappointing though...

        I found the problem.

        OID value types are not supported it seems. At least in the discoverer process.

        This should be supported though. It would be really useful!


          Same problem with 1.8.9

          I've got the same problem with zabbbix 1.8.9:

          19507:20111221:013739.786 discovery: item [.] error: OID [.] value has unknown type [0x06]
          19507:20111221:013739.786 End of discover_service():FAIL

          I hope this issue will be addressed - my goal is to link different kind of equipment to different templates and iana enterprise numbers looks like the obvious choice.