As always you've driven the centre. That's great !
After reconfiguring the message occurs
"%MARS_NETCLK-3-CLK_TRANS: Network clock source transitioned from priority 10 to priority 1"
And controllers are fine now :)
Could you please also explain the mechanism of the fix ?
As I've found in documentation, 'network-clock-select' just
prioritizes clock sources if there are more than one.
<< CITED BEGIN
When an active clock source fails, the system chooses the next lower priority clock source specified by this command. When a higher-priority clock becomes available, the system automatically reselects the higher-priority clock source.
<< CITED END
Thus it doesn't absolutelty clear for me what has been happened :)
Both routers have had the same source, and the problem has been solved only after I had prioritized theirs sources. Hm...
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...