01-18-2011 01:36 PM - edited 03-16-2019 02:56 AM
We are running CUCM 6.1.5su2 (6.1.5.12900-7) and need to add a new subscriber. We cannot upgrade directly from 6.1 to 6.1.5su2 during installation. This is according to the Readme file - and I did try with no luck.
So I would like to install using the 6.1 DVD and provide the 6.1.5 iso as the upgrade/patch during the installation process and then after the install completes do a second upgrade using the 6.1.5su2 iso. Will this procedure work?
matt
01-18-2011 02:18 PM
Hi Matt,
I'm thinking you'll need to jump to an interim 6.1(x) build (not 6.1(5)) as
the patch during install portion of this build. Have a look and
you can see that even the "base" 6.1(5) seems to have the same
Direct Upgrade considerations;
Cisco Unified Communications Manager | 6.1(5)SU2 | 6.1(5)SU1 | 6.1(5)1 |
System Version | 6.1.5.12900-7 | 6.1.5.11900-13 | 6.1.5.10000-10 |
Release Date | Oct 6 2010 | May 17 2010 | Feb 4 2010 |
Standard Support | Direct upgrade: 6.1(5)SU1, 6.1(5), 6.1(4a)SU2, 6.1(4a), 6.1(4)SU1, 6.1(4), 6.1(3b)SU1, 6.1(3b), 6.1(3a), 6.1(3) | Direct upgrade: 6.1(5), 6.1(4a)SU2, 6.1(4a), 6.1(4)SU1, 6.1(4), 6.1(3b)SU1, 6.1(3b), 6.1(3a), 6.1(3) | Direct upgrade: 6.1(4a)SU2, 6.1(4a), 6.1(4)SU1, 6.1(4), 6.1(3b)SU1, 6.1(3b), 6.1(3a), 6.1(3), 5.1(3g), 5.1(3f), 5.1(3e), 5.1(3d), 5.1(3c), 5.1(3b), 5.1(3a), 5.1(3) |
Direct upgrade using DMA: none | Direct upgrade using DMA: none | Direct upgrade using DMA: 4.3(2), 4.2(3), 4.1(3) | |
Note |
1 Cisco does not support using the "Upgrade during install" option with 5.1(3x) DVDs and the 6.1.5 tar.gz upgrade patch. See CSCte78503 for more details. |
http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/compat/ccmcompmatr.html#wp189359
Cheers!
Rob
01-18-2011 02:36 PM
Thanks - yes it looks like 6.1(3) would work as an intermediate release. But will it let a 6.1(3) subscriber join an existing 6.1(5) cluster without doing any harm to the database? Assuming it does let it join, and I then do a post-install upgrade 6.1(5)su2, will I need to do a repair or reset on the database to get replication back in synch?
matt
01-18-2011 03:00 PM
Hi Matt,
Great questions!
To be honest I'm not sure how the Publisher and replication will handle
the "wrong version" Sub. I've never had to build one up with these steps.
You can't be the first person who has had this type of conundrum, but if
it were me I would open a TAC case with all the details just to be safe.
Cheers!
Rob
PS: I know this doesn't help you, but this type of case highlights the need for
current build DVD's. You can order new builds as they come out via PUT just
to mitigate this type of issue.
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