[ZBX-19353] SNMPv3 (SHA/AES) access on Dell Idrac9 fail Created: 2021 May 11  Updated: 2021 May 28

Status: Confirmed
Project: ZABBIX BUGS AND ISSUES
Component/s: None
Affects Version/s: 4.0.30
Fix Version/s: None

Type: Incident report Priority: Trivial
Reporter: Matthias Küster Assignee: Zabbix Development Team
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

We use Zabbix Server 4.0.30 with Zabbix Proxy 4.0.30. Our OS is Ubuntu Server 18.04.


 Description   

Steps to reproduce:

  1. Set Passwort on Dell Idrac
  2. Test it with snmpwalk (snmpwalk -v 3 -u XXXX -l authPriv -a SHA -A XXXX -x AES -X XXXX IP 1.3.6.1.6.3.10.2.1.1
    iso.3.6.1.6.3.10.2.1.1.0 = Hex-STRING: 80 00 1F 88 04 43 33 33 33 4E 58 32) )
  3. Click on chek now in Zabbix
  4. Recheck with snmpwalk (snmpwalk -v 3 -u XXXX -l authPriv -a SHA -A XXXX -x AES -X XXXX IP 1.3.6.1.6.3.10.2.1.1
    snmpwalk: Authentication failure (incorrect password, community or key) )

 

 Comments   
Comment by Dmitry Krupornitsky [ 2021 May 13 ]

Hello, 

What about community name, are they the same? snmpwalk should be tested from the same server as Zabbix server is installed.

Comment by Matthias Küster [ 2021 May 14 ]

Hi,

we use SNMPv3 that does not use community names.
the server is the same for snmpwalk and ZBX proxy.

Comment by Dmitry Krupornitsky [ 2021 May 14 ]

Sorry, did not mentioned v3. Did you try v2, does it work?

Okay, what template do you use?

Comment by Matthias Küster [ 2021 May 14 ]

I have not tested v2 as I need v3
The template is from Zabbix

Comment by Matthias Küster [ 2021 May 28 ]

The problem is complicated. After restarting the proxy, the one DELL IDRAC is accessible again. But other SNMPv3 systems are not always reachable.
We use over 50 pollers for well over 100 SNPV3 hosts on the Zabbix proxy.

After reading the articles ZBX-18876 and ZBX-8385 there seems to be a problem between the transfer from Zabbix to the SNMP service. Or that a host is queried by different poller processes and therefore also different SNMP caches are used.

After restarting the server/proxy the problem is mostly solved.
However, restarting also restarts the pollers and the SNMP services. As a result, all SNMPv3 connections must be renegotiated.

 

We are now using Zabbix 4.0.31

Generated at Wed Jul 16 10:10:17 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.