Symptom: When performing an L2 upgrade to CUCM 9.1(1) from an earlier version of CUCM, the upgrade is stalled with the following message: "insufficient disk space.please use RTMT to clean up common partitions.." If the same symptom is observed during an upgrade to 10.0.1, Please refer the "Pre Upgrade Tasks" section in the Upgrade/Install guide.Conditions: L2 upgrade when the amount of disk space (in absolute terms and not in terms of percentage) is not enough with 9.1 CUCM starts taking in to account the disk space required for TFTP data ie., 9.1 upgrade needs more space than previous L2 upgrades.Workaround: When upgrading Cisco Unified Communications Manager to 9.1(1) version, the upgrade may fail due to insufficient disk space. You will see the following error message: There is not enough disk space in the common partition to perform the upgrade. For steps to resolve this condition please refer to the Cisco Unified Communications Manager 9.1(1) Release Notes or view defect CSCuc63312 in Bug Toolkit on cisco.com.To reduce disk space utilization during an upgrade, follow this procedure. Step 1 Reduce the amount of traces on the system by lowering the low and high watermarks in the Cisco Log Partition Monitoring Tool. The low watermark is adjusted by changing the properties of the LogPartitionLowWaterMarkExceeded alert. The high watermark is adjusted by changing the properties of the LogPartitionHighWaterMarkExceeded alert. For more information about the Cisco Log Partition Monitoring Tool, see the Cisco Unified Real-Time Monitoring Tool Administration Guide.Note: Following the upgrade, you must restore the high and low watermarks to their original values in order to avoid premature purging of traces. The default value for the high watermark is 85. The default value for the low watermark is 80.Step 2 If you still get the error message, install the COP file named ciscocm.free_common_space_v1.0.cop.sgn that you can find on Cisco Connection Online under Cisco Unified Communications Manager Version 9.1 > Unified Communications Manager/ CallManager/Cisco Unity Connection Utilities > COP- Files. This COP file frees disk space to allow the upgrade to proceed.Note: You must perform an upgrade after applying the COP file.Caution: You will not be able to switch to the previous version after the COP file is installed. For example, if you are upgrading from Cisco Unified Communications Manager 9.0(1) to Cisco Unified Communications Manager 9.1(1) and the previous version is Cisco Unified Communications Manager 8.6, the COP file clears the space by removing the 8.6 version data that resides in the common partition. So after you apply the COP file, you will not be able to switch to the 8.6 version.Attention: If you are unable to perform the upgrade and continue to receive the error message even after applying this COP file, it means that the amount of data present on the running version does not leave adequate space for expanding and executing the upgrade. In such a case, more space may be recovered by removing unused device firmware from the TFTP path. In some cases having sufficient space for an upgrade will require that you take a backup, reinstall to a larger capacity disk or larger sized Open Virtual Appliance (OVA), and restore. Contact Cisco Technical Assistance Center (TAC) if further assistance is required.
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.