Hoping someone has run into this issue before...
I've managed to get the Oracle Enterprise agent and the Oracle Listener
work with net-snmp (they both use the obsolete smux protocol), the catch
is that I can get either of them to register to net-snmpd but not both
at the same time! The reason is that they both are trying to use the 0.0
OID spec for their registration:
accepted smux peer: oid SNMPv2-SMI::zeroDotZero, descr dbsnmp
AND:
accepted smux peer: oid SNMPv2-SMI::zeroDotZero, descr NSGS
The first one is the Enterprise agent, the second one is the Listener
(obviusly the above entries were copied from separate runs, since they
don't work together). When I try to get them to register one after the
other this is what I get:
refused smux peer: oid SNMPv2-SMI::zeroDotZero, descr NSGS
In my snmpd.conf I have a line saying "smuxpeer 0.0". Now I assume
net-snmpd refuses the smux authentication because it already shows that
another peer authenticated using the same (0.0) OID spec. So either
Oracle completely ignored the smux protocol guidelines or I'm missing
something here big time. (What's interesting is if I use the master
agent that comes with Oracle (master_peer) instead of net-snmpd both of
the above processes register to it fine.)
Has anyone seen this issue?
Thanks,
Krisztian
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Net-snmp-users mailing list
[email protected]
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users
