[ZBX-5474] Problem with low-level discovery for SNMP Created: 2012 Aug 21  Updated: 2017 May 30  Resolved: 2014 Jun 10

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Server (S)
Affects Version/s: 2.0.2
Fix Version/s: None

Type: Incident report Priority: Major
Reporter: Krzysztof Kardas Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: lld, snmp
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Redhat 6 x86_64, postgreSQL 9.1, zabbix version 2.0.2

Attachments: File dump     Text File odsMajatek.sb1_single.snmpwalk.txt     XML File zbx_export_templates (2).xml    
Issue Links:
Duplicate
duplicates ZBX-3449 Dynamic Index Only Works for single i... Closed

 Description   

I was trying to create a template with autodiscovery feature for Oracle Weblogic SNMP agent. I have created a template, as shown in documentation, that was using

{#SNMPINDEX}

and

{#SNMPVALUE}

macros.
Ther problem is that when I was trying to start the template, it says: Value should be a JSON object
No other info in log.
tpdump showes me that there is a traffic between WLS server and zabbix server, and something is taken, but the discovery process does not complete sucessfuly.

Information - #SNMPINDEX is not as trivial as shown in documentation. It is much more complex. Same for #SNMPVALUE

I have attached dump from tcpdump, and snmpwalk from oracle weblogic server.

 Comments   
Comment by Oleksii Zagorskyi [ 2012 Aug 22 ]

Two OIDs from discovery rules (from 10) of attached template:

<snmp_oid>BEA-WEBLOGIC-MIB::jdbcConnectionPoolRuntimeName</snmp_oid>
<snmp_oid>BEA-WEBLOGIC-MIB::jdbcDataSourceRuntimeName</snmp_oid>

Their values:

BEA-WEBLOGIC-MIB::jdbcConnectionPoolRuntimeName.16.28.28.115.177.229.76.118.54.122.0.83.172.104.11.127.25 = STRING: "CGW-MoneyTransferService"
BEA-WEBLOGIC-MIB::jdbcConnectionPoolRuntimeName.16.39.156.9.120.121.32.67.30.137.246.42.30.13.38.229.6 = STRING: "KangurDatabase"
BEA-WEBLOGIC-MIB::jdbcConnectionPoolRuntimeName.16.45.80.167.154.106.8.229.141.143.214.249.118.177.56.174.132 = STRING: "SGW-CalendarService"
...
BEA-WEBLOGIC-MIB::jdbcConnectionPoolRuntimeName.16.229.207.251.8.216.251.48.2.91.56.44.251.215.173.12.138 = STRING: "pl.pzu.dsi.connection.jdbc.sofiikepzu.PartyService"
BEA-WEBLOGIC-MIB::jdbcConnectionPoolRuntimeName.16.238.160.117.159.109.109.77.29.200.67.44.210.7.117.162.222 = STRING: "pl.pzu.dsi.connection.jdbc.eplatforma.DictionaryService"
BEA-WEBLOGIC-MIB::jdbcConnectionPoolRuntimeName.16.245.40.62.100.13.236.220.30.91.164.191.34.56.205.253.157 = STRING: "SGW-InvoiceService"

BEA-WEBLOGIC-MIB::jdbcDataSourceRuntimeName.16.27.223.187.205.102.106.74.67.38.93.180.42.62.68.75.221 = STRING: "pl.pzu.dsi.connection.jdbc.sofiikepzu.PartyService"
BEA-WEBLOGIC-MIB::jdbcDataSourceRuntimeName.16.30.143.146.95.122.23.89.7.196.13.177.39.11.161.252.173 = STRING: "cgDataSource"
BEA-WEBLOGIC-MIB::jdbcDataSourceRuntimeName.16.36.151.105.73.70.218.185.30.210.72.68.14.234.55.152.15 = STRING: "pl.pzu.dsi.connection.jdbc.sofiiketfi.PartyService"
...
BEA-WEBLOGIC-MIB::jdbcDataSourceRuntimeName.16.231.169.47.118.155.133.65.154.103.101.193.202.157.184.115.68 = STRING: "pl.pzu.dsi.connection.jdbc.filenet.CaseService"
BEA-WEBLOGIC-MIB::jdbcDataSourceRuntimeName.16.243.164.4.137.41.96.244.212.252.52.101.117.156.170.232.38 = STRING: "pl.pzu.dsi.connection.jdbc.eplatforma.DictionaryService"
BEA-WEBLOGIC-MIB::jdbcDataSourceRuntimeName.16.251.221.197.122.199.93.231.99.145.67.130.148.49.135.236.94 = STRING: "CGW-ObligationDocumentServiceStatus"

It seems duplicate of ZBX-3449

In any case would be better to provide SNMP walk tree for particular OID but not for full tree and single discovery rule.

Comment by Oleksii Zagorskyi [ 2014 Jun 10 ]

It indeed is duplicate of ZBX-3449
CLOSED.

Generated at Sun Apr 27 07:51:47 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.