This blog post is a supplement to Denny’s “Orion MIB Database-What Is It Good For?” which answers the most puzzling questions and clarifies common misconceptions about the Orion MIB database. Re-reading Denny’s blog will help you best grasp this blog post.
In a nut-shell, Denny’s blog post discusses:
What is the Orion MIB database primary use?
How else is the MIB database used?
What is the most common misconception surrounding UnDP?
What do you do if you don’t know the OID you need?
How is the MIB database not utilized, though most people think it is?
And why do we have two databases?
Supplementing Denny’s blog post, here are answers to concrete “How-to” questions.
How to add device vendor identification for your “unknown” devices?
With the assumption that you have a clear understanding of the Orion MIB database, it becomes essential to know how to get a SysObjectID and, subsequently, the MIB database updated. A SysObjectID is the unique Object Identifier (OID) used to recognize a device’s vendor during the discovery process. Discovered devices that don’t have a SysObjectID listed in Orion’s built-in database are listed as Unknown in the Orion Summary Home page, as shown in the image below.
In order to add the SysObjectID to Orion’s built-in database, post the SysObjectID and the device information here. Every point release of Orion NPM will have the published SysObjectID added to the Orion’s built-in database.
How to add new MIB’s to the MIB database before creating custom UnDP pollers?
In order to add a new MIB to Orion’s built-in database, open a support case here. A weekly download of the Orion MIB Database file from the customer portal will include the updated MIB database. Those who are not SolarWinds customers without a valid SWID like prospects/evaluators and device manufacturers can forward the MIBs to firstname.lastname@example.org .The following image shows the Customer Portal where the Orion MIB Database is highlighted.
By clicking Orion MIB Database, the MIBs.zip file will be available for a download. After downloading the MIBs.zip to the Orion server, it has to be uploaded to the MIB database. Before uploading, extract the MIBs.cfg file and the Readme.txt file. The Readme.txt file has step by step instructions on how to upload the MIBs.cfg file to the Orion MIB Database. The information in the Readme.txt file will be similar to the instructions pasted below.
After completing the procedure, you should have an updated Orion MIB Database on the server. You can verify this by selecting the Browse MIB tree option in the Orion Universal Device Poller New Universal Device Poller dialog. Then, scroll down to the newly added MIB. The following sequence of images gives direction to look for the newly added MIB.
How to create custom UnDP pollers?
The Orion Administrator Guide explains the process to create a custom UnDP poller in Chapter12.This video tutorial link is also very informative and explains custom UnDP pollers in detail.
How to find MIBs if you don’t or can’t find them in order to create custom UnDP pollers?
The SNMPWALK result will help you find out the MIBs if you don’t or can’t find them. This SNMPWALK application from SolarWinds is very easy to install and use. The following image shows the application.
It is strongly recommended to run this SNMPWALK application from the Orion installed server, so that the results of the snmpwalk do not get timed out or interrupted while scanning. This way, the MIBs configured on the device are being captured ensuring none is missed out. After SNMPWALK completes scanning, it automatically directs the results to be written on a notepad which can be saved, and viewed later. The following image shows the SNMPWALK results with the MIBs on the left and their corresponding values on the right.
From the above results, you can easily trace out the required MIB by looking for its corresponding values.
SolarWinds solutions are rooted in our deep connection to our user base in the THWACK® online community.
More than 150,000 members are here to solve problems, share technology and best practices, and directly
contribute to our product development process.