TR: [nv-l] A authenticationFailure trap (Cisco) received from ent erprise cisco

["D'Apice, Domenico" <D.D'Apice@SAQ.qc.ca>]

Hello Guys

 

any idea about my issue ?

 

thanks

Dominic

---

De : owner-nv-l@lists.us.ibm.com [mailto:owner-nv-l@lists.us.ibm.com] De la part de D'Apice, Domenico
Envoyé : Wednesday, July 20, 2005 10:21 AM
À : nv-l@lists.us.ibm.com
Objet : RE: [nv-l] A authenticationFailure trap (Cisco) received from ent erprise cisco

So, what should i do to correct the problem ?

 

ps : my communityNames.conf file is empty...

ps : those devices that generate error are there since a while....

 

thanks

Dominic

---

De : owner-nv-l@lists.us.ibm.com [mailto:owner-nv-l@lists.us.ibm.com] De la part de Evans, Bill
Envoyé : Wednesday, July 20, 2005 9:57 AM
À : 'nv-l@lists.us.ibm.com'
Objet : RE: [nv-l] A authenticationFailure trap (Cisco) received from ent erprise cisco

I've never been able to get the exact relationship straight but there is an interaction between new node discovery, the "daily" CONFIGURATION poll, the communityNames.conf file and Authentication traps.  It may also be involved with a restart of NetView. 

On discovery you will find NetView taking it's community names from the communityNames.conf file and trying them in turn after trying the default community string.  If the correct one is not the default you will get an authentication trap from the router solicited. (Unless authentication trap forwarding is set off on the Cisco device.) 

This may be happening on your restart.  It would happen if these were new devices in the seed file on the NETMON daemon startup.  I'm not sure about existing devices since they should have an existing defined community string. The documentation doesn't clearly state how that factors into the configuration polling sequence.

Bill Evans
Tivoli NetView Support for DOE
301-903-0057

-----Original Message-----
From: owner-nv-l@lists.us.ibm.com [mailto:owner-nv-l@lists.us.ibm.com] On Behalf Of D'Apice, Domenico
Sent: Wednesday, July 20, 2005 9:37 AM
To: nv-l@lists.us.ibm.com
Subject: RE: [nv-l] A authenticationFailure trap (Cisco) received from enterprise cisco

I've talked to someone of the telecom department and it seem to  have no error log or something about snmp authentification...

These error seem to have begin when we restart netview (Monday) ....

Is there a relation about restarting netview AND these error ???

Thanks
Dominic

-----Message d'origine-----
De : owner-nv-l@lists.us.ibm.com [mailto:owner-nv-l@lists.us.ibm.com] De la part de James Shanks
Envoyé : Wednesday, July 20, 2005 9:14 AM
À : nv-l@lists.us.ibm.com
Objet : Re: [nv-l] A authenticationFailure trap (Cisco) received from enterprise cisco

Isn't there a log on the router which will tell you why it sent the trap?

James Shanks
Level 3 Support  for Tivoli NetView for UNIX and Windows Tivoli Software / IBM Software Group

                                                                          
             "D'Apice,                                                    
             Domenico"                                                    
             <D.D'Apice@SAQ.qc                                          To
             .ca>                      <nv-l@lists.us.ibm.com>            
             Sent by:                                                   cc
             owner-nv-l@lists.                                            
             us.ibm.com                                            Subject
                                       [nv-l] A authenticationFailure trap
                                       (Cisco) received from enterprise   
             07/19/2005 03:48          cisco                              
             PM                                                           
                                                                          
                                                                          
             Please respond to                                            
                   nv-l                                                   
                                                                          
                                                                          

Hello All,

we reveive a netview event "trap authenticationFailure" from 3 of our routers. Nothing has been change from Netview.

Why now Netview (sxptiv0009), receive this event from only 3 of our routers ? (Netview try to get some info of these 3 routers and the acces seem to be denied...but when we doing "mib browser" info seem to be there...

Can it be a error in the router configuration even if we know that the community is set ok each both side (router / netview) ?

------------------------------------------------------
Tue Jul 19 15:20:31 2005 tcdm1s4502.saq. A authenticationFailure trap
(Cisco) received from enterprise cisco with 1 arguments:
authAddr=sxptiv0009

SPECIFIC   : 0 (hex: 0)
GENERIC    : 4
CATEGORY   : Status Events
ENTERPRISE : cisco  1.3.6.1.4.1.9.1.502
SOURCE     : Agent (A)
HOSTNAME   : tcdm1s4502.saq.qc.ca
SEVERITY   : Indeterminate
LOGGEDTIME : 07/19/05 15:20:31
----------------------------------------------------

Thanks to put some light
Dominic D'Apice
+ D.D'Apice@saq.qc.ca