I just saw that you released the v4.0.7 version of the java low level api. I'm looking for a changelog, but could not find any information, i checked the help files, the releases. any hints?

cheers

hello

due an error in our code, we found an error in your code ;) if we use a negative value in the oid string, the SnmpTarget class will throw an NPE.

here is the simple example code:

and its exception.

I guess the lib should throw an invalidMibException or something like this...

cheers

michu

I have a strange issue on a customer site. Our Application monitors ~5000 switches - each switch gets scanned each 1.5h. So there are quite alot of snmp queries each day. The problem comes when we try to read the ifNames. Each day we get arround 4-10 invalid ifNames. Never the same switch or ifName - we couldn't find a pattern. So we added some verbose logging to the application.

"invalid ifNames" means, the string encoding is wrong, instead of an ascii string we get a hex string, here is an example:

The debug output is created by this function:

In our first debug version we made a mistake, and the function was looking like that (we were calling getMibOperation.. twice):

Calling the target.getMibOperations().toString twice did NOT always returned the same value! Sometime this operation returns the ascii string, sometimes it returns the hex string. So currently we think the problem is this call, which gets confused 4-10 times a day.

As our application uses several threads to do the snmp query I want to ask you if the getMibOperations function is thread safe? 

Currently the customer uses the 4.0.3 library, but we're updating to 4.0.6 asap.

hey guys

i have a strange issue using the snmpGet() function. According too the java doc, this method return null if a error occurs:

In my situation, I receive "NULL" instead of null (the object).

Here is my simplified code snipped:

and its output:

this happens if the exception code is 128. Did I miss something or is this a bug in the library? I'm using the 4.0.6 version.

I have a strange issue which occurs rarely. sometimes if I query a switch, the ifnames are returned as hex the same also happens with mac address.

Mac adress example:

and here is a bad if name example: 45 54 48 2d 31

Current I use this code to query a device:

and is the result of the following querys equals:

michu