Upgrade Guide for Cisco Unity Connection Release 10.x
Migrating to a Connection 10.x Virtual Machine
Downloads: This chapterpdf (PDF - 229.0KB) The complete bookPDF (PDF - 3.17MB) | Feedback

Table of Contents

Migrating to Unity Connection 10.x Virtual Machine

Task List for Migrating Unity Connection from a Physical Server to a Virtual Machine

Replacing a Publisher Server in a Unity Connection 10.x Cluster

Manually Change Subscriber Server to Primary Status

Manually Change Publisher Server to Deactivated Status

Install Replacement Publisher Server

Configure the Cluster on Replacement Publisher Server

Replicate Data to the Publisher Server

Replacing Subscriber Server in a Unity Connection 10.x Cluster

Manually Change Publisher Server to Primary Status

Manually Change Subscriber Server to Deactivated Status

Changing the Hostname or IP Address of Subscriber Server on Publisher Server

Install Replacement Subscriber Server

Confirm Unity Connection Cluster is Configured

Re add Cluster to Unity Connection Site (with Intersite Networking Only)

Changing the Boot Order of Unity Connection Virtual Machine

Task List for Migrating Unity Connection from a Physical Server to a Virtual Machine

1. Review the section “Requirements for Installing Cisco Unity Connection 10.x on a Virtual Machine” in System Requirements for Cisco Unity Connection Release 10.x at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/10x/requirements/10xcucsysreqs.html .

2. In the Cisco Unity Connection 10.x Supported Platforms List , in the table of virtualization specifications, determine which VMware configuration you want to deploy on the Unity Connection server, based on the maximum number of ports and the maximum number of users. Then make note of the VMware OVA template that corresponds with that configuration. The document is available at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/10x/supported_platforms/10xcucspl.html .

3. Download the VMware OVA template that you identified in Task 2. See the “Installing Cisco Unity Connection for the First Time on a Virtual Machine” section in the applicable Release Notes for Cisco Unity Connection at http://www.cisco.com/en/US/products/ps6509/prod_release_notes_list.html .


Note Information on downloading a VMware OVA template appears in the Release Notes for Cisco Unity Connection for versions 10.x and later.


4. If the Unity Connection physical server is running version 7.1(2) or earlier: Upgrade to Unity Connection 7.1(3). See the applicable chapter in the Upgrade Guide for Cisco Unity Connection Release 7.x at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/7x/upgrade/guide/7xcucrugx.html . (You upgrade to version 10.x in a later task.)


Caution Running Unity Connection 7.1(3) in a virtual environment for any longer than is required for the migration is not supported.

5. Provision the physical host where the Unity Connection virtual machine will run, according to the “Requirements for Installing a Cisco Unity Connection 10.x Virtual Machine” section in System Requirements for Cisco Unity Connection Release 10.x at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/10x/requirements/10xcucsysreqs.html .

6. Deploy the OVA template that downloaded in Task 3. to create a virtual machine and configures it.

7. In the VMware vSphere Client, configure the virtual disks that are assigned to the Unity Connection virtual machine in independent-persistent mode. This provides the best storage performance.

8. On the virtual machine, change the BIOS setting so the virtual machine boots first from the DVD virtual device, then from the virtual hard disk. See the “Changing the Boot Order of Unity Connection Virtual Machine” section.

9. If you are migrating from Unity Connection without cluster, follow the steps given in the “To Migrate from Unity Connection without Cluster” section.

10. If you are migrating from Unity Connection with cluster, follow the steps given in the “To Migrate from Unity Connection with Cluster” section.

To Migrate from Unity Connection without Cluster


Step 1 Back up the Unity Connection physical server using the Disaster Recovery System. For more information, see the applicable Disaster Recovery System Administration Guide for Cisco Unity Connection at http://www.cisco.com/en/US/products/ps6509/prod_maintenance_guides_list.html .

Step 2 Shut down the Unity Connection physical server using the CLI command utils system shutdown . For more information, see the applicable Command Line Interface Reference Guide for Cisco Unified Communications Solutions at http://www.cisco.com/en/US/products/ps6509/prod_maintenance_guides_list.html .

Step 3 On the virtual machine, install the exact version of Connection that is installed on the physical server, including engineering specials, if any. See the Installation Guide for Cisco Unity Connection Release 10.x at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/10x/installation/guide/10xcucigx.html .

The following two installation settings must be the same on the Connection virtual machine as on the Connection physical server, or using the Disaster Recovery System to transfer data from the physical server to the virtual machine will fail:

  • Hostname of the server
  • IP address of the server

