Hi,
When I try and import some Mitel Networks MIBs I get the following error:
Missing Import Module: MITEL-MIB Line 26. |
I have found the MITEL-MIB in the list of all the import MIB files and imported that correctly but still erroring.
Any ideas?
Thanks
Gavin
Article Comments
Hi Luciano,
I have checked the folder and it does already have the MITEL-MIB file in there.
I have also opened the file as suggested and in side is the following:
ITEL-MIB DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, OBJECT-IDENTITY, OBJECT-TYPE, enterprises, Integer32 FROM SNMPv2-SMI TEXTUAL-CONVENTION FROM SNMPv2-TC MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF ifIndex FROM IF-MIB;
But its still not importing.
Any ideas? I have tried to copy those files to a new folder and tht didnt do anything either.
Regards
Gavin
Oct, 2018 - Permalink
Hello Gavin,
thank you for your reply.
I'm not sure if this was an issue while copy-pasting or if there is a typo in the MIB, but:
MITEL-MIB != ITEL-MIB |
If there is a typo in the MIB's name, then the importer won't recognize it as the proper file. Also, please make sure that both files are in the exact same folder when importing the MIB.
Best Regards,
Luciano Lingnau [Paessler Support]
Oct, 2018 - Permalink
Hi,
Yes it was a copy and paste issue, see below:
MITEL-MIB DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, OBJECT-IDENTITY, OBJECT-TYPE, enterprises, Integer32 FROM SNMPv2-SMI TEXTUAL-CONVENTION FROM SNMPv2-TC MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF ifIndex FROM IF-MIB;
The MITEL-MIB imports fine, its only when I try and inport the following MIB do i see the error:
MITEL-IperaVoiceLAN-MIB DEFINITIONS ::= BEGIN IMPORTS OBJECT-TYPE FROM RFC-1212 TRAP-TYPE FROM RFC-1215 DisplayString, sysName FROM RFC1213-MIB mitelAppCallServer, mitelConfCompliances, mitelConfAgents, mitelGrpIpera3000, mitelIdCsIpera3000 FROM MITEL-MIB; mitelAppCsIpera3000 OBJECT IDENTIFIER ::= {mitelAppCallServer 2} -- "1" being used for sx2000 as mitelAppCs2000 -- MODULE-IDENTITY -- LAST-UPDATED "20140227000000Z" -- ORGANIZATION "MITEL Corporation" -- CONTACT-INFO "MITEL Corporation
They are both in the same folder.
Regards
Gavin
Oct, 2018 - Permalink
Hello there,
thank you for your reply.
In this case please share a link from where both MIB files can be obtained and I will give this a go and try to find any explanation.
Best Regards,
Luciano Lingnau [Paessler Support]
Oct, 2018 - Permalink
here you go: (link removed)
Please let me know once downloaded so I can remove
Oct, 2018 - Permalink
Thank you for your reply. I've downloaded the zip. Here's the list of contents:
C:\Users\llingnau\Downloads\1108124\SNMP_13.2.0.17-20181026T124713Z-001\SNMP_13.2.0.17>dir 26/10/2018 12:47 <DIR> . 26/10/2018 12:47 <DIR> .. 23/02/2015 15:27 51.032 BRIDGE-MIB 23/02/2015 15:27 84.584 EtherLike-MIB 23/02/2015 15:27 68.178 HOST-RESOURCES-MIB 23/02/2015 15:27 24.881 IANAifType-MIB 23/02/2015 15:27 71.814 IF-MIB 23/02/2015 15:27 97.627 MAU-MIB 23/02/2015 15:27 9.835 MITEL-APPCMN-MIB 23/02/2015 15:26 5.652 MITEL-APPLICATION-MON-MIB 23/02/2015 15:27 4.209 MITEL-APPLICATION-PLATFORM-LIST-MIB 23/02/2015 15:27 7.525 MITEL-APPLIST-MIB 23/02/2015 15:27 9.694 MITEL-BCM-MIB 23/02/2015 15:26 36.726 MITEL-BWM-MIB 23/02/2015 15:27 12.057 MITEL-CMNALM-MIB 23/02/2015 15:26 56.379 MITEL-DHCP-MIB 23/02/2015 15:26 6.462 MITEL-DNSGROUP-MIB 23/02/2015 15:27 8.237 MITEL-ERN 23/02/2015 15:26 16.511 MITEL-IPFILTER-MIB 23/02/2015 15:26 2.393 MITEL-IPGROUP-MIB 23/02/2015 15:26 7.293 MITEL-IPLOGICAL-MIB 23/02/2015 15:26 2.067 MITEL-IPNET-DATABASE-MIB 23/02/2015 15:26 2.153 MITEL-IPNETROUTER-MIB 23/02/2015 15:26 8.788 MITEL-IPVIRTUAL-MIB 23/02/2015 15:26 16.530 MITEL-LOGICAL-MIB 11/06/2015 08:32 17.849 MITEL-MIB 23/02/2015 15:26 5.067 MITEL-MN3100-CALL-CONTROL-MIB 23/02/2015 15:26 2.512 MITEL-MN3100-T1-TRAP-MIB 23/02/2015 15:26 9.030 MITEL-NAT-MIB 23/02/2015 15:26 10.127 MITEL-PPPGROUP-MIB 23/02/2015 15:27 1.634 MITEL-PROPIPNETWORKING-MIB 11/06/2015 08:32 20.848 MITEL-RESOURCE-MIB 23/02/2015 15:27 3.745 MITEL-RIP2EXTENSION-MIB 23/02/2015 15:27 8.110 MITEL-ROUTERGROUP-MIB 23/02/2015 15:27 2.958 MITEL-TRAPGROUP-MIB 23/02/2015 15:27 5.079 MITEL-VOICE-MAIL-MIB 23/02/2015 15:27 5.588 MITEL-WANBACKUP-MIB 23/02/2015 15:26 35.308 mitelipera3000mib 23/02/2015 15:26 13.949 mtlcs2000mib 23/02/2015 15:27 32.566 P-BRIDGE-MIB 23/02/2015 15:27 67.177 Q-BRIDGE-MIB 23/02/2015 15:27 79.838 RFC1213-MIB 23/02/2015 15:27 117.659 RFC1271-MIB 23/02/2015 15:27 148.032 RMON-MIB 23/02/2015 15:27 205.275 RMON2-MIB 23/02/2015 15:27 10.771 RSTP-MIB 23/02/2015 15:27 22.380 SNMP-FRAMEWORK-MIB 23/02/2015 15:27 29.354 SNMPv2-MIB 23/02/2015 15:27 79.316 TOKEN-RING-RMON-MIB 47 File(s) 1.544.799 bytes 2 Dir(s) 26.773.692.416 bytes free
It doesn't appear that there is any MIB named MITEL-IperaVoiceLAN-MIB in the zip. This is the filename you've mentioned (that produced errors during the import).
C:\Users\llingnau\Downloads\1108124\SNMP_13.2.0.17-20181026T124713Z-001\SNMP_13.2.0.17>dir *IperaVoice* Directory of C:\Users\llingnau\Downloads\1108124\SNMP_13.2.0.17-20181026T124713Z-001\SNMP_13.2.0.17 File Not Found
Would you mind elaborating?
Oct, 2018 - Permalink
Hi,
No, the MIB im trying to import is mitelipera3000mib that produces the error.
Regards
Gavin
Oct, 2018 - Permalink
Hello Gavin,
thank you for your reply and confirming the actual name of the MIB.
As it turns out the issue appears to be the extension. PRTG only scans the following file formats for the MIB: *.mib, *.my, *.txt when looking for dependent MIBs.
The MITEL-MIB file has no extension, as a result it doesn't get scanned by the MIB Importer when importing the mitelipera3000mib. As soon as you rename it to MITEL-MIB.mib the import will work. I've tested it out.
Best Regards,
Luciano Lingnau [Paessler Support]
Oct, 2018 - Permalink
Hello and thank you for your inquiry.
This error indicates that a required MIB file (mentioned in the error) is not present in the folder where the MIB you're importing is located. Please refer to:
If there is already a file called MITEL-MIB in the folder from which you're importing the other MIB, please open the file in a text editor and make sure it actually is the MIB (and not something else). To be considered a MIB the file needs to contain the following:
Best Regards,
Luciano Lingnau [Paessler Support]
Oct, 2018 - Permalink