Hey Craig,

Auth Failures are vendor specific.
Cisco, Microsoft & Xylan, for instance,  send them under their own OID.
For example, for cisco I coded the auth failure trap to also show the cause 
(authAddr):
(Most other vendors dont fill in this field).

Cisco_Auth_Failure {1.3.6.1.4.1.9} 4 0 A 2 0 "Status Events"
Cisco Incorrect Community Name (authenticationFailure Trap) authAddr: $1.

You could also populate the "Command for Automatic Actions" field to
write these to a separate file or send an email to a service account .....

Good Luck,
--Dermott

----- Original Message -----
From: "Treptow, Craig" <Treptow.Craig AT principal DOT com>
To: "NetView List (E-mail)" <nv-l AT lists.tivoli DOT com>
Sent: Thursday, April 04, 2002 1:42 PM
Subject: [nv-l] Configuring events to log to another log file?


> Netview 6.0.2 AIX 4.3
>
> I would like to take all the authentication error traps and log them to their 
> own file rather than trapd.log.
> It looks like either modifying the "AuthenticationFailures" event category, 
> or creating a new category could work.  Does anybody
know if this is possible, or where it is mentioned?  I'm having trouble find a 
good discussion of this in the manuals.
>
> Thanks.
>
>
> Craig
>
> A dozen, a gross, and a score,
> Plus three times the square root of four,
> Divided by seven,
> Plus five times eleven,
> Equals nine squared plus zero, no more.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: nv-l-unsubscribe AT lists.tivoli DOT com
> For additional commands, e-mail: nv-l-help AT lists.tivoli DOT com
>
> *NOTE*
> This is not an Offical Tivoli Support forum. If you need immediate
> assistance from Tivoli please call the IBM Tivoli Software Group
> help line at 1-800-TIVOLI8(848-6548)
>