Interaction with other load balancing features

IPv6 flow label load balancing interacts with other load balancing features as follows:

• When the flow-label-load-balancing command is enabled on an interface and the global level l4-load-balancing command is also enabled, it applies to all IPv4 packets and to IPv6 packets with a flow label field of zero.

• The following global load-balancing commands apply independently to the corresponding non-IPv6 packet encapsulations:

  • lsr-load-balancing

  • mc-enh-load-balancing

  • service-id-lag-hashing

• When the flow-label-load-balancing command is enabled on an interface and the global load balancing l2tp-load-balancing command is enabled, it applies to the following situations:

  • packets received with L2TPv2 over UDP/IPv4 encapsulation

  • packets received with L2TPv3 over UDP/IPv4 encapsulation

  • packets received with L2TPv3 over UDP/IPv6 encapsulation if the flow label field is zero. Otherwise, flow label hashing applies.

  Packets received with L2TPv3 directly over IPv6 are not hashed on the L2TPv3 session ID. Therefore, hashing of these packets is based on the other interface level hash commands if the flow label field is zero. If the flow label is not zero, flow label hashing applies.

  Note: SR OS implementation of L2TPv3 supports UDP/IPv6 encapsulation only. However, third-party implementations may support L2TPv3 directly over IPv6 encapsulation.

• The global load-balancing command selects a different hashing algorithm and therefore applies all the time when enabled, including when the flow-label-load-balancing command is enabled on the interface: system-ip-load-balancing.

• When the flow-label-load-balancing command is enabled on an interface and the per-interface spi-load-balancing or teid-load-balancing commands are enabled, they apply to all IPv4 packets and to IPv6 packets with a flow label field of zero.

• The following per-interface load-balancing command applies independently to MPLS encapsulated packets: lsr-load-balancing

• The per-interface load balancing command, egr-ip-load-balancing and the flow-label-load-balancing command are mutually exclusive. The CLI enforces this exclusivity.

• The following per-LAG port packet spraying commands override the flow-label-load-balancing command. IPv6 packets, with a non-zero flow label value, are sprayed over LAG links according to the enabled LAG-spraying mode.

  • per-link-hash

  • link-map-profile