>> accepted smux peer: oid SNMPv2-SMI::zeroDotZero, descr dbsnmp
>>=20
>> AND:
>>=20
>> 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.
>> In my snmpd.conf I have a line saying "smuxpeer 0.0". Now I assume
>> net-snmpd refuses the smux authentication because it already=20
>> 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.
As silly as it sounds the "fix" is to include "smuxpeer 0.0" two times in
snmpd.conf. The code doesn't check for this duplicate and when Oracle Agent and
Listener register they each use 1 slot. Voila! Works!
Thanks for your help,
Krisztian
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
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
