|
|
Version 4.4 |
(top) |
|
Note: This information listed here for convenience. For latest information, when in doubt, or if conflicts, see TelePresence Server Release Notes.
|
|
|
|
Version 4.3 |
(top) |
|
Note: This information listed here for convenience. For latest information, when in doubt, or if conflicts, see TelePresence Server Release Notes.
|
|
|
|
Version 4.1 and 4.2 |
(top) |
|
Note: This information listed here for convenience. For latest information, when in doubt, or if conflicts, see TelePresence Server Release Notes.
|
|
|
|
Version 4.0 |
(top) |
|
Note: This information listed here for convenience. For latest information, when in doubt, or if conflicts, see TelePresence Server Release Notes.
|
|
|
|
Version 3.1 |
(top) |
|
Note: This information listed here for convenience. For latest information, when in doubt, or if conflicts, see TelePresence Server Release Notes.
|
|
|
|
Notes on v4.4 Large VM configuration |
(top) |
| |
This VM configuration only supported on certain hardware, and must be the only VM on the server:
- Cisco Multiparty Media 400v
- Cisco Multiparty Media 410v
- Cisco Multiparty Media 410vb
- Cisco Meeting Server 1000
For capacity information, see the Data Sheet and Release Notes.
|
|
|
Notes on v4.1, 4.2 and 4.3 Large VM configuration |
(top) |
| |
This VM configuration only supported on certain hardware, and must be the only VM on the server:
- Cisco Multiparty Media 400v
- Cisco Multiparty Media 410v
- Cisco Multiparty Media 410vb
For capacity information, see the Data Sheet and Release Notes.
|
|
|
Notes on v4.1, 4.2 and 4.3 Medium VM configuration |
(top) |
| |
| This VM configuration must be the only VM on the server.
For capacity information, see the Data Sheet and Release Notes.
|
|
|
Notes on v4.1, 4.2 and 4.3 Small VM configuration |
(top) |
| |
| With BE6000M based on UCS M3 and Specs-based with the E5-2609, the capacity is lower.
For capacity information, see the Data Sheet and Release Notes.
|
|
|
Notes on v4.0 Large VM configuration |
(top) |
| |
This VM configuration only supported on certain hardware and must be the only VM on the server:
- Cisco Multiparty Media 400v
For capacity information, see the Data Sheet and Release Notes.
|
|
|
Notes on v4.0 Medium and Small VM configuration |
(top) |
| |
|
For capacity information, see the Data Sheet and Release Notes.
|
|
|
Notes on v3.1 Medium and Small VM configuration |
(top) |
| |
| When vTS 3.1 is co-resident with other Cisco Collaboration or allowed non-Collaboration/3rd-party apps, vTS 3.1 must follow all of the standard virtualization sizing and co-residency rules.
When vTS 3.1 is the only application on an ESXi host, and the hardware matches requirements in tables above, then the following deployments are also allowed:
- One Medium VM per physical ESXi host
- or Two Small VMs per physical ESXi host
- In the above deployment models, vTS is using physical CPU oversubscription via hyperthreading and deploying 1 vcpu to 1 Logical Core. Note: Recall that none of the other Cisco Collaboration apps support physical CPU oversubscription and are required to deploy 1 vcpu to 1 physical core even when hyper-threading is enabled in the physical CPU / BIOS.
For capacity information, see the Data Sheet and Release Notes.
|
|
|
IOPS and Storage System Performance Requirements |
(top) |
| |
| Mean #IOPS: 6
Read Latency:
Write Latency:
|
|
|
|
|
