cancel
Showing results for 
Search instead for 
Did you mean: 
Create Post
Level 13

PSA: Check your MIBs.cfg file if you've upgraded to NPM 12.0.1 (and maybe 12.0.0 too)

IMPORTANT UPDATE: Since this got a couple of hundred views and several comments, I wanted to let you know of something else I have found.  We were having several weird issues with the web console MIB Browser and the UnDP app on our Orion server.  I checked the newest MIBs.cfg file in my Customer Portal and noticed that it is only 1.4GB in size after unzipping it.  I can only guess that the 1.8GB one that was released in late October or early November that I reference in my original post above was some kind of mistake, as it was quite odd for it to go from 1.3GB in size to 1.8GB in size in such a short time.  The current 1.4GB size seems more reasonable as usually only a couple dozen Megabytes are added to the file on average each week.

I highly recommend replacing your MIBs.cfg file, whether you still have the original 1.3GB size one from when you updated to NPM 12.0.1, or the 1.8GB oversized one I recommended you update to in early November, ASAP.

We have 3 Orion environments, 2 of which are in our Production environment and running on Win 2008 R2 servers and 1 is a Dev box for testing and general tomfoolery that is running on a Win 2012 box. All three had a Mibs.cfg file size of 1.3 GB.  In case you don't know, this file is the SNMP OID Database SolarWinds uses for the Universal Device Poller application and the Manage Pollers page for polling CPU, Memory, Node Details, and custom SNMP polling.  So when you are using their MIB Browser feature you are actually browsing this file.

Per the documentation it says that the latest MIBs.cfg file at the time of release should contained in each product upgrade.  So typically just upgrading Orion should automatically update the Orion MIB database.  Since NPM 12.0.1 was packaged and released on September 28, 2016, our MIBs.cfg file should have been current up to that time.  Now, I'm not sure how much has been added to the Orion MIB database between Sep 28th and now, but the newest version of the MIBs.cfg file is nearly 1.9 GB in size once unzipped...  That's almost a 50% increase in size (probably closer to 40%, but still) in just over a month's time...  My guess is they didn't package up the newest MIBs.cfg file in the NPM 12 release.  I would almost guess that they may have even put a substantially older MIBs.cfg file in there because an extra 600 MB worth of MIBs is a lot.  That file has been around for years and years, so even if it gained 600 MB in 6 months I would be surprised.

In case you don't know this as well, SolarWinds updates the MIBs.cfg database file every two weeks based on customer support tickets, so instead of waiting for a product upgrade you can keep your MIB database up to date yourself.  Usually this isn't necessary unless you have a node you're trying to apply custom SNMP monitoring to and Orion doesn't know about the OID's you are trying to poll.  The file can be downloaded from your Customer Portal under "Helpful Links".  You then simply unzip the downloaded file and replace the old file, located at "C:\ProgramData\Solarwinds\MIBs.cfg", with the new one.  I recommend renaming the old one first to make a backup of it (I simply change its name to "MIBs.cfg.OLD_todaysDateHere") just in case.  Then you restart all Orion Services and you should be good to go.  If you have more than one polling engine then you will need to do this on your Primary Polling Engine and all Additional Polling Engines (I'm not sure about your Additional Web Server if you have one of those, but my guess is if that file is found in that spot then you should probably replace it).

CONCLUSION: The moral of this post is that you should check your MIBs.cfg file and see if it is anywhere close to the size of the new one (1,896 MB to be exact).  I also recommend going into the MIB browser on your web console or into the UnDP application on your server and browsing the MIB library there to see if it works.  I was getting an error in UnDP and just a blank page in the web's MIB Browser until I replaced the file and restarted the services.  And yes, I did try restarting the services first before replacing the file and that didn't help.  Only once I replaced the file and restarted the services did it help.

Also, please reply if you too notice this.  I'd be curious to know how prevalent this issue is or isn't.

12 Replies
Level 7

