[ZBXNEXT-1218] SNMP: Dynamic Prefixes with variable parts in the middle Created: 2012 May 10 Updated: 2019 Apr 12 |
|
| Status: | Open |
| Project: | ZABBIX FEATURE REQUESTS |
| Component/s: | Frontend (F), Server (S) |
| Affects Version/s: | 1.8.11 |
| Fix Version/s: | None |
| Type: | New Feature Request | Priority: | Trivial |
| Reporter: | Mattias Geniar | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 16 |
| Labels: | flexibility, snmp, snmpdynamicindex | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Description |
|
Zabbix supports Dynamic SNMP items such as: ifMtu["index", "ifDescr", "ge-0/0/47"] This works very well, except when the variable part of the SNMP item is somewhere in the middle. Juniper excels at these kind of "exotic" SNMP configurations where they deviate from the standard. The variable part there is ".598", directly after the jnxCosIfqTailDropPkts. The series of numbers behind it are the specific property of that OID. Zabbix does not support a layout such as: JUNIPER-COS-MIB::jnxCosIfqTailDropPkts["index", "ifDescr", "ge-0/0/47"].18.97.115.115.117.114.101.100.45.102.111.114.119.97.114.100.105.110.103 It would be useful, although a very small portion of Zabbix users will require this, to have the variable/dynamic part of the SNMP call to be available anywhere in the SNMP OID. This may be a duplicate issue, I couldn't find one that specifies this exact use case. Apologies if it's a double. |
| Comments |
| Comment by Raymond Kuiper [ 2016 Oct 28 ] |
|
I'm running into the same issue with some Cisco OIDs and Zabbix 2.4.7. VDSL2-LINE-MIB::xdsl2LineBandStatusLnAtten.15.us0 The "15" here is a dynamic index that refers to an entry in the interface tables. Doing a dynamic OID lookup like: .1.3.6.1.2.1.10.251.1.1.2.1.2[index,ifDescr,"Ethernet0-vdsl2"].3 Will fail with the following error message: "Invalid SNMP OID at position 62" |
| Comment by Omni Flux [ 2019 Apr 12 ] |
|
Here's another with a different vendor. interface index.table index.table property
.1.3.6.1.4.1.5454.1.80.4. 1. 1. 1.0 = INTEGER: on(1) .1.3.6.1.4.1.5454.1.80.4. 1. 1. 2.0 = INTEGER: full(1) .1.3.6.1.4.1.5454.1.80.4. 1. 1. 3.0 = INTEGER: on(1) .1.3.6.1.4.1.5454.1.80.4. 1. 1. 4.0 = INTEGER: 1000 .1.3.6.1.4.1.5454.1.80.4. 1. 1. 5.0 = INTEGER: off(0) .1.3.6.1.4.1.5454.1.80.4. 1. 1. 6.0 = INTEGER: 0 .1.3.6.1.4.1.5454.1.80.4. 1. 1. 7.0 = INTEGER: 1000 .1.3.6.1.4.1.5454.1.80.4. 1. 1. 8.0 = INTEGER: on(1) .1.3.6.1.4.1.5454.1.80.4. 1. 2. 1.0 = Counter32: 3166200082 .1.3.6.1.4.1.5454.1.80.4. 1. 2. 2.0 = Counter32: 2183265784 .1.3.6.1.4.1.5454.1.80.4. 1. 2. 3.0 = Counter32: 6571852 .1.3.6.1.4.1.5454.1.80.4. 1. 2. 4.0 = Counter32: 319606 .1.3.6.1.4.1.5454.1.80.4. 1. 2. 5.0 = Counter32: 309567534 .1.3.6.1.4.1.5454.1.80.4. 1. 2. 6.0 = Counter32: 2136271403 .1.3.6.1.4.1.5454.1.80.4. 1. 2. 7.0 = Counter32: 0 .1.3.6.1.4.1.5454.1.80.4. 1. 2. 8.0 = Counter32: 0 .1.3.6.1.4.1.5454.1.80.4. 2. 1. 1.0 = INTEGER: on(1) .1.3.6.1.4.1.5454.1.80.4. 2. 1. 2.0 = INTEGER: full(1) .1.3.6.1.4.1.5454.1.80.4. 2. 1. 3.0 = INTEGER: on(1) .1.3.6.1.4.1.5454.1.80.4. 2. 1. 4.0 = INTEGER: 1000 .1.3.6.1.4.1.5454.1.80.4. 2. 1. 5.0 = INTEGER: off(0) .1.3.6.1.4.1.5454.1.80.4. 2. 1. 6.0 = INTEGER: 0 .1.3.6.1.4.1.5454.1.80.4. 2. 1. 7.0 = INTEGER: 1000 .1.3.6.1.4.1.5454.1.80.4. 2. 1. 8.0 = INTEGER: off(0) .1.3.6.1.4.1.5454.1.80.4. 2. 2. 1.0 = Counter32: 0 .1.3.6.1.4.1.5454.1.80.4. 2. 2. 2.0 = Counter32: 0 .1.3.6.1.4.1.5454.1.80.4. 2. 2. 3.0 = Counter32: 0 .1.3.6.1.4.1.5454.1.80.4. 2. 2. 4.0 = Counter32: 0 .1.3.6.1.4.1.5454.1.80.4. 2. 2. 5.0 = Counter32: 0 .1.3.6.1.4.1.5454.1.80.4. 2. 2. 6.0 = Counter32: 0 .1.3.6.1.4.1.5454.1.80.4. 2. 2. 7.0 = Counter32: 0 .1.3.6.1.4.1.5454.1.80.4. 2. 2. 8.0 = Counter32: 0
|