Submit a ticketCall us

Get a crash course on Network Monitoring delivered right to your inbox
This free 7-day email course provides a primer to the philosophy, theory, and fundamental concepts involved in IT monitoring. Lessons will explain not only how to perform various monitoring tasks, but why and when you should use them. Sign up 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: 17 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