On 2 February 2012 21:29, Francois Bouchard <[email protected]> wrote:
> I changed the MIB and it's compiling now :
>
> /* Index values */
> in_addr_t mpbcRMHNotifiedNMSipAddress-IP;
> char mpbcRMHNotifiedNMSipAddress-Description[NNN];
> size_t mpbcRMHNotifiedNMSipAddress-Description_len;
>
> /* Column values */
> long mpbcRMHNotifiedNMSipAddress-Enabled;
> long old_mpbcRMHNotifiedNMSipAddress-Enabled;
>
>
>
> That shall give an OID table accessible by two indexes and one writable
> column?
That looks right, yes.
> but another quick question, what exactly is the min/mac column setting?
> Is it used for expandable table size (AUGMENT) ?
No - it indicates the number associated with the first and last (accessible)
column objects.
Given the MIB definition
mpbcRMHNotifiedNMSipAddress-Enabled OBJECT-TYPE
:
::= { mpbcRMHNotifiedNMSipAddressEntry 3 }
(and that this is the only directly accessible object), I would expect
table_info->min_column = table_info->max_column = 3;
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
[email protected]
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users
