CUCM 9.1(2)SU1 and CUC 9.1(2)SU1 Upgrade Tips

CUCM Publisher

Upgraded from 9.1(2) to 9.1(2)SU1 [9.1.2.11900-12] over the weekend because of the extensive list of bugfixes.  Release notes – http://www.cisco.com/web/software/282074295/108330/cucm-readme-912su1.pdf

Download the update here – http://software.cisco.com/download/release.html?mdfid=284510097&flowid=45900&softwareid=282074295&release=9.1%282%29SU1&relind=AVAILABLE&rellifecycle=&reltype=latest

The publisher failed with the Common partition not having enough space.  This was a common issue in the 8.x to 9.x upgrades.

The fix is to use RTMT to clear out logs and other things in the common partition, or much easier is to use the “Free common space COP file” – ciscocm.free_common_space_v1.0.cop.sgn.cop file from here – http://software.cisco.com/download/release.html?mdfid=284510097&flowid=45900&softwareid=282204704&release=COP-Files&relind=AVAILABLE&rellifecycle=&reltype=latest

Once you install this COP file the common partition should have enough free space to install the upgrade.  I’ve seen this not clear out enough space in one other upgrade, but in the 9.1(2) to 9.1(2)SU1 upgrade it worked like a champ.

Unity Connection

While the Publisher was upgrading, I initiated the Unity Connection (CUC) upgrade to 9.1(2)SU1.  This install started and failed with a very nondescript error:

The solution in my case was documented in several TAC cases: Reboot the CUC server before doing the install.  I did this and the CUC upgrade completed without any issues.

One major bug fix I’ve been waiting for was a unified inbox issue where users on Exchange with very large mailboxes would have CUC quit syncing VM.  SU1 fixes that problem.

CUCM Subscribers

Once the publisher finished and was rebooted the subscribers upgraded without issue.

3 thoughts on “CUCM 9.1(2)SU1 and CUC 9.1(2)SU1 Upgrade Tips

  1. I have to do this same upgrade, tac is telling me I have to upgrade and reboot pub and sub at same time taking a 25 minute or longer outage which is not good as we have a 24 hour Call Center. My thoughts are to upgrade pub, reboot and make sure it’s up and accessible then upgrade sub, reboot. Phones should only be down to register to pub since all are on sub. Once sub comes up phones register back. Am I thinking right on this?

      • Thats what I did, upgraded last night, worked good other than didn`t know about having to resync jtapi in CCX. They are telling me that will be 5 to 10 minutes that my agents will be offliine.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s