See my reply to "SNMP and Cheyenne Products".   The traps contain
non-printable characters in the supposed ASCII octet string, so NetView
displays them all as hex because he does not know which ones are
significant".  Managewise has obviously decided to mask bad vendor
programming at the risk of burying possibly significant information.

James Shanks
Tivoli (NetView for UNIX) L3 Support



Leonard Bocock <leonard.bocock AT NZ.UNISYS DOT COM> on 03/10/99 11:49:49 PM

Please respond to Discussion of IBM NetView and POLYCENTER Manager on
      NetView <NV-L AT UCSBVM.UCSB DOT EDU>

To:   NV-L AT UCSBVM.UCSB DOT EDU
cc:    (bcc: James Shanks)
Subject:  NV5.1: Hex in snmp trap messages





Hi

We've just imported some arcserve inoculan mibs into NV, and used mib2trap
to
generate trap files - all this worked a treat but the snmp event variable
messages (variable 1 and variable 2 contents) are displayed in NetView in
hex,
not ASCII.  It makes it real slow reading the trap messages...........

The MIBS work ok on ManageWise ie. - the messages are in ASCII.  The var1
and
var2 are defined in the MIB as string-octect (from memory), but i assume
this
has no bearing on the problem or does it.

Anybody got any ideas???

Many thanks,
Leonard Bocock