I have also seen this kind of error occur when NetView tries to process an
incoming trap against a definition for a completely different trap.  It can
happen when you are receiving traps for an Enterprise that's not even
defined in trapd.conf.  I would check to make sure that you have that Cisco
enterprise 1.3.6.1.4.1.9.1.201 defined.  If not, then you will also have to
define the generic/specific trap.  If the enterprise is not defined, then
NetView just keeps going one level "up" the MIB tree until it finds a match.
It will eventually use the generic enterprise of 1.3.6.1.4.1 (which you
should find at the end of trapd.conf) to format a vendor trap.

Joel Gerber - I/T Networking Professional - USAA Information Technology Co.
- San Antonio, TX
* (210)456-4231         * mailto:Joel.Gerber AT USAA DOT com   "
http://www.usaa.com

        -----Original Message-----
        From:   James Shanks [SMTP:James_Shanks AT TIVOLI DOT COM]
        Sent:   Wednesday, November 10, 1999 12:47
        To:     NV-L AT UCSBVM.UCSB DOT EDU
        Subject:        Re: X FMT ERROR

        Sure.  You have a trap defined in trapd.conf under that enterprise
id which says
        to put $3 (the third variable) in the Event Log message (what you
see in
        trapd.log and on the events screen).  But this particular trap does
not have a
        third variable.  It has only one, according to the error message.
So you need
        to use xnmtrap and locate the trap definition and fix it the message
to display
        $1 or change the message to something entirely different (isn't 4 an
        authentication error?  I'll bet the variable is either a community
name or the
        address of who is doing the accessing).   Anyway, that should solve
the problem
        with the display.

        But you will have to investigate further to decide who or what is
causing the
        problem that you get the trap for.

        James Shanks
        Tivoli (NetView for UNIX) L3 Support



        Steven Williams <willi1_s AT ins DOT com> on 11/10/99 01:10:27 PM

        Please respond to steven_williams AT ins DOT com

        To:   NV-L AT UCSBVM.UCSB DOT EDU
        cc:    (bcc: James Shanks/Tivoli Systems)
        Subject:  X FMT ERROR




        We are experiencing a problem on the events display where continuous
"X FMT
        ERROR: accessing element #3, only 1 available" error messages are
being
        received.  It is a generic type 4 with an enterprise of cisco
        1.3.6.1.4.1.9.1.201 and a source unknown(X).  Any ideas on what may
be
        causing this?

          Platform is AIX 4.3.2
          Framework 3.6
          TME 10 5.1(1)

        Steve Williams
        Lucent