OVA Template Details for Unity Connection Release 8.0
From DocWiki
m (1 revision) |
m (1 revision) |
||
(One intermediate revision not shown) | |||
Line 1: | Line 1: | ||
- | *'''Go to:''' [http://www.cisco.com/cisco/software/ | + | *'''Go to:''' [http://www.cisco.com/cisco/software/navigator.html?mdfid=280082558'''OVA Download Location for Unity Connection Release 8.0'''] |
*'''Go to: [[Unified Communications Virtualization Downloads (including OVA/OVF Templates)]] ''' | *'''Go to: [[Unified Communications Virtualization Downloads (including OVA/OVF Templates)]] ''' | ||
Line 109: | Line 109: | ||
| 1 | | 1 | ||
| | | | ||
- | + | When running under ESXi 4.1, requires ESXi Enterprise Plus Licensing since it uses over 4 vCPUs for the Virtual Machine. ESXi 5.0 does not have this restriction. | |
The datastore where the Connection virtual machine will reside must be formatted with a VMware VMFS block size of 2MB or more. A block size of 1MB limits the maximum virtual hard disk size to 256GB. A block size of 2MB allows 512GB virtual disks. <br> | The datastore where the Connection virtual machine will reside must be formatted with a VMware VMFS block size of 2MB or more. A block size of 1MB limits the maximum virtual hard disk size to 256GB. A block size of 2MB allows 512GB virtual disks. <br> |
Revision as of 15:09, 17 April 2012
- Go to: OVA Download Location for Unity Connection Release 8.0
- Go to: Unified Communications Virtualization Downloads (including OVA/OVF Templates)
VM OVA Capacity | VM OVA Parameters | Notes | |||
---|---|---|---|---|---|
vCPU Cores (= Physical Cores) | vRAM (=Physical Memory) | vDisk | vNIC | ||
500 users | 1 | 2 GB | 1x 160 GB disk with pre-aligned disk partitions | 1 |
Requires reserving one physical core per physical server - see co-residency policy. Limits for Standalone Configuration:
Limits for Active/Active Cluster Configuration:
|
1000 users | 1 | 4 GB | 1x 160 GB disk with pre-aligned disk partitions | 1 |
Requires reserving one physical core per physical server - see co-residency policy. Limits for Standalone Configuration:
Limits for Active/Active Cluster Configuration:
For use on CUCM-BE 6000 |
5000 users | 2 | 4 GB | 1x 200 GB | 1 |
Requires reserving one physical core per physical server - see co-residency policy. Limits for Standalone Configuration:
Limits for Active/Active Cluster Configuration:
|
10,000 users | 4 | 4 GB | 2x 146 GB or 2x 300 GB or | 1 |
For the larger 300GB or 500 GB disks, the datastore where the Connection virtual machine will reside must be formatted with a VMware VMFS block size of 2MB or more. A block size of 1MB limits the maximum virtual hard disk size to 256GB. A block size of 2MB allows 512GB virtual disks.
Limits for Standalone Configuration:
Limits for Active/Active Cluster Configuration:
|
20,000 users | 7 | 8 GB | 2x 300 GB or 2x 500 GB If using the C210 TRC, requires atleast one additional disk for the 500 GB Overlay | 1 |
When running under ESXi 4.1, requires ESXi Enterprise Plus Licensing since it uses over 4 vCPUs for the Virtual Machine. ESXi 5.0 does not have this restriction. The datastore where the Connection virtual machine will reside must be formatted with a VMware VMFS block size of 2MB or more. A block size of 1MB limits the maximum virtual hard disk size to 256GB. A block size of 2MB allows 512GB virtual disks.
Limits for Standalone Configuration:
Limits for Active/Active Cluster Configuration:
|
Back to: Unified Communications in a Virtualized Environment |
---|