Database replication mismatch on CUCM cluster after upgrade
After Upgrading the CUCM from 184.108.40.20600 to 220.127.116.1100 the cluster database is not same on both servers. One more thing when trying to insert new phone or update any phone on the SUB node i got the following error:
"Reset Failed. java.sql.SQLException: No UPDATE permission"
Re: Database replication mismatch on CUCM cluster after upgrade
When you attempt the upgrade again, make sure that you verify the dbreplication status before you begin.
That way you can be sure that at least this shouldn't be a problem following the switchover.
Also, always switch the inactive partition on the Publisher following the upgrade before you switch the inactive partitions on the subscribers.
The show tech dbstateinfo cli command available in 5.1(3) should give a good indication of the dbstates, or alternative verify same through the RTMT database summary. Anything other than a status of 2 is cause for concern..
You have reached the Cisco Logistics Support Center.. To Check Status of
your RMA, visit Product Returns & Replacements (RMA). Need help? Contact
us by Phone or Email. North Americas Phone: 1800 553 2447 Option 4
Email: email@example.com Europe Phone: +3...
The short answer is that you don't.... That isn't entirely true while at
the same time it kind of is, but for the most part you don't configure
the softkeys. You enable or disable them via TCL. Here is the long
answer. Be sure to read the whole thing or e...
Topology: IP Phone > Switches > Microsoft NPS setup to forward 802.1x
proxy to > ISE 2.1 patch 3 Authentication: EAP-TLS using Cisco MIC SANs
Phone Models 802.1X support? 802.1x flavor Addtl Comment EAP-MD5 EAP-TLS
Cisco 3905 Y Y N Cisco 6911 Y Y N Cisco ...