topic Hi Kelvin,The hardcoded in Unified Communications Infrastructure

Migrate CUCM & upgrade firmware in one step?

Mary Manly — Tue, 19 Mar 2019 16:30:36 GMT

I am going to be migrating CUCM using PCD from 8.6 to 10.5, retaining the IP addresses of the servers on "new" VM hardware.

I currently have a device package installed for firmware versions that are newer than what 10.5 comes with, natively. There is a device package available for 10.5 that matches all device firmware I am running on 8.6. I want to retain the firmware versions I have now.

Using PCD, am I able to use the pause function, after the 10.5 install (and before reboot) to install the device package before I take down the old server and bring up the new one so the firmware does not get downgraded to the version 10.5 runs, then upgraded, again, to what I currently have in place?

Or, do I need to install 10.5, let Pub reboot, then install the device package on it, fail all phones over to Pub and then reboot the Subs, removing them from the device pool, install the device packages there and add the Subs back to the device pool?

Or, is there another, better, easier, faster way?

Hi Mary,I would suggest using

Manish Gogna — Thu, 23 Apr 2015 07:50:37 GMT

Hi Mary,

I would suggest using BAT to hardcode the existing firmware version on the IP phones ( in the Phone Configuration page ). Doing that will allow the phones to keep the same load even though the device defaults will change after the upgrade. Once the upgrade is complete you can change the device defaults to the desired version and also remove the hardcoded entries from the IP phones if needed.

HTH

Manish

Hi Mary, In addition to what

Aman Soi — Thu, 23 Apr 2015 10:13:44 GMT

Hi Mary,

In addition to what Manish[+5] has said, if IP phones are assigned IP address through DHCP then, you can change tftp IP address to any dummy by taking maintenance window.Since u are using the same IP address for new CUCM10, so, u can upload the old firmwares [download from CUCM 8] in new CUCM 10.

Now, u can change the tftp IP address back to original one after CUCM 10 is ready.

Not aware whether PCD can help you in option 1 as suggested by you.You can open TAC case for confirmation.

regds,

aman

I like the approach Manish

Mary Manly — Thu, 23 Apr 2015 16:04:08 GMT

I like the approach Manish has suggested and that is actually the path I have been going down, slowly. I thought I was on the right track, until it occurred to me that CUCM 10.5 may not have the phone firmware I have defined, immediately after installation.

Changing the TFTP option I like, but not as much, only due to the extremely large number of DHCP scopes in play for a relatively small number of phones (~3000 total).

At this point, I have been planning on doing what Mahish has suggested (I am over halfway there, manually assigning the firmware version and upgrading them, ahead of time). My only concern is that the firmware files I hard code will not migrate over from the 8.6 to the 10.5 and I will have to manually upload it, after the servers are running the new version. If the firmware does get copied, over, I will be golden! If not, then the phones will be at war with TFTP settings! - Perhaps I'm over-thinking this and as long as the phones already have the firmware on them, it won't matter what the default becomes (briefly) as long as the phones don't actually reset?

I have stepped through the migrate process with PCD to right before the "Start Task" and while there is a pause, I have not found how to insert an (device package) upgrade after 10.5 install and prior to reboot.

I have opened a proactive TAC case and will hopefully find out more detail before tomorrow night!

Thank you both, gentlemen, for your replies!

Great advice, Mary

So after much time of

Mary Manly — Thu, 23 Apr 2015 22:52:50 GMT

So after much time of searching and consulting with our Cisco Reps, my time was wasted.

In the Release Notes for 10.5.1 - the original version I was going to upgrade to - the phone firmware versions are listed under New and Changed Features, in the Release Notes: http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/rel_notes/10_5_2/CUCM_BK_C6A7E384_00_cucm-release-notes-1052/CUCM_BK_C6A7E384_00_cucm-release-notes-1052_chapter_010.html

So, foolishly, I downloaded the Release Notes for ver. 10.5.2 when it became available and looked for the firmware versions in the same location on that documentation:

http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/rel_notes/10_5_2/CUCM_BK_C6A7E384_00_cucm-release-notes-1052/CUCM_BK_C6A7E384_00_cucm-release-notes-1052_chapter_010.html

Well, Ctrl+F did not find anything with firmware in the name, as it does with the first link, so I asked our Cisco Rep. if it is not called out or listed, does that mean that it does not change from the previous version? He said "Yes! That is correct".

However, I had already installed cmterm-devicepack8.6.2_26157-1 so my firmware was upgraded from the versions shown in 10.5.1.

Turns out, I just looked in the wrong place for my information. I should have been looking at the readme: http://www.cisco.com/web/software/282074295/121471/cucm-readme-1052su1.pdf instead.

So, the version I have installed will be the same as the default in 10.5.2 after I upgrade. ~sigh

Thank you for taking the time to respond,
Mary

+5 for you both!

Hi Manish,Good Day.Do we need

kelvinteh15 — Mon, 18 May 2015 01:46:57 GMT

Hi Manish,

Good Day.

Do we need to restart the phone after hardcode the existing firmware version on the IP phone .

Thanks.

best regards,

kelvin

Hi Kelvin,The hardcoded

Manish Gogna — Mon, 18 May 2015 03:06:52 GMT

Hi Kelvin,

The hardcoded version of firmware will be implemented only after the phones have been reset. If the default version under device defaults is the same as the one running on the phone then there is no need for reset.

HTH

Manish

Thanks. The firmware are

kelvinteh15 — Mon, 18 May 2015 08:33:15 GMT

Thanks. The firmware are difference and we do not want to upgrade the firmware . So we will hardcoded it and reset it to make it take effect .

best regards,

kelvin.