Juniper Networks, the Juniper Networks logo, JUNOS, NetScreen, ScreenOS, and SteelBelted Radius are registered trademarks of Juniper Networks, Inc. in the United States and
other countries. JUNOSe is a trademark of Juniper Networks, Inc. All other trademarks,
service marks, registered trademarks, or registered service marks are the property of their
respective owners.
Juniper Networks assumes no responsibility for any inaccuracies in this document. Juniper
Networks reserves the right to change, modify, transfer, or otherwise revise this publication
without notice.
Products made or sold by Juniper Networks or components thereof might be covered by one
or more of the following patents that are owned by or licensed to Juniper Networks: U.S.
Patent Nos. 5,473,599, 5,905,725, 5,909,440, 6,192,051, 6,333,650, 6,359,479, 6,406,312,
6,429,706, 6,459,579, 6,493,347, 6,538,518, 6,538,899, 6,552,918, 6,567,902, 6,578,186,
and 6,590,785.
READ THIS END USER LICENSE AGREEMENT (“AGREEMENT”) BEFORE DOWNLOADING, INSTALLING, OR USING THE SOFTWARE. BY
DOWNLOADING, INSTALLING, OR USING THE SOFTWARE OR OTHERWISE EXPRESSING YOUR AGREEMENT TO THE TERMS CONTAINED
HEREIN, YOU (AS CUSTOMER OR IF YOU ARE NOT THE CUSTOMER, AS A REPRESENTATIVE/AGENT AUTHORIZED TO BIND THE CUSTOMER)
CONSENT TO BE BOUND BY THIS AGREEMENT. IF YOU DO NOT OR CANNOT AGREE TO THE TERMS CONTAINED HEREIN, THEN (A) DO NOT
DOWNLOAD, INSTALL, OR USE THE SOFTWARE, AND (B) YOU MAY CONTACT JUNIPER NETWORKS REGARDING LICENSE TERMS.
1.The Parties. The parties to this Agreement are (i) Juniper Networks, Inc. (if the Customer’s principal office is located in the Americas) or Juniper Networks
(Cayman) Limited (if the Customer’s principal office is located outside the Americas) (such applicable entity being referred to herein as “Juniper”), and (ii) the
person or organization that originally purchased from Juniper or an authorized Juniper reseller the applicable license(s) for use of the Software (“Customer”)
(collectively, the “Parties”).
2.The Software. In this Agreement, “Software” means the program modules and features of the Juniper or Juniper-supplied software, for which Customer has paid
the applicable license or support fees to Juniper or an authorized Juniper reseller, or which was embedded by Juniper in equipment which Customer purch as ed
from Juniper or an authorized Juniper reseller. “Software” also includes updates, upgrades and new releases of such software. “Embedded Software” means
Software which Juniper has embedded in or loaded onto the Juniper equipment and any updates, upgrades, additions or replacements which are subsequently
embedded in or loaded onto the equipment.
3.License Grant. Subject to payment of the applicable fees and the limitations and restrictions set forth herein, Juniper grants to Customer a non-exclusive and
non-transferable license, without right to sublicense, to use the Software, in executable form only, subject to the following use restrictions:
a.Customer shall use Embedded Software solely as embedded in, and for execution on, Juniper equipment originally purchased by Customer from Juniper or
an authorized Juniper reseller.
b.Customer shall use the Software on a single hardware chassis having a single processing unit, or as many chassis or processing units for which Customer
has paid the applicable license fees; provided, however, with respect to the Steel-Belted Radius or Odyssey Access Client software only, Customer shall
use such Software on a single computer containing a single physical random access memory space and containing any number of processors. Use of the
Steel-Belted Radius or IMS AAA software on multiple computers or virtual machines (e.g., Solaris zones) requires multiple licenses, regardless of whether
such computers or virtualizations are physically contained on a single chassis.
c.Product purchase documents, paper or electronic user documentation, and/or the particular licenses purchased by Customer may specify limits to
Customer’s use of the Software. Such limits may restrict use to a maximum number of seats, registered endpoints, concurrent users, sessions, calls,
connections, subscribers, clusters, nodes, realms, devices, links, ports or transactions, or require the purchase of separate licenses to use particular features,
functionalities, services, applications, operations, or capabilities, or provide throughput, performance, configuration, bandwidth, interface, processing,
temporal, or geographical limits. In addition, such limits may restrict the use of the Software to managing certain kinds of networks or require the Software
to be used only in conjunction with other specific Software. Customer’s use of the Software shall be subject to all such limitations and purchase of all
applicable licenses.
d.For any trial copy of the Software, Customer’s right to use the Software expires 30 days after download, installation or use of the Software. Customer may
operate the Software after the 30-day trial period only if Customer pays for a license to do so. Customer may not extend or create an additional trial period
by re-installing the Software after the 30-day trial period.
e.The Global Enterprise Edition of the Steel-Belted Radius software may be used by Customer only to manage access to Customer’s enterprise network.
Specifically, service provider customers are expressly prohibited from using the Global Enterprise Edition of the Steel-Belted Radius software to support
any commercial network access services.
The foregoing license is not transferable or assignable by Customer. No license is granted herein to any user who did not originally purchase the applicable
license(s) for the Software from Juniper or an authorized Juniper reseller.
4.Use Prohibitions. Notwithstanding the foregoing, the license provided herein does not permit the Customer to, and Customer agrees not to and shall not: (a)
modify, unbundle, reverse engineer, or create derivative works based on the Software; (b) make unauthorized copies of the Software (except as necessary for
backup purposes); (c) rent, sell, transfer, or grant any rights in and to any copy of the Software, in any form, to any third party; (d) remove any proprietary notices,
labels, or marks on or in any copy of the Software or any product in which the Software is embedded; (e) distribute any copy of the Software to any third party,
including as may be embedded in Juniper equipment sold in the secondhand market; (f) use any ‘locked’ or key-restricted feature, function, service, application,
operation, or capability without first purchasing the applicable license(s) and obtaining a valid key from Juniper, even if such feature, function, service,
application, operation, or capability is enabled without a key; (g) distribute any key for the Software provided by Juniper to any third party; (h) use the Software
in any manner that extends or is broader than the uses purchased by Customer from Juniper or an authorized Juniper reseller; (i) use Embedded Software on nonJuniper equipment; (j) use Embedded Software (or make it available for use) on Juniper equipment that the Customer did not originally purchase from Juniper or
an authorized Juniper reseller; (k) disclose the results of testing or benchmarking of the Software to any third party without the prior written consent of Juniper;
or (l) use the Software in any manner other than as expressly provided herein.
5.Audit. Customer shall maintain accurate records as necessary to verify compliance with this Agreement. Upon request by Juniper, Customer shall furnish such
records to Juniper and certify its compliance with this Agreement.
6.Confidentiality. The Parties agree that aspects of the Software and associated documentation are the confidential property of Juniper. As such, Customer shall
exercise all reasonable commercial ef forts t o mai nta in t he Soft ware a nd associat e d docume ntati on in conf idence , which at a mini mum i ncludes res tri cti ng acce ss
to the Software to Customer employees and contractors having a need to use the Software for Customer’s internal business purposes.
7.Ownership. Juniper and Juniper’s licensors, respectively , retain ownership of all right, title, and interest (including copyright) in and to the Software, associated
documentation, and all copies of the Software. Nothing in this Agreement constitutes a transfer or conveyance of any right, title, or interest in the Software or
associated documentation, or a sale of the Software, associated documentation, or copies of the Software.
8.Warranty, Limitation of Liability, Disclaimer of Warranty. The warranty applicable to the Software shall be as set forth in the warranty statement that
accompanies the Software (the “Warranty Statement”). Nothing in this Agreement shall give rise to any obligation to support the Software. Support services may
be purchased separately. Any such support shall be governed by a separate, written support services agreement. TO THE MAXIMUM EXTENT PERMITTED
BY LAW, JUNIPER SHALL NOT BE LIABLE FOR ANY LOST PROFITS, LOSS OF DATA, OR COSTS OR PROCUREMENT OF SUBSTITUTE GOODS
III
Media Flow Manager Administrator’s Guide
OR SERVICES, OR FOR ANY SPECIAL, INDIRECT, OR CONSEQUENTIAL DAMAGES ARISING OUT OF THIS AGREEMENT, THE SOFTWARE, OR
ANY JUNIPER OR JUNIPER-SUPPLIED SOFTWARE. IN NO EVENT SHALL JUNIPER BE LIABLE FOR DAMAGES ARISING FROM
UNAUTHORIZED OR IMPROPER USE OF ANY JUNIPER OR JUNIPER-SUPPLIED SOFTWARE. EXCEPT AS EXPRESSLY PROVIDED IN THE
WARRANTY STATEMENT TO THE EXTENT PERMITTED BY LAW, JUNIPER DISCLAIMS ANY AND ALL WARRANTIES IN AND TO THE
SOFTWARE (WHETHER EXPRESS, IMPLIED, STATUTORY, OR OTHERWISE), INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE, OR NONINFRINGEMENT. IN NO EVENT DOES JUNIPER WARRANT THAT THE SOFTWARE, OR ANY
EQUIPMENT OR NETWORK RUNNING THE SOFTWARE, WILL OPERATE WITHOUT ERROR OR INTERRUPTION, OR WILL BE FREE OF
VULNERABILITY TO INTRUSION OR ATTACK. In no event shall Juniper’s or its suppliers’ or licensors’ liability to Customer, whether in contract, tort
(including negligence), breach of warranty, or otherwise, exceed the price paid by Customer for the Software that gave rise to the claim, or if the Software is
embedded in another Juniper product, the price paid by Customer for such other product. Customer acknowledges and agrees that Juniper has set its prices and
entered into this Agreement in reliance upon the disclaimers of warranty and the limitations of liability set forth herein, that the same reflect an allocation of risk
between the Parties (including the risk that a contract remedy may fail of its essential purpose and cause consequential loss), and that the same form an essential
basis of the bargain between the Parties.
9.Termination. Any breach of this Agreement or failure by Customer to pay any applicable fees due shall result in automatic termination of the license granted
herein. Upon such termination, Customer shall destroy or return to Juniper all copies of the Software and related documentatio n in Customer’s possession or
control.
10. Taxes. All license fees payable under this agreement are exclusive of tax. Customer shall be responsible for paying Taxes arising from the purchase of the
license, or importation or use of the Software. If applicable, valid exemption documentation for each taxing jurisdiction shall be provided to Juniper prior to
invoicing, and Customer shall promptly notify Juniper if their exemption is revoked or modified. All payments made by Customer shall be net of any applicable
withholding tax. Customer will provide reasonable assistance to Juniper in connection with such withholding taxes by promptly: providing Juniper with valid
tax receipts and other required documentation showing Customer’s payment of any withholding taxes; completing appropriate applications that would reduce the
amount of withholding tax to be paid; and notifying and assisting Juniper in any audit or tax proceeding related to transactions hereunder. Customer shall comply
with all applicable tax laws and regulations, and Customer will promptly pay or reimburse Juniper for all costs and damages related to any liability incurred by
Juniper as a result of Customer’s non-compliance or delay with its responsibilities herein. Customer’s obligations under this Section shall survive termination or
expiration of this Agreement.
11.Export. Customer agrees to comply with all applicable export laws and restrictions and regulations of any United States and any applicable foreign agency or
authority, and not to export or re-export the Software or any direct product thereof in violation of any such restrictions, laws or regulations, or without all
necessary approvals. Customer shall be liable for any such violations. The version of the Software supplied to Customer may contain encryption or other
capabilities restricting Customer’s ability to export the Software without an export license.
12. Commercial Computer Software. The Software is “commercial computer software” and is provided with restricted rights. Use, duplication, or disclosure by
the United States government is subject to restrictions set forth in this Agreement and as provided in DFARS 227.7201 through 227.7202-4, FAR 12.212, FAR
27.405(b)(2), FAR 52.227-19, or FAR 52.227-14(ALT III) as applicable.
13. Interface Information. To the extent required by applicable law, and at Customer's written request, Juniper shall provide Customer with the interfac
information needed to achieve interoperability between the Software and another independently created program, on payment of applicable fee, if any. Customer
shall observe strict obligations of confidentiality with respect to such information and shall use such information in compliance with any applicable terms and
conditions upon which Juniper makes such information available.
14. Third Party Software.Any licensor of Juniper whose software is embedded in the Software and any supplier of Juniper whose products or technology are
embedded in (or services are accessed by) the Software shall be a third party beneficiary with respect to this Agreement, and such licensor or vendor shall have
the right to enforce this Agreement in its own name as if it were Juniper. In addition, certain third party software may be provided with the Software and is subject
to the accompanying license(s), if any, of its respective owner(s). To the extent portions of the Software are distributed under and subject to open source licenses
obligating Juniper to make the source code for such portions publicly available (such as the GNU General Public License (“GPL”) or the GNU Library General
Public License (“LGPL”)), Juniper will make such source code portions (including Juniper modifications, as appropriate) available upon request for a period of
up to three years from the date of distribution. Such request can be made in writing to Juniper Networks, Inc., 1194 N. Mathilda Ave., Sunnyvale, CA 94089,
ATTN: General Counsel. You may obtain a copy of the GPL at http://www.gnu.org/licenses/gpl.html, and a copy of the LGPL at http://www.gnu.org/licenses/
lgpl.html.
15. Miscellaneous. This Agreement shall be governed by the laws of the State of California without reference to its conflicts of laws principles. The provisions of
the U.N. Convention for the International Sale of Goods shall not apply to this Agreement. For any disputes arising under this Agreement, the Parties hereby
consent to the personal and exclusive jurisdiction of, and venue in, the state and federal courts within Santa Clara County, California. This Agreement constitutes
the entire and sole agreement between Juniper and the Customer wi th respec t t o the S oftwar e, and supersedes all prior and contemporaneous agreements relat ing
to the Software, whether oral or written (including any inconsistent terms contained in a purchase order), except that the terms of a separate written agreement
executed by an authorized Juniper representative and Customer shall govern to the extent such terms are inconsistent or conflict with terms contained herein. No
modification to this Agreement nor any waiver of any rights hereunder shall be effective unless expressly assented to in writing by the party to be charged. If any
portion of this Agreement is held invalid, the Parties agree that such invalidity shall not affect the validity of the remainder of this Agreement. This Agreement
and associated documentation has been written in the English language, and the Parties agree that the English version will govern. (For Canada: Les parties aux
présentés confirment leur volonté que cette convention de même que tous les documents y compris tout avis qui s'y rattaché, soient redigés en langue anglaise.
(Translation: The parties confirm that this Agreement and all related documentation is and will be in the English language)).
This Administrator’s Guide is written for administrators of Juniper Networks Media Flow
Manager. In addition to the Guide to This Document
these topics:
•Documentation and Release Notes
•Typographical Conventions
•Te rm in ol o gy
•Documentation Feedback
•Requesting Technical Support
section, below, this preface includes
Guide to This Document
This document provides information on the following topics:
•Media Flow Manager Overview—An overview of Media Flow Manager features.
•Media Flow Manager Web-Based Interface—A page-by-page description of the Web-
based interface for Media Flow Manager.
•About the Command Line Interface (CLI)—Describes CMC CLI logging in, command
notation conventions, roles and privileges, terminology, and CLI options.
•CLI Commands—Alphabetical list of all commands including keywords, arguments, and
notes.
Documentation and Release Notes
To obtain the most current version of all Juniper Networks® technical documentation, see the
product documentation page on the Juniper Networks website at
http://www.juniper.net/techpubs/
Juniper Networks supports a technical book program to publish books by Juniper Networks
engineers and subject matter experts with book publishers around the world. These books go
beyond the technical documentation to explore the nuances of network architecture,
deployment, and administration using JUNOS Software and Juniper Networks devices. In
addition, the Juniper Networks Technical Library, published in conjunction with O'Reilly Media,
explores improving network security, reliability, and availability using JUNOS configuration
techniques. All the books are for sale at technical bookstores and book outlets around the
world. The current list can be viewed at http://www.juniper.net/books
Table 1 describes the typefaces used in this book.
Table 1Typefaces Used in This Book
TypefaceUseExample
ArialOrdinary text.The origin server organizes media
content hierarchically.
Arial BoldCommands in running text, and
Arial ItalicBook titles, and emphasis.See the Juniper Networks Media
Courier New
Courier New
Bold
Terminology
This section provides definitions for Juniper Networks and industry-standard terms that may
be unfamiliar to the reader.
AFR Assured Flow Rate. An Media Flow Controller option that, when enabled, ensures that
media content is delivered at a rate that is minimally needed for the video to play smoothly.
Bit-rate A data rate (the amount of data transferred in one direction over a link divided by the
time taken to transfer it) expressed in bits per second. Juniper Networks notation examples:
Kbps (kilobits per second), KB/s (kilobytes per second).
Edge cache An appliance placed between the Internet and the Web server which caches
content (like Java Script, CSS, images, etc.) and delivers them for the Web server, freeing up
that server for other processes. Media Flow Controller as an edge cache is effectively a
“reverse proxy,” that provides these benefits: reduces the load (network and CPU) on an origin
server by servicing previously retrieved content and enhances the user experience due to a
decrease in latency.
Full Download A media delivery mode in which the entire media file is downloaded before
playback begins; contrast with Progressive Download (see PDL, Progressive DownLoad
screen elements such as page
titles, and option labels.
Text displayed online at a
command line.
Text that you type exactly as
shown; variables are shown in
chevrons (< > ), parameters (which
may include variables) are shown
in box brackets ([ ]), options are
shown in curly brackets ({ }). Runon lines are indicated by an indent
(as shown at right).
Use the interface command to
configure IP addresses.
In the Management Console, use
the Setup > Date and time page.
Flow Manager Administrator’s
Guide and CLI Command
Reference
Media Flow Manager Administrator’s GuideCHAPTER 1 Preface
KB and KiB KB=1000 Kilo Bytes (networking), KiB=1024 Kilo Bytes (storage).
MB and MiB MB=1,000,000 Mega Bytes (networking), MiB=1,005,376 (1024 x 1024) Mega
Bytes (storage).
Media Flow Manager: A management interface that allows you to push configurations to a
number of Media Flow Controllers from a central interface.
Origin Library The source of media content.
Origin Server The media content server.
Player (media player software) Any media player for playing back digital video data from
files of appropriate formats such as MPEG, AVI, RealVideo, Flash, QuickTime, and so forth. In
addition to VCR-like functions such as playing, pausing, stopping, rewinding, and forwarding,
some common functions include zooming/full screen, audio channel selection, subtitle
selection, and frame capturing.
Profile A media “bit-rate profile” is the bit-rate encoding that allows optimal downloads to
different bandwidths.
PDL, Progressive DownLoad A media delivery mode in which the media file is played while
it is being downloaded; contrast with Full Download (see Full Download
Pull vs. Push Pull refers to media fetches from the origin server initiated by Media Flow
Controller based on received requests. Push refers to scheduled media deliveries from the
origin server to Media Flow Controller.
UOL, URI, URL These terms stand for Uniform Object Locator, Uniform Resource Identifier,
Uniform Resource Locator (respectively).
uri-prefix This namespace argument refines what requests Media Flow Controller accepts.
In the URL shown below, the uri-prefix could be defined as / (slash), /vod, or /vod/path1. If /
(slash) is used, all incoming requests to that domain are honored; if /vod, only requests
containing “/vod” are honored; if /vod/path1 requests must include that prefix and that path to
be honored.
).
Virtual Player This is a Media Flow Controller term referring to the sever-side player provided
by Media Flow Controller to assist in media viewing. Media Flow Controller offers several
types of virtual player for use in different scenarios; for SmoothFlow, the Type smoothflow
virtual player is used exclusively.
Documentation Feedback
We encourage you to provide feedback, comments, and suggestions so that we can improve
the documentation. You can send your comments to
techpubs-comments@juniper.net, or fill out the documentation feedback form at
https://www.juniper.net/cgi-bin/docbugreport/. If you are using e-mail, be sure to include the
following information with your comments:
■ Document or topic name
■ URL or page number
■ Software release version (if applicable)
Requesting Technical Support
Technical product support is available through the Juniper Networks Technical Assistance
Center (JTAC). If you are a customer with an active J-Care or JNASC support contract, or are
covered under warranty, and need post-sales technical support, you can access our tools and
resources online or open a case with JTAC.
•JTAC Policies—For a complete understanding of our JTAC procedures and policies,
•JTAC Hours of Operation—The JTAC centers have resources available 24 hours a day,
7 days a week, 365 days a year.
Self-Help Online Tools and Resources
For quick and easy problem resolution, Juniper Networks has designed an online self-service
portal called the Customer Support Center (CSC) that provides you with the following features:
•Find CSC offerings:
http://www.juniper.net/customers/support/
•Search for known bugs:
http://www2.juniper.net/kb/
•Find product documentation:
http://www.juniper.net/techpubs/
•Find solutions and answer questions using our Knowledge Base:
http://kb.juniper.net/
•Download the latest versions of software and review release notes:
http://www.juniper.net/customers/csc/software/
•Search technical bulletins for relevant hardware and software notifications:
https://www.juniper.net/alerts/
•Join and participate in the Juniper Networks Community Forum:
http://www.juniper.net/company/communities/
•Open a case online in the CSC Case Manager:
http://www.juniper.net/cm/
To verify service entitlement by product serial number, use our Serial Number Entitlement
(SNE) Tool located at
CHAPTER 2 Media Flow Manager OverviewMedia Flow Manager Administrator’s Guide
Media Flow Manager
Central Management
Console
Service
Provisioning
System
Log analyzer
(performance and
usage reporting)
Log
aggregation
servers
XML
API
Access logs
Configuration
messages
Network
management
system
SNMP
alarms
Midwest
West Coast
East Coast
g015411
Billing
system
NOC
CHAPTER 2
Media Flow Manager Overview
Juniper Networks Media Flow Manager manages Media Flow Controllers:
•Central Management Console (CMC)—Lets you attach to Media Flow Controllers and
monitor them, group Media Flow Controllers into named categories, create and apply
configuration templates, and apply preset action profiles.
•Service Director with Admission Control—Lets you to direct traffic to the Media Flow
Controller closest to the client. Admission Control lets you control the bandwidth
parameters of managed Media Flow Controllers.
•Real-Time Log File Analyzer—Provided via AWStats™ generates advanced Web,
streaming, and server statistics graphically.
•Seamless integration with 3rd party network management & service provisioning systems.
Media Flow Manager supports various management interfaces: command line interface (CLI),
Web-based Management Console, XML APIs, and SNMP GETs and traps.
Media Flow Controller nodes can be flexibly grouped based on factors such as business
function or geographical location, for easier configuration and management. Configuration
templates can be created and applied to different groups to provision new services. Media
Flow Manager periodically performs application level polling of Media Flow Controllers to
detect service unavailability and generate alarms, if needed. See Figure 1
for illustration.
Figure 1Media Flow Manager Interaction
For details, see the Media Flow Controller Administrator’s Guide and CLI Command
CHAPTER 2 Media Flow Manager OverviewMedia Flow Manager Administrator’s Guide
Note! Media Flow Manager is a separate product and is not a component of Media Flow
Controller. It needs to be deployed and managed separately.
Important! Media Flow Manager does not support RAID arrays.
Tip! Media Flow Manager provides a Web-based interface to manage your Media Flow
Controllers; this is described fully in Chapter 3, “Media Flow Manager Web-Based Interface."
Remote Monitoring and Management
You can use CMC to manage multiple Media Flow Controllers located anywhere in the
network. It communicates with a client running on each Media Flow Controller to collect
management information. Figure 1, “Media Flow Manager Interaction"
Controllers can be scattered in various places and managed by a single CMC.
CMC can be used to configure each of the Media Flow Controllers that the CMC manages.
You can send CLI commands to a particular Media Flow Controller, or a group of Media Flow
Controllers. You can also copy the configuration from one Media Flow Controller and apply it
to another.
Detailed management information about each Media Flow Controller that a CMC manages,
including operational state, disk space, CPU utilization, and software version is provided as
well as summary information about the CMC console.
CMC allows you to access the Management Console of each of the Media Flow Controllers it
manages. You log into, configure, manage, and control a particular Media Flow Controller.
Media Flow Manager logs show the behavior of managed Media Flow Controller’s with respect
to their operational status. The logging infrastructure provides time-based logs to correlate
Media Flow Controller behavior at different times.
shows how Media Flow
Fault Management
CMC provides a real-time fault management of the managed Media Flow Controllers. It
constantly checks the live status of the Media Flow Controller by sending periodic HTTP
“heartbeats.” CMC has the ability to view the full health of appliance(s)—including all system
resources. It uses different colors for in-service versus out-of-service Media Flow Controllers.
CMC can be configured to send SNMP traps for certain alarm generations. CMC also uses
various logs for different events.
Groups and Profiles
CMC allows multiple Media Flow Controllers to be grouped together for ease of configuration
and management. CMC also allows administrators to create profiles, i.e. configuration items
that are grouped together. Once a profile is created, it can be applied to an individual Media
Flow Controller or a configured group of Media Flow Controllers.
CMC can also use a mutual authentication between the Media Flow Controllers and itself
using configurable shared secrets.
Media Flow Manager Administrator’s GuideCHAPTER 2 Media Flow Manager Overview
Central Management Console
This section describes how the Central Management Console (CMC) works; first, terminology:
•Media Flow Manager Server: The machine running the CMC software managing clients.
•CMC Client: The software on a Media Flow Controller being managed by a CMC server.
•CMC Rendezvous: A way to establish the connection between the CMC server and the
CMC client. In this method the Media Flow Controller is pre-configured with the CMC
server information and when the Media Flow Controller comes up it requests connectivity
to the CMC; on the CMC you authorize the Media Flow Controller and the connection gets
established. The other method for connectivity is explicitly configuring the Media Flow
Controller information on the CMC.
The CMC function of Media Flow Manager is server-client based. You configure the CMC
server with a list of Media Flow Controller appliances and it runs the Remote Box
Management Daemon (RBMD). In the standard server-initiated connection scenario, the CMC
server is configured with a means of logging into an administrator account on each client
Media Flow Controller using a password, or SSH v2 RSA or DSA keys, opening a connection,
and proxying requests between the two.
In the client-initiated connection scenario, the Media Flow Controller CMC client logs into the
CMC server using a password, or SSH v2 RSA or DSA keys, opens a connection, and the
same lines of communication are established as with the server-initiated connection.
Some of CMC’s management tasks are accomplished through requests that are proxied.
Other tasks are accomplished by sending the client lists of CLI commands that are executed
locally.
Appliances (Media Flow Controllers)
An appliance represents a single remote system that the CMC manages. It contains the
address of the system, and credentials that can be used to log into it. The credentials may
either be a password, or the name of an identity record (see “Identities,"
which authentication type is selected. Each authentication type can specify with a username to
log in as; the user specified should have administrative privileges for the CMC to manage the
appliance correctly; admin is the default user. Note that for client-initiated connections, the
server does not need these credentials in the appliance record. The central administrator sets
up one or more local accounts for the clients to log into, and gives this login information to the
remote administrators.
Groups
A group record contains references to any number of appliance records. Any action that can
be performed on an appliance, such as applying a profile (executing a set of CLI commands),
can also be performed on a group. An appliance may belong to any number of groups. There
is one reserved group, all, which is automatically maintained to contain every configured
appliance.
below), depending on
Central Management Console27
CHAPTER 2 Media Flow Manager OverviewMedia Flow Manager Administrator’s Guide
Identities
An identity is an RSA or DSA key pair that can be used to log into a managed appliance. Each
identity has a name, which is an administrator-assigned string used to refer to it. Most
commonly, the administrator can ask for an identity to be generated automatically; but an
identity can also be created by specifying the public and private key directly. When specifying
the credentials to use to log into an appliance, the administrator can provide a username and
the name of the identity to use, as an alternative to a username and password.
Profiles
A profile is a stored list of CLI commands that can be run on remote appliances or groups.
When a profile is applied, the non-local configuration on the remote system is first reset to its
defaults. "Local" configuration in this context is anything system-specific that should not be
shared between systems. By default, this is the network interface and route configurations
required for basic network connectivity.
Profiles can be created from the CLI by specifying their lists of commands directly, or from the
Web-based Media Flow Manager Central Management Console (CMC). The CMC lets you
create profiles by filling out configuration forms, much like you would do to configure an
appliance directly. For example, to create a profile that configures NTP on a remote appliance,
the CMC has a special NTP configuration page that looks much like the NTP configuration
page in the Management Console of a Media Flow Controller. You enter the NTP configuration
here, and when you press Apply, the commands to configure NTP in the manner specified are
added to the selected profile. The Central Management Console also allows you to type CLI
commands to be added to a profile, for full manual control.
Status Criteria
A status criterion is one test to be applied to a remote managed appliance to determine its
status or health. These criteria are checked periodically and the results recorded, with the goal
of helping you notice problems in the appliances being managed. You cannot create status
criteria in CMC, but you can enable or disable specific status criteria.
Rendezvous
The rendezvous feature mainly impacts appliances and identities on the server side. The
server is generally configured with one or more identities at manufacture time, which it later
uses to log into clients to manage. The server and client are configured with other information
that allow them to find and authenticate each other. The rendezvous process then ultimately
results in new appliance records being added semi-automatically to the server's configuration.
An administrator at the CMC server must confirm each client before the server starts
managing it. The CMC server may also be put into an auto-accept mode where it immediately
accepts any client that presents itself. The server may then log into each approved client, also
using preconfigured credentials.
Media Flow Manager Administrator’s GuideCHAPTER 2 Media Flow Manager Overview
Media Flow Controller
San Francisco
East Coast user
Central US user
Content delivery network
g015424
Central
Management
Console
with
Service Director
Application
West Coast user
Media Flow Controller
New York
Server
www.example.com
3
4
5 65 65 6
121 2
3
4
Service Director
This section describes how the Service Director feature works. Online video viewing can be
significantly improved by delivering content from a location close to the user. Juniper Networks
Service Director application is a cost-effective and easy to deploy solution to direct video
requests to the nearest content server and deliver location specific content. The benefits are:
•Better customer traction with improved Quality of viewing Experience (QoE) and localized
content
•Eliminate transit bandwidth costs by delivering video from servers within the ISP’s network
Note! The Service Director application is not a replacement for Global Server Load Balancing
(GSLB) or the DNS infrastructure that provide many additional services.
Figure 2How Service Director Works
1. User clicks on a video at example.com
2. Server returns HTML embedded with Flash player
3. Flash player makes a Web query to the Service Director to get the edge server’s
hostname
4. Service Director returns an XML response with the HOST field containing the server
address (Media Flow Controller or Content Delivery Network) based on the user’s location
5. and 6. The Video is delivered
The player and/or portal contacts the Service Director which uses the source IP from the
HTTP header or the IP address in the HTTP query URL and resolves it to one of continent/
country/state/city/ZIP/ISP. Based on the match, an XML file is returned to the Media Flow
Controller making the query with several details. From the XML file the Media Flow Controller
figures out which server to contact. The XML file can be auto-created based on configuration,
Service Director29
CHAPTER 2 Media Flow Manager OverviewMedia Flow Manager Administrator’s Guide
or pre-created according to a given format, or even with a proprietary format as long as the
client will understand the response.
Admission Control
Admission Control works with Service Director. Media Flow Manager runs the Service Director
mechanism to control the edge servers that serve client requests for content, based on the
geographical location of the client. Service Director allows you to configure the closest Media
Flow Controller for a given geographical location. Admission Control leverages the interface
statistics from the Media Flow Controllers and controls the outgoing bandwidth for the content
served by the Media Flow Controllers using the Service Director.
Media Flow Controllers are designed to track the interface stats (RX bytes and TX bytes) on
every network interface. In a typical setup, the TX bytes would be the content delivered by the
Media Flow Controller while the RX bytes would the data fetched from the origin server. The
Media Flow Manager Admission Control feature fetches the interface stats from the Media
Flow Controllers at regular intervals (5 minutes). These RX and TX stats from the various
Media Flow Controllers are then collated to calculate the delivered bandwidth and the received
bandwidth. These collated bandwidths are recorded and plotted on a graph for easy viewing in
the Media Flow Manager. The Service Director uses the configuration of location-to-host
mapping to return an XML with the host name of the edge Media Flow Controller based on the
client’s location. To assist with Admission Control, configure a high watermark bandwidth
and low watermark bandwidth used by the Service Director in the following way:
•If the current bandwidth measured in the last 5 minutes goes above the set high
bandwidth watermark, the Service Director only returns the default configured host
(typically the CDN). This would mean that no new traffic comes to the Media Flow
Controllers while they serve all the current requests.
•If the current bandwidth drops below the set low bandwidth watermark, the Service
Director goes back to normal operation returning hosts based on the set configuration.
This lets you throttle the aggregate bandwidth delivered by the Media Flow Controllers,
ensuring that the publisher does not pay bandwidth overage charges.
Real-Time Log File Analyzer
Juniper Networks Media Flow Manager also provides an interface to AWStats™ realtime
logfile analyzer to provide aggregated log information output to the Reports page. A full log
analysis enables AWStats to show you the following information:
•Number of visits, and number of unique visitors
•Visits duration and last visits
•Authenticated users, and last authenticated visits
•Days of week and rush hours (pages, hits, KB for each hour and day of week)
•Domains/countries of hosts visitors (pages, hits, KB, 269 domains/countries detected,
GeoIp detection)
•Hosts list, last visits and unresolved IP addresses list