Jump to content
Welcome to our new Citrix community!

F5 Ratio Member equilivent

William Olmstead

Recommended Posts

I am moving some IPs from an F5 load balancer that is setup as ratio member.  Is there an equivalent in the NetScaler ?


Ratio (member)

The Ratio (member) method can be used to load balance most connection types. When you configure the Ratio (member) load balancing method you should assign a ratio weight to each pool member that is proportional to the capacity of the server. The number of connections that each server receives over time is proportionate to the assigned ratio weight. Ratio (member) load balancing calculations are localized to each specific pool (member-based calculation), as opposed to the Ratio (node) method in which calculations are applied to all pools of which the node is a member.

Link to comment
Share on other sites

ADC uses wights as well for service bindings - see https://docs.citrix.com/en-us/citrix-adc/current-release/load-balancing/load-balancing-customizing/assign-weight-services.html
Beside this 'static' load balancing, ADC can do more dynamic load balancing based on real service node utilization https://docs.citrix.com/en-us/citrix-adc/current-release/load-balancing/load-balancing-customizing-algorithms.html and using content switch you can load balance traffic using custom calculations.

  • Like 1
Link to comment
Share on other sites

As Petr suggested, weighted load balancing is basically your ratio method. If connections are method set weights per service (or member in a service group) and set the lb method to LeastConnections (or other appropriate method).


For your weight service 100 and the other service 0, so you only hit the "0" service when the primary is donw. Weighted load balancing on the ADC doesn't really do that as your weighted service will still be hit a percentage of the time and not only in the primary is down state scenario. Instead, you can use backup vservers for primary/backup lb described below.


Use weighted load balancing when you want one service to get 2 or 3 times the traffic/capacity of other services and set the weights appropriately.


For primary/backup scenarios, you don't want to use a weighted load balancing scenario.

Instead use a lb vserver with one service (as the primary vserver) and the second lb vserver (non-addressable) with service 2 as the backup vserver.

Configure the primary lb vserver with a "backup vserver" (under Protection methods) in GUI with the designated backup lb vserver.

And the backup lb vserver and its service are only HIT when the the current lb vserver is DOWN.

But this is the preferred handling for your 100/0 weight scenario instead of weighted load balancing.


The other method for a more controlled failover between tiers of lb vservers, is Priority LB. There's a graphic in the GUI.  But useful when you want traffic to Load Balance to SErvers A and B only; but if BOTH are down, then fail over to partner servicers: C and D; and if that tier is down, go to Servers E-G (you can have more then two servers in each tier). Three failover tiers max.

It could accomplish the primary, backup too...but really is overkill for the scenario described.  Just mentioning it for reference for more complex scenarios.




  • Like 1
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Create New...