I recently upgraded a Cisco Call Manager environment from 10.5.1 to 10.5.2, and since I had to figure out all the upgrade steps, I figured I'd post my process. I used the upgrade guide found here: Cisco Upgrade Guide
- Login to CM Publisher Disaster Recovery System
a. Backup -> Backup Device -> Add New (if not already present)
b. Backup -> Manual Backup -> All features -> Start Backup - Login to Unity Disaster Recovery System
a. Backup -> Backup Device -> Add New (if not already present)
b. Backup -> Manual Backup -> All features -> Start Backup - Backup all virtual machines (I used XSI backup to do this)
- Snapshot all virtual machines within VMware
- Stop LDAP sync interval on Call Manager and Unity (I use UDS for IM)
a. This is recommended so that LDAP doesn’t attempt to sync during the upgrade - Stop Extension Mobility service -> CM Pub and Sub -> Cisco Unified Serviceability
- Login to CM Pub, Unity Pub and IM&P Pub
a. OS Administration -> Software Upgrades -> Remote filesystem (or DVD drive)
b. Upload new iso and click “Do not reboot after Upgrade” - Wait for the all the Pub’s to load the new ISO
- Login to CM Sub, Unity Sub, and IM&P Sub
a. OS Administration -> Software Upgrades -> Remote filesystem (or DVD drive)
b. Upload new iso and click “Do not reboot after upgrade” - Login to CM Pub
a. OS Administration -> Settings -> Version -> Switch Version
b. Wait for Pub to come back up - Login to CM Sub
a. OS Administration -> Settings -> Version -> Switch Version
b. Wait for Sub to come back up - Check database status
a. SSH to CM Pub:utils dbreplication runtimestate
- value should be “2” - Check phone functionality
- Check version via cli:
show version active
- Verify Extension Mobility service is running
- Done upgrading Call Manager!
- Login to Unity Pub
a. OS Administration -> Settings -> Version -> Switch Version - Wait for Unity Pub to come back up, try checking voicemail from a phone
- Login to Unity Sub
a. OS Administration -> Settings -> Version -> Switch Version - Check database status
a. SSH to Unity Pub:utils dbreplication runtimestate
- value should be “2” - Done upgrading Unity!
- Login to CM Pub and disable IM HA: System -> Presence Redundancy Groups
- Login to IM&P Pub
a. OS Administration -> Settings -> Version -> Switch Version
b. This server took a while to come back up, it has to wait for the Cisco DB to initialize and then the rest of the services will start up - Wait for IM&P Pub to come back up with all services started
- Login to IM&P Sub
a. OS Administration -> Settings -> Version -> Switch Version
b. This server also took a while to come back up, it has to wait for the Cisco DB to initialize and then the rest of the services will start up - Check database status
a. SSH to IM&P Pub:utils dbreplication runtimestate
- value should be “2” - Log into CM Pub and turn on HA for IM cluster
a. HA will take a couple minutes to re-initialize - Done upgrading IM&P!
- Re-enable LDAP sync on Call Manager and Unity
The upgrade went pretty smoothly, with only one hiccup. After I upgraded the Unity Pub, I couldn't access the Unity Sub webpage in order to switch the version and upgrade. The webpage just wouldn't load. I could have restarted Tomcat and tried to get the webpage working, but I decided to proceed with the upgrade, and switched the version from cli with: utils system switch-version
. The upgrade was successful and the entire environment is working great!