This is a discussion on Help regarding C64 Textual Conventiond defined in "Understanding SNMP MIBs - Perkins" within the SNMP Users forums, part of the Networking and Network Related category; Hi all,=20 I need your help in understanding the Counter64 representation as mentioned in "Understanding SNMP MIBs by ...
|
|||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
|
|||
|
Hi all,=20
I need your help in understanding the Counter64 representation as mentioned in "Understanding SNMP MIBs by DAVID PERKINS, page 51". The book quotes an example the BER serialization of value 56782 of type COUNTER 64 is '9f760300ddce'h. In the above example, value 9f76 is the value of the tag for Counter 64. 03 is the length of the value, and 00ddce is the hexadecimal representation of 56782. My question are=20 1. why is the length field is represented as 03 i.e. one byte, instead of 0003 (2 bytes is reserved for length in Opaque)?=20 2. To represent value of 56782 in hexadecimal it is enough if we represent by 'ddce'h. Why is it represented as '00ddce'h? Which is taking 3 bytes in length?=20 3. Can we use the following tag values for other 64bit data types?=20 Counter64 9f76, Signed64 9f7A, Unsigned64 9f7B. Your clarifications towards understanding this C64 textual convention and data value representation in the Opaque stream will be greatly appreciated.=20 Thanks Mahesh ------------------------------------------------------- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today * Register for a JBoss Training Course Free Certification Exam for All Training Attendees Through End of 2005 Visit http://www.jboss.com/services/certification for more information _______________________________________________ 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/...net-snmp-users |