On 27 February 2012 22:05, Francois Bouchard <francois.bouch...@mpbc.ca> wrote: > There is two tables in the MIB. Table 1 is mpbcRMHAlarmTable, and the > second one is mpbcRMHOSUTable, bath use. > For some reason the get table on mpbcRMHAlarmTable loads the correct table > (table 1) but then automatically loads another table after (table 2 (the > next table)).
What do you mean by "automatically" ? Are you talking about regular timed reloading of the cached data, or what happens when you run an "snmpwalk" command against the agent? Remember that snmpwalk expands to a series of GetNext requests which is repeated until it runs off the end of the table. It doesn't know when to stop - it will keep sending GetNext requests until it receives an answer that isn't part of the requested area (which will then be discarded) That final GetNext request will trigger the next accessible OID supported by the agent - which presumably comes from the mpbcRMHOSUTable This is a standard behaviour when walking any MIB table Dave ------------------------------------------------------------------------------ Try before you buy = See our experts in action! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-dev2 _______________________________________________ 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