We recommend that you enter settings that are unlikely to change for the foreseeable future:

  • Time zone
  • NTP server
  • NIC speed and duplex settings
  • DHCP settings
  • Primary DNS settings
  • SMTP hostname
  • X.509 Certificate information (Organization, Unit, Location, State, and Country)

You must give the Connection virtual machine the same hostname as the Connection physical server so you can restore data.

Step 4 Restore data on the Unity Connection virtual machine using the backup that you made in Step 1.

Step 5 If you installed Unity Connection on the virtual machine: Upgrade to version 10.x or later. See the following chapters:

Step 6 After upgrading to Unity Connection 10.x, you may change the hostname and/or IP address of the Unity Connection virtual machine.

To Migrate from Unity Connection with Cluster


Step 1 If you are using intrasite networking, remove the server from the Unity Connection site. For instructions, see the "Making Changes to the Networking Configuration in Unity Connection 10.x" chapter of the Networking Guide for Cisco Unity Connection 10.x available at http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/10x/networking/guide/10xcucnetx/10xcucnet040.html .

Step 2 Back up the Unity Connection physical server using the Disaster Recovery System. For more information, see the applicable Disaster Recovery System Administration Guide for Cisco Unity Connection at http://www.cisco.com/en/US/products/ps6509/prod_maintenance_guides_list.html .

Step 3 Replace a publisher server in a Unity Connection 10.x cluster. For instructions, see the“Replacing a Publisher Server in a Unity Connection 10.x Cluster” section of this chapter.

Step 4 Restore data on the Unity Connection virtual machine using the backup that you made in Task Step 2

Step 5 Connect the subscriber server to the new Unity Connection cluster and replicate data/messages to the publisher server. For instructions, see the“Replicate Data to the Publisher Server” section of this chapter.

Step 6 Replace a subscriber server in a Unity Connection 10.x cluster. For instructions, see the“Replacing Subscriber Server in a Unity Connection 10.x Cluster” section of this chapter.

Step 7 If you installed Unity Connection on the virtual machine: Upgrade to version 10.x or later. See the following chapters:


Note When the intrasite networking is configured, you need to readd the cluster to the Unity Connection location.



 

Replacing a Publisher Server in a Unity Connection 10.x Cluster

You can replace the publisher server in a Unity Connection cluster without replacing the subscriber server. During the time that the publisher server is not functioning, the subscriber server handles all functions for the Unity Connection cluster to avoid loss of service to the system.

When replacing the server, you must install a replacement publisher server; you cannot convert the subscriber server into the publisher server. On the replaced publisher server, you configure a new Unity Connection cluster. When you connect the subscriber server to the new Unity Connection cluster, the subscriber server replicates its data to the replacement publisher server without loss of service to the system. When the replaced publisher server has Primary or Secondary status, it begins to handle calls again.

Do the applicable procedures in this section in the order listed:

Manually Change Subscriber Server to Primary Status

To Manually Change the Subscriber Server to Primary Status


Step 1 Sign in to Cisco Unity Connection Serviceability.

Step 2 On the Tools menu, select Cluster Management .

Step 3 On the Cluster Management page, under Server Manager, locate the subscriber server.

Step 4 If the subscriber server has Primary status, skip the remaining steps in this procedure and skip to the next procedure.

If the subscriber server has Secondary status, skip to Step 5.

If the subscriber has Deactivated status, change the status to Secondary:

a. In the Change Server Status column for the subscriber server, select Activate .

b. When prompted to confirm changing the server status, select OK .

c. Confirm that the Server Status column indicates that the subscriber server now has Secondary status.

Step 5 In the Change Server Status column for the subscriber server, select Make Primary .

Step 6 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 publisher server will automatically change to Secondary status.



 

Manually Change Publisher Server to Deactivated Status

To Manually Change the Publisher Server from Secondary Status to Deactivated Status


Step 1 Sign in to the Real-Time Monitoring Tool (RTMT).

Step 2 On 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 publisher server.

Step 4 In the right pane, select Start Polling .

Note whether any voice messaging ports are currently handling calls for the server.

Step 5 Return to the Cluster Management page of Cisco Unity Connection Serviceability.

Step 6 If no voice messaging ports are currently handling calls for the publisher server, skip to Step 7.

If there are voice messaging ports that are currently handling calls for the publisher server, on the Cluster Management page, under Port Manager, select Stop Taking Calls for the publisher server, then wait until RTMT shows that all ports for the publisher server are idle.

