A problem with SNMP Traps

[Bakhshik]

We have a Zabbix server and Zabbix proxy running on Centos 8 and Centos 7 respectively. A trap receiver is configured on the Zabbix proxy according to these instructions https://www.youtube.com/watch?v=fVK2YWdTalQ.

While catching traps we see them in the file /tmp/zabbix_traps.tmp, however we don’t see them in the latest data section and therefore the fallback trigger doesn’t fire an alarm.
Here is our SNMP trap fallback trigger’s expression:
{Template SNMP trap fallback:snmptrap.fallback.nodata(300)}=0

[Hamardaban]

If you do not see the value in the latest data, it means that something is configured incorrectly or not completely.
Check all settings according to the documentation https://www.zabbix.com/documentation...types/snmptrap .
Look in the proxy and server log to control the start of the snmp trapper and to check for errors in processing traps.

[rakeshoo7]

SNMP managers can also run into trouble if a device is sending non-standard traps. Although SNMP is a standard protocol, some people have modified the formats of their traps to suit special needs. They might have, for example, added an extra field to their traps to transmit a particular piece of additional data.

[Bakhshik]

While we still don't see a sample SNMP trap in the latest data section, we have started to see traps from our Cisco switches. Please advise what template to use for SNMP traps sent by Cisco network devices.