- The 65+ best Black Friday TV deals 2024: Early sales live now
- Why this $60 Android Auto wireless adapter is my favorite tech accessory this year
- Red Hat Enterprise Linux 9.5 gains security, networking upgrades
- SUSE unveils major rebranding, and a new AI platform that protects your data
- One of the most immersive speakers I've tested is not made by Sonos or JBL (and it's on sale)
Configuring the Unity Connection 10.x Cluster
Configuring the Unity Connection 10.x 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.
To Configure the Cisco Unity Connection 10.x Cluster
Step 1 On the publisher server, sign in to Cisco Unity Connection Administration.
Step 2 In Unity 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
Customizing Cluster Settings in Unity Connection 10.x
To Customize Cluster Settings in 10.x
Step 1 On the publisher server, sign in to Cisco Unity Connection Administration.
Step 2 In Unity 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
To Enable Access to Alert Logs When the 10.x Publisher Server is Not Functioning
Step 1 In Unity 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 Unity Connection 10.x
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 Unity 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 .
To Manually Change an 10.x Server from Secondary Status to Primary Status
Step 1 Sign in to Cisco Unity Connection Serviceability.
Step 2 From the Tools menu, select Cluster Management .
Step 3 On the Cluster Management page, under Server Manager, in the Change Server Status column for the server with Secondary status, select Make Primary .
Step 4 When prompted to confirm changing the server status, select OK .
The Server Status column displays the changed status when the change is complete.
Note The server that originally had Primary status automatically changes to Secondary status.
To Manually Change an 10.x Server from Secondary Status to Deactivated Status
Step 1 Sign in to the Real-Time Monitoring Tool (RTMT).
Step 2 From the Cisco Unity Connection menu, select Port Monitor . The Port Monitor tool appears in the right pane.
Step 3 In the Node field, select the server with Secondary status.
Step 4 In the right pane, select Start Polling .
Step 5 Note whether any voice messaging ports are currently handling calls for the server.
Step 6 Sign in to Cisco Unity Connection Serviceability.
Step 7 From the Tools menu, select Cluster Management .
Step 8 If no voice messaging ports are currently handling calls for the server, skip to Step 9.
If there are voice messaging ports that are currently handling calls for the server, on the Cluster Management page, under Change Port Status, select Stop Taking Calls for the server, then wait until RTMT shows that all ports for the server are idle.
Step 9 On the Cluster Management page, under Server Manager, in the Change Server Status column for the server with Secondary status, select Deactivate .
Caution Deactivating a server will terminate all calls that the ports for the server are handling.
Step 10 When prompted to confirm changing the server status, select OK .
The Server Status column displays the changed status when the change is complete.
To Manually Activate an 10.x Server with Deactivated Status
Step 1 Sign in to Cisco Unity Connection Serviceability.
Step 2 From the Tools menu, select Cluster Management .
Step 3 On the Cluster Management page, under Server Manager, in the Change Server Status column for the server with Deactivated status, select Activate .
Step 4 When prompted to confirm changing the server status, select OK .
The Server Status column displays the changed status when the change is complete.
Stopping All Ports on Unity Connection 10.x from Taking New Calls
Do the procedure in this section to stop all ports on a server from taking any new calls. Calls in progress continue until the callers hang up.
Tip Use the Port Monitor page in the Real-Time Monitoring Tool (RTMT) to determine whether any ports are currently handling calls for the server.
To Stop All Ports on an 10.x Server from Taking New Calls
Step 1 Sign in to Cisco Unity Connection Serviceability.
Step 2 From the Tools menu, select Cluster Management .
Step 3 On the Cluster Management page, under Port Manager, in the Ports in Service column, select Stop Taking Calls for the server.
Restarting All Ports on Unity Connection 10.x to Take Calls
Do the procedure in this section to let ports on a server take calls again after they were stopped.
To Restart All Ports on Unity Connection 10.x to Take Calls
Step 1 Sign in to Cisco Unity Connection Serviceability.
Step 2 From the Tools menu, select Cluster Management .
Step 3 On the Cluster Management page, under Port Manager, in the Ports in Service column, select Take Calls for the server.
Shutting Down a Unity Connection 10.x Server
When a Cisco Unity Connection server has Primary or Secondary status, it is handling voice messaging traffic and cluster replication. We do not recommend shutting down a Unity Connection server while it is has Primary or Secondary status because calls in progress and replication may be abruptly terminated.
If you want to shut down a server (for example, to perform maintenance), we recommend that you do the procedure in this section during nonbusiness hours when voice messaging traffic will be light. Note that the remaining server, if it has Primary or Secondary status, handles all system voice messaging functions and maintains the Unity Connection database.
To Shut Down a 10.x Server
Step 1 On the server that will not be shut down, sign in to Cisco Unity Connection Serviceability.
Step 2 From the Tools menu, select Cluster Management .
Step 3 On the Cluster Management page, locate the server that you want to shut down.
Step 4 If the server that you want to shut down has Secondary status, skip to Step 5.
If the server that you want to shut down has Primary status, change the status:
- In the Change Server Status column for the server with Secondary status, select Make Primary .
- When prompted to confirm changing the server status, select OK .
- Confirm that the Server Status column indicates that the server now has Primary status and that the server you want to shut down has Secondary status.
Step 5 On the server with Secondary status (the one you want to shut down), change the status:
- Sign in to the Real-Time Monitoring Tool (RTMT).
- From the Cisco Unity Connection menu, select Port Monitor . The Port Monitor tool appears in the right pane.
- In the Node field, select the server with Secondary status.
- In the right pane, select Start Polling .
- Note whether any voice messaging ports are currently handling calls for the server.
- If no voice messaging ports are currently handling calls for the server, skip to Step 5g.
If there are voice messaging ports that are currently handling calls for the server, on the Cluster Management page, under Change Port Status, select Stop Taking Calls for the server, then wait until RTMT shows that all ports for the server are idle.
- On the Cluster Management page, under Server Manager, in the Change Server Status column for the server with Secondary status, select Deactivate .
Caution Deactivating a server will terminate all calls that the ports for the server are handling.
- When prompted to confirm changing the server status, select OK .
- Confirm that the Server Status column indicates that the server now has Deactivated status.
Step 6 Shut down the server that you deactivated.
In Cisco Unity Connection Serviceability on the server that is running, the Server Status column shows that the server you shut down has Not Functioning status.
