Ad Widget

Collapse

SNMP Discovery Rule Issue Zabbix 4.2

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • arovah
    Member
    • Nov 2020
    • 43

    #1

    SNMP Discovery Rule Issue Zabbix 4.2

    Dear Colleagues,

    We have issue in Zabbix discovery rule, we are using zabbix version 4.2.1 and the topology is devices/hosts -> zabbix proxy -> zabbix server -> database and agents interface setup using SNMPV2.
    There are some hosts can not get item from discovery rule in zabbix proxy, if i run snmpwalk from Zabbix Proxy to host the result is ok snmpwalk able to run query, but in zabbix web not appears item yet.
    All devices registered on Zabbix are the same using Template Module Interfaces SNMPv2_SCM. Is there a manual way to get item faster ? Please your any advice and suggest ?

    Click image for larger version

Name:	image.png
Views:	502
Size:	33.8 KB
ID:	471469​​


    [mzi@zabbix-proxy02 ~]$ /usr/bin/snmpwalk -v 2c -c passwrod 172.27.xx.xx
    SNMPv2-MIB::sysDescr.0 = STRING: BDCOM(tm) S2928EF Software, Version 81073
    hardware version: A
    SNMPv2-MIB::sysObjectID.0 = OID: SNMPv2-SMI::enterprises.3320.1.458.0
    DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (1075334261) 124 days, 11:02:22.61
    SNMPv2-MIB::sysContact.0 = STRING: [email protected]
    SNMPv2-MIB::sysName.0 = STRING: JATENG-ODC.BANTUL.KOTA-S2928EF-CPE-01
    SNMPv2-MIB::sysLocation.0 = STRING: JATENG-ODC.BANTUL.KOTA-S2928EF-CPE-01
    SNMPv2-MIB::sysServices.0 = INTEGER: 6
    SNMPv2-MIB::sysORLastChange.0 = Timeticks: (1075334265) 124 days, 11:02:22.65
    SNMPv2-MIB::sysORID.1 = OID: SNMPv2-SMI::enterprises.3320.1.458.0
    SNMPv2-MIB::sysORDescr.1 = STRING: BDCOM(tm) S2928EF Software, Version 81073
    hardware version: A
    SNMPv2-MIB::sysORUpTime.1 = Timeticks: (1075334268) 124 days, 11:02:22.68
    IF-MIB::ifNumber.0 = INTEGER: 31
    IF-MIB::ifIndex.165 = INTEGER: 165
    IF-MIB::ifIndex.166 = INTEGER: 166
    IF-MIB::ifIndex.167 = INTEGER: 167
    IF-MIB::ifIndex.168 = INTEGER: 168
    IF-MIB::ifIndex.169 = INTEGER: 169
    IF-MIB::ifIndex.170 = INTEGER: 170
    IF-MIB::ifIndex.171 = INTEGER: 171
    IF-MIB::ifIndex.172 = INTEGER: 172
    IF-MIB::ifIndex.173 = INTEGER: 173
    IF-MIB::ifIndex.174 = INTEGER: 174
    IF-MIB::ifIndex.175 = INTEGER: 175
    IF-MIB::ifIndex.176 = INTEGER: 176
    IF-MIB::ifIndex.177 = INTEGER: 177
    IF-MIB::ifIndex.178 = INTEGER: 178
    IF-MIB::ifIndex.179 = INTEGER: 179
    IF-MIB::ifIndex.180 = INTEGER: 180
    IF-MIB::ifIndex.181 = INTEGER: 181
    IF-MIB::ifIndex.182 = INTEGER: 182
    IF-MIB::ifIndex.183 = INTEGER: 183
    IF-MIB::ifIndex.184 = INTEGER: 184
    IF-MIB::ifIndex.185 = INTEGER: 185
    IF-MIB::ifIndex.186 = INTEGER: 186
    IF-MIB::ifIndex.187 = INTEGER: 187
    IF-MIB::ifIndex.188 = INTEGER: 188
    IF-MIB::ifIndex.189 = INTEGER: 189​

    Thank you
  • arovah
    Member
    • Nov 2020
    • 43

    #2
    up, is there any one can help me?

    Comment

    • arovah
      Member
      • Nov 2020
      • 43

      #3
      up, is there any one can help me?

      Comment

      • vijayk
        Senior Member
        • May 2023
        • 305

        #4
        Can you post the discovery rule here which you created?

        Comment

        • arovah
          Member
          • Nov 2020
          • 43

          #5
          hello vijayk,

          Thank you for your response, here it is the discovery rules detail

          Click image for larger version

Name:	image.png
Views:	239
Size:	61.7 KB
ID:	473366
          Click image for larger version

Name:	image.png
Views:	287
Size:	108.6 KB
ID:	473367

          Click image for larger version

Name:	image.png
Views:	238
Size:	117.3 KB
ID:	473368

          Comment

          • vijayk
            Senior Member
            • May 2023
            • 305

            #6
            Change the update interval value from 30m to less. It might be helpful.

            Comment

            Working...