16.03.2014 Views

Policy Framework Configuration Guide - Juniper Networks

Policy Framework Configuration Guide - Juniper Networks

Policy Framework Configuration Guide - 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.

Chapter 15: Traffic Forwarding and Monitoring <strong>Configuration</strong><br />

To generate a permuted index of next-hop entries for unicast and aggregate next hops,<br />

include the indexed-next-hop statement at the [edit forwarding-options load-balance]<br />

hierarchy level:<br />

indexed-next-hop;<br />

Configuring Per-Flow Load Balancing Based on Hash Values<br />

By default, the Junos OS uses a hashing method based only on the destination address<br />

to elect a forwarding next hop when multiple equal-cost paths are available. All Packet<br />

Forwarding Engine slots are assigned the same hash value by default.<br />

You can enable router-specific or switch-specific load balancing by configuring the router<br />

or switch to assign a unique, load-balance hash value for each Packet Forwarding Engine<br />

slot.<br />

NOTE: This feature is supported only on M120, M320, and MX Series routers.<br />

To configure per-flow load balancing. include the load-balance statement at the [edit<br />

forwarding-options] hierarchy level:<br />

[edit forwarding-options]<br />

load-balance {<br />

indexed-next-hop;<br />

per-flow {<br />

hash-seed;<br />

}<br />

}<br />

To enable per-flow load balancing, you must include the hash-seed statement. The Junos<br />

OS automatically chooses a value for the hashing algorithm. You cannot configure a<br />

specific value for the hash-seed statement when you enable per-flow load balancing.<br />

Configuring Routers, Switches, and Interfaces as DHCP and BOOTP Relay Agents<br />

You can configure the router, switch, or interface to act as a Dynamic Host <strong>Configuration</strong><br />

Protocol (DHCP) and Bootstrap Protocol (BOOTP) relay agent. This means that a locally<br />

attached host can issue a DHCP or BOOTP request as a broadcast message. If the router,<br />

switch, or interface sees this broadcast message, it relays the message to a specified<br />

DHCP or BOOTP server.<br />

You should configure the router, switch, or interface to be a DHCP and BOOTP relay<br />

agent if you have locally attached hosts and a distant DHCP or BOOTP server.<br />

To configure the router or switch to act as a DHCP and BOOTP relay agent, include the<br />

bootp statement at the [edit forwarding-options helpers] hierarchy level:<br />

[edit forwarding-options helpers]<br />

bootp {<br />

client-response-ttl number;<br />

description text-description;<br />

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

369

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

Saved successfully!

Ooh no, something went wrong!