F5 Logo MyF5
Search
  1. MyF5 Home
  2. Knowledge Centers
  3. BIG-IP LTM
  4. BIG-IP Local Traffic Manager: Concepts
  5. Dynamic Ratio Load Balancing
Manual Chapter : Dynamic Ratio Load Balancing

Applies To:

Show Versions Show Versions

BIG-IP LTM

  • 11.5.10, 11.5.9, 11.5.8, 11.5.7, 11.5.6, 11.5.5, 11.5.4, 11.5.3, 11.5.2, 11.5.1
Manual Chapter
Table of Contents | << Previous Chapter

Dynamic Ratio Load Balancing

Introduction to dynamic ratio load balancing

You can configure Dynamic Ratio load balancing for pools that consist of RealNetworks® RealServer™ servers, Microsoft® Windows® servers equipped with Windows Management Instrumentation (WMI), or any server equipped with an SNMP agent such as the UC Davis SNMP agent or Windows® 2000 Server SNMP agent.

To implement Dynamic Ratio load balancing for these types of servers, BIG-IP® Local Traffic Manager™ provides a special monitor plug-in file and a performance monitor for each type of server. The exception is a server equipped with an SNMP agent. In this case, the BIG-IP system provides the monitor only; no special plug-in file is required for a server running an SNMP agent.

Monitor plug-ins and corresponding monitor templates

Shows the required monitor plug-in and the corresponding performance monitor types.

Server Type Monitor plug-in Monitor Type
RealServer™ Windows® server F5RealMon.dll Real Server
RealServer UNIX server f5realmon.so Real Server
Windows server with WMI f5isapi.dll or F5Isapi64.dll or F5.IsHandler.dll WMI
Windows 2000 Server server SNMP agent SNMP DCA and SNMP DCA Base
UNIX server UC Davis SNMP agent SNMP DCA and SNMP DCA Base

Overview of implementing a RealServer monitor

For RealSystem® Server systems, the BIG-IP® system provides a monitor plug-in that gathers the necessary metrics when you have installed the plug-in on the RealSystem Server system. Configuring a RealSystem Server for Dynamic Ratio load balancing consists of four tasks:

  • Installing the monitor plug-in on the RealSystem Server system
  • Configuring a Real Server monitor on the BIG-IP system
  • Associating the monitor with the server to gather the metrics
  • Creating or modifying the server pool to use Dynamic Ratio load balancing

Installing the monitor plug-in on a RealSystem server system (Windows version)

Perform this task to install the monitor plug-in on a RealSystem Server system (Windows version).
  1. Download the monitor plug-in F5RealServerPlugin.dll from the BIG-IP® system. The plug-in is located in the folder /usr/local/www/docs/agents.
  2. Copy F5RealServerPlugin.dll to the RealServer plug-ins directory. (For example, C:\Program Files\RealServer\plug-ins.)
  3. If the RealSystem Server process is running, restart it.
Once the plug-in is installed and compiled, you must configure a Real Server monitor, associate the configured monitor with the node (a RealSystem Server server), and set the load balancing method to Dynamic Ratio.

Installing and compiling a Linux or UNIX RealSystem server monitor plug-in

Perform this task to install and compile a Linux or UNIX RealSystem Server monitor plug-in.
  1. Using the .iso image, burn a CD-ROM of the BIG-IP® system software.
  2. On the CD, navigate to the directory /downloads/rsplug-ins.
  3. Copy the file F5RealMon.src.tar.gz to the directory /var/tmp on the BIG-IP system.
  4. On the BIG-IP system, change to the directory /var/tmp:
    cd /var/tmp
  5. Use the UNIX tar command to uncompress the file F5RealMon.src.tar.gz:
    tar -xvzf F5RealMon.src.tar
  6. Change to the F5RealMon.src directory:
    cd F5RealMon.src
  7. Type the ls command to view the directory contents.
  8. To compile the source, use the instructions in the file build_unix_note.
  9. Start RealSystem Server.
