TOI - Refresh Upgrades in Cisco Unity Connection 8.6

1. TOI - Refresh Upgrades in Cisco Unity Connection 8.6 SaumyaSaxena

2. What is a Refresh Upgrade? • New upgrade implementation starting in Cisco Unity Connection 8.6 • Upgrades from older versions of RHEL cannot be accomplished using the standard L2 upgrade process in Cisco Unity Connection • Performs a “clean install” into the inactive partition, rather than installing to the inactive partition while the old version remains running • Commonly referred to as an “RU” (or Refresh Upgrade)

3. How is this different than previous upgrades? • Requires a COP file to be installed prior to beginning the RU (without the COP file, attempts to upgrade to 8.6 will be blocked from the start) • Looks like a “clean install” when viewing local console of machine • No switch-version (that the administrator will know about) • Post-upgrade CLI / GUI question is changed (be careful of the default): • CLI – Do not automatically switch back to the previous version after the upgrade completes • Web – Do not reboot to the previous partition after the upgrade completes • “Reconfiguration and Upgrade Guide for Cisco Unity Connection 8.x” will have more detailed information

4. Three phases of a refresh upgrade • Export phase – exports all Informix databases, and some platform files, for use later on in the RU process (normally in /common on the hard drive, except for 7825-H3 and 7828-H3 platforms). This phase happens at the beginning of the upgrade process, before any reboots take place. • Install phase – After the export phase completes, the machine reboots into the other partition, and begins to install the new version of Cisco Unity Connection (including RHEL, etc.). This phase also may contain multiple reboots during its process. • Import phase – After everything is installed, the previously-exported data will be imported back to the new install (DB content into Informix, platform files to the proper locations on the hard drive).

5. Notable differences in functionality during upgrade The following applies to standalone RU only: • Most services will be offline for the entire duration of the RU • All administrative interfaces will be offline • All phone access (including voice message access) will be offline • Plan on the server being offline for however long an L2 upgrade + switch-version would take on the system previously (as a rough estimate)

6. 7825-H3 and 7828-H3 refresh upgrades • RAID driver changing for these platforms in Cisco Unity Connection 8.6 (current HW RAID driver in existing versions is not supported in RHEL 5.5, with Connection 8.6) • Part of RU for these platforms is a switch to a new software-based RAID driver that is supported in RHEL 5.5 • To switch the RAID driver, the existing HD content must be formatted • External USB Drive Requirement: minimum 128GB (during Export Phase, data will be put on this USB drive prior to the machine’s hard drives being formatted to use the new RAID driver).

7. 7825-H3 and 7828-H3 refresh upgrades (cont.) • It is very important to make sure DRS backups are taken with these platforms prior to beginning any upgrades • Reverting to older version after RU completes is not allowed (once the hard drive is formatted, there is no old version to revert back to anymore) • Instead of revert, you can re-install old version, then restore from previous DRS backup • In the event of an RU failure on these platforms, the machine may not be able to automatically revert back to the previous version (esp. if the hard drive is already been formatted)

8. Connection cluster refresh upgrades • Subscriber must be online and running prior to beginning RU on publisher (otherwise publisher RU will fail) • Publisher must be completely upgraded and running prior to beginning RU on subscriber (otherwise subscriber RU will fail) • Duration of a cluster RU (both publisher, and subscriber) will be notably longer than previous L2 cluster upgrades (roughly equivalent to two RU back-to-back) • Subscriber will be expected to be online and functional for much longer while publisher is upgrading, and vice versa

9. Cluster refresh upgrade functionality differences • While the publisher is being upgraded: • All admin interfaces (and other services) on both publisher and subscriber are disabled • Phone interface on publisher disabled, still enabled on subscriber • Users can still access messages on subscriber through phone, no state changes are preserved! • Any phone messages left on subscriber during this process will not be delivered until subscriber RU is started • While the subscriber is being upgraded: • Publisher is fully-functional, able to take messages and allow users to retrieve messages on all interfaces • Publisher will also deliver any messages from the subscriber while the publisher was being upgraded • Subscriber will pull down database from publisher, overwriting any local changes that took place while the publisher was upgrading (ex. changes to message read state) • When the subscriber finishes its RU, the cluster should be restored, and the publisher will have primary role

10. Reverting from Connection 8.6 to earlier versions • No voice messages left after upgrading to 8.6 will be migrated back to the previous version • Any changes to greetings or voice names after upgrading to 8.6 will also not be migrated back to the previous version • As before, any administrative changes (user adds, changes, deletes, etc.) after upgrading to 8.6 are also not migrated back to the previous version

