OM / snmpd / smux conflict??

Thomas Anders thomas.anders at blue-cable.de
Sun Jun 24 01:58:14 CDT 2007


Larsen, Peter wrote:
> Sure - where would you propose getting that particular version?

http://www.net-snmp.org/download

> 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()

What about at startup? There should be some output when it parses the
"smuxpeer" line from snmpd.conf. If it's not there, add "-Dread_config"
to make sure the agent is reading the right snmpd.conf.

> clearly somekind of authentication issue??  I've looked in Open Manage, but I'm not able to find out what password to use?

OM usually works w/o a password, AFAIK (oh well).


+Thomas



More information about the Linux-PowerEdge mailing list