Some old cisco devices, like 3640 routers for example, don't provide their 
startup config through SNMP. As a result, NCM stores an empty startup 
config, and each time the global sync task is run, we have an alarm on 
those devices because startup and running configs are different.

Any ideas how to avoid this alarm? Is there a way to create a new device 
family for those devices and avoid the startup/running alarm?

The other way I was thinking at was to make a event rule that would check 
the device type before displaying the alarm. But maybe there is a better 
way.



---
To unsubscribe from spectrum, send email to [email protected] with the body: 
unsubscribe spectrum [email protected]

Reply via email to