1. what exactly meant by the automatic creation?
2. my requirement is like this,
xyz::= SEQUENCE {
a Unsigned32,
b Unsigned32,
c INTEGER,
d INTEGER,
rowstatus RowStatus
}
the object 'a' indicate the index to this table.
the object 'b' is having a default value as 2
But there is no default value for the object 'c' and 'd'
The snmp agent will create a row during the initialization with the
index '1'. Here the row status object will set to NotReady/NotInservice.
Right?
The question is, If i get a SNMPSET for the same row that is with the
index 1.
snmpset ..... localhost d.1 i 10 rowstatus.1 i createandwait
NOTE: we are not receiving set for the object 'c'.
how the agent will update that row in the table. Then agent will make
the rowstatus as "active"?
Regards,
Venkatgiri.
Dave Shield wrote:
2009/4/16 venkatgiri <[email protected]>:
Hi all,
i have a table like
xyz::= SEQUENCE {
a Unsigned32,
b Unsigned32,
c INTEGER,
d INTEGER,
rowstatus RowStatus
}
here i'm using "a" as a index for this table.
i don;t know the order of these objects coming in the SNMPSET right?
Correct.
Your users could send a request
snmpset .... localhost b.1 i 4 rowstatus.1 i createAndGo(4)
or
snmpset .... localhost rowstatus.1 i createAndGo(4) b.1 i 4
and the agent should treat these identically.
if so my question is, assume a row is not created in this table and SNMP
agent receives a SNMP SET command for the object "b"
snmpset ..... localhost b.1 i 4
shall i create a row for this table with the index 1
That depends on how the table has been defined.
If the description indicates that the table supports "automatic creation",
then you could indeed create a row with index 1.
In which case, you should probably be asking whether you need
a RowStatus column at all. (Maybe just for row deletion?)
If the table doesn't support automatic creation, then this request
would fail.
or i need to wait
the row status object to create a row and update the object "b".
If you receive a request
snmpset .... localhost rowstatus.1 i createAndGo(4)
then your agent should create a new row, but would *not*
assign a value for the column 'b', Each SET request is
processed independently - you don't remember values from
one failed request, and use them later.
Dave
------------------------------------------------------------------------------
Stay on top of everything new and different, both inside and
around Java (TM) technology - register by April 22, and save
$200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
300 plus technical and hands-on sessions. Register today.
Use priority code J9JMT32. http://p.sf.net/sfu/p
_______________________________________________
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
