Configuring a cluster of IBM
® Media Manager "SIP Proxy and Registrar" components involves several tasks, including synchronizing system clocks, configuring one or more IBM WebSphere
® proxy server to operate with the cluster.
Before you begin
You can create two types of clusters:
- A Vertical cluster resides on the Primary node and includes two or more cluster members, which run the same application.
- A Horizontal cluster includes a Primary node plus one or more Secondary nodes, all running the same application. Each node contains one cluster member.
It is suggested that you configure WebSphere
Application Server Network Deployment with a single subnet for network traffic. You can use one Network interface card (NIC) on a physical machine or logical partition (LPAR). You can also reference a single Domain name system (DNS) server in the network configuration for the physical machine or LPAR.
Before you can configure a cluster of Sametime
Media Manager "SIP Proxy and Registrar" components, you must have installed the following servers:
- Sametime System Console
This server will function as the cluster's Deployment Manager; the console can function as the Deployment Manager for multiple clusters.
Attention: Each Deployment Manager (including the Sametime System Console when it is used as a Deployment Manager) can support one cluster of each Sametime product. For example, a single Deployment Manager can support a Sametime Proxy server cluster, a Media Manager cluster, and a Meeting server cluster. To create additional clusters for a particular product, install the first server using Cell as the configuration type, which designates it as the Deployment Manager and the primary node for the cluster.
- Sametime Community Server
At least one Sametime Community Server must be deployed to provide presence and awareness for users.
- One Sametime Media Manager "SIP Proxy and Registrar" component, installed with the Primary Node option.
Every cluster requires exactly one Primary Node. The application server on the Primary Node will function as the cluster's application template. All other application servers in the cluster (nodes and cluster members) will be duplicated from the Primary Node's application server. The Primary node's application server can only belong to one cluster. The Primary Node can be used as a container for additional cluster members when creating a vertical cluster (multiple cluster members on the same physical system).
- (Horizontal cluster only) One or more Sametime Media Manager "SIP Proxy and Registrar" components, installed with the Secondary Node option.
Secondary nodes are used to horizontally scale your cluster across multiple physical systems. These additional nodes act as a container for additional cluster members, which are can be used to balance loads and provide failover within the cluster. During the clustering process, you can deploy additional product application servers on any Secondary Nodes within the cluster, creating a horizontal cluster.
To cluster SIP Proxy and Registrar components, complete the following tasks in the sequence shown:
Setting clocks on the SIP Proxy and Registrars to be clusteredParent topic: Clustering Sametime Media Manager components
Next topic: Clustering Conference Manager components
Synchronize the system clocks on the servers to be clustered with an IBM WebSphere
Application Server network deployment.
Clustering SIP Proxy and Registrars
Use the IBM
Sametime System Console to create a cluster of Sametime Servers hosted on IBM WebSphere
Application Server. The Sametime servers must all be running the same type of server; for example, Sametime Meeting Server, Sametime Proxy Server, Sametime Media Manager Conference Manager, Sametime Media Manager SIP Proxy and Registrar, or Sametime Advanced.
Restarting and synchronizing the SIP Proxy and Registrar cluster
Complete the configuration for clustering IBM
Sametime Media Manager SIP Proxy and Registrar components using an IBM WebSphere
Application Server network deployment by restarting and synchronizing nodes in the cluster and restarting the application servers in the cluster.
Setting up a WebSphere proxy server for the SIP Proxy and Registrar cluster
Set up an IBM WebSphere
proxy server for use with a cluster of IBM Sametime
servers. The proxy server can be hosted on a product node, or on a separate computer; it performs routing and caching tasks for the servers in the cluster.
Installing IBM Load Balancer for the SIP Proxy and Registrar cluster
Install and configure IBM
Load Balancer to distribute workload among a cluster of these type of servers: Sametime
Proxy Server, Sametime
Meeting Server, Media Manager Conference Manager, or Media Manager SIP Proxy and Registrar, and Sametime
Configuring WebSphere proxy server for load balancing in a SIP Proxy and Registrar cluster
To best support high availability and provide fail over services, a cluster of IBM Sametime
Media Manager components should be fronted with at least two IBM WebSphere
proxy servers and IBM
Adding load balancer ports to the virtual host alias for the SIP Proxy and Registrar cluster
After creating an IBM Sametime
Media Manager SIP Proxy and Registrar cluster, add the load balancer ports that you created for the cluster’s IBM WebSphere
proxy servers to the sip_proxyreg_host
alias in the cluster’s virtual host