Problem with creating a new row in SNMP table

Rachwal Waldemar-AWR001 <>
Wed Jan 11 14:52:53 CET 2006


I have stuck at the attempt of creating a new row in my SNMP table.
I'm giving 'inconsistentValue' on column (in the MIB : btsRowStatus = {
btsEntry 114 }) which is of the RowStatus type.

This is the first message I send to the agent, so the table should be
empty.
The value of btsRowStatus in SET-REQUEST is 4 which is createAndGo.
The first and the last two varbinds in the PDU are simple variables (not
table columns),
but it should not matter, I assume (these vars are additional
correlation tags and journal number required by the application).

ACCESS rights of all of the columns, including btsRowStatus, are "cr-"
create-read, so they should be okay?

The agent chokes while applying table_func with 'is_set_ok':

   apply: snmp_generic,table_func,[is_set_ok,
                                   [466944,0,1],
                                   [{1,0},
                                    {2,0},
                                    {3,"4000M"},
                                    ...
                                    {114,4},  <--- btsRowStatus,
createAndGo(4), 3rd varbind
                                    {118,0},
                                    {123,0}],
                                   {btsTable,volatile}]


... and the log after "apply:"


** SNMP A-SYMBOLIC-STORE LOG: table info: btsTable
** SNMP A-LOCAL-DB LOG: table btsTable get element: 
   Indexes: [466944,0,1]
   Col:     1
** SNMP A-SYMBOLIC-STORE LOG: table info: btsTable
** SNMP MASTER-AGENT-worker(<0.67.0>) SETLIB LOG: 
   returned: {inconsistentValue,114}
** SNMP A-NET-IF LOG: reply pdu: 
 
{pdu,'get-response',5,inconsistentValue,3,[{varbind,[1,3,6,1,4,1,161,205
2,1,44,1,5,0],'Unsigned32',2147483653,1},{varbind,[1,3,6,1,4,1,161,2052,
1,44,1,6,0],'Unsigned32',2147483658,2},{varbind,[1,3,6,1,4,1,161,99,101,
1,3,1,1,1,114,466944,0,1],'INTEGER',4,3}...
** SNMP A-LOCAL-DB LOG: variable get: snmpEngineMaxMessageSize
** SNMP A-NET-IF INFO: time in agent: 261035 mysec

3> 
3> 
3> 

The full logs, from agent/erlang and manager/perl are attached to this
mail.
If MIBs are required to look at I can send them after some slimming as
they are proprietary stuff :(

Could anybody help? I have no idea what to do next :(

BTW, I'm also curious what is the best way to tackle such sort of
problems...
(a big land of unknown code but you're determined to utilize it)
Debugging, tracing? I read about, but have never used.

Thanks,
WR.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: inconsistentValue.zip
Type: application/x-zip-compressed
Size: 4979 bytes
Desc: inconsistentValue.zip
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20060111/4f08efd3/attachment.bin>


More information about the erlang-questions mailing list