Reply

Policy Compliance Status Changed to Unknown.

Authority
Posts: 41
1854     0

Hi,

 

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.

 

Thanks,
Nick

It will go to Unknown when it knows the configuration has...

Adviser
Posts: 357
1855     0

 

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. 

Thanks John!

Authority
Posts: 41
1855     0

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?

Yes, you'll need to ask for

Adviser
Posts: 357
1855     0

Yes, you'll need to ask for an RFE.

Seems like the current behavior is correct

Expert
Posts: 262
1855     0

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.

Showing results for 
Search instead for 
Do you mean 

Recommended for You