Cisco Unity Connection Server 12.x Maintenance Guide

A comprehensive maintenance guide for Cisco Unity Connection Server 12.x, covering server migration, cluster management, IP/hostname configuration, and language file installation.

Table of contents

Quick guide from the manual

This document provides essential procedures for maintaining a Cisco Unity Connection Server (Release 12.x). Key operations include migrating physical servers to virtual machines, replacing cluster nodes, updating network configurations, and managing language files. Always perform a full system backup before initiating any maintenance tasks.

Migrating a Physical Server to a Virtual Machine

To migrate from a physical server to a virtual machine, follow these steps:

Backup: Perform a full backup of the software component on the physical server using the Disaster Recovery System.
Deploy: Download and deploy the OVA template to create the new virtual machine.
Restore: Restore the software components from the physical server backup to the new virtual machine.
Configuration: Ensure the new virtual machine matches the physical server's Hostname, IP address, Time zone, and NTP server settings.

Replacing a Publisher or Subscriber Server

When replacing a server in a cluster, the remaining server continues to provide services. Follow these general steps:

Status Change: Use the Cluster Management page in Cisco Unity Connection Serviceability to set the remaining server to 'Primary'.
Deactivation: Deactivate the server being replaced via the Server Manager menu.
Installation: Install the replacement server. Ensure security passwords match the existing cluster configuration.
Reconfiguration: Use CLI commands such as utils disaster_recovery prepare restore pub_from_sub (for publisher) or utils cuc cluster renegotiate to restore cluster functionality.

Changing the IP Address or Hostname

Before changing network settings, determine if the server is defined by hostname or IP address. Note that changing these settings requires updating all associated components (e.g., DNS, SMTP, client bookmarks).

Preparation: Ensure the server is healthy (check 'ServerDown' alert status).
Backup: Perform a full backup.
DNS Update: Update forward (A) and reverse (PTR) records on your DNS server.
Admin Update: Update the Hostname/IP address in Cisco Unity Connection Administration (System Settings > Cluster).
OS Update: Update the IP/Hostname in Cisco Unified Operating System Administration (Settings > IP > Ethernet).
Restart: Services will restart automatically after saving changes.

Adding or Removing Unity Connection Languages

Languages can be added or removed as needed. Note that installing many languages reduces available disk space.

Download: Obtain the Locale Installer from Cisco.com.
Installation: Use the 'Install/Upgrade' option in the Software Upgrades menu. You will need to provide the path to the language file on a remote filesystem (FTP/SFTP).
Service Management: Before installing or uninstalling, stop the 'Connection Conversation Manager' and 'Connection Mixer' services via Service Management. Restart them after the process is complete.
Removal: Use the CLI command delete cuc locale <code> to remove unwanted languages.

Official resources from the manual

Official resource Cisco.com

Manufacturer information

Cisco Systems, Inc.

Brand profile

Manufacturer website https://www.cisco.com Support https://www.cisco.com/c/en/us/support.html Manufacturer manuals https://www.cisco.com/c/en/us/support/docs

Practical help

Common problems

Data transfer failure during migration

Ensure the virtual machine's Hostname, IP address, Time zone, and NTP server settings exactly match those of the physical server.

Cannot change IP address manually

If DHCP is enabled, you must either disable it using the 'set network dhcp' CLI command or change the settings via Cisco Unified Operating System Administration.

Cluster status issues

Verify cluster health using the 'show cuc cluster status' CLI command. Ensure the server status is set to Primary or Secondary in Cluster Management.

Language installation fails

Ensure the MD5 checksum of the downloaded file matches the value on Cisco.com. Stop the Connection Conversation Manager and Connection Mixer services before starting.

Before use

Perform a full system backup using the Disaster Recovery System.
Verify that the server is healthy (check for 'ServerDown' alerts).
Ensure all associated components (DNS, SMTP, client bookmarks) are identified for updates if changing network settings.
Stop the Connection Conversation Manager and Connection Mixer services before modifying language files.
Verify cluster status using 'show cuc cluster status' before replacing nodes.

Specs in practice

utils system shutdown: CLI command used to safely shut down the server.
utils cuc cluster renegotiate: CLI command used to trigger cluster renegotiation after replacing a publisher node.
show cuc cluster status: CLI command to confirm the cluster is configured and functioning correctly.
set network dhcp: CLI command to disable DHCP, allowing for manual IP address configuration.

Model compatibility

This guide applies to Cisco Unity Connection Release 12.x.
Third-party certificates must be reconfigured after replacing a publisher or subscriber server.

Show more Show less

Manual page author

David Miller

Documentation analyst

Organizes user manual content into clear summaries, with attention to model details, product context, and everyday usability.