Information Necessary to perform Root Cause Analysis on Unity Failover
The Information needed to troubleshoot why a Unity server running versions 4.x, 5.x, and 7.x failed over:
Mandatory: Should be Included when Opening TAC SR Desired: Follow up Information that should be collected once Mandatory Information has been collected.
Unity failover normally occurs for a few possible reasons:
Call received on the secondary server
The secondary server loses communication with the primary server (primary does not respond for 30 seconds)
Failover is manually initiated using Failover Monitor
SQL replication failures
Slow MAPI interaction with exchange
Mandatory information to get:
GUSI Cab files from both servers. This will tell us why it failed over.
For full root cause analysis, the CCM and SDL Traces from all the nodes in the cluster are necessary.(if Unity is integrated with CM). Traces should span at least 30 minutes prior to the failure. Refer to this link for CM trace collection -
We have several Cisco TelePresence SX80 units with ceiling microphones that we use for interactive classes in our school.for the most most part they work great, but one issue we have is that the ceiling mics pick up every tittle sound that the studen...
Good afternoon-We have just installed a Vg-450. When we create a POTS line and add the config, it will not register until we reset the entire gateway. After that the port registers and functions correctly.Are we missing something? Steve McFarland
Hello All, I need to update the time of CUCM. We have a time mismatch with the recording server and advised to update the time of CUCM. I can see in OS administration that NTP is currently enabled. And I am getting a message Time cannot be set becaus...
I have several voice trunks, but I am having an issue with one of them. I will shut, no shut the voice-port and all is well for a couple hours to a day or more, but the trunk eventually disconnects seemingly random. Below is part ...