Cisco Unity

Document ID: 26060

Contents

Introduction
Prerequisites
      Conventions
      Prerequisites
      Components Used
Configure the Cisco Unity Failover Wizard
      Step-by-Step Instructions
Verify the Result
Troubleshoot
      Error: Method LogonUser Returned [0x522]: A Required Privilege is Not Held by the Client
      Cisco Unity Failover Configuration Wizard Fails on the Secondary Server
NetPro Discussion Forums - Featured Conversations
Related Information

Introduction

This document describes how to configure the failover between Cisco Unity servers with the Unity Failover Wizard. This document is based on Cisco Unity 3.1.4. For more information on architecture, refer to Cisco Unity Failover Configuration and Administration Guide, Release 3.1.

Prerequisites

Conventions

For more information on document conventions, see the Cisco Technical Tips Conventions.

Prerequisites

Before you configure Cisco Unity failover, make sure that you meet the requirements mentioned in the Requirements for Cisco Unity Failover document.

Components Used

The information in this document is based on these software and hardware versions:

• Two Cisco Unity servers Version 3.1.4.

• The second Cisco Unity server must have "Failover Backup Server" set on the key in order to function as a secondary server.

• The IP address of the primary Cisco Unity server (Budweiser) is 10.48.79.89.

• The IP address of the secondary Cisco Unity server (Guinness) is 10.48.79.88.

• The IP address of the Exchange 2000 offbox (Harp) is 10.48.79.90.

• All three servers have been installed in the domain "dublinbrew.com."

The information presented in this document was created from devices in a specific lab environment. All the devices used in this document started with a cleared (default) configuration. If you work in a live network, ensure that you understand the potential impact of any command before you use it.

Configure the Cisco Unity Failover Wizard

Step-by-Step Instructions

These steps show how to properly use the Cisco Unity Failover Wizard to configure the failover between two Unity servers:

1. In Windows Explorer, browse to the directory in which Cisco Unity is installed. The default directory is C:\CommServer.

2. Double-click FailoverConfig.exe to start the Cisco Unity Failover Wizard. Click Next.

   

   1. Click Browse.

   2. Choose the name of the secondary server.

   3. Click OK.

      The IP address for the secondary server is filled in automatically. If the system runs Cisco Unity Version 3.1(3) or later, and you want the switch file for the chosen phone system to replicate with the Wizard, check the Copy switch files from primary server to secondary server check box.

      Note: The switch file is replicated only while the Cisco Unity Failover Wizard is used. If you choose a different phone system after you run the Wizard, the new switch file is not replicated to the secondary server. In addition, changes to the phone system settings are not replicated between the primary and secondary servers. If you change the phone system settings after you run the Cisco Unity Failover Wizard, you must change the values on both servers manually.

   

3. Browse to the account that owns the failover service. Input the password for this account.

   

4. Specify the same account on both the primary and the secondary servers, and then click the Configure button.

   The Wizard verifies the settings and configures failover on the primary server.

   

5. Watch the progress of the Wizard.

   Note: The Structured Query Language (SQL) replication is performed automatically by the Wizard within the Wizard configuration.

   

6. If the Wizard does not finish the configuration successfully, an error message explains why the Wizard failed.

   1. Exit the Wizard.

   2. Correct the problem.

   3. Click the Configure button again.

   

7. Click the Finish button to complete the installation.

   

8. Perform the same procedure on the secondary server. On this server, you will point to the primary server (Budweiser - 10.48.79.89). Once this is done, go to Start > Programs > Unity > Failover Monitor.

   The Failover Monitor window opens:

   

   Obtain this information from the Failover Monitor window:

   • The operation mode is enabled. This means that the failover is set to run automatically.

   • The partner servername is Guinness (secondary server).

   • The local status of this server is Running;Active.

   • The remote status of this server is Running;Inactive.

9. Click the Configure button on the Failover Monitor window to open the Failover Configuration window.

   

   Obtain this information from the Failover Configuration window:

   • The ping interval is 1000 ms. Pings are pushed to the other partner every second. These are health checks to see if the other partner is still "alive."

   • The number of missed pings before failover is 30. In this case, it would failover after 30 seconds if it missed 30 pings.

   • The file replication interval is 10 minutes.

   • Failback has been set to Manual.

   The primary server comes up (after the failover secondary server had taken over when the primary server initially went down). The failback can be scheduled now. This way, failback will attempt to contact the primary server automatically between the time range indicated in the Scheduled Failback area.

10. Click the Advanced button on the Failover Monitor window to open the Failover Advanced Options window.

    

    In the Failover Advanced Options window, you can either set the failover and failback to occur manually or disable it.

Verify the Result

This section provides information that you can use to confirm that your configuration works properly.

Once the failover has been activated on the primary server, both servers will go through these steps. This trace has been taken from the output view on the Failover Monitor window.

The primary server shows a Running-Active status, and the secondary server shows a Running-Inactive status in this example:

11:50:09 Local, AvCsMgr,Running-Active;AvDSAD,Active;
    AvDSGlobalCatalog,Active;AvUMRSyncSvr,Active;Miu,
    Active;Notifier,Active;Ruler,Active;Scheduler,Active;
