:*To download a OVA file, click the '''Download File''' button next to that file. click the '''Add to Cart''' button next to file, then click on the '''Download Cart''' link. A Download Cart page appears.

:*To download a OVA file, click the '''Download File''' button next to that file. click the '''Add to Cart''' button next to file, then click on the '''Download Cart''' link. A Download Cart page appears.

This table shows the supported Cisco Unified EIM-WIM components, their capacities, and the VM computing resource requirements. You must use the OVA virtual machine templates to create the Cisco Unified EIM-WIM component VMs.

+

To see the supported Cisco Unified EIM-WIM components, their capacities, and the VM computing resource requirements, refer to [[Unified Communications Virtualization Downloads (including OVA/OVF Templates)]]. You must use the OVA virtual machine templates to create the Cisco Unified EIM-WIM component VMs.

Note: For Virtual Machines that need more than 4 vCPUs, the VMware vSphere ESXi Enterprise Plus licensing is required (8 way virtual SMP capability). The VMware vSphere Enterprise Plus license can be procured from the Cisco build-to-order or directly from the VMware (see VMware Purchasing section above.)

Note: For Virtual Machines that need more than 4 vCPUs, the VMware vSphere ESXi Enterprise Plus licensing is required (8 way virtual SMP capability). The VMware vSphere Enterprise Plus license can be procured from the Cisco build-to-order or directly from the VMware (see VMware Purchasing section above.)

You can have one or more EIM-WIM components co-resident on the same ESXi server. However, you must follow the rules described below:

You can have one or more EIM-WIM components co-resident on the same ESXi server. However, you must follow the rules described below:

-

1)DB server component for capacity above 360 agents is not co-resident with any other EIM-WIM or other applications - Requires its own blade.

+

1)EIM/WIM Virtual Machines with the exception of DB server Virtual Machine can co-reside with any other UC application Virtual Machine&nbsp;as long as&nbsp;there is no oversubscription of CPU and Memory. DB Server Virtual Machine can co-reside with UC applications Virtual Machines which are not DB server themselves

-

2)Co-Residency of EIM-WIM components with UC applications and other third party application is not supported

+

2)Co-Residency of EIM-WIM components with third party application is not supported

3)You can have any number of EIM-WIM virtual machines on an ESXi server as long as the sum of all the virtual machine CPU and memory resource allocation is not over committed on the available ESXi server computing resources.

3)You can have any number of EIM-WIM virtual machines on an ESXi server as long as the sum of all the virtual machine CPU and memory resource allocation is not over committed on the available ESXi server computing resources.

Line 152:

Line 154:

4) You must not have CPU overcommitted on the ESXi server that is running EIM-WIM components . The total number of vCPUs among all the virtual machines on an ESXi host must not greater than the total number of CPUs available on the ESXi server. In the case of the Cisco UCS B-200 M1, the total number of CPUs available is 8.

4) You must not have CPU overcommitted on the ESXi server that is running EIM-WIM components . The total number of vCPUs among all the virtual machines on an ESXi host must not greater than the total number of CPUs available on the ESXi server. In the case of the Cisco UCS B-200 M1, the total number of CPUs available is 8.

-

5)You must not have memory overcommitted on the ESXi host that is running UC realtime applications. You must allocate minimum 2GB of memory for the ESXi kernel. For example, if an ESXi server on B-200 M1 hardware has 36GB of memory, after you allocate 2GB for the ESXi kernel, you have 34GB available for the virtual machines. The total memory allocated for all the virtual machines on an ESXi server must not be greater than 34GB in this case.

+

5)You must not have memory overcommitted on the ESXi host that is running UC realtime applications. You must allocate minimum 2GB of memory for the ESXi kernel. For example, if an ESXi server on B-200 M1 hardware has 36GB of memory, after you allocate 2GB for the ESXi kernel, you have 34GB available for the virtual machines. The total memory allocated for all the virtual machines on an ESXi server must not be greater than 34GB in this case.

== Performance Requirements ==

== Performance Requirements ==

Line 158:

Line 160:

CPU usage (average) should not exceed 60% for the ESXi Server and for each of the individual processors, and for each VM. Memory usage (average) should not exceed 80%x for the ESXi Server and for each of the VMs. VM snapshots are not supported in production since they have significant impact on system performance.

CPU usage (average) should not exceed 60% for the ESXi Server and for each of the individual processors, and for each VM. Memory usage (average) should not exceed 80%x for the ESXi Server and for each of the VMs. VM snapshots are not supported in production since they have significant impact on system performance.

-

