Dans un cluster Cisco CUCM composé d’un publisher et de plusieurs subscribers, il arrive que la base de donnée répartie ne soit plus bien synchronisée entre les membres.
Il est critique de réaliser ce diagnostic au plus tôt : la procédure ci-dessous explique comment le réaliser.
Il faut tout d’abord se connecter sur le Publisher (dans notre cas c’est un serveur en version 8.0.3) en SSH et taper la commande utils dbreplication status
-------------------- utils dbreplication status --------------------
Replication status check is now running in background.
Use command 'utils dbreplication runtimestate' to check its progress
The final output will be in file cm/trace/dbl/sdi/ReplicationStatus.2012_01_19_08_31_26.out
Please use "file view activelog cm/trace/dbl/sdi/ReplicationStatus.2012_01_19_08_31_26.out " command to see the output
admin:
La vérification du bon statut de réplication prend du temps : le fichier de résultat ne doit pas être visionné immédiatement. Pour évaluer la progression de ce diagnostic, il faut utiliser la commande utils dbreplication runtimestate
DB and Replication Services: ALL RUNNING
Cluster Replication State: Replication status command started at: 2012-01-19-08-31
Replication status command in PROGRESS 421 tables checked out of 519
Processing Table: gatewaylayout
Use 'file view activelog cm/trace/dbl/sdi/ReplicationStatus.2012_01_19_08_31_26.out' to see the details
DB Version: ccm8_0_3_20000_2
Number of replicated tables: 519
Cluster Detailed View from PUB (4 Servers):
PING REPLICATION REPL. DBver& REPL. REPLICATION SETUP
SERVER-NAME IP ADDRESS (msec) RPC? STATUS QUEUE TABLES LOOP? (RTMT) & details
----------- ------------ ------ ---- ----------- ----- ------- ----- -----------------
PUB1 192.168.1.65 0.029 Yes Connected 0 match N/A (2) PUB Setup Completed
SUB1 192.168.1.66 0.183 Yes Connected 0 match N/A (2) Setup Completed
SUB2 192.168.1.67 4.37 Yes Connected 0 match N/A (2) Setup Completed
SUB3 192.168.1.77 3.78 Yes Connected 0 match N/A (2) Setup Completed
admin:
la ligne en gras « Replication status command in PROGRESS 421 tables checked out of 519 » permet de connaitre l’avancement.
La colonne « Replication Loop » peut contenir 3 valeurs :
- 1 : initializing
- 2 : ok
- 3 : failed
Une fois le process de statut terminé, on peut visualiser le statut définitif
DB and Replication Services: ALL RUNNING
Cluster Replication State: Replication status command started at: 2012-01-19-13-44
Replication status command COMPLETED 519 tables checked out of 519
No Errors or Mismatches found.
Use 'file view activelog cm/trace/dbl/sdi/ReplicationStatus.2012_01_19_13_44_12.out' to see the details
DB Version: ccm8_0_3_20000_2
Number of replicated tables: 519
Cluster Detailed View from PUB (4 Servers):
PING REPLICATION REPL. DBver& REPL. REPLICATION SETUP
SERVER-NAME IP ADDRESS (msec) RPC? STATUS QUEUE TABLES LOOP? (RTMT) & details
----------- ------------ ------ ---- ----------- ----- ------- ----- -----------------
PUB1 192.168.1.65 0.025 Yes Connected 0 match N/A (2) PUB Setup Completed
SUB1 192.168.1.181 Yes Connected 444 match N/A (2) Setup Completed
SUB2 192.168.1.67 1.11 Yes Connected 444 match N/A (2) Setup Completed
SUB3 192.168.1.77 1.11 Yes Connected 444 match N/A (2) Setup Completed
