05-26-2010 12:18 AM - edited 03-15-2019 10:56 PM
Good Day All
We are trying to upgrade the publisher from CUCM 7.0(1) to 7.1(3b). Since there is no direct path for this upgrade, we have to hope to a version in between, that is CUCM 7.1(2b).
Since we have two partitions, active and inactive, we have already upgrade the inactive part to 7.1(2b) version as per Cisco Documentation then switch to that version, it ended with:
Active : 7.1(2b) version
Inactive : 7.0(1) version.
The questions here:
Thanks for your time
AT
Solved! Go to Solution.
05-27-2010 06:06 AM
Hi AT,
Here is a clip that describes the CUCM upgrade process
With this version of Cisco Unified Communications Manager, you can install upgrade software on your server while the system continues to operate. Two partitions exist on your system: an active, bootable partition and an inactive, bootable partition. The system boots up and operates entirely on the partition that is marked as the active partition.
When you install upgrade software, you install the software on the inactive partition. The system continues to function normally while you are installing the software. When you are ready, you activate the inactive partition and reboot the system with the new upgrade software. The current active partition will then get identified as the inactive partition when the system restarts. The current software remains in the inactive partition until the next upgrade. Your configuration information migrates automatically to the upgraded version in the active partition.
If for any reason you decide to back out of the upgrade, you can restart the system to the inactive partition that contains the older version of the software.
http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/cucos/6_0_1/cucos/iptpch7.html
So, in your example/environment;
The first upgrade moved you from 7.0 (1) on the active and something else on the inactive
and changed you to 7.1(2b) on the active and 7.0(1) on the inactive.
Your next step/upgrade will move you from 7.1(2b) on the active and 7.0(1) on the inactive
and will change you to 7.1(3b) on the active and 7.1(2b) on the inactive. In a two-hop upgrade
process your original (in your case 7.0(1)) will always be lost as part of the second step
Hope this makes sense.
Cheers!
Rob
05-26-2010 05:35 AM
Hi Adham,
This upgrade will look the same as far as the Partitions go
You will install 7.1(3b) on the Inactive Partition (installs are always done
on the Inactive side) then switch versions from 7.1(2b) to 7.1(3b) and you should
be good to go.
Cheers!
Rob
05-26-2010 12:49 PM
Hi Mr. Huffman,
Thanks for you reply
Do you mean that I won’t switch to the inactive partition after my first upgrade?
So, I will keep the active 7.0(1) partition as it is and do my final upgrade on the inactive 7.1(2b)?
Thanks
AT
05-26-2010 01:01 PM
If you already have:
Active : 7.1(2b) version
Inactive : 7.0(1) version.
Just do the next upgrade, you never get to choose which partition you use. It's the inactive partion always.
HTH
java
If this helps, please rate
www.cisco.com/go/pdihelpdesk
05-26-2010 01:50 PM
Hi Java
Thanks for your reply.
But if the inactive partition is 7.0(1), how is it going to be upgraded to 7.1(3b)? there is no direct path from 7.0(1) to 7.1(3b)
Thank again
AT
05-26-2010 01:54 PM
You use whatever you have on the ACTIVE partition, you DO NOT use the data from the inactive.
HTH
java
If this helps, please rate
www.cisco.com/go/pdihelpdesk
05-26-2010 02:05 PM
Hi again
So,
If I am standing on the active 7.1(2b) with inactive 7.0(1), it will still take my upgrade to 7.1(3b)?
I think -but I am not sure- that we have done the previous step, but we couldn't proceed because there is no space available, how can I solve this problem?
Regards
AT
05-26-2010 09:51 PM
Hi,
I have upgraded CUCM 7.0 (not sure what release is) to CUCM 7.1 (3b) successfully. Is it any document say that CUCM 7.0 (1) can not go directly to 7.1 (3b)?
For your case, I think if the CUCM 7.1 (2b) partition works well, you can switch the active partition to it and upgrade to CUCM 7.1 (3b). CUCM 7.0 will be removed, dont worry about that.
Remember that the upgrade process always get the data from active partition and install new version on in-active partition.
05-27-2010 06:06 AM
Hi AT,
Here is a clip that describes the CUCM upgrade process
With this version of Cisco Unified Communications Manager, you can install upgrade software on your server while the system continues to operate. Two partitions exist on your system: an active, bootable partition and an inactive, bootable partition. The system boots up and operates entirely on the partition that is marked as the active partition.
When you install upgrade software, you install the software on the inactive partition. The system continues to function normally while you are installing the software. When you are ready, you activate the inactive partition and reboot the system with the new upgrade software. The current active partition will then get identified as the inactive partition when the system restarts. The current software remains in the inactive partition until the next upgrade. Your configuration information migrates automatically to the upgraded version in the active partition.
If for any reason you decide to back out of the upgrade, you can restart the system to the inactive partition that contains the older version of the software.
http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/cucos/6_0_1/cucos/iptpch7.html
So, in your example/environment;
The first upgrade moved you from 7.0 (1) on the active and something else on the inactive
and changed you to 7.1(2b) on the active and 7.0(1) on the inactive.
Your next step/upgrade will move you from 7.1(2b) on the active and 7.0(1) on the inactive
and will change you to 7.1(3b) on the active and 7.1(2b) on the inactive. In a two-hop upgrade
process your original (in your case 7.0(1)) will always be lost as part of the second step
Hope this makes sense.
Cheers!
Rob
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