snmpGet snmpUsmMIB.usmMIBObjects.usmStats.usmStatsNotInTimeWindows random on hosts

[orch-bns]

Zabbix Server 4.4 (with Zabbix Proxy relay)

After communication interruption between Zabbix Proxy and Network Device (HPE VSR1000), SNMPv3 communication cannot be established anymore -> "timeout while connecting to <IP>:161"

245:20210122:123559.836 SNMP agent item "zabbix[host,snmp,available]" on host "9050937f1975418bac3c84de7d493b9e-vpe0" failed: first network error, wait for 15 seconds
264:20210122:123620.156 SNMP agent item "zabbix[host,snmp,available]" on host "9050937f1975418bac3c84de7d493b9e-vpe0" failed: another network error, wait for 15 seconds
261:20210122:123641.209 SNMP agent item "zabbix[host,snmp,available]" on host "9050937f1975418bac3c84de7d493b9e-vpe0" failed: another network error, wait for 15 seconds
251:20210122:123702.242 temporarily disabling SNMP agent checks on host "9050937f1975418bac3c84de7d493b9e-vpe0": host unavailable

This post gave me the 1st hint:https://support.zabbix.com/browse/ZBX-2152

Indeed setting random engineid does work:
snmp-agent local-engineid fa163e595345
snmp-agent usm-user v3 <USER> TELCOCLOUD simple authentication-mode sha <PW>

Problems:
-The engineid is unique already in the network (does get generated out of 1st Interface IP.
-No issues before the network interruption
-Workaround: stop/start Zabbix Proxy Docker does solve the "timeout issue" for all affected hosts on that Zabbix Proxy.

Does anybody have got a hint HOW to overcome that issue, without need to restart Zabbix Proxy? Thanks in advance

[orch-bns]

Issue is as described in:
https://www.zabbix.com/forum/search?q=snmpEngineTime
https://www.zabbix.com/forum/in-russian/16505-%D0%9D%D0%B5%D0%BA%D0%BE%D1%80%D1%80%D0%B5%D0%BA%D 1%82%D0%BD%D0%BE-%D1%80%D0%B0%D0%B1%D0%BE%D1%82%D0%B0%D0%B5%D1%82-snmpv3-%D0%B2%D0%BE%D0%B7%D0%BC%D0%BE%D0%B6%D0%BD%D0%BE-bag

Still the question -> how to get around it ??? Is that bug (randomly NOT handling RFC correct) fixed in Zabbix Version 5.x???

Workaround = restart docker proxy is kind of "not clean" as it can cause DB-Corruption (ProxyDB)!