Submit a ticketCall us

Get a crash course on Network Monitoring delivered right to your inbox
This free 7-day email course provides a primer to the philosophy, theory, and fundamental concepts involved in IT monitoring. Lessons will explain not only how to perform various monitoring tasks, but why and when you should use them. Sign up now.

Home > Success Center > Network Performance Monitor (NPM) > Nodes are not polling CPU or memory information after upgrading from NPM 10.x to 11.x

Nodes are not polling CPU or memory information after upgrading from NPM 10.x to 11.x

Updated July 21, 2017

Overview

Nodes are not polling CPU or memory information after upgrading from NPM 10.x to 11.x. Newly added nodes have no polling issues.

Environment

NPM upgraded from version 10.x to 11.x

Cause

This issue is caused by a failure in the Lazy Upgrade procedure when converting the Pollers table. 

Resolution

Confirm the issue:

  1. Find the NodeID via the Nodes table [dbo].[Nodes]:
    1. On the main Orion server, open Database Manager.
    2. Add a default server.
    3. Right-click the Orion database.
    4. Click New query and enter the following:
      SELECT TOP 1000 * FROM [dbo].[Nodes]
    5. Click Execute query.
  2. Use the following query to verify if N.CPU.X PollerTypes does not exist: 
    select * from pollers where Nodeid=<NodeID>
    For example:
    select * from pollers where Nodeid = 1

  3. Click Execute query.

  4. Run List Resources on the node:

    1. On the Web Console, go to Settings > Manage Nodes.

    2. Select the box next to the correct node.

    3. Click List Resources at the top.

    4. Select the example CPU and memory resources, and click Submit. 

  5. Go to the Pollers table to verify that the correct PollerTypes now exist. For example, N.CPU.X (see Step 2).

 

To resolve the issue for all nodes, run the following SQL script:

https://solarwinds-prod.mindtouch.us/@api/deki/files/2916/cpu%2Bpoller%2Breplacement.sql

Last modified
17:07, 23 Jul 2017

Tags

Classifications

Public