02-02-2015 03:38 PM
I am just wondering what kind of conditions will change a policy status from known status (pass/warning/error/info) to 'unknown' status. We have several devices over satelite connection and hourly config collections may sometimes fail. We notice these devices are often to have 'unknown' status in their policy (Even though they had a configuration in Config Explorer Archive within past month days).
I am wondering if there is a way to make policy compliance check only the last known good configuration, regardless how old they are.
02-02-2015 04:26 PM
It will go to Unknown when it knows the configuration has changed (typically from SNMP for Cisco and Juniper devices), but it has not successfully collected a configuration file since the change.
I do not think there is any way to modify this behavior.
02-03-2015 10:13 AM
I think you answer our question.
Since there is not a way to change this behavior, I am going to assume to change this behavior will require we ask for a RFE?
02-12-2015 07:22 PM
To me, it seems like the current behavior is the accurate and desired one:
1) The ccmHistory values indicate that the config has been changed but
2) Config collection has not succeeded since then.
"Unknown" seems to fit that condition quite aptly.