SNMPv3 do not work in zabbix

[akbar415]

If I run snmpwalk on the same machine of zabbix server I can collect data with snmpv3

snmpwalk -v3 -u Usnmp -l AuthNoPriv -a MD5 -A 'AuthPass' 10.x.x.x .1.3.6.1.2.1.1.3.0
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (61650508) 7 days, 3:15:05.08

But in Zabbix Server I can't.

Zabbix do not give me data, queue always empty for snmpv3 agent, error message in front end no even error message in the log.



My zabbix config:

Type: SNMPv3 agent
Key: SysUptime
Host interface: 10.x.x.x:161
SNMP OID: .1.3.6.1.2.1.1.3.0
Security name: {$SNMP_SECNAME}
Security level: authNoPriv
Authentication protocol: MD5
Authentication passphrase: {$SNMP_AUTH}


Zabbix 3.0


When zabbix sends the snmp request through the firewall cluster and, for example, hits firewall node A, the response is sometimes received by firewall node b. Since firewall node b doesn't know who sent the request, it simply drops it.

[batchenr]

Hi,

if i realized correctly if you run it manually it works but if you make it as trigger
it does not work ?

have you checked zabbix macros ?
Administration - > General - > drop down menu choose : Macros

and please add more logs info.
change debug at zabbix_server.conf to 4 and restart see if you can get more output.

[akbar415]

Edited

If I run snmpwalk on the same machine of zabbix server I can collect data with snmpv3

snmpwalk -v3 -u Usnmp -l AuthNoPriv -a MD5 -A 'AuthPass' 10.x.x.x .1.3.6.1.2.1.1.3.0
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (61650508) 7 days, 3:15:05.08

But in Zabbix Server I can't.

Zabbix do not give me data, queue always empty for snmpv3 agent, error message in front end no even error message in the log.



My zabbix config:

Type: SNMPv3 agent
Key: SysUptime
Host interface: 10.x.x.x:161
SNMP OID: .1.3.6.1.2.1.1.3.0
Security name: {$SNMP_SECNAME}
Security level: authNoPriv
Authentication protocol: MD5
Authentication passphrase: {$SNMP_AUTH}



Zabbix 3.0

After some attemps and zabbix restart's I can make zabbix get data with snmp v3 but not in a satisfactory manner.

As we can see in the image below, there is lack of data sometimes.




When this happen, zabbix write this message in the log (debug mode)

42525:20170107:203801.068 SNMP agent item "sysDescr" on host "Switch 7 Andar - DOMAIN0 v3" failed: first network error, wait for 15 seconds
42525:20170107:203816.113 resuming SNMP agent checks on host "Switch 7 Andar - DOMAIN0 v3": connection restored
 42594:20170107:203817.489 item "Switch 7 Andar - DOMAIN0 v3:ifOutOctets[GigabitEthernet3/0/4]" became not supported: Cannot connect to "10.X.X.X:161": Authentication failure (incorrect password, community or key).
42593:20170107:203819.594 item "Switch 7 Andar - DOMAIN0 v3:ifOperStatus[GigabitEthernet3/0/20]" became not supported: Cannot connect to "10.X.X.X:161": Authentication failure (incorrect password, community or key).
 42593:20170107:203819.594 item "Switch 7 Andar - DOMAIN0 v3:ifOutOctets[GigabitEthernet1/0/10]" became not supported: Cannot connect to "10.X.X.X:161": Authentication failure (incorrect password, community or key).
 42593:20170107:203821.602 item "Switch 7 Andar - DOMAIN0 v3:ifAdminStatus[GigabitEthernet1/0/1]" became supported

[batchenr]

it seems like it is - zabbix loosing connection to your device.
you need to check on device side first and maybe also increase Update interval on the item you have created.

[kyern]

I have same issue with Zabbix 3.2.1
snmpget from proxy works fine, but item in status unsupported with "Authentication failure (incorrect password, community or key)" error.
SNMPv1 Agent items is OK
Log:

