Submit a ticketCall us

Solarwinds & Cisco Live! Barcelona
Join us from the 29th of January to the 2nd of February at Cisco Live 2018 in Barcelona, where we will continue to show how monitoring the network with SolarWinds will keep you ahead of the game. At our booth (WEP 1A), we will demonstrate how SolarWinds network solutions can help. As a bonus, we are also hosting a pre-event webinar - Blame the Network, Hybrid IT Edition with our SolarWinds Head Geek™, Patrick Hubbard on January 24th - GMT (UTC+0): 10:00 a.m. to 11:00 a.m. There's still time to RSVP.

Home > Success Center > Archive > 2017December18 - Deletes > Trap message dispays hex encoded string

Trap message dispays hex encoded string

Table of contents
Created by Gary O'Donovan, last modified by Kevin.Swinson on Dec 18, 2017

Views: 766 Votes: 0 Revisions: 8


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