we have created the bitdefender_inform user for this purpose. The alert will be
logged on syslog too.
# snmpinform -v 3 -m ALL -u bitdefender_inform -l authPriv -a MD5 \
-A
<authpass>
-x
DES
-X
<privpass>
localhost
42
\
coldStart.0
If you do not want to use the SNMP version 3 protocol, you can use the other two
supported: 1 and 2c. In this case you do not need the username, all you have to know
is the community string. This is public by default. For example, for version 2c, use
this command.
# snmptrap -c public -v 2c -m ALL localhost 42 coldStart.0
If everything is all right and BitDefender is properly configured (that means theregistry
keys fit the SNMP server configuration), all you have to do is to enable the plugin (if
not already enabled) and try it by sending emails through the MTA. You will shortly
see the report on the syslog of the machine running the SNMP server.
4.3. Update
The BitDefender update process is realized by Live! Update, a daemon which connects
periodically to the BitDefender update server and checks whether new virus definitions,
antispam updates and product upgrades are available. In case there are any, the
daemon will download only the changed files, executing an incremental update and
conserving the bandwidth.
Automatic update
BitDefender Mail Protection for Enterprises is configured to updateautomatically each
8 hours, through bdlived module. In case of a necessary update, before the specified
interval expires, the daemon can be signaled to execute the update routine, manually.
To trigger the on-demand check, one can issue following command, using bdsafe(8).
# bdsafe update
The command will output nothing, but, if you check the log file, you will see a line
stating that the update process has been triggered.
You can check the update module configuration at any time. Just use the bdsafe again.
# bdsafe configure update
13
EVALUATOR'S GUIDE
BitDefender Mail Protection for Enterprises
