Per-Packet Load Balancing Examples - Juniper ACX1000 Configuration Manual

ACX Series Universal Access Router Configuration Guide

Per-Packet Load Balancing Examples

792
in the 32-bit offset. This may also be problematic because these protocols are seen as
a separate flow.
With M Series (with the exception of the M120 router) and T Series routers, the first
fragment is mapped to the same load-balanced destination as the unfragmented packets.
The other fragments can be mapped to other load-balanced destinations.
For the M120 router only, all fragments are mapped to the same load-balanced
destination. This destination is not necessarily the same as that for unfragmented packets.
By default, or if you include only the
interface index as well as the following Layer 3 information in the packet header to load
balance traffic:
Source IP address
Destination IP address
Protocol
By default, IP version 6 (IPv6) packets are automatically load-balanced based on the
following Layer 3 and Layer 4 information:
Source IP address
Destination IP address
Protocol
Source port number
Destination port number
Incoming interface index
Traffic class
Perform per-packet load balancing for all routes:
[edit]
policy-options {
policy-statement load-balancing-policy {
then {
load-balance per-packet;
}
}
}
routing-options {
forwarding-table {
export load-balancing-policy;
}
}
Perform per-packet load balancing only for a limited set of routes:
statement, the router uses the incoming
layer-3
Copyright © 2017, Juniper Networks, Inc.