Selective dynamic load-balancing policies
Selective dynamic load balancing allows you to specify which traffic should or should not use the dynamic load-balancing (DLB) mechanism. Specific types of RDMA traffic, or general traffic being sent to the same DLB prefixes, may not react well to the configured DLB mode. A selective DLB policy provides a mechanism to match this type of traffic and specify an alternate way of forwarding the traffic.
See the SR Linux Routing Protocols Guide for information about dynamic load balancing.
In a selective DLB policy, a policy-forwarding rule can match specific RDMA write operations, identified via destination prefix (optional), protocol (to match UDP), destination port (to identify RDMA traffic), RDMA-OpCode and DSCP value (optional), then specify an action to use static or dynamic ECMP load-balancing.
A selective DLB policy supports the following match condition:
-
rdma-opcode– a single value or range indicating one or more RDMA OpCodes. Whenrdma-opcodeis specified in a selective DLB policy, the following can also be specified in the policy:- Destination IPv4/v6 address prefix
- Protocol (UDP)
- Destination port number
- DSCP value
A selective DLB policy supports the following actions:
static– matching traffic uses static ECMP load balancing, not DLB.dynamic– matching traffic uses flowlet-based DLB.
If no action is specified in a selective DLB policy, the ECMP load balancing option in
system.load-balancing.dynamic.default-load-balancing is used if configured.
See Configure the default system load-balancing behavior.