[ZBX-7007] SNMP v3 randomly erroring in 2.1.4 alpha Created: 2013 Sep 13  Updated: 2023 Apr 20  Resolved: 2018 Jan 30

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Templates (T)
Affects Version/s: 2.1.4
Fix Version/s: None

Type: Incident report Priority: Major
Reporter: oliver marshall Assignee: Unassigned
Resolution: Workaround proposed Votes: 3
Labels: snmpv3
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File 2013-09-13 13_58_03-Zabbix 2.0 Appliance_ Configuration of items.png     PNG File 2013-09-13 14_43_31-root@pb04df7__usr_share_snmp_mibs.png     PNG File image-2023-03-28-13-42-27-571.png     PNG File image-2023-03-28-13-43-40-157.png     PNG File image-2023-03-28-13-48-01-413.png    
Sprint: Sprint 19, Sprint 20

 Description   

Hi

We're seeing a similar issue to ZBX-6495. Sorry for the duplicate but I didn't know whether that closed ticket would get re-opened (it still appears as closed).

I think we are seeing the same issue. We have 2.1.4 and get the following errors in the zabbix server log when using SNMPv3 with devices.
****
25076:20130913:112457.918 item [FreePBX:astConfigCallsActive.0] became supported
25076:20130913:112517.959 item [FreePBX:astConfigCallsActive.0] became not supported: Could not connect to "10.1.39.33:161": Authentication failure (incorrect password, community or key)
25090:20130913:113454.723 item [FreePBX:astConfigCallsActive.0] became supported
25075:20130913:113509.503 item [FreePBX:astConfigCallsActive.0] became not supported: Could not connect to "10.1.39.33:161": Authentication failure (incorrect password, community or key)
25090:20130913:120457.741 item [FreePBX:astConfigCallsActive.0] became supported
25075:20130913:120502.747 item [FreePBX:astConfigCallsActive.0] became not supported: Could not connect to "10.1.39.33:161": Authentication failure (incorrect password, community or key)
*********

The same details and auth types in SNMPWALK work fine. To make it even more odd the error flap about as you can see from the logs. Some checks it comes back with valid numbers, other checks it comes back with an authentication error. If you look at the items screen of the device and refresh you can see the checks fail then randomly pass, then fail.

Happy to provide screenshots and the like.

Olly



 Comments   
Comment by richlv [ 2013 Sep 13 ]

if you create only one snmp item with an interval of 30 or 60 seconds, does it also fail every now and then ?

maybe device rejects connections if it's queried too often...

Comment by oliver marshall [ 2013 Sep 13 ]

We've had the same thing with queries running at 3600 seconds and it happens, it just takes longer to realised its errored.

As a test I set up the same monitoring in PRTG and it works fine there.

Olly

Comment by Belokurov Anton [ 2017 Jan 12 ]

I have same issue in Zabbix 3.2.1. Items with SNMPv3 Agent does not work. Authentication failure (incorrect password, community or key).
Manual snmp request from zabbix proxy via snmpget works fine with same credentials.

Comment by Andrei Voinovich [ 2017 Apr 24 ]

Same behavior for different hosts, version 3.0.8

Comment by Andrei Voinovich [ 2017 Apr 25 ]

Strange thing - I changed StartPollers to 1 and 'Authentication failure' messages has gone away, now graphs are looking good. Do not know what is wrong with SNMPv3 processing..

Comment by Catalin LUPESCU [ 2017 Sep 04 ]

We have applied the solution indicated on the forum (restart Zabbix with only 1 Polisher: StartPoller = 1).
(https://www.zabbix.com/forum/showthread.php?t=56514)
It works because we have only 18 hosts on this proxy. However, operation on only one polling already shows its limitations, because the number of items to be updated is at times delayed and this generates false alarms.

We will have to significantly increase the number of hosts (+2000) monitored by this proxy in the coming weeks, and running on only 1 Poller will not hold the charge.

Comment by Oleg Ivanivskyi [ 2017 Oct 16 ]

I was able to reproduce this issue with Ubiquiti edge switches monitored via SNMPv3.
I can get data from command line with snmpwalk/snmpget, but Zabbix is getting Cannot connect to "<IP>:161": Authentication failure (incorrect password, community or key) error. The credentials are OK. Also I have tried to disable "bulk" requests. Didn't help. Debug has no clue.
For now, I am not sure it is device/type specific or general SNMPv3 issue.

Comment by Oleg Ivanivskyi [ 2017 Oct 18 ]

An update. From Zabbix server log file:

 20971:20171018:151120.747 item "<host>:ifNumber" became not supported: Cannot connect to "<host>:161": Authentication failure (incorrect password, community or key).
 20971:20171018:151120.747 item "<host>:sysContact" became not supported: Cannot connect to "<host>:161": Authentication failure (incorrect password, community or key).
 20971:20171018:151120.747 item "<host>:sysDescr" became not supported: Cannot connect to "<host>:161": Authentication failure (incorrect password, community or key).
 20971:20171018:151120.747 item "<host>:sysLocation" became not supported: Cannot connect to "<host>:161": Authentication failure (incorrect password, community or key).
 20971:20171018:151120.747 item "<host>:sysName" became not supported: Cannot connect to "<host>:161": Authentication failure (incorrect password, community or key).

The device's restart didn't help. The items didn't change state after the restart.

Comment by Oleg Ivanivskyi [ 2017 Oct 25 ]

An update: I have changed SNMP to v2 and all the items are OK and Zabbix is getting data. It looks like SNMPv2 is the possible workaround which doesn't explain the issue with SNMPv3 (Engine ID?).

Comment by Sergejs Paskevics [ 2017 Oct 27 ]

It would be very helpful if you send log files with DebugLevel=4

Comment by Pavel Pavlov [ 2020 Aug 12 ]

Have the same problem: Zabbix (ver 4.0.1) and Huawei Switch. SNMPv3 and Authentication failure (incorrect password, community or key). Please tell me, the solution to the problem has not appeared?

Comment by William Desportes [ 2023 Mar 28 ]

ZBX-22709

Generated at Fri Apr 26 17:13:09 EEST 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.