Setting SNMP to v1 on a Node which supports v2, followed by running a configuration poll will result in the node being reset to v2.
I understand this happening on a Full Configuration Poll, but a standard one should not be resetting this value.
An example issue we are facing due to this:
A server is running two separate SNMP agents on different ports. One supports v1 and v2, the other only v1 and v3. To be able to poll DCIs on different SNMP ports properly, we have to configure the system to be polled using v1 only, as that is what both agents support. However, after each configuration poll the node is reset to using v2 and the SNMP agent supporting v1 and v3 only no longer responds.
Migrated from track.radensolutions.com
- Original Issue: NX-1502
- Type: Bug
- State: Fixed
- Priority: Normal
- Subsystem: Server
- Created: 2018-09-04 06:13:49 UTC
- Updated: 2018-09-20 17:20:17 UTC
- Reporter: Roman Doerr (tursiops.1)
- Last Updated By: Victor Kirhenshtein (@2128506)
Setting SNMP to v1 on a Node which supports v2, followed by running a configuration poll will result in the node being reset to v2.
I understand this happening on a Full Configuration Poll, but a standard one should not be resetting this value.
An example issue we are facing due to this:
A server is running two separate SNMP agents on different ports. One supports v1 and v2, the other only v1 and v3. To be able to poll DCIs on different SNMP ports properly, we have to configure the system to be polled using v1 only, as that is what both agents support. However, after each configuration poll the node is reset to using v2 and the SNMP agent supporting v1 and v3 only no longer responds.
Migrated from track.radensolutions.com