Accepted Solutions
Hi Uday,
The Cluster in Unity Connection acts differently than a CUCM cluster, so the answers to your question are;
Yes & Yes
How a Cluster Works in Cisco Unity Connection
The Cisco Unity Connection cluster feature provides high availability voice messaging through two Connection servers that are configured in a cluster. Under normal conditions, the Connection servers are both active so that:
•
The cluster can be assigned a DNS name that is shared by the Connection servers.
•Clients such as email applications and the web tools available through the Cisco Personal Communications Assistant (PCA) can connect to either Connection server.
•Phone systems can send calls to either Connection server.
•Incoming phone traffic load is balanced between the Connection servers by the phone system, PIMG/TIMG units, or other gateways that are required for the phone system integration.
Each server in the cluster is responsible for handling a share of the incoming calls for the cluster (answering phone calls and taking messages). The server with Primary status is responsible for the following functions:
•Homing and publishing the database and message store, which are both replicated to the other server.
•Sending message notifications and MWI requests (the Connection Notifier service is activated).
•Sending SMTP notifications and VPIM messages (the Connection Message Transfer Agent service is activated).
When one of the servers stops functioning (for example, when it is shut down for maintenance), the remaining server assumes responsibility for handling all incoming calls for the cluster. The remaining server also assumes responsibility for the database and message store, which are both replicated to the other server when the connection and its functionality are restored.
When the server that stopped functioning is able to resume its normal functions and is activated, it resumes responsibility for handling its share of incoming calls for the cluster.
To monitor the status of the servers, the Connection Server Role Manager service runs in Cisco Unity Connection Serviceability on both servers. This service performs the following functions:
•Starts the applicable services on each server, depending on server status.
•Determines whether critical processes (such as voice message processing, database replication, and message store replication) are functioning normally.
•Initiates changes to server status when the server with Primary status is not functioning or when critical services are not running.
Note the following limitations when the publisher server is not functioning:
•If the Connection cluster is integrated with an LDAP directory, directory synchronization does not occur, although authentication continues to work when only the subscriber server is functioning. When the publisher server is functioning again, directory synchronization resumes.
•If a Digital Network includes the Connection cluster, directory updates do not occur, although messages continue to be sent to and from the cluster when only the subscriber server is functioning. When the publisher server is functioning again, directory updates resume.
About the Publisher Server
The first Cisco Unity Connection server that is configured in the cluster is the publisher server. The Cluster Management page in Cisco Unity Connection Serviceability identifies the publisher server.
The publisher server assumes responsibility for publishing the database and message store when the cluster is functioning normally.
When the publisher server does not have Primary status (for example, when the administrator manually changes the status of the other server to Primary, which automatically changes the status of the publisher server to Secondary), the other server assumes responsibility for publishing the database and message store.
The publisher server cannot be removed from the cluster.
Cheers!
Rob
"Show a little faith, there's magic in the night" - Springsteen
Hi Uday,
The Cluster in Unity Connection acts differently than a CUCM cluster, so the answers to your question are;
Yes & Yes
How a Cluster Works in Cisco Unity Connection
The Cisco Unity Connection cluster feature provides high availability voice messaging through two Connection servers that are configured in a cluster. Under normal conditions, the Connection servers are both active so that:
•The cluster can be assigned a DNS name that is shared by the Connection servers.
•Clients such as email applications and the web tools available through the Cisco Personal Communications Assistant (PCA) can connect to either Connection server.
•Phone systems can send calls to either Connection server.
•Incoming phone traffic load is balanced between the Connection servers by the phone system, PIMG/TIMG units, or other gateways that are required for the phone system integration.
Each server in the cluster is responsible for handling a share of the incoming calls for the cluster (answering phone calls and taking messages). The server with Primary status is responsible for the following functions:
•Homing and publishing the database and message store, which are both replicated to the other server.
•Sending message notifications and MWI requests (the Connection Notifier service is activated).
•Sending SMTP notifications and VPIM messages (the Connection Message Transfer Agent service is activated).
When one of the servers stops functioning (for example, when it is shut down for maintenance), the remaining server assumes responsibility for handling all incoming calls for the cluster. The remaining server also assumes responsibility for the database and message store, which are both replicated to the other server when the connection and its functionality are restored.
When the server that stopped functioning is able to resume its normal functions and is activated, it resumes responsibility for handling its share of incoming calls for the cluster.
To monitor the status of the servers, the Connection Server Role Manager service runs in Cisco Unity Connection Serviceability on both servers. This service performs the following functions:
•Starts the applicable services on each server, depending on server status.
•Determines whether critical processes (such as voice message processing, database replication, and message store replication) are functioning normally.
•Initiates changes to server status when the server with Primary status is not functioning or when critical services are not running.
Note the following limitations when the publisher server is not functioning:
•If the Connection cluster is integrated with an LDAP directory, directory synchronization does not occur, although authentication continues to work when only the subscriber server is functioning. When the publisher server is functioning again, directory synchronization resumes.
•If a Digital Network includes the Connection cluster, directory updates do not occur, although messages continue to be sent to and from the cluster when only the subscriber server is functioning. When the publisher server is functioning again, directory updates resume.
About the Publisher Server
The first Cisco Unity Connection server that is configured in the cluster is the publisher server. The Cluster Management page in Cisco Unity Connection Serviceability identifies the publisher server.
The publisher server assumes responsibility for publishing the database and message store when the cluster is functioning normally.
When the publisher server does not have Primary status (for example, when the administrator manually changes the status of the other server to Primary, which automatically changes the status of the publisher server to Secondary), the other server assumes responsibility for publishing the database and message store.
The publisher server cannot be removed from the cluster.
Cheers!
Rob
"Show a little faith, there's magic in the night" - Springsteen
