Applies To:

Show Versions Show Versions

Manual Chapter: Configuring Dynamic Ratio Load Balancing
Manual Chapter
Table of Contents   |   << Previous Chapter

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 ManagerTM 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.
You must install the monitor plug-in on each server to be monitored, and you must create a performance monitor that resides on the BIG-IP system. Once you have created a monitor, the monitor communicates directly with the server plug-in. For each server type, Table A.1 shows the required monitor plug-in and the corresponding performance monitor types.
f5isapi.dll or
F5Isapi64.dll or F5.IsHandler.dll

UC Davis SNMP agent
SNMP DCA and SNMP DCA Base

SNMP DCA and SNMP DCA Base
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:
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.)
1.
Using the .iso image, burn a CD-ROM of the BIG-IP system software.
2.
3.
Copy the file F5RealMon.src.tar.gz to the directory /var/tmp on the BIG-IP system.
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:
7.
Type the ls command to view the directory contents.
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.
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. For more information, see the procedures in this section.
Associating the monitor with the server to gather the metrics.
To associate the custom monitor with the node, see Chapter 3, Nodes.
Creating or modifying the server pool to use the Dynamic Ratio load balancing method. To set the load balancing method on the pool to the Dynamic Ratio method, see Chapter 4, Pools.
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. Table A.2 shows each of the Data Gathering Agent files and the IIS versions that support each file.
f5isapi.dll (32-bit)
f5isapi64.dll (64-bit)
F5.IsHandler.dll
(32-bit, 64-bit, and .NET)
The remainder of the section Implementing a WMI monitor contains the procedures for installing the Data Gathering Agent files f5isapi.dll (or f5isapi64.dll) and 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.
You can install the file f5isapi.dll or f5isapi64.dll on IIS versions 5.0, 6.0, and 7.0.
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.
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.
11.
In the Properties dialog box, click Apply.
The WMI Data Gathering Agent is now ready to be used.
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 wish to allow the file f5isapi.dll or f5isapi64.dll only, navigate to Web Server Extensions -> Tasks: Add a New Webserver Extension. Then:
a)
In the Name field, select F5 ISAPI and click Add for the required files.
This requests a path to the file.
b)
Browse to the file f5isapi.dll or f5isapi64.dll, using the path C:\InetPub\wwwroot\scripts\f5isapi.dll for Default Website, and click OK.
c)
Check the Set Extension Status to Allowed box, and click OK.
The value F5 ISAPI should now appear in the extensions list as Allowed.
To install the Data Gathering Agent f5isapi.dll or f5isapi64.dll on an IIS 7.0 server
1.
Create a scripts directory under the web site document root (C:\InetPub\wwwroot for Default Web Site).
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 add the scripts directory to Default Web Site.
5.
Under Features View, click Handler Mappings.
6.
Click Add Script Map, located on the right side of the screen.
7.
Configure the Add Script Map window with the following values:
Request path: f5isapi.dll (or f5isapi64.dll)
Executables: c:\inetput\scripts\f5isapi.dll (or f5isapi64.dll)
Name: F5isapi
8.
Click OK to save the changes.
9.
Click Yes in the window that asks you if you want to enable this ISAPI extension.
You can install the file F5.IsHandler.dll on IIS versions 6.0 and 7.0.
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.
5.
In the C:\Inetpub\scripts directory, create the file web.config. Figure A.1 shows an example of this file.
Figure A.1 Sample web.config file on an IIS server running version 6.0
7.
Double-click Internet Information Services.
This opens the IIS Management Console.
9.
Allow the file ASP.NET v2.0<build_number>:
a)
Select Web Server Extensions.
b)
Select ASP.NET v2.0<build_number>.
c)
Click Allow.
a)
Expand Websites and <Default Web Site>.
b)
Right-click <Default Web Site> , choose New, and choose Virtual Directory.
c)
Click Next.
d)
Type scripts for the alias and click Next.
e)
Type the directory you created in step 1 (C:\Inetpub\scripts\) and click Next.
f)
Click Next again.
g)
Click Finished.
a)
Right-click Application Pools, choose New, and choose Application Pool.
b)
Type F5 Application Pool in the Application Pool ID box and click OK.
You can now use the remaining steps to set up the Application Pool, Mappings, Directory Security, and ASP.NET to the scripts virtual directory.
12.
Right click scripts and select properties.
b)
From the Application Pool list, select F5 Application Pool.
a)
Click the Configuration button.
c)
For the executable, type the file name C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\
aspnet_isapi.dll.
e)
Clear the box for Check that file exists and click OK.
b)
Click the Edit button.
c)
Disable authentication by clicking the Anonymous Access and Integrated Windows box.
d)
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.
b)
From the ASP.NET version list, select 2.0.<buildnumber> (for example 2.0.50727).
17.
On the scripts Properties page, click OK.
a)
Run the command aspnet_regiis ga <ASP.NETUsername>.
b)
See the web site http://support.microsoft.com/?kbid=267904.
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.
Figure A.2 shows an example of this file.
<add name="F5IsHandler" path="f5isapi.dll" verb="*" type="F5.IsHandler" modules="ManagedPipelineHandler" scriptProcessor="" resourceType="Unspecified" requireAccess="Script" preCondition="" />
Figure A.2 Sample web.config file on an IIS server running version 7.0
5.
Allow anonymous authentication to be overridden by using the appcmd command to set the override mode in the machine-level applicationHost.config file. For example:
appcmd set config "Default Web Site/scripts" /section:anonymousAuthentication /overrideMode:Allow /commit:APPHOST
d)
From Connections, expand <MachineName> (MachineName\UserName).
f)
In the Name box, type F5 Application Pool.
g)
a)
Expand Web Sites and <MachineName>.
b)
Right-click <MachineName> and choose Add Application.
c)
In the Alias box, type scripts.
f)
8.
Change the Authentication setting to Basic Authentication:
a)
Select scripts.
c)
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.
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.
Figure B.3 shows an example of this file.
Figure A.3 Sample web.config file on an IIS server running version 7.5
5.
Allow anonymous authentication to be overridden by using the appcmd command to set the override mode in the machine-level applicationHost.config file. For example:
appcmd set config "Default Web Site/scripts" /section:anonymousAuthentication
Note: appcmd is located in \windows\system32\intesrv.
a)
From the Start menu, choose Control Panel.
b)
Choose Administrative Tools.
c)
Choose Internet Information Services (IIS) Manager.
d)
From Connections, expand <MachineName> (MachineName\UserName).
e)
Right click the Application Pools menu and choose Add Application Pool.
f)
In the Name box, type F5 Application Pool.
g)
h)
From the Application Pools list, right click F5 Application Pool and choose Advanced Settings.
i)
Under the Process Model List, click Identity, and then click the button to the right of ApplicationPoolIdentity.
k)
l)
a)
Expand Web Sites and <MachineName>.
b)
Right click <MachineName> and choose Add Application.
c)
In the Alias box, type scripts.
d)
Change the application pool, click Select, select F5 Application Pool from the Application Pool dropdown, and click OK.
f)
8.
Change the Authentication setting to Basic Authentication:
a)
Select scripts.
c)
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

Was this resource helpful in solving your issue?




NOTE: Please do not provide personal information.



Incorrect answer. Please try again: Please enter the words to the right: Please enter the numbers you hear:

Additional Comments (optional)