Submit a ticketCall us

AnnouncementsChange Is Inevitable

Get valuable help when it comes to tracking and monitoring changes. SolarWinds® Server Configuration Monitor (SCM) is designed to help you: detect, track, and receive alerts when changes occur, correlate system performance against configuration changes, compare server and application configuration against custom baselines, and verify application and system changes.

Learn more.

Home > Success Center > Network Performance Monitor (NPM) > NPM - Knowledgebase Articles > UnDP for ifOperStatus OID is not polling

UnDP for ifOperStatus OID is not polling

Updated 24th Aug 2017    

Overview

Universal Device Poller (UnDP) for the ifOperStatus OID is not polling, or polls only partially.

  • Example A: Device has 24 interfaces, yet only 2 interfaces are being polled in UnDP.
  • Example B: Device has 24 interfaces, yet 0 interfaces are being polled in UnDP 

Environment

  • NPM

Cause 

The issue occurs only for the ifOperStatus OID.

The limitation is by design to ensure that users do not bypass license limitations using a UnDP. For example, with a SL250 license, you shouldn't be able to bypass the limit and monitor more interfaces via the UnDP.

Ifoperstatus is polled out-of-the-box for interfaces, so you do not need to poll from it from UnDP.

Resolution

Polling ifOperStatus requires that the interface is monitored in NPM.

To poll ifOperStatus using a UnDP:

  1. Add the node to NPM for monitoring.
  2. List resources for the node, and add interfaces.
  3. Re-test UnDP, the test should be successful now.
 
Learn more:

 

Last modified

Tags

This page has no custom tags.

Classifications

Public