|
LFI
(voice and CRTP) packets
|
All incoming packets on Q2 are treated as LFI packets
|
The following types of incoming packets are treated as LFI packets:
- Packets matching Q2 (default)
- Packets from ports configured as LFI ports
- Packets to queues other than Q2 that are configured as
LFI queues
Note: When CRTP is configured without MLPPP traffic traverses only
one link thus no load balancing is performed.
|
Traffic is divided into individual traffic flows, and packets
belonging to a flow traverse a single link to avoid packet-ordering
issues.
The link is selected based on a hash computed from the source
address, destination address, and protocol. If the IP payload is TCP
or UDP traffic, the hash also includes the source port and destination
port.
|
|
Non-LFI
(data) packets
|
All data packets, whether fragmented or not, are treated as
non-LFI packets and queued to the Q0s of constituent links.
(Packets smaller than the size specified in the fragmentation
threshold are not fragmented but are treated as non-LFI packets.)
|
The following types of packets are treated as non-LFI packets
and are queued to the Q0s of constituent links:
- Packets not matching Q2
- Packets from ports not configured as LFI ports
- Packets queued to queues not configured for LFI
- Packets that are not CRTP packets
|
All non-LFI packets are queued to the Q0s of constituent links
one by one in weighted round-robin fashion.
|