Submit a ticketCall us

WebinarDatabase Roundtable – Expert Database Professionals Feel Your Pain

In this video broadcast, Head Geek™ Tom LaRock is joined by Karen Lopez, Tim Chapman, and David Klee. They’ve known each other for many years, so this discussion was like four friends getting together to talk data and databases. They discussed diagnostic data collection, common performance root causes, reactive tuning versus proactive, and more. Join us for an engaging discussion on these topics! Plus, Tom LaRock will be available to answer your questions live.

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: 927 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