Static Load-Balancing Methods

LTM Load-Balancing Methods:
o Simple words load balancer is a network device that distributes traffic to other devices.
o A load balancer is a network device that distributing traffic to other network devices.
o Efficiently distributing incoming the network traffic across a group of backend servers.
o Performs three interrelated functions; monitoring hosts, acting as proxy & load balancing.
o Load balancing is essential part of F5 BIG-IP for automatic balancing and distributing traffic.
o Primary intent for load balancing is the same to provide higher availability of applications.
o The basic intent for load balancing is greater performance and better end-user experience.
o LTM has number of load-balancing options-different methods to distribute service requests.
o It is important to emphasize that requests are distributed between available servers only.
o Availability is determined by both monitors & management status of both node & member.
o There are several types of algorithms/methods an F5 can use depending on array of factors.
o LTM uses various types of algorithms to determine the server to which traffic will be sent.
o LTM, Load balancing methods fall into one of two distinct categories are static & dynamic.
Static Load-Balancing Methods:

o Static load balancing methods distribute incoming connections in a uniform manner.
o Static load balancing methods distribute incoming connections in predictable manner.
o The Static load balancing methods are regardless of load factor or current conditions.
o The Static load balancing methods do not take server performance in to consideration.
o Before processing client requests, F5 LTM does not check any parameters of the server.
Dynamic Load-Balancing Methods:

o Dynamic load balancing methods distribute connections by factoring in current conditions.
o Dynamic load balancing methods distribute connections when make load balance decision.
o The Dynamic load balancing methods does consider server performance into consideration.
o In the case of dynamic load balancing methods F5 LTM first checks the server performance.
1 | P a g e Created by Ahmad Ali E-Mail: ahmadalimsc@gmail.com , WhatsApp: 00966564303717

Static Load Balancing Methods:
Round Robin:
o This algorithm/Method is designed to equally distributed load across all the pool members.
o Round Robin load balancing method /algorithm is also the default load-balancing method.
o Round Robin load balancing method /algorithm is default & most commonly used method.
o Generally used when we have equal hardware such as Processor, CPU, RAM, and Memory.
o Round Robin load balancing is appropriate when all pool members have similar capacity.
o F5 Local Traffic Manager evenly distributes client request across all available pool member.

Ratio:
o This algorithm/Method allows to set ratio weights accordingly to capacity of real servers.
o In F5 LTM, traffic gets load balanced accordingly to the ratio weights set on the server.
o Ratio load balancing is desirable when all the pool members do not have uniform capacity.
o The Ratio method is appropriate to use if some of the members are powerful than other.
o Ratio is static method so, that server with highest ratio value will receive more request.
o Ratio load balancing is useful when pool members have varying the available capacity.
o For example, if a pool contains one fast server and three slower server’s ratio can be set.
o Suppose 3 servers, on each server ratios are assigned accordingly to hardware capability.
o If 1st server is assigned a ratio of 3 then 1st three connections go to that server and so on.
o This type of method is mostly used when our servers are not having similar capabilities.

Dynamic Load-Balancing Methods:
Least Connections:
o The Least Connections load balancing mode is a dynamic load balancing algorithm/Method.
o This method, requests are forward to server which has least number of open connections.
o Used when servers of similar capabilities such as same Processor, CPU, RAM and memory.
o This method consider the current connections count to decide where to send next request.
o Distributes connections to server that is currently managing the fewest open connections.
o If multiple servers are having the same amount of connections count, then F5 LTM do.
o Performs Round-Robin algorithm for servers which are having same amount of connection.
o Least Connection load balancing can be performed based upon node or pool member.
o BIG-IP LTM is not going to check the connections the server is having with other servers.
o It is only going to check the connections the F5 BIG-IP LTM is with Pool Members only.

Fastest:
o This method, any new request will go to server who’s processing L7 connections are fastest.
o OR next request goes to the server who is having least outstanding OSI Model L7 requests.
o Distributes new connections to node that currently has the fewest outstanding L7 requests.
o When a connection request is received, the member with fewest connections is chosen.
o Fastest uses the outstanding layer 7 request to decide where to send the next request.
o This type of algorithm is useful where nodes are distributed across separate networks.
o Useful in the environments, where nodes are distributed across different logical networks.
o It is useful for distributing traffic to pool members that may have varying response times.
o Fastest method/algorithm due to load that previous requests have placed on the system.
o The connections are distributed to pool members based upon the server response time.
o Fastest algorithm load balancing can be performed based upon node or pool member.

