Media Flow Controller CLI Commands
Media Flow Controller Administrator’s Guide
342
(namespace) origin-server
Copyright © 2010, Juniper Networks, Inc.
rtsp
follow dest-ip [use-client-ip] |
<FQDN> [<port#>] [rtp-udp | rtp-rtsp]
Specify where Media Flow Controller should go to fetch content from origin upon a cache miss
(required). Use no namespace <name> origin-server to make changes. In Release 2.0.4,
you can configure only one origin server; however, you can configure multiple HTTP or NFS
origin servers via the server-map option (described). See
“Creating and Configuring Server-
Maps (CLI)” on page 79
for implementation details.
Notes:
•
http
—Use HTTP for origin-server delivery; multiple origin servers can be specified using
the
server-map
option.
•
absolute-url
—Derive the origin server from the absolute URL set against the
HTTP access method (GET, HEAD, and so forth). Use absolute-url to configure
Media Flow Controller as a mid-tier, proxy (if set, show namespace output has Proxy
Mode: forward). Media Flow Controller uses the absolute URL to contact the origin-
server. If absolute-url is configured and the incoming request (REQ header) does not
have the absolute URL, then the request is rejected with the appropriate error code.
•
follow
—Define alternate methods of determining which origin-server to use:
•
header
—Use a defined <header_name> in the request as the origin server. For
example, you could set follow header HOST, and the value of the HOST header in
the incoming request is used as the origin server. If the configured header does
not exist, the request is rejected. The <header name> can be any of the well-
defined headers OR a custom header. If set, show namespace output has Proxy
Mode: virtual.
Note!
In Release 2.0.4, only allowed value for header is host.
Optionally, set use-client-ip to use the client IP address in place of the origin
server’s IP address in the request.
•
dest-ip
—Use the destination IP address of the incoming request as the origin
server. Optionally, set use-client-ip to use the client IP address in place of the
origin server’s IP address in the request.
•
server-map
—A defined
server-map
. If set, show namespace output has Proxy
Mode: reverse.
Note!
You can specify more than one server-map only if they both are
either cluster-map or origin-escalation-map types; the order in which the maps are
added to the namespace determines the order in which they are read.
•
<FQDN/path>
—hostname/IP address/path; and (optional) port, default is 80. If set,
show namespace output has Proxy Mode: reverse.
•
nfs
—Use NFS for origin-server delivery; multiple origin servers can be specified using the
server-map
option.
•
server-map
—A defined
server-map
.
Note!
You can specify more than one server-
map only if they both are either cluster-map or origin-escalation-map types; the
order the maps are added to the namespace is the order in which they are read.
•
<FQDN:export_path>
—hostname/IP address:path; and (optional) port; default is 2049.
•
rtstp
—Use RTP/RTSP for origin-server delivery.
•
follow dest-ip
—Use the destination IP address of the incoming request as the
origin server. Optionally, set use-client-ip to use the client IP address in place of the
origin server’s IP address in the request.
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...
