Cisco Unity Connection

Introduction

This document describes a problem encountered with Cisco Unity Connection after you reinstate a replication and also describes the process that is used in order to resolve the problem.

Prerequisites

Requirements

Cisco recommends that you have knowledge of Cisco Unity Connection.

Components Used

The information in this document is based on Cisco Unity Connection Version 8.x.

The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.

Problem

The Cisco Unity Connection Cluster Peer status on the CLI shows as Disconnected.

This is seen on the Publisher:

admin:show cuc cluster status

Server Name  Member ID  Server State   Internal State            Reason
-----------  ---------  -------------  -----------------------   ------
cucpub           0      Primary        Pri Active Disconnected   Normal
cucsub           1      Disconnected   Unknown                   Unknown

This is seen on the Subscriber:

admin:show cuc cluster status

Server Name  Member ID  Server State  Internal State           Reason
-----------  ---------  ------------  -----------------------  ------
cucpub           0      Primary       Pri Active Disconnected  Normal
cucsub           1      Secondary     Sec Active               Normal

Solution

Complete these steps in order to resolve the problem:

1. Shut down the Subscriber.
2. Restart the Publisher, and wait for it to come back online.
3. Wait until you can reach the admin web page, and then place a call to voicemail.
4. Start the Subscriber.

If the issue remains, you must collect the outputs of these commands from both nodes:

• show cuc cluster status
• utils dbreplication runtimestate
• utils diagnose module validate_network
• utils ntp status

You must also collect these logs from both nodes with use of the Real-Time Monitoring Tool (RTMT), from the time of initial Subscriber shutdown until it comes back online:

• Connection Server Role Manager
• Event Viewer - Application Log
• Event Viewer - System Log
• IPT Platform Cluster Manager Logs

Once the outputs and logs are collected, search the data for the source of the problem.

Note: This process can also be used when the Publisher repeatedly attempts to run a Split Brain Resolution without completion.