Once the plug-in is installed and compiled, you must configure a Real Server monitor, associate the configured monitor with the node (a RealSystem Server server), and set the load balancing method to Dynamic Ratio.

Overview of implementing a WMI monitor

For Windows running Windows Management Instrumentation (WMI), the BIG-IP® system provides a Data Gathering Agent for the IIS server. Configuring a Windows platform for Dynamic Ratio load balancing consists of these tasks:

  • Installing the Data Gathering Agent on the IIS server.
  • Configuring a WMI monitor on the BIG-IP system.
  • Associating the monitor with the server to gather the metrics.
  • Creating or modifying the server pool to use the Dynamic Ratio load balancing method.
Important: To enable a user to access WMI metrics on a Windows server, you must configure the WMI monitor on the BIG-IP system correctly.

The procedure for installing the Data Gathering Agent on an IIS server differs depending on whether the server is running IIS version 5.0, 6.0, or 7.0, and whether the Data Gathering Agent is the file f5isapi.dll (or f5isapi64.dll) or the file F5.IsHandler.dll.

Tip: F5 Networks® recommends that you install only the Data Gathering Agent file that pertains to your specific configuration. Installing multiple Data Gathering Agent files could result in unwanted behavior.

IIS version support for the data gathering agent files

The procedure for installing the Data Gathering Agent on an IIS server differs depending on whether the server is running IIS version 5.0, 6.0, or 7.0, and whether the Data Gathering Agent is the file f5isapi.dll (or f5isapi64.dll) or the file F5.IsHandler.dll. This table shows each of the Data Gathering Agent files and the IIS versions that support each file.

Data Gathering Agent IIS version 5.0 IIS version 6.0 IIS version 7.0
f5isapi.dll (32-bit) f5isapi64.dll (64-bit) X X N/A
F5.IsHandler.dll (32-bit, 64-bit, and .NET) N/A X X

Installing the Data Gathering Agent f5Isapi.dll or f5isapi64.dll on an IIS 5.0 server

You can install the file f5isapi.dll or f5isapi64.dll on IIS versions 5.0 or 6.0.
Important: Do not install either of these files on IIS version 7.0 or 7.5. For IIS servers running version 7.0 or 7.5, install the file F5.IsHandler.dll instead.
Perform this task to install the Data Gathering Agent f5Isapi.dll or f5isapi64.dll on an IIS 5.0 server.
  1. Download the Data Gathering Agent (f5Isapi.dll or f5isapi64.dll) from the BIG-IP® system to the Windows platform. You can find this plug-in in either the /var/windlls or the /usr/local/www/docs/agents directory on the BIG-IP system.
  2. Copy f5isapi.dll or f5isapi64.dll to the directory C:\Inetpub\scripts.
  3. Open the Internet Services Manager.
  4. In the left pane of the Internet Services Manager, open the folder machine_name\Default Web Site\Script, where machine_name is the name of the server you are configuring. The contents of Scripts folder opens in the right pane.
  5. In the right pane, right-click f5isapi.dll or f5isapi64.dll, and select Properties. The Properties dialog box for f5isapi.dll or f5isapi64.dll opens.
  6. Clear Logvisits. (Logging of each visit to the agent quickly fills up the log files.)
  7. Click the File Security tab.
    The File Security options appears.
  8. In the Anonymous access and authentication control group box, click Edit.
    The Authentication Methods dialog box opens.
  9. In the dialog box, clear all check boxes, then select Basic Authentication.
  10. In the Authentication Methods dialog box, click OK to accept the changes.
  11. In the Properties dialog box, click Apply.
    The WMI Data Gathering Agent is now ready to be used.
Once you have installed the plug-in, you must configure a WMI monitor, associate the configured monitor with the pool member, and set the load balancing method to Dynamic Ratio.

Installing the Data Gathering Agent f5isapi.dll or f5isapi64.dll on an IIS 6.0 server

