RE: Setting multiple table rows in one set operation

> From: [email protected] 
> [mailto:[email protected]] On 
> Behalf Of vsaavedra
> Sent: Tuesday, January 15, 2008 9:48 AM

> Is it possible to do a SET BULK,

	There is no such PDU, nor is such a thing conceivable, but that's not what you're asking for.

> i.e., setting multiple table 
> rows in one
> set operation?

	It is important to remember that all the SNMP RFCs refer to "conceptual rows".  This is because there is no inherent organization of OIDs, only that which we externally impose.  To state it clearly:  rows do not exist in SNMP at the OID level, which is the level at which protocol operations occur.  Therefore, from an SNMP standpoint, there is no difference between creating one or two rows.

	That being said, it is also important to understand that few MIBs are implemented by SNMP purists.  I would strongly recommend against creating multiple rows in a single PDU despite the fact that, by spec, it should work, unless the MIB specifies that this is a supported operation.

> When I tried  I do the following command :
> 
> snmpset -v 2c -c public localhost IDX.1 i 1  Name.1 s "Name 
> 1" IDX.2 i 2 Name.2 s "Name 2"
> 
> The Output was:
> 
> MY-MIB::IDX.1 = INTEGER: 1
> MY-MIB::IDX.2 = INTEGER: 2
> MY-MIB::Name.1 = STRING: "Name 1"
> MY-MIB::Name.2 = STRING: "Name 2"
> 
> Apparently, everything was OK, but when I do a
> 
> snmpbulkwalk -v2c -Os -c public localhost   MyTable, the output is :
> 
> IDX.1 = INTEGER: 2
> Name.1 = INTEGER: Name 2.
> 
> Apparently, even if I pass two rows, the set is only made once.

	Heh??!!  That whole mess looks fishy!  I don't know what the definition of your MIB is, but it looks to me like you're trying to create the index objects, which is definitely a bad idea, and (I'd have to hit the RFCs for this) probably illegal.  Try just setting the two strings.  In any case, you get all the sets confirmed, so the rows should be there.

	My advice above to not set multiple rows was intended to refer to status based rows, not a simple autocreation row scheme like the one you show.

	In any case, the ability to create and retain rows is strictly internal to the MIB implementation, so if you're having trouble with this, you need to deal with the MIB's author.


	HTH,

Mike

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
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