Media Flow Controller CLI Commands : namespace : (namespace) origin-server

(namespace) origin-server
namespace <name> origin-server
http
absolute-url
follow {dest-ip [use-client-ip] | header <header> [use-client-ip]}
server-map <map_name>
<FQDN/path> [<port>]}
nfs
server-map <name>
<FQDN:export_path> [<port>]
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.2, you can configure only one origin server; however, you can configure multiple HTTP or NFS origin servers via the server-map option (described below). See “Using namespace origin-server <protocol> server-map” on page 83 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, etc.). 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 set header doesn’t 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.2, 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.
FQDN—A hostname or IP address; and (optional) a port, default is 554. Optionally choose an RTP transport mechanism for MFD to use when fetching media data from the origin streaming server, either rtp-udp or rtp-rtsp (interleaved); default is to use what the client specifies.

Report an Error
Media Flow Controller Administrator's Guide and CLI Command Reference
Copyright © 2010 Juniper Networks, Inc.