Observed:
o This algorithm/method is like ratio but here ratio is not manually assigned to the server.
o Observed algorithm is basically Ratio load balancing but with Ratio assigned by BIG-IP.
o Distributes traffic based upon the currently active L4 connections to each pool member.
o Ratio is calculate based upon total no of connection currently active on each pool member.
o The pool member with a smaller number of the connections will receive the higher ratio.
o The pool member with a greater number of the connections will receive lower ration.
o A pool member with a lower than the average connection count is assigned a ratio of 3.
o A pool member with a higher than the average connection count is assigned a ratio of 2.
o Servers with connections lower than average will give ratio of 3, higher give ratio of 2.
o F5 defines higher ratio to server who is having lower than the average layer 4 connections.
o And lower ratio to the server who is having higher than the average layer 4 connections.
o In this algorithm Load balancing can be done based upon pool member or node level.

Predictive:
o In this method, various things are measured before sending any request to the server.
o It measures time which server is taking to progress request or replying back to the client.
o Also calculates a dynamic ratio value based on the number of L4 connections to each server.
o Predictive method/algorithm is similar to Observed but assigns more aggressive value.

Dynamic Ratio:
o This method monitors almost all the server components like CPU, Memory and Processor.
o Dynamic Ratio does load balancing based upon the information gathered from servers.
o Suppose we have 3 servers and 1st server’s CPU is only utilized 30% and its memory 10%.
o Suppose we have 3 servers and 2nd server CPU is utilized 50% and its memory 30% utilized.
o And suppose the 3rd server out of 3 server’s CPU is utilized 60% and its memory 40% utilize.
o Accordingly, to these servers RAM & CPU calculations, F5-BIG-IP will assign ratios to server.
o 1st server is assigned ratio 3, where 2nd server is assigned ratio 2 & 3rd is assigned ratio 1.
o The ratio is assigned according to availability of server’s CPU, Memory and the Processor.
o Dynamic Ratio method or algorithm need to use performance monitor to find out value.
o In order to gather the information in this method need to install an agent on the servers.
o The agent can be SNMP Agent, WMI or it can be Real-Time Real Server to provide info.
o After gathering info, the performance monitor will assign a weight to each pool member.
o The pool member with higher weight will receive more connections than other member.
o In this method Load balancing can be done based upon pool members or node level.

Round Robin:
o This algorithm/Method is designed to equally distributed load across all the pool members.
o Round Robin load balancing method /algorithm is also the default load-balancing method.
o Round Robin load balancing method /algorithm is default & most commonly used method.
o Generally used when we have equal hardware such as Processor, CPU, RAM, and Memory.
o Round Robin load balancing is appropriate when all pool members have similar capacity.
o F5 Local Traffic Manager evenly distributes client request across all available pool member.

Through browser or through curl command send many request to virtual Server IP address.
Curl –s http://192.168.2.100?[1-100]

Ratio:
o This algorithm/Method allows to set ratio weights accordingly to capacity of real servers.
o In F5 LTM, traffic gets load balanced accordingly to the ratio weights set on the server.
o Ratio load balancing is desirable when all the pool members do not have uniform capacity.
o The Ratio method is appropriate to use if some of the members are powerful than other.
o Ratio is static method so, that server with highest ratio value will receive more request.
o Ratio load balancing is useful when pool members have varying the available capacity.
o For example, if a pool contains one fast server and three slower server’s ratio can be set.
o Suppose 3 servers, on each server ratios are assigned accordingly to hardware capability.
o If 1st server is assigned a ratio of 3 then 1st three connections go to that server and so on.
o This type of method is mostly used when our servers are not having similar capabilities.

First clear and Reset previous connections
Change Load Balancing Method to Ratio (Member) which is second Static method.

Change Server-1 Ratio to 10

Finally, three Server Load balancing method and Ratio are set.

Through browser or through curl command send many request to virtual Server IP address.
Curl –s http://192.168.2.100?[1-100]
Let’s Verify this time the servers get connections and request by Ratio set.
Let’s clear the connection for next lab.

Least Connections:
o The Least Connections load balancing mode is a dynamic load balancing algorithm/Method.
o This method, requests are forward to server which has least number of open connections.
o Used when servers of similar capabilities such as same Processor, CPU, RAM and memory.
o This method consider the current connections count to decide where to send next request.
o Distributes connections to server that is currently managing the fewest open connections.
o If multiple servers are having the same amount of connections count, then F5 LTM do.
o Performs Round-Robin algorithm for servers which are having same amount of connection.
o Least Connection load balancing can be performed based upon node or pool member.

Change the method on SSH-Pool from Round Robin to Least Connections (Member)
First let’s clear the connection counter.
Take SSH session to virtual Server 192.168.2.100 to verify Least Connection method.

