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 alerts not triggering after an upgrade to NPM 10.7

UnDP alerts not triggering after an upgrade to NPM 10.7

Table of contents
Created by Interspire Import, last modified by MindTouch on Jun 23, 2016

Views: 773 Votes: 0 Revisions: 8

Issue:

Alerts from some UnDP pollers are not triggered after an upgrade from NPM v10.6 to NPM v10.7.

The pollers stopped working after the upgrade and deleting, recreating and reassigning the UnDP folder resolved the issue. The alerts are still not being triggered even with the polling restored.

The affected new alerts were setup to monitor temperature for Cisco devices.

Cause:

The custom poller ciscoEnvMonTemperatureStatusValue is not properly configured and does not have the specific label.

Resolution:

1. Open the UnDP application.

2. Right-click on the Poller Name and from the Context Menu, select Label.

3. Select the Label to be used for the Poller and click Finish.

    The labels will be polled in the next custom poll. Once these are polled, the alerts should start to trigger.

Applies to: NPM v10.7

Last modified

Tags

Classifications

Public