[cisco-voip] Broken network connection in CUCM cluster

[Jason Aarons (US)]

It might.  Not sure what causes dbreplication to fail, it can fail without losing connectivity (not normal and not a frequent problem). Everything syncs with the Publisher.

You can run RTMT to monitor/alert when the database is out of sync, or manually run a utils dbreplication status from CLI or from GUI Unified Web Reporting run a Database Status Report.

From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Reto Gassmann
Sent: Tuesday, March 29, 2011 3:03 AM
To: cisco-voip at puck.nether.net
Subject: [cisco-voip] Broken network connection in CUCM cluster

Hello Group

We have a CUCM 7.1(3a) cluster with 8 servers in 2 server rooms. The phones are connected to two servers one in every server room.
What happens, when the server rooms lose connection for a few days (and the server 1,3,5,7 won't have connection to server 2,4,6,8) and then get connected again?

server room 1                  ||             server room 2

server 1 (First Node)                      server 2
server 3                                          server 4 (phones)
server 5 (phones)                           server 6
server 7                                          server 8

Will the databases resync?

Thanks for feedback
Reto


-----------------------------------------
Disclaimer:

This e-mail communication and any attachments may contain
confidential and privileged information and is for use by the
designated addressee(s) named above only.  If you are not the
intended addressee, you are hereby notified that you have received
this communication in error and that any use or reproduction of
this email or its contents is strictly prohibited and may be
unlawful.  If you have received this communication in error, please
notify us immediately by replying to this message and deleting it
from your computer. Thank you.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20110329/3a459941/attachment.html>