Avaya P330 Load Balancing Manager User Guide March 2002
Avaya P330 Load Balancing Manager User Guide Copyright 2002 Avaya Inc. ALL RIGHTS RESERVED The products, specifications, and other technical information regarding the products contained in this document are subject to change without notice. All information in this document is believed to be accurate and reliable, but is presented without warranty of any kind, express or implied, and users must take full responsibility for their application of any products specified in this document.
Table of Contents Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi The Purpose of This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi Who Should Use This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi Organization of This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi Chapter 1 — Overview of Load Balancing. . . . . . . . . . . . . . . . . . . . . .
Table of Contents Logical View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22 Logical Tree Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22 Table Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23 RSG Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23 RS Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23 Form Area . . . . . . . . . . . . . . . . . . .
Table of Contents VLAN Area Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52 Mapping VLAN Areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53 Defining a Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55 Defining RSGs and RSs for Application Redirection . . . . . . . . . . . . .56 Defining a Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56 Using Address Wildcards . . . . . . . .
Preface Welcome to Avaya P330 Load Balancing Manager. This chapter provides an introduction to this guide. It includes the following sections: • - A description of the goals of the guide. • - The intended audience of this guide. • Organization of This Guide - A brief description of the subjects contained in the various sections of this guide. The Purpose of This Guide This guide contains the information needed to use Avaya P330 Load Balancing Manager efficiently and effectively.
Preface • Configuring Server Load Balancing - This section describes how to configure Avaya P330 Load Balancing Manager to perform Server Load Balancing. • Configuring Application Redirection - This section describes how to configure Avaya P330 Load Balancing Manager to perform Application Redirection. • Real Server Groups and Real Servers - This section describes how to configure Real Server Groups and Real Servers for the various load balancing applications.
1 Overview of Load Balancing This section describes load balancing and includes the following topics: • What is Load Balancing - A general overview of load balancing. • Load Balancing Elements - A description of the conceptual load balancing elements. • Firewall Load Balancing (FWLB) - An overview of Firewall Load Balancing, including descriptions and configuration examples for routing and bridging firewalls.
What is Load Balancing Load balancing technology allows system administrators to replace single firewalls and servers with multiple firewall and server farms, achieving the following goals: • Improving resilience by removing single points of failure. • Improving performance by utilizing multiple units instead of a single one. This improves the scalability and maintainability of the firewalls and servers in the network.
Chapter 1 Load Balancing Elements There are several abstract load balancing elements: • Real Server (RS) - An RS is a physical server that is associated with a Real IP address. One or more RSs may belong to an RSG. • Real Server Group (RSG) - An RSG is a logical grouping of Real Servers used for load balancing. For example, for SLB, the load balancer distributes packets to Real Servers belonging to a specific RSG.
Firewall Load Balancing (FWLB) This section provides information about Firewall Load Balancing, including a general overview and detailed information about routing and bridging firewalls. FWLB Overview Firewall Load Balancing intercepts all traffic between the LAN and the WAN, and dynamically distributes the load among the available firewalls, based on FWLB configuration.
Chapter 1 Benefits of FWLB FWLB allows you to: • Maximize firewall productivity. • Scale firewall performance. • Eliminate the firewall as a single point of failure. Transparent Routing Firewalls For transparent FWLB, the load balancer receives a packet, makes a load balancing decision, and forwards the packet to a firewall. The firewall does not perform NAT on the packets; the source and destination IP addresses are not changed.
The load balancer enables you to route packets to a DMZ. A DMZ is a portion of the client’s network, apart from the client’s LAN, where remote access is allowed. After creating a DMZ, a third load balancer is installed to route packets to the DMZ. The following figure illustrates transparent FWLB with a DMZ. Figure 1-3. Transparent FWLB With DMZ Non-Transparent Routing Firewalls Non-transparent routing firewalls are firewalls that support dynamic NAT.
Chapter 1 In transparent FWLB, persistency is ensured by the load balancer. In non-transparent FWLB, the firewalls ensure persistency through NAT, and there is no need for the load balancer to intervene. The following figure illustrates non-transparent FWLB. Figure 1-4. Non-Transparent Firewall Load Balancing Bridging Firewalls Bridging firewalls are firewalls that do not perform forwarding at the IP address layer, but rather appear as transparent bridges.
The following figure illustrates bridging FWLB. Figure 1-5. Bridging Firewall Load Balancing VLAN 1 Firewall 1 LAN Load Balancer Load Balancer Access Router Internet Firewall2 VLAN 2 Server Load Balancing (SLB) This section provides information about Server Load Balancing, including a general overview and detailed information about SLB.
Chapter 1 Benefits of SLB SLB improves network performance by: • Minimizing server response time. • Maximizing server availability. • Increasing server utilization and network bandwidth. This is accomplished by balancing session traffic between the available servers, according to rules established during configuration. • Increasing reliability. If any server fails, the remaining servers continue to provide services seamlessly. • Increasing scalability.
Direct Server Return (Triangulation) Direct server return, or triangulation, is an additional implementation of SLB. In standard SLB, the load balancer intercepts traffic between the servers and clients in both directions. In triangulation, load balancing is performed only on traffic from the clients to the server. Traffic from the servers is returned to the client directly through a router without any need for load balancing intervention. For triangulation, the Real Servers must be specially configured.
Chapter 1 Benefits of AR By redirecting client requests to a local cache or application server, you can increase the speed at which clients access information and free up valuable network bandwidth. Application Redirection improves network performance by: • Providing faster client access to information. • Increasing effective network bandwidth. • Filtering traffic. • Directing only suitable traffic to the local cache. • Connecting and load balancing multiple caches.
The following figure illustrates Cache Redirection. Figure 1-7. Cache Redirection In this figure, the sequence of events is as follows: 1. The user issues an HTTP request. The source IP address is the user’s IP address and the destination IP address is the Web server’s IP address. 2. The load balancer routes the packet to the local cache. The packet still has the Web server’s IP address as its destination IP address. 3.
Chapter 1 Combination of Applications You can enable the P333R-LB to use various applications concurrently. For example, it is possible to configure the same P333R-LB to perform Server Load balancing for an Intranet web-server, Application Redirection for web traffic that is Internet-bound, and Firewall Load Balancing for traffic that is Internet-bound. In some cases, the same “type” of traffic can be given two different actions by the load balancer.
Round Robin Using Round Robin, the load balancer issues sessions to each RS in turn. The first RS in the group receives the first session, the second RS receives the next session, and so on. When all the RSs receive a session, the issuing process starts over with the first RS. Round Robin ensures that each RS receives an equal number of sessions. Hash Using the Hash metric, sessions are distributed to RSs using a predefined mathematical hash function.
Chapter 1 MinMiss Hash MinMiss hash distributes sessions to RSs in the same way as the Hash metric. However, MinMiss hash retains persistency even when an RS is removed from the group. When an RS fails or is removed, the load balancer does not change the position of all the RSs in the list. Instead, it redistributes the remaining RSs to the list entries freed by the failing RS. The following figure illustrates how persistency is retained when an RS becomes non-operational. Figure 1-9.
Health Check The load balancer constantly checks the RSs to ensure that each RS is accessible and operational. An RS that fails the health check is automatically removed from the load balancer’s internal list of currently available RSs, and traffic is redirected to other available RSs. There are several types of health check methods that the load balancer can use, including: • ICMP Ping - Each RS is periodically pinged. If no answer is received, the RS is not operational.
Chapter 1 Persistency is achieved by opening a new entry for a server group based on the following: • New entry on source IP address - All sessions from a specific source are directed to the same RS. This is useful for applications where client information must be retained on the RS between sessions. • New entry on destination IP address - All sessions to a specific destination are directed to the same RS.
2 Getting Started with Avaya P330 Load Balancing Manager This chapter provides instructions on how to start Avaya Load Balancing Manager and an overview of the user interface. It includes the following topics: • Starting Avaya Load Balancing Manager - Instructions on how to start Avaya P330 Load Balancing Manager. • The User Interface - An introduction to Avaya P330 Load Balancing Manager’s user interface.
Chapter 2 The User Interface The user interface consists of the following elements: • Menu Bar - Menus for accessing Avaya Load Balancing Manager functions (refer to Appendix A, Menus). • Toolbar - Toolbar buttons for accessing Avaya Load Balancing Manager functions. • Logical or Physical View - Depending on the tab selected, the application displays one of the two views. — Logical View - A logical representation of the network showing Virtual Servers and Services and their associated RSGs and RSs.
— Physical View - A physical representation of the P333R-LB devices in the network showing RSs and RSGs. The Physical View includes a Tree Area and a Form Area. The Form Area displays information related to the element selected in the Tree Area. The following figure shows the Physical View of the user interface, with its various parts labeled. Figure 2-2.
Chapter 2 Table 2-1. Toolbar Buttons (Continued) Buttons Description Menu Item Pastes a rule from the application clipboard. Edit > Paste Adds a new entity. Edit > Add Deletes the selected entity. Edit > Delete Opens the Find dialog box. Edit > Find Refreshes the current view from the device. Changes that were not applied or saved to the device are lost. Action > Refresh Applies current modifications to the device. Action > Send to Device Launches another device manager.
Logical View The Logical View displays a logical representation of the network. The Logical View includes the following areas (these areas are discussed in more detail below): • Logical Tree Area - Displays a hierarchical representation of the network. • Table Area - Displays various tables. • RSG Area - Displays RSGs. • RS Area - Displays RSs. • Form Area - Displays Properties Sheets. The various areas are synchronized.
Chapter 2 Table Area The Table Area displays information related to the selected item in the Logical Tree Area. Depending on which item is selected in the Logical Tree Area, the Table Area displays the Virtual Services Table, the Routing Table, the Rules List, or the Services List. RSG Area The RSG Area displays the RSGs that are related to the selected element in the Logical Tree Area or in the Table Area. RS Area The RS Area displays the RSs that are connected to the RSG selected in the RSG Area.
Virtual Form Area The Form Area displays the Properties Sheet of the element selected in the Physical Tree Area. Status Bar The Status Bar shows the communication status between Avaya Load Balancing Manager and a specific device in the network. The following table shows the possible communication statuses with their corresponding graphics, and gives a short explanation for each status. Table 2-2.
Chapter 2 Applied Changes After finalizing all configuration changes, the changes must be applied to the device. Applied changes affect the current configuration but are not saved when the device is reset. To apply the changes to the device: Click Send to Device. Or Select Action > Send to Device. The configuration changes are applied to the device. The applied changes remain in effect until the device is reset. When the device is reset, it is configured with the last committed configuration.
Searching for Load Balancing Components Avaya Load Balancing Manager allows you to search for RSs or RSGs in the Physical Tree Area. To search for a load balancing component: 1. Click Find. Or Select Edit > Find. The Find dialog box opens. Figure 2-3. Find Dialog Box 2. Enter the IP address of the RS or the name of the RSG to search for, and enter the RLB ID (the slot number of the load balancer module in the stack). 3. Click Find. Avaya Load Balancing Manager searches for the item.
3 Configuring Firewall Load Balancing This chapter provides instructions on how to configure Firewall Load Balancing (FWLB). It includes the following topics: • Firewall Load Balancing Configuration Overview - An overview of the steps involved in configuring FWLB. • Defining a Firewall Service - Instructions on how to define a firewall service. • Editing the Routing Table - Instructions on how to add and edit entries in the service’s Routing Table.
Firewall Load Balancing Configuration Overview Configuring Avaya P330 Load Balancing Manager for FWLB involves several steps. This section provides an overview of the entire process, and the following sections explain each step in detail. To configure Avaya P330 Load Balancing Manager to perform FWLB: 1. Define one or more firewall services (refer to “Defining a Firewall Service” on page 29). 2. Add and edit entries in the Routing Table (refer to “Editing the Routing Table” on page 30). 3.
Chapter 3 Defining a Firewall Service The first step in configuring FWLB is defining a firewall service. A firewall service is a Virtual Service for FWLB (refer to “Load Balancing Elements” on page 3). A firewall service may be a routing firewall service or a bridging firewall service. To define a firewall service: 1. In the Logical Tree Area, select FWLB from the load balancer module you are currently configuring. 2. Select Bridging or Routing, depending on the type of firewall you are configuring. 3.
Editing the Routing Table The Table Area displays the Routing Table when a firewall service is selected in the Logical Tree Area. The Routing Table displays destination and network mask information for the firewall service. Figure 3-1. Routing Table The following table lists the fields in the Routing Table and their descriptions: Table 3-1. Field Description Destination The destination network IP address of this route. An IP address of 0.0.0.0 denotes a default router.
Chapter 3 * Note: When the focus is on the Routing Table, the Properties Sheet displayed in the Form Area is not related to the selected entry in the Routing Table. Rather, the Properties Sheet is related to the firewall service that is selected in the tree. Defining RSGs and RSs for FWLB After you define a firewall service, you can define the RSGs that are connected to the service. The RSG Area displays the RSGs related to the firewall service selected in the Logical Tree Area.
Some fields in the Properties Sheet are Read Only and cannot be edited and other fields are Read/Write. Enter information in all the Read/Write fields. When you click Send to Device to apply the new configuration information to the device, the device updates the Properties Sheet’s Read Only fields with the correct information. The Form Area displays the Properties Sheet of the selected item in the area in focus.
Chapter 3 Routing Firewall Properties Sheet The following tables list the fields in the Routing Firewall Properties Sheet and their descriptions. Table 3-3. Routing Firewall Properties Sheet Fields Field Description Name A user-defined name for the service. Admin Status The user-defined status of the service. Available options are enable and disable. Operational Status The operational status of the service. This field is read only.
Bridging Firewall Properties Sheet The following tables list the fields in the Bridging Firewall Properties Sheet and their descriptions. Table 3-4. Bridging Firewall Properties Sheet Fields Field Description Name A user-defined name for the service. Admin Status The user-defined status of the service. Available options are: • Enable • Disable Operational Status The operational status of the service. This field is read only.
Chapter 3 2. Click Launch Or Select Tools > Launch. Avaya P330 Load Balancing Manager launches on the selected device. * Note: This feature is not available when you run Avaya P330 Load Balancing Manager from the Web.
4 Configuring Server Load Balancing This chapter provides instructions on how to configure Server Load Balancing (SLB). It includes the following topics: • Server Load Balancing Configuration Overview - An overview of the steps involved in configuring SLB. • Defining a Virtual Server - Instructions on how to define a Virtual Server. • Defining a Virtual Service - Instructions on how to define a Virtual Service. • Defining RSGs and RSs for SLB - Instructions on how to define RSGs and RSs.
Chapter 4 Server Load Balancing Configuration Overview Configuring Avaya P330 Load Balancing Manager for SLB involves several steps. This section provides an overview of the entire process, and the following sections explain each step in detail. To configure Avaya P330 Load Balancing Manager to perform SLB: 1. Define one or more Virtual Servers (refer to “Defining a Virtual Server” on page 38). 2. Define one or more Virtual Services (“Defining a Virtual Service” on page 39). 3.
Defining a Virtual Server The first step in configuring SLB is defining a Virtual Server. To define a new Virtual Server: 1. In the Logical Tree Area, select SLB from the load balancer module you are currently configuring. 2. Click Add. Or Select Edit > Add. A new Virtual Server is added to the tree. 3. Enter information about the new Virtual Server in the Properties Sheet. For more information about entering information in the Properties Sheet, refer to “Editing the Properties Sheets for SLB” on page 47.
Chapter 4 Defining a Virtual Service After you define one or more Virtual Servers, you can define related Virtual Services. The Table Area displays the Virtual Services Table when a Virtual Server is selected in the Logical Tree Area. To define a new Virtual Service: 1. In the Logical Tree Area, select the Virtual Server to which you want to add the new Virtual Service. 2. Click anywhere inside the Table Area so that the Table Area receives the focus. 3. Click Add. Or Select Edit > Add.
To modify an existing Virtual Service: 1. Select the service from the Virtual Services Table 2. Edit the information in the Properties Sheet. 3. You can create, edit, or delete the Virtual Service’s proxy IP addresses. For information on proxy IP addresses, refer to “Proxy IP Editor” on page 41. 4. You can create, modify, or delete the Virtual Service’s health check methods. For information on health check methods, refer to “Health Check Editor” on page 43. To delete a Virtual Service: 1.
Chapter 4 Proxy IP Editor The Proxy IP Editor allows you to configure new proxy IP addresses. To open the Proxy IP Editor: Select Tools > Proxy IP Editor. Or Click . The Proxy IP Editor opens. Figure 4-1. Proxy IP Editor The following table lists the fields in the Proxy IP editor and their descriptions: Table 4-1. Proxy IP Editor Fields Field Description Bank ID The bank identifier. Start IP The first IP address in the bank’s range. End IP The last IP address in the bank’s range.
Adding PIP Banks To add a new Proxy IP (PIP) bank: 1. Click . Or Select Edit > Add. A new line appears in the Proxy IP Editor. 2. Configure the PIP bank using the fields in the table. 3. Click . Or Select Action > Send to Device. The bank is added to the device. You can modify any PIP bank that is not currently enabled on the device. Modifying PIP Banks To modify a PIP bank: 1. Select the bank that you want to modify. 2. Edit the bank’s fields in the table. 3. Click .
Chapter 4 Health Check Editor The Health Check Editor allows you to create and configure health check methods. To open the Health Check Editor: Select Tools > Health Check Editor. Or Click . The Health Check Editor opens with one default entry for each health check method. Figure 4-2. Health Check Editor The Health Check Editor includes the following fields: HC Method - The type of the health check entry. HC ID - The ID number for the health check entry.
Adding Health Check Methods To add a health check method: 1. Click . Or Select Action > Add. The Add a New Health Check Entry dialog box opens. Figure 4-3. Add a New Health Check Entry Dialog Box 2. Select the HC Method to create. 3. Enter an HC ID. 4. Click OK. The health check method appears in the Health Check Editor and a Health Check Configuration form appears in the bottom half of the Health Check Editor. 5. Fill in the configuration properties for the health check method.
Chapter 4 Deleting Health Check Methods You can delete one or more Health Check entries. To delete Health Check entries: 1. Select the entry that you want to delete. — To select more than one entry, press CTRL while selecting additional banks. 2. Click Delete. Or Select Edit > Delete. An 3. Click appears next to the entry. . Or Select Action > Send to Device. The entry is deleted from the device. * Note: You cannot delete entries with a HC ID of 1.
HTTP Properties The following table lists the fields in the HTTP Health Check Configuration form and their descriptions: Table 4-3. HTTP Health Check Configuration Properties Field Description HC Method The type of the health check entry. HC ID The ID number for the health check entry. Port The port on which the health check is performed. HTTP Version The HTTP version. Possible versions include: • HTTP 1.0 • HTTP 1.1 HTTP Method The HTTP method used for the health check.
Chapter 4 Script Properties The following table lists the fields in the Script Health Check Configuration form and their descriptions: Table 4-4. Script Health Check Configuration Properties Field Description HC Method The type of the health check entry. HC ID The ID number for the health check entry. Port The port on which the health check is performed. Script Request A user specified script request. Script Expected Response The expected format of the script response.
Module Properties Sheet The following table lists the fields in the Module Properties Sheet and their descriptions. Table 4-5. Module Properties Sheet Field Description IP The IP address of the module. Name A user-defined name for the module. Type The module type. Contact The name of the person responsible for the module. Location The location of the module. SLB-AR Precedence The precedence order of the various load balancing applications.
Chapter 4 Virtual Server Properties Sheet The following table lists the fields in the Virtual Server Properties Sheet and their descriptions. Table 4-6. Virtual Server Properties Sheet Field Description Name A user-defined name for the server. Operational Status The operational status of the service. This field is read only. The possible values are: • Up - the paths are operational • Down - all paths through the firewall are not operational, or no paths are configured.
Table 4-7. Virtual Service Properties Sheet (Continued) Field Description Application The application protocol of the packets to which this service applies. Select an application from the drop-down list. You can customize application protocols using the Application Editor Tool. For more information about customizing application protocols, refer to Chapter 7, Application Editor Tool. RS Port The Real Server port to which this service is mapped. Metric The metric used in load balancing decisions.
5 Configuring Application Redirection This chapter of the on-line help provides instructions on how to configure Application Redirection. It includes the following topics: • Application Redirection Configuration Overview - An overview of the steps involved in configuring AR. • VLAN Area Mapping - Instructions on how to map a VLAN area. • Defining a Service - Instructions on how to define a service for AR. • Defining RSGs and RSs for Application Redirection Instructions on how to define RSGs and RSs.
Application Redirection Configuration Overview Configuring Avaya P330 Load Balancing Manager for AR involves several steps. This section provides an overview of the entire process, and the following sections explain each step in detail. To configure Avaya P330 Load Balancing Manager to perform Application Redirection: 1. Configure VLAN Area Mapping 2. Define one or more services (refer to “Defining a Service” on page 55). 3.
Chapter 5 Mapping VLAN Areas To map VLAN Areas: 1. Select a load balancing module from the Tree Area. 2. Select Tools > VLAN Area Mapping. The VLAN Area Mapping tool opens. Figure 5-1. VLAN Area Mapping 3. Select a VLAN. 4. Define the VLAN Area using the pull-down list box. 5. Click Or Select Action > Send to Device to apply the change. To discard unapplied changes: Click Or Select Action > Refresh. The following table lists the fields in the VLAN Area Mapping tool and their description: Table 5-1.
Table 5-1. VLAN Area Mapping Fields (Continued) Field Description VLAN Area The source from which packets on the selected VLAN originate: • Server - Packets arriving on the selected VLAN are routed to the ultimate destination. • Client - Packets arriving from the selected VLAN are routed to the RS.
Chapter 5 Defining a Service The first step in configuring AR is defining a service. To define a new service: 1. In the Logical Tree Area, select AR from the load balancer module you are currently configuring, and then select Services. The Table Area displays the Virtual Services Table. 2. Click anywhere in the Table Area so that the Table Area receives the focus. 3. Click Add. Or Select Edit > Add. A new row is added to the Virtual Services Table. 4.
Defining RSGs and RSs for Application Redirection After you define a service, you can define the RSGs that are connected to the new service. The RSG Area displays the RSGs related to the service selected in the Virtual Services Table. If no service is selected in the Virtual Services Table, no information is displayed in the RSG Area. The RS Area displays the RSs belonging to the RSG selected in the RSG Area. You can add or delete RSs for each RSG.
Chapter 5 The following table lists the fields in the Rules List and their descriptions: Table 5-2. Rules List Field Description Row Status The status of the entry in the Rules List. Possible values are: • New - The new rule is not yet applied to the device. • Deleted - The rule has been deleted but the change is not yet applied to the device. • Modified - The rule has been modified but the change is not yet applied to the device. • Updated - All changes to the rule are applied to the device.
Table 5-2. Rules List (Continued) Field Description Type The type of filter used for this rule. Available options are: • uni-directional - the filter works on either the incoming or outgoing interface. • bi-directional - the filter works on both the incoming and outgoing interface. Service The service to which the rule is mapped. Select a service from the pull-down list. Operational Status The operational status of the service. This field is read only.
Chapter 5 Using Address Wildcards Wildcards are used to mask all or part of a source or destination IP address. Using wildcards, you can create filters for IP addresses. A wildcard can also be used to mask specific bits of an IP address. This mask is used to specify which bits are used and which bits are ignored. If you specify Host, the wildcard is set to 0.0.0.0, and the entire address is used. If you specify Any, the wildcard is set to 255.255.255.255, and the IP address is ignored.
Module Properties Sheet The following tables list the fields in the Module Properties Sheet and their descriptions. Table 5-3. Module Properties Sheet Field Description IP The IP address of the module. Name A user-defined name for the module. Type The module type. Contact The name of the person responsible for the module. Location The location of the module. SLB-AR Precedence The precedence order of the various load balancing applications.
Chapter 5 AR Virtual Service Properties Sheet The following tables list the fields in the Virtual Service Properties Sheet and their descriptions. Table 5-4. Virtual Service Properties Sheet Field Description Name A user-defined name for the service. Admin Status The user-defined status of the service. Available options are: • Enable • Disable Operational Status The operational status of the service. This field is read only.
6 Real Server Groups and Real Servers This chapter describes how to configure Real Server Groups and Real Servers for load balancing. It includes the following topics: • Real Server Groups - Instructions on how to configure RSGs, including defining and deleting RSGs. • Real Servers - Instructions on how to configure RSs, including defining and deleting RSs. • Editing the RSG and RS Properties Sheets - Instructions on how to edit the RSG and RS Properties Sheets.
Chapter 6 Real Server Groups RSGs are displayed in both the Logical and Physical Views. In the Logical View, a graphical representation of the RSGs connected to the element selected in the Tree or Table Area is displayed in the RSG Area. In the Physical View, all RSGs and RSs are displayed in the Tree Area according to the load balancing application.
Defining a Connected RSG To define a new RSG in relation to other load balancing elements: 1. In the Logical View, select a Virtual Service from the Tree Area or Table Area. 2. Click anywhere inside the RSG Area so that the RSG Area receives the focus. 3. Click Add. Or Select Edit > Add. The Add Real Server Group dialog box opens. Figure 6-1. Add Real Server Group Dialog Box 4. Select Primary to create a primary RSG.
Chapter 6 Defining an Unconnected RSG To define an unconnected RSG: 1. In the Physical Tree Area, select RSGs. 2. Click Add. Or Select Edit > Add. The Create New Real Server Group dialog box opens. Figure 6-2. Create New Real Server Group Dialog Box 3. Enter the name of the new RSG, and click OK. A new RSG is added to the Physical Tree Area. 4. Enter information about the new RSG in the Properties Sheet.
To completely delete an RSG so that it is no longer available for configuration: 1. From the Physical Tree Area, select the RSG you want to delete. 2. Click Delete. Or Select Edit > Delete. The RSG is deleted. * Note: If an RSG is connected to other load balancing elements, completely deleting the RSG also deletes the RSG from any element it is connected to. Real Servers RSs are displayed in both the Logical and Physical Views.
Chapter 6 Defining an RS There are two ways to define an RS. You can define an RS for an existing RSG, or you can define an unconnected RS. When you define an RS for an existing RSG, you can use either the Logical View or the Physical View. Defining an RS for an RSG - Logical View To define a new RS for an existing RSG using the Logical View: 1. In the Logical View, select an RSG from the RSG Area. The RS Table opens in the RS Area. 2. Click anywhere in the RS Area so that the RS Area receives the focus.
6. Enter information about the new RS in the Properties Sheet. For more information about entering information in the Properties Sheet, refer to “Editing the RSG and RS Properties Sheets” on page 70. Defining an RS for an RSG Physical View To define a new RS for an existing RSG using the Physical View: 1. In the Physical Tree Area, select the RSG to which you want to add the RS. 2. Click Add. Or Select Edit > Add. The Add Real Server to Real Server Group dialog box opens. Figure 6-4.
Chapter 6 Deleting an RS There are two ways to delete an RS. You can delete an RS’s connection to an RSG, or you can completely delete the RS so that it is no longer available for configuration. If you completely delete the RS, it no longer appears in any RSG. To delete an RS’s connection to an RSG: 1. In the Logical View, select an RSG from the RSG Area, and then select the RS you want to delete from the RS Area. Or From the Physical Tree Area, select an RSG, and then select the RS you want to delete. 2.
Editing the RSG and RS Properties Sheets When you add a new RSG or RS, the Form Area displays the Properties Sheet of the new entity. For more information about using and editing the Properties Sheets, refer to “Editing the Properties Sheets for FWLB” on page 31. The following tables list the fields in the RSG and RS Properties Sheets. Real Server Group Properties Sheet The following table lists the fields in the RSG Properties Sheet and their descriptions. Table 6-1.
Chapter 6 Real Server Properties Sheet The following table lists the fields in the RS Properties Sheet and their descriptions. Table 6-2. Real Server Properties Sheet Field Description IP address The IP address of the Real Server. Admin Status The user-defined status of the server. Available options are: • Enable • Disable Oper Status The operational status of the server. This field is read only.
7 Application Editor Tool This chapter of the on-line help provides instructions on how to use the Application Editor Tool and how to customize application protocols. It contains the following topics: • Application Editor Tool Overview - An overview of the Application Editor Tool. • Using the Application Editor Tool - Detailed instructions on how to use the Application Editor Tool including adding, modifying, and deleting application protocols.
Chapter 7 Using the Application Editor Tool To open the Application Editor Tool: Click Application Editor. Or Select Tools > Application Editor. The Application Editor Tool opens. Figure 7-1. Application Editor Tool The following table lists the fields in the Application Editor Tool and their description: Table 7-1. Application Editor Tool Fields Field Description Name The name of the application protocol. Type The application type.
Adding Application Protocols To add a new application protocol: 1. Click Add. Or Select Edit > Add. A new protocol appears in the Application Editor Tool. 2. Define the application protocol using the fields in the table. Modifying an Application Protocol You can modify any user-defined application protocol. Predefined application protocols are not editable. To modify an application protocol: 1. Select the application protocol you want to modify. 2. Edit the application protocol's fields in the table.
Chapter 7 Applying Changes When Avaya P330 Load Balancing Manager is updated with the changes to the Application Protocols table, the Application drop-down list in the Virtual Service Properties Sheet for SLB and AR is updated. The changes are saved to a file on the desktop and are automatically loaded the next time you open Avaya Load Balancing Manager. Added protocols appear in the Application drop-down list, and deleted applications no longer appear in the Application drop-down list.
A Menus This appendix gives the menu structure of Avaya P330 Load Balancing Manager. File Menu Table A-1. File Menu Item Description Commit Saves configuration changes to the device. Edit Menu Table A-2. Edit Menu Item Description Cut Cuts a rule from the Rule List to the clipboard. Copy Copies a rule from the Rule List to the clipboard. Paste Pastes a rule from the clipboard into the Rule List. Add Adds a new entity. Delete Deletes the selected entity. Find Opens the Find dialog box.
Appendix A Table A-3. Actions Menu (Continued) Item Description Send to Device Applies current modifications to the device. Tools Menu Table A-4. Tools Menu Item Description Launch Launches another device manager. Application Editor Opens the Application Editor Tool. VLAN Area Mapping Opens the VLAN Area Mapping tool. Help Menu Table A-5. Help Menu 77 Item Description Help Topics Opens the help module contents page for information.
B Error Messages This appendix lists the error messages that appear in Avaya P330 Load Balancing Manager: • The current Properties Sheet contains illegal or missing information. Please fill the form correctly or delete it. • [view name] contains illegal or missing information. • A Group with an identical name already exists. • The Server IP Address is not valid. • The Server ID is not valid. • No Real Servers of this group's type are configured. • Launch action failed.
Index A Adding application protocols 74 connected RSGs 64 firewall services 29 RSGs 63 RSs 67 rules 56 services 39, 55 unconnected RSGs 65 Application Editor Tool overview 72 reports 75 using 73 Application protocols adding 74 applying changes 75 deleting 74 modifying 74 reports 75 Application Redirection (AR) benefits 11 Cache Redirection 11 configuring 51 overview 10 Applied changes 25 AR.
Index F Fields admin status 71 application 50, 61 applications precedence 48, 60 App-Redir enable/disable 32, 48, 60 client IP 57 client IP wildcard 57 contact 32, 48, 60 destination 30 failed health checks 71 FWLB enable/disable 32, 48, 60 hash key (Virtual Service) 50, 61 health check (bridging firewall) 34 health check (routing firewall) 33 health check (Virtual Service) 50, 61 interval 71 IP (module) 32, 48, 60 IP address 71 live servers 50, 61 location 32, 48, 60 Max Port 73 Min Port 73 my health chec
Index How to, continued launch another device manager 34 modify a firewall service 29 modify a rule 58 modify a service for AR 55 modify a Virtual Server 38 modify a Virtual Service 40 modify an application protocol 74 save changes 24 search for RSs and RSGs 26 start Avaya Load Balancing Manager 18 use the Application Editor Tool 73 use the toolbar buttons 20 L Launching another device manager 34 Load balancing elements 3 metrics 13 overview 2 Logical Tree Area 22 Logical View 22 M Menu bar 19 Menus 76 Act
Index RSG 63, continued definition 3 deleting 65 finding 26 Properties Sheet 70 RSG Area 23 Rule defining 56 deleting 58 modifying 58 S Searching for load balancing components 26 Server Load Balancing (SLB) benefits 9 configuring 36 direct server return 10 overview 8 triangulation 10 Service defining 55 deleting 55 modifying 55 Shortcuts 20 SLB.
