# Configure MiVoice Border Gateway Cluster

To provide Teleworker services to devices on the internet, you must cluster the MiVoice Border Gateway application on the MiCollab with one or more remote MBGs located in the Network Edge or DMZ. You can cluster multiple MBG servers in this configuration to support additional Teleworker capacity or to provide resiliency for the Teleworker phones.

If the MiCollab server and remote MBG server(s) are not clustered correctly, the system displays the following error:

"One or more of the current MiVoice Border Gateway configurations are invalid for Teleworker. This configuration requires a cluster with the following attributes: This node (MiCollab) must not reside in the default zone and all nodes (MiCollab and MBG) in the cluster must have weights of non-zero. See help."

After you configure the cluster correctly, the system clears the error message.

To configure the cluster correctly:

1. Log into the MSL server manager on the MiCollab server. Un der Applications, click MiVoice Border Gateway, click the System status tab and then click Dashboard.

2. Create a new cluster on the MiCollab (master) server:

1. - In the Clustering status frame, click Create a cluster.

   - Select the IP address of the MiCollab server in the IP Address of current node field.

   - Enter the IP address of the MBG server (DMZ address or server-gateway WAN address) in the IP Address of peer node field.

   - In the Cluster weight of current node field, select the cluster weight factor value to apply to the MiCollab master server for load balancing. The default value is 0. You must select a non-zero value.

     The "weight factor" determines the node's participation in load balancing. To inform the cluster that the node should handle more than an equal share of the load, increase its weight factor. To handle less load, lower its weight factor.

   - Click Save. The two new nodes are added to the Node information list as members of the "Default" cluster zone.

3. Create a new "LAN" zone:

1. - Click + Zone (Add new zone).

   - In the cluster zone name field enter "LAN".

   - Click Save.

4. Modify the MiCollab node and add it to the "LAN" zone:

3. - Click (Modify node).

   - Set the Cluster zone for current node field to "LAN".

   - Click Save.

5. Log into the MSL server manager on the MBG server. Under Applications, click MiVoice Border Gateway, click the System status tab and then click Dashboard.

6. Join the cluster from MBG (slave) server:

1. - In the Clustering status frame, click Join a cluster.

   - Select the IP address of the MBG server in the IP Address of current node field.

   - Enter the IP address of the MiCollab in the IP Address of peer node field.

   - Click Save.

7. The screen indicates that the master is currently not connected. After several seconds, refresh your browser and the screen is updated to indicate that the servers are clustered. The Cluster status field identifies the MiCollab server as the master node.

8. For the node you have just added, click (Modify node).

9. In the Cluster weight of current node field, select a non-zero value to apply to the slave server. The default value is 0. You must select a non-zero value.

   The "weight factor" determines the node's participation in load balancing. To inform the cluster that the node should handle more than an equal share of the load, increase its weight factor. To handle less load, lower its weight factor.

10. Click Save.

Note: By default, the slave server has a cluster weight of zero (0). If you fail to update this value, the slave server will not participate in load balancing, even if all other nodes in the cluster fail.

11. To add more MBG servers to the cluster, join the cluster from other MBG (slave) servers:

1. - On the MiCollab (master) server, program the MBG(s) as new nodes in the cluster.

   - On the MBG (slave) server(s), program them as slaves to the MiCollab (master) server.

Note: Provision Teleworker services from the MiCollab server. Do not provision them on the MBG servers; otherwise, the MiCollab and MBG databases could get out of sync.