2009/6/26 PoWah Wong <[email protected]>: > However, with the "-d" option, > "snmptrapd -f -C -c /home/powah/snmp/snmptrapd.conf -Lo -d" > or > "snmptrapd -Lf /home/powah/tmp/log.log -f -C -c > /home/powah/snmp/snmptrapd.conf -d" > see all traps displayed on the screen or in the log.log file.
What do you mean by "all traps displayed"? What exactly do you see? The -d option will display a raw packet dump of the incoming trap *before* it is processed. Is this what you are seeing? Or do you see a one- or two-line readable summary of the trap contents? > snmptrapd.conf is as follows: > createUser admin MD5 12345678 DES 87654321 > createUser adminwindows MD5 12345678 DES 87654321 > > authuser log admin > logOption s u You seem to have dropped the "disableAuthorization yes" line, which I suggested a few days ago. That is definitely worth keeping for now, until you manage to get traps received successfully. Then you can start putting back these security checks. But the first thing is to ensure that traps are being received by snmptrapd. Alternatively, as Mike suggests, you could add an "authCommunity" line in order to accept SNMPv1 or v2c notifications. You haven't said what community you used, but that's the name you need to provide in this line. But I'd recommend that you simplify things as much as possible first, and only start putting back the authentication stuff once the fundamentals are working. Dave ------------------------------------------------------------------------------ _______________________________________________ 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
