Media Flow Controller Configuration Tasks : Basic (System) Configurations : Link Bonding, and Static Routes Options

Link Bonding, and Static Routes Options
Configure link bonding (aggregation), and static routes. Media Flow Controller supports three bonding modes:
balance-rr—”Round robin” mode. Sends TCP/IP packets belonging to the same session across multiple links. Out-of-order TCP packets coming through different links are retransmitted; supports load balancing and failover.
balance-xor-layer3+4— Traffic to a particular network peer goes across multiple links, although packets belonging to a single connection/session do not span multiple links; supports load balancing and failover. Link selection based on TCP port + IP address.
link-agg-layer3+4—Link Aggregation Control Protocol (LACP). Allows the automatic negotiation of port bundling to form a single logical channel between LACP-enabled links; supports load balancing and failover.
Media Flow Controller Load Balancing (LB) Direct Server Return (DSR) Guidelines
In order to implement DSR in Media Flow Controller, the following configurations are required.
Media Flow Controller must have the destination virtual IP address (VIP) configured on a loopback or a network interface that will not broadcast that IP address on the network.
Examples:
L4 LB + DSR: This is one of the most popular modes as it allows deployment with an inexpensive load balancer. DSR allows the return data (response) to go from Media Flow Controller to the client directly. This allows scaling from to 10Gbps with a relatively inexpensive LB. The LB itself need not scale to 10Gbps; as long as it has enough bandwidth to handle the rate of incoming requests, this provides a good solution.
L7 LB: DSR doesn't work in this case. The LB has to match the sum of the capacity of all the Media Flow Controllers to which the LB is load-balancing. However, rich L7 policies based on URI, header etc. can be built on LB, and traffic steering can be done in a more flexible way.
See Figure 6, “Direct Server Return,” next for illustration.
Figure 6 Direct Server Return
Configuring Link Bonding and Static Routes
Bond interfaces to create a port-channel or aggregated link for load distribution across links and increased link availability. Example shows bonding interfaces eth10 and eth11 as a named bonded interface “0”. In this way, layer 2 packets are distributed across the defined links for load distribution; if one of the links fail, the other links take over the media delivery. Once you have created the bonded interface, you can use the delivery protocol command to assign it as a traffic interface and set its listen port, if needed.
1.
Create the bond interface with a name and specify a mode. Note! The CLI displays several options for bond <bond_interface> mode that are not supported. Only balance-rr (“round robin”), balance-xor-layer3+4 (Non-LACP), and link-agg-layer3+4 (LACP) are supported modes.
bond <name_for_virtual_interface> mode <bond_mode>
2.
interface <interface_name> <virtual_interface_name>
3.
Assign the new bonded interface as a traffic interface and set non-default (80) listen ports, if needed; up to 64 ports can be assigned. Note! Once you assign a traffic interface, Media Flow Controller accepts traffic only on those assigned interfaces (up to 10); by default, Media Flow Controller accepts traffic on all interfaces.
delivery protocol http interface <bonded_interface_name>
delivery protocol http listen port <port> <port> <port>
Example:
test-vos (config) # bond 0 mode balance-rr
test-vos (config) # interface eth10 bond 0
test-vos (config) # interface eth11 bond 0
test-vos (config) # delivery protocol http interface bond 0 eth12 eth13
test-vos (config) # delivery protocol http listen port 80 81 82
test-vos (config) # show bonds
Bonded Interface 0:
Enabled: yes
Mode: balance-rr
Link Monitor Time: 100
Interfaces:
eth10
eth11
test-vos (config) #
4.
test-vos (config) # interface 0 <IP_address>
5.
Optionally, configure static routes and ensure a static host mapping for the defined hostname. Note ip route only works on devices that already have an IP address assigned. Use show ip route to verify.
ip route <network_prefix> {<netmask> | <mask_length>} {next_hop_IP_address | interface_name>}
ip map-hostname
Example:
test-vos (config) # ip route 123.45.10.0 /24 eth0
6.
service restart mod-delivery
Note! Bonded interfaces show Speed and Duplex as UNKNOWN in show interfaces output; this is not an error condition.

Report an Error
Media Flow Controller Administrator's Guide and CLI Command Reference
Copyright © 2010 Juniper Networks, Inc.