Hi all, I have a question regarding alarmActiveDateAndTime (part of the index of alarmActiveTable) and the way it should be encoded. My understanding is that since DateAndTime is of type OCTET STRING, it has to be encoded like the following example in the OID:
8.7.223.10.8.12.13.45.8 Moreover, it seems that net-snmp is able to successfully parse the OID: $ snmptranslate -OX .1.3.6.1.2.1.118.1.2.2.1.4.0.8.7.223.10.8.12.13.45.8.1 ALARM-MIB::alarmActiveEngineID[STRING: ][STRING: 2015-10-8,12:13:45.8][1] However, someone pointed out that in the examples of RFC3877 [1], alarmActiveDateAndTime is shown with a value of 2342464573 and therefore the OID should be something like e.g.: .1.3.6.1.2.1.118.1.2.2.1.4.0.2342464573.1 This looks strange to me. I didn't found any such conversion in an RFC!? Could someone confirm that DateAndTime has to be encoded as a normal OCTET STRING when used as index? Does anyone have some walk output examples for alarmActiveTable? It seems this MIB is not so common and I was not able to compare. Thank you and Regards, Cyril Jaquier [1] https://tools.ietf.org/html/rfc3877#page-59 ------------------------------------------------------------------------------ _______________________________________________ Net-snmp-users mailing list Net-snmp-users@lists.sourceforge.net Please see the following page to unsubscribe or change other options: https://lists.sourceforge.net/lists/listinfo/net-snmp-users
