update archive vs configuation compare 1

[Cephus]

Has anyone noticed that when you do an update archive the result is " succeeded with the current date and time"

But if you pull up a compare configurations, at the top you will get a different date and time stamp. This apprears to be caused because the system will pull the last archive that registered a change. This can cause confusion..

Has anyone else run across this? Why don't the containers syc?

Thanks for any comments and suggestions..

Cephus
Cephus4@home.com

 

[prisoner]

There are a couple reasons for what you are seeing. First, if you have your CiscoWorks server configured to update the archive automatically and no changes have been made to the devices since the last automatic archive, then you will see this symtom. Second, if you have enabled your CiscoWorks server to listen to Syslog messages for a configuration change, then the archive is automatically updated. The bottom line is the archive request will only update the archive if there has been a change to the configuation files since the last update. Disregard the date you see when requesting an update and go with the timestamp shown on the configuration file when you view in from CiscoWorks.

Cheers,
Prisoner and firefighter to supporting IBM customers

 

[mhq]

I am trying to solve a problem within the Monitoring systems. For some reason an ..error.. message get
sent to the /var/adm/message instead of the /var/log/nco
even though, I have config the syslog.conf with,

# All message levels from all logging facilities will go
# to this file
*.debug /var/log/nco