- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-13-2014 03:34 AM
Hi,
I'm trying to pull back additional Discovery data from some CI types via SNMP and it appears that the relevant MIB files are not included out of the box - one example is for a Nokia IPSO IP2450. So I found a MIB file on the OID View website ("NOKIA-IPSO-SYSTEM-MIB.mib"), downloaded it and added it to the SNMP MIBs list, ensuring that the Name matched the attached filename exactly. I also restarted the MID Server to try and make sure it took the new file, although from the logs it looks like it had taken the MIB file anyway.
However, this doesn't seem to have worked... I've created a test probe just so I can view the XML returned when I try to walk to certain SNMP Fields, such as "ipsoChassisSerialNumber". When I create an SNMP Field record using the OID for this field, "1.3.6.1.4.1.94.1.21.1.1.1", the probe returns the correct serial number but all the tag names below "enterprises" are unknown (see screenshot below), suggesting that the MIB file is not being referenced. When I create an SNMP Field record in MIB name format, "iso.org.dod.internet.private.enterprises.nokia.nokiaProducts.ipsoProducts.ipsoSystem.ipsoChassisGroup.ipsoChassisSerialNumber", this returns nothing at all.
If I understand correctly, I will need to be able to reference the MIB tag names in my sensor (when I create one) in order to make use of the data returned so this isn't much good to me at present.
So could anyone suggest what I might be doing wrong? I am very new to Discovery and I'm not really from a networks background, so I'm at a distinct disadvantage here and would be very grateful for any advice!
Thanks,
Mark
Solved! Go to Solution.
- Labels:
-
Discovery
-
Service Mapping

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-02-2014 02:24 AM
Try removing the .mib suffix on your MIB files. MIB's do not need a suffix so 'NOKIA-IPSO-SYSTEM-MIB.mib' should be 'NOKIA-IPSO-SYSTEM-MIB'.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-02-2014 02:24 AM
Try removing the .mib suffix on your MIB files. MIB's do not need a suffix so 'NOKIA-IPSO-SYSTEM-MIB.mib' should be 'NOKIA-IPSO-SYSTEM-MIB'.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-12-2015 02:25 PM
Did you have any luck with this mark? I am having the exact same issue trying to get serial numbers from our DELL PowerEdge switches.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-15-2015 01:11 PM
Interesting.. have you tried running snmpbulkwalk with that OID? What tags do you see? Try this and post your results.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-19-2015 06:38 AM
Agreed with Daryll's suggestion - as of Dublin our MIB compiler was updated. When uploading MIB's they need to have the extension removed. Restart mid server and all should be well again.
Going a bit deeper - the reason why you see those "unk" values is due to the snmp responding to the OID value (numeric) rather than the text. The mib file is what translates this "1.3.6.1.4.1.94.1.21.1.1.1" into this "iso.org.dod.internet.private.enterprises.nokia.nokiaProducts.ipsoProducts.ipsoSystem.ipsoChassisGroup.ipsoChassisSerialNumber"
once the mib is uploaded properly you'll see the payload change to what you are expecting to see.
Let me know if this helps...and good luck!