11:50:09 Remote, AvCsMgr,Running-Inactive;AvDSAD,Inactive;
    AvDSGlobalCatalog,Inactive;AvUMRSyncSvr,Inactive;
    Miu,Inactive;Notifier,Inactive;Ruler,Inactive;Scheduler,Inactive;
11:50:10 Local, AvCsMgr,Running-Active;AvDSAD,Active;
    AvDSGlobalCatalog,Active;AvUMRSyncSvr,Active;Miu,Active;
    Notifier,Active;Ruler,Active;Scheduler,Active;

This example shows that the failover has been activated:

11:50:10 Failover, AvCsMgr

This example shows that the primary server has started to deactivate:

11:50:11 Local, AvCsMgr,Running-Starting Deactivation;
    AvDSAD,Active;AvDSGlobalCatalog,Active;AvUMRSyncSvr,Active;
    Miu,Active;Notifier,Active;Ruler,Active;
11:50:11 Remote, AvCsMgr,Running-Inactive;AvDSAD,Inactive;
    AvDSGlobalCatalog,Inactive;AvUMRSyncSvr,Inactive;Miu,Inactive;
    Notifier,Inactive;Ruler,Inactive;Scheduler,Inactive;

This example shows that the secondary server has started to activate:

11:50:16 Local, AvCsMgr,Running-Failback;AvDSAD,Failback;
    AvDSGlobalCatalog,Failback;AvUMRSyncSvr,Failback;Miu,Failback;
    Notifier,Failback;Ruler,Failback;Scheduler,Failback;
11:50:16 Remote, AvCsMgr,Running-Activating;AvDSAD,Inactive;
    AvDSGlobalCatalog,Inactive;AvUMRSyncSvr,Inactive;Miu,Inactive;
    Notifier,Inactive;Ruler,Inactive;Scheduler,Inactive;

11:50:22 Local, AvCsMgr,Running-Failback;AvDSAD,Failback;
    AvDSGlobalCatalog,Failback;AvUMRSyncSvr,Failback;Miu,Failback;
    Notifier,Failback;Ruler,Failback;Scheduler,Failback;

The secondary server now runs as the primary server, as shown in this example:

11:50:22 Remote, AvCsMgr,Running-Active;AvDSAD,Active;
    AvDSGlobalCatalog,Active;AvUMRSyncSvr,Active;Miu,Active;
    Notifier,Active;Ruler,Active;Scheduler,Active;

11:50:23 Local, AvCsMgr,Running-Completing Deactivation;
    AvDSAD,Inactive;AvDSGlobalCatalog,Failback;AvUMRSyncSvr,Failback;
    Miu,Failback;Notifier,Failback;Ruler,Failback;Scheduler,Failback;
11:50:23 Remote, AvCsMgr,Running-Active;AvDSAD,Active;
    AvDSGlobalCatalog,Active;AvUMRSyncSvr,Active;Miu,Active;
    Notifier,Active;Ruler,Active;Scheduler,Active;

11:50:27 Local, AvCsMgr,Running-Inactive;AvDSAD,Inactive;
    AvDSGlobalCatalog,Inactive;AvUMRSyncSvr,Inactive;Miu,Inactive;
    Notifier,Inactive;Ruler,Inactive;Scheduler,Inactive;
11:50:27 Remote, AvCsMgr,Running-Active;AvDSAD,Active;
    AvDSGlobalCatalog,Active;AvUMRSyncSvr,Active;Miu,Active;
    Notifier,Active;Ruler,Active;Scheduler,Active;

Troubleshoot

This section provides information that you can use to troubleshoot your configuration.

Error: Method LogonUser Returned [0x522]: A Required Privilege is Not Held by the Client

When you try to run failover configuration wizard on a Cisco unity primary server, it returns the error method logonUser returned [0x522]: A required privilege is not held by the client.

This happens because the login account does not have sufficient privileges. A UnityInstall account is required to run the failover configuration wizard. Log in with a UnityInstall account to solve this problem.

Cisco Unity Failover Configuration Wizard Fails on the Secondary Server

The Cisco Unity Failover Configuration Wizard ran successfully on the primary Unity server, but it failed when it ran on the secondary Unity server; this error message displayed: Cannot generate SSPI context.

This can happen due to the ServicePrincipalNames (SPN) issue between the primary and secondary unity servers. In order to resolve the SPN related issues, download setspn.exe from Microsoft and perform these procedures:

1. List the SPNs in both the unity server with the command setspn -L <servername> from the command prompt.

2. In order to delete any current SPN for the MSSQLSvc entry, type this at a command prompt: setspn -D “MSSQLSvc/<machine:port> <serviceaccountname>” <servername>

   Note: The string inside quotes must match exactly what is seen in the List from step 1. The quotes must be used around the string.

You require domain administrator rights to execute these commands. In order to remove that SPN, it is necessary to continue with the failover configuration.

For more information, refer to the Microsoft Knowledge Base Article 811889.

NetPro Discussion Forums - Featured Conversations

Related Information

• Cisco Unity Failover Configuration and Administration Guide, Release 3.1
• Voice Technology Support
• Voice and IP Communications Product Support
• Recommended: Troubleshooting Cisco IP Telephony
• Technical Support - Cisco Systems