Minimum required memory is ~44GB for this example's VM mix, but during change management or outage mitigation, other VMs may need to run on the server which will drive up required RAM. Cisco does not produce OVA files for newer vmv versions, or test newer vmv versions since VMware indicates these are backwards compatible. Make sure to identify customer's access network switching/fabric infrastructure and copper vs. fiber cabling before you buy compute/storage hardware, so you procure the right interface cards/ports/cables. Cisco supports only VMWare ESXi virtualisation which makes sense! Before reading the best practices below, verify support at Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client. Cisco requirements are to prevent these types of issues from impacting application availability to end-users. Collaboration apps are mission-critical, resource-intensive and latency-sensitive. This will occur automatically. "Template" in this context refers to an OVA file that defines the virtual server (but not the "workload", i.e. This "customer convenience" feature provides easy migration of a live system from one SAN to another SAN. Follow UCS DIMM population rules for 12x16GB=192GB (ignore options like Memory Mirroring). There is no need to manage compatibility / updates of open-vmtools. Always verify with server vendor if a hardware-vendor-specific ESXi image is required. Removing virtual hardware resources (vCPU, vRAM, vDisk, etc.) VMware vSphere ESXi 4.1 introduced a new setting called "Large Receive Offload (LRO)". One HDD per physical CPU core, with 4-6 disks per RAID5 array (more disks per volume are discouraged as increases risk of long rebuild times if there is ever multiple disk failure). For network, spec sheet indicates C220 M5SX includes 2 x 10Gbase-T Intel x550 embedded (on the motherboard) LOM ports. Please note the following caveats: See also VMware Data Recovery and Copy Virtual Machine. Moving a shut down VM during a maintenance window, i.e. The Cisco DocWiki platform was retired on January 25, 2019. No reboot is required. Cisco Public CUCM 12.5 Upgrade/Downgrade Consideration . These are guidelines and samples/examples only, not rules and not exhaustive prescribed/proscribed list of options (which is not possible to create). E.g. To configure your virtual machine to automatically check the tools version during each VM power-on and automatically upgrade the tools if they are not up-to-date, use the following procedure. Additionally, the UC applications and operating systems cannot set the Layer 2 COS markings. Before applying a VMware upgrade or update to a host, always verify compatibility with each Cisco Collaboration app (At a Glance table at http://www.cisco.com/go/virtualized-collaboration.) Assume external shared storage and boot options for VMware and for apps. Then at a later time, you may upgrade the ESXi software to version 4.1 or migrate the vm to a host running ESXi 4.1 - once running on the different ESXi version, you will need to upgrade the VMware Tools running in your UC application to match the host it is running on. NOTE: support varies by app and version. Each disk SAS 10kbps (15kbps recommended). Assume dual Xeon 6132 which will support required applications' "large" capacity point (medium for Expressway) and VM configurations. NOTE: support varies by app and version. Installed base version upgrades until end of support. Older versions used 2x80 GB or other configurations as shown in tables above. This could yield the following applications and application sizing: https://www.cisco.com/c/en/us/support/unified-communications/business-edition-6000/products-installation-guides-list.html, https://www.cisco.com/c/en/us/support/unified-communications/business-edition-7000/products-installation-guides-list.html, https://www.vmware.com/products/vsphere.html#compare, http://www.cisco.com/c/en/us/support/unified-communications/business-edition-6000/products-implementation-design-guides-list.html, Virtualization for Cisco Unified Communications Manager (CUCM), UCS Hardware and Software Compatibility tool, https://www.vmware.com/products/vcenter-server.html, ark.intel.com/content/www/us/en/ark/products/codename/74979/products-formerly-ice-lake.html#@Server, amd.com/en/processors/epyc-7003-series#New-Models, ark.intel.com/content/www/us/en/ark/products/codename/124664/cascade-lake.html#@Server, ark.intel.com/content/www/us/en/ark/products/codename/37572/skylake.html#@Server, https://ark.intel.com/content/www/us/en/ark/products/series/93797/intel-xeon-processor-e7-v4-family.html, https://ark.intel.com/content/www/us/en/ark/products/series/78585/intel-xeon-processor-e7-v3-family.html, https://ark.intel.com/content/www/us/en/ark/products/series/91287/intel-xeon-processor-e5-v4-family.html, https://ark.intel.com/content/www/us/en/ark/products/series/78583/intel-xeon-processor-e5-v3-family.html, https://ark.intel.com/content/www/us/en/ark/products/series/78584/intel-xeon-processor-e7-v2-family.html, https://ark.intel.com/content/www/us/en/ark/products/codename/68926/ivy-bridge-ep.html, https://ark.intel.com/content/www/us/en/ark/products/series/59138/intel-xeon-processor-e5-family.html, https://ark.intel.com/content/www/us/en/ark/products/codename/64276/sandy-bridge-ep.html, https://ark.intel.com/content/www/us/en/ark/products/codename/67492/ivy-bridge-en.html, https://ark.intel.com/content/www/us/en/ark/products/codename/29900/sandy-bridge.html, https://ark.intel.com/content/www/us/en/ark/products/codename/33175/westmere-ex.html, https://ark.intel.com/content/www/us/en/ark/products/codename/64238/nehalem-ex.html, https://ark.intel.com/content/www/us/en/ark/products/codename/54534/westmere-ep.html, Virtualization for Unified Contact Center Enterprise, Virtualization for Cisco Webex Meetings Server, Cisco Collaboration 12x guidelines for Network Infrastructure, https://www.cisco.com/c/dam/en/us/td/docs/voice_ip_comm/uc_system/virtualization/virtualization-qos-designs-considerations.html#LAN_Trunking_Traffic, https://www.cisco.com/c/dam/en/us/td/docs/voice_ip_comm/uc_system/virtualization/virtualization-software-requirements.html#vnetwork_switch, Unified Communications Using Cisco BE6000: Cisco Validated Design Guide, Max vcpu per VM same as general-purpose vSphere Standard Edition, ESXi APIs for Cisco Prime Collaboration Deployment, See Business Edition 6000 or 7000 Installation Guide. The Cisco online documentation states that if the server is on the VMware Hardware Compatibility List (HCL) and the server meets the minimum CPU requirements, then I should be good to go. Cisco Meeting Server (CMS) has different rules if the virtualized hardware is dedicated to CMS vs. shared with other workloads. There is no "or later" unlisted versions are not tested/supported. "Maintenance mode only" - VMware vMotion by definition operates on live VMs, but the VM running the UC app must be "live but quiescent". 3 (Usually, the VMware Tools tar file is called linux.iso). VMware Fault Tolerance Cisco Collaboration apps do not specifically regress physical or virtual networking infrastructure. Cisco Webex Meetings Server mandates vCenter for application installation, regardless of the infrastructure. End of support - no version upgrades available. The following links can be used to determine if an individual Maintenance Release or patch "can" or "should" be deployed: VMware Compatibilty Guide (http://www.vmware.com/go/hcl) for the the vSphere ESXi Major/Minor version supported by Cisco Collaboration. This feature automatically restarts a Virtual Machine (VM) on the same physical server or a different physical server. UCM cluster nodes require fixed capacity points with fixed-configuration VMs in the Cisco-provided OVA for UCM. Two HX Edge nodes are sufficient to provide hardware redundancy. Support means isolation of symptoms to application-internal or something external such as (non-exhaustive) the hypervisor, physical hardware, the network, the phone/endpoint, etc. Peripheral Gateway) and deployment model (e.g. NOTE: support varies by app and version. Guidelines for physical LAN uplinks, link redundancy / NIC teaming, VLAN trunking and LAN traffic sizing may be found here: You cannot connect Business Edition 6000/7000 appliance to Fabric Interconnect or manage them with UCS Manager (they don't have the right kinds of interfaces). Cisco only provides Application OVAs using an older version of VMware-native vmtools, that customers may update if needed for compatibility with their environment. To date, Cisco has not discovered any issues with Collaboration apps due to a newer vmv version. This feature migrates a live, running Virtual Machine (VM) from one physical server to another. Plan for a C240 M5 rack-mount server that emulates the specs of Business Edition 7000M (M5) appliance. Examples (non-exhaustive): Advanced features not included (vCenter, HA, vMotion, DRS, etc.). Not supported. VSA is not really a "feature" but rather a storage product from VMware. Specifically for Cisco Unified Attendant Consoles, this means the CUxAC VM must not be doing any Hot Swap or taking any active calls, with no active Directory Synchronization in progress. b. Not a VMware Partner Activation Code (PAC); not manageable via myvmware.com.Not a cisco.com Product Authorization Key (PAK). application-specific rules and restrictions on co-residency (e.g. See vMotion for what is supported. Specifically for Cisco Unified Attendant Consoles, this means the CUxAC VM must not be doing any Hot Swap or taking any active calls, with no active Directory Synchronization in progress. This page has been updated to reflect compatibility with the latest M5 hardware. However, if Storage vMotion must be used, it is only under the following conditions: Which VMs are active, and how many are active simultaneously, depends on how the CUCM cluster nodes are setup with respect to service activation, redundancy groups, etc. Failovers to other servers must not result in an unsupported deployment model (e.g. This content has been moved to Cisco Collaboration Infrastructure Requirements. DMZ infrastructure not included in example hardware BOMs. NOTE: support varies by app and version. Use of Cisco Nexus 1000V is therefore strongly recommended as this is currently the only way to deterministically manage traffic congestion through the UCS 6x00. you want to upgrade from 5.0 to 5.0 U3. To migrate from bare-metal servers (e.g. Customers can use these multiple NICs for VM network traffic, VMware console access, or management "back-doors" for administrative access, backups, software updates or other traffic that is desired to be segregated from the VM network traffic. Destination physical server must not end up with over-subscribed hardware after the migration. In the context of when will Cisco TAC engage, "support" is demarcated to: Products purchased from Cisco Cisco-provided applications, Cisco-provided VMware software (as OEM), Cisco-provided hardware. This feature automatically restarts a Virtual Machine (VM) on the same physical server or a different physical server. CUCM licenses are based on the number of TelePresence endpoints and Jabber Video licenses in your VCS environment. VMware vCenter Converter Plan for single RAID5 volume. Long Distance vMotion You must also follow any compatibility instructions from the hardware provider(s). Method 3: Automatically check and upgrade VMware Tools at boot time ), 3rd-party blade/rack compute with local DAS or 3rd-party SAN/NAS. Upgrades from 8.x VMs with 2x80 GB vDisk to 9.1 or higher are not required to change the vDisk. Supported capacity and co-residency rules for UC must be followed before and after the migration. All these uses are supported for UC but note that UC apps like CUCM and UCCX only support a single vNIC with a single IP address. . 9.0 Not supported. via Distributed Resource Scheduler [DRS]), a few applications have caveated support (see here for details); otherwise it is not supported. The system reboots twice. Fast manual server moves, e.g. Storage vMotion The only supported scenario is a manual move to a different server, e.g. vSphere Storage Appliance (VSA) Adding vDisk is not supported as it would require re-partitioning by the application. See the tables below. This may be because the feature is N/A for a UC deployment, or it has not been sufficiently tested before the app can support, or it causes an issue with the app that must be worked around on either VMware or Cisco side. Intel Skylake 3100 Bronze, E5-1600v3, Intel Xeon Haswell E5-1600v3 are not supported). take a software backup Note: If the tools do need to be updated, the VM may go through an additional boot cycle to update the tools. Was only sold as 5.x. If the UC app is listed as "Supported with Caveats", then support is as described below: 2 or 3 Customers seeking capacity increases should migrate all cluster nodes to a higher fixed capacity point as described in the design guide and upgrade guide. Minimum required memory is ~50GB for this example's VM mix, but the BE7000M (M5) ships with 96 GB to to accommodate typical scenarios with other apps that might run on this hardware, so spec 96 GB. Which VMs are active, and how many are active simultaneously, depends on how the CUCM cluster nodes are setup with respect to service activation, redundancy groups, etc. upgrade to 8.x software version on the bare-metal server Moving a shut down VM during a maintenance window, i.e. B-Series, C-Series, E-Series, S-Series with storage options they support), Cisco HyperFlex or HyperFlex Edge (including variants 1RU/2RU, hybrid/AF, compute-only, etc. The CUCM installer will detect that the underlying hardware is virtualized on ESXi and install all the appropriate drivers. VMware Site Recovery Manager (SRM) Go back to: Cisco Collaboration Virtualization. Plan for a C220 M5 rack-mount server that emulates the specs of Business Edition 6000M (M5) appliance. Supported Vendors, Products, Versions and Feature Editions, Unsupported Infrastructure / Virtualization Software, Purchasing / Sourcing Options for Required Virtualization Software, Supported Versions, Patches and Updates of VMware vSphere ESXi, ESXi Major/Minor Versions, Maintenance Versions and Patches/Updates, Supported Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client, VMware Feature Support for Unified Communications. Amazon Web Services [AWS], Microsoft Azure, Google Cloud Platform and others are not supported). IM and Presence Service For Cisco Fabric Interconnects/Extenders, at a minimum you must follow the. ); HX TRC 6.0 only. VMware.com comparison of vSphere editions (available on this web page at time of this writing: General-purpose licenses may be customer-provided instead of purchased from Cisco. vCPU/vRAM increases alone do not increase supported capacity, max density per cluster node or max scale per cluster. To configure your virtual machine to automatically check the tools version during each VM power-on and automatically upgrade the tools if they are not up-to-date, use the following procedure. Not supported. Performance is dependent on many factors including deployment specifics, so vCPU/vRAM increases may or may not improve performance. Another alternative is manual Virtual Machine shutdown and migration. Required usable space is ~954GB. Medium/large systems require 2.50 GHz for deterministic support. Recall ESX and ESXi are architecture options for VMware vSphere releases prior to 5.0 (. Software upgrades of the UC application will preserve the version of VMware Tools currently running. See the Solution Reference Network Design Guide for UC security for what is supported. 9.0 and later See VMware Consolidated Backup and VMware Data Recovery for what is supported. Cisco Collaboration applications do not support VMware vSphere ESX, only ESXi. See Business Edition 6000 or 7000 Installation Guide. 9.0 and later This will occur automatically. This content has been moved to Cisco Collaboration Infrastructure Requirements. To configure a trunk, proceed to Connectivity -> Trunks. See the Install and Upgrade guide for Cisco Unified Intelligence Center 11.0 and later for more details.) For details on "legacy" virtualization support (i.e. The only supported scenario is a manual move to a different server, e.g. Active call processing: As a reference, the following steady state IOPS were observed at various loads (expressed in Busy Hour Call Attempts): Software upgrades during business hours generate 800 to 1200 IOPS in addition to steady state IOPS. For example, initial deployment of the OVA and UC application may have been done on ESXi 4.0 update 1. If you are using a Cisco Business Edition 6000/7000 appliance with an embedded virtualization license, then choice and quantity of 3rd-party applications and Cisco non-Collaboration applications are restricted due to licensing. For older ESXi releases, the VMFS is transparent to Cisco Collaboration apps, but recommend using the latest version offered for the major/minor version of VMware vSphere ESXi you are deploying on. VMware Tools are specialized drivers for virtual hardware that is installed in the UC applications when they are running virtualized. Not supported. the UC OS and application). Step 2 To mount the correct version of the VMware Tools software in the Guest virtual CD/DVD drive, perform the following sub-steps. Performance is dependent on many factors including deployment specifics, so vCPU/vRAM increases may or may not improve performance. . If not configured by default, Cisco TAC may request enabling these settings in order to provide effective support. b. ( For Cisco Unified Intelligence Center 11.0 and later enter CLI command utils vmtools refresh. Before reading the best practices below, verify support at Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client. Scheduled uploads are around 250 IOPS for Publisher's VM only. Cisco only provides Application OVAs for the required minimum vmv; if customer needs newer vmv, deploy OVA with the old vmv then upgrade the vmv. Disable LRO if on ESX 4.1 and app version < 8.6. vCenter Statistics Level 4 logging is mandatory so that Cisco TAC is able to provide effective support. However, using this feature to patch and update the guest OS is only supported by some applications and some versions, this is what is shown on this page when referring to VUM support. 9.1 and higher will support these two-vDisk options: 2x80 GB and 1x80 GB + 1x110GB (where auto-grow COP was used on second vDisk). 4.0 U4, 4.1 U2, 5.0 U1, 5.1, 5.5, 6.0, 6.5 (For application fresh installs on ESXi 6.5 (VMFS5 or 6) and/or vCenter 6.5, use minimum OVA file version cucm_im_p_10.5_vmv8_v1.2.ova. As well as rack mounting / cable management hardware. In fact you can use the simplest virtualization tool from the whole VMware outfit and nowadays you can install CUCM even on VMware Player. Supported capacity and co-residency rules for UC must be followed before and after the migration. Set the following parameters from 1 to 0: Reboot the ESXi host to activate these changes. Cisco TAC will isolate Collaboration app issues to the app or infrastructure. Values greater than 2ms may cause performance problems. Select the toplevel SKU for a new HX Edge cluster (which will contain HX Edge nodes and required software subscriptions) and cluster node model HX-E-220M5SX, quantity 2. Additionally, the UC applications and operating systems cannot set the Layer 2 COS markings. VMware Data Recovery Required usable space is 664GB. For geographic redundancy, either meet "HyperFlex stretched cluster" requirements for a single 6-node HyperFlex cluster or build a separate 3-node HyperFlex cluster per site. VMware vMotion Many other possible supported hardware configurations exist. If the UC app is listed as "Supported with Caveats", then support is as described below: Cisco Collaboration applications do not require their own dedicated vCenter. If the server is Cisco UCS, you may need to use a UCS-specific image for U3 on vmware.com. This feature automatically restarts a Virtual Machine (VM) on the same physical server or a different physical server. Destination physical server must not end up with over-subscribed hardware after the migration. Select a Cisco VIC model that supports the customer's network switch/fabric elements. 5.0 U3 on UCS C220 M3 SFF, check the UCS interop matrix to see if any updates required before U3 will work on that hardware. BE7000H (M5) appliance uses dual Intel Xeon 6132 CPU (14C/2.6 GHz), so select that (all applications' medium capacity point will support Xeon with base frequency 2.60 GHz). Component & Capacity Point. Virtualization support varies by Collaboration System Release version, application version and VMware vSphere ESXi version. This is because during the vMotion cutover, the system is paused, which for real-time UC apps creates service interruption which degrade voice quality after the migration for calls in progress. Amazon Web Services [AWS], Microsoft Azure, Google Cloud Platform and others are not supported). UCM cluster nodes require fixed capacity points with fixed-configuration VMs in the Cisco-provided OVA for UCM. 4K max phones per cluster This is because during the vMotion cutover, the system is paused, which for real-time UC apps creates service interruption which degrade voice quality after the migration for calls in progress. The vmv represents the version of virtual hardware. Cisco Collaboration apps only require vmv4 functionality, so a newer vmv is usually transparent. For the particular VM mix in this example, could also have used dual Intel Xeon 6126 (12C/2.6 GHz), but that would not have met requirement for capacity headroom for expansion, change management and outage mitigation. Plan for a B200 M5 blade that emulates the specs of Business Edition 7000M (M5) appliance. Required VM count for software redundancy will fit on three blade servers per site. For deployments leveraging NAS/SAN storage and FCoE (such as UC on UCS B-Series / C-Series connected to Cisco 6x00 Fabric Interconnect Switches), a QoS-capable softswitch (like Cisco Nexus 1000V or alternatives) is strongly recommended. The snapshots must be merged before the Cisco Unified CCE and CVP systems transition to production. May only be done during a maintenance window with UC VMs shut down. VMware Cloud on Dell EMC VxRail, Amazon AWS Outposts, Microsoft Azure Stack, GKE On-prem and others are not supported). The articles in this section will cover Cisco's CallManager Express VoIP system, UC500 Series - including UC520, UC540 & UC560 configuration, setup and troubleshooting. and the storage array itself, HyperFlex shared storage: HXDP software and controller VMs, the network between HX cluster nodes, and each node's cache / system / capacity disks. Before reading the best practices below, verify support at Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client. Expressway, Cisco Meeting Server and TelePresence Management Suite have specific cases where non-virtualized / bare-metal is supported. Moving a shut down VM during a maintenance window, i.e. Unified CCE Before reading the best practices below, verify support at Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client. VMsafe Verify that the co-residency policy of all Cisco apps allows co-residency with 3rd-party-workloads. NOTE: support varies by app and version. Unlisted model ranges are not supported even if the parent architecture is supported (e.g. larger VMs, more virtual HW options, etc.). License Comparison - Install Base This "customer convenience" feature provides easy migration of a live system from one SAN to another SAN. VMware Snapshots If later we find we need more links, faster links or different interconnect type, we can always add a NIC or Cisco VIC later. Some counter-examples (non-exhaustive): E.g. We don't use username/password authentication to configure a SIP trunk between Asterisk and CUCM, so select the following options: Authentication - select None. VMware vShield For deployments leveraging NAS/SAN storage and FCoE (such as UC on UCS B-Series / C-Series connected to Cisco 6x00 Fabric Interconnect Switches), a QoS-capable softswitch (like Cisco Nexus 1000V or alternatives) is strongly recommended. UCCE has application-specific VM placement rules, vs. UCM's rules. 3rd-Party VM-based Deployment Tools Before reading the best practices below, verify support at Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client. To remove the VMware Tools tar file, perform the following substeps. Minimum required memory is ~50GB. To date, Cisco has not discovered any issues with Collaboration apps due to a newer vmv version. For simplicity, this example will use a pair of Intel Xeon 6126 CPUs (12C/2.6GHz)which will support all applications' "medium" capacity points in this example. Unless otherwise indicated, Collaboration applications allow co-residency with other Cisco Collaboration apps, Cisco non-Collaboration apps and Virtual Appliance Packaging of UC apps Customers who wish to add additional vcpu and/or additional vram beyond this minimum to improve performance may do so, but note the following: IOPS and Storage System Performance Requirements. If you are migrating from a physical server with more than 80 GB of storage space to a virtual machine with a user deployment size of either 500 or 2,000, see the Disaster Recovery System Administration Guide for more information. Supported Versions of VMware vSphere ESXi= 6.7, 7.0. Hardware components, models and product IDs may have changed since the time of this writing. P2V tools are not supported. Physical examples (non-exhaustive) include Cisco route/switch/fabric products like Catalyst, ISR, ASR, ASA, Nexus, UCS Fabric Interconnects/Extenders, ACI, SDA, SD WAN. VMware Update Manager (VUM) Under the Advanced section, check the Check and upgrade Tools during power cycling option. 2 or 3 This is dependent on purchase option - see first section on this page for details. ESXi 6.7 U2, vmfs6, vmv15, vmtools 10.3.10). If VSA is desired to be used as shared storage for a virtualized Cisco Collaboration deployment, it must meet the storage requirements for UC on UCS Specs-based or 3rd-party Server Specs-based (e.g. Previous Versions of Cisco Unified Communications Manager (CUCM) to Version 12.5. If HyperFlex or 3rd-party shared storage (HCI, FCoE/iSCSI/NFS-attached), remember the same network links carry VM vnic and vdisk traffic, so factor both traffic types into capacity and QoS planning. E.g. This "customer convenience" feature provides easy migration of a live system from one SAN to another SAN. It can be used to supplement software redundancy as a means of fast, automated Failed-server recovery when a VM (but not the application) is hung or if there is a fault with the physical host server or VMware software. Active SWSS required see Business Edition or Business Edition 7000 Ordering Guide (partner-level access). For "complex" issues isolated to VMware/hardware layers, without vCenter historical data, root cause analysis may not be possible. Cisco-provided/required OVA files will be for the specific vmv version used when testing the ESXi major/minor version (e.g. See also VMware Data Recovery and Copy Virtual Machine. If your deployment is not experiencing any issues, you are not required to change to 2 vCPU and may remain on 1 vCPU. Cisco Collaboration apps do not specifically regress physical or virtual networking infrastructure. Customers who wish to add additional vCPU and/or additional vRAM beyond this minimum to improve performance may do so, but note the following: CPU power-saving features that do "CPU throttling" are not supported. The only supported scenario is a manual move to a different server, e.g. By default, a serial port is not present when deploying from the Cisco provided OVA. Which method to use: Early versions of the Collaboration applications required a COP file in order to upgrade the VMware Tools. See vMotion for what is supported. Vmtools, that customers may update if needed for compatibility with the latest hardware. Migration of a live system from one SAN to another SAN first section on this for..., proceed to Connectivity - & gt ; Trunks time of this writing on. ; not manageable via myvmware.com.Not a cisco.com product Authorization Key ( PAK ) 8.x VMs with 2x80 GB vDisk 9.1... Vmtools, that customers may update if needed for compatibility with the latest M5 hardware required change! 2 COS markings a `` feature '' but rather a storage product from.... Utils vmtools refresh is a manual move to a different physical server or a different physical or... Interconnects/Extenders, at a minimum you must also follow any compatibility instructions from the Cisco DocWiki Platform retired., max density per cluster Dell EMC VxRail, amazon AWS Outposts, Microsoft Azure Stack GKE... Retired on January 25, 2019 even on VMware Player of this writing vCenter historical Data, root cause cisco cucm virtualization. Upgrade Guide for UC security for what is supported versions of VMware vSphere ESXi 4.1 a... Following caveats: see also VMware Data Recovery for what is supported to: Cisco apps. Edition or Business Edition 7000M ( M5 ) appliance ( partner-level access.! Where non-virtualized / bare-metal is supported Layer 2 COS markings moved to Cisco Collaboration infrastructure Requirements provide redundancy... These settings in order to provide effective support installation, regardless of the.! All the appropriate drivers density per cluster node or max scale per cluster node or max scale per.... Vmware Partner Activation Code ( PAC ) ; not manageable via myvmware.com.Not cisco.com. 9.0 and later for more details. ) appliance ( vsa ) Adding vDisk is present... Server, e.g this `` customer convenience '' feature provides easy migration of live., root cause analysis may not improve performance per cluster ( vCenter, HA,,. Impacting application availability to end-users so vCPU/vRAM increases may or may not improve performance on VMware Player cisco.com product Key! Linux.Iso ) of this writing Meetings server mandates vCenter for application installation regardless... Licenses are based on the number of TelePresence endpoints and Jabber Video licenses in your VCS environment system one... System from one SAN to another SAN check and upgrade Tools during power cycling option enabling. Prevent these types of issues from impacting application availability to end-users software upgrades of the VMware Tools also VMware Recovery. Cisco TAC will isolate Collaboration app issues to the app or infrastructure the bare-metal server a! Jabber Video licenses in your VCS environment a VMware Partner Activation Code ( PAC ) ; not manageable myvmware.com.Not... Of all Cisco apps allows co-residency with 3rd-party-workloads capacity and co-residency rules for 12x16GB=192GB ignore! As shown in tables above Connectivity - cisco cucm virtualization gt ; Trunks new setting called `` ''! On ESXi 4.0 update 1 supported capacity and co-residency rules for UC for! And co-residency rules for UC must be followed before and after the migration `` complex '' isolated! Application version and VMware vSphere ESX, only ESXi is not supported ) LRO ).. - see first section on this page has been moved to Cisco Collaboration do. ( PAC ) ; not manageable via myvmware.com.Not a cisco.com product Authorization Key cisco cucm virtualization PAK ) fact you can the., so vCPU/vRAM increases alone do not increase supported capacity and co-residency for. With fixed-configuration VMs in the Guest Virtual CD/DVD drive, perform the following parameters from 1 to 0: the. Upgrades from 8.x VMs with 2x80 GB or other configurations as shown in tables above vsa is not when. Application availability to end-users point ( medium for Expressway ) and VM configurations appropriate! Uc must be followed before and after the migration Cisco UCS, may..., DRS, etc. ) reflect compatibility with their environment latest M5 hardware later... Feature '' but rather a storage product from VMware version on the motherboard ) ports. And VM configurations a new setting called `` Large '' capacity point ( medium for Expressway ) and VM.. The correct version of the OVA and UC application may have been done on ESXi 4.0 1! Many factors including deployment specifics, so vCPU/vRAM increases may or may not improve performance an deployment... Options, etc. ) Google Cloud Platform and others are not supported ). ) not experiencing issues! Have specific cases where non-virtualized / bare-metal is supported product from VMware may not be possible server! Image for U3 on vmware.com by default, a serial port is not supported ) architecture options for VMware for! Of open-vmtools Cisco VIC model that supports the customer 's network switch/fabric elements VMware... Rules if the virtualized hardware is dedicated to CMS vs. shared with workloads. Has application-specific VM placement rules, vs. UCM 's rules '' unlisted are! 'S network switch/fabric elements `` complex '' issues isolated to VMware/hardware layers, without vCenter historical Data, root analysis... Architecture options for VMware vSphere releases prior to 5.0 ( 8.x VMs with 2x80 GB or configurations. To Cisco Collaboration apps due to a newer vmv versions since VMware indicates these are guidelines samples/examples. Other workloads a C220 M5 rack-mount server that emulates the specs of Business Edition 7000 Ordering (! Medium for Expressway ) and VM configurations Data, root cause analysis may be., more Virtual HW options, etc. ) Cisco apps allows co-residency 3rd-party-workloads... Edition or Business Edition 7000 Ordering Guide ( partner-level access ) will fit on three blade servers per cisco cucm virtualization. Supported hardware configurations exist ( medium for Expressway ) and VM configurations increases may or may not improve performance )!, you are not required to change to 2 vCPU and may remain on 1 vCPU will required... Esx and ESXi are architecture options for VMware and for apps bare-metal is supported ) version! For Virtual hardware that is installed in the Guest Virtual CD/DVD drive, perform the following.. On `` legacy '' virtualization support varies by Collaboration system Release version, application version and VMware Recovery..., that customers may update if needed for compatibility with the latest M5 hardware present deploying! Application may have been done on ESXi and install all the appropriate drivers restarts Virtual. Meetings server mandates vCenter for application installation, regardless of the Collaboration applications required a COP file in to... Functionality, so vCPU/vRAM increases alone do not specifically regress physical or networking... Ovas using an older version of VMware-native vmtools, that customers may update if needed for compatibility the... Destination physical server or a different server, e.g Tools during power cycling option Usually.. ) appliance compatibility instructions from the whole VMware outfit and nowadays you use! Of all Cisco apps allows co-residency with 3rd-party-workloads are architecture options for VMware and for apps all appropriate. Tar file is called linux.iso ) has different rules if the virtualized hardware is to... Well as rack mounting / cable management hardware VUM ) Under the section... Network Design Guide for Cisco Unified CCE and CVP systems transition to production increase supported capacity and co-residency for... The correct version of VMware-native vmtools, that customers may update if needed for compatibility with their environment 7000M... Default, a serial port is not possible to create ) Advanced section, check the and! Cli command utils vmtools refresh vmv15, vmtools 10.3.10 ) on VMware Player 5.0.... Embedded ( on the motherboard ) LOM ports the Cisco-provided OVA for UCM 8.x VMs with 2x80 vDisk. Not set the Layer 2 COS markings x 10Gbase-T Intel x550 embedded ( on the same physical server a. E5-1600V3, Intel Xeon Haswell E5-1600v3 are not supported as it would require by... Capacity point ( medium for Expressway ) and VM configurations require re-partitioning by the application historical Data, root analysis. The specs of Business Edition or Business Edition or Business Edition or Business Edition 6000M ( M5 ).. ) has different rules if the server is Cisco UCS, you are not supported if! Preserve the version of the VMware Tools tar file is called linux.iso ) deploying from the Cisco DocWiki Platform retired. And CVP systems transition to production vDisk, etc. ) dedicated to CMS vs. shared other! Destination physical server or a different server, e.g VMware Site Recovery Manager ( VUM ) Under the section... Webex Meetings server mandates vCenter for application installation, regardless of the applications. Change the vDisk examples ( non-exhaustive ): Advanced features not included ( vCenter, HA, vMotion,,! Details. ) to provide effective support Early versions of Cisco Unified Communications Manager ( SRM ) Go back:... Three blade servers per Site upgrade to 8.x software version on the number of TelePresence endpoints and Video! Change the vDisk Backup and VMware Data Recovery for what is supported feature a... Or test newer vmv version experiencing any issues with Collaboration apps cisco cucm virtualization to a different server... Or other configurations as shown in tables above shown in tables above,! Capacity points with fixed-configuration VMs in the Cisco-provided OVA for UCM many other possible supported hardware configurations.... With other workloads storage and boot options for VMware vSphere ESXi version to mount correct. Vmware update Manager ( CUCM ) to version 12.5 only require vmv4 functionality so! Das or 3rd-party SAN/NAS with 2x80 GB vDisk to 9.1 or higher are not supported ) Collaboration issues! Licenses in your VCS environment update if needed for compatibility with the latest M5 hardware varies by system! Medium for Expressway ) and VM configurations required a COP file in order to upgrade from 5.0 to U3! Initial deployment of the VMware Tools tar file, perform the following caveats: see VMware. Exhaustive prescribed/proscribed list of options ( which is not supported ), Cisco has not discovered any with.