UnityConnection 8.6 VM issue + DB replication issue

[fei he]

Hi

We recent just rebuild and restore UnityConnection  Publisher completely. But issue start occurs - when call hit VM system,  user either hear dead air or disconnected straight way.

We stopped all the ports on publisher to take call, then call him VM with no issue. Any idea ?

Furthermore, we suspected that db replication status on publisher shows below:

+++++++++++++++++++++++++++++++++++++++++++++++++

admin:utils dbreplication runtimestate

DB and Replication Services: ALL RUNNING

Cluster Replication State: Replication status command started at: 2013-08-21-21-06

     Replication status command COMPLETED 541 tables checked out of 541

     No Errors or Mismatches found.

     Use 'file view activelog cm/trace/dbl/sdi/ReplicationStatus.2013_08_21_21_06_57.out' to see the details

DB Version: ccm8_6_2_21900_5

Number of replicated tables: 541

Cluster Detailed View from PUB (2 Servers):

                                PING            REPLICATION     REPL.   DBver&  REPL.   REPLICATION SETUP

SERVER-NAME     IP ADDRESS      (msec)  RPC?    STATUS          QUEUE   TABLES  LOOP?   (RTMT) & details

-----------     ------------    ------  ----    -----------     -----   ------- -----   -----------------

POL-CUC1        10.10.35.36     0.055   Yes     Connected       0       match   Yes     (2) PUB Setup Completed

PIB-CUC1        10.2.35.36      1.00    Yes     Connected       0       match   Yes     (2) Not Setup

+++++++++++++++++++++++++++++++++++++++++++++++++

As you can see, value are 2 but PIB-CUC1 show Not Setup.

Same command on subscriber show below

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

admin:utils dbreplication runtimestate

DB and Replication Services: ALL RUNNING

Cluster Replication State: Only available on the PUB

DB Version: ccm8_6_2_21900_5

Number of replicated tables: 541

Cluster Detailed View from SUB (2 Servers):

                                PING            REPLICATION     REPL.   DBver&  REPL.   REPLICATION SETUP

SERVER-NAME     IP ADDRESS      (msec)  RPC?    STATUS          QUEUE   TABLES  LOOP?   (RTMT)

-----------     ------------    ------  ----    -----------     -----   ------- -----   -----------------

POL-CUC1        10.10.35.36     0.997   Yes     Connected       0       match   Yes     (2)

PIB-CUC1        10.2.35.36      0.049   Yes     Connected       0       match   Yes     (2)

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Not sure whether db replication looks fine or not?

Whether this db replication cause VM stop working on publisher?

Regards

Fei

[davrojas · Accepted solution]

Hello Fei,

Based on the fact that you had to rebuilt the Publisher server i was wondering if you ran the folllowing command:

This command creates a clsuter relationship with the publisher server in a Connection cluster after the server was replaced or after Connection was reinstalled on the publisher server. The command overwrites all data on the publisher server with data from the subscriber server and initializes data replication between the servers.

COMMAND SYNTAX

utils cuc cluster renegotiate

USAGE GUIDELINES

Run this command on the subscriber server in a Connection cluster to set up a trust with a publisher server that has been replaced or on which Connection has been reinstalled.

This command can be referenced here:

http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/cli_ref/8_6_1/cli_ref_861.html

If the command above was used then you might want to consider:

Running  'utils dbreplication stop all' to stop the replication and 'utils dbreplication reset all' to tear down and rebuilt replication. The replication should be restored to normal after this.

For the calls being dropped it would be interesting if you could verify whether the ports registered on the CUCM were flapping.

Best Regards,

David Rojas Peck.

[fei he]

Hi David

Appreciate your response.

We did use command utils cuc cluster renegotiate on subscriber after finish rebuild publisher.

Also issue command utils dbreplication stop on sub and pub in order, then utils dbreplication reset all on pub and wait 30 mins and dbreplication status all good.

Regards

Fei