Submit a ticketCall us

WebinarUpcoming Webinar: Should I Move My Database to the Cloud?

So you’ve been running an on-premises SQL Server® for a while now. Maybe you’ve moved it from bare metal to a VM, and have seen some positive benefits. But, do you want to see more? If you said “YES!”, then this session is for you, as James Serra will review the many benefits that can be gained by moving your on-prem SQL Server to an Azure® VM (IaaS). He’ll also talk about the many hybrid approaches, so you can gradually move to the cloud. If you are interested in cost savings, additional features, ease of use, quick scaling, improved reliability, and ending the days of upgrading hardware, this is the session for you.

Register now.

Home > Success Center > Network Performance Monitor (NPM) > 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: 770 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