[cisco-voip] CUCM Upgrade from 8.6.2 to 8.6.2a su3 -- Advice Request

[Chris Ward (chrward)]

The phone upgrade should kick off as soon as the phones re-home to an upgraded CCM server as I believe in this process they re-download their TFTP file which would have the upgraded version in it. If that has changed and they don't, then you just need to reset the phones, preferably a group at a time to not overwhelm the TFTP process (although if it's only a 100 phones or so, then don't worry about it, they can all upgrade at the same time.)

+Chris
TME - Unity Connection and MediaSense

From: Rob Pucci [mailto:rpucci at hakur.net]
Sent: Tuesday, November 12, 2013 11:31 AM
To: Chris Ward (chrward)
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] CUCM Upgrade from 8.6.2 to 8.6.2a su3 -- Advice Request

Thanks for the quick reply and the dance is something I am familiar with...  It funny how if something worked last time, whatever it is, it becomes a requirement for the next upgrade.  Thank goodness there isn't a camera in my cube, because my "It Worked!" dance is quite the sight to see.

With the phone upgrades, is that process automatic or do the phones have to be restarted to kick off the upgrade?  Also, thanks for the CCX link.  I will watch for that.

-Rob

On Tue, Nov 12, 2013 at 8:19 AM, Chris Ward (chrward) <chrward at cisco.com<mailto:chrward at cisco.com>> wrote:
You forgot the upgrade dance and holding your breath!

As a Cisco employee, I have total faith in this upgrade process. :) But seriously, you have the steps correct. And be patient on the reboots. After upgrades, the first reboot takes longer than others, so just bear with it. If you think its hung, just wait longer.

You will need to either allow for phone upgrades (phone may be down during upgrades depending on the model), or you can do them ahead of time with a Device Package. Another thing to add. On your CCX application, the JTAPI version will *may* change in CUCM after the switch version is completed.

CCX will need to be updated:
http://docwiki.cisco.com/wiki/JTAPI_Client_and_data_resynchronization

+Chris
TME - Unity Connection and MediaSense

From: cisco-voip [mailto:cisco-voip-bounces at puck.nether.net<mailto:cisco-voip-bounces at puck.nether.net>] On Behalf Of Rob Pucci
Sent: Tuesday, November 12, 2013 11:04 AM
To: cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
Subject: [cisco-voip] CUCM Upgrade from 8.6.2 to 8.6.2a su3 -- Advice Request

I am doing my first CUCM upgrade (from version 8.6.2 to 8.6.2a su3) and I wanted a sanity check on my planned process:

  1.  Verify latest backups were successful via Disaster Recovery System / Backup / History
  2.  Insert DVD into Publisher
  3.  Login to CUC OS Administration
  4.  Navigate to Software/Upgrades/Install Upgrade
  5.  Choose the DVD, enter "/" in the directory field, and click next
  6.  Select the upgrade version I am installing (8.6.2a su3)
  7.  Choose "Do not switch to new version after upgrade"
  8.  Click Finish once the install is completed
At that point I will accomplish the same upgrade steps on the Subscriber, again selecting "Do not switch to new version after the upgrade".  Once that system is completed I will use Settings / Version / Switch Version on the Publisher.  From what I read it takes around 15 minutes for the system to stabilize.  Once all of the services are back online on the Publisher I will choose Settings / Version / Switch Version on the Subscriber.

After the Subscriber comes back online I will:


  1.  Verify database replication using Cisco Unified Reporting / Unified CM Database Status Report
  2.  Check to make sure all of my phones, media resources, gateways, CTI devices, and SIP trunks are registered and online
  3.  Make test calls to voicemail, a CCX application, extension to extension, and extension to external to make sure everything is working.
Do you see anything that I am missing and of course thanks for any advice!

-Rob

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20131112/ecc24eac/attachment.html>