Juniper MEDIA FLOW CONTROLLER 2.0.4 -, Administrator'S Manual

Page: 200 / 400

Media Flow Controller Common Configuration Tasks (CLI) Media Flow Controller Administrator’s Guide
200 Configuring NFS Fetch for Images (CLI) Copyright © 2010, Juniper Networks, Inc.
Cache Name Configuration
Video-Id : id
Format Tag : itag
Seek Configuration
Enabled: yes
URI Query: begin
Seek Length URI Query :
Assured Flow Configuration
Enabled: no
Rate: 0 kbps
URI query:
Auto: no
Fast Start Configuration
Enabled: no
Size: 0 kBytes
time: 0 seconds
URI query:
Connection Configuration
Max Bandwidth: 0 kbps
Configuring NFS Fetch for Images (CLI)
Configuring Media Flow Controller to fetch all JPEG image files located in a particular directory
on an NFS origin server requires another namespace configuration.
In this example, all requests for files at www.example.com/jpgImages/ that incur a cache
miss (necessitating an origin fetch) are fetched from the specified origin using NFS; the
configuration could look like this:
test-vos (config) # namespace exampleJpegs
test-vos (config namespace exampleJpegs) # domain www.example.com
test-vos (config namespace exampleJpegs) # match uri /jpgImages/
test-vos (config namespace exampleJpegs) # origin-server nfs
exampleOS.com: /home/jpgImages
test-vos (config namespace exampleJpegs) # status active
test-vos (config namespace exampleJpegs) # exit
test-vos (config) #
The match uri-prefix of /jpgImages tells Media Flow Controller to use these namespace
rules for incoming requests containing /jpgImages in the URL: use NFS to fetch the requested
file from the specified origin-server on the default port, if unspecified (default NFS port is
2049).
Just as with the initial namespace configuration, repeat the namespace configurations with the
domain specified without the “www” prefix, and again specified with the IP address, if
requests may come in those ways. Test the configuration with ping.
Tip! If unsure what port you are using for origin-server, use standard Linux shell commands
to figure out the port, and then configure it along with the origin-server, if not the default.