<privpass>
Set the privacy pass phrase used for encrypted SNMP v3 messages. The same
value must be found in
/BDUX/LoggerDaemon/Plugins/SNMP/SecurityPrivProtoPass registry key.
This line will be replacedwith another one, with encrypted passwords, when snmptrapd
daemon is started.
One more thing: you do not need to use all the parameters specified above for SNMP
v3. You can use the authentication without encryption (the SecurityLevel key is
authNoPriv) or no authentication and no encryption (the SecurityLevel key is
noAuthNoPriv). You have to modify the createUser line accordingly.
This would be the user. Now, let's get back to the /etc/snmp/snmpd.conf file and
added some more lines. You might find them already in your file, but commented out.
Uncomment them and set the correct values.
# trapsink: A SNMPv1 trap receiver
trapsink localhost
# trap2sink: A SNMPv2c trap receiver
trap2sink localhost
# informsink: A SNMPv2c inform (acknowledged trap) receiver
informsink localhost public
# trapcommunity: Default trap sink community to use
trapcommunity public
# authtrapenable: Should we send traps when authentication
# failures occur
authtrapenable 1
I think this is the moment to start the snmpd and snmptrapd daemons. If you get an
error, please review the configuration.
Usage
Now you can test the SNMP server. Here are some commands you may start with.
The first one will send TRAP alert that should be logged on syslog. Please note we use
the EngineID.
# snmptrap -e 0xBD224466 -v 3 -m ALL -u bitdefender -l authPriv \
-a
MD5
-A
<authpass>
-x
DES
-X
<privpass>
localhost
42
\
coldStart.0
Another command sends an INFORM alert. In this case, there is no need to specify the
EngineID and the user you have created must not have the EngineID. In our examples,
12
EVALUATOR'S GUIDE
BitDefender Mail Protection for Enterprises
