-
Problem report
-
Resolution: Won't fix
-
Trivial
-
None
-
None
-
None
-
None
-
Zabbix Server and Proxy 6.4
Steps to reproduce:
We have many access switches, including Cisco 2960 and 2950 switches. Occasionally, the Zabbix proxy will send SNMP requests, resulting in hundreds of packets per second, causing the switch CPU to become overloaded. Sometimes this issue can last for several hours. Currently, the solution is to restart the Zabbix proxy service using "systemctl restart zabbix-proxy" on the Zabbix proxy server. After the service restarts, the issue is resolved, and the device's CPU returns to normal and will not recur for a certain period of time. However, this issue occurs intermittently on different models of these switches, and the high CPU usage is due to over 500 SNMP packets per second from the Zabbix proxy. We are currently using the 6.4 mpCisco IOS telate, and high-end and large devices have not experienced this issue. The problem is related to common access Cisco switches.
Result:
|[10:30:26|http://10.0.6.152/tr_events.php?triggerid=71698&eventid=31142961]| | |Warning|[12:15:26|http://10.0.6.152/tr_events.php?triggerid=71698&eventid=31142961]|RESOLVED| |SDS2_JL1|#1: High CPU utilization (over 90% for 5m)|1h 45m|Update| |class: networkcomponent: cpuscope: performance| |h4. 10:00| | | | | |[05:16:09|http://10.0.6.152/tr_events.php?triggerid=87467&eventid=31013911]| | |Warning|[05:26:10|http://10.0.6.152/tr_events.php?triggerid=87467&eventid=31013911]|RESOLVED| |SDS7_JL9|#1: High CPU utilization (over 90% for 5m)|10m 1s|Update| |class: networkcomponent: cpuscope: performance| |h4. 05:00| | | | | |[01:11:10|http://10.0.6.152/tr_events.php?triggerid=87477&eventid=30869783]| | |Warning|[01:36:10|http://10.0.6.152/tr_events.php?triggerid=87477&eventid=30869783]|RESOLVED| |SDS7_JL13|#1: High CPU utilization (over 90% for 5m)|25m|Update| |class: networkcomponent: cpuscope: performance| |h4. Today| | | | | |[2023-03-21 21:11:40|http://10.0.6.152/tr_events.php?triggerid=87477&eventid=30769749]| | |Warning|[2023-03-21 21:16:10|http://10.0.6.152/tr_events.php?triggerid=87477&eventid=30769749]|RESOLVED| |SDS7_JL13|#1: High CPU utilization (over 90% for 5m)|4m 30s|Update| |class: networkcomponent: cpuscope: performance| | |[2023-03-21 08:21:01|http://10.0.6.152/tr_events.php?triggerid=82434&eventid=30397964]| | |Warning|[2023-03-21 08:31:01|http://10.0.6.152/tr_events.php?triggerid=82434&eventid=30397964]|RESOLVED| |SDS6_JL10|#1: High CPU utilization (over 90% for 5m)|10m|Update| |class: networkcomponent: cpuscope: performance| | |[2023-03-21 08:16:19|http://10.0.6.152/tr_events.php?triggerid=89282&eventid=30396244]| | |Warning|[2023-03-21 09:01:19|http://10.0.6.152/tr_events.php?triggerid=89282&eventid=30396244]|RESOLVED| |SDS3_JL3|#1: High CPU utilization (over 90% for 5m)|45m|Update| |class: networkcomponent: cpuscope: performance| | |[2023-03-21 08:10:58|http://10.0.6.152/tr_events.php?triggerid=81155&eventid=30394328]| | |Warning|[2023-03-21 08:20:58|http://10.0.6.152/tr_events.php?triggerid=81155&eventid=30394328]|RESOLVED| |SDS6_JL7|#1: High CPU utilization (over 90% for 5m)|10m|Update| |class: networkcomponent: cpuscope: performance| | |[2023-03-21 07:21:02|http://10.0.6.152/tr_events.php?triggerid=82434&eventid=30375876]| | |Warning|[2023-03-21 07:36:01|http://10.0.6.152/tr_events.php?triggerid=82434&eventid=30375876]|RESOLVED| |SDS6_JL10|#1: High CPU utilization (over 90% for 5m)|14m 59s|Update| |class: networkcomponent: cpuscope: performance| | |[2023-03-21 07:16:49|http://10.0.6.152/tr_events.php?triggerid=89282&eventid=30374588]| | |Warning|[2023-03-21 07:21:20|http://10.0.6.152/tr_events.php?triggerid=89282&eventid=30374588]|RESOLVED| |SDS3_JL3|#1: High CPU utilization (over 90% for 5m)|4m 31s|Update| |class: networkcomponent: cpuscope: performance| | |[2023-03-21 07:15:58|http://10.0.6.152/tr_events.php?triggerid=81155&eventid=30374028]| | |Warning|[2023-03-21 07:20:58|http://10.0.6.152/tr_events.php?triggerid=81155&eventid=30374028]|RESOLVED| |SDS6_JL7|#1: High CPU utilization (over 90% for 5m)|5m|Update| |class: networkcomponent: cpuscope: performance| | |[2023-03-21 06:16:19|http://10.0.6.152/tr_events.php?triggerid=89282&eventid=30351486]| | |Warning|[2023-03-21 06:46:19|http://10.0.6.152/tr_events.php?triggerid=89282&eventid=30351486]|RESOLVED| |SDS3_JL3|#1: High CPU utilization (over 90% for 5m)|30m|Update| |class: networkcomponent: cpuscope: performance| | |[2023-03-21 05:16:01|http://10.0.6.152/tr_events.php?triggerid=82434&eventid=30329645]| | |Warning|[2023-03-21 05:36:01|http://10.0.6.152/tr_events.php?triggerid=82434&eventid=30329645]|RESOLVED| |SDS6_JL10|#1: High CPU utilization (over 90% for 5m)|20m|Update| |class: networkcomponent: cpuscope: performance| | |[2023-03-21 05:15:58|http://10.0.6.152/tr_events.php?triggerid=81155&eventid=30329605]| | |Warning|[2023-03-21 05:35:58|http://10.0.6.152/tr_events.php?triggerid=81155&eventid=30329605]|RESOLVED| |SDS6_JL7|#1: High CPU utilization (over 90% for 5m)|20m|Update| |class: networkcomponent: cpuscope: performance| | |[2023-03-21 05:11:49|http://10.0.6.152/tr_events.php?triggerid=89282&eventid=30327760]| | |Warning|[2023-03-21 05:21:19|http://10.0.6.152/tr_events.php?triggerid=89282&eventid=30327760]|RESOLVED| |SDS3_JL3|#1: High CPU utilization (over 90% for 5m)|9m 30s|Update| |class: networkcomponent: cpuscope: performance| | |[2023-03-21 04:25:58|http://10.0.6.152/tr_events.php?triggerid=81155&eventid=30311362]| | |Warning|[2023-03-21 05:00:58|http://10.0.6.152/tr_events.php?triggerid=81155&eventid=30311362]|RESOLVED| |SDS6_JL7|#1: High CPU utilization (over 90% for 5m)|35m|Update| |class: networkcomponent: cpuscope: performance| | |[2023-03-21 03:15:58|http://10.0.6.152/tr_events.php?triggerid=81155&eventid=30285431]| | |Warning|[2023-03-21 03:40:58|http://10.0.6.152/tr_events.php?triggerid=81155&eventid=30285431]|RESOLVED| |SDS6_JL7|#1: High CPU utilization (over 90% for 5m)|25m|Update| |class: networkcomponent: cpuscope: performance| | |[2023-03-21 02:16:19|http://10.0.6.152/tr_events.php?triggerid=89282&eventid=30263710]| | |Warning|[2023-03-21 02:21:19|http://10.0.6.152/tr_events.php?triggerid=89282&eventid=30263710]|RESOLVED| |SDS3_JL3|#1: High CPU utilization (over 90% for 5m)|5m|Update| |class: networkcomponent: cpuscope: performance| | |[2023-03-21 01:21:19|http://10.0.6.152/tr_events.php?triggerid=89282&eventid=30244256]| | |Warning|[2023-03-21 01:26:19|http://10.0.6.152/tr_events.php?triggerid=89282&eventid=30244256]|RESOLVED| |SDS3_JL3|#1: High CPU utilization (over 90% for 5m)|5m|Update| |class: networkcomponent: cpuscope: performance| | |[2023-03-21 01:21:02|http://10.0.6.152/tr_events.php?triggerid=82434&eventid=30244216]| | |Warning|[2023-03-21 01:26:01|http://10.0.6.152/tr_events.php?triggerid=82434&eventid=30244216]|RESOLVED| |SDS6_JL10|#1: High CPU utilization (over 90% for 5m)|4m 59s|Update| |class: networkcomponent: cpuscope: performance| | |[2023-03-21 01:15:58|http://10.0.6.152/tr_events.php?triggerid=81155&eventid=30242452]| | |Warning|[2023-03-21 01:20:58|http://10.0.6.152/tr_events.php?triggerid=81155&eventid=30242452]|RESOLVED| |SDS6_JL7|#1: High CPU utilization (over 90% for 5m)|5m|Update| |class: networkcomponent: cpuscope: performance|
Expected:
Before upgrading to Zabbix Server 6.4, I was using version 6.2, and during several months of usage, this issue did not occur frequently.
Please investigate this issue further, as sending more than 500 SNMP packets per second to a device for several hours is abnormal.