I am having problems using the MIB Browser in NPM, I don't get any results no matter what I put in the search box.  UnDP seems to be acting funky also.  We went from 11.5.3 to 12.1 recently and our MIB.cfg file is dated 2/7/2017 and is 1.28 GB (1,378,893,824 bytes).  I grabbed the new MIB file and am about to follow the instructions in the readme doc that was contained in the MIBs.zip file which match up with what you explained.  I am glad that i am not the only one having this issue.  I appreciate everyone's posts!  I will respond back if it doesn't work.

0 Kudos
Level 13

IMPORTANT UPDATE: Since this got a couple of hundred views and several comments, I wanted to let you know of something else I have found.  We were having several weird issues with the web console MIB Browser and the UnDP app on our Orion server.  I checked the newest MIBs.cfg file in my Customer Portal and noticed that it is only 1.4GB in size after unzipping it.  I can only guess that the 1.8GB one that was released in late October or early November that I reference in my original post above was some kind of mistake, as it was quite odd for it to go from 1.3GB in size to 1.8GB in size in such a short time.  The current 1.4GB size seems more reasonable as usually only a couple dozen Megabytes are added to the file on average each week. 

I highly recommend replacing your MIBs.cfg file, whether you still have the original 1.3GB size one from when you updated to NPM 12.0.1, or the 1.8GB oversized one I recommended you update to in early November, ASAP. 

I actually have two PowerShell scripts I use to replace these that I'm working on cleaning up to be shared.  One script stops (or starts) all of the SolarWinds services on all of your polling engines and the second script backs up and replaces all of your MIBs.cfg files on each polling engine.If I get some time after the first of the year I'll try and get an updated version posted of that.  I'd like to combine them both into one script as well as speed up the script that stops the services.  It takes forever right now.  It's still better than having to stop the services on each individual polling engine...  Even with the new web console service manager.  How did SolarWinds not put a "Stop All Services on all Polling Engines" button?  How???

Level 12

Is there an official list of each place to find the MIBS.cfg file on a Windows server? Perhaps by application name?

I have found more than one copy of the file, and now keep them all up to date.

On the other side of the coin, is it really necessary to have multiple copies of the file to satisfy the needs of different apps?

Merci d'avance,

Joe

0 Kudos

The only one you need to worry about is "C:\ProgramData\SolarWinds\Mibs.cfg".  The rest don't matter.

Level 13

Same issue here...

We use UNDP quite a bit so the sizing might be different regardless. We are on NPM 12 and its saying last update April

pastedImage_0.png

However we are hot fixing NTA as well as other modules at the weekend so this was useful. I will couple in adding the latest MIBs in as well.

Thanks for the spot

0 Kudos
Level 8

I've tried to get into the habit of updating MIB's whenever we do any planned maintenance/upgrades, although in our case we've probably not got much to worry about if it gets forgotten for a while. Having just upgraded to NPM 12.0.1, deliberately planning to update MIB's in that process as well, I do seem to remember being surprised at the comparative file size you note. I was too busy correcting a little problem I'd introduced to think about it anymore though ...

0 Kudos
Level 8

Thanks for pointing this out!

I've been running v11.5.3 since March and haven't checked the MIBs.cfg since then.

Upgraded to v2016.2.100 a couple of weekends ago using the full download from the customer portal.

Checking the date/time/size of the MIBs.cfg which is in current use: 15/09/2016 / 15:46 / 1.25 GB (1,347,895,296 bytes)

Downloaded the latest MIBs.cfg: 1.80 GB (1,941,577,728 bytes)

Were any of you guys (paulrobbins, mbird, and mark.johnson@morningstar.com)having problem browsing the MIB library in either UnDP or in the Manage Pollers MIB Browser on the web console prior to installing the new Mibs.cfg file manually?

0 Kudos

No problems browsing the MIB library

0 Kudos

Can't say I've used either function for a while, ought to have done - but it's probably pre-NPM12 the last time I did - which isn't that long ago but doesn't help with the question ...

0 Kudos

No issues here.

0 Kudos

Same here, exact same size.

0 Kudos