Step 7 Under Server Manager, in the Change Server Status column for the publisher server, select Deactivate .

Step 8 When prompted to confirm changing the server status, select OK .

The Server Status column displays the changed server status when the change is complete.


 

Install Replacement Publisher Server

To Install the Replacement Publisher Server


Step 1 Shut down the publisher server using the CLI command utils system shutdown . For more information, see the applicable Command Line Interface Reference Guide for Cisco Unified Communications Solutions at http://www.cisco.com/en/US/products/ps6509/prod_maintenance_guides_list.html .

On the subscriber server, in Cisco Unity Connection Serviceability, on the Cluster Management page, the Server Status column shows the publisher server has Not Functioning status.

Step 2 On the virtual machine, install the exact version of Unity Connection that is installed on the physical server, including engineering specials, if any. See the Installation Guide for Cisco Unity Connection Release 10.x at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/10x/installation/guide/10xcucigx.html .

The following two installation settings must be the same on the Unity Connection virtual machine as on the Unity Connection physical server, or using the Disaster Recovery System to transfer data from the physical server to the virtual machine will fail:

  • Hostname of the server
  • IP address of the server

We recommend that you enter settings that are unlikely to change for the foreseeable future:

  • Time zone
  • NTP server
  • NIC speed and duplex settings
  • DHCP settings
  • Primary DNS settings
  • SMTP hostname
  • X.509 Certificate information (Organization, Unit, Location, State, and Country)

You must give the Unity Connection virtual machine the same hostname as the Unity Connection physical server so you can restore data.

Step 3 After installing the replacement publisher server, you may change the hostname and/or IP address of the Unity Connection virtual machine. For more information, see the “Changing the IP Addresses of Unity Connection 10.x Servers” .


 

Configure the Cluster on Replacement Publisher Server

To Configure the Cluster on the Replacement Publisher Server


Step 1 Sign in to Cisco Unity Connection Administration on the publisher server.

Step 2 In Cisco 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 Hostname/IP Address field, enter the hostname or IP address of the subscriber server.

Step 5 In the Description field, enter a description for the subscriber server.

Step 6 Select Save .

Step 7 Sign out of Cisco Unity Connection Administration.


 

Replicate Data to the Publisher Server

To Connect the Subscriber Server to the New Unity Connection Cluster, and Replicate Data and Messages to the Publisher Server


Step 1 Sign in to the command-line interface (CLI) for the subscriber server.

Step 2 Run the CLI command utils cuc cluster renegotiate .


Note When the CLI command completes, the publisher server automatically restarts.


Step 3 Run the CLI command show cuc cluster status on the subscriber server to confirm that the new Unity Connection cluster has been configured correctly.


 

Replacing Subscriber Server in a Unity Connection 10.x Cluster

You can replace the subscriber server in a Unity Connection cluster. During the time that the subscriber server is not functioning, the publisher server will handle all functions for the Unity Connection cluster to avoid loss of service to the system.

When replacing the server, you remove the subscriber server from the Unity Connection cluster and add the replacement subscriber server. After you install the replacement subscriber server, the publisher server replicates its data to the replacement subscriber server without loss of service to the system. When the replaced subscriber server has Primary or Secondary status, it begins to handle calls again.

Do the applicable procedures in this section in the order listed:

Manually Change Publisher Server to Primary Status

To Manually Change the Publisher Server to Primary Status


Step 1 Sign in to Cisco Unity Connection Serviceability.

Step 2 On the Tools menu, select Cluster Management .

Step 3 On the Cluster Management page, under Server Manager, locate the publisher server.

Step 4 If the publisher server has Primary status, skip the remaining steps in this procedure and skip to the next procedure.

If the publisher server has Secondary status, skip to Step 5.

If the publisher has Deactivated status, change the status to Secondary:

a. In the Change Server Status column for the publisher server, select Activate .

b. When prompted to confirm changing the server status, select OK .

c. Confirm that the Server Status column indicates that the publisher server now has Secondary status.

Step 5 In the Change Server Status column for the publisher server, select Make Primary .

Step 6 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 subscriber server automatically changes to Secondary status.



 

Manually Change Subscriber Server to Deactivated Status

To Manually Change the Subscriber Server from Secondary Status to Deactivated Status


Step 1 Sign in to the Real-Time Monitoring Tool (RTMT).

Step 2 On 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 subscriber server.

Step 4 In the right pane, select Start Polling .

Note whether any voice messaging ports are currently handling calls for the server.

Step 5 Return to the Cluster Management page of Cisco Unity Connection Serviceability.

