[cisco-voip] CUCM 6.1.1 replication - pub state is 3-bad

[Patrick Mowry]

Good day,

Short version: when a cluster reset and reinstalling a sub does not fix replication, what do you do next?

 A customer has a 6.1.1-3000-2 cluster of 6 servers that was installed in an environment with power issues. An initial symptom was newly created phone would show a dberror when registering to a subscriber, but could register to the pub just fine. Replication  state of all servers was 3. Powercycled the cluster, and then tried a clusterreset. The end result of this was the pub was still 3 and all subscribers 4. 

Last night I reinstalled one subscriber and this returned it's state to 3. Phones can register to this reinstalled server so I'm tempted to reinstall the others as well. But I don't expect it to be a proper fix. 

Any suggestions are appreciated,

-Patrick