From: <no...@so...> - 2001-06-29 13:40:17
|
Bugs item #436818, was opened at 2001-06-27 12:31 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=112694&aid=436818&group_id=12694 Category: agent Group: None Status: Closed Resolution: Invalid Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Wes Hardaker (hardaker) Summary: MIB-II breaks SET functionality Initial Comment: I had a simple snmpd built to support 2 mibs I need to support, and they appeared to be working as expected, when I was told I needed to add MIB-II functionality. As soon as I added it to the mib-modules, any SET commands simply time out; they never get processed, and you never even see them going through the table code, etc., where WriteMethod gets set. Has anyone encountered this? Any quick solutions? Any help is greatly appreciated. Aldo ---------------------------------------------------------------------- >Comment By: Wes Hardaker (hardaker) Date: 2001-06-29 06:40 Message: Logged In: YES user_id=76242 Not responding is the correct behaviour for SNMPv1 and SNMPv2c when illegal access control is attempted. SNMPv3 would have sent you a report pdu that would have let you know that access was denied. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2001-06-28 22:54 Message: Logged In: NO That was it! Thanks. The fact that it didn't respond at all certainly threw me off. Is this the expected behaviour? Or should it be responding with some form of denial status? Just curious. Aldo ---------------------------------------------------------------------- Comment By: Wes Hardaker (hardaker) Date: 2001-06-27 16:47 Message: Logged In: YES user_id=76242 Your problem certainly sounds like an odd one. The best thing to do is to turn on -Dall on the agent command line arguements and use the debugging output to help figure out what is going wrong. If you're not performing sets into the mibII section you added, it certainly shouldn't be affecting your particular mibs (unless they are clashing). Oh wait. I know what the problem is: You have access control now enabled (it's part of the mibII code). You are no longer allowed to write to your agent (it was actually bad before that you had turned off that code). ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2001-06-27 13:34 Message: Logged In: NO Sorry, I forgot to include system information: snmp 4.2.1 (appeared in 4.2 initially) Linux RedHat 7.1, kernel 2.4.5, gcc 2.96 Aldo ald...@hp... ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=112694&aid=436818&group_id=12694 |