You will have to ask AS/400 what the traps mean and why they are sent the
way that they are.  This is their agent's doing and not NetView's.

The reason that the variable bindings are displayed in hex, even though
they say "octetstring" is because the data sent contains unprintable ascii
characters.  Thus NetView does not know what part of the variable binding
is significant, so he displays it all in hex.  Since "octetstring" is
defined as printable ascii only, the AS/4000 folks are not sending what
they should.  This is their error to fix.   Many other vendors have the
same problem.  It is usually caused by a sloppy programming technique which
pads the variable with binary zeros.  For ascii strings, this should be
blanks or x'20'.

James Shanks
Tivoli (NetView for UNIX) L3 Support



Eric Ortheau <eric.ortheau AT WAT.SAT DOT FR> on 10/15/98 04:23:26 AM

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

To:   NV-L AT UCSBVM.UCSB DOT EDU
cc:    (bcc: James Shanks)
Subject:  AS400 Traps Format





Hi,

One of my customers (NV 5.0, AIX 4.2.1) started SNMP on his AS400s and
is now receiving traps that are badly formatted :

n0332
Wed Sep 30 12:49:13 1998 n0332 u Trap: generic 6 specific 0 args (2):

[1] enterprises.ibm.ibmArchitecture.13.1.1.3.101.1 (OctetString): 0x01
61 12 12 01 5d 00 00 0b ...

[2] enterprises.ibm.ibmArchitecture.13.1.1.3.101.2 (OctetString): 0xd5
f0 f3 f3 f2 40 40 40 20 ...

Regarding that, I have three questions :

* Does anybody know what is the meaning of the specific trap 0 for AS400
?

* Does anybody know why these traps come sometimes with one variable
bindings, and sometimes
with two variable bindings ?

* How can I have NetView translate the Octet String value of the
variable bindings ?


Thank's in advance.



Eric ORTHEAU
Network Architecture and Administration Consultant
SYNOPSE
eric.ortheau AT synopse DOT fr