Jump to: navigation, search

Deploying HA Instances of UC Connector

The following table provides an overview of the tasks you must complete to deploy a highly available configuration of UC Connector in a Windows NLB cluster environment.

Note: The information below presents an NLB cluster approach rather than the recommended IP Address Takeover Approach.

Step Related procedures and Information
Ensure that your system meets the deployment prerequisites. See Windows NLB Cluster HA Deployment Prerequisites.
Configure Windows Network Load Balancing (NLB) Parameters. Use the Windows NLB Configuration Manager to configure load balancing parameters, as described in Configuring Windows NLB cluster parameters.
UC Connector HA Deployment.

Complete the following procedures to deploy your UC Connector HA configuration:
1. Configuring the primary UC Connector (Windows NLB cluster).
2. Configuring the Backup UC Connector (Windows NLB cluster).
3. Configuring HA for Custom Server.
4. Creating Virtual IP Interface control scripts (Windows NLB cluster). Virtual IP (VIP) interface control scripts are used to enable and disable UC Connector ports when UC Connector change modes.
5. Creating application objects for VIP control scripts (Windows NLB cluster). Application objects allow the VIP control scripts to be run as applications.
6. Creating alarm reaction scripts (Windows NLB cluster). Alarm reaction scripts are called when HA-related alarm conditions are activated.
7. Creating alarm conditions (Windows NLB cluster). When an HA-related log event occurs, such as a log event that records when a UC Connector changes from primary to backup mode, Alarm Conditions are activated.
8. Testing alarm conditions (Windows NLB cluster).

This page was last edited on June 27, 2016, at 22:20.
Comments or questions about this documentation? Contact us for support!