Fastest:
o This method, any new request will go to server who’s processing L7 connections are fastest.
o OR next request goes to the server who is having least outstanding OSI Model L7 requests.
o Distributes new connections to node that currently has the fewest outstanding L7 requests.
o When a connection request is received, the member with fewest connections is chosen.
o Fastest uses the outstanding layer 7 request to decide where to send the next request.
o This type of algorithm is useful where nodes are distributed across separate networks.
o Useful in the environments, where nodes are distributed across different logical networks.
o It is useful for distributing traffic to pool members that may have varying response times.
o Fastest method/algorithm due to load that previous requests have placed on the system.
o The connections are distributed to pool members based upon the server response time.
o Fastest algorithm load balancing can be performed based upon node or pool member.

Let’s change Load balancing method to Fastest (Application) on SSH-Pool.
Before to test make sure on SSH-Pool Reset and clear the connection counter.
In this case Server-1 response faster that’s why all three connection get by Server-1

Observed:
o This algorithm/method is like ratio but here ratio is not manually assigned to the server.
o Observed algorithm is basically Ratio load balancing but with Ratio assigned by BIG-IP.
o Distributes traffic based upon the currently active L4 connections to each pool member.
o Ratio is calculate based upon total no of connection currently active on each pool member.
o The pool member with a smaller number of the connections will receive the higher ratio.
o The pool member with a greater number of the connections will receive lower ration.
o Servers with connections lower than average will give ratio of 3, higher give ratio of 2.
o F5 defines higher ratio to server who is having lower than the average layer 4 connections.
o And lower ratio to the server who is having higher than the average layer 4 connections.

Let’s change Load Balancing method to Observed on SSH-Pool.
Before test in the Lab let’s clear and reset the Connection counter.
Let’s verify the Local Traffic Connection method used Observed.

Predictive:
o In this method, various things are measured before sending any request to the server.
o It measures time which server is taking to progress request or replying back to the client.
o Also calculates a dynamic ratio value based on the number of L4 connections to each server.
o Predictive method/algorithm is similar to Observed but assigns more aggressive value.

Dynamic Ratio:
o This method monitors almost all the server components like CPU, Memory and Processor.
o Dynamic Ratio does load balancing based upon the information gathered from servers.
o Suppose we have 3 servers and 1st server’s CPU is only utilized 30% and its memory 10%.
o Suppose we have 3 servers and 2nd server CPU is utilized 50% and its memory 30% utilized .
o And suppose the 3rd server out of 3 servers CPU is utilized 60% and its memory 40% utilize.
o Accordingly, to these servers RAM & CPU calculations, F5-BIG-IP will assign ratios to server.
o 1st server is assigned ratio 3, where 2nd server is assigned ratio 2 & 3rd is assigned ratio 1.
o The ratio is assigned according to availability of servers CPU, Memory and the Processor.
o Dynamic Ratio method or algorithm need to use performance monitor to find out value.
o In order to gather the information in this method need to install an agent on the servers.
o The agent can be SNMP Agent, WMI or it can be Real-Time Real Server to provide info.
o After gathering info, the performance monitor will assign a weight to each pool member.
o The pool member with higher weight will receive more connections than other member.
o In this method Load balancing can be done based upon pool members or node level.

First let’s add a new Windows XP server to the backend Severs.
Let’s enable SNMP_DCA Health Monitor in Default Monitor under Nodes.

Let’s Verify SNMP_DCA Health Monitor is enable under new Windows XP system.
Install Management and Monitoring Tools in Windows XP for SNMP Services.

Navigate to Services>SNMP Services properties and verify Community name is public.
Community is public by default in F5 LTM SNMP_DCA monitor.

Let’s verify Dynamic-Ratio in F5 LTM CLI type tmsh> list ltm node dynamic-ratio
Let’s change Load Balancing method to Dynamic Ratio (Member) under HTTP-Pool

Let’s send huge traffic to Virtual Server IP 192.168.2.100 98 connection has been received by
Windows XP server because of dynamic Ratio is 100.

Load Balancing by Pool Member VS Node:
o F5 BIG-IP Local Traffic Manger do load balancing by pool member or node.
o Node Load Balancing Total service for one IP (Internet Protocol) Address.
o Uses only IP address, considers all connections to server for all connections.
o Node Load Balancing Take all transactions for the IP address into account.
o Load Balancing Pool Member IP(Internet Protocol) Address and Service.
o Pool Member take decision-based transactions happening on service port.
o Only considers connections to the server for a specific port/application.
o Pool member uses IP address and specific service port (in the server pool).
Assuming all servers are currently available, if using Least Connections (Member) load balancing
and the open connection count is shown above in the diagram, Server 3 will receive the next
HTTP request which has minimum HTTP connection number 99 as compare to Server 1 and
Server 2.
Assuming all servers are currently available, if using Least Connections (Node) load balancing
and the open connection count is shown above in the diagram, Server 1 will receive the next
HTTP request which has minimum total HTTP and SSH connection number 109 as compare to
Server 2 and Server 3.
1 | P a g e Created by Ahmad Ali E-Mail: ahmadalimsc@gmail.com , Mobile: 00966564303717

