Hi All,
I was just wondering has anyone ever encountered this problem or even better found a solution.
I have a 2-level index, and Zabbix finds the indexed item correctly, but does not correctly append the full difference between the indexed item you're searching for, and the item you want to find the value for.
Example (from CISCO VPDN MIB):
.1.3.6.1.4.1.9.10.24.1.3.2.1.2.2.24196.60898 = STRING: "[email protected]"
.1.3.6.1.4.1.9.10.24.1.3.2.1.3.2.24196.60898 = INTEGER: 10
.1.3.6.1.4.1.9.10.24.1.3.2.1.4.2.24196.60898 = Timeticks: (52950267) 6 days, 3:05:02.67
.1.3.6.1.4.1.9.10.24.1.3.2.1.5.2.24196.60898 = Counter32: 3685231
.1.3.6.1.4.1.9.10.24.1.3.2.1.6.2.24196.60898 = Counter32: 349105822
.1.3.6.1.4.1.9.10.24.1.3.2.1.7.2.24196.60898 = Counter32: 6645606
.1.3.6.1.4.1.9.10.24.1.3.2.1.8.2.24196.60898 = Counter32: 3877033828
.1.3.6.1.4.1.9.10.24.1.3.2.1.9.2.24196.60898 = INTEGER: 1
.1.3.6.1.4.1.9.10.24.1.3.2.1.10.2.24196.60898 = ""
.1.3.6.1.4.1.9.10.24.1.3.2.1.11.2.24196.60898 = INTEGER: 0
.1.3.6.1.4.1.9.10.24.1.3.2.1.12.2.24196.60898 = INTEGER: 2
.1.3.6.1.4.1.9.10.24.1.3.2.1.20.2.24196.60898 = Gauge32: 0
.1.3.6.1.4.1.9.10.24.1.3.2.1.21.2.24196.60898 = Counter32: 0
.1.3.6.1.4.1.9.10.24.1.3.2.1.22.2.24196.60898 = Counter32: 0
.1.3.6.1.4.1.9.10.24.1.3.2.1.23.2.24196.60898 = ""
.1.3.6.1.4.1.9.10.24.1.3.2.1.24.2.24196.60898 = INTEGER: 0
The item I'm using as my search is "[email protected]", but the base of the index is (according to the MIB) ".1.3.6.1.4.1.9.10.24.1.3.2.1.2". Therefore "2.24196.60898" is the index number. I'm trying to retrieve the value for ".1.3.6.1.4.1.9.10.24.1.3.2.1.6.2.24196.60898" , of which the base should be ".1.3.6.1.4.1.9.10.24.1.3.2.1.6".
Zabbix is reporting the following: "OID [1.3.6.1.4.1.9.10.24.1.3.2.1.6.60898] value has unknow type [0x81]". Does Zabbix have the ability to compare the difference between the the matched index ".1.3.6.1.4.1.9.10.24.1.3.2.1.2.2.24196.60898" , and the search base index we supply, and then append it to the index we're looking for the value for ".1.3.6.1.4.1.9.10.24.1.3.2.1.6"
Thanks
I was just wondering has anyone ever encountered this problem or even better found a solution.
I have a 2-level index, and Zabbix finds the indexed item correctly, but does not correctly append the full difference between the indexed item you're searching for, and the item you want to find the value for.
Example (from CISCO VPDN MIB):
.1.3.6.1.4.1.9.10.24.1.3.2.1.2.2.24196.60898 = STRING: "[email protected]"
.1.3.6.1.4.1.9.10.24.1.3.2.1.3.2.24196.60898 = INTEGER: 10
.1.3.6.1.4.1.9.10.24.1.3.2.1.4.2.24196.60898 = Timeticks: (52950267) 6 days, 3:05:02.67
.1.3.6.1.4.1.9.10.24.1.3.2.1.5.2.24196.60898 = Counter32: 3685231
.1.3.6.1.4.1.9.10.24.1.3.2.1.6.2.24196.60898 = Counter32: 349105822
.1.3.6.1.4.1.9.10.24.1.3.2.1.7.2.24196.60898 = Counter32: 6645606
.1.3.6.1.4.1.9.10.24.1.3.2.1.8.2.24196.60898 = Counter32: 3877033828
.1.3.6.1.4.1.9.10.24.1.3.2.1.9.2.24196.60898 = INTEGER: 1
.1.3.6.1.4.1.9.10.24.1.3.2.1.10.2.24196.60898 = ""
.1.3.6.1.4.1.9.10.24.1.3.2.1.11.2.24196.60898 = INTEGER: 0
.1.3.6.1.4.1.9.10.24.1.3.2.1.12.2.24196.60898 = INTEGER: 2
.1.3.6.1.4.1.9.10.24.1.3.2.1.20.2.24196.60898 = Gauge32: 0
.1.3.6.1.4.1.9.10.24.1.3.2.1.21.2.24196.60898 = Counter32: 0
.1.3.6.1.4.1.9.10.24.1.3.2.1.22.2.24196.60898 = Counter32: 0
.1.3.6.1.4.1.9.10.24.1.3.2.1.23.2.24196.60898 = ""
.1.3.6.1.4.1.9.10.24.1.3.2.1.24.2.24196.60898 = INTEGER: 0
The item I'm using as my search is "[email protected]", but the base of the index is (according to the MIB) ".1.3.6.1.4.1.9.10.24.1.3.2.1.2". Therefore "2.24196.60898" is the index number. I'm trying to retrieve the value for ".1.3.6.1.4.1.9.10.24.1.3.2.1.6.2.24196.60898" , of which the base should be ".1.3.6.1.4.1.9.10.24.1.3.2.1.6".
Zabbix is reporting the following: "OID [1.3.6.1.4.1.9.10.24.1.3.2.1.6.60898] value has unknow type [0x81]". Does Zabbix have the ability to compare the difference between the the matched index ".1.3.6.1.4.1.9.10.24.1.3.2.1.2.2.24196.60898" , and the search base index we supply, and then append it to the index we're looking for the value for ".1.3.6.1.4.1.9.10.24.1.3.2.1.6"
Thanks
Comment