Step 6 If no voice messaging ports are currently handling calls for the server, skip to Step 7.

If there are voice messaging ports that are currently handling calls for the subscriber server, on the Cluster Management page, under Port Manager, select Stop Taking Calls for the subscriber server, then wait until RTMT shows that all ports for the server are idle.

Step 7 Under Server Manager, in the Change Server Status column for the subscriber server, select Deactivate .

Step 8 When prompted to confirm changing server status, select OK .

The Server Status column displays the changed server status when the change is complete.


 

Changing the Hostname or IP Address of Subscriber Server on Publisher Server

Revised July 8, 2014

To Change the Hostname or IP Address for the Subscriber Server in Connection Administration on the Publisher Server


Step 1 If the replacement subscriber server will have a different hostname or IP address, sign in to Cisco Unity Connection Administration on the publisher server.


Note Make sure not to change IP address or hostname of the Unity Connection server at the same time to avoid database corruption.


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

Step 3 On the Find and List Servers page, select Find to display all servers in the cluster.

Step 4 Check the check box in front of the subscriber server and select Delete Selected .

Step 5 When prompted to confirm deleting the server, select OK .

Step 6 Select Add New .

Step 7 On the New Server Configuration page, in the Hostname/IP Address field, enter the hostname or IP address of the replacement server.

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

Step 9 Select Save .

Step 10 Sign out of Cisco Unity Connection Administration.


 

Install Replacement Subscriber Server

To Install the Replacement Subscriber Server


Step 1 Shut down the publisher server using the CLI command utils system shutdown . For more information, see the applicable Command Line Interface Reference Guide for Cisco Unified Communications Solutions at http://www.cisco.com/en/US/products/ps6509/prod_maintenance_guides_list.html .

On the publisher server, in Cisco Unity Connection Serviceability, on the Cluster Management page, the Server Status column shows the subscriber server has Not Functioning status.

Step 2 Follow the instructions in “Installing the Operating System and Unity Connection” section of “Installing Operating System and Unity Connection 10.x” chapter of Installation Guide for Cisco Unity Connection Release 10.x at: http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/10x/installation/guide/10xcucigx/10xcucig020.html.


Note When you reinstall Unity Connection, note the following:

  • You must install the same software and ES version that is installed on the publisher server. Otherwise, the Unity Connection cluster may not function correctly.
  • You must specify the same security password as the subscriber server that you are replacing, which also matches the security password for the publisher server. Otherwise, the Unity Connection cluster will not function. If you do not know the security password, you can change it on the publisher server before you install the subscriber server using the CLI command set password user . For more information, see the applicable version of the Command Line Interface Reference Guide for Cisco Unified Communications Solutions at http://www.cisco.com/en/US/products/ps6509/prod_maintenance_guides_list.html .


 


 

Confirm Unity Connection Cluster is Configured

To Confirm Unity Connection Cluster is Configured


Step 1 Sign in to the command-line interface (CLI) for the subscriber server.

Step 2 Run the CLI command show cuc cluster status .


 

Re add Cluster to Unity Connection Site (with Intersite Networking Only)

To Re add Cluster to the Unity Connection Site (Only When Intrasite Networking is Configured)


 

If you are using intrasite networking, re-add the cluster to the Unity Connection site. For instructions, see the "Making Changes to the Networking Configuration in Unity Connection 10.x" chapter of the Networking Guide for Cisco Unity Connection 10.x available at http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/10x/networking/guide/10xcucnetx/10xcucnet040.html .


 

Changing the Boot Order of Unity Connection Virtual Machine

Do the procedure in this section to change the BIOS setting so the virtual machine boots first from the DVD virtual device, then from the virtual hard disk.

To Change the Boot Order of the Unity Connection 10.x Virtual Machine


Step 1 In VMware vSphere Client, power off the virtual machine on which you deployed the OVA template.

Step 2 In the left pane of vSphere Client, right-click the name of the virtual machine, and select Edit Settings .

Step 3 In the Virtual Machine Properties dialog box, select the Options tab.

Step 4 In the Settings column, under Advanced, select Boot Options .

Step 5 Under Force BIOS Setup, check the The Next Time the Virtual Machine Boots, Force Entry into the BIOS Setup Screen check box.

Step 6 Select OK to close the Virtual Machine Properties dialog box.

Step 7 Power on the virtual machine. The virtual machine boots into the BIOS menu.

Step 8 Navigate to the Boot menu, and change the boot device order so the CD-ROM device is listed first and the Hard Drive device is listed second.

Step 9 Save the change, and exit BIOS setup.