<br> The data is collected from the test run of 200 users working on Email, 200 users working on Chat and 200 more working on Blended Collaboration activities (Total of 600 agents). Email activities were processing at 12 per hour per agent and Chat and Blended Collaboration activities were processed at the rate of 10 per hour per agent. <br>

+

Here are some representative performance counters from tests conducted in our labs.

+

+

=== Email ===

+

+

<br>The data is collected from the test run of 1500 users with emails being processed at a rate of 5 emails per hour per agent. <br>

{| class="wikitable FCK__ShowTableBorders"

{| class="wikitable FCK__ShowTableBorders"

Line 176:

Line 182:

| '''95th Pct.'''

| '''95th Pct.'''

| '''Avg.'''

| '''Avg.'''

-

<br>

+

<br>

|-

|-

| Application Server

| Application Server

-

| 11.7

+

| 1523

-

| 3.21

+

| 433.12

-

| 1.55

+

| 75.1

-

| 51

+

| 512.2

-

| 1

+

| 65.04

-

| 0.726

+

| 16.93

-

| 103

+

| 1087

-

| 19

+

| 368.82

-

| 8.32

+

| 57.88

|-

|-

| File Server

| File Server

-

| 43.65

+

| 22

-

| 25.23

+

| 19.1

-

| 14.36

+

| 14.44

-

| 189

+

| 5

-

| 2

+

| 1

-

| 2

+

| 0.15

-

| 1769

+

| 19

-

| 1025.9

+

| 18

-

| 446

+

| 14

|-

|-

| Database Server

| Database Server

-

| 736.9

+

| 5127

-

| 552

+

| 4948.3

-

| 263.31

+

| 3670.23

-

| 35450

+

| 171

-

| 23184

+

| 26.6

-

| 3903

+

| 10.6

-

| 5737

+

| 5125

-

| 2872

+

| 4866

-

| 1625

+

| 3658.8

|-

|-

| Messaging Server

| Messaging Server

-

| 9.15

+

| 4

-

| 2.71

+

| 1.3

-

| 1.47

+

| 1.14

-

| 57

+

| 0

-

| 1

+

| 0

-

| 0.7

+

| 0

-

| 88

+

| 4

-

| 15.1

+

| 1.3

-

| 8

+

| 1.14

|-

|-

| Services Server

| Services Server

-

| 11.15

+

| 69

-

| 3.155

+

| 20.4

-

| 1.53

+

| 6.5

-

| 55

+

| 7

-

| 1

+

| 1.3

-

| 0.73

+

| 0.29

-

| 1.89

+

| 68

-

| 17

+

| 20.4

-

| 9

+

| 6.19

|-

|-

| Web Server

| Web Server

-

| 11.2

+

| 22.6

-

| 3.36

+

| 16.32

-

| 1.43

+

| 8.59

-

| 55

+

| 14.8

+

| 8.4

+

| 1.74

+

| 12.2

+

| 8.84

+

| 6.73

+

|}

+

+

=== Chat ===

+

+

==== Lite configuration with 200 users. ====

+

+

The data is collected from the test run of 200 users with chats being processed at a rate of 5 chats per hour per agent.

+

+

{| class="wikitable FCK__ShowTableBorders"

+

|-

+

! rowspan="2" | EIM-WIM Components

+

! colspan="3" | IOPS

+

! colspan="3" | Disk Read KBytes / sec

+

! colspan="3" | Disk Write KBytes / sec

+

|-

+

| '''Peak'''

+

| '''95th Pct.'''

+

| '''Avg.'''

+

| '''Peak'''

+

| '''95th Pct.'''

+

| '''Avg.'''

+

| '''Peak'''

+

| '''95th Pct.'''

+

| '''Avg.'''

+

<br>

+

+

|-

+

| Lite Server

+

| 2630

+

| 2532

+

| 2054.7

+

| 715

+

| 76.6

+

| 23.45

+

| 2595

+

| 2516

+

| 2030.6

+

|}

+

+

+

==== Large configuration with 1500 users ====

+

+

The data is collected from the test run of 1500 users with chats being processed at a rate of 5 chats per hour per agent.

+

+

{| class="wikitable FCK__ShowTableBorders"

+

|-

+

! rowspan="2" | EIM-WIM Components

+

! colspan="3" | IOPS

+

! colspan="3" | Disk Read KBytes / sec

+

! colspan="3" | Disk Write KBytes / sec

+

|-

+

| '''Peak'''

+

| '''95th Pct.'''

+

| '''Avg.'''

+

| '''Peak'''

+

| '''95th Pct.'''

+

| '''Avg.'''

+

| '''Peak'''

+

| '''95th Pct.'''

+

| '''Avg.'''

+

<br>

+

+

|-

+

| Application Server

+

| 567

+

| 104

+

| 76.82

+

| 150

+

| 22.8

+

| 4.31

+

| 553

+

| 79.6

+

| 72.11

+

|-

+

| File Server

+

| 15

+

| 14.8

+

| 12.14

+

| 2

+

| 0

+

| 0.03

+

| 15

+

| 13.8

+

| 12.08

+

|-

+

| Database Server

+

| 1517

+

| 1097.4

+

| 955.62

+

| 563

+

| 185

+

| 91.2

+

| 1032

+

| 983.4

+

| 863.48

+

|-

+

| Messaging Server

| 1

| 1

| 0.8

| 0.8

-

| 173

+

| 0.048

+

| 0

+

| 0

+

| 0

+

| 1

+

| 0.8

+

| 0.048

+

|-

+

| Services Server

| 21

| 21

-

| 10.24

+

| 6

+

| 3.68

+

| 2

+

| 0

+

| 0.03

+

| 21

+

| 5

+

| 3.61

+

|-

+

| Web Server

+

| 101

+

| 76

+

| 68.95

+

| 10

+

| 3.2

+

| 0.28

+

| 90

+

| 76

+

| 68.57

|}

|}