Priority Group Activation:
o It is in F5 allows configuring the standby servers for the active servers in the pool.
o Standby Servers won’t receive the traffic from F5 until primary servers are running.
o Standby servers are auto activated once defined number of primary servers goes down.
o Priority Group Activation feature mainly used to provide a web page with maintenance.
o It is to clients when the number of primary servers was unavailable due to load etc.
o Priority Group Activation allows to configure multiple priority pool groups within pool.
o If priority group activation is set, F5 LTM will use available members with the highest.
o In F5 Local Traffic Manager Priority Group configured for pool member within the pool.
o In F5 Local Traffic Manager The default priority of pool members is assigned with 0 value.
o The pool member group which has the highest priority called as a primary priority group.
o The Pool member group other pool member group is called as a secondary priority group.
o By default, the pool member group with the highest priority will receive the traffic only.
o If the minimum number of pool members are not active in the highest priority group.
o Than secondary priority group will be activated in Local Traffic Manger to receive traffic.
o Once minimum number of pool members become active in the primary priority group.
o Then all new connection will be sent to primary priority group in Local Traffic Manager.
o The Priority group method is disabled by default connections are load-balanced based.
If you have 3 members that are active within a pool and you select round robin LB method and
set the priority group activation for less than 2, the virtual server is only going to use two of
three nodes to round robin.

Fallback Host:
o Another feature that you can configure within an HTTP profile is the HTTP redirection.
o LTM redirect request to fallback host when all members of targeted pool are unavailable.
o Also, the pool member is disabled, marked as down, or has exceeded its connection limit.
o When one or more pool members are unavailable redirect HTTP request to fallback host.
o Indicates HTTP error codes from server responses that should trigger redirection to fallback.
o The HTTP redirect could be to many alternate sites including an apology server or any links.
o It can be another virtual server on same system, or a virtual server in another data center.

Fallback Host Configuration:
Go to Main Tab >Local Traffic > Profiles >Services > HTTP >http then in Settings Fallback Host
type the Fallback host URL and hit Update button to save settings.
Now to test redirect is working or not, disable or turnoff all the backend Servers type Virtual
Server IP 192.168.114.200 in web browser it will redirect to www.google.com

Monitoring:
o A Monitor is a test that the LTM can perform on either a node of member.
o Monitors used to determine the status of real server means node or Pool Member.
o A monitor is a BIG-IP feature that verifies connections to pool members or nodes.
o If the real server doesn’t respond to The BIG IP LTM monitor, it will be taken offline.
o The F5 BIG-IP Local Traffic Manager (LTM) traffic will not be sent to this real server.
o The F5 Big-IP LTM system can monitor the health of the nodes and also the member.
o Monitors determine availability & performance of devices, links & services on network.
o Health monitors check availability, performance monitors check performance and load.
o If a monitored device, link, or service does not respond within a specified timeout period.
o The BIG-IP Local Traffic manager (LTM) system can redirect the traffic to another resource.
o In The BIG-IP Local Traffic Manager LTM Monitors gather information about your network.
o Information that Local Traffic Manager LTM monitors gather is available for you to view.
o In Simple words, Monitor is the test that Big-IP Local Traffic Manager (LTM) performed.
o The result of these test will define the status of respective node or member is available.
o The F5 Big-IP perform continues monitoring irrespective of the status of node or member.
o Monitor test devices to listen for specific port, expected response time, & set the interval.
o In Local Traffic Manager (LTM) monitor can be setup for assigned node, member and pool.
Methods of Monitoring:
o Three methods of monitoring: Simple Monitoring, Active Monitoring & Passive Monitoring.
Simple Monitoring:
o Simple Monitoring determines whether the status of a resource is up or down.
o Simple Monitoring just and only checks whether a host is reachable or offline.
o Simple Monitors do not monitor the pool members but only the node itself.
o The system contains three simple monitors, Gateway ICMP, ICMP & TCP_ECHO.
o Simple Monitors work well when only need to determine the up or down status.

Active Monitoring:
o In Active Monitoring sends some type of application traffic and waits for response.
o This can be done by using send and receive string configured under the monitor.
o F5 LTM makes node or Pool member offline, if it does not receive the response.
o It makes node or Pool member offline, if the response is not matching specific string.
o Example of Active Monitoring in Local Traffic Manager (LTM) are HTTP and FTP.
o Active Monitoring creates additional traffic and uses additional resources on F5 LTM.
o It is checks the status of a pool member or node on an ongoing basis as specified.
o If a pool member or the node does not respond within a specified timeout period.
o The BIG-IP LTM system can redirect the traffic to another pool member or the node.
o Each active monitor checks the status of a particular protocol, service, or application.
o HTTP monitor allows to monitor availability of HTTP service on pool, member, or node.
o WMI monitor allows to monitor performance of node that is running the WMI software.
o An active monitor can check for specific responses and run with or without client traffic.

