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 > VoIP & Network Quality Manager (VNQM) > VNQM - Knowledgebase Articles > IP SLA Operation Canned Alert with custom property

IP SLA Operation Canned Alert with custom property

Created by Daniel Phillipps, last modified by MindTouch on Jun 16, 2016

Views: 855 Votes: 1 Revisions: 4

Overview

This article describes the issue with the custom property that cannot be applied to an alert.

Environment

VNQM version 4.2.3

 

Cause 

This issue occurs when the custom property may not have been committed to database before being assigned to alert.

Resolution

  1. Edit the alert. 
  2. In the IP SLA Operation Alert, remove and re-add the filter for the custom property.
  3. Leave the default triggger actions alone for Node Status is not down or not unmanaged.
  4. Leave the default trigger action alone for Operation status is not equal to warning and critical.

Note: If you have an additional trigger condition for a custom property, remove it, and then add it again. Submit the changes and test if everything is working fine.

 

Last modified

Tags

Classifications

Public