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

Administrator’s guide and cli command reference
Table of Contents

Advertisement

Media Flow Controller CLI Commands
live-pub-point
caching
receive-mode
status
match
precedence
break ties when namespaces are defined with the same match criteria. The lower the
precedence number, the higher the preference for that namespace; 0 (zero) is default
and highest. See
header
also be a regex. Optionally, set a precedence.
query-string
value of that query param; can also be a regex. Optionally, set a precedence.
uri
definition and usage. Optionally, set a precedence.
virtual-host
0.0.0.0, which means any IP address. The <port number> specification is optional.
To map requests by TCP port number only, set the IP address to 0.0.0.0 and configure
the port number. If you set the domain to any, configure virtual-host IP to 0.0.0.0,
then requests can be assigned to a namespace based solely on the port number on
which the request comes in to Media Flow Controller. Optionally, set a precedence.
object
specified with either a uri (can include a file name), a <pattern>, or all to delete or list the
contents of all configured namespaces. Use the domain and port arguments for mid-tier
or virtual namespaces. Use revalidate all to validate the timestamp of each object in
cache, even if not expired. See
details.
origin-server
cache misses; see
pre-stage
ftp user <username> password <password>
credentials for the default, auto-created namespace FTP user,
<namespace>_ftpuser; for FTP pre-staging content to Media Flow Controller. Only
this user can do FTP pre-staging for that namespace. When opening the FTP session,
log in as the auto-configured user. (<namespace>_ftpuser); in this way, every FTP
session transfers content only for a single namespace. Please refer to
and
password
proxy-mode transparent on-ip
using the IP address of your Media Flow Controller that you enter. See
for Proxy Configurations" on page 87
338
namespace
—Add a live stream publishing service.
—Either enable or disable (default) caching for this live-pub-point.
—Set a method for receiving live streaming:
—Contact the origin/publishing server when a request from the client
on-demand
is received.
—Make active or inactive (default) the live-pub-point.
—Refine the path of incoming requests (enclose all regex entries in single quotes).
—All match options can utilize the optional precedence argument to
"Using namespace match <criteria> precedence" on page
—A header <name> and <value> or use any for any value of that header; can
—A defined query param <name> and <value> or use any for any
—A <uri-prefix>; can also be a regex. See
—The IP address must be a /32 address; it can take a special value of
—EXEC
command. Either delete, or view (list), the contents of a namespace
—Specify how Media Flow Controller determines and accesses origin for
"(namespace) origin-server,"
—Set authentication options for pre-staging content.
tacacs-server
for setting authentication schemes.
—Set a password, or use a configured RADIUS or TACACS+ password.
Media Flow Controller Administrator's Guide
"uri-prefix" on page 34
"(namespace) object list | delete | revalidate,"
for CLI details.
—Set this namespace to be a Transparent Proxy
for more information.
Copyright © 2010, Juniper Networks, Inc.
for uri-prefix
—Set a password or authentication
radius-server
"Using namespace
84.
for CLI

Advertisement

Table of Contents
loading

This manual is also suitable for:

Media flow controller 2.0.4

Table of Contents