You can install the file f5isapi.dll or f5isapi64.dll on IIS versions 5.0 or 6.0.
Important: Do not install either of these files on IIS version 7.0 or 7.5. For IIS servers running version 7.0 or 7.5, install the file F5.IsHandler.dll instead.
Perform this task to install the Data Gathering Agent f5isapi.dll or f5isapi64.dll on an IIS 6.0 server.
  1. Create a scripts directory under the web site document root (C:\InetPub\wwwroot for Default Website).
  2. Set the properties of the scripts directory to scripts and executables.
  3. Copy the file f5isapi.dll or f5isapi64.dll to the created scripts directory.
  4. Start IIS manager (inetmgr) and navigate to the scripts directory.
  5. On the right pane, select the file name f5isapi.dll or f5isapi64.dll.
  6. Select Properties->File Security->Authentication and Access Control and ensure that the settings anonymous user and Basic Authentication are checked.
  7. If you want to allow all unknown extensions, then in IIS Manager, navigate to Web Server Extensions -> All Unknown ISAPI extensions and allow all unknown extensions. Otherwise, proceed to step 8.
  8. If you want to allow the file f5isapi.dll or f5isapi64.dll only, navigate to Web Server Extensions -> Tasks: Add a New Webserver Extension. Then:
    1. In the Name field, select F5 ISAPI and click Add for the required files. This requests a path to the file.
    2. Browse to the file f5isapi.dll or f5isapi64.dll, using the path C:\InetPub\wwwroot\scripts\f5isapi.dll for Default Website, and click OK.
    3. Check the Set Extension Status to Allowed box, and click OK. The value F5 ISAPI should now appear in the extensions list as Allowed.
Once you have installed the plug-in, you must configure a WMI monitor, associate the configured monitor with the pool member, and set the load balancing method to Dynamic Ratio.

Installing the Data Gathering Agent F5.IsHandler.dll on an IIS 6.0 server

You can install the file F5.IsHandler.dll on IIS versions 6.0 and 7.0.
Perform this task to install the Data Gathering Agent F5.IsHandler.dll on an IIS 6.0 server.
  1. Create a scripts directory under the directory C:\Inetpub. (C:\Inetpub\scripts).
  2. Create a \bin directory under the scripts directory (C:\Inetpub\scripts\bin).
  3. Set the properties of the scripts directory to scripts and executables.
  4. Copy the file F5.IsHandler.dll to the directory C:\Inetpub\scripts\bin.
    In the C:\Inetpub\scripts directory, create the file web.config. This example shows a web.config file on an IIS server running version 6.0. In the example, the path value f5isapi.dll, although appearing to be incorrect, is actually correct. It is the type value, F5.IsHandler, that directs the server to the correct file.
    <?xml version="1.0" encoding="UTF-8"?>
<configuration>
    <system.web>
        <httpHandlers>
            <clear />
            <add verb="*" path="f5isapi.dll" type="F5.IsHandler" />
        </httpHandlers>
    </system.web>
</configuration>
  5. From the Start menu, choose Control Panel and double-click Administration Tools.
  6. Double-click Internet Information Services.
    This opens the IIS Management Console.
  7. Expand the name of the local computer.
  8. Allow the file ASP.NET v2.0build_number :
    1. Select Web Server Extensions.
    2. Select ASP.NET v2.0build_number .
    3. Click Allow.
  9. Create a new virtual directory named scripts:
    1. Expand Websites and Default Web Site.
    2. Right-click Default Web Site, choose New, and choose Virtual Directory.
    3. Click Next.
    4. Type scripts for the alias and click Next.
    5. Type the directory you created in step 1 (C:\Inetpub\scripts\) and click Next.
    6. Click Next again.
    7. Click Finished.
  10. Create an application pool for the file F5.IsHandler.dll:
    1. Right-click Application Pools, choose New, and choose Application Pool.
    2. Type F5 Application Pool in the Application Pool ID box and click OK.
  11. Right click scripts and select properties.
  12. Set up the application pool:
    1. Click the Virtual Directory tab.
    2. From the Application Pool list, select F5 Application Pool.
  13. Set up the mappings:
    1. Click the Configuration button.
    2. On the Mappings tab of the Application Configuration screen, click Add.
    3. For the executable, type the file name C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\ aspnet_isapi.dll.
    4. For the file name extension, type .dll.
    5. Clear the box for Check that file exists and click OK.
    6. On the Application Configuration screen, click OK.
  14. Set up directory security:
    1. Click the Directory Security tab.
    2. Click the Edit button.
    3. Disable authentication by clicking the Anonymous Access and Integrated Windows box.
    4. Check the Basic Authentication box and click OK.
      Note: If you are not authenticating locally, you might need to set the default domain or realm.
  15. Set up the ASP.NET program:
    1. Click the ASP.NET tab.
    2. From the ASP.NET version list, select 2.0.buildnumber (for example 2.0.50727).
  16. On the scripts Properties page, click OK.
  17. Set up access to the IIS metabase:
    1. Run the command aspnet_regiis –ga <ASP.NETUsername>.
    2. See the web site http://support.microsoft.com/?kbid=267904.
