[AGENT++] multi-var set for a table

siva chelliah s.chelliah at samsung.com
Sat Mar 6 20:32:07 CET 2004



One more question. I do not think we are using your MibTable object in our
code, but ...

If the manager issues the following command (after creating the row), should
I update both columns before activating the table?

1)snmpget ... <row status> 5
2)snmpset ...  <col1> data1  <row status> 1 <col2 > data2

Basically I am trying to implement create and go feature and wondering what
to do if the manager uses the above to activate the table.  In create and
go, I am planning to update both columns before activating the table.

Thanks,

Please update your address book with my new e-mail address:
s.chelliah at samsung.com
Siva Chelliah
Samsung Telecommunications America
1301 East Lookout Dr.   Richardson, TX 75082
972-761-7903
Friends come and go, but enemies accumulate - Murphy's Law #1024


-----Original Message-----
From: Frank Fock [mailto:fock at agentpp.com] 
Sent: Thursday, March 04, 2004 1:35 AM
To: siva chelliah
Cc: agentpp at agentpp.org
Subject: Re: [AGENT++] multi-var set for a table

Comments inline:

siva chelliah wrote:

>I do not see that is happening. Can you point out the code/class?
>
>  
>
Take a look at MibTable::check_creation. Although it is called for a
specific index, it processes the RowStatus first.

>Also what happens when someone has more than one request for row status?
>Interesting test case!
>
>  
>
The SNMP protocol specification says that the outcome of this is undefined.

>For example:
>      Snmpset <oid for col1> ... <oid for row status > integer 5 <oid for
>row status > integer 6
>
>Should this create and then delete it right away?!
>  
>
You cannot be sure whether the row is created or deleted by the agent, 
because
it is not defined in which order the agent has to process variable 
bindings.

Best regards,
Frank






More information about the AGENTPP mailing list