> If I do a set command on an oid that is marked as read-only in the MIB file, > should the agent handle the wrong call or should snmpd catch it before the > agent is even run?
I presume by "agent" you actually mean "subagent" ? (since snmpd *is* the SNMP agent) In which case, William is quite correct - it's the subagent that has the responsibility of rejecting such a request. The master agent doesn't know anything about the details of individual objects - it typically only has a single registration for a particular subtree rather than separate registrations for each MIB object. And even if it did, the AgentX registration process doesn't distinguish between read-only and read-write objects. So a SET request would be forwarded from the master agent to the subagent, and the subagent should then reject this. But if you're using our toolkit to code the subagent and have registered this object as read-only, then the (sub)agent driving code will handle this automatically. The master agent will then take care of backing out any other assignments that may have been made. One final point. If the client-side has access to the MIB file, then the "snmpset" command may well refuse to sent the request in the first plase, so the master agent won't ever see anything at all. But that's with our tools - other management software may leave this up to the agent side. Dave ------------------------------------------------------- SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 _______________________________________________ Net-snmp-users mailing list [EMAIL PROTECTED] Please see the following page to unsubscribe or change other options: https://lists.sourceforge.net/lists/listinfo/net-snmp-users
