I've recieved mib files from the Dlink Support. In the MIB import utility i click on browse an pick one of the files. OMSA says.. "no traps found in FILENAME". I've opened the files in an MIB Editor/Browser. (I am not an expert) but I think they should be fine...
Thanks for your post. From the message it looks like the MIB file you tried importing did not contain definitions for SNMP traps. If you can provide the specific file name, we can check to see if there is any trap information available in that MIB. MIB files contain information about various attributes and may or may not contain trap definitions.
This link does not work for me. I wonder if it got mangled in the post.
Open the mibs in notepad and search for the words "TRAP-TYPE" or "NOTIFICATION-TYPE". Those are your trap objects. If you don't see those, then no traps in that mib, and look at the next one. Or maybe email dlink support to see which mibs actually have traps.
there are some "TRAP-TYPE" lines in the file. But I recieve still the same error. If I try to parse a File with "NOTIFICATION-TYPE" I can browse the mib.
So thanks for all your help. I've anybody knows why the TRAP-TYPE files doesnt work, pls let me know.
I ve tried several files. Im just at the beginning of my "monitoring career", is it wrong to import every trap possible as long they are from a device that is availible in our network?
If you give me the exact name of the file you tried, we can review it to see if it contains any traps.
It's ok, to import traps from other devices into the product. But it good to be a bit selective. Review the mib file to see what kind of traps they have defined and if they are the kind that you are interested in monitoring. Certainly hardware failures are important :-)
DELL-Abhijit P
Community Manager
•
711 Posts
2122
0
Posted September 7th, 2012 08:00
Hi,
Thanks for your post. From the message it looks like the MIB file you tried importing did not contain definitions for SNMP traps. If you can provide the specific file name, we can check to see if there is any trap information available in that MIB. MIB files contain information about various attributes and may or may not contain trap definitions.
Regards
Abhijit