Our customer got a problem on Unity, the following is the background:
2 x UM with manual failover
Problem: when customer maintenance their Exchange server, Pri Unity fail contact with Exchange and the TSP port become out of service then pass to Sec Unity, Sec Unity fail to take the call and logging report that cannot failover on this situation.
Attach PNG for reference.
Finally both Unity cannot take the message.
I would like to know if config to Active-Standy Unity with manual failover, this situation is normal? when Pri Unity lost connection with Exchange the TSP port will out of service and pass to Sec Unity? Any configuration and avoid it?
Re: Unity 7 with failover, but both failure on TSP
I've responded with answers in-line below.
I would like to know if config to Active-Standy Unity with manual failover, this situation is normal?
when Pri Unity lost connection with Exchange the TSP port will out of service and pass to Sec Unity?
Answer: In this case, the primary Unity server should have gone into UMR mode, meaning that it would continue to take calls and subscribers would have access only to the vmail message left while Unity was in UMR mode.
Any configuration and avoid it?
Answer: Manual failover will avoid automatic failover from the primary to the secondary.
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.