Ad Widget

Collapse

Discovery not working for single host using snmp v2 check

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • brdr
    Junior Member
    • Apr 2014
    • 13

    #1

    Discovery not working for single host using snmp v2 check

    Hi folks,

    I'm using Zabbix Server v2.2.3 on Linux. I'm looking to have Zabbix (for testing purposed) discover 1 snmp device, another Linux server.

    I can run the snmpwalk command successfully from the actual Zabbix server successfully no problem using 'sysDescr'. The Discovery has 1 simple that (smnp v2 '"sysDescr). Screens shots are too large to attach. I'm happy to forward screen shots some other way.

    My Action conditions are pretty straight forward using the actual Rule I've created, followed up by 'Return value like Linux'. The Operations are simple; Add host to Linux server, and use link template 'Linux OS'. I've attached screen shots of the Actions. NOTE: Event Source for my Action is set to 'Discovery'.

    I've been trying to get this to find the 1 server and bagging my head :-).

    Much appreciate the help.
    Thanks,
    Don
  • brdr
    Junior Member
    • Apr 2014
    • 13

    #2
    More info from zabbix server log (at Debug level). Based on the output it appears 'sysDescr' can not be translated by zabbix server. As I mentioned in my first thread I can run snmpwalk from zabbix server and retrieve sysDescr no problem. Can I not use sysDescr in the rule? Do I need to define a macro for sysDescr?

    Log:
    24279:20140423:085024.037 In process_check()
    24279:20140423:085024.037 process_check() port:161
    24279:20140423:085024.037 In discover_service()
    24279:20140423:085024.038 In substitute_simple_macros() data:'public'
    24279:20140423:085024.038 In substitute_key_macros() data:'sysDescr'
    24279:20140423:085024.038 End of substitute_key_macros():SUCCEED data:'sysDescr'
    24279:20140423:085024.038 In get_values_snmp() host:'' addr:'172.17.20.81' num:1
    24279:20140423:085024.038 In zbx_snmp_open_session()
    24279:20140423:085024.038 SNMP [[email protected]:161]
    24279:20140423:085024.038 End of zbx_snmp_open_session()
    24279:20140423:085024.038 In zbx_snmp_process_standard()
    24279:20140423:085024.038 In zbx_snmp_translate() oid:'sysDescr'
    24279:20140423:085024.038 End of zbx_snmp_translate() oid_translated:'sysDescr'
    24279:20140423:085024.038 In zbx_snmp_get_values() num:1 level:0
    24279:20140423:085024.039 zbx_snmp_get_values() snmp_synch_response() status:0 errstat:0 mapping_num:1
    24279:20140423:085024.039 In zbx_snmp_set_result() type:129 value_type:1 data_type:0
    24279:20140423:085024.039 End of zbx_snmp_set_result():NOTSUPPORTED
    24279:20140423:085024.039 End of zbx_snmp_get_values():SUCCEED
    24279:20140423:085024.040 End of zbx_snmp_process_standard():SUCCEED
    24279:20140423:085024.040 In zbx_snmp_close_session()
    24279:20140423:085024.040 End of zbx_snmp_close_session()
    24279:20140423:085024.040 End of get_values_snmp()
    24279:20140423:085024.040 discovery: item [sysDescr] error: No Such Instance currently exists at this OID
    24279:20140423:085024.040 End of discover_service():FAIL
    24279:20140423:085024.040 query [txnlev:1] [begin;]
    24279:20140423:085024.040 In discovery_update_service() ip:'172.17.20.81' port:161 status:1
    24279:20140423:085024.040 In discovery_register_host() ip:'172.17.20.81' status:1 value:''
    24279:20140423:085024.040 query [txnlev:1] [select dh.dhostid,dh.status,dh.lastup,dh.lastdown from dhosts dh,dservices ds where ds.dhostid=dh.dhostid and ds.dcheckid=19 and ds.value='' order by dh.dhostid]

    Comment

    • brdr
      Junior Member
      • Apr 2014
      • 13

      #3
      Update: My problem was that I wasn't using the full SNMP OID in the rule. I was using 'sysDescr'. Instead, I should have been using 'SNMPv2-MIB::sysDescr.0' Once I did that everything was fine - i.e. host was discovered and put into proper host group.

      Thanks

      Comment

      • aib
        Senior Member
        • Jan 2014
        • 1615

        #4
        Good for you!

        Thank you for your help to yourself!
        Sincerely yours,
        Aleksey

        Comment

        Working...