Passive Monitoring:
o In Passive Monitoring BIG-IP does not sends any type of application traffic to know nodes.
o In Passive Monitoring BIG-IP does not send any type of application traffic to pool member.
o In BIG-IP Local Traffic Manager LTM Passive Monitoring is also known as Inband Monitoring.
o In Passive Monitoring, the BIG-IP LTM monitors the traffic is going to/from pool member.
o If Pool Member doesn’t respond to new or existing connections makes pool member offline.
o Main advantage of Passive Monitoring is it does not create any additional traffic to find out.
o Another advantage of Passive Monitoring is it does not consume more resources on F5 LTM.
o Passive Monitoring does not check for specific resources which make LTM slow to identity.
o Inband Monitor in BIG-IP Local Traffic Manager is only monitor used in Passive Monitoring.
o The Passive Monitor works depends on the client traffic from F5 LTM to Pool Member.
o Checks the health of a pool member based on a specified number of connection attempts.
o Check the health of data request attempts that occur within a specified time period.
o It mark pool member as down quickly, as long as there is some amount of network traffic.
Type of Monitoring:
o There are two types of Monitors used by BIG-IP Local Traffic Manager (LTM).
o Monitoring info is useful during troubleshooting and system maintenance.
Health Monitor:
o Health Monitor verifies particular resource is working or not in a specified time.
o If the resource is not available, then it does not forward the traffic to them.
o Checks resources to determine if they are up and functioning for a given service.
o Health Monitor is designed to report the status of a pool, pool member, or node.
o When marks pool, pool member, or node as down, it stops sending traffic to device.
Performance Monitor:
o Performance Monitor checks load and performance of a resource in the LTM.
o If the load is more on the resource , LTM forward the traffic to other resource.
o Gathers info about resources that system uses to dynamically load balance traffic.
o Server is monitor by performance monitor displays degradation in performance.
o LTM redirects traffic to other resources until performance of server returns to normal.
o The SNMP DCA monitor checks the current CPU, memory, and disk usage of a server.
o SNMP collection agent & then dynamically load balances traffic based on performance.

Address Check Monitors:
o An address check monitor provides a simple verification of an address on a network.
o Sends request to a virtual server when a response is received, the test is successful.
o When associated with node determines availability of all services associated with node.
o If monitor is unsuccessful marks node & all pool members at that IP address as Offline.
Gateway Uses Internet Control Message Protocol (ICMP) to make a simple resource
ICMP check. Check is successful if the monitor receives a response to an ICMP_ECHO.
ICMP Makes a simple node check. The check is successful if the monitor receives a
response to an ICMP_ECHO.
TCP Echo Verifies Transmission Control Protocol (TCP) connections. The check is
successful if the BIG-IP system receives a response to a TCP Echo message.

Address Check Monitor Node Specific:

Address Check Monitor Default Monitor:

Service Check Monitors:
o Determines whether service is available by opening a connection to IP and port.
o The Service checks only test whether the server is listening to respective port.
o In BIG-IP LTM the Service check monitor determines whether a service is available.
o This type of monitor opens a connection to an IP address and port, and then closes.
o When Transmission Control Protocol connection is established, the test is successful.
o When it is associated with pool members, it determines the availability of a service.
o If the monitor is unsuccessful the monitor marks the pool member as Offline in LTM.
o When Service Check Monitor offline member no requests are sent to pool member.
TCP Half Monitors the associated service by sending a TCP SYN packet to the service. As
Open soon as monitor receives SYN-ACK packet, the monitor marks the service as up.
UDP Verifies the User Datagram Protocol (UDP) service by attempting to send UDP
packets to a pool, pool member, or virtual server and receiving a reply.
Inband This monitor, when acting as a client, attempts to connect to a pool member. If
the pool member does not respond to a connection request after a user-specified
number of tries within a user-specified period, the monitor marks the pool
member as down. After the monitor has marked the pool member as down, and
after a user-specified period has passed, the monitor again tries to connect to the
pool member.

Service Check Monitor Members Specific:

Service Check Monitor Pool :

Content Check Monitors
o Determines whether service is available & whether server is serving appropriate content.
o In F5 BIG-IP LTM Content Check Monitor opens a connection to an IP address and port.
o Local Traffic Manager (LTM) Content Check Monitor then issues a command to the server.
o Local Traffic Manager response is compared to the Content Check monitor's receive rule.
o When a portion of the server's response matches the receive rule, the test is successful.
o Content Checks Monitor check whether the server is also serving the correct content.