11. What logs to gather for troubleshooting • All logs on this slide will be located in /var/log/install on the machine • system-history.log: contains previous version and new version information. Also indicates whether upgrade succeeded or failed. • install.log: platform install log file (grab the one with the latest timestamp in the file name). This is the main log documenting the upgrade procedure. • cuc-export.log: contains the logged information from the execution of the Connection Export Phase of the RU • cuc-install.log: contains the logged information from the execution of the Connection Install Phase of the RU • cuc-import.log: contains the logged information from the execution of the Connection Import Phase of the RU

12. What logs to gather for troubleshooting (cont.) • /var/log/active/cuc/informix.log: contains any logging from Informix to capture database-related changes during the upgrade • When troubleshooting RU for a clustered install, be sure to gather the log sets from both the publisher and the subscriber

13. Sample system-history.log • 03/21/2011 07:57:06 | root: Cisco Option Install ciscocm.refresh_upgrade_v0.8.cop Start • 03/21/2011 07:59:09 | root: Cisco Option Install ciscocm.refresh_upgrade_v0.8.cop Success • 03/21/2011 08:26:35 | root: Upgrade (refresh) 8.6.0.98000-54 Start • 03/21/2011 08:38:24 | root: Upgrade (refresh) 8.6.0.98000-54 Start-Install • 03/21/2011 08:49:37 | root: Boot 8.6.0.98000-54 Start • 03/21/2011 09:49:03 | root: Upgrade (refresh) 8.6.0.98000-54 Failure • 03/21/2011 09:51:03 | root: Boot 7.1.3.30000-1 Start

14. Sample install.log • 03/23/2011 16:34:57 component_install|Execute "/common/refresh_upgrade/Cisco/connection/scripts/cuc-export RU Export 8.6.0.99091-9 8.5.1.10000-26 /common/component/connection /usr/local/cm/ /common/log/install/capture.txt"|<LVL::Debug> • 03/23/2011 16:57:11 component_install|(CAPTURE) Launching export|<LVL::Debug> • 03/23/2011 16:57:11 component_install|File:/common/download/8.6.0.99091-9/Cisco/bin/component_install:798, Function: execute_shell_cmd(), /common/refresh_upgrade/Cisco/connection/scripts/cuc-export RU Export 8.6.0.99091-9 8.5.1.10000-26 /common/component/connection /usr/local/cm/ /common/log/install/capture.txtfailed (1)|<LVL::Error> • 03/23/2011 16:57:11 refresh_upgrade|Exiting with result 1|<LVL::Info>

15. Sample cuc-export.log • 2011-03-30 19:35:48 + echo 'Attempt to contact the subscriber server failed. Skipping restarting subscriber server services.'2011-03-30 19:35:48 Attempt to contact the subscriber server failed. Skipping restarting subscriber server services.2011-03-30 19:35:48 + echo 'Restoration of local server (publisher) to secondary server state completed.'2011-03-30 19:35:48 Restoration of local server (publisher) to secondary server state completed.2011-03-30 19:35:48 + recover_was_run=02011-03-30 19:35:48 + echo 'Recovery procedure from failed CUC data export done.'2011-03-30 19:35:48 Recovery procedure from failed CUC data export done.2011-03-30 19:35:48 + main_exit2011-03-30 19:35:48 + rc=02011-03-30 19:35:48 + [[ 0 == 0 ]]2011-03-30 19:35:48 + '[' 0 -ne 0 ']'2011-03-30 19:35:48 + '[' 0 == 0 ']'2011-03-30 19:35:48 + rc=12011-03-30 19:35:48 + '[' 1 '!=' 0 ']'2011-03-30 19:35:48 ++ basename /common/refresh_upgrade/Cisco/connection/scripts/cuc-export2011-03-30 19:35:48 + echo 'cuc-export failed.'2011-03-30 19:35:48 cuc-export failed.2011-03-30 19:35:48 ++ basename /common/refresh_upgrade/Cisco/connection/scripts/cuc-export2011-03-30 19:35:48 ++ date '+%m/%d/%y %H:%M:%S'2011-03-30 19:35:48 + echo 'cuc-export: The CUC export script ran at 03/30/11 19:35:48'2011-03-30 19:35:48 cuc-export: The CUC export script ran at 03/30/11 19:35:482011-03-30 19:35:48 + exit 1

16. Helpful Resources • TOI presentations from IPCBU for RU in CUCM: • http://wwwin-eng.cisco.com/Eng/VTG/IPCBU/CUCM/CallManager_MontBlanc/Presentations/MontBlanc-Refresh-Upgrade-IR1-TOI.pptx • http://wwwin-eng.cisco.com/Eng/VTG/IPCBU/CUCM/CallManager_MontBlanc/Presentations/MontBlanc-Refresh-Upgrade-IR2-TOI.pptx