+

== Installing VMware Tools ==

== Installing VMware Tools ==

Line 256:

Line 391:

== Migrating ==

== Migrating ==

-

Migration of EIM-WIM components from existing physical boxes to VMs is not supported.Also we do not support EIM-WIM deployments which are mix of physical hardware and VMs

+

Migration of EIM-WIM components from existing physical boxes to VMs is not supported. Unified EIM-WIM deployments that are mix of physical hardware and VMs are also not supported.

-

+

-

== Unified EIM-WIM, Release 4.3(2) Support for Virtualization on the ESXi/UCS Platform ==

+

-

+

-

*Unified EIM-WIM is qualified with ESXi4.0 as of now and qualification on ESXi 4.1 is in progress.Note that once the VM is upgraded to ESXi 4.1 , VMWare tools need to upgraded as well in all VMs. For more information on upgrading refer to [http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1003806|http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1003806 VMware documentation]

VMware and Application Software Requirements

Configuring the ESXi Host Network for the Virtual Machines

To configure the network for VMs, you create a virtual switch connected to an Ethernet port on the server, and then associate the virtual machine's network adapter to this virtual switch. To Add a vSwitch

Creating Virtual Machines from OVA VM Template

Downloading OVA Template

To download a OVA file, click the Download File button next to that file. click the Add to Cart button next to file, then click on the Download Cart link. A Download Cart page appears.

Click the Proceed with Download button on this page. A Software License Agreement page appears.

Read the Software License Agreement, then click the Agree button

On the next page, click on either the Download Manager link (requires Java) or the Non Java Download Option link. A new browser window appears.

If you selected Download Manager, a Select Location dialog box appears. Specify the location where you want to save the file, and click Open to save the file to your local machine.

If you selected Non Java Download Option, click the Download link on the new browser window. Specify the location and save the file to your local machine.

Creating Virtual Machines by Deploying the OVA Templates

In the vSphere client, perform the following steps to deploy the Virtual machines.

Highlight the host or cluster to which you wish the VM to be deployed.

Select File > Deploy OVF Template.

Click the Deploy from File radio button and specify the name and location of the file you downloaded in the previous section OR click the Deploy from URL radio button and specify the complete URL in the field, then click Next.

Verify the details of the template, and click Next.

Give the VM you are about to create a name, and choose an inventory location on your host, then click Next.

Choose the datastore on which you would like the VM to reside - be sure there is sufficient free space to accommodate the new VM, then click Next.

Choose a virtual network for the VM, then click Next.

Verify the deployment settings, then click Finish.

Note:

VM CPU affinity is not supported. You don't need to set CPU affinity for the VMs that are running Cisco Unified EIM-WIM applications on the VMware ESXi on UCS platform.

VM resource Reservation - VM resource reservation is not supported for the VMs that are running Cisco Unified EIM-WIM applications on the VMware ESXi on UCS platform. The VM computing resources should have a default reservation setting, which is no resource reservations.

You cannot change the computing resource configuration of your VM at any time.

You can never go below the minimum VM computing resource requirements as defined in the OVA templates.

Note: For Virtual Machines that need more than 4 vCPUs, the VMware vSphere ESXi Enterprise Plus licensing is required (8 way virtual SMP capability). The VMware vSphere Enterprise Plus license can be procured from the Cisco build-to-order or directly from the VMware (see VMware Purchasing section above.)

