System Requirements and Server Configuration

Transcription

1 Hardware Requirements for C Series, page 1 Open Virtualization Files, page 2 VMware Hosting, page 2 Software, page 2 Side A Server Component Configurations, page 5 Side B Server Component Configurations, page 5 Software Licenses, page 6 Fault Tolerance, page 7 Local and Wide Area Network Communications, page 7 Bandwidth Provisioning and Network QoS Considerations, page Data Backup, page NTP and Time Synchronization, page Hardware Requirements for C Series The Packaged CCE deployment at the customer site must run in a duplexed environment with a pair of Unified Computing System (UCS) servers. These servers are referred to as Side A Host and Side B Host. Packaged CCE now supports both the Unified Computing System (UCS) C20 M3S TRC#1 and C260 M2 TRC#1 servers for existing deployments. Only the UCS C20 M3S TRC#1 is available for new Packaged CCE orders. C20 M3S: TRC.231 C260 M2: 1

2 Open Virtualization Files Open Virtualization Files VMware Hosting Software Open Virtualization Format files, packaged as OVAs, define the basic structure of the VMs that are created. This includes the CPU, RAM, disk space, reservation for CPU, and reservation for memory. OVA files for Packaged CCE are contained in the CCE-PAC-M1-OVA zip file at Cisco.com. ESXi 5.1 with VM Version is required. Cisco Systems Contact Center Components Component Unified Contact Center Enterprise Unified Customer Voice Portal Unified Communications Manager Unified Intelligence Center Cisco Finesse Major Release Version 10.0 and later maintenance releases 10.0 and later maintenance releases Unified CM 10.0(1) and later maintenance releases Unified CM 9.1(1) and later maintenance releases 10.0 and later maintenance releases 10.0 and later maintenance releases Operating System Microsoft Windows Microsoft Windows Linux-based Unified Communications Operating System Linux-based Unified Communications Operating System Linux-based Unified Communications Operating System Optional: Cisco Unified Interaction Manager/Web Interaction Manager and later maintenance releases Cisco SocialMiner and later maintenance releases Cisco MediaSense and later maintenance releases Third-Party Software This section lists third-party software required to deliver virtualized Contact Center modules. 2

3 Supported Browsers te Third-party software requirements are for both golden templates and direct installs. Software Microsoft Windows Server 200 R2 Standard Edition Microsoft Windows Active Directory Microsoft SQL Server 200 R2 x6 Standard Edition Antivirus Version Service Pack 1 Windows Server 2003, 200, and 2012 Service Pack 2 One of: Symantec Endpoint Protection 12.1 Trend Micro Server Protect version 5. McAfee VirusScan Enterprise.i tes Used for: te Unified CCE Call Server Unified CCE Data Server Unified CVP Server Unified CVP OAMP Server Unified CVP Reporting Server Windows Server 200 Remote Desktop is not supported for software installation or upgrade. Windows Server Active Directory support is inclusive of R2 versions. Packaged CCE does not require any specific Active Directory functional level. Used for Unified CCE Data Server. Required for all applications that run on the Windows platform. Java Java 6 Update 30 or latest update. Java 7 and later releases are not supported. Supported Browsers These browsers are supported for Release 10.0: Microsoft Internet Explorer 9 Mozilla Firefox 2 and later 3

4 Automation Tools Automation Tools Download and then install the following tools on the client from which the automation will be run. Software GoldenTemplateTool zip file PowerCLI OVF tool WinImage Microsoft Excel Version 10.0(1) 5.0, 32-bit 32-bit.5, 32-bit Release 2003 or later Download Go to series_home.html. Click Download Software. Then select Packaged Contact Center Enterprise Deployment Scripts. details?downloadgroup=ovftool350&productid=353 te -- WinImage is shareware. If you choose to not purchase a licensed copy, you will see pop-ups when you run this tool. Clicking at the pop-ups allows you to proceed. Base Configuration and Utility Tools Software CCEPACM1BaseConfig10x.zip Domain_Update_Tool.zip tes This software automatically configures certain elements needed for every PCCE deployment This tool is required after installing the base configuration to modify the domain name stored in the database. Download Go to the Download Software page at /software.cisco.com/download/ type.html?mdfid=236031&i=rm. Click the link for Configuration Scripts. Then select the zip file for the Base Configuration script. Go to the Download Software page at /software.cisco.com/download/ type.html?mdfid=236031&i=rm. Click the link for Configuration Scripts. Then select the utility to modify the domain name.

5 Side A Server Component Configurations Side A Server Component Configurations Components vcpu* RAM (in GB) HDD (in GB) CPU Reservation (in MHz) Virtual Network Adapter Type RAM Reservation (in MB) Unified CCE Call Server Unified CCE Data Server Unified CVP Server 1A Unified CVP Server 2A Finesse E Unified CVP OAMP Server 1 0 no reservation made no reservation made Unified Intelligence Center Publisher Flexible 10GB (1020MB) Unified Communications Manager Publisher Unified Communications Manager Subscriber * vcpus are oversubscribed by design. Side B Server Component Configurations Components vcpu* RAM (in GB) HDD (in GB) CPU Reservation (in MHz) Virtual Network Adapter Type RAM Reservation (in MB) Unified CCE Call Server

