[ZBX-16416] We are seeing Holes in our Zabbix graphs when using SNMP v3 with AuthPriv both enabled. Created: 2019 Jul 25 Updated: 2019 Jul 31 Resolved: 2019 Jul 26 |
|
Status: | Closed |
Project: | ZABBIX BUGS AND ISSUES |
Component/s: | Server (S) |
Affects Version/s: | 4.0.9 |
Fix Version/s: | None |
Type: | Incident report | Priority: | Blocker |
Reporter: | Kshitij Sinha | Assignee: | Zabbix Support Team |
Resolution: | Fixed | Votes: | 0 |
Labels: | None | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified |
Attachments: | ZabbixGraphIssue.JPG ZabbixValuesIssue.JPG |
Description |
Hi, Issue Description: We are deploying a new tool for monitoring called Zabbix, when we deploy Zabbix server to monitor our network devices using SNMP v3 we get timeout getting data from the devices as seen in below logs: 13345:20190724:091038.222 SNMP agent item "system.cpu.utilv3c1[cpmCPUTotal5minRev.\{#SNMPINDEX}]" on host "XXXXX-XXXXX" failed: first network error, wait for 15 seconds 13314:20190724:091039.231 SNMP agent item "system.cpu.utilv3c1[cpmCPUTotal5minRev.\{#SNMPINDEX}]" on host "XXXXX-XXXXX" failed: first network error, wait for 15 seconds Cannot find module (BLUECOAT-SG-DISK-MIB): At line 0 in (none) 13310:20190724:091041.518 SNMP agent item "system.cpu.utilv3c1[cpmCPUTotal5minRev.\{#SNMPINDEX}]" on host "XXXXX-XXXXX" failed: first network error, wait for 15 seconds
As a result of these timeouts, we are unable to populate proper graphs with accurate data. We are using SNMP v3 with AuthPriv set up. When we change to SNMP v 2c or SNMP v3 with AuthNOpriv we do not encounter this issue.
We have increased the zabbix timeout in server.conf to maximum allowed value of 30 seconds. However, the issue still persists.
The device happens with various vendors including CISCO and Checkpoint.
We need a fix as this is as it is holding deployment and it seems like a bug or limitation at Zabbix code level.
|
Comments |
Comment by Edgars Melveris [ 2019 Jul 26 ] |
Hello Kshitij, I suggest to look at some of the already existing bug reports, in most cases this is a device/configuration issue. |
Comment by Edgars Melveris [ 2019 Jul 26 ] |
I'm currently closing the issue, feel free to reopen if you can provide additional information for problems on Zabbix side. |
Comment by Kshitij Sinha [ 2019 Jul 31 ] |
Hi Edgars, I checked the old bugs but they were all of old versions. If you can point me towards any specific bug ID's, I will be happy to check them out.
Thanks. |