.. _p_set_up_cisco_unified_communications_manager_servers:
Set Up Cisco Unified Communications Manager Servers
---------------------------------------------------
.. _18.1-Patch-Bundle-3|VOSSSOL-8699:
Use this procedure to configure Cisco Unified Communications Manager
servers within a Unified CM cluster.
Procedure
.........
.. note::
References to HCM-F and Shared Data Repository (SDR) are only relevant if
installed.
1. Log in as the appropriate hierarchy administrator.
Only a provider or reseller administrator can create a shared
instance. A customer, provider, or reseller administrator can create a
dedicated instance.
2. Set the hierarchy path to the correct level. Create a shared instance
at the provider or reseller level. Create a dedicated instance at the
customer level.
3. Choose **Device Management > CUCM > Servers**.
4. Click **Add**.
5. Enter the Unified CM server name in the **CUCM Server Name** field.
Note: A Unified CM server that has been configured in HCM-F and synced
into VOSS-4-UC may exist at the sys.hcs hierarchy. If the server name you
enter matches this server, the **Migrate from HCM-F to VOSS-4-UC** check box is
displayed. Click **Save** to migrate this server to the current hierarchy
level. The fields are populated with the values that were configured in HCM-F.
If you do not want to migrate the server, enter a different server name.
6. From the **Server Type** drop-down, choose **Voice/Video**.
7. To configure a publisher node, select the **Publisher** check box.
On the **Publisher** tab, you can specify the following information:
+--------------------------+--------------------------------------------------------------+
| Field | Description |
+==========================+==============================================================+
| | Choose the Prime Collaboration |
| | management application monitoring this |
| Prime Collab | cluster. |
| | |
| | To unassociate Prime Collaboration for |
| | this cluster, choose **None**. |
+--------------------------+--------------------------------------------------------------+
| Call Processing ID | The Call Processing ID of this cluster |
+--------------------------+--------------------------------------------------------------+
| SDR Cluster ID | The SDR CUCM cluster ID, as shown on |
| | **SDR Configuration > SDR CUCM Clusters**. |
+--------------------------+--------------------------------------------------------------+
| | Read-only field. If creating at |
| Multi-Tenant | provider level, this field is set to |
| | Shared. If creating at customer level, |
| | this field is set to Dedicated. |
+--------------------------+--------------------------------------------------------------+
| | Choose the version of the Unified CM |
| Version | Servers in this cluster. The available |
| | versions depend on the version of the |
| | HCM-F device that has been configured. |
+--------------------------+--------------------------------------------------------------+
| Port | The port on the Unified CM server to |
| | connect to. Default is 8443. |
+--------------------------+--------------------------------------------------------------+
| | Choose **Automatic** to automatically move |
| | synced in users to sites, based on the |
| | filters and filter order defined in |
| User Move Mode | **User Management > Manage Filters**. |
| | Choose **Manual** if you want an Administrator |
| | to manually move synced in users to a |
| | Site. |
+--------------------------+--------------------------------------------------------------+
| | Choose the Entitlement Profile that |
| | specifies which devices and services |
| | users synced from this Unified CM are |
| | entitled to. |
| | |
| | Note: |
| | |
| User Entitlement Profile | A violation of the Entitlement Profile |
| | does not prevent a user from being |
| | synced to VOSS-4-UC from Unified CM. |
| | However, subsequent updates to the user |
| | fail until the user's configuration |
| | satisfies the restrictions set in the |
| | Entitlement Profile. |
+--------------------------+--------------------------------------------------------------+
| Enable Change | Select this check box to enable Change Notification. |
| Notification Sync | By enabling this, a Change Notification data sync |
| | and corresponding Schedule will be created. The |
| | Schedule is initially created as Disabled and needs |
| | to be manually enabled from the Scheduling menu. The Change |
| | Notification Sync interval is set to 14 days by default. See |
| | the note below this table. |
+--------------------------+--------------------------------------------------------------+
Refer to the topic on the Change Notification Feature (CNF) following :ref:`VOSS_CNF_overview`.
8. For a Unified CM Publisher node, fill in the **Cluster Name** field with
the name you want for this cluster. A new cluster is created with this
name. This field is required.
For Unified CM Subscribers, choose the Unified CM cluster from the
**Cluster Name** drop-down menu.
9. Expand **Network Addresses**.
a. Choose the SERVICE_PROVIDER_SPACE address space.
#. The **Hostname** field is automatically populated with the Unified CM
Server Name. Edit it if necessary.
#. Enter the IP address of the Cisco Unified Communications Manager
Server in the **IPv4 Address** field.
Note: Either the hostname or the IP address is required. Ensure
that the hostname or IP address does not contain a trailing blank
space. VOSS-4-UC cannot validate an entry that contains a blank
space at the end of the hostname or IP address.
#. Fill in the domain of the Unified CM application.
#. Provide an optional description for the network address.
If NAT is used, also configure an APPLICATION_SPACE network address.
10. Expand **Credentials**.
a. Add credentials for PLATFORM, ADMIN, HTTP, and SNMP_Vx credential
types. Click + to add more credentials.
#. Fill in the user ID and password that you configured when you
installed the Unified CM.
#. Choose RO (Read-only) or RW (Read or Write) for the Access Type.
The default is RO.
#. Provide an optional description for the credential.
ADMIN, HTTP, PLATFORM, and SNMP are required for PCA to manage Unified
CM. PLATFORM and ADMIN are also required for Service Inventory to
generate reports for UC applications.
Note:
Expiration of the ADMIN account results in failed data syncs between
Unified CM and VOSS-4-UC
11. On the **Field Mappings** tab, complete field mappings as desired.
Hard-coded mappings appear in gray and cannot be modified.
12. Click **Save**.
A Unified CM network device is created in VOSS-4-UC. A cluster and Unified
CM are created in the SDR.
13. Test the connection between Unified CM and VOSS-4-UC
a. Choose **Device Management > Advanced > CUCM Network Device**.
b. Click the Unified CM you just added.
c. Choose **Action > Test Connection**.
If the test fails, and you used a hostname, make sure VOSS-4-UC has
the correct DNS and Domain set.
a. Log in to the platform CLI.
#. Query the current DNS setting: **network dns**.
#. Set the DNS if needed: **network dns <dns_server_ip_address>**.
#. Query the current domain setting: **network domain**.
#. Set the domain if needed: **network domain <domain>**.
Note:
Use the **CUCM Network Device** page only for testing the connection. Do
not edit Unified CM from this page. To change any configuration of the
Unified CM, edit it from the **Device Management > CUCM > Servers** page
in VOSS-4-UC.