Submit a ticketCall us

Webinar: Web Help Desk for HR, Facilities and Accounting Departments
This webinar will focus on use cases for HR, Facilities and Accounting.

Having a unified ticketing and asset management system for all the departments in your company can provide end-users with a seamless experience and make things easier for your IT team. Yet, with different business tasks and objectives, many departments don’t fully understand the capabilities of Web Help Desk and how the software can be customized for effective use in their departments.
Register Now.

Home > Success Center > Network Performance Monitor (NPM) > Trap alert variables are not translated during a test

Trap alert variables are not translated during a test

Created by Justin Wyllys, last modified by MindTouch on Jun 23, 2016

Views: 11 Votes: 0 Revisions: 5


When creating an alert to forward a trap for a given scenario, the test trap result shows variables instead of their values if you have restricted the alert to a different object than what you are testing. 


For example, your trigger condition is configured only to alert on an interface named "GigabitEthernet0/1" but you are testing the alert on an interface named "GigabitEthernet2/15". The resulting trap result would include variables instead of their translated values. 


  • NPM 11 and later
  • Web based alerting in which you are forwarding a trap as part of the Trigger Action.


The object you have defined in the trigger condition does not match the object you selected for the test.


Select the same object for the test which you selected for the trigger condition.

Last modified
23:47, 22 Jun 2016


This page has no custom tags.