Hi We have created a global collection and applied a NCM policy to that collection. When the policy is enabled then any devices within the GC that are non-compliant are alarmed against. However any subsequent devices in the GC that have their config changed to become non-compliant are not alarmed against. I have deliberately changed a device config to be non-compliant and initiated a config capture for that device, yet there is no alarm raised for the device. The only way to have the alarm raised is to disable and reenable the policy.
In the NCM manual it states "A policy is checked and compared every time a device's host configuration file is captured." This doesn't look like it is happening and there appears to be a bug. Has anyone else seen this? This is on Spectrum 9.2.1 Regards, John --- To unsubscribe from spectrum, send email to [email protected] with the body: unsubscribe spectrum [email protected]
