We have struggled with an issue for more than a year related to HA over WAN. Even a brief network outage (1-2 seconds) between data centers would cause the master role to switch from the publisher to the subscriber. Mastership changed any time the nodes went into island mode. We finally found the root cause after numerous TAC cases, and I think it's worth sharing since changing the hostnames is supported.
The logic to elect the master node when recovering from island mode is:
Step 1. Check the service status of the nodes. If node 1 is IN_SERVICE and node 2 is in PARTIAL_SERVICE, node 1 becomes the master. If the states are the same (IN_SERVICE or PARTIAL_SERVICE), go to step 2.
Step 2. The hardware specification of both nodes will be checked. The server with the better specification will be handed the mastership. If the hardware specifications are the same, go to step 3.
Step 3. The publisher (i.e. node 1) will become the master if the hostname matches the PrimaryEngineComputerName in the ClusterSpecificConfig. If there is no match, go to step 4.
Step 4. Make the subscriber master.
Alright, now let's back up about 18 months. We decided to build a new cluster to migrate from version 9.0 to 10.6. The intent was to simplify the transition from CAD to Finesse. We built a new cluster on 9.0, restored from backup, changed the hostnames and IPs, and then upgraded to 10.6.
Back to the present (now on version 11.6), we finally lucked out with a TAC engineer that explained the island mode recovery process above. The engineer used the CET (Configuration Editor Tool) to check the ClusterSpecificConfig file where we discovered the primaryEngineComputerName was the hostname of our 9.0 publisher. So now we know step 3 above always fails and the subscriber is elected master as a result.
TAC advised this value is populated at the time of install and cannot be changed (even with root access). The 9.0 cluster had been offline for over a year. Therefore, the best solution was to rename the 11.6 publisher to match the primaryEngineComputerName.
In conclusion, changing the hostname is supported, but it will cause issues with HA. Ideally, the set network hostname command should be updated to also change the primaryEngineComputerName. I asked to have a caveat added to the appropriate section of the admin guide. It's unclear if this request reached the technical writing team – I never received confirmation.
Our UCCX servers have started filling up our webservices logs with "CCBU_Smack Listener Processor" messages. This started around the same time the certificates expired on our UCCX Servers. This may be a coincidence but it does seem strange tha...
Our location upgraded from CAD to Finesse a year ago. We have four departments that use the Call Center function and are setup with a primary number (Direct Line) as well as a Call Center extension on each agent's phone. Example: Jane has a di...
Hi Guys, I would like seeking assistance on how to configure Cisco Prime to send notification to third party monitoring system. The third party monitoring system is Ivanti Service Manager. This third party system only intend to receive events o...
Hello Guys, Is it possible to have 3 Nodes in a single UCCX Cluster, As per my understanding UCCX works only in HA mode in which we can have only 2 UCCX Servers. Or else is it possible to configure cluster between two UCCX Clusters. We have...
Hello there. My company is about to buy a Cisco Webex Room Kit and told me to check out whether it is possible to use the Room Kit with an external touch monitor (not that little tablet).The Room Kit is supposed to be mounted on top of a TV. Wha...