CUCM Install Upgrade Failure Issues

Available Languages

Download Options

  • PDF     (9.4 KB)
    View with Adobe Reader on a variety of devices
  • ePub     (79.2 KB)
    View in various apps on iPhone, iPad, Android, Sony Reader, or Windows Phone
  • Mobi (Kindle)     (64.0 KB)
    View on Kindle device or Kindle app on multiple devices
Updated:September 5, 2020
Document ID:213682

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

    Introduction

    This document contains useful information about the details and logs, which you have to share with TAC for Cisco Unified Communications Manager (CUCM) Install Upgrade failure issues. Proactive, collection and uploads of the logs allow the Cisco Technical Support team to begin the investigation of your Service Request more quickly and efficiently.

    Problem

    What kind of logs and details to be collected and shared with TAC  Service Request for Install Upgrade failure issues. 

    Information to Collect

    Upgrade Failed Logs/Details

    These details/logs are needed for analysis if the upgrade is failed.

    • Share the screenshot or upgrade error messages for the Upgrade failure.
    • Full CallManager version that you're upgrading to (10.5.X.XXXXX-X).


    Collect these Logs from CLI of Publisher and from Upgrade failed node

    • show network cluster
    • utils diagnose test
    • show version active
    • show version inactive
    • utils core active list
    • show status
    • show hardware
    • utils dbreplication runtimestate
    • utils service list
    • utils system upgrade status


    Collect these logs from CLI of upgrade failed node and get the files downloaded via SFTP.


    file get install *


    OR


    You can download the upgrade logs also via RTMT, navigate to Tools > Trace & Log Central > Collect Install Logs.

    Install Failed Logs/Details

     These additional details/logs are required for analysis if the new Installation or rebuild is failed.

    • Is it rebuild for the existing server or new node Install to the cluster?
    • You can provide error details which you received during the installation?

    Refer to this document and share the dumped Install failure logs.


    UC Virtual Installations: Dump the Install Logs to a Serial Port
    https://www.cisco.com/c/en/us/support/docs/unified-communications/unity-connection/116577-technote-UC-00.html

    Related Information

    1. CUCM Hardware Configuration Compatibility Matrix
      https://www.cisco.com/c/dam/en/us/td/docs/voice_ip_comm/uc_system/virtualization/virtualization-cisco-unified-communications-manager.html#v9.0
    2. How to free up common partition space by adjusting log partition watermark in RTMT - CUCM 
      https://www.cisco.com/c/en/us/support/docs/unified-communications/unified-communications-manager-callmanager/200581-Procedure-to-Adjust-WaterMark-in-RTMT-of.html
    3. How to Collect Traces for CUCM   https://www.cisco.com/c/en/us/support/docs/unified-communications/unified-communications-manager-callmanager/200787-How-to-Collect-Traces-for-CUCM-9-x-10-x.html
    TAC Authored

    Contributed by Cisco Engineers

    • Sinto P T
      Cisco TAC Engineer

    Was this Document Helpful?

    FeedbackFeedback

    Contact Cisco

    This Document Applies to These Products