21.03.2013 Views

Junos® OS Ethernet Interfaces Configuration ... - Juniper Networks

Junos® OS Ethernet Interfaces Configuration ... - Juniper Networks

Junos® OS Ethernet Interfaces Configuration ... - Juniper Networks

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Configuring Symmetric Load Balancing on an 802.3ad LAG on MX Series Routers<br />

Copyright © 2012, <strong>Juniper</strong> <strong>Networks</strong>, Inc.<br />

You can specify whether symmetric hash or complement hash is done for load-balancing<br />

traffic. To configure symmetric hash, use the symmetric-hash statement at the [edit<br />

forwarding-options hash-key family inet] hierarchy level. To configure symmetric hash<br />

complement, use the symmetric-hash complement statement and option at the [edit<br />

forwarding-options hash-key family inet] hierarchy level.<br />

These operations can also be performed at the PIC level by specifying a hash key. To<br />

configure a hash key at the PIC level, use the symmetric-hash or symmetric-hash<br />

complement statement at the [edit chassis hash-key family inet] and [edit chassis hash-key<br />

family multiservice] hierarchy levels.<br />

Consider the example in Figure 14 on page 125.<br />

Figure 14: Symmetric Load Balancing on an 802.3ad LAG on MX Series<br />

Routers<br />

A<br />

MX-series router<br />

i1<br />

i2<br />

i3<br />

Intelligent Devices<br />

A<br />

A<br />

B<br />

MX-series router<br />

B<br />

B<br />

Forward traffic<br />

Reverse traffic<br />

Router A is configured with symmetric hash and Router B is configured with symmetric<br />

hash complement. Thus, for a given flow fx, post hash computation is from Router A to<br />

Router B through i2. The reverse traffic for the same flow fx is from Router B to Router A<br />

through the same i2 device as its hashing (done after swapping source and destination<br />

fields) and returns the same link index; since it is performed on the interchanged source<br />

and destination addresses.<br />

However, the link chosen may or may not correspond to what was attached to the DPI.<br />

In other words, the hashing result should point to the same links that are connected, so<br />

that the traffic flows through the same DPI devices in both directions. To make sure this<br />

happens, you need to also configure the counterpart ports (ports that are connected to<br />

same DPI-iN) with the identical link index. This is done when configuring a child-link into<br />

the LAG bundle. This ensures that the link chosen for a given hash result is always the<br />

same on either router.<br />

Note that any two links connected to each other should have the same link index and<br />

these link indices must be unique in a given bundle.<br />

Chapter 4: Configuring Aggregated <strong>Ethernet</strong> <strong>Interfaces</strong><br />

g017349<br />

125

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!