Cisco Unified EIM-WIM Component Co-Residency

You can have one or more EIM-WIM components co-resident on the same ESXi server. However, you must follow the rules described below:

1)EIM/WIM Virtual Machines with the exception of DB server Virtual Machine can co-reside with any other UC application Virtual Machine as long as there is no oversubscription of CPU and Memory. DB Server Virtual Machine can co-reside with UC applications Virtual Machines which are not DB server themselves

2)Co-Residency of EIM-WIM components with third party application is not supported

3)You can have any number of EIM-WIM virtual machines on an ESXi server as long as the sum of all the virtual machine CPU and memory resource allocation is not over committed on the available ESXi server computing resources.

4) You must not have CPU overcommitted on the ESXi server that is running EIM-WIM components . The total number of vCPUs among all the virtual machines on an ESXi host must not greater than the total number of CPUs available on the ESXi server. In the case of the Cisco UCS B-200 M1, the total number of CPUs available is 8.

5)You must not have memory overcommitted on the ESXi host that is running UC realtime applications. You must allocate minimum 2GB of memory for the ESXi kernel. For example, if an ESXi server on B-200 M1 hardware has 36GB of memory, after you allocate 2GB for the ESXi kernel, you have 34GB available for the virtual machines. The total memory allocated for all the virtual machines on an ESXi server must not be greater than 34GB in this case.

Performance Requirements

CPU usage (average) should not exceed 60% for the ESXi Server and for each of the individual processors, and for each VM. Memory usage (average) should not exceed 80%x for the ESXi Server and for each of the VMs. VM snapshots are not supported in production since they have significant impact on system performance.

Here are some representative performance counters from tests conducted in our labs.

Email

The data is collected from the test run of 1500 users with emails being processed at a rate of 5 emails per hour per agent.

EIM-WIM Components

IOPS

Disk Read KBytes / sec

Disk Write KBytes / sec

Peak

95th Pct.

Avg.

Peak

95th Pct.

Avg.

Peak

95th Pct.

Avg.

Application Server

1523

433.12

75.1

512.2

65.04

16.93

1087

368.82

57.88

File Server

22

19.1

14.44

5

1

0.15

19

18

14

Database Server

5127

4948.3

3670.23

171

26.6

10.6

5125

4866

3658.8

Messaging Server

4

1.3

1.14

0

0

0

4

1.3

1.14

Services Server

69

20.4

6.5

7

1.3

0.29

68

20.4

6.19

Web Server

22.6

16.32

8.59

14.8

8.4

1.74

12.2

8.84

6.73

Chat

Lite configuration with 200 users.

The data is collected from the test run of 200 users with chats being processed at a rate of 5 chats per hour per agent.

EIM-WIM Components

IOPS

Disk Read KBytes / sec

Disk Write KBytes / sec

Peak

95th Pct.

Avg.

Peak

95th Pct.

Avg.

Peak

95th Pct.

Avg.

Lite Server

2630

2532

2054.7

715

76.6

23.45

2595

2516

2030.6

Large configuration with 1500 users

The data is collected from the test run of 1500 users with chats being processed at a rate of 5 chats per hour per agent.

EIM-WIM Components

IOPS

Disk Read KBytes / sec

Disk Write KBytes / sec

Peak

95th Pct.

Avg.

Peak

95th Pct.

Avg.

Peak

95th Pct.

Avg.

Application Server

567

104

76.82

150

22.8

4.31

553

79.6

72.11

File Server

15

14.8

12.14

2

0

0.03

15

13.8

12.08

Database Server

1517

1097.4

955.62

563

185

91.2

1032

983.4

863.48

Messaging Server

1

0.8

0.048

0

0

0

1

0.8

0.048

Services Server

21

6

3.68

2

0

0.03

21

5

3.61

Web Server

101

76

68.95

10

3.2

0.28

90

76

68.57

Installing VMware Tools

The VMware Tools must be installed on each of the VMs and all of the VMware Tools default settings should be used. Refer to the VMware documentation for instructions on installing or upgrading VMware Tools on the VM with Windows operating system.

Installing Cisco Unified EIM-WIM Components on Virtual Machines

You can install the Cisco Unified EIM-WIM components after the configuration of the VMs. Installation of these Cisco Unified EIM-WIM components on a VM is the same as the installation of these components on physical hardware. Refer to the Cisco Unified EIM-WIM Install Guide for the steps to install Cisco Unified EIM-WIM components.

Migrating

Migration of EIM-WIM components from existing physical boxes to VMs is not supported. Unified EIM-WIM deployments that are mix of physical hardware and VMs are also not supported.