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 message dispays hex encoded string

Trap message dispays hex encoded string

Table of contents
Created by Gary O'Donovan, last modified by MindTouch on Jun 23, 2016

Views: 24 Votes: 0 Revisions: 7


This article details the reason for trap messages being displayed in hex.


All NPM versions


Normally string variables (octet string) included with a trap message are displayed/rendered as ASCII characters when processed by the Traverse Message Handler.  However, if a string contains any non-printable characters, then the string is displayed as hex encoded bytes.

Last modified
23:47, 22 Jun 2016