SnmpTarget.snmpGet() returns "NULL" instead of null..

in SNMP API • 10 years ago

hey guys

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

Returns:

null, if no OID is specified earlier or in case of errors.

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

Here is my simplified code snipped:

public static String getVal(SnmpTarget target, String oid) {
String retVal = null;
target.setObjectID(oid);
retVal = target.snmpGet();
System.out.println("ec: "+target.getErrorCode()+", es: "+target.getErrorString()+", exception code:"+target.getExceptionCode());
if (StringUtils.equals(retVal, "NULL")) {
System.out.println("STRING NULL DETECTED");
retVal=null;
}
handleSnmpError(target);
return retVal;
}

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.

Replies(1)

pradheep.v Employee

9 years ago

Hi,

The noSuchObject' is SNMP V2C/V3 exception and would have occurred because the requested

Object ID : .1.3.6.1.4.1.9.9.68.1.5.1.1.1.2 was not implemented in the agent.

In this case the the SNMP V2C/V3 response will contain NULL value for that OID with 'noSuchObject' exception.

Please note that SnmpTarget.snmpGet() will return 'null' only if the OID is not specified before or it contains errors.

In SNMP V2C/V3 'noSuchObject' is not an error, it is an exception and hence 'null' will not be returned.

Hence please make sure that the Object ID is implemented in the agent to overcome this issue.

For further information regarding this exception, please refer RFC1905.

Trust this information is helpful.

Please get back to us for further clarifications.

regards,

Pradheep