AW: AuthenticationFailure

1999-01-13 10:22:02
Subject: AW: AuthenticationFailure
From: "Brunschede, Gerd" <Gerd.Brunschede AT HIK.FZK DOT DE>
To: nv-l AT lists.tivoli DOT com
Date: Wed, 13 Jan 1999 16:22:02 +0100
Hi Ken,

thanks for your answer. 
The Community Name for the loopback is set to public, so that
should not be the problem.
About HACMP: we have no HACMP, we only one NetView started.


-----Ursprüngliche Nachricht-----
Von: Ken Garst. [mailto:KGarst AT GIANTOFMARYLAND DOT COM]
Gesendet am: Mittwoch, 13. Januar 1999 15:38
Betreff: Re: AuthenticationFailure

I am having the same problem in a 2-node HACMP cascading environment with
one host runninng Netview 5.1 and both running AIX 4.2.1.

When I failover to the alternate node, the Netview control desk is flooded
with authen failures with the trap generated by the same host that Netview
is running on.  After about 20 minutes the flood of authen failures goes
away and Netview runs correctly.

I had this problem once before and corrected it my setting a community name
for loopback under the ip under the Netview Options->SNMP
Configuration.  However, I have tried this for my cluster hosts and it
doesn't solve the problem.

It was suggested that I run the xnmsnmpconf -clearCache before starting the
Netview daemons,  I added this command to the Netview startup script under
HACMP and the flood of authen failures still occurs.

In any case, perhaps these two things may help you, particularly the one
about setting the community name in the Netview options->snmp config.


<Prev in Thread] Current Thread [Next in Thread>