[cisco-voip] Unity Connection 10.5.2 Split Brain Recovery

Thomas LeMay thomaslemay at comcast.net
Wed Oct 28 13:33:08 EDT 2015


Hi, 

 

Questions: What is the best business practice for the type of NTP server to
use as the source: windows or some other operating system?

 

Thank you,

 

Tom

 

From: cisco-voip [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of
Aaron Banks
Sent: Wednesday, October 28, 2015 12:39 AM
To: Ryan Huff; cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Unity Connection 10.5.2 Split Brain Recovery

 

Thank you for all of that.  You know what it was - NTP.  I shut down the HA.
NTP was doing weird things on the primary node and I asked the customer if
the NTP server address he gave me was a windows server.  Bingo.  I changed
the NTP source, rebooted the primary, called voicemail and then powered on
the HA.

Lesson learned.

  _____  

From: ryanhuff at outlook.com
To: amichaelbanks at hotmail.com; cisco-voip at puck.nether.net
Subject: RE: [cisco-voip] Unity Connection 10.5.2 Split Brain Recovery
Date: Tue, 27 Oct 2015 17:25:47 +0000

1.) Shut down the HA node.

 

2.) Reboot the primary node

 

3.) Once the primary node is up, place a call into voicemail 

 

4.) Power the HA node back on

 

5.) Once HA is up, verify HA status.

 

 

 

Sent from my T-Mobile 4G LTE Device



-------- Original message --------
From: Aaron Banks 
Date:10/27/2015 12:35 PM (GMT-05:00) 
To: cisco-voip at puck.nether.net 
Subject: [cisco-voip] Unity Connection 10.5.2 Split Brain Recovery 



Has anyone seen/resolved a split brain recovery in Unity Connection 10.5.2?
The primary and secondary keep swapping back and forth every few minutes.  I
can ping and trace to each server.  I restarted the primary but that did not
resolve the issue.  In the RTMT system logs, the secondary sends an NTP
query to the primary the response is the primary is inaccessible or down.
I'm stumped.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20151028/5faf2e40/attachment.html>


More information about the cisco-voip mailing list