[cisco-voip] Unity 7 failover issues

[Pat Hayes]

Sounds like you have two different problems.

For the failovers, look at the application event log on the secondary
server. Every time there is a failover the reason for it will be
logged there. Typical reasons include losing connectivity to the
primary Unity server and calls being presented/forwarded to the
secondary server. If this has had problems since day one, take an
extra careful look at your port and line group configuration. Also
ensure that no CSS can reach the secondary's ports directly.

For EMS, since the problems began does it work at all? Has the system
been rebooted at all since then? Are you running the latest version
from CiscoUnityTools.com (1.3.13)? If it only fails some of the time,
you might want to check the EMS log file to see if it is reporting any
connectivity or similar problems.

-Pat

On Mon, Oct 4, 2010 at 12:03 PM, Faye Day <fday at wilson-co.com> wrote:
> Hey Guys,
>
>
>
> Running Unity 7.0(2) with Exchange. Two servers, primary and secondary,
> setup for failover. Primary server will spontaneously/randomly failover to
> the secondary. Can’t figure out why it’s doing this. When I try to use
> failback on the secondary, the process runs, secondary becomes inactive,
> then the process immediately begins again and runs thru until the secondary
> is again in control. I’m having to reboot the primary a couple times a week
> to force the failback so I can work.
>
>
>
> Also, I only find out that the failover has happened when I try to login for
> admin tasks on the primary and can’t do anything, because the notifications
> aren’t working right either. All notifications are setup properly in EMS
> admin – email, voice mail, syslog – but they are not working correctly
> either. Sometimes my syslog receives the notification, sometimes if I try a
> test message I get an email, but the voice mail notification won’t work at
> all. All these notifications had been working but just stopped some time
> ago. Nothing has changed, no updates, etc.
>
>
>
> Any suggestions would be greatly appreciated. I’ve combed CCO, googled,
> posted to tech net, etc, and my first line support has been lackluster to
> say the least. Their advice has been to stop unity on the secondary. If I do
> that, when I restart it after the primary becomes primary again (it is after
> all supposed to be running on both – for failover), the failover process
> just starts up again – not every time but sometimes.
>
>
>
> Ideas?
>
>
>
> Thanks,
>
>
>
> Faye Day
>
>
>
> Wilson County Technology Services
>
> Assistant Director
>
> (252) 206-1024
>
> (252) 265-5960 fax
>
>
>
> Opinions in this message may not represent the policy of Wilson County.
> Email correspondence to and from me, in connection with the transaction of
> public business, is subject to the North Carolina Public Records Law and may
> be disclosed to third parties.
>
>
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>