Configuring a Cisco Unity Connection Cluster

Posted on by Admin

Related Post

Configuring a Cisco Unity Connection Cluster

Task List for Configuring a Cisco Unity Connection Cluster

Caution Configure a Cisco Unity Connection cluster only after you have installed the publisher server and set up administrator workstations according to instructions in the Installation Guide for Cisco Unity Connection Release 9.x.

Do the following tasks in the order listed to configure a Cisco Unity Connection cluster correctly:

1. On the publisher server, configure the Connection cluster by adding the host name or IP address of the subscriber server and enable access to alert logs for when the publisher server is not functioning. See the “Configuring the Cisco Unity Connection Cluster” section.

2. Set up alert notification of server status changes. See the “Setting Up Alert Notification of Server Status Changes in Cisco Unity Connection” section.

3. Optional: Adjust the cluster settings. See the “Customizing Cluster Settings in Connection” section.

4. Continue with the next task in “Part 3: Configuring the Cluster, and Installing and Configuring the Subscriber Connection Server” in the “Task List for Installing a Cisco Unity Connection 9.x System with a Connection Cluster Configured” in the Installation Guide for Cisco Unity Connection Release 9.x .

Configuring the Cisco Unity Connection Cluster

You configure the cluster after you have installed the publisher server.

Do the two procedures in this section in the order listed.

NoteThe Cisco Unity Connection cluster feature is not supported for use with Cisco Unified Communications Manager Business Edition 3000 and Cisco Unified Communications Manager Business Edition 5000. The Cisco Unity Connection cluster feature is not supported for use with Cisco Unified Communications Manager Business Edition 3000 and Cisco Unified Communications Manager Business Edition 5000.

To Configure the Cisco Unity Connection 9.x Cluster

Step 1 On the publisher server, sign in to Cisco Unity Connection Administration.

Step 2 In Connection Administration, expand System Settings , then select Cluster .

Step 3 On the Find and List Servers page, select Add New .

Step 4 On the New Server Configuration page, in the Host Name/IP Address field, enter the host name or IP address of the second server in the cluster.

Step 5 Optional: In the MAC Address field, enter the MAC address of the second server.

Step 6 In the Description field, enter Server 2 or another description for the second server.

Step 7 Select Save .

To Enable Access to Alert Logs for When the 9.x Publisher Server Is Not Functioning

Step 1 In Connection Administration, expand System Settings , then select Service Parameters .

Step 2 On the Service Parameters page, in the Server field, select the publisher server.

Step 3 In the Service field, select Cisco AMC Service .

Step 4 In the Failover Collector field, select the subscriber server.

Step 5 Select Save .

Setting Up Alert Notification of Server Status Changes in Cisco Unity Connection

We recommend that you configure the Cisco Unified Real-Time Monitoring Tool to send notifications for the following Cisco Unity Connection alerts:

  • AutoFailbackFailed
  • AutoFailbackSucceeded
  • AutoFailoverFailed
  • AutoFailoverSucceeded
  • NoConnectionToPeer
  • SbrFailed

For instructions on setting up alert notification for Connection alerts, see the “Working with Alerts” chapter (in the “Alerts” part) of the Cisco Unified Real-Time Monitoring Tool Administration Guide at http://www.cisco.com/en/US/products/ps6509/prod_maintenance_guides_list.html .

Customizing Cluster Settings in Connection

To Customize Cluster Settings in 9.x

Step 1 On the publisher server, sign in to Cisco Unity Connection Administration.

Step 2 In Connection Administration, expand System Settings > Advanced , then select Cluster Configuration .

Step 3 On the Cluster Configuration page, change the settings as applicable:

Deactivate server with
Secondary status when
replication is backlogged

When this check box is checked, a replication backlog condition causes the server with Secondary status to change to Deactivated.

When this check box is unchecked, a replication backlog condition does not cause the server with Secondary status to change status.

The default is unchecked.
Automatically change
server status when the
publisher server fails

When this check box is checked, a failure of the publisher server causes the server with Secondary status to change automatically to Primary.

When this check box is unchecked, a failure of the publisher server does not cause the server with Secondary status to change status. The status of the server must be changed manually.

The default is checked.

Step 4 Select Save .

More Details: http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/9x/cluster_administration/guide/9xcuccagx/9xcuccag005.html