Communication attributes differ from parent alarms in CA SPECTRUM when setting the model type default flag

Products

• Spectrum
• Network Observability

Issue/Introduction

When setting the modeltype default for the attributes listed below, the attribute value either does not roll down to the apps/interfaces and/or the default value does not apply to any new models that are created:

EH_Map_Version (0x130be)            
TimeOut (0x110c4)      
TryCount (0x110c5)     
Agent_Port (0x10023)     
mdl_creat_method (0x12a73)     
mdl_creat_athr (0x11026)     
Community_Name (0x10024)     
Network_Address (0x12d7f)
Polling_Interval (0x10070)

Environment

Release: Any
Component:

Resolution

This is functioning as designed as the code has specific settings on these attributes to be able to perform properly.  When the attribute is changed on the device Spectrum rolls that value down to the interfaces to keep them in sync.  When the "Set As Default" is used on these SNMP Communication attributes, it breaks that functionality.

Therefore you should not use the "Set As Default" flag on these attributes in the Attribute Editor when changing the values of these attributes.

The workaround is to either manually search for and update the attributes on the models you need, or to use policy manager to apply the changes to a global collection containing the models.

If a user has changed the value and selected the Set As Default, to get the rollback function to work again, you need to change the value back to the default and use the "Set As Default".  For example, if the "Set As Default" polling_interval was changed to 600, to get the rollback function to work again, "Set As Default" to 300 (which is the OOB default).