On Tue, 2005-11-29 at 18:26 +0000, Patrick Welche wrote: > I tried > > snmptranslate -Tp -OS -m all -PW -Pe > > which gave .... things like: > > MODULE-IDENTITY MACRO (lines 55..79 parsed and ignored). > OBJECT-IDENTITY MACRO (lines 81..103 parsed and ignored). > OBJECT-TYPE MACRO (lines 212..298 parsed and ignored). > NOTIFICATION-TYPE MACRO (lines 302..334 parsed and ignored).
All from our (already-cut-down) SNMPv2-SMI file > TEXTUAL-CONVENTION MACRO (lines 8..48 parsed and ignored). >From SNMPv2-TC. I'd be tempted to simply comment out these particular macro. definitions, since they're hardcoded into the MIB parser, and we've already tweaked these two MIB files anyway. The same holds true for the macro definitions in SNMPv2-CONF > Warning: string too long: At line 643 in ..../SNMPv2-TC.txt That's the "RowStatus" description. I'd agree - this description *is* too long. Take it up with the SNMP working group that defined this syntax :-) > Warning: string too long: At line 529 in .../SNMPv2-MIB.txt Hmmm... That's the description of "snmpWarmStartNotificationGroup" within snmpBasicComplianceRev2. I'm surprised that is issuing a warning - it's only four lines (and a couple of hundred characters). Definitely warrents further investigation. > Warning: string too long: At line 186 in .../SNMP-FRAMEWORK-MIB.txt That's the description of the SnmpEngineID TC. A bit more reasonable to complain about this - it's not as ludicrous as the RowStatus description, but it's still 4K plus. Other "over-long" strings include DISMAN-EVENT-MIB: 1779, 1786 DISMAN-EXPRESSION-MIB: 435 DISMAN-SCHEDULE-MIB: 623, 683 EtherLike-MIB: 1480, 1501, 1523, ... HOST-RESOURCES-MIB: 1441, 1452 IEEE802dot11-MIB: 2650, 2658, 2666, 2674, 2682 IF-MIB: 1166, 1174, 1181, etc, etc NOTIFICATION-LOG-MIB: 687, 695, 706: SNMP-NOTIFICATION-MIB: 475, 487, 514, 526 SNMP-USER-BASED-SM-MIB: 268 SNMP-VIEW-BASED-ACM-MIB: 785 Most of these seem to be in the various MODULE-COMPLIANCE descriptions (apart from D-EXP-MIB::expExpression and S-USM-MIB::KeyChange which are legitimately long strings). Investigation is called for. > Warning: No known translation for type (SysOREntry): At line 204 in > ..../SNMPv2-MIB.txt > Warning: No known translation for type (SnmpTargetAddrEntry): At line 284 in > .../SNMP-TARGET-MIB.txt That warning seems to be issued for *every* table definition, where the XxxEntry SEQUENCE is defined after the xxxTable and xxxEntry objects that refer to it. Suppressing these will probably require a dedicated hack in the MIB parsing code. > My guess is the error is among the 3com mibs, > but it's hard to see the wood from the trees - any thoughts? Note that all of these problems are *warnings* rather than errors, so it might be worth omitting the '-PW' (verbose warning) flag, and just run with '-Pe'. Dave ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
