Load Balancing

Published on May 2016 | Categories: Documents | Downloads: 57 | Comments: 0 | Views: 558
of 6
Download PDF   Embed   Report

Comments

Content

OutlookSoft® Everest™

Load Balancing Administrator's Guide
April 29, 2005

100 Prospect Street, North Tower Stamford, Connecticut 06901 USA Telephone: (203) 964-3100 www.OutlookSoft.com

OutlookSoft Everest v4.2

Load Balancing

Copyright information
OutlookSoft, the OutlookSoft logos, and Everest are trademarks or registered trademarks of OutlookSoft Corporation. All other trademarks and logos are the property of their respective owners. ©2000 – 2005 OutlookSoft Corporation. All rights reserved.

© 2000-2005 OutlookSoft Corporation. All rights reserved.

Page 2

OutlookSoft Everest v4.2

Load Balancing

Table of Contents
Introduction .......................................................................................................................... 4 Before you begin ................................................................................................................... 4 Setting up network load balancing............................................................................................ 4 Setting up pooling.................................................................................................................. 5 Determining hardware setup ................................................................................................... 5

© 2000-2005 OutlookSoft Corporation. All rights reserved.

Page 3

OutlookSoft Everest v4.2

Load Balancing

Introduction
Everest supports load balancing using F5 and Cisco devices. This document describes the basic steps on configuring load balancing. It only details the specific settings that are required for Everest. Other settings may conform to system defaults or client requirements. In addition, we support Microsoft software load balancing and other hardware and software solutions, but these solutions have not been tested, nor do we provide guidance. This document is applicable to Everest version 4.1 and later. The following configurations are examples used in this document: • • • • • • Everest load balance virtual name: Everestloadbalanced.outlooksoft.com Everest load balance virtual IP address: 192.168.3.33 Web server 1 IP address: 192.168.0.1 Web server 2 IP address: 192.168.0.2 200 user workstations: 192.168.4.x (for example, 192.168.4.2 - 192.168.4.202) 200 user workstations: 192.168.5.x (for example, 192.168.5.2 - 192.168.5.202) All connections to Everest using the Admin interface must specify a named web server and NOT the load balanced virtual name or virtual IP address.

Note:

Before you begin
Before adding your network load balancing device to the physical network, you should determine your network scheme and document it. Knowing where all the components are physically located will determine how you set up load balancing, since there are several configuration options. For more information, see Determining hardware setup later in this document.

Setting up network load balancing
Before performing the following steps, determine the virtual IP address and virtual name for the web server. The IP address must be a valid network IP address that can be resolved by all client workstations. You can use the short name or a fully qualified domain name, based on client preference for name registration and name resolution. For example, when using Active Directory in a large enterprise, fully-qualified domain names are preferred. To set up network load balancing 1. Register/update the virtual IP address and virtual name on your network resolving services, for example, DNS, WINS, etc. Add the virtual IP address and virtual name to the load balancing device. You use a terminal interface to add each node (or server) that will be used in the load balance to the load balancer. You add each node by specifying its IP address and the services/ports that it will respond on. Each service/port that will be load balanced must be defined for each server.

2.

© 2000-2005 OutlookSoft Corporation. All rights reserved.

Page 4

OutlookSoft Everest v4.2

Load Balancing

3. 4.

Install Everest on all web servers using the virtual name or virtual IP address. See the Everest Installation Guide for more information. Set up pooling. See Setting up pooling later in this document for more information.

Setting up pooling
The pool manages all servers used in the load balancing. To set up pooling 1. 2. 3. 4. The first task when setting up the pool is to specify the system name used for the pool. Next, establish the load balancing method. Everest can support any type of load balancing method, however, ‘Round Robin’ is the most commonly used. Add each server on the specified service/port to the pool. Specify the ‘stickiness’ (or persistence) of the connection. There are many ways to configure connection ‘stickyness’, however, not all have been fully tested. We recommend you do the following, as it is a known configuration that provides full Everest functionality. a. b. Configure ‘stickiness’ based on source IP address. Set connection ‘stickiness’ to expire after 10 minutes. This ensures that all client connections from an individual workstation to Everest pass through the same web server for a period up to 10 minutes. If 10 minutes passes without a client connection from the individual workstation to the Everest server, the ‘sticky’ record will be dropped. You may want to configure the ‘stickiness’ of the connection based on the subnet address. Meaning that all traffic from 192.168.4.x will be routed to one web server, and all traffic from 192.168.5.x will be routed to a different web server. This approach will function correctly, however, if your user base is not evenly distributed across the two subnets, you may be putting more load on one web server that could be equally distributing over the two. While a 50 x 50 load distribution is not possible using persistence, the goal is to come as close as possible. If using Citrix, we recommend that you pay close consideration to the number of users that connect to each Citrix server. All connections from a Citrix server are viewed as one client workstation by a Cisco or F5 load balancer.

Note:

Note:

Determining hardware setup
Generally, you have two options for setting up the network load balancing device. The device can sit on the same physical subnet/network as the Everest servers, or it can be placed on another. Typically, network administrators prefer to place the load balancing device on a different network segment or VLAN in order to monitor/balance network traffic and for ease of maintenance. If the load balance device is not placed on the same network segment as the Everest web servers, a manual change may be required on each Everest Web Server in order to use the Everest Server Manager. To determine if the change is needed in your environment, perform the following test: Open a DOS dialog box on each Everest web server and ping the virtual name (or

© 2000-2005 OutlookSoft Corporation. All rights reserved.

Page 5

OutlookSoft Everest v4.2

Load Balancing

virtual IP address) being used for the Everest load balanced application. For example, select Start > Run > cmd, then Ping <Everestloadbalanced.outlooksoft.com>. If you do not receive a reply, it may be due to the network configuration. In this case, modify the HOST file (c:\windows\system32\drivers\etc for Windows 2003 servers, c:\winnt\system32\drivers\etc for pre-Windows 2003 servers), and following this example: Web Server 1 HOST file Web Server 2 HOST file <192.168.0.1 <192.168.0.2 Everestloadbalanced.outlooksoft.com> Everestloadbalanced.outlooksoft.com>

Additional support
If you have any questions about Everest load balancing, please contact an authorized OutlookSoft technical services representative.

© 2000-2005 OutlookSoft Corporation. All rights reserved.

Page 6

Sponsor Documents

Or use your account on DocShare.tips

Hide

Forgot your password?

Or register your new account on DocShare.tips

Hide

Lost your password? Please enter your email address. You will receive a link to create a new password.

Back to log-in

Close