Large MIB table - do not want cache or copy
Joe Lorenz <[email protected]>
| Newsgroups | gmane.network.net-snmp.user |
|---|---|
| Message-ID | <[email protected]> |
I'm trying to implement a MIB defining a very large (read-only) table (~250k rows). My data source API already provides get/get-next in correct order and data format. I expected it to be straightforward to map the appropriate handler actions, but I'm struggling with the details. It seemed like mib2c.raw-table.conf would be the right way to go, avoiding any caching or copying of the entire set of table data (which is a requirement). What I've been unable to find is any actual example that uses this mib2c config. I'm lost on what needs to be done with the various structures (indexes, etc.) especially for the get-next. The table is read-only. I have no need to implement row add/remove. I'm using version 5.7.2.1 of the software collection. If anyone can point me to an example or otherwise provide some hints, that would be most helpful. Many thanks, -Joe ------------------------------------------------------------------------------ _______________________________________________ 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