snmpset problem

CK Ng ckng____cs.usm.my
Thu Jun 8 10:05:08 CEST 2000


>> I try to set an octet string (using SNMP++ tools) of an Oid to some
values
>> with spaces like "testing 123", but all I'm able to set is the word
>> "testing", everything after a white space are 'truncated'!!!
>
>this is a limitation of the SNMP++ consoleExamples snmpSet: The string
>is read with cin which skips all input after the first space.

I just noticed that.. so it's no problem  =)

>> Another thing is I'm able to access the agent using snmp++ manager tools,
>> without any security measures, ie v1 & v2.   But when i try to use UCD
>> tools, it won't work. However, if authentication or privacy is used, UCD
>> tools work fine so as SNMP++ tools.
>
>What exactly does not work (reading or writing)? I checked my public
>agent with UCD-snmp version: 4.1.1 and I could read but not write with
>v1/v2c because write access for v1/v2c is disabled. With enabled write
>access get and set requests worked fine.

Both read and write. And full access is actually enabled.
Using default settings, SNMPv1 is used right? So get, set, walk etc. from
SNMP++ can access the Oids, but not with UCD's.

here some output of agent for walk:

...
20000608.16:04:32: 00565: (2)EVENT  : RequestList: request received
(id)(siz)(fro)(ver)(com): (547826118), (1), (127.0.0.1/1025), (SNMPv1),
(v1).
20000608.16:04:32: 00565: (3)EVENT  : RequestList: received v1/v2c request
(FOUND)(community)(cid)(cname)(filter_tag): : (FALSE), (v1), (), (), ().

[repeated few times]
...

Thanks again.




More information about the AGENTPP mailing list