tag:blogger.com,1999:blog-4421651675096124175.post8664518995455898043..comments2024-03-02T21:14:43.287-08:00Comments on Unified Communications Guerrilla: CUCM 9.1(2) and the Jump UpgradeWilliam Bellhttp://www.blogger.com/profile/02559158040046322600noreply@blogger.comBlogger22125tag:blogger.com,1999:blog-4421651675096124175.post-58607876480223532492015-09-01T21:37:53.897-07:002015-09-01T21:37:53.897-07:00Great article, This helped me to migrate my 8.x CU...Great article, This helped me to migrate my 8.x CUCM environment to 9.1.2<br />I have documented the notes and practices i considered during my upgrade http://letusexplain.blogspot.com/2015/08/cucm-upgrade-guide-8x-to-912.htmlSenthil Kumar Murugesanhttps://www.blogger.com/profile/17045983595991631814noreply@blogger.comtag:blogger.com,1999:blog-4421651675096124175.post-82085721365032779032014-10-13T14:56:52.353-07:002014-10-13T14:56:52.353-07:00I assume you are referring to the original article...I assume you are referring to the original article. After completing step 5, the VM guest OS is running on an unaligned disk partition. The reason being that the target source versions in the Jump Upgrade process are not optimized for virtualization. <br /><br />Running with unaligned disk partitions is not recommended due the impact on latency and I/O.<br /><br />HTH.<br />-Bill (@ucguerrilla)UC Guerrillahttps://www.blogger.com/profile/14454391786438461256noreply@blogger.comtag:blogger.com,1999:blog-4421651675096124175.post-72713614096322147742014-10-13T12:09:42.645-07:002014-10-13T12:09:42.645-07:00Why would you need to build out another 9.1 cluste...Why would you need to build out another 9.1 cluster? Could you not stop at number 5 and go live on that cluster? Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-4421651675096124175.post-37851139686030861352014-07-22T15:20:22.055-07:002014-07-22T15:20:22.055-07:00Frank,
I haven't been able to successfully pe...Frank,<br /><br />I haven't been able to successfully perform upgrades in VMware for pre-VM versions of CUCM. Well, I have been able to do it but not consistently. It fails more often than not. <br /><br />A while ago I just decided to use the MCS servers we have in our lab to stage this type of upgrade. You may not have that option. But, because I had that option I didn't need to work out the formula for getting a 6.1.1 system to 6.1.3. <br /><br />Maybe someone who comes across this thread has worked it out.<br /><br />HTH.<br /><br />-Bill (@ucguerrilla)UC Guerrillahttps://www.blogger.com/profile/14454391786438461256noreply@blogger.comtag:blogger.com,1999:blog-4421651675096124175.post-31693556408848977872014-07-22T13:02:54.193-07:002014-07-22T13:02:54.193-07:00Bill do you know of any way of doing the entire pr...Bill do you know of any way of doing the entire process in VMware. I have a 6.1.1 cluster that restores into VMware, but I can not patch to 6.1.3, 6.1.4 for the jump start.<br />The issue isn't license or machine spec. the upgrade seems fails after the database transfer.<br /><br />FrankAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-4421651675096124175.post-49957221275718804412014-06-30T15:45:12.980-07:002014-06-30T15:45:12.980-07:00Great post Bill. Thanks for saving me so much tim...Great post Bill. Thanks for saving me so much time reading numerous guides to get this infromation. Now for the 40 hour upgrade for my customer !!! As you say at least we can complete this in a lab environment.Anonymoushttps://www.blogger.com/profile/16942969652578283325noreply@blogger.comtag:blogger.com,1999:blog-4421651675096124175.post-84919656063260965142014-05-14T11:23:51.444-07:002014-05-14T11:23:51.444-07:00Thanks for the advice. I'll get you a round ...Thanks for the advice. I'll get you a round if we run into each other a live. It shouldn't be hard to recognize you.<br /><br /><br />Thanks<br /><br /><br /><br />TerrenceAnonymoushttps://www.blogger.com/profile/07614627783902966449noreply@blogger.comtag:blogger.com,1999:blog-4421651675096124175.post-20613523230150145312014-05-13T22:12:29.977-07:002014-05-13T22:12:29.977-07:00If you are doing the jump upgrade then the recomme...If you are doing the jump upgrade then the recommendation is to stage the entire cluster in the virtual environment to do the upgrade. This is how I do it. I build a staging cluster in a separate staging environment (w/ DNS, NTP, etc. - enough to get through the install checks). Build the staging cluster with the same IP addresses/ hostnames.<br /><br />Then I do the DRS restore and run the jump upgrade process. Once the upgrade is complete, I change the IP address/hostname to the new settings. Do a DRS backup. In parallel, I have already built the new CUCM cluster with the correct IP addresses (changed addresses) and names. I will restore the last DRS backup and then expand the cluster.<br /><br />That is glossing over some details, but hopefully you get the gist.<br /><br />HTH<br /><br />-Bill (@ucguerrilla)UC Guerrillahttps://www.blogger.com/profile/14454391786438461256noreply@blogger.comtag:blogger.com,1999:blog-4421651675096124175.post-79020378413741648612014-05-13T20:31:58.557-07:002014-05-13T20:31:58.557-07:00This is good stuff. However I"m running into...This is good stuff. However I"m running into a situation where I have to change the Hostname, and the IP's of the PUB/SUB during the upgrade process. I'm hoping that I don't get any database corruption. I have the PUB built with the old IP to get DRS to work properly. My issues is now I have to change the IP of the PUB to the new IP address that the customer gave me. All the while, I still have the old SUB IP address, and will be adding a new SUB server to the mix. I'm hoping I can escape this without breaking the database. Anonymoushttps://www.blogger.com/profile/07614627783902966449noreply@blogger.comtag:blogger.com,1999:blog-4421651675096124175.post-65975655962500357562014-02-13T07:06:11.804-08:002014-02-13T07:06:11.804-08:00To :anonymous
Yes you can but you will then need...To :anonymous <br /><br />Yes you can but you will then need to rehost your license to your new Vmware Mac License address.<br />Also like posted here above take care of all extra files are loaded to the new subscriber ( i.e. MOH, and such )Haffihttps://www.blogger.com/profile/06783923642753446758noreply@blogger.comtag:blogger.com,1999:blog-4421651675096124175.post-33539413136264867882014-01-23T20:08:58.384-08:002014-01-23T20:08:58.384-08:00here is my question: If I do have mcs pub and sub ...here is my question: If I do have mcs pub and sub ver 8.0.3, can I just build 8.0.3 in VMware then load cop v1.3 then restore mcs pub backup to VMware then build fresh sub on VMware and let it replicate from pub rather than restoring original sub from mcs serverAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-4421651675096124175.post-19789481651541588802014-01-06T19:32:40.772-08:002014-01-06T19:32:40.772-08:00excellent post Billy!excellent post Billy!MeinkMinsterhttps://www.blogger.com/profile/06607677271274027236noreply@blogger.comtag:blogger.com,1999:blog-4421651675096124175.post-12751281627282797422013-11-14T11:53:36.362-08:002013-11-14T11:53:36.362-08:00Hey Bill.....always great to read your blog! Altho...Hey Bill.....always great to read your blog! Although not perfect, I do agree 100% that the Jump upgrade is a big step forward. I'd rather skip the upgrade altogether though and just go for the 10 beers with ya ;-)<br /><br />Cheers!<br />HuffAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-4421651675096124175.post-33545848821052675802013-10-20T09:48:25.917-07:002013-10-20T09:48:25.917-07:00Well the main new thing here is correcting the lic...Well the main new thing here is correcting the licensing issue if you've ever seen the "Upgrades are prohibited during license grace period" message. Before, it would take licensing to issue a new license on your 6.x/7.x VM in order to proceed with the 8.x/9.x upgrade or to have TAC do a workaround via root (or do yourself via root). The main benefit of the new supported jump upgrade process is the refresh upgrade v1.3 Cop file which will allow you to bypass the licensing check in order to compete the upgrade.Brian Meadehttps://www.blogger.com/profile/10713741178020350909noreply@blogger.comtag:blogger.com,1999:blog-4421651675096124175.post-56137594466986193812013-10-11T19:57:03.943-07:002013-10-11T19:57:03.943-07:00No, Cisco does not support running UCM 6x/7x in vm...No, Cisco does not support running UCM 6x/7x in vmware. What they support is a direct upgrade from specific versions of 6x/7x instead of forcing customers to follow a multi-step upgrade. For the purposes of the Jump Upgrade methodology, you can load the specific 6x/7x versions in vmware. <br /><br />As you noted, this is not a "new" way of thinking. I have been doing upgrades via vmware for a while, myself. What is new is that Cisco has provided a Tac supported process.<br /><br />HTH.<br /><br />-BillUC Guerrillahttps://www.blogger.com/profile/14454391786438461256noreply@blogger.comtag:blogger.com,1999:blog-4421651675096124175.post-65890838555724217552013-10-11T10:09:36.094-07:002013-10-11T10:09:36.094-07:00We've been using this upgrade method since fo...We've been using this upgrade method since for the last two years. We have successfully upgraded CUCM from 6, and 7 versions to 8.5 and higher. Most of the time it includes changing the IP address of the CUCM cluster because you can't have two production systems running with the same IP's. Does Cisco now support running UC version 6 and 7 on VMware?Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-4421651675096124175.post-11608669516459160262013-10-02T16:17:52.601-07:002013-10-02T16:17:52.601-07:00NICE WORK!!! Cisco notes for the upgrade are not ...NICE WORK!!! Cisco notes for the upgrade are not very clear...wish you were able to post step by step instructions for upgrading cluster ENV. from 8.6 to 9.1 CUCM!! Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-4421651675096124175.post-72551208449788276172013-08-22T03:05:38.133-07:002013-08-22T03:05:38.133-07:00Great article Bill... TBH I think there is still a...Great article Bill... TBH I think there is still a long way (hopefully in 10.x) to go before this lengthy process is truly commercially viable; the killer step for me is tearing the upgraded UCS 9.1.2 for a fresh install to get the DRS restore on (imagine rebuilding that 8 x Node cluster). Pretty sure we will just carry on grinding out upgrades using diligince on the existing sub/tftp/moh nodes and a single Pub Bridged upgrade..... though it looks like 9.1.2 isnt on the MCS Compatability matrix even for Bridged.btmhttps://www.blogger.com/profile/12104018996874138622noreply@blogger.comtag:blogger.com,1999:blog-4421651675096124175.post-6184725621397699722013-08-15T16:54:32.046-07:002013-08-15T16:54:32.046-07:00Good to know. Will check out the VoE recording onc...Good to know. Will check out the VoE recording once I get some cycles.<br /><br />Thanks again!<br /><br />-Bill (@ucguerrilla)UC Guerrillahttps://www.blogger.com/profile/14454391786438461256noreply@blogger.comtag:blogger.com,1999:blog-4421651675096124175.post-74807203410350491032013-08-15T16:15:38.489-07:002013-08-15T16:15:38.489-07:00They actually covered the restore/rebuild the subs...They actually covered the restore/rebuild the subscriber in today's VoE about jump upgrades. If you are a partner go check it out. Dan Keller gave a thorough response, which was essentially Bill's 1-4, plus some more info on #5. Apparently, if the new subscriber is the same IP/hostname, the feature services can come up as activated but won't actually run. They have to be deactivated and reactivated before they actually run because of some sort of markings somewhere. Also any trace file configurations are no longer kept. I think that was everything. They are also working on getting the steps for this documented to make it supported.Anonymoushttps://www.blogger.com/profile/10735951098405351373noreply@blogger.comtag:blogger.com,1999:blog-4421651675096124175.post-20752316190532033942013-08-15T15:03:30.890-07:002013-08-15T15:03:30.890-07:00Will,
No problem. I may incorporate this into the...Will,<br /><br />No problem. I may incorporate this into the main blog but to avoid making you wait, here is a summary.<br /><br />1. MOH files. Any MOH files that you have uploaded to IPVMS nodes in the cluster need to be manually uploaded again. You have to be mindful of file names and you may need to retrieve originals from existing UCM nodes.<br /><br />2. TFTP files (backgrounds, ringtones, etc.). Basically, any custom file that you have uploaded to the TFTP nodes in the cluster would need to be manually dealt with.<br /><br />3. Certs (CTL). Mixed mode clusters. The DRS carries with it the various certs in the cluster. If you don't restore the subs then you don't get their certs. <br /><br />4. Certs (ITL). Security By Default. Same consideration as above.<br /><br />5. I have heard mention of the fact that when you add a new subscriber a new unique ID is created. Even if the IP addr and name is the same as in source version. This may result in some "ghosts in the shell". I recently read something on this (in a forum) and haven't been able to confirm. I have checked my lab systems and I see no such "ghosts". So, jury is still out (IMO) on this one. <br /><br />I think that sums it up.<br /><br />-BillUC Guerrillahttps://www.blogger.com/profile/14454391786438461256noreply@blogger.comtag:blogger.com,1999:blog-4421651675096124175.post-6960434073774983172013-08-15T12:46:20.553-07:002013-08-15T12:46:20.553-07:00Can you elaborate on the tradeoffs you mentioned w...Can you elaborate on the tradeoffs you mentioned with the publisher upgrade approach? I haven't done that yet and since it's not an official process I haven't seen it documented.<br /><br />thanks,<br />willAnonymousnoreply@blogger.com