Hello Robert,
I have tested the patch and it seems to work in these
conditions:
1. trapsses destination down
2. destination started after agent started
3. destination restarted while agent running
And all traps were received as expected. No error
message was seen.
Thanks a lot for your
On Fri, 22 Apr 2005 15:02:10 +0100 Dave wrote:
DS On Fri, 2005-04-22 at 14:54, Robert Story wrote:
DS Ok, I found my mistake. Reverse the previous patch,
DS and apply this one instead...
DS
DS
DS @@ -704,6 +704,7 @@
DS session-version = SNMP_DEFAULT_VERSION;
DS session-securityModel
On Fri, 22 Apr 2005 09:00:58 -0700 (PDT) Mauricio wrote:
MR I have tested what you sent me, but I'm getting this
MR message:
MR
MR snmpd: send_trap: USM unknown security name (no such
MR user exists)
Sigh. Ok, I now know more about trap sessions and engineID discovery that I
really wanted to,
Hello,
I have tested what you sent me, but I'm getting this
message:
snmpd: send_trap: USM unknown security name (no such
user exists)
NET-SNMP version 5.2.1
snmpd: send_trap: USM unknown security name (no such
user exists)
snmpd: send_trap: USM unknown security name (no such
user exists)
It
On Sun, 17 Apr 2005 11:44:21 -0700 (PDT) Mauricio wrote:
MR I have tested the patch you sent me, but it seems to
MR fail. I get this line:
MR
MR C:\usrsnmpd
MR netsnmp_assert x failed C:\Documents and
MR Settings\Maure\Desktop\net-snmp-5.2.1\ne
MR t-snmp-5.2.1\snmplib\snmp_api.c:1271
MR
MR The
Hello Robert,
I have deleted that line, but there's still errors. I
used gdb to debug and got this:
Program received signal SIGSEGV, Segmentation fault.
snmp_sess_synch_response (sessp=0x80d96a8,
pdu=Variable pdu is not available.
) at snmp_client.c:870
870 cbsav = ss-callback;
(gdb) l
Hello Robert,
I have tested the patch you sent me, but it seems to
fail. I get this line:
C:\usrsnmpd
netsnmp_assert x failed C:\Documents and
Settings\Maure\Desktop\net-snmp-5.2.1\ne
t-snmp-5.2.1\snmplib\snmp_api.c:1271
The code that seems to generate the error is this:
if (slp != NULL) {
On Thu, 14 Apr 2005 18:35:08 -0700 (PDT) Mauricio wrote:
MR Yeah, that's what he tried. I do remember seeing a
MR patch go by that delayed
MR engineID discovery until it was needed. I'll see if
MR I can dig it up...
MR
MR I'd appreciate that.
The patch was for 5.0.9, and I changed it a bit,
On Fri, 15 Apr 2005 10:09:58 -0400 Robert wrote:
RS The patch was for 5.0.9, and I changed it a bit, so this is untested. Give
RS it a whirl and let me know if:
RS
RS a) there is no error message at startup if the peer is down
RS b) after bringing up the peer, informs are received...
forgot to
On Thu, 2005-04-14 at 01:30, Mauricio Reyes wrote:
Yes, I can send traps with those parameters. When the
trapsess destination machine is up, I receive the
traps as expected.
That's basically working as expected.
Remember that traps are an *unreliable* mechanism.
If the trap receiver is down
On Thu, 14 Apr 2005 09:45:24 +0100 Dave wrote:
DS On Thu, 2005-04-14 at 01:30, Mauricio Reyes wrote:
DS Yes, I can send traps with those parameters. When the
DS trapsess destination machine is up, I receive the
DS traps as expected.
DS
DS The situation here sounds slightly different.
DS If the
Hello Robert,
I'd appreciate that.
Thanks a lot.
--- Robert Story [EMAIL PROTECTED] wrote:
On Thu, 14 Apr 2005 09:45:24 +0100 Dave wrote:
DS On Thu, 2005-04-14 at 01:30, Mauricio Reyes
wrote:
DS Yes, I can send traps with those parameters.
When the
DS trapsess destination machine is
Hello Robert,
Yes, I can send traps with those parameters. When the
trapsess destination machine is up, I receive the
traps as expected.
Can you help me with this? I really need to solve
this.
Thanks a lot.
--- Robert Story [EMAIL PROTECTED] wrote:
On Tue, 29 Mar 2005 17:33:16 -0800 (PST)
13 matches
Mail list logo
