#CISCO CUCM 8.6 RELEASE NOTES INSTALL#
#CISCO CUCM 8.6 RELEASE NOTES UPGRADE#
#CISCO CUCM 8.6 RELEASE NOTES SOFTWARE#

Considering that a CUCM reboot can take 15-20 minutes to complete each time during an upgrade, you’re looking at nearly an hour of rebooting time under certain circumstances. The system is going to reboot no less than twice, perhaps even three times.

#CISCO CUCM 8.6 RELEASE NOTES UPGRADE#

It turns out that when you upgrade from 8.5 to 8.6, its going to take a while. There’s another reason for putting this email field in here now, though. Probably a long overdue option that comes in handy for those of us that spend more than a few stress-filled moments clicking the Refresh buttons on our web browsers waiting for CUCM to come back to life after an upgrade. This allows the server to send you an email whenever the upgrade is completed. As near as I can tell, it makes some changes to the Tomcat service on the server as well as adding two new fields to the Install/Upgrade window: It’s also going to reboot the server after installation.

It needs to be installed on every server in the cluster. The 8.6 installer checks for the presence of this file and won’t kick off unless it’s present. This file is ciscocm.refresh_upgrade_v1.0.cop.sgn.

#CISCO CUCM 8.6 RELEASE NOTES INSTALL#

This is part of the reason for the extra steps in moving to CUCM 8.6įirstly, Cisco wants you to install a special Cisco Options Package (COP) file on 8.5(1) systems. The bad news is that the upgrade of the OS can be a bit destructive. This is good news that allows the system to stay current and support a larger variety of hardware. With version 8.6, Cisco has moved away from an OS platform based on Redhat Enterprise Linux (RHEL) 4 and upgraded the underlying OS to RHEL 5. Development stops on the old version and it’s time to move to the new one.

#CISCO CUCM 8.6 RELEASE NOTES SOFTWARE#

However, much like the shift from Windows 2000 to Windows 2003, software eventually reaches the end of its life. Cisco provides patches for the OS with every release of CUCM software and the user never knows what’s going on because of the way the system installs the patches transparently. The Telephony OS in CUCM 5.x was new for those used to working in Windows but somewhat familiar to those that have seen Linux before, even if the login shell looked nothing like bash. Cisco eventually ported CallManager 4.3 to Windows Server 2003, but in the end the decision was made to move to an appliance-based OS that utilized Linux. Up until version 5, that was Windows 2000 with some hardening and customizations. Huh? What’s a refresh upgrade? Why isn’t this ISO file working? Well, it turns out Cisco needs you to take an additional step first.ĬUCM runs on an operating system.

19:31:48 refresh_upgrade|*** Please install the Refresh Upgrade COP, and reattempt the upgrade ***| If you’ve popped a freshly burned 8.6(1) ISO into your DVD drive or copied it via SFTP, you kicked off you installation and likely saw the following error message: 19:31:48 refresh_upgrade|********** Upgrade Failed **********| However, if you are a user of CUCM 8.x and you’re trying to move to 8.6, you’ve probably had a couple of head scratching moments so far. If you are a Cisco voice rock star, you all too often find yourself upgrading to newer releases of Cisco Unified Communications Manager (CUCM) to support new devices like the Cius or fix show stopping bugs like the 180-day uptime lockup. Whether we are patching bugs or adding new features to our systems, the installation of software never seems to end. Upgrades are a fact of life for network rock stars.

Cisco cucm 8.6 release notes