delivery
309
Media Flow Controller Administrator’s Guide
Media Flow Controller CLI Commands
max-conn <number>
timeout <seconds>
connection [close use-reset | persistence num-requests <0 - 100>]
file-type <suffix> content-type <type>
interface {all | <interface> <interface> <interface> ...}
listen port {80 | <port> <port> <port> ...}
req-length maximum <bytes>
trace enable
Set content delivery options; choose either http (default port is 80), or rtsp (default port is
554). Two delivery protocol (one for http and one for rtsp) configurations are allowed. Not all
options are available for rtsp. Use no delivery protocol <protocol> <option> to reset to
default. Notes:
•
allow-req
—(http only) Media Flow Controller supports known HTTP methods (GET,
POST, TRACE, CONNECT, OPTIONS, DELETE, PUT) always; other HTTP access
methods, including custom methods, are supported via this option; up to 16 may be
added. Use all, to accept any request. The default, none, restricts access to only the
known HTTP methods as described.
•
conn-pool
—(http only). Set connection pooling (allows many HTTP requests to multiplex
over a single TCP connection to the origin) options:
•
max-arp-entry
—Set the maximum number of ARP entries in the ARP Cache Table
•
origin
—Set connection pooling to origin options:
•
disable
and
enable
—Either enable (default) or disable connection pooling to
the origin server.
•
max-conn
—Optionally, set a maximum number of connections that can be
opened to the origin server concurrently. Default is 256; maximum allowed is
2048.
•
timeout
—Optionally, set a timeout for a single connection in the connection
pool; maximum allowed is 86,4000 seconds (24 hours), default is 300 seconds.
This is separate from
network
connection idle timeout.
•
connection
—(http only). Set connection ...options:
•
close use-reset
—While closing the connection, issue a reset against the fin.
•
persistence
—Set the persistent number of HTTP requests allowed per connection.
•
file-type
to
content-type
match—(http only) Associate certain file-types (for
example, HTML, FLV, MP4, or MOV) with certain content-types (for example, text/html,
video/x-flv, video/mp4, or video/quicktime) to be set in the HTTP header. When HTTP is
used for access to origin, this command is needed only if a Content-Type header is not
returned by the origin server; this has no effect if the origin server returns a Content-Type
header. Repeat the command as needed to continue associating file types with content
types. Use no to delete a specified entry.
•
interface
—Specifiy the set of interfaces on which the media delivery protocol listens for
incoming requests. If not specified, Media Flow Controller listens on ALL interfaces
(default); if specified, Media Flow Controller listens ONLY on those specified. You can
specify a list of space-separated interfaces such as eth2 eth3 eth4 eth5 or eth10 eth11
eth12 eth13 eth20 eth21 eth22, and so on. Up to 10 can be specified. Use no and
specify the configured interfaces to reset the default (all), or remove a specified interface.
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...
