Re: mib2c.iterate.conf generates errors
Dave Shield <[email protected]>
| Newsgroups | gmane.network.net-snmp.user |
|---|---|
| Message-ID | <CAKoMtGaWGk43oYECOAz7MqZfgejOBNneqUiPMaCh8+SUx02FKw@mail.gmail.com> |
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