Any Opengear console server with firmware V3.1 or later can be integrated with SolarWinds Orion NPM. Opengear provides Universal Device Pollers for use with NPM which can be used for monitoring serial port status, current user sessions, connected UPS and Remote Power Controller performance and environmental state. In Opengear console servers with firmware V3.11 or later the SNMP status and trap MIBs were extended to provide more and better structured SNMP status and traps from the console servers.
- To monitor your console server and its managed devices you will first need to import the Opengear Pollers into your NPM. For details refer Opengear SolarWinds Integration Guide How-To documents.
Can I access a remote managed device from the Solarwinds NPM?
To patch the Solarwinds Orion Web Console with a HTTPS Client Launcher:
- Copy the IntegrationIcons.ascx over the installed version. Typically:
- Copy the HTTPS picture file Opengear.png into the appropriate image directory:
- Force a browser cache reload or open a new web browser and you can now see the HTTPS icon displayed in the top left tool-bar when you navigate to a Device via the Web Console
Will NPM poll the console server MIB or report on SNMP traps?
The ideal solution for SNMP alarm monitoring is to configure your manager to poll regularly (5-15 minutes) as well as receiving instant notification of events (unreliable). This way you get instant notification while maintaining polling intervals that won't flood your network with management traffic (and high polling rates of thousands of devices can cause this).
So with Orion NPM we use these two ways to detect when an event happens (polling and SNMP traps). However these currently draw from two slightly different Opengear MIB tables. The status MIB tables which can be polled and has a running count of the rule which triggered the alarm, contains not quite the same info as the asynchronous trap which will be sent for the same event.
- So for example the information available via polling for the alarm sensor for an EMD is (for each EMD alarm rule configured on the console server - from OG-STATUS-MIB):
- The EMD rule index which cause the alarm (ogEmdStatusIndex)
- The EMD name / label for which the event occurred (ogEmdStatusName)
- The current temperature when the event occurred (ogEmdStatusTemp)
- The current humidity when the alarm occurred (ogEmdStatusHumidity)
- The number of times this rule has caused an alarm (ogEmdStatusAlertCount)
- While the information contained in the asynchronous trap notification sent from the consoles server to the Solarwinds SNMP Manager is (from OG-SENSOR-MIB):
- The EMD name / label for which the event occurred (ogsensStatusName)
- The type of the device which the alarm originated from, in this case 'emd' (ogsensStatusDevType)
- The type of alarm rule which triggered e.g. 'temp' (ogsensStatusType)
- The current numerical value of whatever condition that caused the alarm (ogsensStatusValue)
So you can see these are not particularly similar. Polling the OG-STATUS-MIB on Orion results in a graph that goes up when the alarm counters increment. And this poll does not contain the same info as the asynchronous trap which will be sent by the console server for the same event.
Can I get the list of everything that will be polled?
At the moment on Orion we provide pre-canned polling for:
Opengear Serial Ports
Opengear Active Users
Opengear Signal Alerts
Opengear Environment Alerts
Opengear UPS Alerts
When the UnDP file is imported via the Universal Device Poller you can select either the Poller groups which specifically interest you or at a finer level the individual Pollers. For example the Opengear Serial Port Universal Device Poller groups break down as follows:
For more details on the UnDP file and Poller groups refer to thwack_ community site andhttp://opengear.com/snmp/solarwinds/
For OID details refer to the OG-STATUS-MIB which can be found at http://opengear.com/snmp/
As mentioned earlier new SNMP status and trap MIBs were created in Opengear console server firmware versions 3.10.2 and above. However, to ensure this change doesn't upset any earlier SNMP usage you may already have in place, there's an option to Use Legacy Notifications. Setting this option means the console server will send the older SNMP traps that are compatible with those sent in older firmware before the new MIBS were added.
Refer https://opengear.zendesk.com/entries/32422199-New-status-and-trap-MIBS for more details.