On 29 June 2011 13:28, venkatgiri <venkatgir...@globaledgesoft.com> wrote: > Now i have got one more question, the rule of encoding the bits is > applicable for both SNMP manager(during SNMP SET) and SNMP client(during > SNMPGET/SNMPWALK operation).
The encoding rules are applied to *ALL* SNMP requests, when preparing them for putting onto the wire, or parsing an incoming packet. It doesn't matter whether these are GET, GETNEXT, SET requests, traps, informs, or some new as-yet-undefined SNMP request packet. The encoding rules are applied consistently to *all* requests. > Does SNMP Client has real reverse the bits when queried through SNMPGET, > irrespective of the bit length(either 8 bits or 64 bits). Sorry - I don't understand what you are asking. Forget about 64-bit - it's simply not relevant here. BITS objects are *strings* - so work with char[] values i.e. one or more 8-bit quantities. I would suggest that you start with a simpler MIB object definition, with just two or three named bits, and get that working properly first. Then look at extending this by adding more named bits - first to complete the full eight-bit char value, and then a couple more to take it into the second octet, and only then move on to your full 19-bit version Dave ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 _______________________________________________ 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
