Re: restarting snmpd does not generate a trap

On 07/12/2007, PoWah Wong <[email protected]> wrote:
> I can send a trap from the FC6 machine to my snmptrapd
> at 172.20.11.58:
> # snmptrap -v 3 -u test_MD5_AES -l authPriv -a MD5 -A
>     12345678 -x AES -X 87654321 -e
>     0x800000000102030405060708 172.20.11.58 0 coldStart.0

OK - so if that invocation works, why not try using the
same settings in your snmpd.conf file.
I.e.

    trapsess -v 3 -u test_MD5_AES -l authPriv -a MD5 -A
     12345678 -x AES -X 87654321 -e
     0x800000000102030405060708 172.20.11.58:162


Note that the options should come *before* the name of
the host to send notifications to - just as they do with
the "snmptrap" command.


It might also be worth trying "snmptrap" using the
same settings as the trapsess entries.

If you can run
    "snmptrap  {something}   172.20.11:58:162"
successfully, then you ought to be able to use
    "trapsess {something} 172.20.11:58:162"

And vice versa.

Dave

-------------------------------------------------------------------------
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
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