02-14-2012 11:52 AM
Well, really trying to import CISCO-ENTITY-SENSOR-EXT-MIB in order to process traps from ASA with "snmp-server enable traps entity power-supply-failure" configured. Figures that CISCO-ENTITY-SENSOR-MIB is a prerequisite. After painstakingly loading up the MIB dependencies listed at http://tools.cisco.com/Support/SNMP/do/BrowseMIB.do?local=en&step=2&mibName=CISCO-ENTITY-SENSOR-MIB, it fails at the last juncture with
CISCO-ENTITY-SENSOR-MIB itself:
snmpttconvertmib --in=CISCO-ENTITY-SENSOR-MIB.my --out=/etc/snmp/snmptt.conf.cisco --debug
***** Processing MIB file *****
snmptranslate version: NET-SNMP version: 5.3.1
severity: Normal
File to load is: ./CISCO-ENTITY-SENSOR-MIB.my
File to APPEND TO: /etc/snmp/snmptt.conf.cisco
MIBS environment var: ./CISCO-ENTITY-SENSOR-MIB.my
mib name: CISCO-ENTITY-SENSOR-MIB
Processing MIB: CISCO-ENTITY-SENSOR-MIB
skipping a TRAP-TYPE / NOTIFICATION-TYPE line - probably an import line.
#
Line: 631
NOTIFICATION-TYPE: entSensorThresholdNotification
Variables: entSensorThresholdValue entSensorValue
Enterprise: entitySensorMIBNotifications
Looking up via snmptranslate: CISCO-ENTITY-SENSOR-MIB::entSensorThresholdNotification
No log handling enabled - turning on stderr logging
Cannot find module (ENTITY-MIB): At line 27 in ./CISCO-ENTITY-SENSOR-MIB.my
Cannot find module (CISCO-TC): At line 29 in ./CISCO-ENTITY-SENSOR-MIB.my
Cannot find module (CISCO-SMI): At line 31 in ./CISCO-ENTITY-SENSOR-MIB.my
Did not find 'entPhysicalIndex' in module #-1 (./CISCO-ENTITY-SENSOR-MIB.my)
Did not find 'EntPhysicalIndexOrZero' in module #-1 (./CISCO-ENTITY-SENSOR-MIB.my)
Did not find 'ciscoMgmt' in module #-1 (./CISCO-ENTITY-SENSOR-MIB.my)
Unlinked OID in CISCO-ENTITY-SENSOR-MIB: ciscoEntitySensorMIB ::= { ciscoMgmt 91 }
Undefined identifier: ciscoMgmt near line 33 of ./CISCO-ENTITY-SENSOR-MIB.my
Cannot adopt OID in CISCO-ENTITY-SENSOR-MIB: entitySensorMIBConformance ::= { ciscoEntitySensorMIB 3 }
Cannot adopt OID in CISCO-ENTITY-SENSOR-MIB: entitySensorMIBNotificationPrefix ::= { ciscoEntitySensorMIB 2 }
Cannot adopt OID in CISCO-ENTITY-SENSOR-MIB: entitySensorMIBObjects ::= { ciscoEntitySensorMIB 1 }
Cannot adopt OID in CISCO-ENTITY-SENSOR-MIB: entitySensorMIBNotifications ::= { entitySensorMIBNotificationPrefix 0 }
Cannot adopt OID in CISCO-ENTITY-SENSOR-MIB: entSensorValueEntry ::= { entSensorValueTable 1 }
Cannot adopt OID in CISCO-ENTITY-SENSOR-MIB: entitySensorNotifCtrlGlobalGroup ::= { entitySensorMIBGroups 5 }
Cannot adopt OID in CISCO-ENTITY-SENSOR-MIB: entitySensorValueGroupSup1 ::= { entitySensorMIBGroups 4 }
Cannot adopt OID in CISCO-ENTITY-SENSOR-MIB: entitySensorThresholdNotificationGroup ::= { entitySensorMIBGroups 3 }
Cannot adopt OID in CISCO-ENTITY-SENSOR-MIB: entitySensorThresholdGroup ::= { entitySensorMIBGroups 2 }
Cannot adopt OID in CISCO-ENTITY-SENSOR-MIB: entitySensorValueGroup ::= { entitySensorMIBGroups 1 }
Cannot adopt OID in CISCO-ENTITY-SENSOR-MIB: entSensorThresholdTable ::= { entSensorThresholds 1 }
Cannot adopt OID in CISCO-ENTITY-SENSOR-MIB: entSensorMeasuredEntity ::= { entSensorValueEntry 8 }
Cannot adopt OID in CISCO-ENTITY-SENSOR-MIB: entSensorValueUpdateRate ::= { entSensorValueEntry 7 }
Cannot adopt OID in CISCO-ENTITY-SENSOR-MIB: entSensorValueTimeStamp ::= { entSensorValueEntry 6 }
Cannot adopt OID in CISCO-ENTITY-SENSOR-MIB: entSensorStatus ::= { entSensorValueEntry 5 }
Cannot adopt OID in CISCO-ENTITY-SENSOR-MIB: entSensorValue ::= { entSensorValueEntry 4 }
Cannot adopt OID in CISCO-ENTITY-SENSOR-MIB: entSensorPrecision ::= { entSensorValueEntry 3 }
Cannot adopt OID in CISCO-ENTITY-SENSOR-MIB: entSensorScale ::= { entSensorValueEntry 2 }
Cannot adopt OID in CISCO-ENTITY-SENSOR-MIB: entSensorType ::= { entSensorValueEntry 1 }
Cannot adopt OID in CISCO-ENTITY-SENSOR-MIB: entSensorThresholdEntry ::= { entSensorThresholdTable 1 }
Cannot adopt OID in CISCO-ENTITY-SENSOR-MIB: entSensorThreshNotifGlobalEnable ::= { entSensorGlobalObjects 1 }
Cannot adopt OID in CISCO-ENTITY-SENSOR-MIB: ciscoEntitySensorMIB ::= { ciscoMgmt 91 }
Cannot adopt OID in CISCO-ENTITY-SENSOR-MIB: entSensorGlobalObjects ::= { entitySensorMIBObjects 3 }
Cannot adopt OID in CISCO-ENTITY-SENSOR-MIB: entSensorThresholds ::= { entitySensorMIBObjects 2 }
Cannot adopt OID in CISCO-ENTITY-SENSOR-MIB: entSensorValues ::= { entitySensorMIBObjects 1 }
Cannot adopt OID in CISCO-ENTITY-SENSOR-MIB: entSensorThresholdNotificationEnable ::= { entSensorThresholdEntry 6 }
Cannot adopt OID in CISCO-ENTITY-SENSOR-MIB: entSensorThresholdEvaluation ::= { entSensorThresholdEntry 5 }
Cannot adopt OID in CISCO-ENTITY-SENSOR-MIB: entSensorThresholdValue ::= { entSensorThresholdEntry 4 }
Cannot adopt OID in CISCO-ENTITY-SENSOR-MIB: entSensorThresholdRelation ::= { entSensorThresholdEntry 3 }
Cannot adopt OID in CISCO-ENTITY-SENSOR-MIB: entSensorThresholdSeverity ::= { entSensorThresholdEntry 2 }
Cannot adopt OID in CISCO-ENTITY-SENSOR-MIB: entSensorThresholdIndex ::= { entSensorThresholdEntry 1 }
Cannot adopt OID in CISCO-ENTITY-SENSOR-MIB: entSensorThresholdNotification ::= { entitySensorMIBNotifications 1 }
Cannot adopt OID in CISCO-ENTITY-SENSOR-MIB: entSensorValueTable ::= { entSensorValues 1 }
Cannot adopt OID in CISCO-ENTITY-SENSOR-MIB: entitySensorMIBGroups ::= { entitySensorMIBConformance 2 }
Cannot adopt OID in CISCO-ENTITY-SENSOR-MIB: entitySensorMIBCompliances ::= { entitySensorMIBConformance 1 }
Cannot adopt OID in CISCO-ENTITY-SENSOR-MIB: entitySensorMIBComplianceV04 ::= { entitySensorMIBCompliances 4 }
Cannot adopt OID in CISCO-ENTITY-SENSOR-MIB: entitySensorMIBComplianceV03 ::= { entitySensorMIBCompliances 3 }
Cannot adopt OID in CISCO-ENTITY-SENSOR-MIB: entitySensorMIBComplianceV02 ::= { entitySensorMIBCompliances 2 }
Cannot adopt OID in CISCO-ENTITY-SENSOR-MIB: entitySensorMIBComplianceV01 ::= { entitySensorMIBCompliances 1 }
Unknown object identifier: CISCO-ENTITY-SENSOR-MIB::entSensorThresholdNotification
OID:
Done
Total translations: 1
Successful translations: 0
Failed translations: 1
Those three allegedly missing MIBs are right there in the same directory, and have been imported earlier (though some had no "translation"):
ls
CISCO-ENTITY-SENSOR-EXT-MIB.my CISCO-TC.my RFC-1212.my SNMPv2-CONF.my SNMPv2-TC-V1SMI.my
CISCO-ENTITY-SENSOR-MIB.my ENTITY-MIB.my RFC-1215.my SNMPv2-SMI.my v1
CISCO-SMI.my RFC1155-SMI.my SNMP-FRAMEWORK-MIB.my SNMPv2-TC.my
snmpttconvertmib --in=CISCO-SMI.my --out=/etc/snmp/snmptt.conf.cisco --debug
***** Processing MIB file *****
snmptranslate version: NET-SNMP version: 5.3.1
severity: Normal
File to load is: ./CISCO-SMI.my
File to APPEND TO: /etc/snmp/snmptt.conf.cisco
MIBS environment var: ./CISCO-SMI.my
mib name: CISCO-SMI
Processing MIB: CISCO-SMI
Done
Total translations: 0
Successful translations: 0
Failed translations: 0
snmpttconvertmib --in=CISCO-TC.my --out=/etc/snmp/snmptt.conf.cisco --debug
***** Processing MIB file *****
snmptranslate version: NET-SNMP version: 5.3.1
severity: Normal
File to load is: ./CISCO-TC.my
File to APPEND TO: /etc/snmp/snmptt.conf.cisco
MIBS environment var: ./CISCO-TC.my
mib name: CISCO-TC
Processing MIB: CISCO-TC
Done
Total translations: 0
Successful translations: 0
Failed translations: 0
snmpttconvertmib --in=ENTITY-MIB.my --out=/etc/snmp/snmptt.conf.cisco --debug
***** Processing MIB file *****
snmptranslate version: NET-SNMP version: 5.3.1
severity: Normal
File to load is: ./ENTITY-MIB.my
File to APPEND TO: /etc/snmp/snmptt.conf.cisco
MIBS environment var: ./ENTITY-MIB.my
mib name: ENTITY-MIB
Processing MIB: ENTITY-MIB
skipping a TRAP-TYPE / NOTIFICATION-TYPE line - probably an import line.
#
Line: 1142
NOTIFICATION-TYPE: entConfigChange
Enterprise: entityMIBTrapPrefix
Looking up via snmptranslate: ENTITY-MIB::entConfigChange
OID: .1.3.6.1.2.1.47.2.0.1
Done
Total translations: 1
Successful translations: 1
Failed translations: 0
What am I missing?
Solved! Go to Solution.
02-16-2012 01:27 AM
yjdabear, nice to hear again from you!
I found this, but I am not sure if this is really the cause of your problem...
snmpttconvertmib relies on snmptranslate; and snmptranslate looks up for mib files in
$HOME/.snmp/mibs
/usr/local/share/snmp/mibs
put the prerequisite mib files into one of these directories and try to re-run snmpttconvertmib;
02-15-2012 09:49 AM
I've successfully tried to stay clear of this type of thing as much as I could so my response might be silly.
But one of the things I recall was that a 'somemib.my' file needed 'thatothermib', that was actually there in the directory as 'thatothermib.my', just like I downloaded it, but the mibcompiler was smart enough to look for 'thatothermib.mib'.
Not sure if is was referenced in the other mibfile with a specific extension of if it was the compiler trying to stop me.
Never understood how they managed to make something so simple so complicated.
Cheers,
Michel
02-16-2012 01:27 AM
yjdabear, nice to hear again from you!
I found this, but I am not sure if this is really the cause of your problem...
snmpttconvertmib relies on snmptranslate; and snmptranslate looks up for mib files in
$HOME/.snmp/mibs
/usr/local/share/snmp/mibs
put the prerequisite mib files into one of these directories and try to re-run snmpttconvertmib;
02-16-2012 11:40 AM
You're the man, Martin! (Sie sind der Mann???)
Sticking the mibs in the top level of either ~/.snmp/mibs or /usr/share/snmp/mibs did the trick, but not /usr/local/share/snmp/mibs. I had them in a subdirectory under /usr/share/snmp/mibs, which apparently doesn't fly with snmpttconvertmib/snmptranslate. Le Sigh.
.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide