It isn't you. The reason it's failing to import is an unsatisfied dependency.
Looking at the MIB text, the IMPORTS section lists the objects imported and
what MIB defines the objects. If those MIBs haven't previously been imported or
shipped with InterMapper, it doesn't know the definitions for the imported
objects and throws an error.
IMPORTS
enterprises,Counter,IpAddress
FROM RFC1155-SMI
OBJECT-TYPE
FROM RFC-1212
DisplayString
FROM RFC1213-MIB
TRAP-TYPE
FROM RFC-1215
PositiveInteger,NonNegativeInteger
FROM UPS-MIB;
This isn't an InterMapper thing; it's an SNMP thing. As it happens, InterMapper
ships with all of the MIBs in the IMPORTS clause of the USHA-MIB with the
exception of the UPS-MIB.
Import that first and then import the USHA-MIB.
The UPS-MIB, among others, is available for download here.
http://download.intermapper.com/thirdparty/libsmi-0.4.8/mibs/dirlist.php
FYI:
If you want to check whether your MIB is already in InterMapper, check the
InterMapper Settings/MIB Files directory.
--
Mike Maki
InterMapper Technical Support
[email protected]
-------------------- m2f --------------------
Read this topic online here:
http://forums.intermapper.com/viewtopic.php?p=4355#4355
____________________________________________________________________
List archives:
http://www.mail-archive.com/intermapper-talk%40list.dartware.com/
To unsubscribe: send email to: [email protected]
