#CISCO CUCM 8.6 UPGRADE LICENSE LICENSE#
You need to follow all of the Cisco guidance related to migrating licenses to CUCM 9.1 and the Enterprise License Manager (ELM) IOW, you need to emulate your production environment (to a degree) You need to segregate the VMware environment you are using to do the Jump Upgrade and you also need to account for the IP addresses of your system, NTP, DNS, and related services. You want to minimize steps to build the interim clusters in vmware.
![cisco cucm 8.6 upgrade license cisco cucm 8.6 upgrade license](https://www.firewall.cx/images/stories/cisco-voice-ue-license-1a.jpg)
![cisco cucm 8.6 upgrade license cisco cucm 8.6 upgrade license](https://community.cisco.com/legacyfs/online/legacy/0/6/0/128060-2-CUCM.png)
To pull this upgrade off you do need to make sure you address several pre-requisites: The latter can lead to bad decision making and, therefore, have a direct impact on the former. So, stress is lower and I for one engineer all of my upgrade processes to reduce risk and stress. The upside? You can do most of this during normal working hours. It is still a black hole in regards to overall time. Coming up with methods to optimize the process by doing things in parallel will help the time factor. from the source version to the target versionĪs you can probably deduce from the process steps, this upgrade method isn't necessarily "quick" but it does achieve its objective of minimizing impact to production users.
![cisco cucm 8.6 upgrade license cisco cucm 8.6 upgrade license](https://www.cisco.com/c/dam/en/us/support/docs/voice-unified-communications/unified-communications-manager-callmanager/116130-config-cucm-elm-00-03.jpeg)
In VMware, build out a new cluster (all nodes) at the base version you are running in production.Perform a DRS backup of your production system.You need to get your production system to one of the following versions: 6.1.4, 6.1.5, 7.1.3, or 7.1.5 (process not shown above).