Configuring Link Bonding And Static Routes (Cli); Figure 6 Direct Server Return - Juniper MEDIA FLOW CONTROLLER 2.0.4 - ADMINISTRATOR S GUIDE AND CLI Administrator's Manual

Administrator’s guide and cli command reference
Table of Contents

Advertisement

Media Flow Controller Configuration Tasks (CLI)
See
Figure 6, "Direct Server Return,"
Media
Flow
Controller
Media
Flow
Controller
Figure 6
Direct Server Return

Configuring Link Bonding and Static Routes (CLI)

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.
After you have created the bonded interface, you can use the delivery protocol command to
assign it as a traffic interface and configure its listen port, if needed.
1. Create the bond interface with a name and specify a mode.
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. Add interfaces to bond; repeat as needed.
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.
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:
Mode:
Link Monitor Time:
Interfaces:
66
Creating and Configuring Link Bonding and Static Routes (CLI)
Server load balancer
2
makes LB decision.
Forwards to available
Media Flow Controller.
Server
load
balancer
yes
balance-rr
100
eth10
eth11
Media Flow Controller Administrator's Guide
for illustration.
Client requests video over IP address
Internet
directly to client. (Direct Server Return)
Note!
After you assign a traffic interface, Media
Copyright © 2010, Juniper Networks, Inc.
1
Media Flow Controller responds
3
Note!
The CLI lists several
Client

Advertisement

Table of Contents
loading

This manual is also suitable for:

Media flow controller 2.0.4

Table of Contents