Hi, I have been out of touch with SNMP community for several years! and now I have a cpmplex issue relating to it.
Currently we have two different management interfaces - CLI and SNMP. The managed data is stored in our backend code that is common to both CLI and SNMP. However, I would not like to expose my managed data directly to the SNMP subagent. So, we have an API exposed to the SNMP. The problem becomes a bit tricky when I have a table with dynamic row that can potentially have CREATE-WAIT set by the manager . As per SNMP protocol, set for columns can comes in different SNMP PDU. Let's say only column1 and col 2 is set and it comes in one PDU. Then col3 can come in different PDU. In addition, these columns are mandatory ( I don't wont to make them part of the index for the table). Unless all the mandatory parameter are received, I cannot call my backend API to create a row. I would like the subagent to handle this SNMP specific stuff without the backend knowing about all this. So, ideally I would want subagent to collect all columns set for a particular row and then call my API to create a row with all columns received. So, from subagent implementation, I was thinking that for this to happen, the SNMP subagent should "cache" all the requests coming in different SNMP PDU and create a row instance for the same and populte that row instance as when different PDU come. So, my questions are: 1) In latest version of net-snmp, I read that there is a something called row-context data structure. Does it handle the issue I have mentioned above ? I understand that there are two API that is generated per table. One to create a row context and other to commit it (either add/remove). I can understand that row context creation can happen when my RowStatus is set to createAndWait, but when will the commit function be called ? Is there anyway I can add a logic in subagent that once I received all 3 columsn, then I call the commit function inside which in turn will call my backend API ? 2) Is there any concept of caching out the cached data if for some reason I did not receive set for all mandatory columns I am expecting. This might happen let say col1 and col2 is set and came in one PDU, however, for some reason col3 in second PDU did not arrive at the agent. ( say manager got disconnected), then in that case will that cached data be flushed out by the subagent. TIA, Anurag _______________________________________________ Net-snmp-coders mailing list Net-snmp-coders@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
