[cisco-voip] Chaining CCM upgrades

[Lelio Fulgenzi]

It seems that there is a conflict in documentation here. The Q&A says one thing and the compatibility mattrix says another. I will be opening a case with the TAC tomorow to try and clear things up and see what can be done about getting TAC support for a 3.3(3) -> 4.1(2) upgrade. 

According to the Cisco CallManager 4.1 Q&A reference page you can order an upgrade package for 3.X to 4.1. In particular:-----                                                                -----

    Q. What is the price of the upgrade to Cisco CallManager 4.1?
    A. Customers with a Software Application Support plus Upgrades (SASU) contract who currently are running Cisco CallManager 3.2, 3.3, or 4.0 and desire to upgrade to Cisco CallManager 4.1 can order their free upgrades using the PUT tool located at http://www.cisco.com/upgrade.

According to Upgrading Cisco CallManager Release 4.1(2)-Preinstallation Information some information regarding which versions are supported. 3.3 is mentioned, but when you go to the compatibility matrix, it's only 3.3(4) that is supported. 
    From which versions of Cisco CallManager can I upgrade to Cisco CallManager Release 4.1(2)? 
    To verify which versions of Cisco CallManager are compatible for upgrade, refer to the Cisco CallManager Compatibility Matrix. To obtain the most recent version of this document, go to http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/ccmcomp.htm 

    If your server runs a version of Cisco CallManager Release 3.2 or earlier, you must first upgrade every server in the cluster to the latest version of Cisco CallManager Release 3.3 before you can upgrade to a version of Cisco CallManager Release 4.1. For information on upgrading to Cisco CallManager Release 3.3 or 4.0, refer to the appropriate version of the Upgrading Cisco CallManager document. You cannot upgrade directly from Cisco CallManager Release 3.2 or earlier to Cisco CallManager Release 4.1. 

    Before you perform any upgrade procedures, Cisco strongly recommends that you install the latest operating system upgrade/service release, SQL service releases/hotfixes, and Cisco CallManager service release for the versions that currently run in the cluster. Cisco provides the service release and corresponding readme documentation on cisco.com. To obtain these documents, go to http://www.cisco.com/public/sw-center/sw-voice.shtml. 


So, your (and our) upgrade path seems like it will be 3.3(3) -> 3.3(4) -> 4.1(2). This seems a little odd, since we were told that the 3.3(4) would be a train of it's own, and 3.3(3) is moving to the 4.x train. This might actually buy us something, since 3.3(4) is compatible with current and some of the later versions of IPCC express and CRS that 3.3(3) is not compatible with, giving us a migration path to upgrade CRS/IPCC after our 3.3(4) upgrade.


--------------------------------------------------------------------------------

Caution Cisco recommends that you only upgrade to Cisco CallManager 4.1(2) from a version that is compatible for upgrade to 4.1(2). Versions that are not compatible for upgrade to 4.1(2) may contain features that are not supported in 4.1(2). If you upgrade from an unsupported version, you will not be able to access those features that are not supported in 4.1(2) and you will lose the data that is associated with those features. 
--------------------------------------------------------------------------------






Lelio Fulgenzi, B.A.                                  lelio at uoguelph.ca.eh
Network Analyst (CCS)
University of Guelph                             FAX:(519) 767-1060 JNHN
Guelph, Ontario N1G 2W1                          TEL:(519) 824-4120 x56354
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
     remove the 1st letter of the canadian alphabet from my email, eh!
  ----- Original Message ----- 
  From: Mike Armstrong 
  To: cisco-voip at puck.nether.net 
  Sent: Wednesday, December 29, 2004 9:42 PM
  Subject: [cisco-voip] Chaining CCM upgrades


  We want to go from 3.3(3) to 4.1(2), which really could involve a 
  3.3(3)->4.0(1)->4.0(1)sr2a->4.0(2a)->4.0(2a)sr1a->4.1(2) chain.  I'd like to 
  shorten the process by

  a) not installing the interim service releases, and
  b) ignoring the subscriber altogether until the publisher is up to 4.1(2), 
  then simply building a new 4.1(2) subscriber and linking it up.  Service 
  interruption is not a problem.

  Any thoughts/wisdom/comments/advice?

  Mike Armstrong
  UF/IFAS CREC 

  _______________________________________________
  cisco-voip mailing list
  cisco-voip at puck.nether.net
  https://puck.nether.net/mailman/listinfo/cisco-voip
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20041229/a4aa8b6d/attachment-0001.html