Template and unsupported SNMP

Started by lweidig, July 22, 2012, 04:36:31 PM

Previous topic - Next topic

lweidig

We have created a template where one of the SNMP items in that template applies to the majority of the devices in the template, but some not.  We are trying to create the system as automatic as possible so we have created rules to assign templates to devices as discovered.  When one of the devices that does not support this SNMP item is discovered it kicks off an error:

Status of DCI 877 (SNMP: .1.3.6.1.4.1...) changed to UNSUPPORTED

This is fine, I would expect that during the initial application of the template.  We then go in and change this item to  Disabled, but leave it in there.

The problem comes in that if we go into the template to make any further changes, or even just to check things it seems to update some sort of flag and try to apply the template items again.  This causes all the nodes to once again process the unsupported message above and for us to clear them and set the item to disabled.

Maybe during the applying of templates it could check if the item exists for the node already and set to disabled.  If so, NOT fire this message as it has likely already been seen and handled. 

Victor Kirhenshtein

I can add this as configurable option. I don't have time to add this in 1.2.2, so I schedule this for 1.2.3 release.

Best regards,
Victor

Victor Kirhenshtein

Hi!

Finally implemented in 1.2.4. Now disabled DCI are not updated from template by default. The old behaviour can be enabled by setting server's configuration parameter ApplyDCIFromTemplateToDisabledDCI to 1.

Best regards,
Victor

lweidig