Once you have installed the plug-in, you must configure a WMI monitor, associate the configured monitor with the pool member, and set the load balancing method to Dynamic Ratio.

Installing the Data Gathering Agent F5.IsHandler.dll on an IIS 7.0 server

Important: Do not install the files f5isapi.dll or f5isapi64.dll on IIS version 7.0.
Perform this task to install the Data Gathering Agent F5.IsHandler.dll on an IIS 7.0 server
  1. Create a scripts directory under the directory C:\Inetpub. (C:\Inetpub\scripts).
  2. Create a \bin directory under the scripts directory (C:\Inetpub\scripts\bin).
  3. Copy the file F5.IsHandler.dll to the directory C:\Inetpub\scripts\bin.
  4. In the C:\Inetpub\scripts directory, create the file web.config. This figure shows an example of web.config file on an IIS server running version 7.0. 
                        <?xml version="1.0" encoding="UTF-8"?>
                        <configuration>
                            <system.webServer>
                                <handlers>
                                    <clear />
                                    <add name="F5IsHandler" path="f5isapi.dll" verb="*" type="F5.IsHandler" modules="ManagedPipelineHandler" scriptProcessor="" resourceType="Unspecified" requireAccess="Script" preCondition="" />
                                </handlers>
                                <security>
                                    <authentication>
                                        <anonymousAuthentication enabled="false" />
                                    </authentication>
                                </security>
                            </system.webServer>
                       </configuration>
    Important: In this example, the path value f5isapi.dll, although appearing to be incorrect, is actually correct. It is the type value, F5.IsHandler, that directs the server to the correct file.
  5. Allow anonymous authentication to be overridden by using the appcmd command to set the override mode in the machine-level applicationHost.config file. 
                            appcmd set config "Default Web Site/scripts" 
                        /section:anonymousAuthentication /overrideMode:Allow 
                        /commit:APPHOST
  6. Set up a new application pool for the file F5.IsHandler.dll:
    1. From the Start menu, choose Control Panel.
    2. Choose Administrative Tools
    3. Choose Internet Information Services (IIS) Manager.
    4. From Connections, expand MachineName ( MachineName\UserName ).
    5. Right click the Application Pools menu and choose Add Application Pool.
    6. In the Name box, type F5 Application Pool.
    7. Click OK.
  7. Create a new application named scripts:
    1. Expand Web Sites and MachineName .
    2. Right-click MachineName and choose Add Application.
    3. In the Alias box, type scripts.
    4. To change the application pool, click Select.
    5. For the physical path, type the directory you created in step 1 (C:\Inetpub\scripts\).
    6. Click OK.
  8. Change the Authentication setting to Basic Authentication:
    1. Select scripts.
    2. In the center pane, double click Authentication.
    3. Verify that the status of all items under Authentication is Disabled, except for the Basic Authentication item. To enable or disable an authentication item, right click the name and choose Enable or Disable.
  9. Ensure that the bin directory and/or the webconfig files are removed from the hidden segments list.
  10. To view a list of hidden items, click the scripts application (see step 7), double-click Request Filtering, and click the Hidden Segments section.
Once you have installed the plug-in, you must configure a WMI monitor, associate the configured monitor with the pool member, and set the load balancing method to Dynamic Ratio.

Installing the Data Gathering Agent F5.IsHandler.dll on an IIS 7.5 server

Important: Do not install the files f5isapi.dll or f5isapi64.dll on IIS version 7.5. For IIS servers running version 7.5, always install the file F5.IsHandler.dll.
Perform this task to install the Data Gathering Agent F5.IsHandler.dll on an IIS 7.5 server
  1. Create a scripts directory under the directory C:\Inetpub (C:\Inetpub\scripts).
  2. Create a \bin directory under the scripts directory (C:\Inetpub\scripts\bin).
  3. Copy the file F5.IsHandler.dll to the directory C:\Inetpub\scripts\bin.
  4. In the C:\Inetpub\scripts directory, create the file web.config. 
    <?xml version="1.0" encoding="UTF-8"?>
                    <configuration>
                        <system.webServer>
                            <handlers>
                                <clear />
                                <add name="F5IsHandler" path="f5isapi.dll" verb="*" type="F5.IsHandler"
                                    modules="ManagedPipelineHandler" scriptProcessor="" resourceType="Unspecified"
                                    requireAccess="Script" preCondition="" />
                            </handlers>
                            <security>
                                <authentication>
                                    <anonymousAuthentication enabled="false" />
                                </authentication>
                            </security>
                        </system.webServer>
                        </configuration>
    Important: In the above example, the path value f5isapi.dll, although appearing to be incorrect, is actually correct. It is the type value, F5.IsHandler, that directs the server to the correct file.
  5. Allow anonymous authentication to be overridden by using the appcmd command to set the override mode in the machine-level applicationHost.config file. 
    appcmd set config "Default Web Site/scripts"
/section:anonymousAuthentication
/overrideMode:Allow /commit:APPHOST
    Note: appcmd is located in \windows\system32\intesrv.
  6. Set up a new application pool for the file F5.IsHandler.dll:
    1. From the Start menu, choose Control Panel.
    2. Choose Administrative Tools.
    3. Choose Internet Information Services (IIS) Manager.
    4. From Connections, expand MachineName ( MachineName\UserName ).
    5. Right click the Application Pools menu and choose Add Application Pool.
    6. In the Name box, type F5 Application Pool.
    7. Click OK.
    8. From the Application Pools list, right click F5 Application Pool and choose Advanced Settings.
    9. Under the Process Model List, click Identity, and then click the button to the right of ApplicationPoolIdentity.
    10. Click the drop down for Built-in account, and choose NetworkService.
    11. Click OK.
    12. Click OK.
  7. Create a new application named scripts:
    1. Expand Web Sites and MachineName .
    2. Right click MachineName and choose Add Application.
    3. In the Alias box, type scripts.
    4. Change the application pool, click Select, select F5 Application Pool from the Application Pool drop-down, and click OK.
    5. For the physical path, type the directory you created in step 1 (C:\Inetpub\scripts\).
    6. Click OK.
  8. Change the Authentication setting to Basic Authentication:
    1. Select scripts.
    2. In the center pane, double click Authentication.
    3. Verify that the status of all items under Authentication is Disabled, except for the Basic Authentication item. To enable or disable an authentication item, right click the name and choose Enable or Disable.
Once you have installed the plug-in, you must configure a WMI monitor, associate the configured monitor with the pool member, and set the load balancing method to Dynamic Ratio.
Table of Contents | << Previous Chapter
Contact Support Contact Support

Have a Question?

Support and Sales >

About F5

Education

F5 Sites

Support Tasks




©2023 F5 Networks, Inc. All rights reserved.


Trademarks Policies Privacy California Privacy Do Not Sell My Personal Information