This is a discussion on RE: Using net-snmp with Oracle Enterprise Manager agent and Listener within the SNMP Users forums, part of the Networking and Network Related category; > From: net-snmp-users-bounces@lists.sourceforge.net > [mailto:net-snmp-users-bounces@lists.sourceforge.net] On > ...
|
|||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
|
|||
|
> From: net-snmp-users-bounces@lists.sourceforge.net > [mailto:net-snmp-users-bounces@lists.sourceforge.net] On > Behalf Of kabbalah74-unsec@yahoo.com > Sent: Monday, October 01, 2007 2:32 PM > Hoping someone has run into this issue before... Ehhhhh... not me. > 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: I do not believe the problem is due to registration. > accepted smux peer: oid SNMPv2-SMI::zeroDotZero, descr dbsnmp > > AND: > > accepted smux peer: oid SNMPv2-SMI::zeroDotZero, descr NSGS These appear to indicate that both subagents are setting their identity to .0.0 in the OpenPDU. This is not strictly illegal, but is a really bad idea. > 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 This indicates that it is refusing the peer (subagent), not the registration. An SMUX peer may perform many registrations. > 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. Non sequitur, I think. The "smuxpeer" line indicates what may be registered, not what sessions may be opened. At least that's how the docs read, but there's a password parameter, and SMUX only uses passwords in the OpenPDU, i.e., per peer, so I'm not quite sure what should work or not here. > So either > Oracle completely ignored the smux protocol guidelines or I'm missing > something here big time. Option 3 - you're finding out why SMUX never went far. > (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.) Oracle's subagents and master work together - nothing surprising about that. > Has anyone seen this issue? Not specifically, no. Suggested workaround: Use the Oracle master agent to host these two subagents and use the "proxy" directive in the snmpd.conf of your net-snmp master agent to forward requests for those subagents only to the Oracle master agent. HTH, Mike ------------------------------------------------------------------------- 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 Net-snmp-users@lists.sourceforge.net Please see the following page to unsubscribe or change other options: https://lists.sourceforge.net/lists/...net-snmp-users |