01-02-2014 09:34 PM - edited 03-16-2019 09:05 PM
Hi,
I've got one subscriber in a cluster the pulisher and subscriber are connecting through MPLS.
After having some issue with MPLS link the subscriber lost connectivity to publisher.now the link is up.but subscriber can not replicate the database.
Things I've done:
1- ping sub to bub > successfull
2-ping pub to sub > Successfull
3- Sub > utils dbreplication stop
4- Pub > utils dbreplication stop
5: pub > utils dbreplication clusterreset
6: pub > utils dbreplication reset all.
7: network state on both nodes are up and diagnose passed
8: utils dbreplication runtimestate:
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
----------- ------------ ------ ---- ----------- ----- ------- ----- -----------------
05LXF5UC02 10.125.3.243 0.034 Yes Connected 0 match Yes (3) PUB
06LXF5UC02 10.125.98.243 14.6 No Off-Line N/A ? No (?) N/A
Can someone give some advise?
Thanks.
Solved! Go to Solution.
01-03-2014 01:05 AM
Hi Kamin,
Try the following steps:
>>utils dbreplication stop on the subscriber
>> once it is stopped on the subscriber then utils dbreplication stop on the publisher
>> wait for a few minutes for it to finish
>> utils dbreplication dropadmindb on the publisher
>> wait for it to finish
>> utils dbreplication dropadmindb on the subscriber
>> wait for a few minutes for it to finish
>>utils dbreplication reset all on the publisher
Manish
01-02-2014 11:13 PM
Hi Kamin,
The subscriber needs to be rebooted after you issued the clusterreset command from the Publisher. Please check the following link for more details
https://supportforums.cisco.com/docs/DOC-13672#List_of_steps
HTH
Manish
01-03-2014 12:28 AM
Hi Manish,
Thanks for response.
I've rebooted the subscriber and the result is as per bellow:
:utils dbreplication runtimestate
DB and Replication Services: ALL RUNNING
Cluster Replication State: Only available on the PUB
DB Version: ccm8_6_2_22900_9
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)
----------- ------------ ------ ---- ----------- ----- ------- ----- -----------------
05LXF5UC02 10.125.3.243 16.1 No Active-Dropped 1410240 ? No (?)
06LXF5UC02 10.125.98.243 0.027 Yes Connected 0 match Yes (3)
01-03-2014 01:05 AM
Hi Kamin,
Try the following steps:
>>utils dbreplication stop on the subscriber
>> once it is stopped on the subscriber then utils dbreplication stop on the publisher
>> wait for a few minutes for it to finish
>> utils dbreplication dropadmindb on the publisher
>> wait for it to finish
>> utils dbreplication dropadmindb on the subscriber
>> wait for a few minutes for it to finish
>>utils dbreplication reset all on the publisher
Manish
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide