Anyone know the load-balancing action for mpls traffic using the default
hash? Does the per-flow balancing see one-flow per label for outgoing
traffic? The Juniper documentation leads me to believe this but when I lab
it I get perfect load balancing using just one label when I send multiple IP
flows down the same LSP. I thought this was only possible when the hash-key
is set to look at the IP header with: (I have left out the inet config)
Forwarding-options {
hash-key {
family mpls {
label-1;
label-2;
payload {
ip;
}
}
}
Damon Pegg
Network Development
Easynet plc
t: 0207 900 7075
f: 0207 900 4443
m: 07931 406206
e: damon.pegg@uk.easynet.net
w: www.easynet.com
hash? Does the per-flow balancing see one-flow per label for outgoing
traffic? The Juniper documentation leads me to believe this but when I lab
it I get perfect load balancing using just one label when I send multiple IP
flows down the same LSP. I thought this was only possible when the hash-key
is set to look at the IP header with: (I have left out the inet config)
Forwarding-options {
hash-key {
family mpls {
label-1;
label-2;
payload {
ip;
}
}
}
Damon Pegg
Network Development
Easynet plc
t: 0207 900 7075
f: 0207 900 4443
m: 07931 406206
e: damon.pegg@uk.easynet.net
w: www.easynet.com