CCM 4.1.3 to $.2.3

Unanswered Question
Jan 29th, 2008
User Badges:

planning an upgrade from 4.1.3 to 4.2.1, and then to 4.2.3, possibly 4.2.3SR3. I am hopeful to get this done in one maintenance window. Is there a time period which I should let pass between upgrading and letting the pub/sub sync, before starting to upgrade again? thanks

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 4.9 (6 ratings)
Loading.
Rob Huffman Tue, 01/29/2008 - 13:21
User Badges:
  • Super Blue, 32500 points or more
  • Hall of Fame,

    Founding Member

  • Cisco Designated VIP,

    2017 IP Telephony, Unified Communications

Hi Pete,


You should be able to skip the CCM 4.2(1) portion of the plan and go straight from CCM 4.1(3) to CCM 4.2(3).


The 4.2(3)sr3 part is really quick as well :)



http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/upgrade/4_2_3/upgrfrom.html



Hope this helps!

Rob

balitewiczp Tue, 01/29/2008 - 14:39
User Badges:

Thanks, that will certainly cut down on the install time. Is there a period of time I should wait between pub/sub 4.2(3)reboots, and the start of the SR3 install?


also, what will happen if I use the wrong passphrase /sa passwords. All I have to go on is the documentation of a former employee. thanks

Rob Huffman Tue, 01/29/2008 - 15:44
User Badges:
  • Super Blue, 32500 points or more
  • Hall of Fame,

    Founding Member

  • Cisco Designated VIP,

    2017 IP Telephony, Unified Communications

Hi Pete,


The recommendation would be to Upgrade the Pub (including SR's) first. Then upgrade the Sub/Subs (including SR's) then do a final reboot of all boxes.


Here is some good reference material for an upgrade to CCM 4.2(3);


Upgrading a Cisco CallManager Cluster


The Rules of the Cisco CallManager Upgrade


Follow these rules when you upgrade Cisco CallManager:


Always upgrade the publisher and standalone TFTP server (if exists) first.


Upgrade the backup Cisco CallManagers second.


Upgrade the primary Cisco CallManagers last.


After all Cisco CallManagers are upgraded, all servers must be rebooted.


Make sure that when the SA and Administrator passwords are set they are the same for all servers in the cluster.


From this excellent doc;



Upgrading a Cisco CallManager Cluster


http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_tech_note09186a00800945ca.shtml#upgradepublisher


You will want to sync up or at least check the passwords before you ever start. The method for CCM 4.x is listed in this doc;


Recovering an SQLSvc Account Password


http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_tech_note09186a0080095225.shtml



Hope this helps!

Rob

balitewiczp Thu, 01/31/2008 - 13:12
User Badges:

yes, the info helps. Does the upgrade effect the phone loads? I have upgraded the phone loads since the inception of 4.13, and I'm concerned the install of 4.2.3 might downgrade these loads.

Jaime Valencia Thu, 01/31/2008 - 13:21
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    2011

the upgrade does affect the phone loads and there is the chance you have a higher version than the ones the original CCM 4.2(3), if you want to verify what's going to be installed you can look at the readme for CCM 4.2(3) at the download page


http://www.cisco.com/cgi-bin/tablebuild.pl/callmgr-42

ciscocm-ffu.4-2-3-ReadMe.pdf


that contains all the firmware version that will be installed


HTH

balitewiczp Thu, 01/31/2008 - 13:30
User Badges:

yes, this helps. the other question I had is to upgrade the pub, including the SR, and then start on the sub, or upgrade the pub then sub, and then starton the SR. Also, is a final reboot of all servers absolutely necessary. thanks

Jaime Valencia Thu, 01/31/2008 - 14:05
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    2011

upgrade both servers to base version (PUB, then SUB)

then apply the SR to both (PUB then SUB)


the cluster reboot is recommended to sync the SDL layer after all the updates.

it's not really mandatory but a best practice


HTH

Actions

This Discussion