Page History

...

• When user add a new load balancing rule, CS would:
  1. Find a unused guest ip from existing guest ip pool for this network.
  2. Create an static NAT rule on the firewall, make every traffic go to the public ip(which is used for load balancing) redirect to this guest ip.
  3. Create an load balancing rule on the load balancer, using the guest ip above as the source ip(instead of public ip in the side-by-side mode).
  4. Thus all the traffic goes to the public ip, would be redirect to the load balancer's internal guest ip, finally reach the guest vms through load balancing policy on the load balancer.
• When user add a firewall rule(for the load balancing rules)
  1. Since the public ip is not used by load balancer in this mode, we can configure firewall rule on the firewall(which own the public ip) without any trouble.
• This design would result in every public ip used for load balancing rule consuming one public ip and one guest ip as well.
• The static nat rule connect firewall and load balancer won't show in the firewall table of CS, it's considered a part of implementation of load balancing rule itself.
• The "inline mode" is a property of network offering now. One F5 device can be used in "inline" network and "side-by-side" network at the same time.

...