1. We first must verify that the Spectrum Server is receiving the traps being sent by SysEDGE Agent.
This can be done via a sniffer trace - we recommend the Wireshark application. If we are not receiving communication from the sysEdge ip on port 162, then Spectrum is not going to receive a trap. If not then the SysEdge.cf in tmp to verify if the trap_community public i.p. 162 is configured.
Please note it must be set to port 162 or Spectrum see it.
2. Is the customer seeing "Unknown alert received" events asserted on the Host_systemEDGE model?
If so then the trap is arriving, but the trap is not supported out of the box and has not been mapped in Spectrum. We will need to use the trap information, to create custom mappings in Spectrum, to make the trap alarm.
e.g. unknown trap from sysedge agent arrives to Spectrum as follows:
enterprise: 184.108.40.206.4.1.546.1.1 (iso.220.127.116.11.1.546.1.1)
generic-trap: enterpriseSpecific (6)
variable bindings for this trap:
Object Name: 18.104.22.168.4.1.522.214.171.124.1.7 (iso.126.96.36.199.1.5188.8.131.52.1.7)
Object Name: 184.108.40.206.4.1.5220.127.116.11.2.7 (iso.18.104.22.168.1.522.214.171.124.2.7)
Object Name: 126.96.36.199.4.1.5188.8.131.52.3.7 (iso.184.108.40.206.1.5220.127.116.11.3.7)
Object Name: 18.104.22.168.4.1.522.214.171.124.4.7 (iso.126.96.36.199.1.5188.8.131.52.4.7)
A grep in the CsVendor folder, shows no results for this trap 184.108.40.206.4.1.5220.127.116.11.21. or the variable bindings so we need to create a custom alert map entry at
<$SPECROOT>\custom\Events\AlertMap in the following format
and a custom event to alarm - <0x000fffxxx>
# trap name
18.104.22.168.4.1.522.214.171.124.21 0x000fffxxx 126.96.36.199.4.1.5188.8.131.52.1.7(1,2) \
This is an example of a customized trap and its varbind mappings.