[SNMP4J] BITSTRING

[Frank Fock]

Hello Art,

RFC 1442 has been obsoleted by RFC 1902 which is obsoleted by
RFC2578. Both do not define the BIT STRING type anymore.
Thus, a SNMPv2c standard compliant implementation should not
implement/use it.

You may extend SMNP4J by your own implementation of a BIT STRING
type. I will do so for the next SNMP4J release 1.7.3 too.
But I will add it in a way, that it needs to be "activated"
to be present, because that type is deprecated for 20 (!) years
now!

Best regards,
Frank

kapay wrote:
> Hello Frank,
> 
> Thank you for responding.
> I am referring to the BIT STRING type with the HEX ID of 0x03 defined in 
> RFC1442 (http://www.faqs.org/rfcs/rfc1442.html). The BITS type that you 
> mentioned has a HEX ID of 0x04 which is the same as OCTET STRING.
> 
> ----
> 
>  7.1.4.  BIT STRING
> 
>           The BIT STRING type represents an enumeration of named bits.
>           This collection is assigned non-negative, contiguous values,
>           starting at zero.  Only those named-bits so enumerated may be
>           present in a value.
> 
>           A requirement on "standard" MIB modules is that the hyphen
>           character is not allowed as a part of the label name for any
>           named-bit enumeration.
> 
> ----
> 
> I got a device who is returning BIT STRING data probably because that 
> device also suppots SNMPv2. Do you think this will work if I use SNMPv2 
> instead? Does SNMP4j supports this data type for SNMPv2c?
> 
> I looked through the SNMP4j sources and couldn't find any definition for 
> BIT STRING type. Just for reference ireasonings's SNMP API contains this 
> definition; 
> http://www.ireasoning.com/javadocs/com/ireasoning/protocol/snmp/SnmpDataType.html#BITSTRING
>  
> Thank you.
> Art
> 
> 
> */Frank Fock <fock at agentpp.com>/* wrote:
> 
>     Hi Art,
> 
>     BITSTRING is not a valid SNMP type. Does it is not supported
>     by SNMP4J. Probably you mean the BITS type. That is supported
>     (see recent discussion on this mailing list).
> 
>     When you get a genVBErr as response, the value of the requested
>     variable must be null and thus you cannot see which type it
>     would had been.
> 
>     Best regards,
>     Frank
> 
>     kapay wrote:
>      > Hello.
>      >
>      > Does SNMP4j (v1.5) supports BITSTRING data type?
>      > I am using SNMPv1 and snmp4j returns the "General variable
>     binding error" string when the snmp device responded with a
>     BITSTRING value.
>      >
>      > Thank you.
>      > Art.
>      >
>      >
>      >
>      > ---------------------------------
>      > Do you Yahoo!?
>      > Next-gen email? Have it all with the all-new Yahoo! Mail Beta.
>      > _______________________________________________
>      > SNMP4J mailing list
>      > SNMP4J at agentpp.org
>      > http://lists.agentpp.org/mailman/listinfo/snmp4j
> 
>     -- 
>     AGENT++
>     http://www.agentpp.com
>     http://www.mibexplorer.com
>     http://www.mibdesigner.com
> 
> 
> ------------------------------------------------------------------------
> How low will we go? Check out Yahoo! Messenger’s low PC-to-Phone call 
> rates. 
> <http://us.rd.yahoo.com/mail_us/taglines/postman8/*http://us.rd.yahoo.com/evt=39663/*http://voice.yahoo.com>

-- 
AGENT++
http://www.agentpp.com
http://www.mibexplorer.com
http://www.mibdesigner.com