Creating A Namespace And Setting Namespace Options (Cli) - Juniper MEDIA FLOW CONTROLLER 2.0.4 - ADMINISTRATOR S GUIDE AND CLI Administrator's Manual

Administrator’s guide and cli command reference
Table of Contents

Advertisement

Media Flow Controller Administrator's Guide
any number and combination of these two to a namespace; the order of in which the
maps are added to the namespace denotes the order in which they are read.
server-map <name> [format-type <type>]
2. Set a URL for the server-map; this tells Media Flow Controller where to fetch the XML
mapping file. Also, set a refresh interval (how often Media Flow Controller refreshes the
XML file). The default refresh-interval is 0 (zero), which means no refresh after the initial
fetch. When you set the file-url Media Flow Controller immediately initiates an HTTP GET,
retrieves the file, and executes MapXML to convert the data to binary. From server-map
prefix mode:
file-url <URL> refresh-interval <time>
3. The final step is to add a server-map (or, potentially, multiple server-maps in the case of
cluster-map and origin-escalation-map) to a namespace origin-server configuration.
When the server map is added, Media Flow Controller starts the heartbeat (cluster-map
and origin-escalation-map only) to the defined nodes (10 beats/second).
namespace<name> origin-server <protocol> server-map <name>
Example (for NFS origin):
test-vos (config) # server-map newMap
test-vos (config server-map newMap) # file-url http://example.com/nfs/
maps/ refresh-interval 9000
test-vos (config server-map newMap) # exit
test-vos (config) # show server-map
Server-map : newMap
Format-Type :
Map File : http://example.com/nfs/maps/
Refresh Interval : 9000
test-vos (config) # namespace newTest origin-server nfs server-map newMap

Creating a Namespace and Setting Namespace Options (CLI)

Before you configure Media Flow Controller namespaces, see
Flow Controller" on page
Create namespaces to define fine-grained delivery policies, including optionally adding a
custom virtual player. You must create a namespace for each origin server and delivery criteria
scheme you use. You can create up to 256 namespaces in one Media Flow Controller. See
namespace
Using namespace cache-inherit
Using namespace domain regex
Using namespace domain <FQDN:Port>
Using namespace match uri regex
Using namespace match <criteria> precedence
Using namespace delivery protocol <protocol> origin-fetch cache-age
Using namespace object delete | list
Using namespace for Live Streaming Delivery Without Caching
Using namespace for Live Streaming Delivery With Caching
58.
for CLI details.
Creating a Namespace and Setting Namespace Options (CLI)
Media Flow Controller Configuration Tasks (CLI)
"Before You Configure Media
81

Advertisement

Table of Contents
loading

This manual is also suitable for:

Media flow controller 2.0.4

Table of Contents