Submit a ticketCall us

Announcing NPM 12.2
With NPM 12.2 you can monitor your Cisco ASA firewalls, to monitor VPN tunnels for basic visibility and troubleshooting tunnels. NPM 12.2 also uses the SolarWinds Orion Installer so you can easily install and upgrade one or more Orion Platform products simultaneously.
See new features and improvements.

Home > Success Center > Network Performance Monitor (NPM) > Polling is stopped after upgrade to NPM 10.5

Polling is stopped after upgrade to NPM 10.5

Overview

Polling stops on some primary polling engines that have been upgraded to SolarWinds NPM version 10.5.

Environment

NPM 10.5

Cause

This occurs when either or both of the following obsolete files, listed in their default locations, are not removed upon upgrade:

  • C:\Program Files (x86)\Common Files\SolarWinds\Collector\Plugins\NPM.Interface.Snmp.Plugin
  • C:\Program Files (x86)\Common Files\SolarWinds\Collector\Plugins\NPM.Node.Remap.Snmp.Plugin

The presence of this issue may be indicated by nodes reporting a Next Poll time that is actually in the past. To confirm that these files are causing the polling stoppage issue on your polling engine, review both the Data Processor Log and the Polling Controller Log generated by the SolarWinds diagnostics utility, as indicated in the following procedure:

  1. On the polling engine that is experiencing the polling stoppage, click Start > All Programs > SolarWinds Orion > Documentation and Support Orion Diagnostics.
  2. Click Start.
  3. Provide a location to save the SolarWindsDiagnostics.zip archive.
  4. Extract the SolarWindsDiagnostics.zip archive, and then open both the Data Processor Log and the Polling Controller Log.
    Note: the default location for both logs is SolarwindsDiagnostics\Collector\Logs\
  5. If the files listed above are causing your polling stoppage, you should see errors in both logs similar to the following:
    2013-05-31 11:28:26,403 [Scheduler] ERROR SolarWinds.Collector.CollectorAppBase - Plugin NPM.Interface.Snmp failed to initialize.

Resolution

  1. Verify that SolarWinds Network Performance Monitor version 10.5 is installed on the server that is supposed to be polling.
    Note: This issue has only occurred on primary polling engines.
  2. Locate the following files, listed in their default locations on an x64 Windows machine:
    • C:\Program Files (x86)\Common Files\SolarWinds\Collector\Plugins\NPM.Interface.Snmp.Plugin
    • C:\Program Files (x86)\Common Files\SolarWinds\Collector\Plugins\NPM.Node.Remap.Snmp.Plugin
  3. Move the files listed above to the server desktop, so NPM can no longer access them.
  4. Click Start All Programs SolarWinds Orion Advanced Features Orion Service Manager.
  5. Click Shutdown Everything, and then wait for all services to stop.
  6. Click Start Everything, and then wait for all services to restart.
  7. In the Orion Web Console, view Node Details for any node for which polling had previously stopped.
    Note: The files above should be removed from the polling engine to which is assigned the node for which polling has stopped.
  8. Click Poll Now, and then wait to confirm that the Next Poll time is updated to a future time.
  9. If polling has been restored, delete the files that were moved to the server desktop.

This article applies to SolarWinds Network Performance Monitor version 10.5

Last modified
23:22, 22 Jun 2016

Tags

Classifications

Public