snmp on localhost
raver
OS AIX 4.1.5 (I know, will be decommed soon)
HW Motorola Powerstack
Community Name Not the default
I am getting this message every couple of seconds in the syslog:
Dec 28 14:46:07 gouda snmpd[46558]: NOTICE: SMUX packet from
(localhost_ip+2847+532)
Dec 28 14:46:07 gouda snmpd[46558]: EXCEPTIONS: simpleOpen rejected
(badIdentity): risc6000public.1.1 (SMUX localhost_ip+2847+532)
Dec 28 14:46:12 gouda snmpd[46558]: NOTICE: SMUX relation started
with (localhost_ip+2848+533)
(I have replaced the real ip address with "localhost_ip" as it is
proprietary company information).
Just about any similar problems I've found in USENET don't have any
replies posted. I've tried several things including modifying
syslogd.conf to not log them to the syslog. I want to log *.debug
so I tried adding snmpd.debug to goto /dev/null but it didn't work.
Its a standard AIX snmpd install but with the community name changed
for security reasons and with dpid2 turned off because its not necessary.
I tried editing the snmpd.conf file and added smux lines and tried
changing the trap line and added community lines but honestly, I don't
know snmp very well. I went through the snmpd man page and that is
where I got some ideas for trying various lines in the snmpd.conf
to no avail.
I tried which are now commented out because none of them worked:
#smux 1.3.6.1.4.1.2.3.1.2.1.2 gated_password # gated
#smux 1.3.6.1.4.1.2.3.1.2.2 private #gated
#smux 1.3.6.1.4.1.2.3.1.2.2 private 0.0.0.0 0.0.0.0
Does ANYBODY have any idea what I can do to suppress these messages?
SNMP is running so that the system can be monitored by Operations from
a remote site so I don't want to turn it off. Any help is appreciated.
I hope this post doesn't go unanswered as well...... :)
Thx,
-raver
Laurent CROUX
RDBMS Version:: 8.1.5
Operating System and Version:: AIX 4
Error Number (if applicable)::
Product (i.e. Instance, Security Manager, etc.):: Oracle Agent
Product Version::
OEM Console Operating System and Version::
Errors in /var/tmp
Whenever we start the Agent the following errors start appearing in
snmpd.log in /var/tmp and eventually fill up the file system.
What within the Agent would cause this?
04/03/00 08:37:57 NOTICE: SMUX packet from (128.163.2.50+34304+69668880)
04/03/00 08:37:57 EXCEPTIONS: simpleOpen rejected (badIdentity): 0.0 (SMUX
128.1
63.2.50+34304+69668880)
04/03/00 08:37:57 NOTICE: SMUX relation started with
(128.163.2.50+34305+6966888
1)
04/03/00 08:37:57 NOTICE: SMUX packet from (128.163.2.50+34305+69668881)
04/03/00 08:37:57 EXCEPTIONS: simpleOpen rejected (badIdentity): 0.0 (SMUX
128.1
Subject: Re : Errors in /var/tmp
Hello,
You need to set up "snmpd.conf" correctly and turn off this logging. Do the
following:
1) Stop the snmpd daemon
2) From a Unix prompt, get the output of hostname <enter>.
3) Find out what is the ip address that is associated with this ip address.
4) Add the following line to "snmpd.conf" with the ip address. For example:
smux 0.0 "" 123.456.789.011
5) Restart the snmpd daemon and make sure any errors are gone. The exception
error should no longer appear in the "snmpd.log" (the other 2 lines are ok).
6) Now turn off logging so the file won't fill up:
7) Remark out all the logging lines in the "snmpd.conf" file.
8) Stop and restart the snmpd daemon.
In case you are using a 3rd party app that uses SNMP with this native snmpd,
turning off logging will only mean that the server will stop logging to the
snmpd.log file, but the 3rd party app will still report errors in case there
are any problems with SNMP communication.
The SMUX multiplexer needs to be aware of itself in order to succesfully
send the information about the SNMP queries and traps.
Without this information, the SNMP system processes will generate warnings,
since they are operating 'in the dark'.
"raver" <b...@pobox.com> wrote in message
news:cabbe869.02010...@posting.google.com...
raver
Thanks for the advice. Logging was already set to 'disabled' but I
went ahead and commented the logging lines out anyway. Then I added
the following line:
smux 0.0 "" ipaddress_of_localhost
...and started snmpd but that did not work. I am still getting the
NOTICE and EXCEPTIONS lines logged in the syslog every 5 seconds - 3
new lines every 5 seconds. Any other advice would be helpful. Thanks.
-raver
Laurent CROUX
"
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:lcl...@US.IBM.COM]
Gesendet am: Donnerstag, 14. Januar 1999 12:40
An: NV...@UCSBVM.UCSB.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_...@TIVOLI.COM]
Gesendet am: Mittwoch, 13. Januar 1999 15:48
An: NV...@UCSBVM.UCSB.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.Br...@HIK.FZK.DE> on 01/13/99 09:29:46 AM
Please respond to Discussion of IBM NetView and POLYCENTER Manager on
NetView <NV...@UCSBVM.UCSB.EDU>
To: NV...@UCSBVM.UCSB.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.br...@hik.fzk.de
"""
Laurent CROUX