Re: mib2c.iterate.conf generates errors

Francois Bouchard <[email protected]>
Newsgroups gmane.network.net-snmp.user
Message-ID <CAAZiaZcrp0bShhbf9-evZw3ti2UAm7EG_Zy0CJRjq1u9Y0Sg2Q@mail.gmail.com>
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?


but another quick question, what exactly is the min/mac column setting?  Is
it used for expandable table size (AUGMENT) ?
and for the  table_info->max_column = 4;
                  table_info->max_column = 4;

Thanks




Francois

2012/2/1 Dave Shield <[email protected]>

> On 1 February 2012 17:41, Francois Bouchard <[email protected]>
> wrote:
> >>What is the actual, concrete, exact MIB definition of the specific MIB
> >> object mpbcRMHAlarmIndex?
> >
> > Here is the MIB OID definition that that the code in my last post comes
> > from.
>
>   [snip]
>
> Thanks.
> That confirms my suspicion - the MIB definitions of the two index
> objects are not quite correct:
>
>
>
>
> >     mpbcRMHNotifiedNMSipAddressEntry OBJECT-TYPE
>                 :
> >         INDEX               {
> >                                 mpbcRMHNotifiedNMSipAddress-IP,
> >                                 mpbcRMHNotifiedNMSipAddress-Description
> >                             }
>
> These two are the index objects for the table...
>
>
> >     mpbcRMHNotifiedNMSipAddress-IP OBJECT-TYPE
> >         MAX-ACCESS          read-write
>
> >     mpbcRMHNotifiedNMSipAddress-Description OBJECT-TYPE
> >         MAX-ACCESS          read-write
>
> so ought to be defined as "not-accessible"
>
>
> >     mpbcRMHNotifiedNMSipAddress-Enabled OBJECT-TYPE
> >         MAX-ACCESS          read-write
>
> This is the only column object that needs to be implemented.
>
>
> If you make the two index object "not-accessible", and re-run
> mib2c,  you should find that the data structure looks closer
> to what you were expecting.
>
>
> Dave
>

------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
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-d2d

_______________________________________________
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
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.