15526:20161227:154854.770 item "UPSR1:apc_snmp_batt_test" became not supported: Cannot connect to "192.168.254.31:161": Authentication failure (incorrect password, community or key).
 15525:20161227:154925.155 item "UPSR1:apc_snmp_batt_test" became supported
 15524:20161227:154944.802 error reason for "UPSR1:upsAdvBatteryCapacity" changed: SNMP error: authorizationError (access denied to that object)
 15525:20161227:154956.357 item "UPSR1:apc_snmp_batt_test" became not supported: Cannot connect to "192.168.254.31:161": Authentication failure (incorrect password, community or key).
 15526:20161227:155242.164 item "UPSR1:iemStatusProbeCurrentTemp" became not supported: Cannot connect to "192.168.254.31:161": Authentication failure (incorrect password, community or key).
 15525:20161227:155244.170 item "UPSR1:upsAdvBatteryActualVoltage" became not supported: Cannot connect to "192.168.254.31:161": Authentication failure (incorrect password, community or key).
 15527:20161227:155245.239 item "UPSR1:upsAdvBatteryCapacity" became not supported: Cannot connect to "192.168.254.31:161": Authentication failure (incorrect password, community or key).
 15527:20161227:155246.277 item "UPSR1:upsAdvBatteryRunTimeRemaining" became not supported: Cannot connect to "192.168.254.31:161": Authentication failure (incorrect password, community or key).
 15527:20161227:155247.351 item "UPSR1:upsAdvBatteryTemperature" became not supported: Cannot connect to "192.168.254.31:161": Authentication failure (incorrect password, community or key).
 15526:20161227:155249.660 item "UPSR1:upsAdvInputFrequency" became not supported: Cannot connect to "192.168.254.31:161": Authentication failure (incorrect password, community or key).
 15526:20161227:155250.837 item "UPSR1:upsAdvInputLineVoltage" became not supported: Cannot connect to "192.168.254.31:161": Authentication failure (incorrect password, community or key).
 15526:20161227:155251.871 item "UPSR1:upsAdvOutputCurrent" became not supported: Cannot connect to "192.168.254.31:161": Authentication failure (incorrect password, community or key).
 15524:20161227:155253.496 item "UPSR1:upsAdvOutputFrequency" became not supported: Cannot connect to "192.168.254.31:161": Authentication failure (incorrect password, community or key).
 15524:20161227:155253.496 item "UPSR1:upsAdvOutputLoad" became not supported: Cannot connect to "192.168.254.31:161": Authentication failure (incorrect password, community or key).
 15525:20161227:155255.530 item "UPSR1:upsAdvOutputVoltage" became not supported: Cannot connect to "192.168.254.31:161": Authentication failure (incorrect password, community or key).
 15525:20161227:155429.929 item "UPSR1:upsAdvBatteryReplaceIndicator" became not supported: Cannot connect to "192.168.254.31:161": Authentication failure (incorrect password, community or key).
 15525:20161227:155433.813 item "UPSR1:upsAdvIdentSerialNumber" became not supported: Cannot connect to "192.168.254.31:161": Authentication failure (incorrect password, community or key).
 15525:20161227:155441.126 item "UPSR1:upsBasicBatteryLastReplaceDate" became not supported: Cannot connect to "192.168.254.31:161": Authentication failure (incorrect password, community or key).
 15525:20161227:155441.127 item "UPSR1:upsBasicBatteryStatus" became not supported: Cannot connect to "192.168.254.31:161": Authentication failure (incorrect password, community or key).
 15526:20161227:160429.148 item "UPSR1:upsAdvBatteryCapacity" became supported
 15526:20161227:160458.329 item "UPSR1:upsAdvBatteryCapacity" became not supported: Cannot connect to "192.168.254.31:161": Authentication failure (incorrect password, community or key).
 15524:20161227:161425.152 item "UPSR1:apc_snmp_batt_test" became supported
 15526:20161227:161426.231 item "UPSR1:iemStatusProbeCurrentTemp" became supported
 15524:20161227:161427.232 item "UPSR1:upsAdvBatteryActualVoltage" became supported
 15526:20161227:161428.322 item "UPSR1:upsAdvBatteryCapacity" became supported
 15524:20161227:161429.742 item "UPSR1:upsAdvBatteryReplaceIndicator" became supported
 15527:20161227:161430.521 item "UPSR1:upsAdvBatteryRunTimeRemaining" became supported
 15527:20161227:161431.779 item "UPSR1:upsAdvBatteryTemperature" became supported
 15524:20161227:161432.805 item "UPSR1:upsAdvIdentSerialNumber" became supported
 15524:20161227:161435.048 item "UPSR1:upsAdvInputLineVoltage" became supported
 15524:20161227:161436.089 item "UPSR1:upsAdvOutputCurrent" became supported
 15524:20161227:161436.090 item "UPSR1:upsAdvOutputFrequency" became supported
 15526:20161227:161439.659 error reason for "UPSR1:upsBasicBatteryLastReplaceDate" changed: No Such Instance currently exists at this OID
 15525:20161227:161455.061 item "UPSR1:apc_snmp_batt_test" became not supported: Cannot connect to "192.168.254.31:161": Authentication failure (incorrect password, community or key).
 15527:20161227:161458.417 item "UPSR1:upsAdvBatteryCapacity" became not supported: Cannot connect to "192.168.254.31:161": Authentication failure (incorrect password, community or key).
 15526:20161227:161506.592 item "UPSR1:upsAdvOutputCurrent" became not supported: Cannot connect to "192.168.254.31:161": Authentication failure (incorrect password, community or key).
 15527:20161227:161528.382 item "UPSR1:upsAdvBatteryActualVoltage" became not supported: Cannot connect to "192.168.254.31:161": Authentication failure (incorrect password, community or key).
 15525:20161227:161531.531 item "UPSR1:upsAdvBatteryTemperature" became not supported: Cannot connect to "192.168.254.31:161": Authentication failure (incorrect password, community or key).
 15525:20161227:161537.631 item "UPSR1:upsAdvOutputFrequency" became not supported: Cannot connect to "192.168.254.31:161": Authentication failure (incorrect password, community or key).
 15527:20161227:161557.125 item "UPSR1:iemStatusProbeCurrentTemp" became not supported: Cannot connect to "192.168.254.31:161": Authentication failure (incorrect password, community or key).
 15525:20161227:161604.610 item "UPSR1:upsAdvInputLineVoltage" became not supported: Cannot connect to "192.168.254.31:161": Authentication failure (incorrect password, community or key).
 15527:20161227:161631.791 item "UPSR1:upsAdvBatteryRunTimeRemaining" became not supported: Cannot connect to "192.168.254.31:161": Authentication failure (incorrect password, community or key).