Content Check Monitor Pool :

Content Check Monitor Member Specific:

Interactive Check Monitors:
o An Interactive check monitor interacts with servers by sending multiple commands.
o An Interactive check monitor interacts with servers and processing multiple responses.
o It is typically a custom monitor or external monitor that tests a specific application.
o For example, an FTP monitor connects, logs in by using the user ID and the password.
o Navigates to specific directory & then downloads specific file to the /var/tmp directory.
o If Interactive Check Monitor retrieved the file, it means the check & test is successful.
o LTM opens TCP connection to an IP address and port and logs in to the specific server.
o F5 BIG-IP Local Traffic Manager (LTM) receives the file and closes the TCP connection.

Interactive Check Monitor:

External Monitor:
o F5 BIG-IP LTM's external monitors are incredibly flexible, fairly easy to implement.
o Useful for monitoring applications for which there is no built-in monitor template.
o They give the ability to effectively monitor the health of just about any application.
o By writing custom scripts to interact with your servers in the same way users would.
o In BIG-IP an "External Monitor" is a script that is "external" to the configuration file.
o Contains logic designed to interact with servers to verify health of load balanced services.
o LTM runs a unique instance of the custom-crafted script against each pool member.
o The script logic formulates and submits a request (or requests) to the target pool member.
o Evaluates response & manages pool member's availability based on results of response.
o Using an External type of monitor in F5 BIG-IP LTM, you can create your own monitor type.
o Create a custom External-type monitor and within it, specify a user-supplied monitor to run.
o It is External Program setting that use to specify executable name of user-supplied monitor.
o An External-type monitor searches the directory /usr/bin/monitors for that monitor name.
o Arguments setting allows you to specify any command-line arguments that are required.
Go to Main > System > File Management > External Monitor Program List >Import , Import the
file from external system give it a name and click import.

Choose File browse to select external Script file in this case scr.txt file, type any name in this
case scr and click import button.
Now, go to Main > Local Traffic > Monitors > Create to create new External Monitor.
Now create External Monitor, provide name, description, type, Parent Monitor, interval,
timeout, external program which is name of the script imported if require arguments and
variable provide it.

Name Type the name of the monitor.
Description Specifies descriptive text that identifies the monitor.
Type Specifies the type of monitor.
Parent Monitor Specifies an existing monitor for the system to use for setting initial
values for the new monitor
Interval Specifies, in seconds, the frequency at which the system issues the
monitor check
Timeout Specifies the number of seconds the target has in which to respond to
the monitor request.
External Program Specifies the name of the file for the monitor to use
Arguments Specifies any command-line arguments that the script requires.
Variables Specifies any variables that the script requires.

Apply the external Monitor to Pool, in this case to HTTP-Pool, Go to Main > Local Traffic > Pools
>Pool List click on pool go to Configuration Health Monitors and apply External Monitor.
To verify open Wireshark in Windows XP and capture the pickets you will see F5 LTM which IP
address is 192.168.1.100 sending ICMP packet after every 5 second to monitor the server.
To very External Monitor is working or not off windows XP system, availability is Offline now.

Script Monitor:
o You can use the scripted component in F5 BIG-IP LTM to configure a custom monitor.
o You can use the default scripted monitor that the Local Traffic Manager provides.
o Use Scripted type of monitor to generate a simple script that reads a file that you create.
o The file contains send and expect strings to specify lines that you want to send or receive.
o External script itself should be a shell script (if at all possible) to minimize overhead.
o File contains send & expect strings to specify lines that want to send or expect to receive.
o Scripted Monitors use Expect method/"model" (send/expect) to determine a nodes health.
o Expect is a UNIX binary that sends a command and then expects are specific response back.
o Script Monitor file can be created in F5 BIG-IP location in this directory /usr/bin/monitors/

Default Monitor:
o Default Monitor only applied to the nodes that do not have any Specific Monitor.
o ICMP Monitor is most commonly used as default Monitor in the F5 BIG-IP LTM.
o Whatever the monitor assign will be assigned to all nodes configured on F5 LTM.
o Default Monitor can be configured under Local Traffic > Nodes > Default Monitor.
Objects Descriptions
Health Monitors Specifies the health monitors that monitor this node.
Active Specifies the health monitors that the system currently uses to
monitor this node.
Available Specifies the health monitors that are configured on the system,
and that you can use to monitor this node.
Availability Requirement Specifies, if you activate more than one health monitor
Update To apply the configure Health Monitors.

Node Specific Monitor:
o Node Specific Monitor allows you to configure monitor specifically to each node.
Can be configured under Main > Local Traffic > Nodes > Then select the node you want to
configure Health Monitor > Configuration > Health Monitors > Node Specific.
Health Monitors Specifies the health monitors that monitor this node.
monitor this node.
Available Specifies the health monitors that are configured on the system, and
that you can use to monitor this node.
Node Specific Specifies that system monitors this node with monitors configure

