Hi all,
we just published patch release 3.0.2292. It fixes issues broken NXSL function SNMPSet, potential heap corruption in GSM notification channel driver, and bug in database migration if target is TimescaleDB.
Best regards,
Victor
проблема по отправки смс осталась
Hi,
Have noticed some odd behaviour with SNMP proxying since V3
Nodes that are polled via a server with the agent acting as a proxy are exhibiting the following odd behaviour:
- SNMP Version randomly resets to V1 from configured value
- SNMP Community string will go blank if you set the Prevent automatic SNMP configuration changes, and any attempt to add a string fails.
- Nodes with SNMP enabled will frequently report SYS_SNMP_UNREACHABLE and then next poll interval will go back to normal.
From observations, the issue is worse for switches.
Cheers, Brett.
Hi,
we don't have other reports for such behavior, even for quite large deployments. Please turn on debug logging on proxy and server to level 6 and send part of the logs for period when one such issue experienced.
Best regards,
Victor
Quote from: Victor Kirhenshtein on September 27, 2019, 06:54:34 PM
Hi,
we don't have other reports for such behavior, even for quite large deployments. Please turn on debug logging on proxy and server to level 6 and send part of the logs for period when one such issue experienced.
Best regards,
Victor
Hi Victor,
Sorry for the delay.
Have had a close look and the issue seems to be with the SNMP Community string. I use custom community strings for each device type.
Nodes that are being proxied by the agent seem to randomly forget the manually configured string and default to using public as well as resting the SNMP Version to 1.
Any attempt to manually enter the correct string in the GUI results in a blank field and continued use of public string and version 1 protocol.
Oddly, doing a full configuration poll will restore the correct version and string in the GUI and normal SNMP polling continues until it "glitches" again.
When the polling "glitches" the node reports SYS_SNMP_UNREACHABLE.
When the polling "glitches" it also reports all configured SNMP DCI as unsupported as the SNMP version has been reset.
This seems to cycle with the configured polling interval of 60 seconds.
All nodes use SNMP V2c.
All nodes that are not proxied are not affected.
Network discovery is disabled and I do have all custom SNMP Community Strings defined.
Have logs, but would prefer to not post publicly.
Thanks, Brett.
Hi,
just sent you upload link for logs in PM. We will take a look at this when logs will be available.
Best regards,
Victor