For mine I use:
snmp-server enable traps entity config-change
This captures any running or startup config changes. The
fru-remove should capture hardware changes (not problems with existing but actual inserts or removals of modules).
I know you specified the community in the
snmp-server host line but do you also have a line for
snmp-server community ***** ?
I use snmp v3 so mine will look different than yours, but still, you should be right.
Are you sure it isn't sending traps though?
You can troubleshoot with various commands (or even using an snmpwalk tool like the one from Paessler):
To ensure that the SNMP process that receives incoming packets from
the NMS is running, enter the following command:
hostname(config)# show process | grep snmp
To capture syslog messages from SNMP and have them appear on the ASA
or ASASM console, enter the following commands:
hostname(config)# logging list snmp message 212001-212015
hostname(config)# logging console snmp
To make sure that the SNMP process is sending and receiving packets,
enter the following commands:
hostname(config)# clear snmp-server statistics
hostname(config)# show snmp-server statistics
The output is based on the SNMP group of the SNMPv2-MIB.
To make sure that SNMP packets are going through the ASA or ASASM and
to the SNMP process, enter the following commands:
hostname(config)# clear asp drop
hostname(config)# show asp drop