Table Of Contents
Behavior of Cisco Unity Failover During Outages of Networked Components
Introduction
Outage Scenarios for Networks of Windows 2000 and Exchange 2000
The Primary Server Is Disconnected from the Network, Then Reconnected
The Secondary Server Is Disconnected from the Network, Then Reconnected
The Primary and Secondary Servers Are Simultaneously Disconnected from the Network, Then the Primary Server Is Reconnected First
The Primary and Secondary Servers Are Simultaneously Disconnected from the Network, Then the Secondary Server Is Reconnected First
The Primary and Secondary Servers Are Simultaneously Disconnected from the Network, Then Both Servers Are Simultaneously Reconnected
The Exchange 2000 Server That Has the Cisco Unity Messaging System Mailbox Is Disconnected from the Network, Then Reconnected
The Exchange 2000 Server That Has the Cisco Unity Messaging System Mailbox Is Disconnected from the Network, Then the Primary and Secondary Servers Are Restarted
The Exchange 5.5 Server in a Mixed-Messaging Environment Is Disconnected from the Network, Then Reconnected
The Exchange 2000 Server That Does Not Have the Cisco Unity Messaging System Mailbox Is Disconnected from the Network, Then Reconnected
The Publisher Cisco CallManager Server Is Disconnected from the Network, Then Reconnected
The Subscriber Cisco CallManager Server Is Disconnected from the Network, Then Reconnected
The Cisco CallManager Cluster Is Disconnected from the Network, Then Reconnected
The Domain Controller That Cisco Unity Is Connected to Is Disconnected from the Network, Then Reconnected
An Additional Domain Controller That Cisco Unity Is Not Connected to Is Disconnected from the Network, Then Reconnected
The Global Catalog Server That Cisco Unity Is Connected to Is Disconnected from the Network, Then Reconnected
The Global Catalog Server That Cisco Unity Is Not Connected to Is Disconnected from the Network, Then Reconnected
The Primary Server Crashes
The Secondary Server Crashes
The Primary and Secondary Servers Crash Simultaneously
The Primary Server Is Disconnected from the Network, Then the Exchange 2000 Server That Has the Cisco Unity Messaging System Mailbox Is Disconnected from the Network
The Exchange 2000 Server That Has the Cisco Unity Messaging System Mailbox Is Disconnected from the Network, Then the Primary Server Is Disconnected from the Network
The Exchange 2000 Server That Has the Cisco Unity Messaging System Mailbox and the Primary Server Simultaneously Crash, Then Are Reconnected
Outage Scenarios for Networks of Windows NT and Exchange 5.5
The Primary Server Is Disconnected from the Network, Then Reconnected
The Secondary Server Is Disconnected from the Network, Then Reconnected
The Primary and Secondary Servers Are Simultaneously Disconnected from the Network, Then the Primary Server Is Reconnected First
The Primary and Secondary Servers Are Simultaneously Disconnected from the Network, Then the Secondary Server Is Reconnected First
The Primary and Secondary Servers Are Simultaneously Disconnected from the Network, Then Both Servers Are Simultaneously Reconnected
The Exchange 5.5 Server That Has the Cisco Unity Messaging System Mailbox Is Disconnected from the Network, Then Reconnected
The Exchange 5.5 Server That Has the Cisco Unity Messaging System Mailbox Is Disconnected from the Network, Then the Primary and Secondary Servers Are Restarted
The Exchange 5.5 Server That Does Not Have the Cisco Unity Messaging System Mailbox Is Disconnected from the Network, Then Reconnected
The Publisher Cisco CallManager Server Is Disconnected from the Network, Then Reconnected
The Subscriber Cisco CallManager Server Is Disconnected from the Network, Then Reconnected
The Cisco CallManager Cluster Is Disconnected from the Network, Then Reconnected
The Primary Domain Controller Is Disconnected from the Network, Then Reconnected
The Backup Domain Controller Is Disconnected from the Network, Then Reconnected
The Primary Domain Controller and Backup Domain Controller Are Disconnected from the Network, Then Reconnected
The Primary Domain Controller Is Disconnected from the Network, Then the Primary and Secondary Servers Are Restarted
The Primary Domain Controller and Backup Domain Controller Are Disconnected from the Network, Then the Primary and Secondary Servers Are Restarted
The Primary Server Crashes
The Secondary Server Crashes
The Primary and Secondary Servers Crash Simultaneously
The Primary Server Is Disconnected from the Network, Then the Exchange 5.5 Server That Has the Cisco Unity Messaging System Mailbox Is Disconnected from the Network
The Exchange 5.5 Server That Has the Cisco Unity Messaging System Mailbox Is Disconnected from the Network, Then the Primary Server Is Disconnected from the Network
The Exchange 5.5 Server That Has the Cisco Unity Messaging System Mailbox and the Primary Server Simultaneously Crash, Then Are Reconnected
Restarting UnityDb Database Replication and Configuring the Distribution Agent Schedule
Behavior of Cisco Unity Failover During Outages of Networked Components
This chapter contains the following sections:
•
Introduction
•Outage Scenarios for Networks of Windows 2000 and Exchange 2000
•Outage Scenarios for Networks of Windows NT and Exchange 5.5
•Restarting UnityDb Database Replication and Configuring the Distribution Agent Schedule
Introduction
The sections in this chapter describe how the primary and secondary servers behave when the components that Cisco Unity uses over the network are disconnected (for example, due to a partial or complete network outage).
The scenarios described cover the range of probable component or network outages. Each scenario assumes the following before the outage occurs:
•Cisco Unity is running on both the primary and secondary servers.
•The primary server is active, and the secondary server is inactive.
•The phone system that Cisco Unity connects to is Cisco CallManager.
Except when Cisco Unity is shut down, all Cisco Unity services continue to run, though the functionality of certain services are affected by the outages.
Outage Scenarios for Networks of Windows 2000 and Exchange 2000
This section contains the following scenarios:
•The Primary Server Is Disconnected from the Network, Then Reconnected
•The Secondary Server Is Disconnected from the Network, Then Reconnected
•The Primary and Secondary Servers Are Simultaneously Disconnected from the Network, Then the Primary Server Is Reconnected First
•The Primary and Secondary Servers Are Simultaneously Disconnected from the Network, Then the Secondary Server Is Reconnected First
•The Primary and Secondary Servers Are Simultaneously Disconnected from the Network, Then Both Servers Are Simultaneously Reconnected
•The Exchange 2000 Server That Has the Cisco Unity Messaging System Mailbox Is Disconnected from the Network, Then Reconnected
•The Exchange 2000 Server That Has the Cisco Unity Messaging System Mailbox Is Disconnected from the Network, Then the Primary and Secondary Servers Are Restarted
•The Exchange 5.5 Server in a Mixed-Messaging Environment Is Disconnected from the Network, Then Reconnected
•The Exchange 2000 Server That Does Not Have the Cisco Unity Messaging System Mailbox Is Disconnected from the Network, Then Reconnected
•The Publisher Cisco CallManager Server Is Disconnected from the Network, Then Reconnected
•The Subscriber Cisco CallManager Server Is Disconnected from the Network, Then Reconnected
•The Cisco CallManager Cluster Is Disconnected from the Network, Then Reconnected
•The Domain Controller That Cisco Unity Is Connected to Is Disconnected from the Network, Then Reconnected
•An Additional Domain Controller That Cisco Unity Is Not Connected to Is Disconnected from the Network, Then Reconnected
•The Global Catalog Server That Cisco Unity Is Connected to Is Disconnected from the Network, Then Reconnected
•The Global Catalog Server That Cisco Unity Is Not Connected to Is Disconnected from the Network, Then Reconnected
•The Primary Server Crashes
•The Secondary Server Crashes
•The Primary and Secondary Servers Crash Simultaneously
•The Primary Server Is Disconnected from the Network, Then the Exchange 2000 Server That Has the Cisco Unity Messaging System Mailbox Is Disconnected from the Network
•The Exchange 2000 Server That Has the Cisco Unity Messaging System Mailbox Is Disconnected from the Network, Then the Primary Server Is Disconnected from the Network
•The Exchange 2000 Server That Has the Cisco Unity Messaging System Mailbox and the Primary Server Simultaneously Crash, Then Are Reconnected
The Primary Server Is Disconnected from the Network, Then Reconnected
In testing, this scenario was simulated by disabling the network interface card on the primary server.
Disconnection Behavior
•The secondary server answers all calls.
•Subscribers are able to leave and listen to messages. External callers can leave messages for subscribers.
•All voice messaging ports on the primary server unregister with the Cisco CallManager server.
•The Node Manager services (AvCsNodeMgr.exe) on the primary and secondary servers no longer receive status from each other.
•The Failover Monitor on the primary server shows that the primary server is active. The Failover Monitor on the secondary server shows that the secondary server is active.
•Messages, greetings, and other recordings made on the primary server but not replicated to the secondary server before the network outage are not available on the secondary server.
•The Replication Monitor in the SQL Enterprise Manager displays errors.
•UnityDb database replication between the primary and secondary servers stops.
•The secondary server handles directory synchronization, MWIs, event notification, and message notification.
Reconnection Behavior
•The primary server becomes active, and the secondary server becomes inactive.
•All voice messaging ports on the primary server register with the Cisco CallManager server.
•The primary server answers all calls.
•Subscribers are able to leave and listen to messages. External callers can leave messages for subscribers.
•The Node Manager services (AvCsNodeMgr.exe) on the primary and secondary servers send status to and receive status from each other.
•The Failover Monitors on the primary and secondary servers show that the primary server is active.
•Changes to the UnityDb database that occurred while the primary server was offline are replicated from the secondary server to the primary server.
•The primary server handles directory synchronization, MWIs, event notification, and message notification.
•Messages, greetings, and other recordings made on the primary server but not replicated to the secondary server before the network outage are replicated to the secondary server.
•Messages, greetings, and other recordings made on the secondary server during the network outage are replicated to the primary server.
•For Cisco Unity 3.1(3) and earlier, if the network outage lasted more than five minutes, the Distribution agent on the primary server may need to be manually started to resume UnityDb database replication when the primary server becomes active again. See the "Restarting UnityDb Database Replication and Configuring the Distribution Agent Schedule" section.
The Secondary Server Is Disconnected from the Network, Then Reconnected
In testing, this scenario was simulated by disabling the network interface card on the secondary server.
Disconnection Behavior
•The primary server continues answering all calls.
•Subscribers are able to leave and listen to messages. External callers can leave messages for subscribers.
•All voice messaging ports on the secondary server unregister with the Cisco CallManager server.
•The Node Manager services (AvCsNodeMgr.exe) on the primary and secondary servers no longer receive status from each other.
•The Failover Monitor on the primary server shows that the primary server is active. The Failover Monitor on the secondary server shows that the secondary server is active.
•The Replication Monitor in the SQL Enterprise Manager displays errors.
•UnityDb database replication between the primary and secondary servers stops.
•The primary server handles directory synchronization, MWIs, event notification, and message notification.
Reconnection Behavior
•The primary server remains active, and the secondary server becomes inactive.
•The primary server continues answering all calls.
•Subscribers are able to leave and listen to messages. External callers can leave messages for subscribers.
•All voice messaging ports on the secondary server register with the Cisco CallManager server.
•The Node Manager services (AvCsNodeMgr.exe) on the primary and secondary servers send status to and receive status from each other.
•The Failover Monitors on the primary and secondary servers show that the primary server is active.
•Changes to the UnityDb database that occurred while the secondary server was offline are replicated from the primary server to the secondary server.
•The primary server continues handling directory synchronization, MWIs, event notification, and message notification.
•Messages, greetings, and other recordings made on the primary server but not replicated to the secondary server before the network outage are replicated to the secondary server.
•Messages, greetings, and other recordings made on the primary server during the network outage are replicated to the secondary server.
•For Cisco Unity 3.1(3) and earlier, if the network outage lasted more than five minutes, the Distribution agent on the primary server may need to be manually started to resume UnityDb database replication when the primary server becomes active again. See the "Restarting UnityDb Database Replication and Configuring the Distribution Agent Schedule" section.
The Primary and Secondary Servers Are Simultaneously Disconnected from the Network, Then the Primary Server Is Reconnected First
In testing, this scenario was simulated by disabling the network interface card on the primary and secondary servers at the same time.
Disconnection Behavior
•There is no voice messaging functionality. Neither the primary nor secondary server answers calls.
•Subscribers are not able to leave or listen to messages. External callers cannot leave messages for subscribers.
•Callers trying to leave messages hear a fast busy tone instead of the personal greeting for the subscriber.
•All voice messaging ports on the primary and secondary servers unregister with the Cisco CallManager server.
•The Node Manager services (AvCsNodeMgr.exe) on the primary and secondary servers no longer receive status from each other.
•The Failover Monitor on the primary server shows that the primary server is active. The Failover Monitor on the secondary server shows that the secondary server is active.
•Subscribers can call other subscribers directly and talk to each other.
•The Replication Monitor in the SQL Enterprise Manager displays errors.
•UnityDb database replication between the primary and secondary servers stops.
•Neither server initiates directory synchronization, MWIs, event notification, or message notification.
Reconnection Behavior (Only the Primary Server Is Reconnected)
•The Failover Monitor on the primary server shows that the primary server is active. The Failover Monitor on the secondary server shows that the secondary server is active.
•All voice messaging ports on the primary server register with the Cisco CallManager server.
•The primary server answers all calls.
•Subscribers are able to leave and listen to messages. External callers can leave messages for subscribers.
•Messages, greetings, and other recordings made on the primary server but not replicated to the secondary server before the network outage are not replicated to the secondary server because it is offline.
•Changes to the UnityDb database that occurred before the network outage and were not replicated to the secondary server are not replicated because the secondary server is offline.
•The primary server handles directory synchronization, MWIs, event notification, and message notification.
Reconnection Behavior (the Secondary Server Is Also Reconnected)
•The Failover Monitors on the primary and secondary servers show that the primary server is active and the secondary server is inactive.
•All voice messaging ports on the secondary server register with the Cisco CallManager server.
•The primary server continues answering all calls.
•The Node Manager services (AvCsNodeMgr.exe) on the primary and secondary servers send status to and receive status from each other.
•Changes to the UnityDb database that occurred while the secondary server was offline are replicated from the primary server to the secondary server.
•For Cisco Unity 3.1(3) and earlier, if the network outage lasted more than five minutes, the Distribution agent on the primary server may need to be manually started to resume UnityDb database replication when the network outage is resolved. See the "Restarting UnityDb Database Replication and Configuring the Distribution Agent Schedule" section.
•The primary server continues handling directory synchronization, MWIs, event notification, and message notification.
•Messages, greetings, and other recordings made on the primary server but not replicated to the secondary server before the network outage are replicated to the secondary server.
•Messages, greetings, and other recordings made on the primary server while the secondary server was offline are replicated to the secondary server.
The Primary and Secondary Servers Are Simultaneously Disconnected from the Network, Then the Secondary Server Is Reconnected First
In testing, this scenario was simulated by disabling the network interface card on the primary and secondary servers at the same time.
Disconnection Behavior
•There is no voice messaging functionality. Neither the primary nor secondary server answers calls.
•Subscribers are not able to leave or listen to messages. External callers cannot leave messages for subscribers.
•Callers trying to leave messages hear a fast busy tone instead of the personal greeting for the subscriber.
•All voice messaging ports on the primary and secondary servers unregister with the Cisco CallManager server.
•The Node Manager services (AvCsNodeMgr.exe) on the primary and secondary servers no longer receive status from each other.
•The Failover Monitor on the primary server shows that the primary server is active. The Failover Monitor on the secondary server shows that the secondary server is active.
•Subscribers can call other subscribers directly and talk to each other.
•The Replication Monitor in the SQL Enterprise Manager displays errors.
•UnityDb database replication between the primary and secondary servers stops.
•Neither server initiates directory synchronization, MWIs, event notification, or message notification.
Reconnection Behavior (Only the Secondary Server Is Reconnected)
•The Failover Monitor on the primary server shows that the primary server is active. The Failover Monitor on the secondary server shows that the secondary server is active.
•All voice messaging ports on the secondary server register with the Cisco CallManager server.
•The secondary server answers all calls.
•Subscribers are able to leave and listen to messages. External callers can leave messages for subscribers.
•Messages, greetings, and other recordings made on the primary server but not replicated to the secondary server before the network outage are not replicated to the secondary server because the primary server is offline.
•Messages, greetings, and other recordings made on the secondary server during the network outage are not replicated to the primary server because the primary server is offline.
•Changes to the UnityDb database that occurred before the network outage and were not replicated to the secondary server are not replicated because the primary server is offline.
•The secondary server handles directory synchronization, MWIs, event notification, and message notification.
Reconnection Behavior (the Primary Server Is Also Reconnected)
•The primary server becomes, active and the secondary server becomes inactive.
•All voice messaging ports on the primary server register with the Cisco CallManager server.
•The primary server answers all calls.
•The Node Manager services (AvCsNodeMgr.exe) on the primary and secondary servers send status to and receive status from each other.
•The Failover Monitors on the primary and secondary servers show that the primary server is active and the secondary server is inactive.
•Changes to the UnityDb database that occurred while the primary server was offline are replicated from the secondary server to the primary server.
•For Cisco Unity 3.1(3) and earlier, if the network outage lasted more than five minutes, the Distribution agent on the primary server may need to be manually started to resume UnityDb database replication when the network outage is resolved. See the "Restarting UnityDb Database Replication and Configuring the Distribution Agent Schedule" section.
•The primary server handles directory synchronization, MWIs, event notification, and message notification.
•Messages, greetings, and other recordings made on the primary server but not replicated to the secondary server before the network outage are replicated to the secondary server.
•Messages, greetings, and other recordings made on the secondary server while the primary server was offline are replicated to the primary server.
The Primary and Secondary Servers Are Simultaneously Disconnected from the Network, Then Both Servers Are Simultaneously Reconnected
In testing, this scenario was simulated by disabling the network interface card on the primary and secondary servers at the same time.
Disconnection Behavior
•There is no voice messaging functionality. Neither the primary nor secondary server answers calls.
•Subscribers are not able to leave or listen to messages. External callers cannot leave messages for subscribers.
•Callers trying to leave messages hear a fast busy tone instead of the personal greeting for the subscriber.
•All voice messaging ports on the primary and secondary servers unregister with the Cisco CallManager server.
•The Node Manager services (AvCsNodeMgr.exe) on the primary and secondary servers no longer receive status from each other.
•The Failover Monitor on the primary server shows that the primary server is active. The Failover Monitor on the secondary server shows that the secondary server is active.
•Subscribers can call other subscribers directly and talk to each other.
•The Replication Monitor in the SQL Enterprise Manager displays errors.
•UnityDb database replication between the primary and secondary servers stops.
•Neither server initiates directory synchronization, MWIs, event notification, or message notification.
Reconnection Behavior
•The primary server remains active, and the secondary server becomes inactive.
•All voice messaging ports on the primary and secondary servers register with the Cisco CallManager server.
•The primary server answers all calls.
•Subscribers are able to leave and listen to messages. External callers can leave messages for subscribers.
•The Node Manager services (AvCsNodeMgr.exe) on the primary and secondary servers send status to and receive status from each other.
•The Failover Monitors on the primary and secondary servers show that the primary server is active.
•The primary server handles directory synchronization, MWIs, event notification, and message notification.
•Messages, greetings, and other recordings made on the primary server but not replicated to the secondary server before the network outage are replicated to the secondary server.
•For Cisco Unity 3.1(3) and earlier, if the network outage lasted more than five minutes, the Distribution agent on the primary server may need to be manually started to resume UnityDb database replication when the primary server becomes active again. See the "Restarting UnityDb Database Replication and Configuring the Distribution Agent Schedule" section.
The Exchange 2000 Server That Has the Cisco Unity Messaging System Mailbox Is Disconnected from the Network, Then Reconnected
In testing, this scenario was simulated by disabling the network interface card on the Exchange 2000 server.
Disconnection Behavior
•All subscribers hear the Unity Messaging Repository (UMR) conversation when they log on to Cisco Unity.
•External callers can leave messages for subscribers. The new messages are stored in the UnityMTA folder on the primary server.
•Subscribers homed on the same Cisco Unity server can leave messages for each other by dialing an extension or logging on to Cisco Unity. The new messages are stored in the UnityMTA folder on the primary server.
•Subscribers can call the Cisco Unity server and listen to their new messages stored in the UnityMTA folder on the primary server. Messages stored on the Exchange server before the network outage are not available.
•The primary server handles directory synchronization.
•MWIs, event notification, and message notification are not handled.
Reconnection Behavior
•Subscribers who log on to Cisco Unity no longer hear the UMR conversation, but hear the appropriate conversation.
•Messages stored in the UnityMTA folder on the primary server are delivered to the appropriate subscriber Inboxes.
•The primary server sets MWIs for subscribers who have unheard messages stored on the Exchange 2000 server.
•External callers and subscribers can leave messages for subscribers. The messages are stored on the Exchange server.
•The primary server handles directory synchronization, MWIs, event notification, and message notification.
The Exchange 2000 Server That Has the Cisco Unity Messaging System Mailbox Is Disconnected from the Network, Then the Primary and Secondary Servers Are Restarted
In testing, this scenario was simulated by disabling the network interface card on the Exchange 2000 server, then stopping and restarting the primary and secondary servers.
Restarting Behavior for the Primary and Secondary Servers
•The Cisco Unity service (AvCsMgr.exe) on both servers does not start.
•There is no voice messaging functionality. Neither the primary nor secondary server answers calls.
•Subscribers are not able to leave or listen to messages. External callers cannot leave messages for subscribers.
The Exchange 5.5 Server in a Mixed-Messaging Environment Is Disconnected from the Network, Then Reconnected
In testing, this scenario was simulated by disabling the network interface card on the Exchange 5.5 server.
Disconnection Behavior
•Subscribers whose messages are stored on another Exchange server that is not disconnected are not affected.
•Subscribers whose messages are stored on the Exchange 5.5 server that is disconnected hear the Unity Messaging Repository (UMR) conversation when they log on to Cisco Unity.
•Messages for subscribers on the Exchange 5.5 server that are left by subscribers are stored in the MTA queue on the bridgehead Exchange server. The messages are not stored in the UnityMTA folder on the active server. Subscribers cannot listen to their new messages from subscribers until the network outage is resolved.
•Messages for subscribers on the Exchange 5.5 server that are left by external callers are stored in the UnityMTA folder on the primary server. Subscribers can call the Cisco Unity server and listen to their new messages from external callers.
•Messages stored on the Exchange server before the network outage are not available.
•MWIs are not set for subscribers whose messages are stored on the Exchange 5.5 server.
Reconnection Behavior
•All messages stored in the MTA queue on the bridgehead Exchange server and in the UnityMTA folder on the active server are delivered to subscriber Inboxes.
•The primary server sets MWIs for subscribers who have unheard messages stored on the Exchange 5.5 server.
The Exchange 2000 Server That Does Not Have the Cisco Unity Messaging System Mailbox Is Disconnected from the Network, Then Reconnected
In testing, this scenario was simulated by disabling the network interface card on the Exchange 2000 server.
Disconnection Behavior
•Subscribers whose messages are stored on another Exchange server that is not disconnected are not affected.
•Subscribers whose messages are stored on the Exchange 2000 server that is disconnected hear the Unity Messaging Repository (UMR) conversation when they log on to Cisco Unity.
•Messages for subscribers on the Exchange 2000 server that are left by subscribers are stored in the MTA queue on the bridgehead Exchange server. The messages are not stored in the UnityMTA folder on the active server.
•Messages for subscribers on the Exchange 2000 server that are left by external callers are stored in the UnityMTA folder on the active server. Subscribers cannot listen to their messages until the network outage is resolved.
•MWIs are not set for subscribers whose messages are stored on the Exchange 2000 server.
Reconnection Behavior
•All messages stored in the MTA queue on the bridgehead Exchange server and in the UnityMTA folder on the active server are delivered to subscriber Inboxes.
•The primary server sets MWIs for subscribers who have unheard messages stored on the Exchange 2000 server.
The Publisher Cisco CallManager Server Is Disconnected from the Network, Then Reconnected
In testing, this scenario was simulated by disabling the network interface card on the publisher (primary) Cisco CallManager server.
Disconnection Behavior
•The primary Cisco Unity server continues to be active, and the secondary Cisco Unity server continues to be inactive.
•All voice messaging ports on the primary and secondary servers unregister with the publisher (primary) Cisco CallManager server and register with the subscriber (secondary) Cisco CallManager server.
•The primary Cisco Unity server continues answering all calls.
Reconnection Behavior
•The primary Cisco Unity server continues to be active, and the secondary Cisco Unity server continues to be inactive.
•If registering automatically with the publisher (primary) Cisco CallManager server is enabled, all voice messaging ports on the primary and secondary servers unregister with the subscriber (secondary) Cisco CallManager server and register with the publisher (primary) Cisco CallManager server.
•If registering automatically with the publisher (primary) Cisco CallManager server is not enabled, all voice messaging ports on the primary and secondary servers remain registered with the subscriber (secondary) Cisco CallManager server.
•The primary Cisco Unity server continues answering all calls.
The Subscriber Cisco CallManager Server Is Disconnected from the Network, Then Reconnected
In testing, this scenario was simulated by disabling the network interface card on the subscriber (secondary) Cisco CallManager server.
Disconnection Behavior
•The primary Cisco Unity server continues to be active, and the secondary Cisco Unity server continues to be inactive.
•All voice messaging ports on the primary and secondary Cisco Unity servers remain registered with the publisher (primary) Cisco CallManager server.
•The primary Cisco Unity server continues answering all calls.
Reconnection Behavior
•The primary Cisco Unity server continues to be active, and the secondary Cisco Unity server continues to be inactive.
•All voice messaging ports on the primary and secondary Cisco Unity servers remain registered with the publisher (primary) Cisco CallManager server.
•The primary Cisco Unity server continues answering all calls.
The Cisco CallManager Cluster Is Disconnected from the Network, Then Reconnected
In testing, this scenario was simulated by disabling the network interface card on all Cisco CallManager servers in the cluster.
Disconnection Behavior
•The primary Cisco Unity server continues to be active, and the secondary Cisco Unity server continues to be inactive.
•All voice messaging ports on the primary and secondary Cisco Unity servers unregister with the publisher (primary) Cisco CallManager server. They do not register with another Cisco CallManager server.
•Cisco Unity does not answer calls.
•Subscribers are not able to leave or listen to messages. External callers cannot leave messages for subscribers because phones will not forward calls to Cisco Unity.
•Subscribers calling Cisco Unity hear a fast busy tone.
•Subscribers on a Cisco Unity connected to another Cisco CallManager cluster can leave messages for subscribers of the disconnected cluster.
Reconnection Behavior
•The primary Cisco Unity server continues to be active, and the secondary Cisco Unity server continues to be inactive.
•All voice messaging ports on the primary and secondary Cisco Unity servers register with the publisher (primary) Cisco CallManager server.
•The primary Cisco Unity server answers all calls.
The Domain Controller That Cisco Unity Is Connected to Is Disconnected from the Network, Then Reconnected
In testing, this scenario was simulated by disabling the network interface card on the domain controller that Cisco Unity is connected to.
Disconnection Behavior
•The primary server continues to be active, and the secondary server continues to be inactive.
•Directory synchronization does not occur.
•Changes to Cisco Unity objects made on other domain controllers in the same domain are not written to the UnityDb database.
•Changes detected in the global catalog server are written to the UnityDb database.
•Subscribers are able to leave and listen to messages. External callers can leave messages for subscribers.
Reconnection Behavior
•The primary server continues to be active, and the secondary server continues to be inactive.
•Changes made on other domain controllers in the same domain during the network outage are written to the UnityDb database.
An Additional Domain Controller That Cisco Unity Is Not Connected to Is Disconnected from the Network, Then Reconnected
In testing, this scenario was simulated by disabling the network interface card on a domain controller that Cisco Unity is not connected to.
Disconnection Behavior
•The primary server continues to be active, and the secondary server continues to be inactive.
•The primary server continues answering all calls.
Reconnection Behavior
•The primary server continues to be active, and the secondary server continues to be inactive.
•The primary server continues answering all calls.
The Global Catalog Server That Cisco Unity Is Connected to Is Disconnected from the Network, Then Reconnected
In testing, this scenario was simulated by disabling the network interface card on the global catalog server that Cisco Unity is connected to.
Disconnection Behavior
•The primary server continues to be active, and the secondary server continues to be inactive.
•The primary server continues answering all calls.
•Subscribers are not able to leave messages. When trying to leave a message, subscribers hear silence.
•External callers can leave messages for subscribers. Subscribers cannot listen to the messages until the network outage is resolved and the new messages are delivered to subscriber Inboxes.
•Subscribers can call other subscribers directly and talk to each other.
•The Global Catalog monitor does not detect changes. Changes made to Cisco Unity objects on other Cisco Unity servers are not written to the local UnityDb database.
•Subscribers on other Cisco Unity servers can leave messages for subscribers on the local server.
•Subscribers can listen to saved messages. New messages from external callers are not available until the network outage is resolved.
Reconnection Behavior
•The primary server continues to be active, and the secondary server continues to be inactive.
•The primary server continues answering all calls.
•Changes made to Cisco Unity objects on other Cisco Unity servers are written to the local UnityDb database.
•All messages stored in the MTA queue on the bridgehead Exchange server and in the UnityMTA folder on the active server are delivered to subscriber Inboxes.
•Users cannot access the Cisco Unity Administrator or the ActiveAssistant. An error appears stating that the account is not associated with a subscriber. Restarting the primary server provides access to the Cisco Unity Administrator and the ActiveAssistant.
The Global Catalog Server That Cisco Unity Is Not Connected to Is Disconnected from the Network, Then Reconnected
In testing, this scenario was simulated by disabling the network interface card on the global catalog server that Cisco Unity is not connected to.
Disconnection Behavior
•The primary server continues to be active, and the secondary server continues to be inactive.
•The primary server continues answering all calls.
Reconnection Behavior
•The primary server continues to be active, and the secondary server continues to be inactive.
•The primary server continues answering all calls.
The Primary Server Crashes
In testing, this scenario was simulated by turning off power to the primary server.
Disconnection Behavior
•The secondary server answers all calls. Depending on network latency, this behavior may take a few minutes to begin.
•The Failover Monitor on the secondary server shows that the secondary server is active.
•Subscribers are able to leave and listen to messages. External callers can leave messages for subscribers.
•Messages, greetings, and other recordings made on the primary server but not replicated to the secondary server before the network outage are not available on the secondary server.
•The secondary server handles directory synchronization, MWIs, event notification, and message notification.
Reconnection Behavior Before Failback
•The primary server is inactive, and the secondary server remains active.
•The secondary server answers all calls.
•All voice messaging ports on the primary server remain unregistered with the Cisco CallManager server.
Reconnection Behavior After Failback
•When failback is manually initiated or when a scheduled failback occurs, the primary server becomes active and the secondary server becomes inactive.
•All voice messaging ports on the primary server register with the Cisco CallManager server.
•The primary server answers all calls.
•Subscribers are able to leave and listen to messages. External callers can leave messages for subscribers.
•The Node Manager services (AvCsNodeMgr.exe) on the primary and secondary servers send status to and receive status from each other.
•The Failover Monitors on the primary and secondary servers show that the primary server is active.
•Changes to the UnityDb database that occurred while the primary server was offline are replicated from the secondary server to the primary server.
•The primary server handles directory synchronization, MWIs, event notification, and message notification.
•Messages, greetings, and other recordings made on the primary server but not replicated to the secondary server before the server outage are replicated to the secondary server.
•Messages, greetings, and other recordings made on the secondary server during the server outage are replicated to the primary server.
•For Cisco Unity 3.1(3) and earlier, if the server outage lasted more than five minutes, the Distribution agent on the primary server may need to be manually started to resume UnityDb database replication when the secondary server is online again. See the "Restarting UnityDb Database Replication and Configuring the Distribution Agent Schedule" section.
The Secondary Server Crashes
In testing, this scenario was simulated by turning off power to the secondary server.
Disconnection Behavior
•The primary server continues answering all calls.
•Subscribers are able to leave and listen to messages. External callers can leave messages for subscribers.
•The Failover Monitor on the primary server shows that the primary server is active.
•The Replication Monitor in the SQL Enterprise Manager displays errors.
•UnityDb database replication between the primary and secondary servers stops.
•The primary server handles directory synchronization, MWIs, event notification, and message notification.
Reconnection Behavior
•The primary server remains active, and the secondary server becomes inactive.
•The primary server continues answering all calls.
•Subscribers are able to leave and listen to messages. External callers can leave messages for subscribers.
•All voice messaging ports on the secondary server register with the Cisco CallManager server.
•The Node Manager services (AvCsNodeMgr.exe) on the primary and secondary servers send status to and receive status from each other.
•The Failover Monitors on the primary and secondary servers show that the primary server is active.
•Changes to the UnityDb database that occurred while the secondary server was offline are replicated from the primary server to the secondary server.
•The primary server continues handling directory synchronization, MWIs, event notification, and message notification.
•Messages, greetings, and other recordings made on the primary server but not replicated to the secondary server before the server outage are replicated to the secondary server.
•Messages, greetings, and other recordings made on the primary server during the server outage are replicated to the secondary server.
•For Cisco Unity 3.1(3) and earlier, if the server outage lasted more than five minutes, the Distribution agent on the primary server may need to be manually started to resume UnityDb database replication when the secondary is online again. See the "Restarting UnityDb Database Replication and Configuring the Distribution Agent Schedule" section.
The Primary and Secondary Servers Crash Simultaneously
In testing, this scenario was simulated by turning off power to the primary and secondary servers at the same time.
Disconnection Behavior
•There is no voice messaging functionality. Neither the primary nor secondary server answers calls.
•Subscribers are not able to leave or listen to messages. External callers cannot leave messages for subscribers.
•Callers trying to leave messages hear a fast busy tone instead of the personal greeting for the subscriber.
•Subscribers can call other subscribers directly and talk to each other.
•Neither server initiates directory synchronization, MWIs, event notification, or message notification.
Reconnection Behavior (Only the Primary Server Is Reconnected)
•The Failover Monitor on the primary server shows that the primary server is active.
•All voice messaging ports on the primary server register with the Cisco CallManager server.
•The primary server answers all calls.
•Subscribers are able to leave and listen to messages. External callers can leave messages for subscribers.
•Messages, greetings, and other recordings made on the primary server but not replicated to the secondary server before the server outage are not replicated to the secondary server because the secondary server is offline.
•Changes to the UnityDb database that occurred before the server outage and were not replicated to the secondary server are not replicated because the secondary server is offline.
•The primary server handles directory synchronization, MWIs, event notification, and message notification.
Reconnection Behavior (the Secondary Server Is Also Reconnected)
•The Failover Monitors on the primary and secondary servers show that the primary server is active and the secondary server is inactive.
•All voice messaging ports on the secondary server register with the Cisco CallManager server.
•The primary server continues answering all calls.
•The Node Manager services (AvCsNodeMgr.exe) on the primary and secondary servers send status to and receive status from each other.
•Changes to the UnityDb database that occurred while the secondary server was offline are replicated from the primary server to the secondary server.
•For Cisco Unity 3.1(3) and earlier, if the server outage lasted more than five minutes, the Distribution agent on the primary server may need to be manually started to resume UnityDb database replication when the outage is resolved. See the "Restarting UnityDb Database Replication and Configuring the Distribution Agent Schedule" section.
•The primary server continues handling directory synchronization, MWIs, event notification, and message notification.
•Messages, greetings, and other recordings made on the primary server but not replicated to the secondary server before the server outage are replicated to the secondary server.
•Messages, greetings, and other recordings made on the primary server while the secondary server was offline are replicated to the secondary server.
The Primary Server Is Disconnected from the Network, Then the Exchange 2000 Server That Has the Cisco Unity Messaging System Mailbox Is Disconnected from the Network
In testing, this scenario was simulated by disabling the network interface card on the primary server, then on the Exchange 2000 server.
Disconnection Behavior (Only the Primary Server Is Disconnected)
•The secondary server answers all calls.
•Subscribers are able to leave and listen to messages. External callers can leave messages for subscribers.
•All voice messaging ports on the primary server unregister with the Cisco CallManager server.
•The Node Manager services (AvCsNodeMgr.exe) on the primary and secondary servers no longer receive status from each other.
•The Failover Monitor on the primary server shows that the primary server is active. The Failover Monitor on the secondary server shows that the secondary server is active.
•Messages, greetings, and other recordings made on the primary server but not replicated to the secondary server before the network outage are not available on the secondary server.
•The Replication Monitor in the SQL Enterprise Manager displays errors.
•UnityDb database replication between the primary and secondary servers stops.
•The secondary server handles directory synchronization, MWIs, event notification, and message notification.
Disconnection Behavior (the Exchange 2000 Server Is Also Disconnected)
•All subscribers hear the Unity Messaging Repository (UMR) conversation when they log on to Cisco Unity.
•External callers can leave messages for subscribers. The new messages are stored in the UnityMTA folder on the secondary server.
•Subscribers homed on a different Cisco Unity server can leave messages for subscribers on another Cisco Unity server by calling the Cisco Unity server. The new messages are stored in the UnityMTA folder on the secondary server.
•Subscribers can call the Cisco Unity server and listen to their new messages stored in the UnityMTA folder on the secondary server. Messages stored on the Exchange 2000 server before the network outage are not available.
•The secondary server handles directory synchronization.
•MWIs, event notification, and message notification are not handled.
Reconnection Behavior When the Exchange 2000 Server Is Reconnected and the Primary Server Remains Disconnected
•Subscribers who log on to Cisco Unity no longer hear the UMR conversation, but hear the appropriate conversation.
•Messages stored in the UnityMTA folder on the secondary server are delivered to the appropriate subscriber Inboxes.
•The secondary server sets MWIs for subscribers who have unheard messages stored on the Exchange 2000 server.
•External callers and subscribers can leave messages for subscribers. The messages are stored on the Exchange 2000 server.
•The secondary server handles directory synchronization, MWIs, event notification, and message notification.
Reconnection Behavior After the Exchange 2000 Server Is Reconnected, Then the Primary Server Is Reconnected
•The primary server becomes active, and the secondary server becomes inactive.
•All voice messaging ports on the primary server register with the Cisco CallManager server.
•The primary server answers all calls.
•Subscribers are able to leave and listen to messages. External callers can leave messages for subscribers.
•The Node Manager services (AvCsNodeMgr.exe) on the primary and secondary servers send status to and receive status from each other.
•The Failover Monitors on the primary and secondary servers show that the primary server is active.
•Changes to the UnityDb database that occurred while the primary server was offline are replicated from the secondary server to the primary server.
•The primary server handles directory synchronization, MWIs, event notification, and message notification.
•Messages, greetings, and other recordings made on the primary server but not replicated to the secondary server before the network outage are replicated to the secondary server.
•Messages, greetings, and other recordings made on the secondary server during the network outage are replicated to the primary server.
Reconnection Behavior When the Primary Server Is Reconnected and the Exchange 2000 Server Remains Disconnected
•The primary server becomes active, and the secondary server becomes inactive.
•All voice messaging ports on the primary server register with the Cisco CallManager server.
•The primary server answers all calls.
•All subscribers hear the UMR conversation when they log on to Cisco Unity.
•The Node Manager services (AvCsNodeMgr.exe) on the primary and secondary servers send status to and receive status from each other.
•The Failover Monitors on the primary and secondary servers show that the primary server is active.
•Changes to the UnityDb database that occurred while the primary server was offline are replicated from the secondary server to the primary server.
•The primary server handles directory synchronization, MWIs, event notification, and message notification.
•Messages, greetings, and other recordings made on the primary server but not replicated to the secondary server before the network outage are replicated to the secondary server.
•Messages, greetings, and other recordings made on the secondary server during the network outage are replicated to the primary server.
Reconnection Behavior After the Primary Server Is Reconnected, Then the Exchange 2000 Server Is Reconnected
•Subscribers who log on to Cisco Unity no longer hear the UMR conversation, but hear the appropriate conversation.
•Messages stored in the UnityMTA folder on the primary server are delivered to the appropriate subscriber Inboxes.
•The primary server sets MWIs for subscribers who have unheard messages stored on the Exchange 2000 server.
•External callers and subscribers can leave messages for subscribers. The messages are stored on the Exchange 2000 server.
•The primary server handles directory synchronization, MWIs, event notification, and message notification.
The Exchange 2000 Server That Has the Cisco Unity Messaging System Mailbox Is Disconnected from the Network, Then the Primary Server Is Disconnected from the Network
In testing, this scenario was simulated by disabling the network interface card on the Exchange 2000 server, then on the primary server.
Disconnection Behavior (Only the Exchange 2000 Server Is Disconnected)
•The primary server continues to be active, and the secondary server continues to be inactive.
•The primary server continues answering all calls.
•All subscribers hear the Unity Messaging Repository (UMR) conversation when they log on to Cisco Unity.
•External callers can leave messages for subscribers. The new messages are stored in the UnityMTA folder on the primary server.
•Subscribers homed on the same Cisco Unity server can leave messages for each other by dialing an extension or logging on to Cisco Unity. The new messages are stored in the UnityMTA folder on the primary server.
•Subscribers can call the Cisco Unity server and listen to their new messages stored in the UnityMTA folder on the primary server. Messages stored on the Exchange 2000 server before the network outage are not available.
•The primary server handles directory synchronization and file replication.
•MWIs, event notification, and message notification are not handled.
Disconnection Behavior (the Primary Server Is Also Disconnected)
•The secondary server answers all calls.
•The Failover Monitor on the primary server shows that the primary server is active. The Failover Monitor on the secondary server shows that the secondary server is active.
•All subscribers hear the UMR conversation when they log on to Cisco Unity.
•External callers can leave messages for subscribers. The new messages are stored in the UnityMTA folder on the secondary server.
•Subscribers homed on the same Cisco Unity server can leave messages for each other by dialing an extension or logging on to Cisco Unity. The new messages are stored in the UnityMTA folder on the secondary server.
•Subscribers can call the Cisco Unity server and listen to their new messages stored in the UnityMTA folder on the secondary server. Messages stored on the Exchange 2000 server before the network outage are not available.
•MWIs, event notification, and message notification are not handled.
Reconnection Behavior When the Primary Server Is Reconnected and the Exchange 2000 Server Remains Disconnected
•The primary server becomes active, and the secondary server becomes inactive.
•All voice messaging ports on the primary server register with the Cisco CallManager server.
•The primary server answers all calls.
•The Node Manager services (AvCsNodeMgr.exe) on the primary and secondary servers send status to and receive status from each other.
•The Failover Monitors on the primary and secondary servers show that the primary server is active.
•Changes to the UnityDb database that occurred while the primary server was offline are replicated from the secondary server to the primary server.
•The primary server handles directory synchronization, MWIs, event notification, and message notification.
•Messages, greetings, and other recordings made on the primary server but not replicated to the secondary server before the network outage are replicated to the secondary server.
•Messages, greetings, and other recordings made on the secondary server during the network outage are replicated to the primary server.
Reconnection Behavior After the Primary Server Is Reconnected, Then the Exchange 2000 Server Is Reconnected
•Subscribers who log on to Cisco Unity no longer hear the UMR conversation, but hear the appropriate conversation.
•Messages stored in the UnityMTA folder on the primary server are delivered to the appropriate subscriber Inboxes.
•The primary server sets MWIs for subscribers who have unheard messages stored on the Exchange 2000 server.
•External callers and subscribers can leave messages for subscribers. The messages are stored on the Exchange 2000 server.
•The primary server handles directory synchronization, MWIs, event notification, and message notification.
Reconnection Behavior When the Exchange 2000 Server Is Reconnected and the Primary Server Remains Disconnected
•Subscribers who log on to Cisco Unity no longer hear the UMR conversation, but hear the appropriate conversation.
•Messages stored in the UnityMTA folder on the secondary server are delivered to the appropriate subscriber Inboxes.
•The secondary server sets MWIs for subscribers who have unheard messages stored on the Exchange 2000 server.
•External callers and subscribers can leave messages for subscribers. The messages are stored on the Exchange 2000 server.
•The secondary server handles directory synchronization, MWIs, event notification, and message notification.
Reconnection Behavior After the Exchange 2000 Server Is Reconnected, Then the Primary Server Is Reconnected
•The primary server becomes active, and the secondary server becomes inactive.
•All voice messaging ports on the primary server register with the Cisco CallManager server.
•The primary server answers all calls.
•Subscribers are able to leave and listen to messages. External callers can leave messages for subscribers
•The Node Manager services (AvCsNodeMgr.exe) on the primary and secondary servers send status to and receive status from each other.
•The Failover Monitors on the primary and secondary servers show that the primary server is active.
•Changes to the UnityDb database that occurred while the primary server was offline are replicated from the secondary server to the primary server.
•The primary server handles directory synchronization, MWIs, event notification, and message notification.
•Messages, greetings, and other recordings made on the primary server but not replicated to the secondary server before the network outage are replicated to the secondary server.
•Messages, greetings, and other recordings made on the secondary server during the network outage are replicated to the primary server.
The Exchange 2000 Server That Has the Cisco Unity Messaging System Mailbox and the Primary Server Simultaneously Crash, Then Are Reconnected
In testing, this scenario was simulated by turning off power to the Exchange 2000 server and to the primary server at the same time.
Disconnection Behavior
•The secondary server answers all calls.
•All subscribers hear the Unity Messaging Repository (UMR) conversation when they log on to Cisco Unity.
•External callers can leave messages for subscribers. The new messages are stored in the UnityMTA folder on the secondary server.
•Subscribers homed on a different Cisco Unity server can leave messages for subscribers on another Cisco Unity server by calling the Cisco Unity server. The new messages are stored in the UnityMTA folder on the secondary server.
•Subscribers can call the Cisco Unity server and listen to their new messages stored in the UnityMTA folder on the secondary server. Messages stored on the Exchange 2000 server before the network outage are not available.
•MWIs, event notification, and message notification are not handled.
Reconnection Behavior When the Exchange 2000 Server Is Reconnected and the Primary Server Remains Disconnected
•Subscribers who log on to Cisco Unity no longer hear the UMR conversation, but hear the appropriate conversation.
•Messages stored in the UnityMTA folder on the secondary server are delivered to the appropriate subscriber Inboxes.
•The secondary server sets MWIs for subscribers who have unheard messages stored on the Exchange 2000 server.
•External callers and subscribers can leave messages for subscribers. The messages are stored on the Exchange 2000 server.
•The secondary server handles directory synchronization, MWIs, event notification, and message notification.
Reconnection Behavior After the Exchange 2000 Server Is Reconnected, Then the Primary Server Is Reconnected
•The primary server is inactive, and the secondary server remains active.
•When failback is manually initiated or when a scheduled failback occurs, the primary server becomes active and the secondary server becomes inactive.
•When the primary server becomes active, all voice messaging ports on the primary server register with the Cisco CallManager server.
•When the primary server becomes active, it answers all calls. Until then, the secondary server answers all calls.
•Subscribers are able to leave and listen to messages. External callers can leave messages for subscribers.
•The Node Manager services (AvCsNodeMgr.exe) on the primary and secondary servers send status to and receive status from each other.
•When the primary server becomes active, the Failover Monitors on the primary and secondary servers show that the primary server is active.
•Changes to the UnityDb database that occurred while the primary server was offline are replicated from the secondary server to the primary server.
•When the primary server becomes active, it handles directory synchronization, MWIs, event notification, and message notification.
•Messages, greetings, and other recordings made on the primary server but not replicated to the secondary server before the network outage are replicated to the secondary server.
•Messages, greetings, and other recordings made on the secondary server during the network outage are replicated to the primary server.
Reconnection Behavior When the Primary Server Is Reconnected and the Exchange 2000 Server Remains Disconnected
•The Cisco Unity service (AvCsMgr.exe) on the primary server does not start.
•The secondary server continues to be active.
•The secondary server continues answering all calls.
Reconnection Behavior After the Primary Server Is Reconnected, Then the Exchange 2000 Server Is Reconnected and the Cisco Unity Service (AvCsMgr.exe) on the Primary Server Is Manually Started
•The primary server is inactive, and the secondary server remains active.
•When failback is manually initiated or when a scheduled failback occurs, the primary server becomes active and the secondary server becomes inactive.
•When the primary server becomes active, all voice messaging ports on the primary server register with the Cisco CallManager server.
•When the primary server becomes active, it answers all calls. Until then, the secondary server answers all calls.
•Subscribers are able to leave and listen to messages. External callers can leave messages for subscribers. The messages are stored on the Exchange 2000 server.
•Subscribers who log on to Cisco Unity no longer hear the UMR conversation, but hear the appropriate conversation.
•Messages stored in the UnityMTA folder on the secondary server are delivered to the appropriate subscriber Inboxes.
•The primary server sets MWIs for subscribers who have unheard messages stored on the Exchange 2000 server.
•The Node Manager services (AvCsNodeMgr.exe) on the primary and secondary servers send status to and receive status from each other.
•The Failover Monitors on the primary and secondary servers show that the primary server is active.
•Changes to the UnityDb database that occurred while the primary server was offline are replicated from the secondary server to the primary server.
•The primary server handles directory synchronization, MWIs, event notification, and message notification.
•Messages, greetings, and other recordings made on the primary server but not replicated to the secondary server before the network outage are replicated to the secondary server.
•Messages, greetings, and other recordings made on the secondary server while the primary server was inactive are replicated to the primary server.
Outage Scenarios for Networks of Windows NT and Exchange 5.5
Note While the Cisco Unity server can be part of a Windows NT domain, only Windows 2000 can be installed on the Cisco Unity server.
This section contains the following scenarios:
•The Primary Server Is Disconnected from the Network, Then Reconnected
•The Secondary Server Is Disconnected from the Network, Then Reconnected
•The Primary and Secondary Servers Are Simultaneously Disconnected from the Network, Then the Primary Server Is Reconnected First
•The Primary and Secondary Servers Are Simultaneously Disconnected from the Network, Then the Secondary Server Is Reconnected First
•The Primary and Secondary Servers Are Simultaneously Disconnected from the Network, Then Both Servers Are Simultaneously Reconnected
•The Exchange 5.5 Server That Has the Cisco Unity Messaging System Mailbox Is Disconnected from the Network, Then Reconnected
•The Exchange 5.5 Server That Has the Cisco Unity Messaging System Mailbox Is Disconnected from the Network, Then the Primary and Secondary Servers Are Restarted
•The Exchange 5.5 Server That Does Not Have the Cisco Unity Messaging System Mailbox Is Disconnected from the Network, Then Reconnected
•The Publisher Cisco CallManager Server Is Disconnected from the Network, Then Reconnected
•The Subscriber Cisco CallManager Server Is Disconnected from the Network, Then Reconnected
•The Cisco CallManager Cluster Is Disconnected from the Network, Then Reconnected
•The Primary Domain Controller Is Disconnected from the Network, Then Reconnected
•The Backup Domain Controller Is Disconnected from the Network, Then Reconnected
•The Primary Domain Controller and Backup Domain Controller Are Disconnected from the Network, Then Reconnected
•The Primary Domain Controller Is Disconnected from the Network, Then the Primary and Secondary Servers Are Restarted
•The Primary Domain Controller and Backup Domain Controller Are Disconnected from the Network, Then the Primary and Secondary Servers Are Restarted
•The Primary Server Crashes
•The Secondary Server Crashes
•The Primary and Secondary Servers Crash Simultaneously
•The Primary Server Is Disconnected from the Network, Then the Exchange 5.5 Server That Has the Cisco Unity Messaging System Mailbox Is Disconnected from the Network
•The Exchange 5.5 Server That Has the Cisco Unity Messaging System Mailbox Is Disconnected from the Network, Then the Primary Server Is Disconnected from the Network
•The Exchange 5.5 Server That Has the Cisco Unity Messaging System Mailbox and the Primary Server Simultaneously Crash, Then Are Reconnected
The Primary Server Is Disconnected from the Network, Then Reconnected
In testing, this scenario was simulated by disabling the network interface card on the primary server.
Disconnection Behavior
•The secondary server answers all calls.
•Subscribers are able to leave and listen to messages. External callers can leave messages for subscribers.
•All voice messaging ports on the primary server unregister with the Cisco CallManager server.
•The Node Manager services (AvCsNodeMgr.exe) on the primary and secondary servers no longer receive status from each other.
•The Failover Monitor on the primary server shows that the primary server is active. The Failover Monitor on the secondary server shows that the secondary server is active.
•Messages, greetings, and other recordings made on the primary server but not replicated to the secondary server before the network outage are not available on the secondary server.
•The Replication Monitor in the SQL Enterprise Manager displays errors.
•UnityDb database replication between the primary and secondary servers stops.
•The secondary server handles directory synchronization, MWIs, event notification, and message notification.
Reconnection Behavior
•The primary server becomes active, and the secondary server becomes inactive.
•All voice messaging ports on the primary server register with the Cisco CallManager server.
•The primary server answers all calls.
•Subscribers are able to leave and listen to messages. External callers can leave messages for subscribers.
•The Node Manager services (AvCsNodeMgr.exe) on the primary and secondary servers send status to and receive status from each other.
•The Failover Monitors on the primary and secondary servers show that the primary server is active.
•Changes to the UnityDb database that occurred while the primary server was offline are replicated from the secondary server to the primary server.
•The primary server handles directory synchronization, MWIs, event notification, and message notification.
•Messages, greetings, and other recordings made on the primary server but not replicated to the secondary server before the network outage are replicated to the secondary server.
•Messages, greetings, and other recordings made on the secondary server during the network outage are replicated to the primary server.
•For Cisco Unity 3.1(3) and earlier, if the network outage lasted more than five minutes, the Distribution agent on the primary server may need to be manually started to resume UnityDb database replication when the primary server becomes active again. See the "Restarting UnityDb Database Replication and Configuring the Distribution Agent Schedule" section.
The Secondary Server Is Disconnected from the Network, Then Reconnected
In testing, this scenario was simulated by disabling the network interface card on the secondary server.
Disconnection Behavior
•The primary server continues answering all calls.
•Subscribers are able to leave and listen to messages. External callers can leave messages for subscribers.
•All voice messaging ports on the secondary server unregister with the Cisco CallManager server.
•The Node Manager services (AvCsNodeMgr.exe) on the primary and secondary servers no longer receive status from each other.
•The Failover Monitor on the primary server shows that the primary server is active. The Failover Monitor on the secondary server shows that the secondary server is active.
•The Replication Monitor in the SQL Enterprise Manager displays errors.
•UnityDb database replication between the primary and secondary servers stops.
•The primary server handles directory synchronization, MWIs, event notification, and message notification.
Reconnection Behavior
•The primary server remains active, and the secondary server becomes inactive.
•The primary server continues answering all calls.
•Subscribers are able to leave and listen to messages. External callers can leave messages for subscribers.
•All voice messaging ports on the secondary server register with the Cisco CallManager server.
•The Node Manager services (AvCsNodeMgr.exe) on the primary and secondary servers send status to and receive status from each other.
•The Failover Monitors on the primary and secondary servers show that the primary server is active.
•Changes to the UnityDb database that occurred while the secondary server was offline are replicated from the primary server to the secondary server.
•The primary server continues handling directory synchronization, MWIs, event notification, and message notification.
•Messages, greetings, and other recordings made on the primary server but not replicated to the secondary server before the network outage are replicated to the secondary server.
•Messages, greetings, and other recordings made on the primary server during the network outage are replicated to the secondary server.
•For Cisco Unity 3.1(3) and earlier, if the network outage lasted more than five minutes, the Distribution agent on the primary server may need to be manually started to resume UnityDb database replication when the primary server becomes active again. See the "Restarting UnityDb Database Replication and Configuring the Distribution Agent Schedule" section.
The Primary and Secondary Servers Are Simultaneously Disconnected from the Network, Then the Primary Server Is Reconnected First
In testing, this scenario was simulated by disabling the network interface card on the primary and secondary servers at the same time.
Disconnection Behavior
•There is no voice messaging functionality. Neither the primary nor secondary server answers calls.
•Subscribers are not able to leave or listen to messages. External callers cannot leave messages for subscribers.
•Callers trying to leave messages hear a fast busy tone instead of the personal greeting for the subscriber.
•All voice messaging ports on the primary and secondary servers unregister with the Cisco CallManager server.
•The Node Manager services (AvCsNodeMgr.exe) on the primary and secondary servers no longer receive status from each other.
•The Failover Monitor on the primary server shows that the primary server is active. The Failover Monitor on the secondary server shows that the secondary server is active.
•Subscribers can call other subscribers directly and talk to each other.
•The Replication Monitor in the SQL Enterprise Manager displays errors.
•UnityDb database replication between the primary and secondary servers stops.
•Neither server initiates directory synchronization, MWIs, event notification, or message notification.
Reconnection Behavior (Only the Primary Server Is Reconnected)
•The Failover Monitor on the primary server shows that the primary server is active. The Failover Monitor on the secondary server shows that the secondary server is active.
•All voice messaging ports on the primary server register with the Cisco CallManager server.
•The primary server answers all calls.
•Subscribers are able to leave and listen to messages. External callers can leave messages for subscribers.
•Messages, greetings, and other recordings made on the primary server but not replicated to the secondary server before the network outage are not replicated to the secondary server because the secondary server is offline.
•Changes to the UnityDb database that occurred before the network outage and were not replicated to the secondary server are not replicated because the secondary server is offline.
•The primary server handles directory synchronization, MWIs, event notification, and message notification.
Reconnection Behavior (the Secondary Server Is Also Reconnected)
•The Failover Monitors on the primary and secondary servers show that the primary server is active and the secondary server is inactive.
•All voice messaging ports on the secondary server register with the Cisco CallManager server.
•The primary server continues answering all calls.
•The Node Manager services (AvCsNodeMgr.exe) on the primary and secondary servers send status to and receive status from each other.
•Changes to the UnityDb database that occurred while the secondary server was offline are replicated from the primary server to the secondary server.
•For Cisco Unity 3.1(3) and earlier, if the network outage lasted more than five minutes, the Distribution agent on the primary server may need to be manually started to resume UnityDb database replication when the network outage is resolved. See the "Restarting UnityDb Database Replication and Configuring the Distribution Agent Schedule" section.
•The primary server continues handling directory synchronization, MWIs, event notification, and message notification.
•Messages, greetings, and other recordings made on the primary server but not replicated to the secondary server before the network outage are replicated to the secondary server.
•Messages, greetings, and other recordings made on the primary server while the secondary server was offline are replicated to the secondary server.
The Primary and Secondary Servers Are Simultaneously Disconnected from the Network, Then the Secondary Server Is Reconnected First
In testing, this scenario was simulated by disabling the network interface card on the primary and secondary servers at the same time.
Disconnection Behavior
•There is no voice messaging functionality. Neither the primary nor secondary server answers calls.
•Subscribers are not able to leave or listen to messages. External callers cannot leave messages for subscribers.
•Callers trying to leave messages hear a fast busy tone instead of the personal greeting for the subscriber.
•All voice messaging ports on the primary and secondary servers unregister with the Cisco CallManager server.
•The Node Manager services (AvCsNodeMgr.exe) on the primary and secondary servers no longer receive status from each other.
•The Failover Monitor on the primary server shows that the primary server is active. The Failover Monitor on the secondary server shows that the secondary server is active.
•Subscribers can call other subscribers directly and talk to each other.
•The Replication Monitor in the SQL Enterprise Manager displays errors.
•UnityDb database replication between the primary and secondary servers stops.
•Neither server initiates directory synchronization, MWIs, event notification, or message notification.
Reconnection Behavior (Only the Secondary Server Is Reconnected)
•The Failover Monitor on the primary server shows that the primary server is active. The Failover Monitor on the secondary server shows that the secondary server is active.
•All voice messaging ports on the secondary server register with the Cisco CallManager server.
•The secondary server answers all calls.
•Subscribers are able to leave and listen to messages. External callers can leave messages for subscribers.
•Messages, greetings, and other recordings made on the primary server but not replicated to the secondary server before the network outage are not replicated to the secondary server because the primary server is offline.
•Messages, greetings, and other recordings made on the secondary server during the network outage are not replicated to the primary server because the primary server is offline.
•Changes to the UnityDb database that occurred before the network outage and were not replicated to the secondary server are not replicated because the primary server is offline.
•The secondary server handles directory synchronization, MWIs, event notification, and message notification.
Reconnection Behavior (the Primary Server Is Also Reconnected)
•The primary becomes active, and the secondary server becomes inactive.
•All voice messaging ports on the primary server register with the Cisco CallManager server.
•The primary server answers all calls.
•The Node Manager services (AvCsNodeMgr.exe) on the primary and secondary servers send status to and receive status from each other.
•The Failover Monitors on the primary and secondary servers show that primary server is active and the secondary server is inactive.
•Changes to the UnityDb database that occurred while the primary server was offline are replicated from the secondary server to the primary server.
•For Cisco Unity 3.1(3) and earlier, if the network outage lasted more than five minutes, the Distribution agent on the primary server may need to be manually started to resume UnityDb database replication when the network outage is resolved. See the "Restarting UnityDb Database Replication and Configuring the Distribution Agent Schedule" section.
•The primary server handles directory synchronization, MWIs, event notification, and message notification.
•Messages, greetings, and other recordings made on the primary server but not replicated to the secondary server before the network outage are replicated to the secondary server.
•Messages, greetings, and other recordings made on the secondary server while the primary server was offline are replicated to the primary server.
The Primary and Secondary Servers Are Simultaneously Disconnected from the Network, Then Both Servers Are Simultaneously Reconnected
In testing, this scenario was simulated by disabling the network interface card on the primary and secondary servers at the same time.
Disconnection Behavior
•There is no voice messaging functionality. Neither the primary nor secondary server answers calls.
•Subscribers are not able to leave or listen to messages. External callers cannot leave messages for subscribers.
•Callers trying to leave messages hear a fast busy tone instead of the personal greeting for the subscriber.
•All voice messaging ports on the primary and secondary servers unregister with the Cisco CallManager server.
•The Node Manager services (AvCsNodeMgr.exe) on the primary and secondary servers no longer receive status from each other.
•The Failover Monitor on the primary server shows that the primary server is active. The Failover Monitor on the secondary server shows that the secondary server is active.
•Subscribers can call other subscribers directly and talk to each other.
•The Replication Monitor in the SQL Enterprise Manager displays errors.
•UnityDb database replication between the primary and secondary servers stops.
•Neither server initiates directory synchronization, MWIs, event notification, or message notification.
Reconnection Behavior
•The primary server remains active, and the secondary server becomes inactive.
•All voice messaging ports on the primary and secondary servers register with the Cisco CallManager server.
•The primary server answers all calls.
•Subscribers are able to leave and listen to messages. External callers can leave messages for subscribers.
•The Node Manager services (AvCsNodeMgr.exe) on the primary and secondary servers send status to and receive status from each other.
•The Failover Monitors on the primary and secondary servers show that the primary server is active.
•The primary server handles directory synchronization, MWIs, event notification, and message notification.
•Messages, greetings, and other recordings made on the primary server but not replicated to the secondary server before the network outage are replicated to the secondary server.
•For Cisco Unity 3.1(3) and earlier, if the network outage lasted more than five minutes, the Distribution agent on the primary server may need to be manually started to resume UnityDb database replication when the primary server becomes active again. See the "Restarting UnityDb Database Replication and Configuring the Distribution Agent Schedule" section.
The Exchange 5.5 Server That Has the Cisco Unity Messaging System Mailbox Is Disconnected from the Network, Then Reconnected
In testing, this scenario was simulated by disabling the network interface card on the Exchange 5.5 server.
Disconnection Behavior
•All subscribers hear the Unity Messaging Repository (UMR) conversation when they log on to Cisco Unity.
•External callers can leave messages for subscribers. The new messages are stored in the UnityMTA folder on the primary server.
•Subscribers homed on the same Cisco Unity server can leave messages for each other by dialing an extension or logging on to Cisco Unity. The new messages are stored in the UnityMTA folder on the primary server.
•Subscribers can call the Cisco Unity server and listen to their new messages stored in the UnityMTA folder on the primary server. Messages stored on the Exchange 5.5 server before the network outage are not available.
•Directory synchronization, MWIs, event notification, and message notification are not handled.
Reconnection Behavior
•Subscribers who log on to Cisco Unity no longer hear the UMR conversation, but hear the appropriate conversation.
•Messages stored in the UnityMTA folder on the primary server are delivered to the appropriate subscriber Inboxes.
•The primary server sets MWIs for subscribers who have unheard messages stored on the Exchange 5.5 server.
•External callers and subscribers can leave messages for subscribers. The messages are stored on the Exchange 5.5 server.
•The primary server handles directory synchronization, MWIs, event notification, and message notification.
The Exchange 5.5 Server That Has the Cisco Unity Messaging System Mailbox Is Disconnected from the Network, Then the Primary and Secondary Servers Are Restarted
In testing, this scenario was simulated by disabling the network interface card on the Exchange 5.5 server, then stopping and restarting the primary and secondary servers.
Restarting Behavior for Primary and Secondary Servers
•The Cisco Unity service (AvCsMgr.exe) on both servers does not start.
•There is no voice messaging functionality. Neither the primary nor secondary server answers calls.
•Subscribers are not able to leave or listen to messages. External callers cannot leave messages for subscribers.
The Exchange 5.5 Server That Does Not Have the Cisco Unity Messaging System Mailbox Is Disconnected from the Network, Then Reconnected
In testing, this scenario was simulated by disabling the network interface card on the Exchange 5.5 server.
Disconnection Behavior
•Subscribers whose messages are stored on another Exchange server that is not disconnected are not affected.
•Subscribers whose messages are stored on the Exchange 5.5 server that is disconnected hear the Unity Messaging Repository (UMR) conversation when they log on to Cisco Unity.
•Messages for subscribers on the Exchange 5.5 server that are left by subscribers are stored in the MTA queue on the bridgehead Exchange server. The messages are not stored in the UnityMTA folder on the active server. Subscribers cannot listen to their new messages from subscribers until the network outage is resolved.
•Messages for subscribers on the Exchange 5.5 server that are left by external callers are stored in the UnityMTA folder on the primary server. Subscribers can call the Cisco Unity server and listen to their new messages from external callers.
•Messages stored on the Exchange 5.5 server before the network outage are not available.
•MWIs are not set for subscribers whose messages are stored on the Exchange 5.5 server.
Reconnection Behavior
•All messages stored in the MTA queue on the bridgehead Exchange server and in the UnityMTA folder on the primary server are delivered to subscriber Inboxes.
•The primary server sets MWIs for subscribers who have unheard messages stored on the Exchange 5.5 server.
The Publisher Cisco CallManager Server Is Disconnected from the Network, Then Reconnected
In testing, this scenario was simulated by disabling the network interface card on the publisher (primary) Cisco CallManager server.
Disconnection Behavior
•The primary Cisco Unity server continues to be active, and the secondary Cisco Unity server continues to be inactive.
•All voice messaging ports on the primary and secondary Cisco Unity servers unregister with the publisher (primary) Cisco CallManager server and register with the subscriber (secondary) Cisco CallManager server.
•The primary Cisco Unity server continues answering all calls.
Reconnection Behavior
•The primary Cisco Unity server continues to be active, and the secondary Cisco Unity server continues to be inactive.
•If registering automatically with the publisher (primary) Cisco CallManager server is enabled, all voice messaging ports on the primary and secondary Cisco Unity servers unregister with the subscriber (secondary) Cisco CallManager server and register with the publisher (primary) Cisco CallManager server.
•If registering automatically with the publisher (primary) Cisco CallManager server is not enabled, all voice messaging ports on the primary and secondary Cisco Unity servers remain registered with the subscriber (secondary) Cisco CallManager server.
•The primary Cisco Unity server continues answering all calls.
The Subscriber Cisco CallManager Server Is Disconnected from the Network, Then Reconnected
In testing, this scenario was simulated by disabling the network interface card on the subscriber (secondary) Cisco CallManager server.
Disconnection Behavior
•The primary Cisco Unity server continues to be active, and the secondary Cisco Unity server continues to be inactive.
•All voice messaging ports on the primary and secondary Cisco Unity servers remain registered with the publisher (primary) Cisco CallManager server.
•The primary Cisco Unity server continues answering all calls.
Reconnection Behavior
•The primary Cisco Unity server continues to be active, and the secondary Cisco Unity server continues to be inactive.
•All voice messaging ports on the primary and secondary Cisco Unity servers remain registered with the publisher (primary) Cisco CallManager server.
•The primary Cisco Unity server continues answering all calls.
The Cisco CallManager Cluster Is Disconnected from the Network, Then Reconnected
In testing, this scenario was simulated by disabling the network interface card on all Cisco CallManager servers in the cluster.
Disconnection Behavior
•The primary Cisco Unity server continues to be active, and the secondary Cisco Unity server continues to be inactive.
•All voice messaging ports on the primary and secondary Cisco Unity servers unregister with the publisher (primary) Cisco CallManager server. They do not register with another Cisco CallManager server.
•Cisco Unity does not answer calls.
•Subscribers are not able to leave or listen to messages. External callers cannot leave messages for subscribers because phones will not forward calls to Cisco Unity.
•Subscribers calling Cisco Unity hear a fast busy tone.
•Subscribers on a Cisco Unity connected to another Cisco CallManager cluster can leave messages for subscribers of the disconnected cluster.
Reconnection Behavior
•The primary Cisco Unity server continues to be active, and the secondary Cisco Unity server continues to be inactive.
•All voice messaging ports on the primary and secondary Cisco Unity servers register with the publisher (primary) Cisco CallManager server.
•The primary Cisco Unity server answers all calls.
The Primary Domain Controller Is Disconnected from the Network, Then Reconnected
In testing, this scenario was simulated by disabling the network interface card on the primary domain controller.
Disconnection Behavior
•The primary server continues to be active, and the secondary server continues to be inactive.
•The primary server continues answering all calls.
•Subscribers are able to leave and listen to messages. External callers can leave messages for subscribers.
•The primary server handles directory synchronization for changes made to the Exchange 5.5 server.
•The primary server handles MWIs, event notification, and message notification.
Reconnection Behavior
•The primary server continues to be active, and the secondary server continues to be inactive.
•The primary server continues answering all calls.
•Subscribers are able to leave and listen to messages. External callers can leave messages for subscribers.
•The primary server handles directory synchronization, MWIs, event notification, and message notification.
The Backup Domain Controller Is Disconnected from the Network, Then Reconnected
In testing, this scenario was simulated by disabling the network interface card on the backup domain controller.
Disconnection Behavior
•The primary server continues to be active, and the secondary server continues to be inactive.
•The primary server continues answering all calls.
Reconnection Behavior
•The primary server continues to be active, and the secondary server continues to be inactive.
•The primary server continues answering all calls.
The Primary Domain Controller and Backup Domain Controller Are Disconnected from the Network, Then Reconnected
In testing, this scenario was simulated by disabling the network interface cards on the primary domain controller and the backup domain controller.
Disconnection Behavior
•The primary server continues to be active, and the secondary server continues to be inactive.
•The primary server continues answering all calls.
•Subscribers are able to leave and listen to messages. External callers can leave messages for subscribers.
•The primary server handles directory synchronization for changes made to the Exchange 5.5 server.
•The primary server handles MWIs, event notification, and message notification.
Reconnection Behavior
•The primary server continues to be active, and the secondary server continues to be inactive.
•The primary server continues answering all calls.
•Subscribers are able to leave and listen to messages. External callers can leave messages for subscribers.
•The primary server handles directory synchronization, MWIs, event notification, and message notification.
The Primary Domain Controller Is Disconnected from the Network, Then the Primary and Secondary Servers Are Restarted
In testing, this scenario was simulated by disabling the network interface card on the primary domain controller, then stopping and restarting the primary and secondary servers.
Restarting Behavior for Primary and Secondary Servers
•The primary and secondary servers both start.
•The primary server becomes active, and the secondary server becomes inactive.
•All voice messaging ports on the primary server register with the Cisco CallManager server.
•The primary server answers all calls.
•Subscribers are able to leave and listen to messages. External callers can leave messages for subscribers.
•The Node Manager services (AvCsNodeMgr.exe) on the primary and secondary servers send status to and receive status from each other.
•The Failover Monitors on the primary and secondary servers show that the primary server is active.
•The primary server handles directory synchronization for changes made to the Exchange 5.5 server.
•The primary server handles MWIs, event notification, and message notification.
The Primary Domain Controller and Backup Domain Controller Are Disconnected from the Network, Then the Primary and Secondary Servers Are Restarted
In testing, this scenario was simulated by disabling the network interface cards on the primary domain controller (PDC) and the backup domain controller (BDC), then stopping and restarting the primary and secondary servers.
Restarting Behavior for Primary and Secondary Servers
•The primary and secondary servers both start.
•The primary server becomes active, and the secondary server becomes inactive.
•All voice messaging ports on the primary server register with the Cisco CallManager server.
•The primary server answers all calls.
•Subscribers are able to leave and listen to messages. External callers can leave messages for subscribers.
•The Node Manager services (AvCsNodeMgr.exe) on the primary and secondary servers send status to and receive status from each other.
•The Failover Monitors on the primary and secondary servers show that the primary server is active.
•The primary server handles directory synchronization for changes made to the Exchange 5.5 server.
•The primary server handles MWIs, event notification, and message notification.
•Users cannot access the Cisco Unity Administrator or the ActiveAssistant. An error appears stating that the account is not associated with a subscriber.
After the PDC or the BDC is reconnected, users can access the Cisco Unity Administrator or the ActiveAssistant.
The Primary Server Crashes
In testing, this scenario was simulated by turning off power to the primary server.
Disconnection Behavior
•The secondary server answers all calls. Depending on network latency, this behavior may take a few minutes to begin.
•The Failover Monitor on the secondary server shows that the secondary server is active.
•Subscribers are able to leave and listen to messages. External callers can leave messages for subscribers.
•Messages, greetings, and other recordings made on the primary server but not replicated to the secondary server before the network outage are not available on the secondary server.
•The secondary server handles directory synchronization, MWIs, event notification, and message notification.
Reconnection Behavior Before Failback
•The primary server is inactive, and the secondary server remains active.
•The secondary server answers all calls.
•All voice messaging ports on the primary server remain unregistered with the Cisco CallManager server.
Reconnection Behavior After Failback
•When failback is manually initiated or when a scheduled failback occurs, the primary server becomes active and the secondary server becomes inactive.
•All voice messaging ports on the primary server register with the Cisco CallManager server.
•The primary server answers all calls.
•Subscribers are able to leave and listen to messages. External callers can leave messages for subscribers.
•The Node Manager services (AvCsNodeMgr.exe) on the primary and secondary servers send status to and receive status from each other.
•The Failover Monitors on the primary and secondary servers show that the primary server is active.
•Changes to the UnityDb database that occurred while the primary server was offline are replicated from the secondary server to the primary server.
•The primary server handles directory synchronization, MWIs, event notification, and message notification.
•Messages, greetings, and other recordings made on the primary server but not replicated to the secondary server before the server outage are replicated to the secondary server.
•Messages, greetings, and other recordings made on the secondary server during the server outage are replicated to the primary server.
The Secondary Server Crashes
In testing, this scenario was simulated by turning off power to the secondary server.
Disconnection Behavior
•The primary server continues answering all calls.
•Subscribers are able to leave and listen to messages. External callers can leave messages for subscribers.
•The Failover Monitor on the primary server shows that the primary server is active.
•The Replication Monitor in the SQL Enterprise Manager displays errors.
•UnityDb database replication between the primary and secondary servers stops.
•The primary server handles directory synchronization, MWIs, event notification, and message notification.
Reconnection Behavior
•The primary server remains active, and the secondary server becomes inactive.
•The primary server continues answering all calls.
•Subscribers are able to leave and listen to messages. External callers can leave messages for subscribers.
•All voice messaging ports on the secondary server register with the Cisco CallManager server.
•The Node Manager services (AvCsNodeMgr.exe) on the primary and secondary servers send status to and receive status from each other.
•The Failover Monitors on the primary and secondary servers show that the primary server is active.
•Changes to the UnityDb database that occurred while the secondary server was offline are replicated from the primary server to the secondary server.
•The primary server continues handling directory synchronization, MWIs, event notification, and message notification.
•Messages, greetings, and other recordings made on the primary server but not replicated to the secondary server before the server outage are replicated to the secondary server.
•Messages, greetings, and other recordings made on the primary server during the server outage are replicated to the secondary server.
•For Cisco Unity 3.1(3) and earlier, if the server outage lasted more than five minutes, the Distribution agent on the primary server may need to be manually started to resume UnityDb database replication when the secondary server is online again. See the "Restarting UnityDb Database Replication and Configuring the Distribution Agent Schedule" section.
The Primary and Secondary Servers Crash Simultaneously
In testing, this scenario was simulated by turning off power to the primary and secondary servers at the same time.
Disconnection Behavior
•There is no voice messaging functionality. Neither the primary nor secondary server answers calls.
•Subscribers are not able to leave or listen to messages. External callers cannot leave messages for subscribers.
•Callers trying to leave messages hear a fast busy tone instead of the personal greeting for the subscriber.
•Subscribers can call other subscribers directly and talk to each other.
•Neither server initiates directory synchronization, MWIs, event notification, or message notification.
Reconnection Behavior (Only the Primary Server Is Reconnected)
•The Failover Monitor on the primary server shows that the primary server is active.
•All voice messaging ports on the primary server register with the Cisco CallManager server.
•The primary server answers all calls.
•Subscribers are able to leave and listen to messages. External callers can leave messages for subscribers.
•Messages, greetings, and other recordings made on the primary server but not replicated to the secondary server before the server outage are not replicated to the secondary server because it is offline.
•Changes to the UnityDb database that occurred before the server outage and were not replicated to the secondary server are not replicated because the secondary server is offline.
•The primary server handles directory synchronization, MWIs, event notification, and message notification.
Reconnection Behavior (the Secondary Server Is Also Reconnected)
•The Failover Monitors on the primary and secondary servers show that the primary server is active and the secondary server is inactive.
•All voice messaging ports on the secondary server register with the Cisco CallManager server.
•The primary server continues answering all calls.
•The Node Manager services (AvCsNodeMgr.exe) on the primary and secondary servers send status to and receive status from each other.
•Changes to the UnityDb database that occurred while the secondary server was offline are replicated from the primary server to the secondary server.
•For Cisco Unity 3.1(3) and earlier, if the server outage lasted more than five minutes, the Distribution agent on the primary server may need to be manually started to resume UnityDb database replication when the network outage is resolved. See the "Restarting UnityDb Database Replication and Configuring the Distribution Agent Schedule" section.
•The primary server continues handling directory synchronization, MWIs, event notification, and message notification.
•Messages, greetings, and other recordings made on the primary server but not replicated to the secondary server before the server outage are replicated to the secondary server.
•Messages, greetings, and other recordings made on the primary server while the secondary server was offline are replicated to the secondary server.
The Primary Server Is Disconnected from the Network, Then the Exchange 5.5 Server That Has the Cisco Unity Messaging System Mailbox Is Disconnected from the Network
In testing, this scenario was simulated by disabling the network interface card on the primary server, then on the Exchange 5.5 server.
Disconnection Behavior (Only the Primary Server Is Disconnected)
•The secondary server answers all calls.
•Subscribers are able to leave and listen to messages. External callers can leave messages for subscribers.
•All voice messaging ports on the primary server unregister with the Cisco CallManager server.
•The Node Manager services (AvCsNodeMgr.exe) on the primary and secondary servers no longer receive status from each other.
•The Failover Monitor on the primary server shows that the primary server is active. The Failover Monitor on the secondary server shows that the secondary server is active.
•Messages, greetings, and other recordings made on the primary server but not replicated to the secondary server before the network outage are not available on the secondary server.
•The Replication Monitor in the SQL Enterprise Manager displays errors.
•UnityDb database replication between the primary and secondary servers stops.
•The secondary server handles directory synchronization, MWIs, event notification, and message notification.
Disconnection Behavior (the Exchange 5.5 Server Is Also Disconnected)
•All subscribers hear the Unity Messaging Repository (UMR) conversation when they log on to Cisco Unity.
•External callers can leave messages for subscribers. The new messages are stored in the UnityMTA folder on the secondary server.
•Subscribers homed on the same Cisco Unity server can leave messages for each other by dialing an extension or logging on to Cisco Unity. The new messages are stored in the UnityMTA folder on the secondary server.
•Subscribers can call the Cisco Unity server and listen to their new messages stored in the UnityMTA folder on the secondary server. Messages stored on the Exchange 5.5 server before the network outage are not available.
•The secondary server handles directory synchronization.
•MWIs, event notification, and message notification are not handled.
Reconnection Behavior When the Exchange 5.5 Server Is Reconnected and the Primary Server Remains Disconnected
•Subscribers who log on to Cisco Unity no longer hear the UMR conversation, but hear the appropriate conversation.
•Messages stored in the UnityMTA folder on the secondary server are delivered to the appropriate subscriber Inboxes.
•The secondary server sets MWIs for subscribers who have unheard messages stored on the Exchange 5.5 server.
•External callers and subscribers can leave messages for subscribers. The messages are stored on the Exchange 5.5 server.
•The secondary server handles directory synchronization, MWIs, event notification, and message notification.
Reconnection Behavior After the Exchange 5.5 Server Is Reconnected, Then the Primary Server Is Reconnected
•The primary server becomes active, and the secondary server becomes inactive.
•All voice messaging ports on the primary server register with the Cisco CallManager server.
•The primary server answers all calls.
•Subscribers are able to leave and listen to messages. External callers can leave messages for subscribers.
•The Node Manager services (AvCsNodeMgr.exe) on the primary and secondary servers send status to and receive status from each other.
•The Failover Monitors on the primary and secondary servers show that the primary server is active.
•Changes to the UnityDb database that occurred while the primary server was offline are replicated from the secondary server to the primary server.
•The primary server handles directory synchronization, MWIs, event notification, and message notification.
•Messages, greetings, and other recordings made on the primary server but not replicated to the secondary server before the network outage are replicated to the secondary server.
•Messages, greetings, and other recordings made on the secondary server during the network outage are replicated to the primary server.
Reconnection Behavior When the Primary Server Is Reconnected and the Exchange 5.5 Server Remains Disconnected
•The primary server becomes active, and the secondary server becomes inactive.
•All voice messaging ports on the primary server register with the Cisco CallManager server.
•The primary server answers all calls.
•All subscribers hear the UMR conversation when they log on to Cisco Unity.
•The Node Manager services (AvCsNodeMgr.exe) on the primary and secondary servers send status to and receive status from each other.
•The Failover Monitors on the primary and secondary servers show that the primary server is active.
•Changes to the UnityDb database that occurred while the primary server was offline are replicated from the secondary server to the primary server.
•The primary server handles directory synchronization, MWIs, event notification, and message notification.
•Messages, greetings, and other recordings made on the primary server but not replicated to the secondary server before the network outage are replicated to the secondary server.
•Messages, greetings, and other recordings made on the secondary server during the network outage are replicated to the primary server.
Reconnection Behavior After the Primary Server Is Reconnected, Then the Exchange 5.5 Server Is Reconnected
•Subscribers who log on to Cisco Unity no longer hear the UMR conversation, but hear the appropriate conversation.
•Messages stored in the UnityMTA folder on the primary server are delivered to the appropriate subscriber Inboxes.
•The primary server sets MWIs for subscribers who have unheard messages stored on the Exchange 5.5 server.
•External callers and subscribers can leave messages for subscribers. The messages are stored on the Exchange 5.5 server.
•The primary server handles directory synchronization, MWIs, event notification, and message notification.
The Exchange 5.5 Server That Has the Cisco Unity Messaging System Mailbox Is Disconnected from the Network, Then the Primary Server Is Disconnected from the Network
In testing, this scenario was simulated by disabling the network interface card on the Exchange 5.5 server, then on the primary server.
Disconnection Behavior (Only the Exchange 5.5 Server Is Disconnected)
•The primary server continues to be active, and the secondary server continues to be inactive.
•The primary server continues answering all calls.
•All subscribers hear the Unity Messaging Repository (UMR) conversation when they log on to Cisco Unity.
•External callers can leave messages for subscribers. The new messages are stored in the UnityMTA folder on the primary server.
•Subscribers homed on the same Cisco Unity server can leave messages for each other by dialing an extension or logging on to Cisco Unity. The new messages are stored in the UnityMTA folder on the primary server.
•Subscribers can call the Cisco Unity server and listen to their new messages stored in the UnityMTA folder on the primary server. Messages stored on the Exchange 5.5 server before the network outage are not available.
•The primary server handles directory synchronization and file replication.
•MWIs, event notification, and message notification are not handled.
Disconnection Behavior (the Primary Server Is Also Disconnected)
•The secondary server answers all calls.
•The Failover Monitor on the primary server shows that the primary server is active. The Failover Monitor on the secondary server shows that the secondary server is active.
•All subscribers hear the UMR conversation when they log on to Cisco Unity.
•External callers can leave messages for subscribers. The new messages are stored in the UnityMTA folder on the secondary server.
•Subscribers homed on the same Cisco Unity server can leave messages for each other by dialing an extension or logging on to Cisco Unity. The new messages are stored in the UnityMTA folder on the secondary server.
•Subscribers can call the Cisco Unity server and listen to their new messages stored in the UnityMTA folder on the secondary server. Messages stored on the Exchange 5.5 server before the network outage are not available.
•MWIs, event notification, and message notification are not handled.
Reconnection Behavior When the Primary Server Is Reconnected and the Exchange 5.5 Server Remains Disconnected
•The primary server becomes active, and the secondary server becomes inactive.
•All voice messaging ports on the primary server register with the Cisco CallManager server.
•The primary server answers all calls.
•All subscribers hear the UMR conversation when they log on to Cisco Unity.
•The Node Manager services (AvCsNodeMgr.exe) on the primary and secondary servers send status to and receive status from each other.
•The Failover Monitors on the primary and secondary servers show that the primary server is active.
•Changes to the UnityDb database that occurred while the primary server was offline are replicated from the secondary server to the primary server.
•The primary server handles directory synchronization, MWIs, event notification, and message notification.
•Messages, greetings, and other recordings made on the primary server but not replicated to the secondary server before the network outage are replicated to the secondary server.
•Messages, greetings, and other recordings made on the secondary server during the network outage are replicated to the primary server.
Reconnection Behavior After the Primary Server Is Reconnected, Then the Exchange 5.5 Server Is Reconnected
•Subscribers who log on to Cisco Unity no longer hear the UMR conversation, but hear the appropriate conversation.
•Messages stored in the UnityMTA folder on the primary server are delivered to the appropriate subscriber Inboxes.
•The primary server sets MWIs for subscribers who have unheard messages stored on the Exchange 5.5 server.
•External callers and subscribers can leave messages for subscribers. The messages are stored on the Exchange 5.5 server.
•The primary server handles directory synchronization, MWIs, event notification, and message notification.
Reconnection Behavior When the Exchange 5.5 Server Is Reconnected and the Primary Server Remains Disconnected
•Subscribers who log on to Cisco Unity no longer hear the UMR conversation, but hear the appropriate conversation.
•Messages stored in the UnityMTA folder on the secondary server are delivered to the appropriate subscriber Inboxes.
•The secondary server sets MWIs for subscribers who have unheard messages stored on the Exchange 5.5 server.
•External callers and subscribers can leave messages for subscribers. The messages are stored on the Exchange 5.5 server.
•The secondary server handles directory synchronization, MWIs, event notification, and message notification.
Reconnection Behavior After the Exchange 5.5 Server Is Reconnected, Then the Primary Server Is Reconnected
•The primary server becomes active, and the secondary server becomes inactive.
•All voice messaging ports on the primary server register with the Cisco CallManager server.
•The primary server answers all calls.
•Subscribers are able to leave and listen to messages. External callers can leave messages for subscribers
•The Node Manager services (AvCsNodeMgr.exe) on the primary and secondary servers send status to and receive status from each other.
•The Failover Monitors on the primary and secondary servers show that the primary server is active.
•Changes to the UnityDb database that occurred while the primary server was offline are replicated from the secondary server to the primary server.
•The primary server handles directory synchronization, MWIs, event notification, and message notification.
•Messages, greetings, and other recordings made on the primary server but not replicated to the secondary server before the network outage are replicated to the secondary server.
•Messages, greetings, and other recordings made on the secondary server during the network outage are replicated to the primary server.
The Exchange 5.5 Server That Has the Cisco Unity Messaging System Mailbox and the Primary Server Simultaneously Crash, Then Are Reconnected
In testing, this scenario was simulated by turning off power to the Exchange 5.5 server and to the primary server at the same time.
Disconnection Behavior
•The secondary server answers all calls.
•All subscribers hear the Unity Messaging Repository (UMR) conversation when they log on to Cisco Unity.
•External callers can leave messages for subscribers. The new messages are stored in the UnityMTA folder on the secondary server.
•Subscribers homed on the same Cisco Unity server can leave messages for each other by dialing an extension or logging on to Cisco Unity. The new messages are stored in the UnityMTA folder on the secondary server.
•Subscribers can call the Cisco Unity server and listen to their new messages stored in the UnityMTA folder on the secondary server. Messages stored on the Exchange 5.5 server before the network outage are not available.
•MWIs, event notification, and message notification are not handled.
Reconnection Behavior When the Exchange 5.5 Server Is Reconnected and the Primary Server Remains Disconnected
•Subscribers who log on to Cisco Unity no longer hear the UMR conversation, but hear the appropriate conversation.
•Messages stored in the UnityMTA folder on the secondary server are delivered to the appropriate subscriber Inboxes.
•The secondary server sets MWIs for subscribers who have unheard messages stored on the Exchange 5.5 server.
•External callers and subscribers can leave messages for subscribers. The messages are stored on the Exchange 5.5 server.
•The secondary server handles directory synchronization, MWIs, event notification, and message notification.
Reconnection Behavior After the Exchange 5.5 Server Is Reconnected, Then the Primary Server Is Reconnected
•The primary server is inactive, and the secondary server remains active.
•The secondary server answers all calls.
•When failback is manually initiated or when a scheduled failback occurs, the primary server becomes active and the secondary server becomes inactive.
•When the primary server becomes active, all voice messaging ports on the primary server register with the Cisco CallManager server.
•When the primary server becomes active, it answers all calls.
•Subscribers are able to leave and listen to messages. External callers can leave messages for subscribers.
•The Node Manager services (AvCsNodeMgr.exe) on the primary and secondary servers send status to and receive status from each other.
•When the primary server becomes active, the Failover Monitors on the primary and secondary servers show that the primary server is active.
•Changes to the UnityDb database that occurred while the primary server was offline are replicated from the secondary server to the primary server.
•When the primary server becomes active, it handles directory synchronization, MWIs, event notification, and message notification.
•Messages, greetings, and other recordings made on the primary server but not replicated to the secondary server before the network outage are replicated to the secondary server.
•Messages, greetings, and other recordings made on the secondary server during the network outage are replicated to the primary server.
Reconnection Behavior When the Primary Server Is Reconnected and the Exchange 5.5 Server Remains Disconnected
•The Cisco Unity service (AvCsMgr.exe) on the primary server does not start.
•The secondary server continues to be active.
•The secondary server continues answering all calls.
Reconnection Behavior After the Primary Server Is Reconnected, Then the Exchange 5.5 Server Is Reconnected and the Cisco Unity Service (AvCsMgr.exe) on the Primary Server Is Manually Started
•The primary server is inactive, and the secondary server remains active.
•When failback is manually initiated or when a scheduled failback occurs, the primary server becomes active and the secondary server becomes inactive.
•When the primary server becomes active, all voice messaging ports on the primary server register with the Cisco CallManager server.
•When the primary server becomes active, it answers all calls. Until then, the secondary server answers all calls.
•Subscribers are able to leave and listen to messages. External callers can leave messages for subscribers. The messages are stored on the Exchange 5.5 server.
•Subscribers who log on to Cisco Unity no longer hear the UMR conversation, but hear the appropriate conversation.
•Messages stored in the UnityMTA folder on the secondary server are delivered to the appropriate subscriber Inboxes.
•The primary server sets MWIs for subscribers who have unheard messages stored on the Exchange 5.5 server.
•The Node Manager services (AvCsNodeMgr.exe) on the primary and secondary servers send status to and receive status from each other.
•The Failover Monitors on the primary and secondary servers show that the primary server is active.
•Changes to the UnityDb database that occurred while the primary server was offline are replicated from the secondary server to the primary server.
•The primary server handles directory synchronization, MWIs, event notification, and message notification.
•Messages, greetings, and other recordings made on the primary server but not replicated to the secondary server before the network outage are replicated to the secondary server.
•Messages, greetings, and other recordings made on the secondary server while the primary server was inactive are replicated to the primary server.
Restarting UnityDb Database Replication and Configuring the Distribution Agent Schedule
On a Cisco Unity system with version 3.1(3) or earlier, if the network outage lasted more than five minutes, the Distribution agent on the primary server may need to be manually started to resume UnityDb database replication when the primary server becomes active again. Do the following three procedures in the order listed.
On a Cisco Unity system with version 3.1(4) or later, UnityDb database replication restarts automatically, and the following procedures are not necessary.
To restart UnityDb database replication
Step 1 On the primary server, on the Windows Start menu, click Microsoft SQL Server > Enterprise Manager.
Step 2 In the Tree pane on the left, expand the Primary Server node, then expand the Replication Monitor node.
Step 3 Expand the Publisher directory.
Step 4 Click UnityDB Publication, then right-click UnityDB Publication and click Properties.
Step 5 In the Properties dialog box, click the General tab.
Step 6 Confirm that the Subscriptions Never Expire check box is checked.
Step 7 Click the Subscriptions tab. Confirm that UnityDb on the secondary server appears as a subscription.
Step 8 Click Reinitialize, and click Yes.
Step 9 Click OK to close the Properties dialog box.
Step 10 In the right pane of the SQL Server Enterprise Manager window, right-click the Snapshot agent and click Start Agent.
To change the Distribution agent schedule
Step 1 In the right pane of the SQL Server Enterprise Manager window, right-click the Distribution agent (<Secondary server name>:UnityDb) and click Agent Properties.
Step 2 In the Agent Properties dialog box, click the Schedules tab.
Step 3 Click Edit.
Step 4 Check the Recurring check box, and click Change.
Step 5 Enter the following values in the applicable fields:
Occurs
|
Daily
|
Daily
|
Every 1 Day
|
Daily Frequency
|
Occurs Every 1 Minute
|
Duration
|
No End Date
|
Step 6 Click OK to close the Change Schedule dialog box.
Step 7 Click OK to close the Edit Properties dialog box.
Step 8 Click OK to close the Agent Properties dialog box.
Step 9 Close the SQL Server Enterprise Manager.
To confirm that the secondary server accepts the changes
Step 1 On the secondary server, right-click the Cisco Unity icon in the system tray, and click Stop to stop the Cisco Unity service.
Step 2 Right-click the Cisco Unity icon in the system tray, and click Start to restart the Cisco Unity service.
Step 3 Confirm that Cisco Unity starts.
Step 4 On the Windows Start menu, click Programs > Administrative Tools > Services.
Step 5 In the Services window, confirm that the following services display the status "Started" in the Started column:
•AvCsGateway
•AvCsMgr
•AvCsNodeMgr
•AvDirChangeWriter
•AvRepDirSvrSvc
•AvUMRSyncSvr
Feedback
