ProfessorCustom Properties auto-resetting after Save?
I will probably open a support ticket and I hope this is just an ignorance thing on my part, but figured I'd check first.
A user reported a weird situation. They have a resource folder in which they have set a custom property (snmp.version) to be "v3". For some reason one of the devices in that folder is overriding that with a custom property where the value is set to "v2c". SO FAR NO PROBLEM.
But when we either change the custom property on the resource OR DELETE the custom property, as soon as we hit SAVE, the custom property is unchanged. We set snmp.version to v3 and LM immediately sets it to v2c. We delete the custom property, in hope the v3 value is inherited as it should be, but as soon as we hit save ... NO DICE. The value is just v2c anyway.
No matter how many times we go change this property (set directly) and edit it to be v2c, or delete it, as soon as we hit save, NOTHING. It the logs I see that I edited the device, but no details.
Is there some weird known scenario where this happens? I've never seen anything like it. And I have ENSURED that v2c is not set on any of the other static or dynamic folders that the resource is in.
Has anyone seen this before? I kind of feel silly honestly. I wanted to ask here before I bother support.
Hey Lewis_Beard
snmp.version is actually something that is set by the collector. It's a custom property as there are situations where you have to manually define it because a device does not respond to the typical snmp discovery process. However, in 99% of situations, snmp.version will be set by the collector and it's set with a value of the version that successfully responded during the collector autoprops process for a device.
This is described here in this doc:- On an individual device, snmp.version is automatically set by LogicMonitor to the version of SNMP which responds. LogicMonitor attempts SNMP communication initially with version 3, then 2c, and finally version 1. The highest responding version is set for this value, and any attempts to edit it will automatically revert.
- If you attempt to change the SNMP version after initial device addition (by entering new credentials), you must ensure it and the pertinent credentials function. If LogicMonitor is not able to communicate using the new version specified, it will automatically revert to the original version as a result of the failure.
