Is there no way to import a manufacturer's MIB file?

[sgrant]

I can't find anywhere on the Forums or the wiki that show how to do this.
I don't think it's very time efficient for me to crawl through all of the Unclassified devices and manually add the OIDs for each of them. We do not want to extend Service-Now either, the categories that exist are working perfectly for us at the moment.

Please help.
thanks
Sandy G

[aleck_lin]

Subash,

What you need is dependent on what information you're pulling back. From the link you sent, it looks like you should be able to pull some pretty basic information about Windows. For classifying windows with SNMP, we have some basic Windows SNMP classifiers matching against the sysdescr OID. You'll probably need to add more for additional versions (like 7, 2008, 2012 and etc). Then you'll need to write you own custom probes and sensors to parse out the data from SNMP. All of this is do-able, but you'll need to know Discovery and Javascript well to navigate your way through.

Now that I've told you how to do it. My piece of advice is to ask you NOT to do Discovery with Windows using SNMP. The information you'll get back is limited, unless all your looking for is very, very simple and rudimentary data. I don't know your situation, but I'd fight for those windows credentials before you go off and implement things on your own.

[subash_biswas]

Thanks Aleck, will do.

[sgrant]

um, if we 'incorrectly' named the record before we found out this wonderful knowledge, will the record be 'broken' somehow? will correcting the name fix that?

i.e.
1 - HP Magic Printers MIB file - (record name) has the HP-BASE_MIB.mib file attached to it
2 - Admin "discovers" 😛 😛 this note, and realizes mistake
3 - Admin corrects the name of the record to match the filename "HP BASE MIB" is now the record name
4 - ??????? is it fixed now??? if not, what is the correct way to do this???

thanks

[sgrant]

We are running July release 3, and I need to get this to work in our environment.
I need to have a 'known good' process for importing MIB files into Discovery correctly. I'm pretty sure what I have currently isn't working (based on the fact that any Discovery using SNMP hangs). YES, I have watched the video, but we are not extending any tables at this point, and everything we are adding already has an appropriate Class.

I have been struggling with this for a couple of weeks now, off and on and I find I'm missing answers to the following:
- What is the correct file extension for MIB files that get imported?
- What is the correct naming convention required on the Instance-side, so it will be recognized?
- When removing an incorrect MIB, what's the correct procedure? (I have tried: remove-save-close-loadnew-save-close(Restart Service on MID) / remove-save-loadnew-save&update(Restart Service on MID) - neither have been very successful
- Do I even need the entire MIB file for a few devices? or would it be more efficient to just add individual OID's?
- Any tips on finding OID's for devices that are fairly old? We have some devices that are only reporting the Manufacturer portion of the OID, there's nothing in the xml that contains the entire string...

any help would be much appreciated, this is killing me 😞
S

[aleck_lin]

Sandy,

The file extension should be .mib although to be honest, I've never tried anything else.

There's really no name convention on the instance side as long as you attach the corresponding MIB.

To remove a MIB file, you should be able to just remove the attachment. When you say it hasn't been successful, is the MID server not downloading it?

I'm not a MIB expert, but I believe you need as many MIB files as you need to make it compile correctly. You could theoretically just add numerical OIDs, but it was broken before Berlin, so you'll need a post Berlin version of the instance to be able query for numerical OIDs.

Finding the right MIBs can be challenging. I wish I had better suggestions.

Thanks!