Use the VMware ESXi 4.0 virtualized platform to deploy IBM
® Unified Telephony using virtual machines.
A virtualized deployment is very similar to a physical deployment except for a few additional constraints. The most critical part, from a virtualized point of view, is the cross-over connection. Network latency on this connection can lead to intermittent failures (where one node believes the other has failed and may go into recovery mode). For this reason, the inter-cluster connection between nodes is usually on its own dedicated subnet. However a Virtual Host that is near to its physical limits may intermittently be overtaxed, resulting in virtual network performance impacts. This needs to be considered when sizing the virtual host. So you have two options: deploy both Telephony Control Server nodes on a single physical host where there is a high degree of certainty that resources will not be overutilized, or deploy each Telephony Control Server node on a separate physical host, where both physical hosts and the network in-between can guarantee no latency. Regardless of whether the system is virtual or physical, you have the same network options with regards to Signalling, Management and Billing networks.
For best results, the minimum virtualized deployment should provide for failover by including two physical hosts, with a Telephony Control Server node and a Telephony Application Server hosted on each (for example, tcs_node1/tas_node1 on the first server, and tcs_node2/tas_node2 on the second server).
You can deploy the Telephony Control Server nodes in one of the following configurations:
Co-located on 1 physical server
- 3 subnets reserved for Admin, Billing, Signaling
- Cross-over connected via virtual switch
Co-located on 2 physical servers
- 3 subnets + one Private:
- 3 subnets reserved for Admin, Billing, Signaling, plus 1 Private for Cross-over
- Cross-over cable connection between the nodes
- 4 subnets
- 4 subnets reserved for Admin, Billing, Signaling, and Cross-over
- Cross-over connectivity occurs through a layer 2 switch
Geo-separated on 2 physical servers
4 subnets per node, for a total of 8 subnets:
Parent topic: Deployment scenarios
- 4 subnets reserved for Admin, Billing, Signaling, and Cross-over for node 1
- 4 subnets reserved for Admin, Billing, Signaling, and Cross-over for node 2