6 Software Licenses Components vcpu* RAM (in GB) HDD (in GB) CPU Reservation (in MHz) Virtual Network Adapter Type RAM Reservation (in MB) Unified CCE Data Server Unified CVP Server 1B Unified CVP Server 2B Unified CVP Reporting Server (optional) no reservations made no reservations made Finesse E Unified Intelligence Center Subscriber Flexible 10GB (1020MB) Unified Communications Manager Subscriber * vcpus are oversubscribed by design. Software Licenses Software License or PAK Quantity Included with Packaged CCE license SKU? Required? Details Unified CVP PAKs 1 PAK for each of the four required Unified CVP Servers Unified Intelligence Center 1 PAK 1 PAK to be applied to the Unified Intelligence Center Publisher on Side A. Unified Call Studio 2 PAKs 1 PAK for each Unified Call Studio workstation. Unified CVP Reporting Server 1 or 2 PAKs Maximum of 2 additional Unified CVP PAKs for each optional Unified CVP Reporting Server. 6

7 Fault Tolerance Software License or PAK Quantity Included with Packaged CCE license SKU? Required? Details Microsoft Windows Server 200 R licenses 1 Virtual OS license for each of the required Unified CCE Call and Data Servers = licenses. 1 Virtual OS license for each of the required Unified CVP Servers = licenses. 1 Virtual OS license for the Unified CVP OAMP Server = 1 license. 1 additional Windows Server Virtual OS license for an optional Unified CVP Reporting Server. te For more information on Microsoft Windows Server Licensing options, please contact Microsoft or your authorized Microsoft reseller. Microsoft SQL Server licenses 1 license for each Data Server. VMware vsphere Standard or Enterprise ESXi 5.x licenses 2 licenses for the server on Side A and 2 licenses for the server on Side B. 1 license per CPU in each server. Each server has 2 CPUs. VMware vcenter 5.x 1 license Needed by partners who use the Packaged CCE Golden Template cloning process. Fault Tolerance Packaged Contact Center Enterprise uses two servers to run the core applications components in duplex (synchronized) operation. This gives the contact center site survivability and recovery in most failure scenarios. Packaged CCE does not support simplex (single-server) deployments, outside of lab mode. Router and PG co-location on a single physical server (one per side) requires a high level of network fault tolerance to avoid a double failure. A double failure is the loss of both the Visible and Private network connectivity to the host server, causing a potentially serious degradation in call routing. Recovery from double failure requires manual intervention. Local and Wide Area Network Communications Due to the use of VMware virtual switch (vswitch) and the nature of the fault and recovery mechanism, Cisco Systems requires VMware NIC Teaming to connect to redundant physical switches for the Packaged CCE public and private networks. See the Cisco Packaged Contact Center Enterprise Installation and Upgrade Guide for more on this design. 7

8 Bandwidth Provisioning and Network QoS Considerations Network uplink designs other than that detailed in the Cisco Packaged Contact Center Enterprise Installation and Upgrade Guide may expose the applications to unexpected fault scenarios that impact the recovery and/or operation of the Contact Center. This fault tolerant design specifies use of two VMware vswitches, one each for the Packaged CCE public and private network VLANs. Each vswitch has one Active and one Standby vmnic. Each Active/Standby pair should be split across physical NIC adapters (for example, Active onboard/standby on add-in card) and alternate Active paths to two data center switches. These two data center switches must be configured for both public and private network communications. The intention of the uplinks is to ensure that no single failure (physical NIC card, cable, physical switch) causes the loss of both the public and private network communications at the same time, or the loss of both the Active and Standby for the same vswitch at the same time. te VMware and server management vswitch should also be configured separately for enterprise management separate from either the public or private network communications paths, following VMware best practices. Campus LAN, Metro Area Network (MAN) and Wide Area Network (WAN) (all considered WAN from here) split Packaged CCE deployments require a highly available Visible network communications between those data centers. These data centers must also have dedicated or shared Packaged CCE Private network communications path in a topology such that no single point of failure within that data center and WAN infrastructure results in the loss of both the Packaged CCE visible and private network communications for more than 500ms. Latency Requirements Network Visible Private Maximum Round Trip Time Supported 00 ms 100 ms Bandwidth Provisioning and Network QoS Considerations Data Backup Your Wide Area Network must support QoS. For details, refer to the Bandwidth Provisioning and QoS considerations section in the Cisco Unified Contact Center Enterprise Design Guide. at en/us/partner/products/sw/custcosw/ps1/products_implementation_design_guides_list.html. Data backup tools must be run during a scheduled maintenance window. If you use local SQL backups, make sure that the local machine has sufficient capacity. If not, back up to remote storage on the network. NTP and Time Synchronization Packaged CCE requires that all parts of the solution have the same time. While time drift occurs naturally, it is critical to configure NTP to keep solution components synchronized. To prevent time drifts on Live Data reports, the NTP settings on the Data Server VMs, the Call Server VMs, and on the Cisco Unified Intelligence Center Publisher and Subscriber VMs must be synchronized.

9 NTP and Time Synchronization Refer to the Cisco Packaged Contact Center Enterprise Installation and Upgrade Guide for details: 9

10 NTP and Time Synchronization 10