Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements
Webcast-Catalyst9k
New Member

Reoccuring message %C4K_REDUNDANCY-5-CONFIGSYNC in logs

We keep getting this message which is filling up the logs every 60 mins.

What is it and what can I do about it?

Thanks

%C4K_REDUNDANCY-5-CONFIGSYNC: The calendar has been successfully synchronized to the standby supervisor

7 REPLIES

Re: Reoccuring message %C4K_REDUNDANCY-5-CONFIGSYNC in logs

%C4K_REDUNDANCY-5-CONFIGSYNC: The [chars] has been successfully synchronized to

the standby supervisor

Explanation The configuration has been successfully synchronized to the standby supervisor.

Recommended Action No action is required. This message is informational only.

http://www.cisco.com/en/US/docs/switches/lan/catalyst4500/12.2/37sg/system/messages/emsg.html#wp1387942

HTH

Narayan

New Member

Re: Reoccuring message %C4K_REDUNDANCY-5-CONFIGSYNC in logs

Thanks.

Why does it keep filling up the logs. Is it suppose to be doing this every 60 minutes and sending this message out?

Thanks

Re: Reoccuring message %C4K_REDUNDANCY-5-CONFIGSYNC in logs

Yes it does it every 60 minutes

The reason you are seeing this is because you have setup your logging level to greater than 5..

I dont know of a way to stop this message being generated. It would have been great if the IOS too had something like the PIX/ASA where u can use a particular ID and disable the logging

Narayan

New Member

Re: Reoccuring message %C4K_REDUNDANCY-5-CONFIGSYNC in logs

Thank you very much

Bronze

Re: Reoccuring message %C4K_REDUNDANCY-5-CONFIGSYNC in logs

Hi,

I hope this helps..

XXX(config)=logging trap errors/warnings....

BR

*aijaz*

New Member

Re: Reoccuring message %C4K_REDUNDANCY-5-CONFIGSYNC in logs

Please explain. I don't understand.

Thanks

Bronze

Re: Reoccuring message %C4K_REDUNDANCY-5-CONFIGSYNC in logs

Hi,

The command "logging trap warning" only logs the warning level messages to syslog server this way you wont get the informational level messages, including the message which you are getting every 60 min.

You can configure the trap with various levels.

(config)#logging trap ?

<0-7> Logging severity level

alerts Immediate action needed (severity=1)

critical Critical conditions (severity=2)

debugging Debugging messages (severity=7)

emergencies System is unusable (severity=0)

errors Error conditions (severity=3)

informational Informational messages (severity=6)

notifications Normal but significant conditions (severity=5)

warnings Warning conditions (severity=4)

I hope this clarifies.... Please rate all helpful posts above.

BR

*aijaz*

408
Views
0
Helpful
7
Replies
CreatePlease to create content