On 16.03.2012 14:04, John O'Mahony wrote: 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? > Sounds like a known bug to be fixed in H08. H. -- amasol Kundentag, 28. und 29. März 2012, Campus Neue Balan Hilmar Preuße amasol AG Senior Consultant Campus Neue Balan Tel +49 89 1894743-18 Claudius-Keller-Straße 3b Fax +49 89 1894743-99 D-81669 München eMail [email protected] http://www.amasol.de/ amasol Aktiengesellschaft für Informations- und Kommunikationstechnologie Aufsichtsrat: Prof. Dr. Stephan Kaiser (Vorsitzender) Vorstand: Wolfgang Bachmann, Stefan Deml, Thomas Dirsch, Frank Jahn Johann Maurer Amtsgericht München HRB 128327, Sitz der Gesellschaft München --- To unsubscribe from spectrum, send email to [email protected] with the body: unsubscribe spectrum [email protected]
