setting multiple columns in one command

I have run into some unexpected behavior.  I have some dataset type
tables that I have implemented through an agentx subagent.  I have
three different tables all under a common branch:

snmpwalk -v2c -c public localhost adsEIDTable
DAR-SIM::adsEIDValue.1 = INTEGER: 0
DAR-SIM::adsEIDMask.1 = INTEGER: 0

snmpwalk -v2c -c public localhost adsIDTable
DAR-SIM::adsIDValue.1 = INTEGER: 0
DAR-SIM::adsIDMask.1 = INTEGER: 0

snmpwalk -v2c -c public localhost adsWordTable
DAR-SIM::adsWordPosition.1 = INTEGER: 0

Now lets say I try to do multiple sets in one command to the
adsWordTable to create new rows:

snmpset -v2c -c admin localhost adsWordPosition.1 i 8
adsWordPosition.2 i 9        adsWordPosition.3 i 2
DAR-SIM::adsWordPosition.1 = INTEGER: 8
DAR-SIM::adsWordPosition.2 = INTEGER: 9
DAR-SIM::adsWordPosition.3 = INTEGER: 2

It reports that the new columns were created and the values were all
set correctly, but when I do a walk of the table it doesn't have the
new rows that were supposedly just created.  Instead it simply sets
the original column to the last value I tried to set.  In this case 2.

DAR-SIM::adsWordPosition.1 = INTEGER: 2

The tables with two columns behave in a similar way.  If i set both
columns in the same row it works just fine.

snmpset -v2c -c admin localhost adsIDMask.1 i 7 adsIDValue.1 i 5
results in:
DAR-SIM::adsIDMask.1 = INTEGER: 7
DAR-SIM::adsIDValue.1 = INTEGER: 5

When I try to set two columns in different rows it will set both
columns to the right value but it will only use the first row.

snmpset -v2c -c admin localhost adsIDMask.2 i 4 adsIDValue.3 i 3
results in:
DAR-SIM::adsIDValue.1 = INTEGER: 5
DAR-SIM::adsIDValue.2 = INTEGER: 3
DAR-SIM::adsIDMask.1 = INTEGER: 7
DAR-SIM::adsIDMask.2 = INTEGER: 4

Setting columns from the different tables causes problems too.  If the
objects are being set for different rows it works fine.

snmpset -v2c -c admin localhost adsEIDValue.2 i 3 adsIDMask.5 i 4
results in:
DAR-SIM::adsEIDValue.2 = INTEGER: 3
DAR-SIM::adsIDMask.5 = INTEGER: 4

If the objects from the different tables are in the same row it will
treat the second object as if its a column in the first table.

snmpset -v2c -c admin localhost adsEIDValue.2 i 11 adsIDMask.2 i 12
results in:
DAR-SIM::adsEIDValue.2 = INTEGER: 11
DAR-SIM::adsEIDMask.2 = INTEGER: 12

snmpset -v2c -c admin localhost adsIDMask.2 i 4 adsWordPosition.2 i 6
results in:
DAR-SIM::adsIDMask.2 = INTEGER: 4
DAR-SIM::adsIDValue.2 = INTEGER: 6

This causes big problems when I try to set a mask from one of the
other tables after I have set adsWordPosition.

snmpset -v2c -c admin localhost adsWordPosition.2 i 11 adsIDMask.2 i 12
Error in packet.
Reason: noCreation (That table does not support row creation or that
object can not ever be created)
Failed object: DAR-SIM::adsIDMask.2

I think its trying to set column three of adsWordTable but there is no
column three.
Doing any of these commands individually they will work fine and it
always correctly handles the first obect.  The command itself reports
everything was done correctly its only when I do a walk of the
branch/tables that I see that it was not (except for in the case right
above).  Anyone know if I'm trying to do something that's not supposed
to be done?  If it's a bug anyone have any ideas where I might start
looking?

Thanks,
Chris


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO September
19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
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