Here you will find some load balancer policies predefined by LCOS that can be used under 2.8.10.2.16 LB-Policy or 2.70.5.2.12 LB-Policy.
Note: Note: This function only has an effect on routed data traffic. All internal services of the LANCOM router only use the ROUND-ROBIN policy.
- SNMP ID:
- 2.8.20.4
- Console path:
- Setup > IP-Router > Load-Balancer
- Possible values:
- DEFAULT
- This load balancer policy always has the same effect as not specifying a policy or leaving the LB-Policy column empty. In the firewall and in the command line ping, it triggers a fallback to the policy from table 2.8.20.2.13 LB-Policy. In table 2.8.20.2.13 LB-Policy, it triggers a fallback to the TRAFFIC selector.
- TRAFFIC
- This policy identifies the underlying physical connection for each channel and retrieves its absolute Rx load and Tx load from the columns Rx/s-average and Tx/s-average in . If the physical bandwidth is known for all these physical connections (typically for wired connections but not for mobile networks), it calculates the relative loads by dividing the absolute loads by the respective bandwidth. Otherwise, it continues to work with the absolute loads. In the next step, it selects the larger value between the Rx and Tx loads. It then selects the channel with the lowest load.
- BANDWIDTH
- The load balancer policy BANDWIDTH selects a channel randomly. If the bandwidth is known for all underlying physical connections, the probability of selecting a particular channel is proportional to its bandwidth, i.e., a 50 Mbps channel is selected five times more often than a 10 Mbps channel. Otherwise, if at least one bandwidth is unknown, the channel is selected uniformly at random.
- ROUND-ROBIN
- The load balancer policy ROUND-ROBIN selects the channels in turn.
- MOST-USED
- With this policy, the load balancer selects the channel that currently has the most firewall sessions (regardless of whether in the send or receive direction and regardless of whether IPv4 or IPv6). This policy only makes sense as a counterpart to Dynamic Path Selection, i.e. if a branch device on the load balancer uses Dynamic Path Selection, then the head office should use MOST-USED on its associated load balancer. This effectively means that the head office adapts to the Dynamic Path Selection decisions of the branch office without the branch office having to explicitly communicate its decision to the head office.