[akbar415]

it seems like it is - zabbix loosing connection to your device.
you need to check on device side first and maybe also increase Update interval on the item you have created.

This switch was previously monitored with snmp v 2c without problem.
I raised the update interval from 1 minute to 3 minutes and then to 5 minutes but the still the same issue.

[Pada]

Do you have the correct "Context name", "Security name", "Security level" and "Port" on all of your items?

What happens if you disable all but one of those SNMPv3 items?

I've had something similar with the JMX Agent when 2 of the 50 JMX items had a missing authentication value, and then it batched the queries and used the incorrectly configured item's values for the authentication parameters.

[batchenr]

Do you have the correct "Context name", "Security name", "Security level" and "Port" on all of your items?

What happens if you disable all but one of those SNMPv3 items?

I've had something similar with the JMX Agent when 2 of the 50 JMX items had a missing authentication value, and then it batched the queries and used the incorrectly configured item's values for the authentication parameters.

yes now that im remembering if i had some item not supported at a snmp device it has
caused this.
remove all unsupported items from this device at zabbix configuration.

[sfl]

Any update ?
same issue here with snmpv3 and zabbix 3.2.4

snmpwalk runs fine with -v 3 -a SHA -x AES

I have unchecked "use bulk request" to see if it is better ....

[DukeNukem3D]

Seems you are not alone, same behavior for different hosts, version 3.0.8

[DukeNukem3D]

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..

[syndeysider]

I have the same problem here... I've set the StartPollers=1 and the issue went away. This is interesting....

[aurelie]

Hello All,

I actually have the same issue on Zabbix 3.2.
(Random authentication failure on SNMP v3 items)
I changed the StartPoller to 1 and I no longer have "random authentication failure".

I have only 18 hosts on this proxy but I will need to strongly increase host number in the coming months.

How many items (or nvps) do you have with only 1 Poller before to get delay on zabbix polling.
Do you still have only 1 Poller? or is someone found an other solution.

Thanks,
Aurelie

[dave_it]

I've changed StartPoolers value to: 1. Hosts still get unsupported randomly How to get the host supported again? For me only solution is to remove host and add it one more time. This doesn't make any sense because I'm loosing all data, stats, graphs etc.

[sfl]

Hi all,

Same here with now ZBX 3.4.6 / Ubuntu 16.04.3 LTS with package version.
Setting StartPoller to 1 solve random authentication issue. Unfortunately one poller is not enough for polling all devices :-(

Is issue happening also on compiled zabbix binaries ?