Creating And Configuring Link Bonding And Static Routes (Cli); Load Balancing (Lb) Direct Server Return (Dsr) Guidelines - Juniper MEDIA FLOW CONTROLLER 2.0.4 - ADMINISTRATOR S GUIDE AND CLI Administrator's Manual

Media Flow Controller Administrator's Guide
test-vos (config) # clock timezone America North United_States Pacific
2. Optionally, configure banners. There are two configurable banners: motd (message of the
day) and login. In the CLI, both are displayed at the command line when you log in; in the
Management Console, only the login message is displayed, on the login page. Multi-word
messages must be surrounded by quotes. Use show host and show banner to verify.
banner [login <message_string>] [banner motd <message_string>]
Example:
test-vos (config) # banner login "Welcome to Media Flow Controller"
test-vos (config) # banner motd "Please note new link bonding commands"

Creating and Configuring Link Bonding and Static Routes (CLI)

Media Flow Controller supports three bonding modes:
•
balance-rr
session across multiple links. Out-of-order TCP packets coming through different links are
retransmitted; supports load balancing and failover.
•
balance-xor-layer3+4
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
negotiation of port bundling to form a single logical channel between LACP-enabled links;
supports load balancing and failover.

Load Balancing (LB) Direct Server Return (DSR) Guidelines

In order to implement DSR in Media Flow Controller, the following configurations are required.
•
Server load balancer (SLB) and Media Flow Controller must be Layer 2 adjacent.
•
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.
•
Media Flow Controller must not GARP (gratuitous address resolution protocol) the VIP
address with its own MAC (media access control) address. You can disable ARP on a
Media Flow Controller interface with interface <interface_name> arp disable.
•
The return response from Media Flow Controller must bypass the SLB.
•
Response from Media Flow Controller routed to host not Layer 2 adjacent, via configured
route or gateway.
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 does not 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, and so forth. can be built on LB, and traffic steering can be done in
a more flexible way.
—"Round robin" mode. Sends TCP/IP packets belonging to the same
— Traffic to a particular network peer goes across multiple links,
—Link Aggregation Control Protocol (LACP). Allows the automatic
Creating and Configuring Link Bonding and Static Routes (CLI)
Media Flow Controller Configuration Tasks (CLI)
65