Check the configuration lines in the SystemEdge configuration.
This should look like the following example:
SNMP_V3_TRAP_INFO 192.168.1.2-162 * secureuser 100
The 100 at the end of the line is neccesary for SPECTRUM to encode the trap correctly.
This changes SystemEDGE?s default trap encoding. More information is in sysedge\doc\Trap-Encoding.txt file
Restart the SDManager service on the SpectroSERVER.
This is a vital step with any change being made to the SystemEdge Engine ID, as the SDManager will not associate the traps with the modeled device any longer and will drop the traps without processing them.
How to integrate SystemEdge with Spectrum as an SNMPv3 device
Causes of this problem:
After the integration and discovery of the SystemEdge agent in SPECTRUM, you cannot see any of the SNMPv3 traps being processed as events.
If you are still having problems with the integration following these steps, you should contact CA Technical Support and provide the following information:
SystemEdge v3 configuration
Line trace from the client to the SPECTRUM server showing the trap being sent.
SDM.out file from the SpectroSERVER
(Legacy KB ID CNC TS29833 )