A Fortinet device not yet Spectrum certified and discovered in Spectrum as GnSNMPDev is sending traps to Spectrum. Some of these are failing with the message: Unknown alert received from device RPPFWXXXXX of type GnSNMPDev. Device Time 2+18:08:40. (Trap type 188.8.131.52.184.108.40.206.2) Trap var bind data: OID: 220.127.116.11.18.104.22.168.0 Value: 23812084 OID: 22.214.171.124.126.96.36.199.4.1.0 Value: 188.8.131.52.184.108.40.206.2 OID: 220.127.116.11.18.104.22.168.1.7 Value: 169.254.4.6 OID: 22.214.171.124.126.96.36.199.1.14 Value: 6.3 OID: 188.8.131.52.184.108.40.206.1.2 Value: 1 Why?
The AlertMap file to handle the trap type 220.127.116.11.18.104.22.168.2 and 22.214.171.124.126.96.36.199.1 is present under the folder: <$SPECROOT>\SS\CsVendor\Ctron_SNMP_Rtr\BGP4_App and when the trap arrives to Spectrum, probably this is not processed because the device was discovered as GnSNMPDev, resulting in an "Unknown alert received from device RPPFWXXXXX of type GnSNMPDev..."
Spectrum 10.3 on any platform
Copy the AlertMap from the <$SPECROOT>\SS\CsVendor\Ctron_SNMP_Rtr\BGP4_App into the <$SPECROOT>\Custom\Events folder, then open the VNM model -> SpectroSERVER Control and click on Update Event Configuration.