[ZBXNEXT-3940] Provide a way to flush SNMP cache for a host or all hosts Created: 2017 Jun 14 Updated: 2023 Dec 20 Resolved: 2020 Mar 11 |
|
Status: | Closed |
Project: | ZABBIX FEATURE REQUESTS |
Component/s: | API (A), Frontend (F), Proxy (P), Server (S) |
Affects Version/s: | 3.0.9 |
Fix Version/s: | 5.0.0alpha3, 5.0 (plan) |
Type: | Change Request | Priority: | Trivial |
Reporter: | Raymond Kuiper | Assignee: | Marina Generalova (Inactive) |
Resolution: | Fixed | Votes: | 13 |
Labels: | cache, runtimecontrol, snmp, snmpv3 | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified |
Issue Links: |
|
||||||||||||||||||||
Team: | Team D | ||||||||||||||||||||
Sprint: | Sprint 61 (Feb 2020), Sprint 62 (Mar 2020) | ||||||||||||||||||||
Story Points: | 1 |
Description |
Zabbix caches some SNMP properties (engine time, engine boots, engine id) of a host when using SNMPv3 to enable RFC complaint communication with these hosts. Unfortunately, we seem to be running into some snmpEngineTime issues on some devices every once in a while (we've double checked to see there are no duplicate SNMPengineID's in this environment). The only current remedy we have if these issues occur, is to either reboot the device (which resets the engine time on the device and increments the engine boots counter), or we need to restart the Zabbix server proces (which clears the cache and is less of a problem normally). It would be great if we could flush the snmp cache for these problem devices (via GUI and API) or if we could clear all of the SNMP cache with a -R flag to zabbix_server and zabbix_proxy without having to restart the entire server. Relates to (amongst others): |
Comments |
Comment by Oleksii Zagorskyi [ 2017 Jun 14 ] |
My correction is - not Zabbix cashes, but the netsnmp library, used by zabbix daemon, does it. So it's sort of a "side effect". I think it should be not that hard to implement libnetsnmp's function "free_etimelist" calling to all poller* processes by zabbix's -R flag. |
Comment by Raymond Kuiper [ 2017 Jun 14 ] |
Thanks for the comment, zalex |
Comment by richlv [ 2017 Jun 14 ] |
some time ago there was a discussion on whether zabbix could detect/suspect these problems happening and try flushing the cache. |
Comment by Raymond Kuiper [ 2017 Jun 14 ] |
I would be happy to be able to manually remedy the issue. I might even be able to use a Zabbix action to remedy it if I can do it on a per host basis via the API |
Comment by Oleksii Zagorskyi [ 2018 Apr 20 ] |
|
Comment by Sandro G. [ 2018 Jun 21 ] |
@Oleksiy Zagorskyi Background: I would like to use the net-snmp function (free_etimelist) to restore the correct SNMPv3 query when restarting the switches without restarting the entire Zabbix proxy each time. I hope you or someone who has already used the function can help me.
|
Comment by Oleksii Zagorskyi [ 2018 Jun 22 ] |
I did not and probably anyone else did not try to write such patch for zabbix_server. |
Comment by Vitaly Zhuravlev [ 2019 Jan 11 ] |
If I got it right, that should be fixed by automatically flushing the cache when such parameters are changed. No new buttons. zalex_ua No, automatic is not the best way. And changed items config is not the only case when flushing snmp cache is needed. I'd prefer to go with an option to flush it manually on demand. vzhuravlev: why it's not the best way? zalex_ua could you fill up criteria how to detect when the automatic flushing should be performed? vzhuravlev: Changing items. What else? You said there is more. zalex_ua Also because of a set of use cases described in And the question - is it possible to detect such conditions from the library response? From discussion with wiper in the So, I'd prefer to have an option to flush the cache manually anyway. |
Comment by Alexei Vladishev [ 2020 Jan 24 ] |
Manual flushing of SNMP cache is included into Zabbix 5.0 roadmap. If everything goes fine it will be implemented and available very soon, stay tuned. |
Comment by Artjoms Rimdjonoks [ 2020 Feb 27 ] |
Available in versions:
|
Comment by Marina Generalova (Inactive) [ 2020 Mar 02 ] |
Documentation updated: |
Comment by Oleksii Zagorskyi [ 2020 Mar 04 ] |
THANK YOU ALL for this new feature in zabbix !!! |
Comment by Raymond Kuiper [ 2020 Mar 05 ] |
Very happy this has finally made it's way into Zabbix, thank you! |