> SMUX protocol doesn't support multi var-bind.
That's not correct.
RFC 1227 states:
[Section 3]
When the SNMP agent receives an SNMP GetRequest-PDU, GetNextRequest-
PDU, or SetRequest-PDU .... the SNMP agent sends an
equivalent SNMP PDU containing only those variables within the
subtree registered by that SMUX peer. ^^^^^^^^^
[Section 3.1.3]
When an SNMP SetRequest-PDU is received... at least one SNMP SetRequest-
PDU is sent, with only those variables of interest to that peer.
^^^^^^^^^
There is the *option* of splitting multiple varbinds into separate SMUX
requests, but only for Get/GetNext requests:
[Section 3.1.4]
When constructing an SNMP GetRequest-PDU or GetNextRequest-PDU for a
SMUX peer, the SNMP agent may send one, or more than one variable in
a single request.
This possibility is not listed for SET requests, so (implicitly) such
varbinds should be kept together - for exactly the reasons you discuss.
Please note also that there are a number of fundamental limitations
with the SMUX protocol, so any new development should seriously consider
using AgentX instead.
Dave
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
Net-snmp-coders mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
