We think you have liked this presentation. If you wish to download it, please recommend it to your friends in any social system. Share buttons are a little bit lower. Thank you!
Presentation is loading. Please wait.
Published byShyanne Joye
Modified about 1 year ago
Saumya Saxena TOI - Refresh Upgrades in Cisco Unity Connection 8.6
© 2011 Cisco and/or its affiliates. All rights reserved. Cisco ConfidentialPresentation_ID 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)
© 2011 Cisco and/or its affiliates. All rights reserved. Cisco ConfidentialPresentation_ID 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
© 2011 Cisco and/or its affiliates. All rights reserved. Cisco ConfidentialPresentation_ID 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).
© 2011 Cisco and/or its affiliates. All rights reserved. Cisco ConfidentialPresentation_ID 5 Notable differences in functionality during upgrade 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) The following applies to standalone RU only:
© 2011 Cisco and/or its affiliates. All rights reserved. Cisco ConfidentialPresentation_ID 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).
© 2011 Cisco and/or its affiliates. All rights reserved. Cisco ConfidentialPresentation_ID 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)
© 2011 Cisco and/or its affiliates. All rights reserved. Cisco ConfidentialPresentation_ID 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
© 2011 Cisco and/or its affiliates. All rights reserved. Cisco ConfidentialPresentation_ID 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
© 2011 Cisco and/or its affiliates. All rights reserved. Cisco ConfidentialPresentation_ID 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
© 2011 Cisco and/or its affiliates. All rights reserved. Cisco ConfidentialPresentation_ID 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
© 2011 Cisco and/or its affiliates. All rights reserved. Cisco ConfidentialPresentation_ID 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
© 2011 Cisco and/or its affiliates. All rights reserved. Cisco ConfidentialPresentation_ID 13 Sample system-history.log 03/21/ :57:06 | root: Cisco Option Install ciscocm.refresh_upgrade_v0.8.cop Start 03/21/ :59:09 | root: Cisco Option Install ciscocm.refresh_upgrade_v0.8.cop Success 03/21/ :26:35 | root: Upgrade (refresh) Start 03/21/ :38:24 | root: Upgrade (refresh) Start-Install 03/21/ :49:37 | root: Boot Start 03/21/ :49:03 | root: Upgrade (refresh) Failure 03/21/ :51:03 | root: Boot Start
© 2011 Cisco and/or its affiliates. All rights reserved. Cisco ConfidentialPresentation_ID 14 Sample install.log 03/23/ :34:57 component_install|Execute "/common/refresh_upgrade/Cisco/connection/scripts/cuc-export RU Export /common/component/connection /usr/local/cm/ /common/log/install/capture.txt"| 03/23/ :57:11 component_install|(CAPTURE) Launching export| 03/23/ :57:11 component_install|File:/common/download/ /Cisco/bin/component_install:798, Function: execute_shell_cmd(), /common/refresh_upgrade/Cisco/connection/scripts/cuc-export RU Export /common/component/connection /usr/local/cm/ /common/log/install/capture.txt failed (1)| 03/23/ :57:11 refresh_upgrade|Exiting with result 1|
© 2011 Cisco and/or its affiliates. All rights reserved. Cisco ConfidentialPresentation_ID 15 Sample cuc-export.log :35:48 + echo 'Attempt to contact the subscriber server failed. Skipping restarting subscriber server services.' :35:48 Attempt to contact the subscriber server failed. Skipping restarting subscriber server services :35:48 + echo 'Restoration of local server (publisher) to secondary server state completed.' :35:48 Restoration of local server (publisher) to secondary server state completed :35:48 + recover_was_run= :35:48 + echo 'Recovery procedure from failed CUC data export done.' :35:48 Recovery procedure from failed CUC data export done :35:48 + main_exit :35:48 + rc= :35:48 + [[ 0 == 0 ]] :35:48 + '[' 0 -ne 0 ']' :35:48 + '[' 0 == 0 ']' :35:48 + rc= :35:48 + '[' 1 '!=' 0 ']' :35:48 ++ basename /common/refresh_upgrade/Cisco/connection/scripts/cuc-export :35:48 + echo 'cuc-export failed.' :35:48 cuc-export failed :35:48 ++ basename /common/refresh_upgrade/Cisco/connection/scripts/cuc-export :35:48 ++ date '+%m/%d/%y %H:%M:%S' :35:48 + echo 'cuc-export: The CUC export script ran at 03/30/11 19:35:48' :35:48 cuc-export: The CUC export script ran at 03/30/11 19:35: :35:48 + exit 1
© 2011 Cisco and/or its affiliates. All rights reserved. Cisco ConfidentialPresentation_ID 16 Helpful Resources TOI presentations from IPCBU for RU in CUCM: eng.cisco.com/Eng/VTG/IPCBU/CUCM/CallManager_MontBlanc/Presentations/Mont Blanc-Refresh-Upgrade-IR1-TOI.pptx eng.cisco.com/Eng/VTG/IPCBU/CUCM/CallManager_MontBlanc/Presentations/Mont Blanc-Refresh-Upgrade-IR2-TOI.pptx
June 10, 2013 XenClient Enterprise 5.0 Synchronizer and Hyper-V.
The ESC-QuickBooks Integration For Use with ESC Version 12.
Migrating WVWC Content to a Personal G-Mail Account Moving messages, contacts, calendar events, and documents.
Unattended Installation for Window XP By Marshall Cooper.
© 2004 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice Command View XP 2.0 HP Restricted.
Windows 2008 Active Directory Configuration – Week 4 of 6 Microsoft Test: Mark McCoy MCSE, CNE, CISSP.
Using H.E.L.P. on a Network Report Solutions Inc. 435 West Broadway Centralia, IL
Cancer Education Database (EDB) Version 2.0 Training Presentation Prepared By: Surveillance and Evaluation Unit Center for Center Surveillance and Control.
FILEMAKER SERVER SOFTWARE & REMOTE ADMINISTRATION FILEMAKER PRO 5.5 SERVER SOFTWARE.
XenClient Enterprise 4.5 Snapback and OS Profiles.
Chapter 17: Recovery System Failure Classification Storage Structure Recovery and Atomicity Log-Based Recovery Shadow Paging Recovery With Concurrent Transactions.
Copyright line. Maintaining an Active Directory Environment Exam Objectives Backup and Recovery Backup and Recovery Offline Maintenance Offline Maintenance.
VMware vCenter Server High Availability Product Support Engineering VMware Confidential.
Microsoft TS Windows 7,Configuring Visit: Pass4sureofficial.com.
4.1 What is new and what has changed? 4.1. Does H.E.L.P. 4.1 work differently? H.E.L.P. 4.1 looks the same It operates the same The icons are the same.
Introduction to Perfect Jury Welcome to the Perfect Jury PowerPoint overview. Perfect Jury was designed to enhance the speed and accuracy of jury administration.
Jump to Contents Instructor Tutorial essignments.com Paperless assignment submission system.
SIMPLE SOLUTIONS FOR COMPLEX ENVIRONMENTS Presentation Template Version: 4.0 Advanced Maintenance Presentation Node Repair & System Upgrade.
Intro to Virtualization Phil Grimes Coach / Mentor Security Consultant.
Preparing for Installation Reviewing the list of tasks Working with DNS Recording information Backing up files Uncompressing the drive Disabling disk mirroring.
MCTS Guide to Microsoft 7 Chapter 2 Installing Windows 7.
Jet Enterprise Installation Instructions for Jet Partners V
MCTS Guide to Microsoft Windows 7 Chapter 13 Enterprise Computing.
BAI613 Packet Telephony Module 6 Enterprise IP telephony.
General Information Please take the time to make note of your merchant identification number in the space provided For questions regarding your merchant.
Introduction to Oracle Physical Structure Physical Structure Logical Structure Logical Structure SGA / PGA SGA / PGA Background Processes Background Processes.
Computer Hope Copyright © Cannady ACOS. All rights reserved.
IP Momentum Confidential Cisco IP Phone Provisioning GuideSylantro- hosted Service Release /06/05.
Student Getting Started Guide *Updated December 2011 to include information on Integrated Digital Book/MindTap Reader.
Version 4.1 CCNA Discovery 2– Chapter 7. Contents 7.1: ISP Services : TCP / IP Protocols 7.2: 7.3: DNS 7.3: 7.4: Application Layer Protocols 7.4.
© 2016 SlidePlayer.com Inc. All rights reserved.