Octectstring not well stored in strings.properties file

Description

Here's an example:

string.properties:
ifPhysAddress=0\uFFFD\uFFFDI\u0580

collectd.log:
Processing varBind: .1.3.6.1.2.1.2.2.1.6.3 = 0��Iր

Database:
opennms=# select snmpifindex,snmpphysaddr from snmpinterface where nodeid = 3;
snmpifindex | snmpphysaddr
------------------------------- 3 | 30e4db49d680

Acceptance / Success Criteria

None

Lucidchart Diagrams

Activity

Show:

Jesse White January 26, 2015 at 9:17 AM

Note that the 'hexstring' type only supports Octetstring values, so make sure that this is only set on devices/MIBs where the values being returned is in fact an Octetstring.

Jesse White January 26, 2015 at 9:12 AM

Fixed in 95eee04870.

Added support for a new 'hexstring' type that will explicitly convert Octetstrings to Hex strings (as opposed to their ASCII representation) before persisting them to strings.properties.

Fixed

Details

Assignee

Reporter

Affects versions

Priority

PagerDuty

Created January 22, 2015 at 11:45 AM
Updated April 7, 2015 at 3:04 PM
Resolved January 26, 2015 at 9:12 AM

Flag notifications