Upgrading Call Manager 5.x to 6.x

Unanswered Question
Jun 16th, 2009

Hi,

Can any please pass on the info on how to upgrade CCM 5.x to 6.x..

Faizal

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 4.5 (2 ratings)
Loading.
bigcappa1 Wed, 06/17/2009 - 05:03

Faizal,

Hi, there are some processes you need to go through to get the software and the correct licences.

1. You need to purchase the upgrade licenses via your vendor and then use PUT (Product Upgrade Tool) to register these licences and obtain the licenses and software for the upgrade.

2. Once registered you should receive soon after the software along with documentation containing the PAK codes. Registered the PAK codes using the publisher MAC address. This will then enable licencing to send the version 6 application product licence to you.

once you have the licences then you can upgrade. Here is the excert from the SRND

CALL MANAGER UPGRADING TO VERSION 6

Call Processing Redundancy

You can choose from the following Unified CM redundancy configurations:

• Two to one (2:1) - For every two primary subscribers, there is one shared secondary or backup subscriber.

• One to one (1:1) - For every primary subscriber, there is a secondary or backup subscriber.

The 1:1 redundancy scheme allows upgrades with only the failover periods impacting the cluster. The failover mechanism has been enhanced so that you can achieve failover rates for Skinny Client Control Protocol (SCCP) IP phones of approximately 125 registrations per second. The failover mechanism for Session Initiation Protocol (SIP) phones is approximately 40 registrations per second.

A cluster can be upgraded to Unified CM 6.x without impacting the services. Two different versions (releases) of Unified CM may be on the same server, one in the active partition and the other in the inactive partition. All services and devices use the Unified CM version in the active partition for all Unified CM functionality. During the upgrade process, the cluster operations continue using its current release of Unified CM in the active partition, while the upgrade version gets installed in the inactive partition. Once the upgrade process is completed, the servers can be rebooted to switch the inactive partition to the active partition, thus running the new version of Unified CM.

Upgrading from Unified CM 5.x to Unified CM 6.x

The 1:1 redundancy scheme enables you to upgrade the cluster using the following method:

Step 1

Install the new version of Unified CM on the publisher. Do not reboot.

Step 2

Install the new version of Unified CM on all subscribers simultaneously. Do not reboot.

Step 3

Reboot only the publisher. Switch to the new version of Unified CM and allow some time for the database to initialize.

Step 4

Reboot the TFTP server(s) one at a time. Switch to the new version of Unified CM and wait for the configuration files to be rebuilt before upgrading any further servers in the cluster.

Step 5

Reboot the dedicated music on hold (MoH) server(s) one at a time. Switch to the new version of Unified CM.

Step 6

Reboot the backup subscriber(s) one at a time. Switch to the new version of Unified CM. This step might impact some users if 50/50 load balancing is implemented.

Step 7

Fail-over the devices from the primary subscribers to their backups.

Step 8

Reboot the primary subscriber(s) one at a time. Switch to the new version of Unified CM.

With this upgrade method, there is no period (except for the failover period) when devices are registered to subscriber servers that are running different versions of the Unified CM software.

Note - When upgrading from Cisco Unified CM 5.x to Unified CM 6.x, any changes made to the subscriber's database in the active partition after the start of the upgrade process will not be migrated to the new version of the database.

HTH

Paul

Actions

This Discussion