This is an off-topic post. Still, the issues raised are sure to be of interest to implementors of agents, and I would very much like to receive comments.
As an alternative to a table, would it be acceptable to set a selector via one OID, and based upon that selector value, get other OIDs, each with corresponding dependent values? This is to say, instead of a table, and using an index to get the OIDs of one row of the table, use this alternative method for getting corresponding data elements. My interest in such a scheme is as a means to extend application of a standardised MIB. For instance, say a MIB is constructed for a device that exists in a standalone fashion. Now, suppose a different device provider builds a device that now contains within it two (or more) of the original standalone device. It could be most efficient to use the existing MIB for the standalone device, and use a small enterprise MIB to provide a means to select which of the several standalone devices shall be reported upon by walking the standardised MIB. How acceptable is such a solution? Is the better choice to develop a different MIB (expectedly an enterprise MIB), and not to use the standardised MIB in such a fashion? What is the relevant practice and experience? William R. Buckley President SoftNerd, A California Corporation Director Emeritus, International Core Wars Society [EMAIL PROTECTED] 415-756-6699 ------------------------------------------------------- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click _______________________________________________ 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
