0 values in SET request returns BAD values

[Alex Finogenov]

Robert,

*If I remember correctly*, this is caused by MibTable::ready() rejecting a
SET if the value for the object's value type equals to the varbind value
found in the request, i.e. when there is no change in value after SET. Since
the initial value for an integral type (int, long) by default is 0, the
Agent++ will reject the SET request if the varbind's value is 0.

If you don't want to mess with the code, a workaround is to define DEFVAL in
the MIB for those objects. The leaves with DEFVAL in the MIB will not be
tested for the mentioned condition.

Alex

> -----Original Message-----
> From: Adelberg, Robert (RADELBER) [mailto:RADELBER____arinc.com]
> Sent: Friday, September 21, 2001 10:34 AM
> To: agentpp-dl____fock.de
> Subject: 0 values in SET request returns BAD values
> 
> 
> Hi,
> 
> Without going into much detail, I have a table with 10 
> columns, of which all
> are either
> Integer32, INTEGER, or OctetStr. It is doubly indexed on the first two
> parameters which are
> INTEGER.
> 
> When I do a set request to add a new row, if any of the 
> Integer32 values are
> zero, the
> agent returns Error Bad Value, on the first parameter, an 
> index (inot the
> zero parameter).
> 
> If I set all the values to at least 1, it works.
> 
> I think it is being rejected in the MibTable() set request 
> because I never
> see the individual
> parameter set request being called.
> 
> Does anyone have an idea as to what might be causing this?
> 
> 
> 
> Rob Adelberg
> Arinc, Inc.
>