Hi Leslie,

no box has an ATM-Adapter but on the falling box the muxatmd daemon is
started. Don't ask me why. And now I could solve the problem by adding the
following ling to the file /etc/snmpd.conf

smux 1.3.6.1.4.1.2.3.1.2.3.1.1 muxatmd_password # muxatmd

Now it works fine. Thank you for the help.

Best regards
Gerd

-----Ursprüngliche Nachricht-----
Von: Leslie Clark [mailto:lclark AT US.IBM DOT COM]
Gesendet am: Donnerstag, 14. Januar 1999 12:40
An: NV-L AT UCSBVM.UCSB DOT EDU
Betreff: AW: AuthenticationFailure

Does one box have an ATM interface and the other one not? This has come
up before. Seems like it was caused by the atm daemon running on a box that
did not have an atm interface.

Cordially,

Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking
===========================================================================
Hi James,

I did what you advised an turned on the logging level in snmpd.conf to 3 on
the node where snmpd works wrong and on the node where snmpd works correct.
In the trace-output I can see on the defective node a line

simple {version 0, identify risc6000public.1.1, description "SNUX ATM
daemon",
password "muxatmd_password" }

After this command is listed the error-message

simpleOpen rejected (badIdentity): risc6000public.1.1

The above command does not exist on the good node.
The files snmpd.conf and snmpd.peer are the same on bothe nodes.

Best regards
Gerd

-----Ursprüngliche Nachricht-----
Von: James Shanks [mailto:James_Shanks AT TIVOLI DOT COM]
Gesendet am: Mittwoch, 13. Januar 1999 15:48
An: NV-L AT UCSBVM.UCSB DOT EDU
Betreff: Re: AuthenticationFailure

I am not certain that you have one problem.  There may be several.
I would turn on the logging level in snmpd to 3 so you can get a trace of
all activity.

Trapgend is a SMUX peer, which requires entries in the snmpd.peers file to
match those in snmpd.conf, otherwise the open will be rejected with the
sort of message you see here.  But I don't know how you could get a logon
from trapgend with a community name of "risc6000public.1.1" since it is
hard coded internally as "nv6000", so this looks like a failure from some
other process/daemon trying to open a connection to snmpd.

James Shanks
Tivoli (NetView for UNIX) L3 Support



"Brunschede, Gerd" <Gerd.Brunschede AT HIK.FZK DOT DE> on 01/13/99 09:29:46 AM

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)
Subject:  AuthenticationFailure





Hi,

I have a strange problem and need some help.

We have four SP-Nodes with exactely the same /etc/snmpd.conf-file.
The same Community-Names are defined on the Nodes and the server.
On the Nodes I have started the trapgend und the snmpd.
Only on one node I get the Event-message

Incorrect Community Name (authenticationFailure Trap) public

If I look to the file /usr/tmp/snmpd.log I see the following message

EXEPTIONS: simpleOpen rejected (badIdentity): risc6000public.1.1 (SMUX
127.0.0.1.2230+6)

Where does this come from and how can I solve this problem?

Thanks in Advance

Gerd Brunschede
Forschungszentrum Karlsruhe GmbH
HIK
Hermann-von-Helmholtz-Platz 1
76344 Eggenstein-Leopoldshafen
Tel.: +49 7247 82-5637
Fax:  +49 7247 82-4972
e-mail: gerd.brunschede AT hik.fzk DOT de