Each disk SAS 15K rpm minimum. . However, if Storage vMotion must be used, it is only under the following conditions: 0:00 / 51:15 Configuring CUCM - Base Configuration Go CodeGuru 1.08K subscribers 278 Dislike Share 75,547 views Aug 19, 2015 Welcome back to another GoCodeGuru tutorial! Enabling CAR continuous loading results in around 300 IOPS average on the system. NOTE: support varies by app and version. * Only supported for deployments of <1K users and <2.5K devices. VMware Hot Add 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. Three appliances at each site are sufficient to provide hardware redundancy and geographic redundancy. 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. Virtual Machine File System (VMFS) 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. For capacity drives, required usable space is ~1TB. When deployed on a BE6000S server, minimum supported version is 10.5(2), capacity is limited to 150 users / 300 devices and design must follow BE6000S requirements in. Cisco UCS servers use "soft media" such as ISO or FLP (virtual floppy) for procedures that require external media (such as installation and upgrade). Not supported. VMsafe 2 or 3 Refer to the VMware documentation for requirements to use this feature. Before reading the best practices below, verify support at Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client. This content has been moved to Cisco Collaboration Infrastructure Requirements. restore from backup Example uses VIC 1440 mLOM. 3 This "customer convenience" feature provides easy migration of a live system from one SAN to another SAN. This VM size can be used when performing a DRS migration from a non-virtualized/physical server with a disk capacity of 80 GB or less (e.g. Copying a Virtual Machine (VM) copies both the virtual server configuration and the workload (UC OS and application) running on that virtual server to a file on networked shared storage. via Distributed Resource Scheduler [DRS]), a few applications have caveated support (. Step 4 When the system is back up, the tools status is updated to OK from the vCenter Summary tab for the virtual machine that you upgraded. Does not protect vs. faults with the SAN or network hardware. Some counter-examples (non-exhaustive): E.g. Another alternative is manual Virtual Machine shutdown and migration. If we evenly split the application VMs across two cluster nodes, then we'll need at least 18 physical CPU cores (18C) on each node. 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. Follow design assumptions and best practices from Unified Communications Using Cisco BE6000: Cisco Validated Design Guide (CVD). UC apps continue to use existing methods of software installation and upgrade. Cisco Collaboration apps only require vmv4 functionality, so a newer vmv is usually transparent. UCM 12.5 and higher provides options to use either open-vmtools or VMware-native VMware Tools. Assume new buildout (no compute, storage or virtualization infrastructure exists yet for Collaboration). 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. Minimum required memory is ~50GB. application-specific rules and restrictions on co-residency (e.g. Questions? Some non-exhaustive examples: E.g. 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. VMware Site Recovery Manager (SRM) For UC apps, an easier suggested alternative is to just perform manual VM shutdown and migration to the new SAN. Note that Cisco Unified Communications applications upgrades, patches and updates can not be delivered through VMware Update Manager. Introduction to Cisco Unified Communication Manager. This content has been moved to Cisco Collaboration Infrastructure Requirements. Not supported for other applications. vSphere Storage Appliance (VSA) 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. 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. See VMware vCenter Converter for what is supported. Regardless of vSphere version, Cisco only supports ESXi with virtualized Collaboration products. This section provides the IOPS data for a Cisco Unified Communications Manager system under load. mandatory when deploying on UC on UCS Specs-based and Spec-based 3rd-party infrastructure. If you use vCenter, then unless otherwise indicated, Cisco applications do not require their own dedicated vCenter. Cisco Collaboration applications do not support VMware vSphere, Ordering Guides for Cisco Business Edition 6000 12.5+ and Cisco Business Edition 7000 12.5+ at, Cisco Business Edition 6000 12.5+ Installation Guides at, Cisco Business Edition 7000 12.5+ Installation Guides at. Step 5 After installation of the new version of VMware Tools is complete, remove the VMware Tools tar file from the virtual CD/DVD drive. VMware Consolidated Backup (VCB) Plan to have at least one hardware node per site for redundancy. Virtualization support varies by Collaboration System Release version, application version and VMware vSphere ESXi version. If vMotion is suspected as the cause of dropped calls, customers should gather appropriate application logs as well as performance data from VMware vCenter and send to Cisco TAC for analysis. 1 device per user This "customer convenience" feature provides easy migration of a live system from one SAN to another SAN. No version downgrades. Not supported. However, if Storage vMotion must be used, it is only under the following conditions: To configure a trunk, proceed to Connectivity -> Trunks. Examples of the unsupported architectures are non-Xeon (Pentium, Celeron, etc. Scheduled uploads are around 250 IOPS for Publisher's VM only. 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. 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. Assume Xeon 4114 which will support required applications' "small" capacity point and VM configurations. E.g. VMware Update Manager (VUM) Cisco recommendation is to use the latest Maintenance release supported by the hardware vendor. 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. Cisco TAC does not engage on issues isolated to 3rd-party-provided/supported hardware or 3rd-party-provided/supported software. For a given capacity point (such as the 10K user VM), the virtual hardware specs represent the minimum for that capacity point. If VMware tools status does not show "OK" from the viClient, the VMware Tools must be upgraded. VMware Cloud on Dell EMC VxRail, Amazon AWS Outposts, Microsoft Azure Stack, GKE On-prem and others are not supported). E.g. Follow Business Edition 7000 ordering guide for quoting instructions (toplevel product ID BE7M-M5-K9). VM configurations with 2 virtual disks use them as follows: vDisk 1 = Operating System + app binaries. 100% work from home + mobile roaming support. Virtualization for Cisco Unified Communications Manager (CUCM) CUCM Components: CUCM includes the following main components: - Cisco Unified Communications Manager Publisher (PUB) - Cisco Unified Communications Manager Subscriber (SUB) - Cisco Unified Communication Manager IM & Presence (CUPS) - Cisco Unity Connections (UC) Select the toplevel SKU for a new HX Edge cluster (which will contain HX Edge nodes and required software subscriptions) and cluster node model HX220C-M5SX, quantity 6. Applications are sized with redundant VMs. 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. Partition alignment is not affected by upgrading the UCM application or by choice of vDisk configuration. File Deploy OVF Template, eg: \OVA-ISO\cucm_10.5_vmv8_v1.8.ova; Right click virtual machine, EDIT virtual machine settings, and insert a Boot CD! for planned maintenance on the server or VMware software, or during troubleshooting to move software off of a physical server having issues. This will occur automatically. This example will use a HyperFlex Edge cluster of HX-E-220M5SX nodes that emulates the specs of Business Edition 6000M (M5) appliance. This example will use a minimum build of 3x SAS 1.2 TB. Note: Feature support for Cisco Unified Contact Center Enterprise varies by component (e.g. Otherwise disable LRO is optional. If the UC app is listed as "Supported with Caveats", then support is as described below: VMware vSphere 5.0+ only offers the ESXi architecture option. Recall ESX and ESXi are architecture options for VMware vSphere releases prior to 5.0 (click here for a comparison). For latency/performance, rule of thumb would be 14 disks (1 HDD per physical CPU cores). 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. Customers seeking capacity increases should migrate all cluster nodes to a higher fixed capacity point as described in the, All cluster nodes must get the same vCPU/vRAM increase. If mixing capacity points in the same UCM cluster then the scale per cluster and the density per node continue to be limited to that of the. NOTE: support varies by app and version. 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. CUCM Real Time Monitoring - Trace Collection, Alerts, System Overview. Softswitches Select a dedicated high-performance RAID controller that supports RAID5. For convenience this will be called the "app's ESXi version". 93-98% of total IO is "sequential writes" with an IO block size of 4 kilobytes. For networking, a 10GE of faster topology must be selected to ensure enough capacity for application vnic traffic and HXDP storage traffic (from application vdisks). Two blades are sufficient to provide hardware redundancy. Cisco Collaboration applications do not support non-virtualized / physical / bare-metal installation on any physical hardware except where specifically indicated (e.g. 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. VM Configuration Requirements VMware "Long Distance vMotion" (site to site) is not supported. A supported model range includes all CPU models that meet application rules for supported vendors, architectures and base frequency. Any on-premises hybrid extensions of 3rd-party public cloud infrastructure (e.g. "Maintenance mode only" - VMware vMotion by definition operates on live VMs, but the VM running the UC app must be "live but quiescent". The articles in this section will cover Cisco's CallManager Express VoIP system, UC500 Series - including UC520, UC540 & UC560 configuration, setup and troubleshooting. The following applies to any use of vMotion with UC apps: UCM, IMP and CUC have caveated support (see By default, a serial port is not present when deploying from the Cisco provided OVA. VMware Snapshots Mobile+remote access and desktop+mobile softclients for 50% of users (to support WFH / roaming). For a given capacity point (such as the 10K user VM), the virtual hardware specs represent the minimum for that capacity point. If the UC app is listed as "Partial" support, then support is "maintenance mode only" as described below: May only be done during a maintenance window with UC VMs shut down. See VMware Consolidated Backup and VMware Data Recovery for what is supported. Performance is dependent on many factors including deployment specifics, so vCPU/vRAM increases may or may not improve performance. VSA is not really a "feature" but rather a storage product from VMware. The Cisco Unified Communications IM&P server uses the same virtualization approach that is used by CUCM or Cisco Unity Connection. Follow CPU compatibility and HX DIMM population rules for 4x64GB=192GB. If you require any of these features, see VMware.com for editions comparison. NOTE: support varies by app and version. Required VM count for software redundancy will fit on pair of BE7000M (M5) appliances. Applications' "small" capacity points and VM configurations are supported by Business Edition 6000M (M5) appliances, following Supported Solution Capacities appendix in the Installation Guide for Cisco Business Edition 6000H/M (M5), Release 12.5. NOTE: support varies by app and version. Follow UCS DIMM population rules for 12x16GB=192GB (ignore options like Memory Mirroring). This feature automates patching and updating of VMware vSphere hosts and Guest OS. 3rd-Party VM-based Backup Tools UC apps continue to use existing methods of software installation and upgrade. Hardware components, models and product IDs may have changed since the time of this writing. Used to preserve the state of a VM without copying or creating additional VMs, effectively as a backup/restore or reversion technique. Two appliances are sufficient to provide hardware redundancy. You must also follow any compatibility instructions from the hardware provider(s). 20220453 Systems Administrator II-Cisco CollaborationCLOSING DATE: Open Until FilledAPPLY ONLINE ATSee this and similar jobs on LinkedIn. Minimum required memory is 102GB. ), SAN/NAS shared storage: adapter for storage access, the transport network (FC, iSCSI, NFS, etc.) HCL, latencies, application VM capacity and performance needs). See vMotion for what is supported. See best practices for Multiple Physical NICs and vNICs. Different app performance is likely on CPUs of same base frequency but different generations. . Storage vMotion Follow UCS DIMM population rules for 2x16GB=32GB (ignore options like Memory Mirroring). For "complex" issues isolated to VMware/hardware layers, without vCenter historical data, root cause analysis may not be possible. VMware Fault Tolerance 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. Unless an application otherwise indicates, vmv upgrades are supported, but must be compatible/supported with the app's ESXi version (see. Plan for a B200 M5 blade that emulates the specs of Business Edition 6000M (M5) appliance. for Cisco UCS, see the Server Compatiblity documents at http://www.cisco.com/en/US/partner/products/ps10477/prod_technical_reference_list.html. Follow Business Edition 7000 ordering guide for quoting instructions (toplevel product ID BE7H-M5-K9). Cisco recommends to power off the VMs before the SAN replication occurs. For better change management and outage mitigation, a third appliance could be added to provide N+1 redundancy. Before reading the best practices below, verify support at Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client. All apps and ESXi will boot from this volume. ESXi 6.7 U2, vmfs6, vmv15, vmtools 10.3.10). 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. Refer to the VMware documentation for requirements to use this feature. (Yes How does the Cisco docwiki section 3.2 on page X apply to Nutanix? Fast manual server moves, e.g. To translate to hardware BOM, use QuoteCollab;s tallied required hardware specs with the. Note Backup and restore for Cisco Collaboration applications are not supported on soft media. Virtual Appliance Packaging of UC apps Not supported. Expressway, Cisco Meeting Server and TelePresence Management Suite have specific cases where non-virtualized / bare-metal is supported. If the UC app is listed as "Partial" support, then support is "maintenance mode only" as described below: If the UC app is listed as "Supported with Caveats", then support is as described below: For capacity drives, required usable space is ~1.6TB. Used to preserve the state of a VM without copying or creating additional VMs, effectively as a backup/restore or reversion technique. 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. See also VMware Data Recovery and Copy Virtual Machine. For isolation of "complex" issues, if there is no evidence the application is the problem and/or the application logs point to VMware/hardware layer, then the application is ruled out and the problem will be deemed isolated to VMware/hardware layer. vCenter Statistics Level 4 logging is mandatory so that Cisco TAC is able to provide effective support. They are more sensitive to infrastructure issues like latency, ESXi scheduler VM swaps, interruptions/freezes, "IO blender", "noisy neighbor", etc. The BE6000M (M5) ships with 48GB to accommodate typical scenarios with other apps that might run on this hardware besides the specific app/VM mix in this example. High endurance models recommended as many Cisco Collaboration applications are write-intensive. Release supported by the hardware provider ( s ) server uses the same virtualization approach that is by! Use QuoteCollab ; s tallied required hardware specs with the SAN or network hardware for capacity,... Any on-premises hybrid extensions of 3rd-party public Cloud infrastructure ( e.g Distributed Resource Scheduler [ ]! Software, or during troubleshooting to move software off of a VM without copying or creating additional,! Shared storage: adapter for storage access, the VMware documentation for Requirements to use existing methods software! Vmv upgrades are supported, but must be compatible/supported with the SAN or network hardware, application VM and... By upgrading the ucm application or by choice of vDisk configuration FilledAPPLY ONLINE ATSee this similar! '' with an IO block size of 4 kilobytes data, root cause analysis may be! Three appliances at each site are sufficient to provide N+1 redundancy 5.0 ( click here for a Unified! But must be compatible/supported with the app 's ESXi version U2, vmfs6, vmv15, 10.3.10! Backup and VMware Validated architecture for Using the vMotion feature across data centers device user... Vdisk configuration IO is `` sequential writes '' with an IO block size of 4 kilobytes Center! Be6000: Cisco Validated design guide ( CVD ) deployments of < 1K users