12-08-2024 05:06 AM
Hello ,
I have a cluster with CUCM and SUB with version 12.5.1.18900-40. I need to install a new SUB with same version of the PUB.
But when I search about it I can find that
Note
Because the 12.5.1.18900-40 build is a non-bootable ISO, it proves useful only for upgrades. You cannot use it for new installations. You may however install with the base version 12.5.1.10000-22 and apply 12.5.1.18900-40 as a patch during the installation.
Also I don't have the bootable iso for the base version 12.5.1.10000-22 .
My questions are
1- If I download the non bootable iso 12.5.1.18900-40 and then convert it to bootable and install it , is there any risk for upcoming TAC support ?
- How can I download the bootable base version 12.5.1.10000-22
- Can see that TAC recommend to install subscriber with upgrade during installation so could you please give me the steps ?
12-08-2024 05:48 AM
1. This is not TAC supported. I know someone that did this and TAC subsequently denied support on the entire CUCM cluster until they rebuilt it.
2. It may be available through My Cisco Entitlements but I haven’t tried that on an end of sale version. TAC can also publish exact ISOs under special file access.
3. Read the upgrade guide; however, in my experience that upgrade-during-install fails more often than it succeeds. I just get TAC or the TSA supporting that customer to publish the exact ISO I need.
PS- That version is end of software maintenance. You should be upgrading to 15. Also, a three-node cluster is not a recommended deployment model; if you’re exceeding 1250 phones the cluster should become five nodes to separate TFTP and call processing subs.
12-08-2024 09:41 AM
If you have a valid subscription for licensing you should be able to download the bootable ISO file for a specific portal at Cisco. At the moment I can’t remember the name of it. Hopefully someone else can help you out with that if you don’t find it.
If you create a bootable ISO on your own you void all TAC support, so I wouldn’t do that.
12-08-2024 11:34 PM
Making the non-bootable version, if I recall correctly, works on 12.5 but not on versions 14 and above. This is not a recommended process, and no one can confirm if you will encounter issues or not—you need to try it yourself. If you do run into issues, it's uncertain whether Cisco TAC will support you.
You take ownership of any issues that occur using the bootable version you create from the non-bootable one.
CUCM 12.5 reaches EOS on August 31, 2025. If you have a valid contract for CUCM, reach out to TAC and request the files for installing the subscriber.
The MCE portal is where you can find the bootable files for installation, and @Jonathan Schulenberg has shared the link to the portal.
I'll try the option of installing the version for which I have the bootable file for 12.5 and then upgrade during the installation. Most of the time, this has encountered issues. This would be an option if you don't have TAC support an alternative will be making the bootable version you create from the non-bootable one.
If you don't have active support, I recommend obtaining it by moving to Flex. Upgrade to versions 14 or 15 and then add the second subscriber.
12-10-2024 09:27 AM
Thanks all for reply , I got the Bootable ISO Bootable_UCSInstall_UCOS_12.5.1.10000-22.sgn and download UCSInstall_UCOS_12.5.1.18900-40.sha512.iso
and tried to install it on my lab , I selected an option with install patch for upgrade , then when installer ask for giving the patch file , There are three options :
1- DVD, when I mounted the patch and select this options it gave me an error with DVD is not selected
2- FTP & SFTP , It gives me the no patches, however I confirmed that there is a connection between both CUCM and SFTP ,
Error attached
Any advise and recommendation ?
12-10-2024 09:59 AM
On your FTP or SFTP server put the upgrade file(s) in a directory that only contains these. Do not use your Download directory.
12-10-2024 04:01 PM
Did it with no luck , I can see that the UCSInstall_UCOS_12.5.1.18900-40.sha512.iso is SHA512 , my question is I know that 12.5x doesn't support SHA till you install a cop file ciscocm.enable-sha512sum-2021-signing-key-v1.0.cop.sgn. so could be this issue ?
12-11-2024 01:53 AM
For the CUCM node you installed using Bootable_UCSInstall_UCOS_12.5.1.10000-22, to recognize the file UCSInstall_UCOS_12.5.1.18900-40.sha512.iso as a valid upgrade, you need to have the COP files or be on version 12.5.1.12013-1 or above.
12-11-2024 06:35 AM
Could you kindly send me the link which share that information and also specifies which cop files are required here? Bootable_UCSInstall_UCOS_12.5.1.10000-2 is the only bootable version I have. so cant go to 2.5.1.12013-1
12-11-2024 07:19 AM
If you have a bootable 12.5.1.10000-2, but your system was updated to 12.5.1.12013-1 then you should have a non-bootable ISO for the upgrade. You can install the 12.5.1.10000-2 and later upgrade to 12.5.1.12013-1 prior to attempting the restore. Alternately, the install wizard provides an option to 'upgrade with a patch', where you start the install with the bootable ISO and then switch to the upgrade ISO to complete the installation.
Maren
12-11-2024 07:58 AM
That's wat I did , I have the Bootable ISO 12.5.1.10000-22 and my system is 2.5.1.18900-40 so I downloaded the non-bootable ISO, and while I Install the basic version , selected insert a Patch upgrade. prompt has been appeared to locate the upgrade cop file via SFTP, FTP and DVD but it doesn't work. it gives me an error with invalid patch. so any suggestion ?
12-11-2024 09:13 AM
Can you access the FTP or SFTP via a normal client with the same credentials and if so do you see the upgrade ISO in that directory? Second thing, do you happen to have any other files than CM upgrade ISO/COP files in the directory set as used by the FTP/SFTP server? If you do please move the file(s) into a directory that only contains the CM upgrade file(s) and update the configuration in your FTP/SFTP server software.
12-11-2024 11:01 AM - edited 12-11-2024 11:01 AM
12-12-2024 02:33 AM
As @Maren Mahoney mentioned, you can install the node with Bootable_UCSInstall_UCOS_12.5.1.10000-2, then either upgrade to 12.5.1.12013-1 or install the COP file (if that works), and finally upgrade to 12.5.1.18900-40.
12-11-2024 11:17 AM
Would you kindly share this informational link?
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