Friday, July 22, 2011

Fixing Cisco Callmanager Replication

Cisco Callmanagers consistently have random problems with replication.  Here's what works for me.
  1.  Sacrifice a chicken and egg … never know what comes first
  2.  Ssh to your primary callmanager and your secondary callmanager
  3.  Run the following:  show perf query class "Number of Replicates Created and State of Replication"
  4.  If Replication state shows 2 on both, you should be good
  5.  If Replication state shows 3 on both, you’re jacked (proceed to step 7)
  6.  If Replication state shows 0 on either, it’s initializing … don’t jack with (proceed to step 7)
  7.  For simplicity, reboot any firewalls in between ... the cause is often either a firewall or access control list blocking traffic
  8.  Wait 10 minutes and continue to run:  show perf query class "Number of Replicates Created and State of Replication"
  9.  If the status changes to 2, you’re good
  10.  If the status doesn’t change to 2, run:  utils dbreplication reset all
  11.  Wait 10 minutes and continue to run:  show perf query class "Number of Replicates Created and State of Replication"
  12.  If this still doesn’t work, I don’t know


NOTE:  Don’t reboot the callmanagers unless the Replication state shows 2