findmanualpdf.com

Maintenance Guide for Cisco Unity Connection Server 12.x

Comprehensive maintenance guide for Cisco Unity Connection Server 12.x. Learn how to migrate servers, replace publisher and subscriber nodes, change IP addresses, and manage language files.

Table of contents

Quick guide from the manual

This document provides essential procedures for maintaining Cisco Unity Connection Server 12.x. Key tasks include migrating physical servers to virtual machines, replacing cluster nodes, updating network configurations, and managing language files. Always perform server replacements during off-peak hours to minimize service impact. Ensure you have performed a full backup using the Disaster Recovery System before initiating any major 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.
  • Deploy: Download and deploy the OVA template to create the new virtual machine.
  • Restore: Restore the software component from the physical server backup to the new virtual machine.
  • Configuration: If required, install new languages or remove existing ones.

Replacing a Publisher or Subscriber Server

When upgrading or replacing nodes in a cluster, follow these procedures:

  • Status Check: Use the Cluster Management page in Cisco Unity Connection Serviceability to verify server status (Primary/Secondary).
  • Deactivation: Use the Real-Time Monitoring Tool (RTMT) to monitor voice messaging ports. Ensure ports are idle before deactivating the server.
  • Shutdown: Use the CLI command utils system shutdown to shut down the server being replaced.
  • Installation: Install the replacement virtual machine, ensuring Hostname, IP address, Time zone, and NTP server settings match the original.
  • Cluster Configuration: Use the CLI command utils cuc cluster renegotiate on the subscriber server to re-establish the cluster.
  • Verification: Run show cuc cluster status to confirm the new cluster configuration.

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 careful coordination with associated components.

  • Preparation: Ensure the ServerDown alert is clear in the Real-Time Monitoring Tool.
  • Validation: Run utils diagnose module validate_network to check connectivity and DNS configuration.
  • Update: Update DNS records (A and PTR) on your DNS server.
  • Configuration: Update the IP/Hostname in Cisco Unity Connection Administration and Cisco Unified Operating System Administration.
  • Restart: Services will restart automatically after saving changes. Do not perform actions until services are fully operational.

Adding or Removing Languages

You can manage installed languages without enforcing a limit, though disk space usage should be monitored.

  • Adding: Download the locale installer from Cisco.com. Use the Install/Upgrade option in the Software Upgrades menu.
  • Removing: Use the CLI command show cuc locales to list installed languages, then use delete cuc locale <code> to remove the specific language.
  • Service Restart: Always stop the Connection Conversation Manager and Connection Mixer services before installing or uninstalling language files, and restart them afterward.

Manufacturer information

Cisco Systems, Inc.

Brand profile

Practical help

Common problems

Server status is not Primary or Secondary

Check the Cluster Management page and use the 'Make Primary' option if necessary.

MD5 checksum mismatch during language installation

The downloaded file is likely damaged. Download the file again until the MD5 value matches the one listed on Cisco.com.

Connection lost during software installation

If you see a warning about another session installing software, select 'Assume Control' to take over the installation.

Server replacement fails to transfer data

Ensure the virtual machine settings (Hostname, IP address, Time zone, NTP server) are identical to the physical server.

Before use

  • Verify server status in the Cluster Management page.
  • Perform a full backup using the Disaster Recovery System.
  • Check network connectivity using 'utils diagnose module validate_network'.
  • Ensure security passwords match across the cluster nodes.
  • Verify that voice messaging ports are idle before deactivating a server.

Specs in practice

Publisher Server
The primary node in a Unity Connection cluster responsible for configuration and database management.
Subscriber Server
The secondary node in a Unity Connection cluster that provides redundancy.

Model compatibility

  • Requires Cisco Unity Connection Release 12.x.
  • Third-party certificates must be reconfigured after replacing a publisher or subscriber server.
  • If using DHCP, you cannot manually change the IP address; you must disable DHCP or change settings via Cisco Unified Operating System Administration.

Manual page author

David Miller

Documentation analyst

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