Most mibs depend upon other mibs which define calls made, and so must be loaded before the desired mib will work.
This is contained in the mib IMPORTS section of the mib.
For example:
IMPORTS
MODULE-IDENTITY,
OBJECT-IDENTITY,
enterprises
FROM SNMPv2-SMI;
In this case the mib requires SNMPv2-SMI.
In this example vnxe_alert.mib depends upon SNMPv3-SMI and SNMPv3-TC, so when the probe used vnxe_alert.mib it checks for SNMPv3-SMI and SNMPv3-TC, and if not found then it can't use vnxe_alert.mib.
log sample:
May 6 09:52:23:739 [8128] snmptd: MIB search path: C:\Program Files (x86)\Nimsoft\MIBS
Cannot find module (SNMPv3-SMI): At line 6 in C:\Program Files (x86)\Nimsoft\MIBS/_vnxe_alert.mib.new
May 6 09:52:23:740 [8128] snmptd: Cannot find module (SNMPv3-TC): At line 9 in C:\Program Files (x86)\Nimsoft\MIBS/_vnxe_alert.mib.new
Did not find 'enterprises' in module #-1 (C:\Program Files (x86)\Nimsoft\MIBS/_vnxe_alert.mib.new)
May 6 09:52:23:740 [8128] snmptd: Did not find 'DisplayString' in module #-1 (C:\Program Files (x86)\Nimsoft\MIBS/_vnxe_alert.mib.new)
Did not find 'TimeStamp' in module #-1 (C:\Program Files (x86)\Nimsoft\MIBS/_vnxe_alert.mib.new)
May 6 09:52:23:740 [8128] snmptd: Unlinked OID in Vnxe-MIB: emc ::= { enterprises 1139 }
Undefined identifier: enterprises near line 33 of C:\Program Files (x86)\Nimsoft\MIBS/_vnxe_alert.mib.new
FROM vnxe_alert.mib
IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, OBJECT-IDENTITY,
enterprises
FROM SNMPv3-SMI
DisplayString, TimeStamp
FROM SNMPv3-TC;