Unity Connection version 15.0 upgrade via data export Subscriber i

[CoDeC]

hi,

I have upgrade Unity Connection from 12.5 (1) to 15 with Import Data. The first nodes, successfully, but the I got errors with the second node. I guess that before start the upgrade procedure of the second node, it is needed to add in the cluster, correct?

regards,

[Nithin Eluvathingal]

When performing a fresh install with the data export option, you don’t need to add the second node’s details to the Primary. The Publisher will already include those details in the exported data,Given that the source cluster consist of Pub and SUB.

[CoDeC]

hi,

the first node, publisher, I upgraded with Export/Import Data procedure and the second node I tried with Export/Import Data procedure and Fresh Install. In both cases, I got errors errors for second node.

regards,

[Roger Kallberg]

@CoDeC Your question isn’t really a match with the OPs question, so it would have been better if you would have created your own post.

Edit: I split your question out from the post you originally responded in. So now it is a separate post.

[CoDeC]

thanks and apologies. you are full right.

[Nithin Eluvathingal]

Check both unity to identify any expired certificates, particularly the Tomcat certificate.

[CoDeC]

thanks for your answer.

there are not Tomcat certificates expired. We have only some CallManager-trust certificates expired.  

I have attached a couple of screenshot of the errors that I got on the second node.

regards,

[Nithin Eluvathingal]

Are you having an issue with CM or Unity? Your original post mentions Unity, but your latest post refers to CM.

Which node is failing?

For the error during the fresh install with the data export option, I’ll export new data from the source node ( failed ) and reinstall it using that data.

the new data.

[CoDeC]

hi,

It is Unity Connection. About your reference of certificates expired, in Unity have only some certificates expired of CallManager-trust.

Tomcat certificate of both Unity Connection are not expired yet. I will try to export again of the secondary node and import again. I let you know if works.

regards

Failed the second node.

[Roger Kallberg]

It’s not recommended to keep expired certificates on your system. Either you renew them or remove them if not in use anymore.

[CoDeC]

Hi,

I have checked the errors and I like say the installation messages there is one packages failed:

06/22/2025 15:20:12 IPM|capture: Verifying packages...|<LVL::Debug>
06/22/2025 15:20:12 IPM|capture: Preparing packages...|<LVL::Debug>
06/22/2025 15:20:12 IPM|capture: 	package cm-lib-1.0.0.0-1.x86_64 is already installed|<LVL::Debug>
06/22/2025 15:20:12 IPM|Internal Error, File:ipm.c:2014, Function: ipmReadNormalizedInputLine(), "rpm --percent -iv --replacefiles /common/rpm-archive/15.0.1.10000-24/RPMS/thirdparty/cm-lib-1.0.0.0-1.x86_64.rpm " failed (1).|<LVL::Critical>
06/22/2025 15:20:14 IPM|  end-of-session "Installing thirdparty component": 2.010 secs.|<LVL::Info>
06/22/2025 15:20:14 IPM|Close progress meter "Component Install"|<LVL::Info>
06/22/2025 15:20:14 component_install|Writing thirdparty into /common/log/install/component_failed.xml file.|<LVL::Info>
06/22/2025 15:20:14 component_install|/common/log/install/component_failed.xml created : 0|<LVL::Info>
06/22/2025 15:20:14 component_install|(CAPTURE) SET CcmFirstNode=no|<LVL::Debug>
06/22/2025 15:20:14 component_install|(CAPTURE) SET CcmDBHost=deeipcuc1|<LVL::Debug>
06/22/2025 15:20:14 component_install|(CAPTURE) SET CUPDBHost=|<LVL::Debug>
06/22/2025 15:20:14 component_install|(CAPTURE) [25/06/22_15:19:53] ssh_keys_migrate: Import ssh keys|<LVL::Debug>
06/22/2025 15:20:14 component_install|(CAPTURE) [25/06/22_15:19:53] ssh_keys_migrate: removing DSA keys during import|<LVL::Debug>
06/22/2025 15:20:14 component_install|(CAPTURE) [25/06/22_15:19:53] ssh_keys_migrate: RSA key bits check (regen , existing): 3072 , 2048|<LVL::Debug>
06/22/2025 15:20:14 component_install|(CAPTURE) [25/06/22_15:19:53] ssh_keys_migrate: Regenerated SSH rsa key of 3072 bits|<LVL::Debug>
06/22/2025 15:20:14 component_install|(CAPTURE) [25/06/22_15:19:53] ssh_keys_migrate: Import ssh keys complete|<LVL::Debug>
06/22/2025 15:20:14 component_install|(CAPTURE) [25/06/22_15:19:57] drf_migrate: Import drf data.|<LVL::Debug>
06/22/2025 15:20:14 component_install|(CAPTURE) [25/06/22_15:19:57] drf_migrate: Import drf data complete.|<LVL::Debug>
06/22/2025 15:20:14 component_install|File:/opt/cisco/install/bin/component_install:882, Function: exec_progmeter(), /opt/cisco/install/bin/progmeter failed (1)|<LVL::Error>

 but not idea the root cause of the fail. 

[CoDeC]

hi,

finally I opened a tac case. the engineer identified the issue due to the installer script was unable to correctly retrieve the primary node's information from the /common/cluster_info.xml file. In this file had only the data of the publisher. the engineer added the subscriber, restart the publisher and then install the subscriber (fresh install). Although I don't know the root cause yet. Maybe, removing the subscriber from System Settings > Cluster and added it again would fix the issue.

I let you know if the cisco engineer know the root cause.

thanks all by the help.

regards,

regards,