Greetings,
I inherited an SNMP table with the following definition. Before I open my mouth
and complain and make a fool of myself, I would like to know from the experts
that the table definition is correct and perhaps it is the way I used mib2c to
compile it that is the problem. BTW, I used mib2c.iterate_access.conf.
Thanks,
Mostafa
TableEntry ::= SEQUENCE {
rowIndex Integer32 not-accessible
column1 Integer32 read-create
column2 Integer32 read-create
column3 Integer32 read-create
column4 Integer32 read-create
column5 Integer32 read-only
column6 Integer32 read-only
column7 Integer32 read-only
column8 Integer32 read-only
column9 Integer32 read-only
column10 Integer32 read-only
tableRowStatus RowStatus }
Would the SNMP manager be able to create table rows based on the
above-mentioned table definition knowing that some columns are read only?
If I execute the bash script listed below to set row 1 create-read columns only
($snmpV3Params contains all snmpV3 required authentication and privacy
parameters), I only get an error with the last statement that performs the
create and go. I am guessing that the read only columns are causing the problem.
Error in packet.
Reason: inconsistentValue (The set value is illegal or unsupported in some way)
Failed object: set tableRowStatus.1
/***************** The last part of the bash script
******************************/
set()
{
snmpset $snmpV3Params $ip "$@"
}
# Delete row 1
set tableRowStatus.1 i 6
# Populate the columns that can be created
set column1.1 i 1
set column2.1 i 32
set column3.1 i 1
set column4.1 i 2
# create & go
set tableRowStatus.1 i 4
_______________________________________________
Net-snmp-users mailing list
Net-snmp-users@lists.sourceforge.net
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users
