Forum Discussion

Lewis_Beard's avatar
Lewis_Beard
Icon for Professor rankProfessor
30 days ago
Solved

Custom 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 the...
  • LMjosephBrett's avatar
    LMjosephBrett
    30 days ago

    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:

    https://www.logicmonitor.com/support/getting-started/advanced-logicmonitor-setup/defining-authentication-credentials#h-defining-snmp-credentials-and-properties

    • 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.
LMjosephBrett's avatar
LMjosephBrett
Icon for LM Conqueror rankLM Conqueror
30 days ago

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:

https://www.logicmonitor.com/support/getting-started/advanced-logicmonitor-setup/defining-authentication-credentials#h-defining-snmp-credentials-and-properties

  • 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.
Lewis_Beard's avatar
Lewis_Beard
Icon for Professor rankProfessor
30 days ago

So youre saying that the credentials that are set on the resource for v3 are incorrect, or not set up on the device, so its immediately testing and reverting? OK I'll check it out. Thanks