For Release 9.0(1), a new OVA template is available that provides appropriate resource allocation for 9.0 UCCE components running on ESXi 5.0. Note that the 9.0(1) OVA adds CPU reservation for most virtual machines (this is new since Release 8.5(2)); doing so enables VMware hypervisor behavior that is beneficial for real-time applications. [http://www.cisco.com/cisco/software/release.html?mdfid=268439622&release=1.1&relind=AVAILABLE&flowid=5210&softwareid=283914286&rellifecycle=&reltype=latest Download]&nbsp;the appropriate OVA file for the ESXi version you are deploying on. When you deploy the OVA, a drop-down list of the configurations are presented allowing you to select the appropriate configuration for the UCCE sized component that you are installing.

For Release 9.0(1), a new OVA template is available that provides appropriate resource allocation for 9.0 UCCE components running on ESXi 5.0. Note that the 9.0(1) OVA adds CPU reservation for most virtual machines (this is new since Release 8.5(2)); doing so enables VMware hypervisor behavior that is beneficial for real-time applications. [http://www.cisco.com/cisco/software/release.html?mdfid=268439622&release=1.1&relind=AVAILABLE&flowid=5210&softwareid=283914286&rellifecycle=&reltype=latest Download]&nbsp;the appropriate OVA file for the ESXi version you are deploying on. When you deploy the OVA, a drop-down list of the configurations are presented allowing you to select the appropriate configuration for the UCCE sized component that you are installing.

-

<br>

+

<br>

{| border="1" cellspacing="3" cellpadding="3"

{| border="1" cellspacing="3" cellpadding="3"

-

|- style="background: rgb(229,228,226)"

+

|- style="background: rgb(229, 228, 226);"

! Configuration Name

! Configuration Name

! vCPU Cores

! vCPU Cores

Line 11:

Line 11:

! vRAM reservation (MB)

! vRAM reservation (MB)

! vDisk (GB)

! vDisk (GB)

-

! vNIC<br>

+

! vNIC<br>

! Notes

! Notes

|-

|-

Line 33:

Line 33:

The two vDisks can be in the same datastore

The two vDisks can be in the same datastore

-

The DB vDisk can be custom sized at OVA deployment based on solution sizing and customer retention requirements using the DB Estimator tool.

+

The DB vDisk can be custom sized at OVA deployment based on solution sizing and customer retention requirements using the DB Estimator tool.

|-

|-

Line 44:

Line 44:

| 2

| 2

| The two vDisks can be in the same datastore

| The two vDisks can be in the same datastore

-

The DB vDisk can be custom sized at OVA deployment based on solution sizing and customer retention requirements using the DB Estimator tool.

+

The DB vDisk can be custom sized at OVA deployment based on solution sizing and customer retention requirements using the DB Estimator tool.

|-

|-

Line 56:

Line 56:

| &nbsp;

| &nbsp;

|-

|-

-

| '''Agent PG – CAD 1000 agents'''

+

| '''Agent PG – CAD 1000 agents'''

| 2

| 2

| 3600

| 3600

Line 63:

Line 63:

| 1x 80

| 1x 80

| 2

| 2

-

| If '''SQL is used with CAD''', the recommendation is to add&nbsp;2 vCPU to VM Properties (i.e., '''4 vCPUs''' in total) and a second vDisk for SQL and DB. This second vDisk can be sized as needed, or use default recommendation of 80 GB.&nbsp;

+

| If '''SQL is used with CAD''', you&nbsp;may add&nbsp;2 vCPU to VM Properties (i.e., '''4 vCPUs''' in total), 2G vRAM ('''8G vRAM '''in total)&nbsp;and a second vDisk for SQL and DB for performance improvement. This second vDisk can be sized as needed, or use the default&nbsp;size of 80 GB.&nbsp;

|-

|-

| '''Agent PG – CTIOS 450 agents'''

| '''Agent PG – CTIOS 450 agents'''

Line 74:

Line 74:

| &nbsp;

| &nbsp;

|-

|-

-

| '''Agent PG – CAD 297 agents'''

+

| '''Agent PG – CAD 297 agents'''

| 1

| 1

| 1800

| 1800

Line 81:

Line 81:

| 1x 80

| 1x 80

| 2

| 2

-

| If '''SQL is used with CAD''', the recommendation is to add 1 vCPU to VM Properties (i.e., '''2 vCPUs'''&nbsp;in total) and a second vDisk for SQL and DB. This second vDisk can be sized as needed, or use default recommendation of 80 GB. Also, increase the vRAM to 6G.

+

| If '''SQL is used with CAD''', you may&nbsp;add 1 vCPU to VM Properties (i.e., '''2 vCPUs'''&nbsp;in total), 2G vRAM ('''6G vRAM '''in total), and a second vDisk for SQL and DB for performance improvement. This second vDisk can be sized as needed, or use the default size of&nbsp;80 GB.

|-

|-

| '''MR PG 2000 agents 10 pims'''

| '''MR PG 2000 agents 10 pims'''

Line 192:

Line 192:

The two vDisks can be in the same datastore

The two vDisks can be in the same datastore

-

The DB vDisk can be custom sized at OVA deployment based on solution sizing and customer retention requirements using the DB Estimator tool.

+

The DB vDisk can be custom sized at OVA deployment based on solution sizing and customer retention requirements using the DB Estimator tool.

|-

|-

Line 205:

Line 205:

The two vDisks can be in the same datastore

The two vDisks can be in the same datastore

-

The DB vDisk can be custom sized at OVA deployment based on solution sizing and customer retention requirements using the DB Estimator tool.

+

The DB vDisk can be custom sized at OVA deployment based on solution sizing and customer retention requirements using the DB Estimator tool.

|-

|-

Line 218:

Line 218:

The two vDisks can be in the same datastore &nbsp;

The two vDisks can be in the same datastore &nbsp;

-

The DB vDisk can be custom sized at OVA deployment based on solution sizing and customer retention requirements using the DB Estimator tool.

+

The DB vDisk can be custom sized at OVA deployment based on solution sizing and customer retention requirements using the DB Estimator tool.

|-

|-

Line 257:

Line 257:

| &nbsp;

| &nbsp;

|-

|-

-

| '''Sigtran Gateway'''

+

| '''Sigtran Gateway/RSM'''

-

| 2

+

| 2

-

| -

+

| -

-

| 4

+

| 4

-

| 4096

+

| 4096

-

| 100

+

| 100

-

| 1

+

| 1

-

| Use the CCMP single box OVA and adjust the vCPU down to 2 (from 4).

+

| &nbsp;

|}

|}

Latest revision as of 14:23, 18 December 2013

For Release 9.0(1), a new OVA template is available that provides appropriate resource allocation for 9.0 UCCE components running on ESXi 5.0. Note that the 9.0(1) OVA adds CPU reservation for most virtual machines (this is new since Release 8.5(2)); doing so enables VMware hypervisor behavior that is beneficial for real-time applications. Download the appropriate OVA file for the ESXi version you are deploying on. When you deploy the OVA, a drop-down list of the configurations are presented allowing you to select the appropriate configuration for the UCCE sized component that you are installing.

Configuration Name

vCPU Cores

vCPU reservation (MHz)

vRAM / Memory (GB)

vRAM reservation (MB)

vDisk (GB)

vNIC

Notes

Router 8000/12000 agents

4

3000

8

8192

1 x80

2

Logger 8000/12000 agents

4

3000

8

8192

1x 80 for OS1x 500 for DB

2

The two vDisks can be in the same datastore

The DB vDisk can be custom sized at OVA deployment based on solution sizing and customer retention requirements using the DB Estimator tool.

Rogger 4000 agents

4

5400

6

6144

1x 80 for OS1x 150 for DB

2

The two vDisks can be in the same datastore

The DB vDisk can be custom sized at OVA deployment based on solution sizing and customer retention requirements using the DB Estimator tool.

Agent PG – CTIOS 2000 agents

2

3600

6

6144

1x 80

2

Agent PG – CAD 1000 agents

2

3600

6

6144

1x 80

2

If SQL is used with CAD, you may add 2 vCPU to VM Properties (i.e., 4 vCPUs in total), 2G vRAM (8G vRAM in total) and a second vDisk for SQL and DB for performance improvement. This second vDisk can be sized as needed, or use the default size of 80 GB.

Agent PG – CTIOS 450 agents

1

1800

4

4096

1x 80

2

Agent PG – CAD 297 agents

1

1800

4

4096

1x 80

2

If SQL is used with CAD, you may add 1 vCPU to VM Properties (i.e., 2 vCPUs in total), 2G vRAM (6G vRAM in total), and a second vDisk for SQL and DB for performance improvement. This second vDisk can be sized as needed, or use the default size of 80 GB.