Setting up NLB

It is important to set up the Network Load Balancing (NLB) clusters before installing K2 blackpearl. It is also important to test that the cluster is performing correctly prior to installing K2 blackpearl. An incorrectly configured cluster can cause issues when using K2 blackpearl, and it adds a layer of complexity to troubleshooting.

The Network Load Balancing supported by K2 is:

Windows Network Load Balancing Manager

The following sections will describe how to configure the two supported types as recommended by K2.

Windows Network Load Balancing Manager

Configuring Network Load Balancing is an advanced task and should only be performed by an appropriately trained professional. The steps and configurations given in this help file are to be used as a guide - your system may require additional configuration due to different hardware and software compatibilities.
The 64-bit version of Network Load Balancing Manager (nlbmgr.exe) must be used for 64-bit Windows operating systems. For more information and to get the 64-bit version of the Network Load Balancing Manager tool, please refer to the following Microsoft KB Article: http://support.microsoft.com/kb/892782

When configuring a cluster, follow the below steps:

	Open Network Load Balancing Manager (nlbmgr.exe) (Administrative Tools > Network Load Balancing Manager, or Run > nlbmgr.exe) If the feature has not been added to the Windows Server 2012, use the Add Roles andFeatures wizard on the Server Manager > Dashboard.
	Add a New Cluster (right-click on Network Load Balancing Clusters and select New Cluster)
	On the Connect screen, connect to the first host in the cluster and select the appropriate connection as the interface. If the server has multiple network adapters, many interfaces may be displayed. Be sure to select the appropriate network adapter from the list, and click next
	On the Host Parameters screen, select the host priority, add the host IP address and subnet mask, select the initial host stare then click next
	the Cluster IP Addresses screen, add in any additional IP addresses that the cluster can be accessed from, and click next
	In the Cluster Parameters window, enter the appropriate IP address, subnet mask, full internet name, and cluster operation mode, and click next
	On the Port Rules screen, edit the existing rule to use the appropriate affinity. See the notes below for recommendations based on the cluster type. Click next to continue
	To add a second node to the cluster, right-click on the newly created cluster and select Add Host to Cluster
	Connect to the second host, and make sure to select the appropriate interface

For a K2 Host Server cluster, use a Unicast operation mode and set the affinity to None. Since the K2 Host Server is a stateless machine, no affinity is necessary per session.

For a K2 Workspace Server cluster, use a Unicast operation mode and set the affinity to Single. You will want to ensure that the web pages retain an affinity to the web server during the session.

For a K2 for SharePoint Server cluster, use a Unicast operation mode and set the affinity to Single. You will want to ensure that the web pages retain an affinity to the web server during the session.

The same is true for all server clusters that host web based components (such as Process Portals, web services, web parts).

In some cases, the Network Load Balancing Manager console will time out before the second node is configured. If that happens, just right-click on the cluster and select Refresh. You should see all the nodes in a Converged state. Make sure that your cluster is configured correctly before starting the installation.

As mentioned in the Network Load Balancing Setup and Configuration topic, at least two network adaptors are required when the
Unicast operation mode is selected.

Set up the NLB configuration to allow traffic through on the K2 Workflow (default of 5252) and K2 Hostserver (default of 5555) ports.

Hardware based load balancing

Follow the hardware manufacturer's guidelines for configuring a load balanced host. Use the above notes for specifics on a K2 Host Server Cluster or a K2 Workspace Server Cluster.

While infrastructure changes are required by K2, each environment is different and has its peculiarities which must be taken into account. Modifying the infrastructure could have unforeseen results if the changes are not appropriately understood or managed. Given the broad spectrum of underlying infrastructure utilized, it is recommended that a panel or committee with appropriate skill in each area concerned be assembled to outline the underlying infrastructure changes and gauge the impact of the required changes.