Cisco Unified Communications Manager (CallManager) 15 Virtual Server Template (OVA) 1.0 Overview 2.0 Scope 3.0 Deployment Options 4.0 Changes from previous releases 5.0 Instructions 6.0 Trademarks and Notices 1.0 Overview The Cisco Unified Communications Manager (CUCM) 15 Virtual Server Template (OVA) defines a virtual machine configuration that are supported in the CUCM 15 release. This OVA contains all supported virtual machine configurations of this CUCM release. Any fresh install of CUCM 15 must use a virtual machine created from this OVA. 2.0 Scope The CUCM template is an OVA (open virtual archive) file that can be imported/deployed using the OVF (open virtualization format) support of VMware. The OVA file defines the following for the virtual machine based on the deployment selected: - Number of virtual CPUs (vcpu) running on supported Intel Xeon physical CPU - Amount of virtual RAM (vram) - Number and size of virtual disk drives (vdisk) - All virtual machine configurations support only a single virtual NIC (vNIC). - ESXi version support: ESXi 7.0 and 8.0 (with VM version 17) are minimum required. See also the UCM 15 page at https://www.cisco.com/c/dam/en/us/td/docs/voice_ip_comm/uc_system/virtualization/cisco-collaboration-virtualization.html - OS support: Other 4.x or later Linux (64-bit) 3.0 Deployment Options Work with your channel partner or Cisco account team to run Collaboration Sizing Tool with desired vcpu count per VM and desired physical CPU base frequency to see what your virtual machine requirements must be for your design. For typical best practices designs that will align with assumptions of Cisco Preferred Architectures (PA) / Cisco Validated Designs (CVD) for Collaboration, the recommended starting points below may be used at install-time. Small: Cisco Unified Communications Manager (CUCM) configuration for single cluster of max 1000 users and max 1200 devices (BE6000M appliance hardware) or max 2500 devices (BE6000H appliance hardware), based on Unified Communications Using Cisco BE6000: Cisco Validated Design Guide (CVD). Details: CPU: 2 vCPU with 800 MHz reservation Memory: 10 GB with 10 GB reservation Disk: 1 - 110 GB disk with pre-aligned disk partitions A single virtual NIC (vNIC) of type VMXNET3 Medium: Cisco Unified Communications Manager (CUCM) configuration for single cluster of around 5000 phones based on Preferred Architecture for Cisco Collaboration Enterprise On-Premises Deployments, CVD. Details: CPU: 2 vCPU with 3600 MHz reservation Memory: 12 GB with 12 GB reservation Disk: 1 - 110 GB disk with pre-aligned disk partitions A single virtual NIC (vNIC) of type VMXNET3 Large: Cisco Unified Communications Manager (CUCM) single cluster of 10,000 phones or more, based on Preferred Architecture for Cisco Collaboration Enterprise On-Premises Deployments, CVD. Details: CPU: 4 vCPU with 7200 MHz reservation Memory: 14 GB with 14 GB reservation Disk: 1 - 110 GB disk with pre-aligned disk partitions A single virtual NIC (vNIC) of type VMXNET3 5.0 Instructions Instructions to upgrade the virtual hardware version: Below is an example list of steps to accomplish this process. Depending on the specific version of ESXi in your environment and other variables, some of these steps may vary slightly. NOTE: PERFORM ONLY ON VMS RUNNING ON ESXi HOST 7.0 AND ABOVE. NOTE: If these changes are done on VMs running on ESXi host lower than 7.0, the VMs will fail to boot. 1) Navigate to the Summary tab for the VM in question, right-click the Storage volume on which the VM is located, and choose "Browse this datastore". 2) In the "Datastore Browser" window, locate and select the relevant folder for the VM in question. 3) Right-click on the .vmx file and choose "Download...", select a folder on your local machine for the file. 4) Make a backup copy of the .vmx file on your local machine by running the following commands from a Windows Command Prompt in the same folder as the downloaded .vmx file. If your edits break the virtual machine,you can roll back to the original version of the file. copy".vmx"".vmxBACKUP" 5) Modifiy the configuration file-".vmx file": Locate the entry for virtualHW.version. Change the entry to: virtualHW.version = "17" 6) Upload the edited .vmx file to the Datastore by selecting the relevant folder for the VM in question in the "Datastore Browser" window, clicking the button for "Upload files to this datastore", and choosing "Upload File..." 7) Locate the edited .vmx file from your local machine and select it, acknowledging that existing files of the same name will be overwritten Note: Keep the "Datastore Browser" window open, as you will need it again in Step 10 8) Now that .vmx file is updated, note on which ESXi host the VM in question is located. 9) From the main vSphere client window, right-click the VM in question in the list of VMs and choose "Remove from Inventory" 10) Navigate back to the "Datastore Browser" (from the window left open earlier. Otherwise, open the Datastore Browser from another VM's Summary page "Storage" list or the ESXi host 's Summary page "Storage" list) 11) Locate and select the relevant folder for the VM in question 12) Right-click on the .vmx file and choose "Add to Inventory". 13) Step through the "Add to Inventory" wizard, selecting the same host on which you previously noted the VM was located. These steps will ensure that the VM will utilize the update d .vmx file using the virtual hardware version 17. 14) On the newly-readded VM you can verify the change by navigating to the summary tab and noting the VM Version field. 6.0 Trademarks and Notices Copyright 2011-2015, 2017, 2019, 2020, 2023 Cisco Systems, Inc. All Rights Reserved