Unity server failed ...... but when !! FO running

Unanswered Question
Mar 24th, 2009


I've just been asked by one of our customers to make changes to a Class of Service on their Unity UM service. I could not get to the main web-address, so tried the FO server and got on no problem. When I looked at the FO monitor in Tools Depot I can only see local services and I can't ping the primary server. I'm going to have to get the customer to physically look at server, but I'm sure they'll ask when it failed.

The logs in Commserver are detailed, but I can't find any idea when the fail-over actually occurred.

Can anyone tell me how I can find the date/time when the fail-over occurred?

Many thanks


  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Rob Huffman Tue, 03/24/2009 - 07:16

Hi Chris,

I thought that this may be what you were looking for;

Determining the Cause of Failover or Failback from an Event ID

This section describes how to determine the cause of failover and failback based on the event IDs that appear in the Event log.

To Determine the Cause of Failover or Failback from an Event ID


Step 1 On the primary server, on the Windows Start menu, click Programs > Administrative Tools > Event Viewer.

Step 2 In the Tree pane on the left, click Application Log. The log appears in the right pane.

Step 3 Locate the entries that show CiscoUnity_NodeMgr in the Source column.

Step 4 For the entries, note the event IDs that appear in the Event column.

Step 5 On the secondary server, repeat Step 1 through Step 4.

Step 6 Use Table 3-2, which follows the procedure, to determine the cause of failover or failback.


Hope this helps and best of luck!


Tray Stoutmeyer Tue, 03/24/2009 - 09:26

What you are looking for on the secondary application logs/event viewer is a message that states a call came in on port x and Unity is configured to answer the call. This is exactly when the failover occured.



This Discussion