Can't help with your specific question but no matter what enterprise, a generic
4 specific 0 is an "authentication failure" or basically a "bad community name"
trap.  It means that someone did an SNMP operation and did not supply the
correct community name for it.   It is my understanding that you are not
required to define the standard SNMP traps (generic 1 - 5) in a MIB because they
are not vendor specific, and by using the mib-2 OID I would guess that is what
the agent who sent them is implying.   Sorry but I don't know much about the
even the standard snmpd agent on NT.  Is there one running on those boxes?


James Shanks
Tivoli (NetView for UNIX) L3 Support



Graeme Nelson <GNELSON AT MACQUARIE.COM DOT AU> on 12/07/99 04:12:19 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/Tivoli Systems)
Subject:  Unknown trap 1.3.6.1.2.1.11 generic 4, specific 0




Hi Netviewers,
Does anyone know the MIB for this trap. Its being sent by NT servers running
Critrix Metaframe.
The OID 1.3.6.1.2.1.11 matches snmp from RFC-1213-MIB-II MIB and could relate to
snmpInBadCommunityNames (OID 1.3.6.1.2.1.11.4). There are no traps in that MIB.

There are 2 servers involved and the traps are being sent at different times.
The only suggestion for something that would poll these servers is EGP (External
Gateway Protocol).

Any other suggestions as to where we should look would be appreciated.

Graeme Nelson
Macquarie Bank Ltd
Sydney, Australia
gnelson AT macquarie.com DOT au