User manual JUNIPER NETWORKS MEDIA FLOW CONTROLLER 2.0.4 ADMINISTRATOR S GUIDE AND CLI COMMAND REFERENCE

[. . . ] Media Flow ControllerTM Administrator's Guide and CLI Command Reference Release 2. 0. 4 Published: 2010-9-17 Copyright © 2010, Juniper Networks, Inc. Media Flow Controller Administrator's Guide Juniper Networks, Junos, Steel-Belted Radius, NetScreen, and ScreenOS are registered trademarks of Juniper Networks, Inc. in the United States and other countries. The Juniper Networks Logo, the Junos logo, and JunosE are trademarks of Juniper Networks, Inc. All other trademarks, service marks, registered trademarks, or registered service marks are the property of their respective owners. [. . . ] Any incoming request for a file located in /videos/HD will use the assigned SmoothFlow virtual player Type 4, HD. That virtual player tells Media Flow Controller what actions to perform when certain query params are sent from the client player. In this case, any incoming requests for videos at www. example. com/videos/HD will have SmoothFlow functionality applied as indicated, with a working SmoothFlow client player. 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. 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. 202 Configuring SmoothFlow Restricted by File Path (CLI) Copyright © 2010, Juniper Networks, Inc. Media Flow Controller Administrator's Guide Media Flow Controller Common Configuration Tasks (CLI) Configuring the SNMP Agent (CLI) You can configure the SNMP agent running in the Media Flow Controller to integrate with 3rdparty Network Management Systems (NMS). The following are the key Media Flow Controller configuration items: · · Configure the NMS IP address: snmp host <NMS_IP_address> Configure the community string, a shared secret between the NMS & Media Flow Controller: snmp host <NMS_IP_address> traps <community_string> · · Enable generation of traps in the Media Flow Controller: snmp enable traps Configure the events for which traps have to be generated and sent to the NMS: snmp traps event <trap_event> See also snmp traps events. Pre-Staging Content with FTP (CLI) You pre-stage content to a Media Flow Controller edge cache or origin so it is there when the first request arrives. Typically, content is pre-staged to origin; however, you can pre-stage content to the edge, but always pre-stage such content to origin as well because edge caches function as volatile storage and evict content rapidly. When you create a namespace, an FTP user is automatically created with the name <namespace>_ftpuser, without a password. You need to use the CLI username or namespace commands to give the user a password; then you can log in as that namespace's FTP user and issue the FTP commands to push the content to Media Flow Controller (default FTP port is 21). In this way, each FTP session transfers content only for one namespace at a time and users cannot view the content of another FTP user. If the pre-staging is to an attached library (2 machine arrangement), then you can see the listing of the files using your FTP client. If the pre-staging is to Media Flow Controller directly, then you can use the namespace object list all command to see the listing of transferred files. Pre-staging content in this manner simply places the files on the Media Flow Controller. In order to pre-process for SmoothFlow, you must follow a different procedure. See Chapter 8, "SmoothFlow Deployment for more information. FTP in Media Flow Controller has no checksum support. Configuring Media Flow Controller Mid-Tier Proxy (CLI) Service providers are using 3-tier architectures de-coupling front end servers from back-end storage servers by deploying mid-tier proxies. Mid-tier proxies reduce network latency, save bandwidth costs, offload origin servers, and scale front-end server throughput. Media requests are handled by front-end servers, supporting multiple protocols, that issue HTTP fetch Configuring the SNMP Agent (CLI) 203 Media Flow Controller Common Configuration Tasks (CLI) Media Flow Controller Administrator's Guide requests to Media Flow Controller mid-tier proxy, instead of to origin servers. Media Flow Controller serves the content just as an origin server would in a network without mid-tier servers. You can configure Media Flow Controller as a mid-tier proxy via a namespace setting. In this deployment, you must also configure user browsers to point at the Media Flow Controller; domain and match uri-prefix settings are generally irrelevant and can be set to any and / (slash), respectively. If you have multiple namespaces, set a low precedence (10 is the lowest) so incoming requests can pass to namespaces with specific uri-prefix matches (instead of / that accepts all incoming requests). [. . . ] Notes: · auth--Configure authentication settings for the Web proxy. · authtype--Configure the type of authentication to be used with a Web proxy. Only matters if a proxy is configured with web proxy host. The no variant resets the authtype to its default, which is none. · none--No authentication required. [. . . ]