[ZBXNEXT-5703] Receive SNMP traps by Zabbix Server/Proxy without snmptrapd Created: 2020 Jan 20  Updated: 2025 Mar 10

Status: Open
Project: ZABBIX FEATURE REQUESTS
Component/s: Proxy (P), Server (S)
Affects Version/s: None
Fix Version/s: None

Type: Change Request Priority: Trivial
Reporter: Edgar Akhmetshin Assignee: Zabbix Development Team
Resolution: Unresolved Votes: 25
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Causes
caused by ZBX-17192 SNMP traps in RHEL8/CentOS 8 - missin... Closed
Duplicate
Sub-task
depends on ZBXNEXT-6941 Introduce rate-limiting for trapper/S... Open

 Description   

There are currently two ways (perl script or snmptt) suggested, both through a third-party library and process.

Since distributions deliver the required packages with varying degrees of support, situations may arise when there are simply no regular capabilities - you need to install additional packages and third-party repositories or build manually. Fresh example: ZBX-17192.

Another problem is to deal with SNMPv3 traps, every hosts should be added manually to the snmptrapd configuration file or some configuration management system, this becomes more complicated.

The idea:

  • create Zabbix Server/Proxy module for SNMPv1/2/3 with public documentation how to extend and modify it according to the environment needs. Only basic functionality to catch all traps - as perl script provided now, some multithreaded options may be added for large environments with high snmp traps flow like cellular providers, etc...;
  • use SNMPv3 credentials for polling to allow incoming traps without additional settings, get EngineID from device directly or allow additional filed to add only this information, not to duplicate credentials in frontend and in snmptrapd;

Regards,
Edgar



 Comments   
Comment by Dimitri Bellini [ 2022 Mar 31 ]

I would like to share my 2 cents to this ZBXNEXT, maybe is better to open a new one but i do not know :-0

Before Zabbix 6.0, if you would like to create a Zabbix in High Availability you had to configure Corosync/Pacemaker cluster and multiple resources to manage the failover status of a services.
One of this services in most of our cases was SNMPTRAPD but as you know there is a BIG problem on that using Zabbix.
Everytime Zabbix Server restarts will try to re-read all "snmptrap logs", usually we fix it with a script on Pacemaker "resource".
At the moment with Zabbix 6.0 and the native implementation of High Availability we can NOT do that... How we can workaround this problem?
As already proposed the better solution is to have this type of "check/service" inside Zabbix Server/Proxy.
Thanks so much

Generated at Mon Mar 31 01:28:24 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.