Cisco Unified Intelligence Center uses Hazelcast for application clustering. Hazelcast provides a second-level cache for the Unified Intelligence Center application layer. When any entity (for example: report, report definition, and so on) cached by Hazelcast is updated in one of the Unified Intelligence Center nodes, it must be invalidated and reloaded in all the other Unified Intelligence Center nodes in the cluster. The Hazelcast cluster automatically takes care of it by publishing clusterwide notifications containing the identifiers of such entities which must be invalidated.

In Unified Intelligence Center, the default mechanism for Hazelcast cluster discovery or formation is UDP multicast. Unified Intelligence Center uses the Multicast group IP address 224.2.2.3 and port 54327. You cannot change these settings in Unified Intelligence Center.

The UDP multicast based discovery mechanism will not work for the customer in the following scenarios:

• When the network has multicasting disabled.

• If the nodes in the Unified Intelligence Center cluster are in different subnets.

In such scenarios, you can change the discovery mechanism to TCP/IP. You can form the CUIC application cluster using TCP/IP instead of the default UDP Multicast based discovery mechanism.

Use the following CLI commands to manage the cluster mode (UDP Multicast vs TCP/IP). That is, use the following CLI commands to switch to TCP/IP only if the customer’s network does not support Multicasting:

• utils cuic cluster show—This command shows the current cluster mode that is enabled on this node and the other member details.

  Note	The member details are available only in the TCP/IP mode. The member details displayed are of the configured members and does not represent the cluster in real time.

• utils cuic cluster mode—This command is used to switch the Hazelcast cluster join configuration from Multicast to TCP/IP and the opposite way.

  Note	After changing the cluster mode in all the nodes, restart “Intelligence Center Reporting Service” in all the nodes starting from the publisher sequentially.

• utils cuic cluster refresh—This command refreshes the cluster member information only when executed in the TCP/IP mode. Run this command when there is an addition or deletion of nodes to the CUIC cluster, which is already in TCP/IP.

Usage

You can use these commands using to switch to TCP/IP only when the customer’s network does not support the Multicasting requirements that are specified in Port Utilization Guide for Cisco Unified Contact Center Solutions > Intracluster Ports Between Cisco Unified Intelligence Center section available at https://www.cisco.com/c/en/us/support/customer-collaboration/unified-contact-center-enterprise/products-installation-and-configuration-guides-list.html.

Note

Stop the “Cisco Unified Intelligence Center Reporting Service” on all the Unified Intelligence Center nodes before performing cluster configuration changes using these CLI commands. When you have completed the cluster configuration changes on all nodes, use the “utils cuic cluster show” command to ensure that all nodes have identical configuration before starting “Cisco Unified Intelligence Center Reporting Service” on any one of them. Unified Intelligence Center cluster / application will work only if all the nodes use the same mode–that is, either Multicast or TCP/IP. Mixed mode is not allowed. If the network is disconnected and after the cluster nodes retain the network, ensure to perform “synchronize cluster” from all the nodes after logging into the Unified Intelligence Center reporting application.

Steps

Run the following CLIs on all nodes in the given sequence starting from the Publisher node:

Note	Execute every step on all nodes before performing the subsequent step.