10-23-2014 05:24 AM - edited 03-17-2019 12:39 AM
Hello,
I have been trying to move a CUCM 7.1(5) cluster on MCS to 10.5(1) on UCS without much success.
Initially I tried to go from 7.1(5) to 10.5(1) by following the Jump upgrade process.
I successfully built a replica of the CUCM 7.1(5) cluster on the UCS servers and did a DRS restore.
When I tried doing an upgrade to CUCM 10.5(1) it failed on the database installation stage.
I raised a TAC case and was asked for logs which I provided but the Cisco Database Installation Service Log did not have any information for the failure.
The TAC engineer said that he had seen this before and it was a problem with dial plans installed on the server.
I had the UK dial plan installed so I rebuilt the cluster on UCS without installing dial plan, locales and phone firmware as I had previously. The only cop file I installed was the refresh upgrade file.
When I tried to upgrade I got the same error.
I was not getting much response from the TAC engineer so I thought I would try upgrading to CUCM 9.1(2) as an interim step. This worked fine and I took a backup then re-installed CUCM 9.1(2) to align the partitions then did a restore. Again this worked ok.
I then tried to install to 10.5(1). I installed the ciscocm.version3-keys.cop file and started the upgrade. It failed in exactly the same place and once again there was no database log.
The failure message I get in the install log is shown below:
10/23/2014 10:25:45 component_install|File:/opt/cisco/install/bin/component_install:807, Function: exec_progmeter(), /opt/cisco/install/bin/progmeter failed (1)|<LVL::Error>
10/23/2014 10:25:45 appmanager.sh|Internal Error, File:/usr/local/bin/base_scripts/appmanager.sh:273, Function: refresh_upgrade(), failed to refresh_upgrade infrastructure_post components|<LVL::Critical>
10/23/2014 10:25:45 post_install|File:/opt/cisco/install/bin/post_install:961, Function: install_applications(), /usr/local/bin/base_scripts/appmanager.sh -refresh-upgrade failed (1)|<LVL::Error>
10/23/2014 10:25:45 post_install|Exiting with result 1|<LVL::Info>
Has anyone seen anything similar to this and, if yes, how was it resolved?
I am trying to get more urgency from TAC but the case has been open for four days so far and I have had very little response.
Thanks
06-12-2015 01:52 PM
s
11-30-2016 06:59 AM
I had the same issue where publisher would upgrade but subscriber would fail to upgrade at the database install phase. Errors in the install log were the same. I was able to resolve it by choosing to not automatically switch versions on the publisher.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide