The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
To support application nodes behind the NAT, Cisco Prime Collaboration Deployment tracks the private IP address and the NAT IP address. Use Cisco Prime Collaboration Deployment to specify the NAT IP address for deployment nodes and the application. Cisco Prime Collaboration Deployment uses the NAT IP address to communicate with the application node. However, when you configure a node using the platformConfig.xml file, the node uses its private address.
When Cisco Prime Collaboration Deployment is behind the NAT and communicates with an application virtual machine or an ESXi host, the communication occurs using the NAT IP address.
Note | When Cisco Prime Collaboration Deployment is behind the NAT and application nodes are in a private network, the application nodes communicate with the NAT IP address. |
Use the NAT Settings window in the Administration menu to set the NAT IP address for Cisco Prime Collaboration Deployment. The NAT IP address that you enter on this window does not appear on any window on the GUI.
With the Discover Cluster feature, Cisco Prime Collaboration Deployment communicates with the servers that are already running Unified Communications applications and adds that cluster information into the Cisco Prime Collaboration Deployment inventory.
When you perform the Discover Cluster operation, the Cisco Prime Collaboration Deployment server communicates with the publisher of the cluster and retrieves the cluster information. Then, it communicates with each server, installs the ciscocm.ucmap_platformconfig.cop file on the server (to retrieve configuration information), and collects information about the hostname, IP, product type, and both active and inactive versions for that server.
Note | When the publisher is behind the NAT, providing the private IP address of the publisher does not reach to the node. You must provide the proper IP address for successful node discovery. |
Note | To know which applications are supported, see Supported Releases. |
Note | If a cluster includes Cisco Unified Communications Manager and Cisco Unified Presence (Cisco Unified Communications and IM and Presence Service servers), the Cluster Discovery discovers the Cisco Unified Presence or IM and Presence Service nodes as part of the Cisco Unified Communications Manager cluster. |
Step 1 | Select from the menu of the Cisco Prime Collaboration Deployment application. | ||
Step 2 | Click Define New UC Cluster. | ||
Step 3 | The Define Cluster wizard appears. Under Step 1 of the wizard, enter the Cluster name. Click Next. | ||
Step 4 | Step 2 of the Add Cluster wizard allows you to add nodes to your cluster. Begin by clicking Add Node at the top of the Cluster Name table. | ||
Step 5 | The Add Node
dialog box appears. The dialog box contains a table that lists all available
VMs, sorted by name and by host. At the top of the page, fill in the Network
settings for this Node. In the middle of the page, choose the Functions for the
node, and near the bottom, choose a VM for this node. Select the VM you wish to
add and then enter the following information in the sections below the VM
table:
| ||
Step 6 | Click OK. | ||
Step 7 | The VM you added is now listed in the Cluster Name table. (To add more nodes to the cluster, repeat steps 4 through 6 until all nodes are added.) After all nodes are added to the Cluster Node table, click Next. | ||
Step 8 | The Configure
Cluster Wide Settings page appears. Enter the OS Administration Credentials,
Application Credentials, Security Password, SMTP Settings, and Certificate
Information for this cluster. Click
Next.
| ||
Step 9 | The Configure DNS Settings screen appears. DNS settings are optional. If you wish to add a DNS setting for a node, select the node and click Assign DNS Settings. The Cisco Unified Contact Center Express application must use DNS. | ||
Step 10 | The Configure
NTP Settings screen appears. You must enter at least one NTP server. If you are
not using DNS, you must enter an IP address. If you are using DNS, you can enter an
FQDN.
| ||
Step 11 | The Configure NIC Settings page appears. This step is optional. To use the default value of 1500, click Next to continue. Or, if you wish to change the settings, choose the server, and enter an MTU size between 552 and 1500, and click Apply to Selected. Click Next after you configure the NIC settings. | ||
Step 12 | Choose a time zone for each node in the cluster. To choose the time zone, select the node and choose the desired time zone settings in the boxes at the top, and click the Apply to Selected. When you finish setting time zones for all the nodes, click Finish. | ||
Step 13 | The new install cluster is listed on the Clusters screen, with a cluster type of "New Install." The cluster is defined but not yet created. When you are ready to install the cluster, create an install task. The install task uses the install cluster that you defined, and creates the cluster. |
Discover the existing cluster you wish to migrate. See the "Discover a Cluster" procedure at Discover a Cluster.
Define a migration cluster.
Note | After you define the migration cluster, see "Migration Task" at Migration Task to define when and how to perform the migration. |
Step 1 | From the Cisco Prime Collaboration Deployment application, select . | ||
Step 2 | Click Define Migration Destination Cluster. The Define Migration Destination Cluster wizard appears. | ||
Step 3 | In the Specify
Clusters section, specify the name of the cluster, select the source UC cluster
from the drop-down list. Enter a name in the Destination Cluster Name field and
select one of the following Destination Network Settings options:
| ||
Step 4 | Click Next. The Assign Destination Cluster Nodes window appears. | ||
Step 5 | Click the
Assign
Destination Cluster Nodes button to select the destination virtual
machine for each source node.
| ||
Step 6 | Select a
virtual machine, click
Next
Node to go to the next node in the cluster, and select another
virtual machine for the destination virtual machine, and click
Done.
| ||
Step 7 | Click Next. The Configure NTP/SMTP Settings window appears. | ||
Step 8 | Enter the
Network Time Protocol (NTP) server settings to be applied to the migration
nodes when the migration task runs, and optionally, enter the SMTP server
settings.
In a proxy TFTP setup, if a network migration is performed "off-cluster", you need to manually configure the new hostname and IP address of that off-cluster in the proxy TFTP. Off-cluster refers to situations where TFTP functionality is being performed by a proxy that is not part of that specific Unified Communications Manager cluster. During a migration, that TFTP server (that is not part of the cluster) is not modified. If you want to change the hostname or IP address of that server, you must do it as a separate process and not with Cisco Prime Collaboration Deployment. | ||
Step 9 | Click Next. The Define DNS Settings window appears. | ||
Step 10 | To change the
DNS setting for a node, select the node or nodes from the table and click
Assign
DNS Settings. Enter the primary and secondary DNS, then click
OK to apply the changes.
You cannot change the domain name during a migration. | ||
Step 11 | Click
Finish.
The changes are saved and a row is added to the clusters table to reflect the new migration cluster that you have created. |
For information about supported releases for Cisco Prime Collaboration Deployment, see Supported Releases.
For information about direct upgrade paths, see the Cisco Unified Communications Manager Software Compatibility Matrix at the following URL: http://www.cisco.com/c/en/us/support/unified-communications/unified-communications-manager-callmanager/products-device-support-tables-list.html.
For upgrade and migration information that is not covered in the above references (for example, upgrading from Release 4.x), see the Drive to Collaboration site at the following URL: http://www.cisco.com/web/solutions/vnlanding/comm_manager_upgrade.html.
Product and Functions |
Cluster Discovery |
Migration to 10.x Cluster |
Upgrade Task (Upgrade Application Server or Install COP Files) |
Restart Task |
Switch Version Task |
Fresh Install a New 10.x Cluster |
Readdress Task (Change Hostname or IP Addresses for One or More Nodes in a Cluster) |
---|---|---|---|---|---|---|---|
Cisco Unified Communications Manager |
6.1(5), 7.1(3), 7.1(5), 8.0(1), 8.0(2), 8.0(3), 8.5(1), 8.6(1), 8.6(2), 9.0.(1), 9.1(1), 9.1(2), 10.0(1), 10.5(1), 10.5(2) |
6.1(5), 7.1(3), 7.1(5), 8.0(1), 8.0(2), 8.0(3), 8.5(1), 8.6(1), 8.6(2), 9.0.(1), 9.1(1), 9.1(2), 10.0(1) |
8.6(1), 8.6(2), 9.0.(1), 9.1(1), 9.1(2), 10.0(1), 10.5(1), 10.5(2) |
8.6(1), 8.6(2), 9.0.(1), 9.1(1), 9.1(2), 10.0(1) |
8.6(1), 8.6(2), 9.0.(1), 9.1(1), 9.1(2), 10.x |
10.x, 10.5(1), 10.5(2) |
10.x |
Cisco Unified Presence |
8.5, 8.6 |
8.5(4), 8.6(3), 8.6(4), 8.6(5) |
8.6(3), 8.6(4), 8.6(5) |
8.6(3), 8.6(4), 8.6(5) |
8.6(3), 8.6(4), 8.6(5) |
— |
— |
IM and Presence Service |
9.0(1), 9.1(1), 10.x |
9.0(1), 9.1(1), 10.x |
9.0(1), 9.1(1), 10.x |
9.0(1), 9.1(1), 10.x |
9.0(1), 9.1(1), 10.x |
10.x, 10.5(1), 10.5(2) |
Not Supported |
Cisco Unified Contact Center Express |
8.5.1, 9.0, 9.0.2, and 10.x |
Not Supported |
9.0(2), 10.x |
9.0(2), 10.x |
9.0(2), 10.x |
10.5(x) |
10.5(x) |
Cisco Unity Connection |
8.6.1, 8.6.2, 9.x and 10.x |
Not Supported |
From 8.6(x) to 8.6(x) From 8.6(x) to 9.x From 9.x to 9.x From 10.0(1) to 10.x |
8.6(1), 8.6(2), 9.x, 10.x |
8.6(1), 8.6(2), 9.x, 10.x |
10.5(x) |
10.5(x) |
Note | The supported releases table does not include the Engineering Special (ES)/ Service Update (SU) versions. To upgrade or migrate to ES/SU versions, see the release notes of the corresponding product, such as IM and Presence, Cisco Unified Communications Manager, and Unity. |
From | To | Task Types Supported |
---|---|---|
Export Restricted (K9) |
Export Restricted (K9) |
Supported for Upgrade paths Supported for Migration paths |
Export Restricted (K9) |
Export Unrestricted (XU) |
Not supported for Upgrade paths Supported for Migration paths |
Export Unrestricted (XU) |
Export Restricted (K9) |
Not supported for Upgrade paths Not supported for Migration paths |
Export Unrestricted (XU) |
Export Unrestricted (XU) |
Supported for Upgrade paths Supported for Migration paths |
Following is the new CLI command that is available in Cisco Unified Communications Manager Release 10.5(2):
utils disaster_recovery show_registration SERVER—Shows the features that you need to back up. For example, if you want to back up PCD, choose PCD from the feature list. The SERVER field is mandatory.
For more information, see the DRS documentation for Cisco Unified Communications Manager, at http://www.cisco.com/en/us/products/sw/voicesw/ps556/prod_maintenance_guides_list.html.