Re: mib2c.iterate.conf generates errors

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


    mpbcRMHNotifiedNMSipAddressTable OBJECT-TYPE
        SYNTAX              SEQUENCE OF MpbcRMH-NotifiedNMSipAddressEntry
        MAX-ACCESS          not-accessible
        STATUS              current
        DESCRIPTION         "Please replace this text with your
description."
        ::= { mpbcRMHNetMgt 1 }

    mpbcRMHNotifiedNMSipAddressEntry OBJECT-TYPE
        SYNTAX              MpbcRMH-NotifiedNMSipAddressEntry
        MAX-ACCESS          not-accessible
        STATUS              current
        DESCRIPTION         "Please replace this text with your
description."
        INDEX               {
                                mpbcRMHNotifiedNMSipAddress-IP,
                                mpbcRMHNotifiedNMSipAddress-Description
                            }
        ::= { mpbcRMHNotifiedNMSipAddressTable 1 }

    MpbcRMH-NotifiedNMSipAddressEntry ::= SEQUENCE {
        mpbcRMHNotifiedNMSipAddress-IP
            IpAddress,
        mpbcRMHNotifiedNMSipAddress-Description
            OCTET STRING,
        mpbcRMHNotifiedNMSipAddress-Enabled
            TruthValue
    }

    mpbcRMHNotifiedNMSipAddress-IP OBJECT-TYPE
        SYNTAX              IpAddress
        MAX-ACCESS          read-write
        STATUS              current
        DESCRIPTION         "Please replace this text with your
description."
        ::= { mpbcRMHNotifiedNMSipAddressEntry 1 }

    mpbcRMHNotifiedNMSipAddress-Description OBJECT-TYPE
        SYNTAX              OCTET STRING
        MAX-ACCESS          read-write
        STATUS              current
        DESCRIPTION         "Please replace this text with your
description."
        ::= { mpbcRMHNotifiedNMSipAddressEntry 2 }

    mpbcRMHNotifiedNMSipAddress-Enabled OBJECT-TYPE
        SYNTAX              TruthValue
        MAX-ACCESS          read-write
        STATUS              current
        DESCRIPTION         "Please replace this text with your
description."
        ::= { mpbcRMHNotifiedNMSipAddressEntry 3 }





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

>    [ First - *please* don't mail me privately, without copying
>     any responses to the mailing list.  I don't have the time
>     or inclination to offer private, unpaid, SNMP consultancy.
>     Keep discussions to the list, where others can both learn
>     and offer advice.  Thanks.   ]
>
>
> On 31 January 2012 21:10, Francois Bouchard <[email protected]>
> wrote:
> >> What is the MIB definition of the mpbcRMHAlarmIndex object?
> > Its a read-only table, updated from cached data.
>
> No - not
>   "what is some vague hand-wavy description of sort-of what the table is
> about"
>
> What is the actual, concrete, exact MIB definition of the specific MIB
> object
> mpbcRMHAlarmIndex?
> I'm asking for the fragment of the MIB file that defines this object.
> The block:
>
>   mpbcRMHAlarmIndex  OBJECT-TYPE
>       :
>   ::= { mpbcRMHAlarmEntry 1 }
>
> (or whatever it actually is)
>
>
>
>
> >>My best guess is that the object has been defined as 'read-only'
> >>rather than 'not-accessible', so it's being picked up by the code
> >>dealing with accessible columns, as well as the code concerned
> >>with indexes.
> > Now with a read-write table (3 columns, and x rows) it is doing the same
> > repetition with mib2c.table_data.conf
>
> Very possibly.
> Can you please provide the (exact) MIB definition of this table
> so we can identify why this is happening.
>
>
>
> > i.e. generated code:
> >     /* Index values */
> >     in_addr_t NotifiedNMSipAddress_IP;
> >     char NotifiedNMSipAddress_Description[NNN];
> >     size_tNotifiedNMSipAddress_Description_len;
> >
> >     /* Column values */
> >     in_addr_t NotifiedNMSipAddress_IP;
> >     in_addr_t old_NotifiedNMSipAddress_IP;
> >     char NotifiedNMSipAddress_Description[NNN];
> >     size_t NotifiedNMSipAddress_Description_len;
> >     char old_NotifiedNMSipAddress_Description[NNN];
> >     size_t old_NotifiedNMSipAddress_Description_len;
> >     long NotifiedNMSipAddress_Enabled;
> >     long old_NotifiedNMSipAddress_Enabled;
>
>
> In the absence of the necessary information to explain this
> definitively, I'll stand by my provisional explanation above.
> My guess is that the MIB table is improperly defined
> (with readable index values)
>
> 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.