On Tue, 2006-01-03 at 10:52 -0800, rwilcox wrote:
>I don't usually have spaces between the -c and -v
> arguments, I seem to recall having problems when I had
> spaces.
With or without space - it makes no difference.
I invariably use "-c public" and "-v 2c", as I
find this style clearer to unde
On Sat, 2005-12-31 at 11:18 +0530, Krishnaprasad wrote:
> Then the output of this progam is: Ret
> OID:1.3.6.1.2.1.1.3.0,Type:snmp.SNMPTimeTicks,Value:75941
> But if we run the snmpcommand as "snmpget -c public -v 2c
> localhost .1.3.6.1.2.1.1.3.0", i got the systemuptime value
> correctly.(Timet
Hello All,
I already implemented OID for accessing my variable .The datatype for
this OID is OCTETSTRING.
I run the snmpcommands (snmpget ,snmpwalk) for getting the string
values corresponding for this OID variable.
After running this commands i got the output as a HEXSTRING value whose
si
Hello,
It sounds like the OID is fine when using the
net-snmp tools, but the Java app is having problems?
If not, any more detail you can provide, like program
output would help. You say that you didn't get the
correct string. What did you get and what did you
expect?
Also,
> But
Hello,
I am not aware of any limitation within the agent
regarding length. You need to make sure that the OID
you are setting can handle a string of that size(refer
to MIB documentation). Your handler for that OID
needs to be able to handle 400 characters (I assume
you are developing the agen
Hello All,
How can we send a 400 character string using snmpv1. Is it possible or not.
Thanks in advance,
Krishnaprasad
