Media Flow Controller Configuration Tasks (CLI)
Media Flow Controller Administrator’s Guide
66
Creating and Configuring Link Bonding and Static Routes (CLI)
Copyright © 2010, Juniper Networks, Inc.
See
Figure 6, “Direct Server Return,”
for illustration.
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.
Note!
The CLI lists several
options for bond <bond_interface> mode that are not supported. Only balance-rr
(“round robin”), balance-xor-4 (Non-LACP), and link-agg-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.
Note!
After 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
2
1
g015415
Client
Internet
Media
Flow
Controller
Client requests video over IP address
Server load balancer
makes LB decision.
Forwards to available
Media Flow Controller.
3
Media Flow Controller responds
directly to client. (Direct Server Return)
Server
load
balancer
Media
Flow
Controller
Summary of Contents for MEDIA FLOW CONTROLLER 2.0.4 -
Page 6: ...Media Flow Controller Administrator s Guide VI Copyright 2010 Juniper Networks Inc...
Page 24: ...LIST OF FIGURES XXIV Copyright 2010 Juniper Networks Inc...
Page 37: ...Copyright 2010 Juniper Networks Inc 37 PART 1 Media Flow Controller Administration...
Page 38: ...Media Flow Controller Administrator s Guide 38 Copyright 2010 Juniper Networks Inc...
Page 285: ...Copyright 2010 Juniper Networks Inc 285 PART 2 Media Flow Controller Command and MIB Reference...
Page 286: ...Media Flow Controller Administrator s Guide 286 Copyright 2010 Juniper Networks Inc...