Pool Monitor:
o The health Monitor is assigned to the pools and all the members in the pool.
o Any new pool member added to pool automatically assigned with health monitor.
Configure under Main > Local Traffic > Pools > Then Select the pool you want to configure
health monitor > Health Monitor
Health Monitors Specifies an association between a health or performance monitor
and an entire pool, rather than with individual pool members.
<< and >> Use the Move buttons to adjust list membership.
Active Lists the health monitors that are already assigned to the pool.
Available Lists the health monitors that are available to add to the pool.

Member Specific Monitor:
o The Pool Monitor can be overridden by using member specific Monitor.
o It is possible to have different health monitors for different pool members.
o Each and every monitor is assigned at least two values Timeout & Interval.
Can be configured under Main > Local Traffic > Pools> Then select pool you want to configure
Health Monitor > Members > Pool Member > Change the configuration from Basic to Advanced
> Health Monitors > Member Specific.
Health Monitors Specifies the health monitors that the system uses to monitor this
pool member.
Member Specific To configure different health monitor for the individual pool member.
<< and >> Use the Move buttons to adjust list membership.
monitor this pool member.
Available Specifies the health monitors that are configured on the system, and
that you can use to monitor this pool member.

Test Monitor:
o The Test feature provides a way to test the monitors as they are being configured.
o To do so, you associate a test candidate such as node and port with the monitor.
o Click Test to run single-shot probe, and then view the returned results which display.
o Using Test provides method to correct monitor-configuration errors before deploying.
o In F5 BIG-IP Local Traffic Manager (LTM), that you can run only one test at a time.
o It offers health monitor test feature for verifying monitor settings on given target host.
o You have configured health monitor that is not assigned to pool, pool member, or node.
On the Main tab, go to Local Traffic > Monitors, Select the name of monitor you want to test,
Select Test tab, For Address, type the IP address and port number of the destination host.

Static Load-Balancing Methods

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Static Load-Balancing Methods

Uploaded by

Copyright:

Available Formats

LTM Load-Balancing Methods:

Static Load-Balancing Methods:

Dynamic Load-Balancing Methods:

1 | P a g e Created by Ahmad Ali E-Mail: ahmadalimsc@gmail.com , WhatsApp: 00966564303717

1 | P a g e Created by Ahmad Ali E-Mail: ahmadalimsc@gmail.com , WhatsApp: 00966564303717

2 | P a g e Created by Ahmad Ali E-Mail: ahmadalimsc@gmail.com , WhatsApp: 00966564303717

1 | P a g e Created by Ahmad Ali E-Mail: ahmadalimsc@gmail.com , WhatsApp: 00966564303717

2 | P a g e Created by Ahmad Ali E-Mail: ahmadalimsc@gmail.com , WhatsApp: 00966564303717

3 | P a g e Created by Ahmad Ali E-Mail: ahmadalimsc@gmail.com , WhatsApp: 00966564303717

4 | P a g e Created by Ahmad Ali E-Mail: ahmadalimsc@gmail.com , WhatsApp: 00966564303717

5 | P a g e Created by Ahmad Ali E-Mail: ahmadalimsc@gmail.com , WhatsApp: 00966564303717

1 | P a g e Created by Ahmad Ali E-Mail: ahmadalimsc@gmail.com , WhatsApp: 00966564303717

2 | P a g e Created by Ahmad Ali E-Mail: ahmadalimsc@gmail.com , WhatsApp: 00966564303717

1 | P a g e Created by Ahmad Ali E-Mail: ahmadalimsc@gmail.com , WhatsApp: 00966564303717

2 | P a g e Created by Ahmad Ali E-Mail: ahmadalimsc@gmail.com , WhatsApp: 00966564303717

Change Server-2 Ratio to 5

3 | P a g e Created by Ahmad Ali E-Mail: ahmadalimsc@gmail.com , WhatsApp: 00966564303717

4 | P a g e Created by Ahmad Ali E-Mail: ahmadalimsc@gmail.com , WhatsApp: 00966564303717

Let’s clear the connection for next lab.

5 | P a g e Created by Ahmad Ali E-Mail: ahmadalimsc@gmail.com , WhatsApp: 00966564303717

1 | P a g e Created by Ahmad Ali E-Mail: ahmadalimsc@gmail.com , WhatsApp: 00966564303717

First let’s clear the connection counter.

2 | P a g e Created by Ahmad Ali E-Mail: ahmadalimsc@gmail.com , WhatsApp: 00966564303717

1 | P a g e Created by Ahmad Ali E-Mail: ahmadalimsc@gmail.com , WhatsApp: 00966564303717

