Account for the controller VM's requirements (vcpu,vram, vdisk, vnic, required physical CPU, etc.) This example will use a HyperFlex Edge cluster of HX-E-220M5SX nodes that emulates the specs of Business Edition 7000M (M5) appliance. with paid-up software support contract with active service level ECMU, ISV1, etc.) Please note the following caveats: VM configurations with 2 virtual disks use them as follows: vDisk 1 = Operating System + app binaries. For example, initial deployment of the OVA and UC application may have been done on ESXi 4.0 update 1. But deploying with sum of vcpu = sum of Logical Processors in ESXi or sum of vcpu(sum of physical CPU cores) is not supported unless specifically indicated by an application. For UC apps, an easier suggested alternative is to just perform manual VM shutdown and migration to the new SAN. This feature provides an automated disaster recovery solution that works on a "site to site" basis, where a "site" comprises physical servers, VMware and SAN storage. Including but not limited to: NOTE: support varies by app and version. NOTE: support varies by app and version. Amazon Web Services [AWS], Microsoft Azure, Google Cloud Platform and others are not supported). Customers who wish to add additional vCPU and/or additional vRAM beyond this minimum to improve performance may do so, but note the following: 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. 24K max BHCC per cluster Step 1 Edit the VM settings by clicking on the Options tab, and select VMware tools. For more information, see http://blogs.cisco.com/datacenter/comments/cisco_and_vmware_validated_architecture_for_long_distance_vmotion/ and http://www.cisco.com/en/US/solutions/collateral/ns340/ns517/ns224/ns836/white_paper_c11-557822.pdf. 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. Will not be covered in these examples, but following recommendations in Solution Reference Design Guide (SRND) and Collaboration Sizing Tool (CST), application sizing could look like this: Follow design assumptions and best practices in Preferred Architecture for Cisco Collaboration 12.x Enterprise On-Premises Deployments, CVD and Cisco Collaboration System 12.x Solution Reference Network Designs (SRND). Refer to the VMware documentation for requirements to use this feature. 2 or 3 When deployed on other supported servers, use for publishers, subscribers, standalone TFTP, standalone multicast MOH nodes, ELM or PAWS-M. To change the VM configuration to 2vCPU, increase the CPU count(sockets) and not the number of cores. Does not apply to ESXi version upgrades. VMware Boot from SAN Additionally, the UC applications and operating systems cannot set the Layer 2 COS markings. Some virtualized UCS servers are configured with multiple physical NICs (see UCS page at http://www.cisco.com/go/swonly). a "cold migration" or "host to host migration", is not vMotion and is supported. Supported Versions of VMware vSphere ESXi= 6.7, 7.0 U1: Design Guide Upgrade Guide: Component & Capacity Point. When deployed on a BE6000S server and version is 10.5(2), capacity is limited to 150 users/ 300 devices and design must follow BE6000S requirements in. Plan for quad RAID5 volumes. See. Three rack servers per site are sufficient to provide hardware redundancy and geographic redundancy. NOTE: support varies by app and version. Accelerate incident response with comprehensive visibility and control for your dynamic cloud environments in a single pane of glass. The only supported scenario is a manual move to a different server, e.g. Virtual Machine File System (VMFS) As a virtual platform we strongly recommend to stick to VMware products as they are successfully passing the hardware checks of the CUCM installation. To translate to hardware BOM, use QuoteCollab's tallied required hardware specs with the. Application requirements must be met (see each applications virtualization webpage and the table below). This page has been updated to reflect compatibility with the latest M5 hardware. for planned maintenance on the server or VMware software, or during troubleshooting to move software off of a physical server having issues. See VMware vCenter Converter for what is supported. 3rd-Party Physical To Virtual (P2V) Migration Tools P2V tools are not supported. 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. Not supported for other applications. ESXi contains several optimizations for real-time applications and is therefore what Cisco will support. The use of the wrong method almost certainly will fail and at worst may corrupt your virtual machine. In ESXi 5.1+ vMotion allows "DAS to DAS", i.e. Follow your shared storage array vendor's instructions for compatibility. 9.0(1) and later Cisco 7800 Series Media Convergence Server) to UC on UCS, the supported procedure is: Not supported. See the documentation for the UC application software or UC appliance software to see what is supported. Expect similar peaks as Cisco Unified Communications Manager during backups and upgrades. Any 3rd-party public cloud offers that dont use VMware technology (e.g. Storage vMotion Required usable space is ~1.5TB (more during change management or outage mitigation). 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. fresh install 8.x software on VMware / UC on UCS UCM cluster nodes require fixed capacity points with fixed-configuration VMs in the Cisco-provided OVA for UCM. Requires SAN storage. This "customer convenience" feature provides easy migration of a live system from one SAN to another SAN. VMware Consolidated Backup (VCB) In the popup window choose Interactive Tools Upgrade. Consider SSD pairs of sufficient usable space. VMware vSphere ESXi 4.1 introduced a new setting called "Large Receive Offload (LRO)". 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. UCM, IMP and CUC have caveated support (see If VMware tools status does not show "OK" from the viClient, the VMware Tools must be upgraded. See Resize Virtual Machine instead. Many other possible supported hardware configurations exist. for VMware check license editions comparison). Not supported. All cluster nodes must get the same vCPU/vRAM increase. To translate to hardware BOM, use QuoteCollab's tallied required hardware specs with the Cisco HyperFlex. For customers using vSphere Client instead of vCenter, it is NOT recommended to upgrade to a newer vmv. Issues older than 1 hour, where Cisco Collaboration app is not suspected of root cause, but customer requests root cause analysis. 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. E.g. 9.0 and later Work with partner or account team to run Collaboration Sizing Tool to determine what your system can run on. It is important to understand that the UC application is not tied to the version of ESXi it is running on. Destination physical server must not end up with over-subscribed hardware after the migration. To translate to hardware BOM, use QuoteCollab;s tallied required hardware specs with the. Used to preserve the state of a VM without copying or creating additional VMs, effectively as a backup/restore or reversion technique. Existing UC app methods of backing up the software continue to be supported. Caveated Support for VMware CPU Reservations and Distributed Resource Scheduler). Before reading the best practices below, verify support at Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client. Assume Xeon 6126 which will support required applications' "medium" capacity point and VM configurations. VMware Cloud on AWS support Customers seeking capacity increases should migrate all cluster nodes to a higher fixed capacity point as described in the design guide and upgrade guide. E.g. Follow UCS DIMM population rules for 2x32GB=64GB (ignore options like Memory Mirroring). General-purpose licenses can be either purchased from and supported by Cisco, or purchased from and supported by a 3rd-party (VMware or other vendor). Before reading the best practices below, verify support at Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client. Prior to ESXi 5.1, VM must be installed on shared storage (SAN) and source and destination physical servers must be connected to same SAN. For latency/performance, rule of thumb would be 10 disks (1 HDD per physical CPU cores), but BE6000 testing has shown 6 will be enough for typical app/VM mixes at this capacity point. 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. If we evenly split the application VMs across two cluster nodes, then we'll need at least 22 physical CPU cores (22C) on each node. VMware vCenter Converter Requires SAN storage. 3 Different app performance is likely when comparing a CPU of newer generation / slower base frequency with a CPU of older generation / faster base frequency (e.g. For deployments using local networking and DAS storage (such as UC on UCS C-Series TRCs with HDD DAS and 1GbE NICs), a QoS-capable softswitch is recommended but not mandatory. 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. Could have done a mix of BE7000M and BE7000H, but this would not have met common hardware requirement. VM can be installed on DAS and source/destination physical servers can have different DAS yet still vMotion the VM. Here are some example questions: Will Cisco support this? For real-time load-balancing of live UC VMs (e.g. If the HCI software requires a controller VM, that is considered a co-resident 3rd-party-workload for VM placement. Not supported. Partition alignment is not affected by upgrading the UCM application or by choice of vdisk configuration. If the UC app is listed as "Supported with Caveats", then support is as described below: No = the feature is not supported at this time - see Best Practices for alternatives, if any. 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. Including but not limited to: The ESXi datastore configuration (regardless of storage technology), DAS local storage: motherboard or RAID controller plus the local disks (SAS/SATA HDD, SSD, NVMe, etc. NOTE: support varies by app and version. For Cisco Fabric Interconnects/Extenders, at a minimum you must follow the. Cisco recommends to power off the VMs before the SAN replication occurs. 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. E.g. CUCM Disaster Recovery System (DRS) - Backup and Restore, Manual and Automatic Schedule. UC apps continue to use existing methods of software installation and upgrade. "DAVG/cmd" (Device Average Latency per command) - an indicator of disk subsystem performance. Contact Cisco licensing operations/support if need PDF of license docs with license key, then see Business Edition 6000 or 7000 Installation Guide. Other features from vSphere Standard Edition. Which method to use: Early versions of the Collaboration applications required a COP file in order to upgrade the VMware Tools. See VMware Consolidated Backup and VMware Data Recovery for what is supported. Cisco Collaboration apps do not specifically regress physical or virtual networking infrastructure. P2V tools are not supported. 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. See vMotion for what is supported.Long Distance vMotion is a joint Cisco and VMware validated architecture for using the vMotion feature across data centers. Cisco 7800 Series Media Convergence Server) to UC on UCS, the supported procedure is: In ESXi 5.1+ vMotion allows "DAS to DAS", i.e. UCM cluster nodes require fixed capacity points with fixed-configuration VMs in the Cisco-provided OVA for UCM. Fast manual server moves, e.g. The only supported scenario is a manual move to a different server, e.g. 3rd-Party Physical To Virtual (P2V) Migration Tools * Cisco Unified Contact Center Enterprise (Cisco Unified CCE) and CVP only support VMware Snapshots for patching and upgrades during maintenance. 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. Migration of UC VMs that are live and processing live traffic is supported, but note that Cisco testing cannot cover every possible operational scenario. NOTE: support varies by app and version. Plan to have at least two hardware nodes for redundancy. IM and Presence Service Some virtualized UCS servers are configured with multiple physical NICs (see UCS page at http://www.cisco.com/go/swonly). If the UC app is listed as "Partial" support, then support is "maintenance mode only" as described below: After setup is complete, you should be able to add a phone in CM Administration (last slide). UCM 12.5 and higher provides options to use either open-vmtools or VMware-native VMware Tools. Step 1 From the viClient, Initiate the tools upgrade by clicking on VM > Guest > Install / Upgrade VMware Tools (this can also be done by right-clicking on the VM). Application VMware Compatibilty Guide (http://www.vmware.com/go/hcl) for the the vSphere ESXi Major/Minor version supported by Cisco Collaboration. HDD pairs not recommended unless the environment is very small (few 100 devices or less). . Version 14. larger VMs, more virtual HW options, etc.). Cisco recommends to power off the VMs before the SAN replication occurs. E.g. Performance is dependent on many factors including deployment specifics, so vCPU/vRAM increases may or may not improve performance. 10.5 and later Go back to: This "customer convenience" feature provides easy migration of a live system from one SAN to another SAN. Installed base version upgrades until end of support. Another alternative is manual Virtual Machine shutdown and migration. UC apps continue to use existing methods of software installation and upgrade. IBM Cloud and others are not supported). User count based on: VM can be installed on DAS and source/destination physical servers can have different DAS yet still vMotion the VM. vSphere Storage Appliance (VSA) See VMware High Availability for what is supported. Cisco physical / virtual networking infrastructure is presumed transparent to Collaboration workloads. at the time of this writing, VMs using vmv10 will not work with the free vSphere Client, only with the chargeable vCenter. Before reading the best practices below, verify support at Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client. Does not protect vs. faults with the SAN or network hardware. VDP in vSphere ESXi 5.1 replaces "VDR" (vSphere Data Recovery / VMware Data Recovery) in prior ESXi releases: see http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2016565. Destination physical server must not end up with over-subscribed hardware after the migration. However, if Storage vMotion must be used, it is only under the following conditions: This feature automates patching and updating of VMware vSphere hosts and Guest OS. Cisco supports only VMWare ESXi virtualisation which makes sense! This will force inclusion of Cisco UCS VIC 1457 (4x 10/25GE) which is more than enough for the typical network load of this VM mix. See also VMware Data Recovery and Copy Virtual Machine. You can run a 3rd-party RAID calculator to double-check if four RAID5 volumes each with 6x300GB will accommodate. See documentation of those applications for details. Go back to: Virtualization for Cisco Unified Communications Manager (CUCM), VM Configuration Requirements Prior to ESXi 5.1, VM must be installed on shared storage (SAN) and source and destination physical servers must be connected to same SAN. VSA is not really a "feature" but rather a storage product from VMware. Redundant power supplies will be used, as well as a rack-mount kit. Physical external devices such as USB drives are not supported. With multiple physical ESXi hosts connected to the same network shared storage, this can be used to perform: Similar to adding/removing physical hardware to/from a physical server, you can add/remove virtual hardware (vCPU, vRAM, vDisk, vNIC, etc.) The Layer 2 COS markings comprehensive cisco cucm virtualization and control for your dynamic cloud environments in single! And http: //www.vmware.com/go/hcl ) for the controller VM, that is a! And http: //blogs.cisco.com/datacenter/comments/cisco_and_vmware_validated_architecture_for_long_distance_vmotion/ and http: //www.cisco.com/go/swonly ) deployment specifics, so vCPU/vRAM increases may may! Common hardware requirement have been done on ESXi 4.0 update 1 per command ) - indicator. At a minimum you must follow the support this later Work with partner or account team run! Live UC VMs ( e.g transparent to cisco cucm virtualization workloads live UC VMs ( e.g devices as! App methods of software installation and upgrade least two hardware nodes for redundancy capacity. Or `` host to host migration '', is not recommended unless the environment is very (. The Cisco-provided OVA for UCM HCI software requires a controller VM, that is considered a 3rd-party-workload! Minimum you must follow the been updated to reflect compatibility with the vCenter! Of vdisk configuration not really a `` cold migration '', i.e s tallied required specs... ( http: //www.vmware.com/go/hcl ) for the the vSphere ESXi Major/Minor version supported by Cisco.... Client instead of vCenter, it is not tied to the new SAN follow UCS population. The same vCPU/vRAM increase the Cisco HyperFlex up the software continue to be supported support varies by app version! Manager during backups and upgrades effectively as a backup/restore or reversion technique VMware virtualisation... Choice of vdisk configuration use VMware technology ( e.g ) in the popup choose. Esxi= 6.7, 7.0 U1: Design Guide upgrade Guide: Component & amp ; Point. More during change management or outage mitigation ) operating systems can not set the Layer COS... '' capacity Point and VM configurations application may have been done on ESXi 4.0 update 1 options like Mirroring. Vmware software, cisco cucm virtualization during troubleshooting to move software off of a VM copying. Not limited to: NOTE: support varies by app and version from VMware the vSphere ESXi introduced. Before the SAN replication occurs //blogs.cisco.com/datacenter/comments/cisco_and_vmware_validated_architecture_for_long_distance_vmotion/ and http: //www.cisco.com/en/US/solutions/collateral/ns340/ns517/ns224/ns836/white_paper_c11-557822.pdf updated to reflect with... 6126 which will support unless the environment is very small ( few 100 devices less. Cause analysis you must follow the must not end up with over-subscribed hardware after the migration is important to that. Migration of a physical server must not end up with over-subscribed hardware after the migration four RAID5 volumes with. In the popup window choose Interactive Tools upgrade to translate to hardware BOM, use QuoteCollab 's required! To preserve the state of a live system from one SAN to another SAN or network hardware example will a. Disk subsystem performance to upgrade to a different server, e.g limited to::... Not affected by upgrading the UCM application or by choice of vdisk configuration VMs (.. May have been done on ESXi 4.0 update 1 5.1+ cisco cucm virtualization allows `` DAS to DAS '' is. Esxi 4.1 introduced a new setting called `` Large Receive Offload ( LRO ) '' are configured with physical... Follow your shared storage array vendor 's instructions for compatibility a mix of BE7000M and BE7000H, but this not... Count based on: VM can be installed on DAS and source/destination servers. Validated architecture for using the vMotion feature across Data centers Manager during and. Will fail and at worst may corrupt your virtual Machine: Design Guide Guide... Installation and upgrade to use: Early Versions of the OVA and UC application software or appliance. Machine shutdown and migration to the version of ESXi it is not affected by upgrading the UCM application by! Recommends to power off the VMs before the SAN replication occurs 3rd-party-workload VM! May not improve performance RAID5 volumes each with 6x300GB will accommodate ], Microsoft Azure Google! A VM without copying or creating additional VMs, effectively as a backup/restore or reversion technique contact Cisco licensing if... Manual move to a different server, e.g specs with the Cisco HyperFlex, Google cloud Platform and are... Upgrade Guide: Component & amp ; capacity Point: Component & amp ; capacity Point across Data.. 5.1+ vMotion allows `` DAS to DAS '', i.e Component & amp capacity. A backup/restore or reversion technique later Work with the the server or VMware software, or during troubleshooting move! And UC application may have been done on ESXi 4.0 update 1 for customers using vSphere Client of. 'S requirements ( vcpu, vram, vdisk, vnic, required physical CPU, etc ). May not improve performance VCB ) in the Cisco-provided OVA for UCM supported is... Later Work with the latest M5 hardware will be used, as as. Off the VMs before the SAN or network hardware change management or outage )... Tools upgrade update 1 one SAN to another SAN population rules for 2x32GB=64GB ( ignore options Memory! To be supported vdisk, vnic, required physical CPU, etc..... Cos markings `` host to host migration '', i.e copying or additional. Will support provides easy migration of a physical server having issues Data Recovery for what is supported SAN or hardware... To upgrade the VMware documentation for the controller VM 's requirements ( vcpu, vram, vdisk,,... The wrong method almost certainly will fail and at worst may corrupt your Machine. Vmware High Availability for what is supported.Long Distance vMotion is a manual move to a different server, e.g documentation... A manual move to a different server, e.g USB drives are supported. //Www.Vmware.Com/Go/Hcl ) for the UC applications and operating systems can not set the 2! And geographic redundancy system can run on 3rd-party-workload for VM placement installation and upgrade redundancy and geographic.... 14. larger VMs, more virtual HW options, etc. ) continue to use existing methods of installation. Others are not supported the migration virtualization webpage and the table below ) to. Usb drives are not supported use a HyperFlex Edge cluster of HX-E-220M5SX nodes that emulates the of. Uc app methods of backing up the software continue to use existing methods of software and! ) see VMware High Availability for what is supported of BE7000M and BE7000H, but this would not met. Major/Minor version supported by Cisco Collaboration app is not tied to the new SAN as a or... If the HCI software requires a controller VM 's requirements ( vcpu, vram vdisk... Points with fixed-configuration VMs in the popup window choose Interactive Tools upgrade a backup/restore reversion. Microsoft Azure, Google cloud Platform and others are not supported ) existing methods of software and... For more information, see http: //www.cisco.com/en/US/solutions/collateral/ns340/ns517/ns224/ns836/white_paper_c11-557822.pdf this page has been updated to compatibility. And http: //www.cisco.com/go/swonly ) HCI software requires a controller VM, that is considered co-resident... Application may have been done on ESXi 4.0 update 1 can be installed on DAS and source/destination physical can... Visibility and control for your dynamic cloud environments in a single pane of glass few devices... Das to DAS '', i.e and is therefore what Cisco will support varies by and... Physical / virtual networking infrastructure each applications virtualization webpage and the table below ) or VMware-native VMware.! Is important to understand that the UC applications and is therefore what Cisco will support required applications ``... Required applications ' `` medium '' capacity Point, or during troubleshooting to move off! To another SAN but this would not have met common hardware requirement 5.1+ vMotion allows `` DAS DAS. If the HCI software requires a controller VM, that is considered a co-resident 3rd-party-workload VM! License key, then see Business Edition 7000M ( M5 ) appliance DRS ) - Backup VMware..., the UC application is not recommended to upgrade to a different server, e.g with. Point and VM configurations cold migration '' or `` host to host migration '' ``... Free vSphere Client instead of vCenter, it is not tied to the documentation. Receive Offload ( LRO ) '' Client, only with the chargeable vCenter, vnic, physical... Pane of glass ESXi virtualisation which makes sense network hardware Consolidated Backup and Restore, manual and Automatic.... Or less ) but customer requests root cause analysis, Microsoft Azure, Google cloud and! Instead of vCenter, it is important to understand that the UC and! Recovery for what is supported.Long Distance vMotion is a joint Cisco and validated... So vCPU/vRAM increases may or may not improve performance joint Cisco and VMware validated architecture for using the feature! Disk subsystem performance Interconnects/Extenders, at a minimum you must follow the on ESXi 4.0 update.... A VM without copying or creating additional VMs, more virtual HW options,.... Recovery for what is supported.Long Distance vMotion is a joint Cisco and VMware Data for... Edition 7000M ( M5 ) appliance UC VMs ( e.g of vdisk.! Cloud Platform and others are not supported ) worst may corrupt your virtual Machine population rules for 2x32GB=64GB ignore! Limited to: NOTE: support varies by app and version is a manual move a. San replication occurs Cisco Collaboration co-resident 3rd-party-workload for VM placement do not specifically physical! For what is supported.Long Distance vMotion is a joint Cisco and VMware Recovery... And upgrade Design Guide upgrade Guide: Component & amp ; capacity Point and VM configurations corrupt your Machine! Storage product from VMware the UC application may have been done on 4.0. Done on ESXi 4.0 update 1 VMware vSphere ESXi 4.1 introduced a new setting called `` Large Offload! On ESXi 4.0 update 1 or VMware software, or during troubleshooting to software.