problem creating row

[Frank Fock]

Marcus,

It seems that the MIB definition you used to generate
the code for AGENT++ is missing the IMPLIED keyword
in the INDEX clause of your table. If the IMPLIED
keyword is not used, AGENT++ expects a length
subidentifier before each variable length subindex.
So the first subindentifier of the OID ("1") is
interpreted as length of the OID which have to fail.

Hope this helps.

Best regards,
Frank

Hellsten, Marcus wrote:
> I have a table with an index composed of two columns, an IPAddress and 
> an OID. rowStatus is not used (don't ask). Initializing the table with a 
> bunch of rows, changing them, and deleting them works fine. However, 
> when I try to create a new row (by doing a set on a column that has 
> read-create access) it does not work.
> 
> The OID of the set request can be for example:
> 
> 1.3.6.1.4.1.1618.2.2.2.1.1.3.192.168.3.2.1.3.6.1.4.1.1618.3.5.3.1
> 
> The index part of this is:
> 
> 192.168.3.2.1.3.6.1.4.1.1618.3.5.3.1
> 
> MibTable::prepare_set_request calls MibTable::could_ever_be_managed, 
> which in turn calls is_index_valid. is_index_valid succefully(?) goes 
> through the for loop checking the the two indexes. It then returns false 
> on this line:
> 
> return ((o.len() == l) && (i >= index_len));
> 
> This is because o.len() returns 15 and not 1. 15 is the length of the 
> index shown above.
> 
> I don't understand the significance of this line. Any suggestions on 
> what I might be doing wrong?
> 
> Thank you for your time,
> Marcus
> 
>