2 | P a g e Created by Ahmad Ali E-Mail: ahmadalimsc@gmail.com , WhatsApp: 00966564303717

1 | P a g e Created by Ahmad Ali E-Mail: ahmadalimsc@gmail.com , WhatsApp: 00966564303717

Let’s verify the Local Traffic Connection method used Observed.

2 | P a g e Created by Ahmad Ali E-Mail: ahmadalimsc@gmail.com , WhatsApp: 00966564303717

1 | P a g e Created by Ahmad Ali E-Mail: ahmadalimsc@gmail.com , WhatsApp: 00966564303717

1 | P a g e Created by Ahmad Ali E-Mail: ahmadalimsc@gmail.com , WhatsApp: 00966564303717

Let’s enable SNMP_DCA Health Monitor in Default Monitor under Nodes.

2 | P a g e Created by Ahmad Ali E-Mail: ahmadalimsc@gmail.com , WhatsApp: 00966564303717

Install Management and Monitoring Tools in Windows XP for SNMP Services.

3 | P a g e Created by Ahmad Ali E-Mail: ahmadalimsc@gmail.com , WhatsApp: 00966564303717

Community is public by default in F5 LTM SNMP_DCA monitor.

4 | P a g e Created by Ahmad Ali E-Mail: ahmadalimsc@gmail.com , WhatsApp: 00966564303717

5 | P a g e Created by Ahmad Ali E-Mail: ahmadalimsc@gmail.com , WhatsApp: 00966564303717

6 | P a g e Created by Ahmad Ali E-Mail: ahmadalimsc@gmail.com , WhatsApp: 00966564303717

1 | P a g e Created by Ahmad Ali E-Mail: ahmadalimsc@gmail.com , Mobile: 00966564303717

1 | P a g e Created by Ahmad Ali E-Mail: ahmadalimsc@gmail.com , Mobile: 00966564303717

1 | P a g e Created by Ahmad Ali E-Mail: ahmadalimsc@gmail.com , Mobile: 00966564303717

2 | P a g e Created by Ahmad Ali E-Mail: ahmadalimsc@gmail.com , Mobile: 00966564303717

1 | P a g e Created by Ahmad Ali E-Mail: ahmadalimsc@gmail.com , Mobile: 00966564303717

2 | P a g e Created by Ahmad Ali E-Mail: ahmadalimsc@gmail.com , Mobile: 00966564303717

3 | P a g e Created by Ahmad Ali E-Mail: ahmadalimsc@gmail.com , Mobile: 00966564303717

1 | P a g e Created by Ahmad Ali E-Mail: ahmadalimsc@gmail.com , Mobile: 00966564303717

2 | P a g e Created by Ahmad Ali E-Mail: ahmadalimsc@gmail.com , Mobile: 00966564303717

3 | P a g e Created by Ahmad Ali E-Mail: ahmadalimsc@gmail.com , Mobile: 00966564303717

1 | P a g e Created by Ahmad Ali E-Mail: ahmadalimsc@gmail.com , Mobile: 00966564303717

2 | P a g e Created by Ahmad Ali E-Mail: ahmadalimsc@gmail.com , Mobile: 00966564303717

3 | P a g e Created by Ahmad Ali E-Mail: ahmadalimsc@gmail.com , Mobile: 00966564303717

1 | P a g e Created by Ahmad Ali E-Mail: ahmadalimsc@gmail.com , Mobile: 00966564303717

2 | P a g e Created by Ahmad Ali E-Mail: ahmadalimsc@gmail.com , Mobile: 00966564303717

4 | P a g e Created by Ahmad Ali E-Mail: ahmadalimsc@gmail.com , Mobile: 00966564303717

1 | P a g e Created by Ahmad Ali E-Mail: ahmadalimsc@gmail.com , Mobile: 00966564303717

2 | P a g e Created by Ahmad Ali E-Mail: ahmadalimsc@gmail.com , Mobile: 00966564303717

1 | P a g e Created by Ahmad Ali E-Mail: ahmadalimsc@gmail.com , Mobile: 00966564303717

2 | P a g e Created by Ahmad Ali E-Mail: ahmadalimsc@gmail.com , Mobile: 00966564303717

3 | P a g e Created by Ahmad Ali E-Mail: ahmadalimsc@gmail.com , Mobile: 00966564303717

4 | P a g e Created by Ahmad Ali E-Mail: ahmadalimsc@gmail.com , Mobile: 00966564303717

5 | P a g e Created by Ahmad Ali E-Mail: ahmadalimsc@gmail.com , Mobile: 00966564303717

1 | P a g e Created by Ahmad Ali E-Mail: ahmadalimsc@gmail.com , Mobile: 00966564303717