Juniper MEDIA FLOW CONTROLLER 2.0.4 - ADMINISTRATOR S GUIDE AND CLI Administrator's Manual page 342

Media Flow Controller CLI Commands
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
Maps (CLI)" on page 79
Notes:
•
—Use HTTP for origin-server delivery; multiple origin servers can be specified using
http
the server-map
•
absolute-url
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
•
•
•
server-map
Mode: reverse.
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>
show namespace output has Proxy Mode: reverse.
•
—Use NFS for origin-server delivery; multiple origin servers can be specified using the
nfs
server-map
•
server-map
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>
•
rtstp
•
follow dest-ip
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.
342 (namespace) origin-server
for implementation details.
option.
—Derive the origin server from the absolute URL set against the
—Define alternate methods of determining which origin-server to use:
—Use a defined <header_name> in the request as the origin server. For
header
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!
Optionally, set use-client-ip to use the client IP address in place of the origin
server's IP address in the request.
—Use the destination IP address of the incoming request as the origin
dest-ip
server. Optionally, set use-client-ip to use the client IP address in place of the
origin server's IP address in the request.
—A defined server-map. If set, show namespace output has Proxy
Note! You can specify more than one server-map only if they both are
—hostname/IP address/path; and (optional) port, default is 80. If set,
option.
—A defined server-map.
—hostname/IP address:path; and (optional) port; default is 2049.
—Use RTP/RTSP for origin-server delivery.
—Use the destination IP address of the incoming request as the
Media Flow Controller Administrator's Guide
In Release 2.0.4, only allowed value for header is host.
Note! You can specify more than one server-
"Creating and Configuring Server-
Copyright © 2010, Juniper Networks, Inc.