Need some advise i am going to upgrade pub and 3 subs from cucm 6.1 to 6.5 can i install the upgrade in the inactive partition on each server or do i have to do the publisher reboot and than do the 3 subs the same way??????
The "inactive partition" method for the CUCM upgrade process is the desired
The new vesrion is built on the inactive partition and just sits there
until instructed to switch versions. here is an example from the 6.x SRND
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 6.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 Unified CM 6.0 to Unified CM 6.1 or later releases, any changes made to user-facing call processing features in the active partition of the subscriber's database will be migrated to the new version of the database. Any other database changes made in the active partition of the publisher's database will not be migrated to the new version of the database.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...