Skip navigation

Product Blog

2 Posts authored by: Nandish
Nandish

Device Support

Posted by Nandish Oct 20, 2011

This blog post is a supplement to denny.lecompte’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.

clip_image002

In order to add the SysObjectID to Orion’s built-in database, post the SysObjectID and the device information Tell us your "Unknown" devices!. 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 mibs@solarwinds.com .The following image shows the Customer Portal where the Orion MIB Database is highlighted.

clip_image004

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.

clip_image006

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.

clip_image008

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.

clip_image010

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.

clip_image012

From the above results, you can easily trace out the required MIB by looking for its corresponding values.

Orion provides numerous preconfigured alert actions, but in today’s on-the-move world, we want to get text alerts on our mobile phones.

Phone alerts and Pager alerts can be very efficient for getting the real-time updates and alerts, sent as SMS/text messages while you are on the go. Orion can easily trigger alerts using 3rd party phone alert applications such as the popular NotePager Pro and PageGate products.

You can download an evaluation version of NotePager Pro from this link. When you install NotePager Pro on the Orion server, it automatically gets added to the Dial Paging or SMS service option listed under Alert Actions in the Orion Advanced Alerts Tool.

Now, it is time to configure the settings in NotePager Pro. This video tutorial link is a great source for answering questions on setup and shows step-by-step directions on configuring NotePager with different protocols. NotePage also has a dedicated page for “SolarWinds Orion Network Performance Monitor Integration”

The following diagram shows how an alert is triggered from Orion to mobile phones or pagers via applications like NotePager Pro.

 

In the diagram above, when an Alert is triggered from Orion, it tries to establish a connection with NotePager application and forward the alert information to it. Next, NotePager goes on to establish a connection with the carrier via one of the following protocols listed below using a Modem or the Internet.

· SMTP

· SNPP

· TAP

· WCTP

The carrier looks up for the SMTP address or SNPP address or WCTP address and validates if it is in the supported list, then directs the actual message to the carrier’s core network before delivering it to phones or pagers as alerts.

Out-of-band SMS alerting is also supported by NotePager Pro, allowing the administrator to employ out-of-band alerting via a modem. Even when the ISP connection or mail server goes down, out-of-band alerts still work. SNPP, SMTP, and WCTP protocols work using two-way communication, sending alerts from Orion to a mobile device and vice versa. However, to get this working, you need to get a PollerID/SenderID(usually the email address) from the carrier, either directly or from their website. Only after entering the PollerID/SenderID will the end user be able to retrieve the alert on their mobile phone and also use the two-way feature.

Here is a list of example PollerID/SenderIDs which can be used while configuring the recipient.

NotePager Pro runs as a desktop Win32 application requiring the administrator to be logged into the console at all times to receive alerts. Another application from NotePage called PageGate can run as a Windows service and offers a more powerful tool for communication.

Click this link to download the evaluation version of PageGate. After installing it on the Orion Server, along with the PageGate Admin and PageGate client, you should see the PageGate action in the list of Alert Actions in the Orion Advanced Alerts tool.

After successful installation, go to Start->PageGate->PageGate Admin and select Help. The help provides details on configuring every aspect of the PageGate tool. This application provides much more than will be utilized by Orion Alerts. Once the recipients and the carrier is setup on PageGate Admin tool, this alert will automatically add an action to the list on the Orion Advanced Alerts Tool. It should look something like the screenshot below.

clip_image006

Filter Blog

By date: By tag: