OM / snmpd / smux conflict??
PLarsen at CIBER.com
Sat Jun 23 20:16:45 CDT 2007
>Larsen, Peter wrote:
>> [root at mgmtserv ~]# rpm -q net-snmp
>> [root at mgmtserv ~]# tail /etc/snmp/snmpd.conf
>> smuxpeer .22.214.171.124.4.1.674.10892.1
>Would you be willing to try with latest net-snmp 5.4.1.pre3 (built from
>source) instead to rule out a bug in the RHEL4 package?
Sure - where would you propose getting that particular version?
>I'd also suggest to temporarily add "-Dsmux,smux_init,smux_conf" to the
>snmpd options (in /etc/sysconfig/snmpd.options or whatever RHEL4
>promotes) and look into the output. Feel free to post it here if you
>can't make sense out of it.
I did that, and this is what I get:
[smux_accept] accepted fd 13 from 127.0.0.1:46500
smux: [smux_open_process] version 0, len 59, type 2
smux: [smux_open_process] smux peer: SNMPv2-SMI::enterprises.674.10892.1
smux: [smux_open_process] len 47, type 6
smux: [smux_open_process] smux peer descr: Systems Management SNMP MIB Plug-in Manager
smux: [smux_open_process] len 2, type 4
smux: [smux_open_process] smux peer passwd:
smux: [smux_open_process] len 0, type 4
refused smux peer: oid SNMPv2-SMI::enterprises.674.10892.1, password , descr Systems Management SNMP MIB Plug-in Manager
smux: [smux_close] sending close to fd 13, reason 5
smux: [smux_accept] peer on 13 failed authentication
smux: [smux_accept] Calling accept()
clearly somekind of authentication issue?? I've looked in Open Manage, but I'm not able to find out what password to use?
More information about the Linux-PowerEdge