-
Type:
Problem report
-
Resolution: Unresolved
-
Priority:
Trivial
-
None
-
Affects Version/s: 7.0.15
-
Component/s: Frontend (F), Proxy (P), Server (S)
ZBXNEXT-8246 added "Integer from BITS" preprocessing step, which great.
But in reality I get this:
iso.2.840.10006.300.43.1.2.1.1.23.1 = STRING: "=" iso.2.840.10006.300.43.1.2.1.1.23.1 = STRING: "=" iso.2.840.10006.300.43.1.2.1.1.23.2 = STRING: "=" iso.2.840.10006.300.43.1.2.1.1.23.3 = STRING: "=" iso.2.840.10006.300.43.1.2.1.1.23.4 = Hex-STRING: 00 iso.2.840.10006.300.43.1.2.1.1.23.5 = STRING: "=" iso.2.840.10006.300.43.1.2.1.1.23.6 = STRING: "=" iso.2.840.10006.300.43.1.2.1.1.23.7 = STRING: "=" iso.2.840.10006.300.43.1.2.1.1.23.8 = STRING: "="
I understand rfc3417#section-8 uses OCTET-STRING both for BITS and for STRING so snmp tools have to guess (or be forced by -Oa or -Ox).
Can this be resolved by allowing "Integer from BITS" preprocessing to work on STRING values so it works regardless of how snmp tools's guess goes?
Thank you.
