Rather than deploying with specialized hardware, you can create a virtualized deployment of IBM
® Unified Telephony by first installing the VMware ESX/ESXi virtualized platform on any supported hardware, and then deploying Sametime
Unified Telephony servers on top of it.
Before you begin
Install the VMWare ESXi 4.0 virtualized platform onto each server that will host a virtualized Sametime
Unified Telephony server. For detailed software and hardware recommendations, see the VMware Compatibility Guides
. Information on virtual machine overhead characteristics is available in the VMware Resource Management Guide for each version of VMware; resource guides are available at the VMware documentation page
About this task
A virtual machine is a self-contained operating system that behaves as if it is a separate computer. A virtual environment is hardware independent, relying on the virtualization platform to mimic the necessary hardware. Sametime
Unified Telephony supports the use of the VMware VMWare ESXi 4.0 virtualized platform for a standard duplex (co-located and geographically separated) configuration. All hardware used should be on the VMware compatibility list for VMWare ESXi 4.0.
Because a virtualized deployment is hardware independent, IBM
cannot predict which hardware your deployment will use; the examples provided in this guide describe the installation and set-up for a IBM
x3550 M2 server.
The virtual machine specifications are essentially the same as the physical machines with regards to CPU, memory and hard disks; the one difference, which is very important, is that on a virtual system, hyperthreading on the CPU's must be disabled.
The virtualized Sametime
Unified Telephony deployment has the following specific characteristics:
- Supports Sametime Unified Telephony images in a Storage Area referred to as a “datastore”.
- Is hardware independent.
- Has no maintenance controller interfaces (RSA, IMM, iRMC, VMK).
- Does not support hardware alarming.
- Currently supports and requires a fixed number of 4 (virtual) Ethernet ports.
- Supports 2-node clustering in co-location and network geographical separation.
- Can be deployed as co-located on 1 host (both nodes on same physical host) or on 2 hosts, or as a geo-separated system on 2 hosts.
- Can use internal or SAN storage.
- Is compatible with VMware ESXi 4; all hardware used should be on the VMware compatibility list for ESXi 4.0.
- Requires a virtual machine disk size of at least 140 GB.
The virtualized deployment is subject to the following limitations:
- Hyperthreading must be disabled on the CPUs.
- When installing from an ISO image file, you must allocate at least 5 GB of disk space in a node’s datastore for the placement of the Virtualization Image DVD ISO and Node Configuration files.
- Because the virtual machine is hardware independent, it is assumed that the physical server and the virtualized platform are installed, supervised, and maintained by the customer. This documentation does not describe how to deploy the physical server or the VMware virtualized platform.
- The virtual Sametime Unified Telephony server assumes it has one disk and 4 Ethernet ports.
- Disk location (local or network), disk redundancy (RAID), hardware redundancy, and network redundancy (bonding driver) are outside the scope the virtual Sametime Unified Telephony server’s control, and must be installed by the customer.
Although the VMware platform supports a wider range of hardware than the standard Sametime
Unified Telephony servers, you must still ensure that your servers meeting the minimum requirements described here. Failure to meet these requirements may result in diminished performance, or even a non-functioning product.
Complete these steps to ensure you are preparing the virtualization environment correctly:
Parent topic: Planning
- Review the virtualization requirements described in this subsection.
- Verify that your physical server hardware is supported by VMware.
- Decide whether you will deploy a SAN (Storage Area Network) drive or use the local hard disk of the physical server.
- If you will connect a SAN, verify that it is supported by VMware.
- Make sure you have a working Microsoft™ Windows™ or Linux™ system available for building the node.cfg files and placing them on the virtual floppy disks for installing the Telephony Control Server application.
- If network redundancy is required, configure the VMware host with NIC teaming and determine the network port to VMNIC mapping.
- Decide which type of installation configuration you will be conducting: co-located or geo-separated.
- For a co-located configuration, decide whether the guest servers will be running on 1 physical host server or 2 physical host servers.
- Determine network cabling based on the configuration decisions you made in the previous steps.
- Create the guest virtual machines according to the specifications in the VMware release notes.
- Install the Telephony Control Server image on each of virtual machines.