This kb article describes how to verify the status when finding no added object is displayed on MIB browser, even though the mib file is already added to MIB repository via MIB setup wizard in UIM snmp probes like snmpget or snmptd probes.
The cause varies and can be a loading mib file failure as indicated in probe log.
The snmptd/snmpget probe will record results of loading mib files on snmptd.log/snmpget.log if loglevel is more than "3", therefore, user can check loading mib file has succeeded or not with the procedure below:
1. Open [Raw Configure] dialog on Admin Console
2. Set value of /setup/loglevel key to "3" or more, then apply the change
3. Deactivate the probe
4. Activate the probe, then the probe will start to load mib files
5. Check snmptd.log/snmpget.log
Below is an example which snmptd probe failed to load mib file. The cause is inappropriate mib file format (no object identifier is specified, "::= { enterprises xxxx }" is missing).
Jun 22 18:15:31:980 [2752] snmptd: SNMPInitialize - reading all available mibs
Jun 22 18:15:31:980 [2752] snmptd: Found NIM_ROOT = 'C:\Program Files\Nimsoft\Nimsoft Robot x64'
Jun 22 18:15:31:980 [2752] snmptd: MIBS directory is 'C:\Program Files\Nimsoft\Nimsoft Robot x64\MIBS'
Jun 22 18:15:31:980 [2752] snmptd: SNMPInitialize - calling init_snmp
Jun 22 18:15:31:996 [2752] snmptd: init_mib: Seen MIBDIRS: Looking in 'C:\Program Files\Nimsoft\Nimsoft Robot x64\MIBS' for mib dirs ...
Jun 22 18:15:32:089 [2752] snmptd: init_mib: Seen MIBS: Looking in 'all' for mib files ...
Jun 22 18:15:32:183 [2752] snmptd: Expected "::=" (FeatureSet): At line 37 in C:\Program Files\Nimsoft\Nimsoft Robot x64\MIBS/TEST-MIB.mib
Expected "{" (TEXTUAL-CONVENTION): At line 37 in C:\Program Files\Nimsoft\Nimsoft Robot x64\MIBS/TEST-MIB.mib
Jun 22 18:15:32:183 [2752] snmptd: Bad object identifier: At line 37 in C:\Program Files\Nimsoft\Nimsoft Robot x64\MIBS/TEST-MIB.mib
Bad parse of MODULE-IDENTITY: At line 37 in C:\Program Files\Nimsoft\Nimsoft Robot x64\MIBS/TEST-MIB.mib