installing same cucm version inactive partition

[mattiep00]

Is it possible to install the same version of cucm v9 to an appliance? We had already upgraded but not switched and now there have been changes to the running version that we had to include in the new version.  Thanka

[Aman Soi]

Hi,

Never seen this requirement.

But changes made in the DB of active version do not get replicated to version in inactive partition.

what is the CUCM version u are running in which changes have been made and upgraded CUCM version?

regds,

aman

[mattiep00]

Cucm 8.6 upgrading to 9.1

[Aman Soi]

Hi ,

Understood.

you first upgraded from 8.6 to 9.1 , did not do switch over, after that you made changes in 8.6 but that changes won't replicate to 9.1

Now u want to do switch over to 9.1.

Best option would be to re-install CUCM 9.1 in INACTIVE Partiton while 8.6 is in Active Partiton and immediately do switchover.

regds,

aman

[Ayodeji Okanlawon]

If you have not switched to the upgraded version, then you are not running cucm 9.1 rather you are still on the old cucm version. Second you cant install the same cucm version on the smae server. Your options are to upgrade your current cucm 8.6 version to the cucm 9 and it will have all your data in it.

You cant just install cucm 9 in inactive partition, you do that by upgrading your existing system.

Please rate all useful posts

"opportunity is a haughty goddess who waste no time with those who are unprepared"

[ananth1991]

I am aware it's 2 year old post,but i hope it will help some one Who will go for an upgrade without any stress:-)

We have experienced the same problem,Where we have upgraded the publisher alone in inactive Partition to 9.1.2.14900-14 but we didn't switched the version.After a week we installed the same version again in publisher on inactive Partition without any issues.

Below are the installation logs.If my guess is correct, it removes all the old files in inactive partition while we upgrade.

01/31/2016 23:01:55 upgrade_manager.sh|New version is 9.1.2.14900-14|<LVL::Info>
01/31/2016 23:01:55 upgrade_manager.sh|Not a restricted to unrestricted upgrade|<LVL::Info>
01/31/2016 23:01:55 upgrade_manager.sh|Cleanup data from a prior upgrade attempt|<LVL::Info>
01/31/2016 23:01:55 upgrade_manager.sh|Removing any /grub/boot/grub/grub.conf.recovery|<LVL::Debug>
01/31/2016 23:01:55 upgrade_manager.sh|Removing previous rpm_archive /common/rpm-archive/9.1.2.14900-14|<LVL::Info>
01/31/2016 23:01:55 upgrade_manager.sh|Invalidate upgrade partition|<LVL::Info>
01/31/2016 23:01:55 upgrade_manager.sh|Clean up rpm any stale __db. files in rpmdb on the to side|<LVL::Debug>
01/31/2016 23:01:56 upgrade_manager.sh|Removing any master RPM from /partB|<LVL::Debug>
01/31/2016 23:01:59 upgrade_manager.sh|Removing any /partB/etc/opt/cisco/install.conf|<LVL::Debug>
01/31/2016 23:01:59 upgrade_manager.sh|Invalidate any product configuration file|<LVL::Debug>
01/31/2016 23:01:59 upgrade_manager.sh|Setting product and deployment version attributes in /partB/etc/opt/cisco/install/conf/callmanager_product.conf to 0.0.0.0000-0000|<LVL::Debug>