Juniper MEDIA FLOW CONTROLLER 2.0.4 - ADMINISTRATOR S GUIDE AND CLI Administrator's Manual
  1. Manuals
  2. Brands
  3. Juniper Manuals
  4. Software
  5. MEDIA FLOW CONTROLLER 2.0.4 - ADMINISTRATOR S GUIDE AND...
  6. Administrator's manual
Juniper MEDIA FLOW CONTROLLER 2.0.4 - ADMINISTRATOR S GUIDE AND CLI Administrator's Manual

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

Administrator’s guide and cli command reference
Hide thumbs
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
Table of Contents

Advertisement

Quick Links

Download this manual
Media Flow Controller™
Administrator's Guide and CLI Command Reference
Release
2.0.4
Published: 2010-9-17
Copyright © 2010, Juniper Networks, Inc.

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the MEDIA FLOW CONTROLLER 2.0.4 - ADMINISTRATOR S GUIDE AND CLI and is the answer not in the manual?

Questions and answers

Subscribe to Our Youtube Channel

Related Manuals for Juniper MEDIA FLOW CONTROLLER 2.0.4 - ADMINISTRATOR S GUIDE AND CLI

Summary of Contents for Juniper MEDIA FLOW CONTROLLER 2.0.4 - ADMINISTRATOR S GUIDE AND CLI

  • Page 1 Media Flow Controller™ Administrator’s Guide and CLI Command Reference Release 2.0.4 Published: 2010-9-17 Copyright © 2010, Juniper Networks, Inc.
  • Page 2 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.

  • Page 3: End User License Agreement

    DOWNLOAD, INSTALL, OR USE THE SOFTWARE, AND (B) YOU MAY CONTACT JUNIPER NETWORKS REGARDING LICENSE TERMS. 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...
  • Page 4 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.

  • Page 5: Document History

    Media Flow Controller Administrator’s Guide Document History Date Media Flow Controller Version Comments 2010-4-27 Release 2.0 Document Version 2.0 2010-5-14 Release 2.0.1 Document Version 2.0a 2010-6-17 Release 2.0.2 Document Version 2.0b 2010-7-21 Release 2.0.3 Document Version 2.0c 2010-9-17 Release 2.0.4 Document Version 2.0d...
  • Page 6 Media Flow Controller Administrator’s Guide Copyright © 2010, Juniper Networks, Inc.

  • Page 7: Table Of Contents

    Self-Help Online Tools and Resources ................1.35 Opening a Case with JTAC ....................1.35 PART 1 Media Flow Controller Administration Media Flow Controller Overview ............2.39 Media Flow Controller Overview ................. 2.39 Environment........................ 2.40 Copyright © 2010, Juniper Networks, Inc.
  • Page 8 Type generic........................2.54 Type break.......................... 2.54 Type qss-streamlet ......................2.54 Type yahoo......................... 2.54 Type smoothflow ........................ 2.55 Type youtube........................2.55 Type smoothstream-pub..................... 2.55 Encoding Schemes......................2.56 Media Flow Controller Media Flow Manager Functions..........2.56 VIII Copyright © 2010, Juniper Networks, Inc.
  • Page 9 Media Flow Controller Administrator’s Guide TABLE OF CONTENTS Media Flow Controller Configuration Tasks (CLI) ........3.57 Before You Configure Media Flow Controller ............. 3.58 About the Media Flow Controller CLI ................3.58 Connecting and Logging In....................3.59 Using the Command Modes ....................3.59 Prompt and Response Conventions...................
  • Page 10 Saving and Applying Configurations, Resetting Factory Defaults (CLI)....3.104 Rebooting Media Flow Controller (CLI)..............3.105 Upgrading Media Flow Controller (CLI) ..............3.105 Configuring the Web Interface (CLI) ................. 3.106 Configuring the Web Interface Proxy (CLI) ............... 3.107 Copyright © 2010, Juniper Networks, Inc.
  • Page 11 Media Flow Controller Administrator’s Guide TABLE OF CONTENTS Media Flow Controller Configuration Tasks (Web Interface) ....4.109 About the Media Flow Controller Web Interface ............4.110 Connecting and Logging In....................4.110 Logging In to Media Flow Controller for the First Time (Web Interface) ....4.111 Configuring Media Flow Controller for the First Time (Web Interface)......
  • Page 12 Virtual Player smoothstream-pub Type Configuration............4.179 Configuring NameSpaces (Web Interface) ............... 4.179 Add Namespace ....................... 4.180 Configuration List......................4.180 Namespace Configuration ....................4.180 Managing the Media-Cache (Web Interface) ............4.186 Disk Name ........................4.186 Copyright © 2010, Juniper Networks, Inc.
  • Page 13 Media Flow Controller Administrator’s Guide TABLE OF CONTENTS Configuring Service Logging (Web Interface) ............4.187 Access Log Configuration....................4.187 Access Log Copy/Auto Download Configuration.............. 4.187 Stream Log Configuration....................4.188 Stream Log Copy/Auto Download Configuration.............. 4.189 Viewing Logs Overview..................... 4.189 Viewing the System Log (Web Interface) ................. 4.189 Viewing the Service Log (Web Interface) .................
  • Page 14 System Log Severity Levels and Classes ................ 6.228 Configuring Media Flow Controller System Logging (CLI) ..........6.229 Configuring Log Statistics Thresholds (CLI) ............. 6.231 Stats Reports Names Options ..................6.232 Stats Measurement Counters ................... 6.233 Copyright © 2010, Juniper Networks, Inc.
  • Page 15 Media Flow Controller Administrator’s Guide TABLE OF CONTENTS Stats Alarms......................6.234 Configuring stats alarm Notifications ................6.236 SNMP Alarms ......................6.237 SNMP ..........................6.237 Configuring Media Flow Controller Fault Notifications (CLI) ........6.240 Server Map Configuration ..............7.243 Server Map Overview ....................7.243 Server Map Format Types ..................
  • Page 16 Incoming Requests’ URL Length..................9.283 PART 2 Media Flow Controller Command and MIB Reference Media Flow Controller CLI Commands ..........10.287 aaa .......................... 10.289 aaa (authentication) ....................10.289 aaa (authorization) ....................10.289 accesslog ........................ 10.290 Copyright © 2010, Juniper Networks, Inc.
  • Page 17 Media Flow Controller Administrator’s Guide TABLE OF CONTENTS accesslog format Options ..................10.291 analytics ........................10.292 application....................... 10.293 arp........................... 10.293 banner........................10.294 bond ........................10.294 boot ......................... 10.295 cachelog........................10.295 clear ........................10.296 cli..........................10.296 clock........................10.298 cmc ......................... 10.299 cmc auth .........................
  • Page 18 Example for NFS Origin ................10.350 server-map Example for HTTP Origin ................10.351 service........................10.351 show........................10.352 slogin........................10.353 snmp-server ......................10.353 snmp traps........................10.354 snmp traps events ......................10.354 ssh .......................... 10.355 XVIII Copyright © 2010, Juniper Networks, Inc.
  • Page 19 Media Flow Controller Administrator’s Guide TABLE OF CONTENTS ssh client ......................... 10.355 ssh server ....................... 10.357 stats ........................10.358 stats alarms......................10.360 stats alarm States......................10.360 stats alarm rate-limit count ..................... 10.360 stats CHDs......................10.362 stats samples ......................10.364 streamlog ........................ 10.365 streamlog format Options ....................
  • Page 20 TABLE OF CONTENTS Media Flow Controller Administrator’s Guide Media Flow Controller MIB Definitions ..........11.385 Variables ......................... 11.385 NOTIFICATIONS ....................11.388 INDEX ....................IX.391 Copyright © 2010, Juniper Networks, Inc.
  • Page 21 LIST OF FIGURES Figure 1 Juniper Networks Media Flow Controller Operations (reverse proxy deployment) ..2.44 Figure 2 Media Flow Controller Ingest and Delivery Options ............. 2.46 Figure 3 Media Flow Controller Cache Ingest and Promotion Process........2.49 Figure 4 SmoothFlow™...
  • Page 22 Figure 63 Log Configuration Page Detail (Stream Log Copy/Auto Upload Configuration)..4.189 Figure 64 Media Flow Controller Example Current Log ............. 4.190 Figure 65 Media Flow Controller Dashboard Example............... 4.193 Figure 66 Media Flow Controller Disk Cache Graph Example ........... 4.194 XXII Copyright © 2010, Juniper Networks, Inc.
  • Page 23 LIST OF FIGURES Figure 67 Publishing Workflow, Typical Steps ................8.254 Figure 68 On-Demand Workflow, Typical Steps ................ 8.263 Figure 69 wget Test for Media Flow Controller HTTP Delivery and Cache........ 9.277 XXIII...
  • Page 24 LIST OF FIGURES XXIV Copyright © 2010, Juniper Networks, Inc.
  • Page 25 Required Configurable Nodes and Parameters ............8.267 Table 27 TCP/IP Diagnostic Utilities ..................9.276 Table 28 Accesslog Format Options ..................10.291 Table 29 errorlog level Options ....................10.314 Table 30 errorlog module Options................... 10.314 Copyright © 2010, Juniper Networks, Inc.
  • Page 26 Logging Severity Levels ................... 10.331 Table 32 SNMP Traps Notify-able Events................10.355 Table 33 Stats Alarms ......................10.361 Table 34 Stats CHDs....................... 10.362 Table 35 Stats Samples ......................10.364 Table 36 streamlog format Options ..................10.366 XXVI Copyright © 2010, Juniper Networks, Inc.

  • Page 27: Preface

    On fresh installations, any partition data on the drive is overwritten. Previously, if disk drives had non-Centos data when doing a fresh installation, the installer responded with a partition error. Copyright © 2010, Juniper Networks, Inc. What’s New in Release 2.0.4...

  • Page 28: Logging Enhancements

    You can now list controllers on the media cache; currently 3ware controller only. Hardware Support Juniper Networks VXA Series Chassis • Media Flow Controller Release 2.0.4 is qualified to run on Juniper Networks VXA Series appliances. • Supported models are VXA1001and VXA1002 chassis, and VXA2002 and VXA2010 NEBS-compliant chassis.

  • Page 29: Documentation And Release Notes

    385: Provides the base MIBs supported by Media Flow Controller. 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.

  • Page 30: Terminology

    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). See also Profile (Bit-rate profile).
  • Page 31 CLI Command Line Interface. Client Node or software program (front-end device) that requests services from a server. CMC Central Management Console, Juniper Networks management interface that allows you to push configurations to a number of Media Flow Controllers from a central interface. In Release 2.0.4, only client configuration is supported.
  • Page 32 NTP Network Time Protocol. Origin library The source of media content, typically a server located at a data center. Origin server The media content server. Juniper Networks Media Flow Controller can be configured as an Origin 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.
  • Page 33 Media Flow Controller Administrator’s Guide Preface Relative URL A relative URL points to the location of a file from a point of reference, usually the directory beneath. Preceded by two dots (../directory_path/file.txt) for the directory above; one dot (./directory_path/file.txt) for the current directory. Contrast with Absolute URL.

  • Page 34: Documentation Feedback

    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.

  • Page 35: Self-Help Online Tools And Resources

    Media Flow Controller Administrator’s Guide Preface 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/...
  • Page 36 Preface Media Flow Controller Administrator’s Guide Requesting Technical Support Copyright © 2010, Juniper Networks, Inc.

  • Page 37: Media Flow Controller Administration

    PART 1 Media Flow Controller Administration Copyright © 2010, Juniper Networks, Inc.
  • Page 38 Media Flow Controller Administrator’s Guide Copyright © 2010, Juniper Networks, Inc.

  • Page 39: Media Flow Controller Overview

    Media Flow Controller is powered by the Juniper Networks Media Operating System (NMoS™), a media-intelligent operating system designed to serve large numbers of sessions and deliver high throughput by optimizing resource utilization and new media technologies.

  • Page 40: Environment

    Hardware Description •   Processor Juniper Networks VXA Series Media Flow Engine. •   One quad-core (2.0 GHz or higher) x86 64-bit processor (second quad- core processor recommended for future capacity expansion). Minimum of 8GB. The actual amount of RAM depends on system requirements like throughput sessions per seconds, and so forth.

  • Page 41: Delivery Network Link Aggregation

    • “Email and Email2SMS Alerts” on page 43 In addition to these management interfaces, multiple Media Flow Controllers deployed in a network can be configured and managed from a centralized location using Juniper Networks Media Flow Manager. Management Interfaces Overview...

  • Page 42: Command Line Interface (Cli)

    (ro) access to a Media Flow Controller. The default value for this community string is public. Using this community string like a password, the NMS can retrieve data from Media Flow Controllers. In Release 2.0.4 only SNMP ro (Read-Only) is supported. Management Interfaces Overview Copyright © 2010, Juniper Networks, Inc.

  • Page 43: Email And Email2Sms Alerts

    Media Flow Controller Administrator’s Guide Media Flow Controller Overview Email and Email2SMS Alerts Media Flow Controller allows you to be notified via email during events such as high CPU/ Memory utilization, Interface up/down, threshold crossing on statistics or counters. Media Flow Controller uses SMTP protocol to send emails to the administrators.

  • Page 44: Figure 1 Juniper Networks Media Flow Controller Operations (Reverse Proxy Deployment)

    Network Network Management station Figure 1 Juniper Networks Media Flow Controller Operations (reverse proxy deployment) Figure 1 illustrates the relations between Media Flow Controller and other network components in the media delivery optimization operation. 1. Requests come in from the Internet via HTTP, to (typically) an Ethernet switch or Load Balancer that redirects the request to Media Flow Controller.

  • Page 45: Media Flow Controller Functions Overview

    Media Flow Controller cache. 3. Management interfaces monitor activity and allow configuration changes. Media Flow Controller Functions Overview Juniper Networks Media Flow Controller provides several highly specialized functions for optimizing the delivery and storage of media content. •...

  • Page 46: Streaming With Http

    Request to delete a resource. Responses not cacheable. Retrieve the resource identified by the Request-URI. Responses are cacheable. HEAD Obtain meta-information. Identical to GET except content is not returned. Responses are cacheable. Media Flow Controller Delivery Methods Copyright © 2010, Juniper Networks, Inc.

  • Page 47: Streaming With Rtsp

    Media Flow Controller Administrator’s Guide Media Flow Controller Overview Table 3 HTTP Methods (Continued) Method Description OPTIONS Get available request/response options. Responses are not cacheable. POST Request server action: •   annotate an existing resource •   post a message •   accept a block of data •  ...

  • Page 48: Connection Pooling

    The order of in which the maps are added to the namespace denotes the order in which they are read. Chapter 7, “Server Map Configuration,” for more details including requirements. Media Flow Controller Delivery Methods Copyright © 2010, Juniper Networks, Inc.

  • Page 49: Media Flow Controller Hierarchical Caching

    Media Flow Controller Administrator’s Guide Media Flow Controller Overview Media Flow Controller Hierarchical Caching When Media Flow Controller fetches data from origin upon cache miss, it caches the data in its local disks. Media Flow Controller implements an hierarchical caching mechanism that allows it to serve up to 10Gbps of data with just 16GB of RAM and a combination of SSD, SAS, and SATA storage.

  • Page 50: Media Flow Controller Assuredflow

    1. A new connection is rejected if the incoming interface is already serving at its bandwidth limit. 2. After a new connection is accepted, the first GET request can be rejected (with an HTTP error code) during various stages of processing: Media Flow Controller AssuredFlow Copyright © 2010, Juniper Networks, Inc.

  • Page 51: Media Flow Controller Smoothflow

    Media Flow Controller SmoothFlow SmoothFlow™ refers to the Quality of Experience (QoE) feature that Juniper Networks Media Flow Controller can provide to viewers for uninterrupted video viewing. Last-mile bandwidth fluctuations can cause buffering, or long pauses. Juniper Networks...

  • Page 52: How Smoothflow Works

    As the assets are delivered to the client players over the delivery channel, feedback hints to SmoothFlow are sent over the control channel telling Media Flow Controller when to switch to a different bit-rate profile. Media Flow Controller SmoothFlow Copyright © 2010, Juniper Networks, Inc.

  • Page 53: Media Flow Controller Network Connection

    Media Flow Controller Administrator’s Guide Media Flow Controller Overview Media Flow Controller Network Connection network connection CLI commands let you specify how requests are handled. These are global values and may be overridden by namespace custom virtual-player settings. You can specify an assured-flow-rate, how many concurrent sessions to allow (Media Flow Controller can support up to 40,000 concurrent sessions), the idle timeout for a connection, and max-bandwidth (the maximum allowable bandwidth) for any one given session.

  • Page 54: Type Generic

    Type yahoo The type yahoo (formerly type 3) virtual player includes assured-flow, connection max- bandwidth, and seek options (see Type generic for details) as well as these special options: Media Flow Controller Virtual Player Functions Copyright © 2010, Juniper Networks, Inc.

  • Page 55: Type Smoothflow

    Media Flow Controller Administrator’s Guide Media Flow Controller Overview • —Configure an external server to do health checks by making Media Flow health-probe Controller fetch data from origin and play it to the server initiating the health check. The signal that a given HTTP request is for a health probe is the health-probe query-string- parm name.

  • Page 56: Encoding Schemes

    Using Media Flow Manager, you can remotely manage individual Media Flow Controllers, or you can group Media Flow Controllers, and remotely apply saved configurations, called “profiles.” For details, see the Media Flow Manager™ Administrator’s Guide and CLI Command Reference. Media Flow Controller Media Flow Manager Functions Copyright © 2010, Juniper Networks, Inc.

  • Page 57: Media Flow Controller Configuration Tasks (Cli)

    “Rebooting Media Flow Controller (CLI)” on page 105 • “Upgrading Media Flow Controller (CLI)” on page 105 • “Configuring the Web Interface (CLI)” on page 106 • “Configuring the Web Interface Proxy (CLI)” on page 107 Copyright © 2010, Juniper Networks, Inc.

  • Page 58: Before You Configure Media Flow Controller

    • “Media Flow Controller Functions Overview” on page 45 About the Media Flow Controller CLI The Juniper Networks Media Flow Controller™command line interface (CLI) supports industry-standard commands for configuration and management as well as Media Flow Controller specific commands. The CLI supports command-line editing: press the up arrow to repeat previous lines, and the left arrow to edit the current line.

  • Page 59: Connecting And Logging In

    Media Flow Controller Administrator’s Guide Media Flow Controller Configuration Tasks (CLI) Connecting and Logging In You can connect to the CLI with SSH, Telnet (after enabled; Telnet is disabled by default), or serial console using the IP address of your Media Flow Controller. The Media Flow Controller responds with a login prompt.

  • Page 60: Prompt And Response Conventions

    Some settings, such as the terminal length and width, are inherently session-specific, and there are no corresponding commands to set defaults. Also, some commands are only available in default form. About the Media Flow Controller CLI Copyright © 2010, Juniper Networks, Inc.

  • Page 61: Logging In To Media Flow Controller For The First Time (Cli)

    Media Flow Controller Administrator’s Guide Media Flow Controller Configuration Tasks (CLI) Logging In to Media Flow Controller for the First Time (CLI) Before you log in to Media Flow Controller for the first time, see “Before You Configure Media Flow Controller” on page To log into the system command line interface (CLI) for the first time, you need the IP address assigned the management interface.

  • Page 62: Cutting And Pasting An Interface Configuration (Cli)

    Media Flow Controller Configuration Tasks (CLI) Media Flow Controller Administrator’s Guide To configure Media Flow Controller interfaces, hostname, domain list, DNS, and default gateway: 1. Configure interface IP addresses for management (eth0), and origin fetch (eth1). Later, use the delivery protocol commands to configure traffic interfaces as needed (described “Media Flow Controller Policy Configurations Overview”).

  • Page 63: Example: Media Flow Controller Interface Configuration

    Media Flow Controller Administrator’s Guide Media Flow Controller Configuration Tasks (CLI) Example: Media Flow Controller Interface Configuration When Media Flow Controller initializes, the on-board Ethernet interfaces are numbered Eth0, Eth1, and so on. When a NIC, dual- or quad- port, is attached to the server, the 1st NIC (goes by PCI channel number) gets interface names Eth10, Eth11, and so on to Eth19.

  • Page 64: Configuring Media Flow Controller System Clock And Banners (Cli)

    Alternately, configure the system clock, and timezone. Use show clock to verify. clock set <hh:mm:ss> [<yyyy/mm/dd>] clock timezone <zone> [<zone_word>] [<zone_word>] ... Example: test-vos (config) # clock set 15:51:30 Configuring Media Flow Controller System Clock and Banners (CLI) Copyright © 2010, Juniper Networks, Inc.

  • Page 65: Creating And Configuring Link Bonding And Static Routes (Cli)

    Media Flow Controller Administrator’s Guide Media Flow Controller Configuration Tasks (CLI) test-vos (config) # clock timezone America North United_States Pacific 2. Optionally, configure banners. There are two configurable banners: motd (message of the day) and login. In the CLI, both are displayed at the command line when you log in; in the Management Console, only the login message is displayed, on the login page.

  • Page 66: Configuring Link Bonding And Static Routes (Cli)

    (config) # delivery protocol http listen port 80 81 82 test-vos (config) # show bonds Bonded Interface 0: Enabled: Mode: balance-rr Link Monitor Time: Interfaces: eth10 eth11 Creating and Configuring Link Bonding and Static Routes (CLI) Copyright © 2010, Juniper Networks, Inc.

  • Page 67: Authentication / Authorization And Users Options

    Media Flow Controller Administrator’s Guide Media Flow Controller Configuration Tasks (CLI) 4. Configure the IP address for the bonded interface. test-vos (config) # interface 0 <IP_address> 5. Optionally, configure static routes and ensure a static host mapping for the defined hostname.

  • Page 68: User Account Defaults And States

    The admin and monitor accounts begin in this state (unless overridden by configured defaults), but should be changed for better security. username foo nopassword Authentication / Authorization and Users Options Copyright © 2010, Juniper Networks, Inc.

  • Page 69: Configuring Media Flow Controller User Accounts (Cli)

    Media Flow Controller Administrator’s Guide Media Flow Controller Configuration Tasks (CLI) Configuring Media Flow Controller User Accounts (CLI) Before you configure Media Flow Controller user accounts, see “Before You Configure Media Flow Controller” on page You may want to configure user accounts to allow multiple administrators to make configuration changes, or to allow certain people to view or monitor the appliance.

  • Page 70: Enabling Media Flow Controller Cmc Client Rendezvous (Cli)

    8. All Media Flow Controllers are enabled for CMC management by default. To disable this and ensure that this Media Flow Controller cannot be managed by CMC: no cmc client enable Enabling Media Flow Controller CMC Client Rendezvous (CLI) Copyright © 2010, Juniper Networks, Inc.

  • Page 71: Applying The Media Flow Controller License (Cli)

    Controller license for normal operations. You need to provide the node ID, which is the MAC address of Eth0 interface; use show interface eth0 to find the hardware (HW MAC) address. Based on this Juniper Networks will provide you a license key. After installing the license you get full feature capability. See license for CLI details.

  • Page 72: Media Flow Controller Policy Configurations Overview

    (zero), means assured flow is disabled (no minimum rate is provisioned). See “Media Flow Controller AssuredFlow” on page 50 for detailed description. network connection assured-flow-rate {0 | <kbps>} Media Flow Controller Policy Configurations Overview Copyright © 2010, Juniper Networks, Inc.

  • Page 73: Configuring Media Flow Controller Delivery Protocol (Cli)

    Media Flow Controller Administrator’s Guide Media Flow Controller Configuration Tasks (CLI) Important! Configure global network concurrent session limit; default is 10 (without Media Flow Controller license), 5000 (with Media Flow Controller license). The Media Flow Controller license changes the default. network connection concurrent session {5000 | <integer>} 3.

  • Page 74: Creating And Configuring Virtual Players (Cli)

    You may want to create a virtual player for each type of video you deliver; for example, if you deliver YouTube® videos, create a type youtube virtual-player for use in the corresponding namespace. Media Flow Controller virtual players support and complement client-side video Creating and Configuring Virtual Players (CLI) Copyright © 2010, Juniper Networks, Inc.

  • Page 75: Using Query-String-Parm

    • “Configuring YouTube Video Caching (CLI)” on page 199 Note! Media Flow Controller provides an API you can use to create custom virtual players. For more information, contact Juniper Networks Customer Support; see “Requesting Technical Support” on page Note! In Release 2.0.4, the show options command ? (question mark), lists all virtual player options no matter what virtual player type you are configuring;...

  • Page 76: Using Hash-Verify

    (1000Kbps) is applied. The configured CLI looks like this: virtual-player my_virtual_player type qss-streamlet rate-map match 01 rate 300 rate-map match 02 rate 500 rate-map match 03 rate 1000 Creating and Configuring Virtual Players (CLI) Copyright © 2010, Juniper Networks, Inc.

  • Page 77: Using Virtual Player Type Youtube

    Media Flow Controller Administrator’s Guide Media Flow Controller Configuration Tasks (CLI) In this way, URLs containing 01 in the correct place (12 bytes from the end) map to an assured flow rate of 300; with 02 the assured flow rate is 500; and so on. Defaults are: Match: 00 Rate: 150 kbps Match: 01...

  • Page 78: Example: Configuring Generic Virtual Player (Cli)

    0 (zero) means no throughput at all. After a value is entered, this parameter is enabled. See “Media Flow Controller AssuredFlow” on page 50 for more information. assured-flow {auto | query-string-parm <string> | rate <kbps>} Creating and Configuring Virtual Players (CLI) Copyright © 2010, Juniper Networks, Inc.

  • Page 79: Creating And Configuring Server-Maps (Cli)

    Media Flow Controller Administrator’s Guide Media Flow Controller Configuration Tasks (CLI) 5. Optionally, configure connection max-bandwidth delivery optimization. Default is 0 (unbounded) with the Media Flow Controller license, 200 kbps without it; you must have the license to change the unlicensed default. Use no connection to reset default. connection max-bandwidth {0 | <kbps>} 6.

  • Page 80: Using Server-Map For Origin Escalation

    To allow origin escalation (try another defined origin if the first fails), set format-type origin-escalation-map. To use NFS publishing points for origin, set format- type nfs-map. For cluster-map and origin-escalation-map only, you can define and add Creating and Configuring Server-Maps (CLI) Copyright © 2010, Juniper Networks, Inc.

  • Page 81: Creating A Namespace And Setting Namespace Options (Cli)

    Media Flow Controller Administrator’s Guide Media Flow Controller Configuration Tasks (CLI) 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>...

  • Page 82: Using Namespace Cache-Inherit

    This section provides some examples of namespace domain regex use. Change specifics accordingly. Note! Regex entries do not contain spaces; also, enclose all regex entries in single quotes (not shown in examples). See Table Creating a Namespace and Setting Namespace Options (CLI) Copyright © 2010, Juniper Networks, Inc.

  • Page 83: Using Namespace Domain

    Media Flow Controller Administrator’s Guide Media Flow Controller Configuration Tasks (CLI) Table 8 Example namespace domain regex entries Regex Matches www.example.com www.example.com|example.com example.com .*example.com abcdef02.origin.cms.example.com:80 ^[a-f,0-9]{8}\.(origin\.|cdn\.)?cms\.example\.com:80$ abcdef02.cdn.cms.example.com:80 abcdef02.cms.example.com:80 cms123.dc2.example.com:80 ^cms[0-9]{3}\.(dc2|qcg7)\.example\.com:80$ cms123.qcg7.example.com:80 orig.sv1.example.com:80 ^orig.(sv1|qcg1|qcg5)\.example\.com:80$ orig.qcg1.example.com:80 orig.qcg5.example.com:80 ^(cms[0-9]{3}).*(qcg[0-9]+|sv1|ch1|dc2|af1)\.example\.com:80$ cms123.x.y.qcg0.example.com:80 cms123.x.y.qcg01.example.com:80 cms123.x.y.sv1.example.com:80 cms123.x.y.ch1.example.com:80 cms123.x.y.dc2.example.com:80 cms123.x.y.af1.example.com:80 Using namespace domain <FQDN:Port>...

  • Page 84: Using Namespace Match Uri Regex

    All three URLs match namespace ns3 set domain (a.com) and match uri / (slash). In order to ensure that match uri #1 (/abc/def) maps to ns1 and not ns3, set the precedence value. Creating a Namespace and Setting Namespace Options (CLI) Copyright © 2010, Juniper Networks, Inc.

  • Page 85: Using Namespace Delivery Protocol Origin-Fetch Cache-Age

    Media Flow Controller Administrator’s Guide Media Flow Controller Configuration Tasks (CLI) Same as the case with match uri #2 (/abc), to map to ns2. Only match uri 3 ( / )should be mapped to ns3 with the precedence value configured as shown. Note! Excessive use of precedence has performance impact as precedence allows for longest prefix matching.

  • Page 86: Using Namespace Object Delete | List

    <name> match uri <uri-prefix> origin-server rtsp <IP_address | hostname> [port] status active delivery protocol rtsp exit live-pub-point <pp_ name> receive-mode on-demand status active exit exit Creating a Namespace and Setting Namespace Options (CLI) Copyright © 2010, Juniper Networks, Inc.

  • Page 87: Using Namespace For Live Streaming Delivery With Caching

    Media Flow Controller Administrator’s Guide Media Flow Controller Configuration Tasks (CLI) Using namespace for Live Streaming Delivery With Caching An example namespace configuration to deliver live streaming objects with caching is given; the delivery protocol and live-pub-point commands both enter you to prefix mode. namespace <name>...

  • Page 88: Example: Transparent Proxy Namespace Configuration

    The value shown for origin-fetch content-store media object-size is only a recommendation; default value is 0 (zero). namespace tproxy match uri / precedence 1 origin-server http follow dest-ip use-client-ip Creating a Namespace and Setting Namespace Options (CLI) Copyright © 2010, Juniper Networks, Inc.

  • Page 89: Using Namespace Match Virtual-Host

    Media Flow Controller Administrator’s Guide Media Flow Controller Configuration Tasks (CLI) proxy-mode transparent on-ip <IP_address_of_your_interface> delivery protocol http origin-request x-forwarded-for disable origin-request host-header inherit incoming-req permit origin-fetch content-store media object-size 32768 status active exit exit Using namespace match virtual-host You can specify a virtual host for the namespace match criteria; see Virtual Host definition.
  • Page 90 {deny | permit} • origin-request—(http only) Optionally, configure parameters for data requested from origin. See (namespace) delivery protocol http origin-request for CLI details. Creating a Namespace and Setting Namespace Options (CLI) Copyright © 2010, Juniper Networks, Inc.
  • Page 91 Media Flow Controller Administrator’s Guide Media Flow Controller Configuration Tasks (CLI) Note! Set origin-request host-header inherit incoming-req in accordance with the origin-server setting; see Table 10, “Namespace origin-server and origin-request Dependencies per Proxy Deployment for CLI details. Use x-forwarded-for to allow (with enable) or disallow (with disable) setting the X-Forwarded-For header to the client IP address;...

  • Page 92: Managing The Media Flow Controller Disk Cache (Cli)

    6 times, it is promoted to Tier1. • “Analyzing the Disk Cache” on page 93 • “Disk Cache Problems” on page 94 • “Replacing Bad Disks” on page 95 Managing the Media Flow Controller Disk Cache (CLI) Copyright © 2010, Juniper Networks, Inc.

  • Page 93: Analyzing The Disk Cache

    Media Flow Controller Administrator’s Guide Media Flow Controller Configuration Tasks (CLI) Analyzing the Disk Cache When Media Flow Controller is having caching issues, you want to check the disk cache. To analyze the media disk cache: 1. Get system-assigned disk names to use in configuration. Use list to view all disk drives, their names, physical location, serial number, type, and capacity.

  • Page 94: Disk Cache Problems

    DM2_MGMT_STATE_CACHEABLE = "disk cacheable, but cache not enabled" DM2_MGMT_STATE_INVAL_FORMAT_BEFORE_MOUNT and DM2_MGMT_STATE_FORMAT_UNKNOWN_AFTER_MOUNT = "disk has wrong format hence not cacheable" DM2_MGMT_STATE_DEACTIVATED = "disk has been deactivated"; DM2_MGMT_STATE_ACTIVATED = "disk has been activated"; Managing the Media Flow Controller Disk Cache (CLI) Copyright © 2010, Juniper Networks, Inc.

  • Page 95: Replacing Bad Disks

    Media Flow Controller Administrator’s Guide Media Flow Controller Configuration Tasks (CLI) DM2_MGMT_STATE_IMPROPER_UNMOUNT and DM2_MGMT_STATE_IMPROPER_MOUNT = "soft disk error, try to clear" DM2_MGMT_STATE_CACHE_RUNNING = "cache running"; DM2_MUST_FORMAT = “Disk Cache Enable Failed - Disk Cache must be formatted before enabling” DEFAULT = "unknown state, please try again a little later"; When a disk cache error is displayed, a first step to take is bringing down the disk and bringing it back up;...
  • Page 96 The documented disk replacement procedure for replacing a bad disk on VXA Series works correctly provided that Media Flow Controller can still identify the disk (show media- cache disk list). Managing the Media Flow Controller Disk Cache (CLI) Copyright © 2010, Juniper Networks, Inc.

  • Page 97: Installing And Using Fms In Media Flow Controller (Cli)

    Media Flow Controller Administrator’s Guide Media Flow Controller Configuration Tasks (CLI) Installing and Using FMS in Media Flow Controller (CLI) Before you configure FMS in Media Flow Controller, see “Before You Configure Media Flow Controller” on page Media Flow Controller has the ability to work with Adobe Flash Media Server (FMS) to stream Flash videos over Real Time Messaging Protocol™...
  • Page 98 (y/n) Default [y]: n ----------- Install Action Summary ----------- WARNING: You have chosen to overwrite a previous installation. Installation directory = /nkn/adobe/fms Flash Media Server Port = 1935 Installing and Using FMS in Media Flow Controller (CLI) Copyright © 2010, Juniper Networks, Inc.

  • Page 99: Modifying And Restarting The Fms Service (Cli)

    Media Flow Controller Administrator’s Guide Media Flow Controller Configuration Tasks (CLI) Flash Media Admin Server Port = 1111 Administrative username = admin Administrative password = (suppressed) service owner = admin service user = admin service group = admin 12. Finish the installation. Proceed with the installation? (y/n/q): y Modifying and Restarting the FMS Service (CLI) You must manually configure two FMS files.

  • Page 100: Configuring The Fms Admin Console-First Time (Cli)

    When an RTMP request comes to FMS, it scans the configuration file in the application directory /fms/applications to find the requested file. You configure Media Flow Controller namespace to correspond with the configuration of VOD_DIR. Installing and Using FMS in Media Flow Controller (CLI) Copyright © 2010, Juniper Networks, Inc.
  • Page 101 Media Flow Controller Administrator’s Guide Media Flow Controller Configuration Tasks (CLI) Important! The configuration in FMS must match your FMS Media Flow Controller namespace configuration. • “Configuring FMS VOD (CLI)” on page 101 • “Configuring Namespace for FMS VOD (CLI)” on page 102 •...
  • Page 102 /secondpath Player2 requests file: application vod1 and file sample.flv vod2: Application.xml: <Streams>/;/nkn/mnt/fuse/thirdpath</Streams> name space match uri: /thirdpath Player3 requests file: application vod2 and file sample.flv Installing and Using FMS in Media Flow Controller (CLI) Copyright © 2010, Juniper Networks, Inc.

  • Page 103: Using Video Directories For Fms

    Media Flow Controller Administrator’s Guide Media Flow Controller Configuration Tasks (CLI) Configuring Multiple Namespaces and URIs for VOD—Method 2 Have only one application and use the client player to provide different file paths that map to different namespaces. vod: Application.xml: <Streams>/;/nkn/mnt/fuse</Streams> player1 requests file: firstpath/sample.flv player2 requests file: secondpath/sample.flv player3 requests file: thirdpath/sample.flv...

  • Page 104: Administering Media Flow Controller Overview (Cli)

    (config) # configuration upload 04_01_09 scp://joe@example.com/ home/joe Password: ******* test-vos (config) # configuration delete 04_01_09 test-vos (config) # show configuration files initial (active) initial.bak test-vos (config) # configuration fetch scp://joe@example.com/home/joe/ 04_01_09 Password: ******* Administering Media Flow Controller Overview (CLI) Copyright © 2010, Juniper Networks, Inc.

  • Page 105: Rebooting Media Flow Controller (Cli)

    Upgrading Media Flow Controller (CLI) When upgrades are available, Juniper Networks will broadcast the upgrade URL to use in this procedure. Upgrade preserves the current, saved, configurations; however, you may still want to save the current configuration to a file on another system by following the previous procedure.

  • Page 106: Configuring The Web Interface (Cli)

    30 minutes; timeout is the time after which a session expires, default is 900 seconds or 15 minutes. web session renewal <number_of_minutes> web session timeout <number_of_minutes> Configuring the Web Interface (CLI) Copyright © 2010, Juniper Networks, Inc.

  • Page 107: Configuring The Web Interface Proxy (Cli)

    Media Flow Controller Administrator’s Guide Media Flow Controller Configuration Tasks (CLI) Example: test-vos (config) # web auto-logout 9000 test-vos (config) # web http port 8080 test-vos (config) # web httpd listen interface eth0 test-vos (config) # web https port 443 test-vos (config) # web session renewal 60 test-vos (config) # web session timeout 9000 test-vos (config) #...
  • Page 108 Media Flow Controller Configuration Tasks (CLI) Media Flow Controller Administrator’s Guide Configuring the Web Interface Proxy (CLI) Copyright © 2010, Juniper Networks, Inc.
  • Page 109 “Managing the Media-Cache (Web Interface)” on page 186 • “Configuring Service Logging (Web Interface)” on page 187 • “Viewing Logs Overview” on page 189 • “Viewing the Dashboard” on page 192 • “Viewing Reports (Interface Statistics)” on page 195 Copyright © 2010, Juniper Networks, Inc.

  • Page 110: Media Flow Controller Configuration Tasks (Web Interface)

    • Unprivileged (unpriv): Can view all configurations but cannot change any configurations. Can view Dashboard and Reports, but cannot view Logs. Cannot log in as unpriv. About the Media Flow Controller Web Interface Copyright © 2010, Juniper Networks, Inc.

  • Page 111: Logging In To Media Flow Controller For The First Time (Web Interface)

    Media Flow Controller Administrator’s Guide Media Flow Controller Configuration Tasks (Web Interface) Related Topics • “How Media Flow Controller Works” on page 43 • “Media Flow Controller Functions Overview” on page 45 Logging In to Media Flow Controller for the First Time (Web Interface) Before you log in to Media Flow Controller for the first time, see “Before You Configure Media...

  • Page 112: Figure 8 Ez Config Tab Page Detail (Missing Enable Interfaces And Service Restart Areas)

    Media Flow Controller Configuration Tasks (Web Interface) Media Flow Controller Administrator’s Guide Figure 8 EZ Config Tab Page Detail (missing Enable Interfaces and Service Restart areas) Configuring Media Flow Controller for the First Time (Web Interface) Copyright © 2010, Juniper Networks, Inc.

  • Page 113: Configuring Media Flow Controller For The First Time (Web Interface)

    Media Flow Controller Administrator’s Guide Media Flow Controller Configuration Tasks (Web Interface) Setting the System Hostname (EZconfig) To set the system hostname using the EZconfig tab System Hostname area: 1. Enter information in the text boxes: • Host Name (FQDN)—Enter a FQDN hostname for the system. •...

  • Page 114: Adding A Namespace (Ezconfig)

    FTP settings, and mod-log for changes to logging settings. The mod-oom service (offline origin fetch manager) is provided for debugging purposes only. Configuring Media Flow Controller for the First Time (Web Interface) Copyright © 2010, Juniper Networks, Inc.

  • Page 115: Monitoring Media Flow Controller Statistics (Web Interface)

    Media Flow Controller Administrator’s Guide Media Flow Controller Configuration Tasks (Web Interface) Monitoring Media Flow Controller Statistics (Web Interface) The Monitoring tab gives you quick access to statistics and information about the current system, including bandwidth usage, namespace usage, CPU load, and more. Summary Page Purpose View statistics and graphs of the managed Media Flow Controllers;...

  • Page 116: Viewing Media Flow Controller Bandwidth Usage

    The Bandwidth Usage (Last Hour) page is displayed. • Click Pause and Resume buttons to stop/start graph charting. Figure 9 Monitoring > Bandwidth Usage (Last Hour) Chart Example Monitoring Media Flow Controller Statistics (Web Interface) Copyright © 2010, Juniper Networks, Inc.

  • Page 117: Viewing Media Flow Controller Namespace Counters

    Media Flow Controller Administrator’s Guide Media Flow Controller Configuration Tasks (Web Interface) Viewing Media Flow Controller Namespace Counters Purpose List the current configured namespaces and the current number of GET requests for each. Action • From the left navigation pane in the Monitoring tab, click Namespace. The Namespace Counters page is displayed.

  • Page 118: Viewing Network Usage

    The Network Usage (Last Hour) page is displayed. • Use Pause and Resume buttons to stop/start graph charting. Figure 11 Monitoring > Network Usage (Last Hour) Page Detail Monitoring Media Flow Controller Statistics (Web Interface) Copyright © 2010, Juniper Networks, Inc.

  • Page 119: Viewing Memory Utilization

    • Use Pause and Resume buttons to stop/start graph charting. Media Flow Controller System Configuration Overview You can configure many system settings for the Juniper Networks Media Flow Controller by using the System Config tab. To configure system settings: •...

  • Page 120: Figure 12 Network Interfaces Page Detail (Eth0 State And Eth0 Configuration)

    Media Flow Controller Configuration Tasks (Web Interface) Media Flow Controller Administrator’s Guide Figure 12 Network Interfaces Page Detail (eth0 state and eth0 configuration) eth0 state View the state of the eth0 interface, see Figure 12. To view the eth0 state area: Status (Admin up: The interface is enabled, Link up: The interface has a current connection), IP address, Netmask, Type, Speed, Duplex, MTU, HWaddr (hardware address), and a Comment (if configured) for each discovered interface.

  • Page 121: Configuring Interfaces, Default Gateway, Static Routes, Dns And Domain Names, Hostname And Banners (Web Interface)

    Media Flow Controller Administrator’s Guide Media Flow Controller Configuration Tasks (Web Interface) • Specify IP Address Manually—Enter the IP address and Netmask you want for this Media Flow Controller. • Speed and Duplex—Choose Auto (default) for the Speed and Duplex to be set automatically based on hardware.

  • Page 122: Setting The Default Gateway And Static Routes (Web Interface)

    Media Flow Controller Configuration Tasks (Web Interface) Media Flow Controller Administrator’s Guide Add new interface alias An interface alias lets you assign multiple IP addresses to the same interface. See Figure 14 for a graphic. Figure 14 Network Interfaces Page Detail (Add new interface alias) To add a new interface alias: 1.

  • Page 123: Figure 15 Ip Routing Page

    Media Flow Controller Administrator’s Guide Media Flow Controller Configuration Tasks (Web Interface) Figure 15 IP Routing Page Default Gateway Set the default gateway as the main access point to external networks, including the Internet. To set the default gateway: 1. Enter an IP address in the Default gateway text box and click Set Default Gateway to immediately apply changes.

  • Page 124: Configuring Dns And Domain Names (Web Interface)

    Media Flow Controller Configuration Tasks (Web Interface) Media Flow Controller Administrator’s Guide • Interface—The port configured for this static route. • Active—Whether or not this route is being used currently. • Static—Whether or not this route is static (hard coded). Select a route and click Removed Selected to immediately apply changes;...

  • Page 125: Figure 16 Dns Page Detail (Add Or Modify Name Servers)

    Media Flow Controller Administrator’s Guide Media Flow Controller Configuration Tasks (Web Interface) Figure 16 DNS Page Detail (Add or Modify Name Servers) Configuring Interfaces, Default Gateway, Static Routes, DNS and Domain Names, Hostname and Banners (Web...
  • Page 126 Media Flow Controller Configuration Tasks (Web Interface) Media Flow Controller Administrator’s Guide Static and Dynamic Name Servers View all configured static and dynamic name servers: • IP Address—Of the configured name server. • Active—Whether or not this name server is being used currently. •...

  • Page 127: Setting Hostnames And Banners (Web Interface)

    Media Flow Controller Administrator’s Guide Media Flow Controller Configuration Tasks (Web Interface) Setting Hostnames and Banners (Web Interface) View or change the System Hostname and the DHCP Hostname (Dynamic Host Configuration Protocol), and set Banners. You can set a MOTD (message of the day), a Login Remote, and a Login Local banner.
  • Page 128 Media Flow Controller Configuration Tasks (Web Interface) Media Flow Controller Administrator’s Guide System Hostname To configure a hostname for the system: 1. Enter a name in the Host Name text box and click Apply to immediately apply changes; Cancel to revert to existing configuration. 2.

  • Page 129: Configuring Static Hosts And Arp (Web Interface)

    Media Flow Controller Administrator’s Guide Media Flow Controller Configuration Tasks (Web Interface) Configuring Static Hosts and ARP (Web Interface) Before you configure Media Flow Controller static hosts and ARP, see “Before You Configure Media Flow Controller” on page Configuring Static Hosts Set static host entries;...

  • Page 130: Configuring Arp (Web Interface)

    MAC address—The physical address of this entry. • Interface—The port configured for this entry. • Active—Whether or not this entry is being used currently. • Static—Whether or not this entry comes from DNS. Configuring Static Hosts and ARP (Web Interface) Copyright © 2010, Juniper Networks, Inc.

  • Page 131: Configuring Date, Time, And Ntp (Web Interface)

    Media Flow Controller Administrator’s Guide Media Flow Controller Configuration Tasks (Web Interface) 2. Click Remove Selected to delete an entry. 3. Click Save at the top of the page to make changes persistent. Add Static Entry Add entries to the ARP cache as a static entry. See Figure To add a static ARP entry: 1.

  • Page 132: Configuring Ntp (Web Interface)

    To configure NTP servers: • From the left navigation pane in the System Config tab, select NTP. The NTP page is displayed. See Figure Figure 21 NTP Page Configuring Date, Time, and NTP (Web Interface) Copyright © 2010, Juniper Networks, Inc.
  • Page 133 Media Flow Controller Administrator’s Guide Media Flow Controller Configuration Tasks (Web Interface) NTP Setup Set NTP synchronization. See Figure To enable/disable NTP time synchronization: 1. Select the checkbox to enable NTP; de-select it to disable NTP. 2. Click Apply to complete enabling NTP, Cancel to revert to existing configuration. 3.

  • Page 134: Configuring Radius, Tacacs+, And Ssh (Web Interface)

    To configure RADIUS: • From the left navigation pane in the System Config tab, select RADIUS. The RADIUS page is displayed. See Figure Configuring RADIUS, TACACS+, and SSH (Web Interface) Copyright © 2010, Juniper Networks, Inc.

  • Page 135: Figure 22 Radius Page

    Media Flow Controller Administrator’s Guide Media Flow Controller Configuration Tasks (Web Interface) Figure 22 RADIUS Page Default RADIUS Settings Configure Default RADIUS Settings. See Figure 22. To configure default RADIUS settings: 1. Enter this information to the text boxes: • Key—A shared secret text string.

  • Page 136: Configuring Tacacs+ (Web Interface)

    Configure TACACS+ authentication options. To configure TACACS+: • From the left navigation pane in the System Config tab, select TACACS+. The TACACS+ page is displayed. See Figure Configuring RADIUS, TACACS+, and SSH (Web Interface) Copyright © 2010, Juniper Networks, Inc.

  • Page 137: Figure 23 Tacacs+ Page

    Media Flow Controller Administrator’s Guide Media Flow Controller Configuration Tasks (Web Interface) Figure 23 TACACS+ Page Default TACACS+ Settings Configure Default TACACS+ Settings. See Figure To configure default TACACS+: 1. Enter this information to the text boxes: • Key—A shared secret text string. If no key is set, the user is prompted for the key. •...

  • Page 138: Configuring Ssh (Web Interface)

    Configure Secure Sockets Shell (SSH) transmissions. SSH is protocol to secure connections through an encryption known to the server and the client. The encryption operates via Host Configuring RADIUS, TACACS+, and SSH (Web Interface) Copyright © 2010, Juniper Networks, Inc.

  • Page 139: Configuring Users And Aaa (Web Interface)

    Media Flow Controller Administrator’s Guide Media Flow Controller Configuration Tasks (Web Interface) Keys, a secret string configured on the server and communicated to an authenticated client. for CLI details. To configure SSH: • From the left navigation pane in the System Config tab, select SSH. The SSH page is displayed.

  • Page 140: Configuring Users (Web Interface)

    From the left navigation pane in the System Config tab, select Users. The Users page is displayed. See Figure Figure 25 Users Page Detail (additional Password areas are displayed for each user) Configuring Users and AAA (Web Interface) Copyright © 2010, Juniper Networks, Inc.
  • Page 141 Media Flow Controller Administrator’s Guide Media Flow Controller Configuration Tasks (Web Interface) Active Users View configured users information. See Figure 25. To view user information: • Username—Used for logins. • Full Name—For the user, as configured. • Line—How the user is connected, SSH or Web. •...

  • Page 142: Configuring Aaa (Web Interface)

    The authentication methods must be configured. 2. Click Apply to complete operation; Cancel to revert to existing configuration. 3. Click Save at the top of the page to make changes persistent across reboots. Configuring Users and AAA (Web Interface) Copyright © 2010, Juniper Networks, Inc.

  • Page 143: Configuring Snmp, Faults, And Logging (Web Interface)

    Media Flow Controller Administrator’s Guide Media Flow Controller Configuration Tasks (Web Interface) Authorization Set authorization options. See Figure To set authorization: 1. Choose a Map Order— How the remote user mapping behaves when authenticating users via RADIUS or TACACS+. If the authenticated user name is valid locally, no mapping is performed.

  • Page 144: Figure 27 System Config > Snmp Page

    • Enable Communities—Enable or disable (by un-checking) community-based authentication on this system; the SNMP "public" community is enabled by default. If disabled, the community configured is ignored. Configuring SNMP, Faults, and Logging (Web Interface) Copyright © 2010, Juniper Networks, Inc.

  • Page 145: Configuring Fault Reporting (Web Interface)

    Media Flow Controller Administrator’s Guide Media Flow Controller Configuration Tasks (Web Interface) • Enable Traps—Enable or disable (by un-checking) sending SNMP traps from this system. The SNMP server must be enabled first. See snmp traps for details. 2. Enter this information to the text boxes: •...

  • Page 146: Figure 28 Faults Page

    1. Enter this information to the text boxes: • SMTP server—Use a hostname or IP address to set the mail relay (mailhub in the CLI) to use to send notification emails. Configuring SNMP, Faults, and Logging (Web Interface) Copyright © 2010, Juniper Networks, Inc.
  • Page 147 Media Flow Controller Administrator’s Guide Media Flow Controller Configuration Tasks (Web Interface) • Domain name override—Use a hostname or IP address to set the domain name from which emails are to appear to come (provided that the return address is not already fully-qualified).

  • Page 148: Configuring System Logging (Web Interface)

    It does not record service activity or errors. The Media Flow Controller errorlog records service related errors but is mostly useful for debugging by Juniper Networks Support. Media Flow Controller provides several service-specific logs, detailed in ”Chapter 9, “Media Flow Controller Troubleshooting.”...

  • Page 149: Figure 29 Logging Page Detail (Does Not Show Log Format Area)

    Media Flow Controller Administrator’s Guide Media Flow Controller Configuration Tasks (Web Interface) Figure 29 Logging Page Detail (does not show Log Format area) Configuring SNMP, Faults, and Logging (Web Interface)
  • Page 150 Force Rotation to immediately generate a syslog file and start logging over. 4. Click Save at the top of the page to make changes persistent across reboots. Configuring SNMP, Faults, and Logging (Web Interface) Copyright © 2010, Juniper Networks, Inc.

  • Page 151: Figure 30 Logging Page Detail (Log Format)

    Media Flow Controller Administrator’s Guide Media Flow Controller Configuration Tasks (Web Interface) Remote Log Sinks View and delete configured log sinks (remote servers receiving log messages from this system). See Figure 1. View this information: • Remote Sink—Address of configured Remote Sink. •...

  • Page 152: Administering Media Flow Controller Overview

    From the left navigation pane in the System Config tab, select Config Mgmt. The Configurations page is displayed. See Figure Figure 31 System Config > Configurations Page Detail (Configuration Files) Administering Media Flow Controller Overview Copyright © 2010, Juniper Networks, Inc.
  • Page 153 Click Save As to save the active configuration as a new file; enter a name in the New filename text box. 2. Click Save at the top of the page to make changes persistent across reboots. Copyright © 2010, Juniper Networks, Inc.

  • Page 154: Figure 32 System Config > Configurations Page Detail (Configuration Files)

    Remote Config Name—File name of the desired configuration. • New Config Name—A new name for the imported configuration (optional). • Import shared data only—Uncheck to import all nodes, even those not available on this system. Copyright © 2010, Juniper Networks, Inc.

  • Page 155: Installing Licenses (Web Interface)

    Media Flow Controller Administrator’s Guide Media Flow Controller Configuration Tasks (Web Interface) 2. Click Import Configuration. Figure 34 System Config > Configurations Page Detail (Import Configuration) Installing Licenses (Web Interface) Use this page to view and remove installed licenses, and add new licenses. To manage licensing: •...

  • Page 156: Upgrading The System (Web Interface)

    From the left navigation pane in the System Config tab, select Upgrade. The Upgrades and Imaging page is displayed. See Figure Figure 36 System Config > Upgrade Page Detail (Installed Images) Installed Images Manage installed images. See Figure Upgrading the System (Web Interface) Copyright © 2010, Juniper Networks, Inc.

  • Page 157: Rebooting The System (Web Interface)

    Media Flow Controller Administrator’s Guide Media Flow Controller Configuration Tasks (Web Interface) To manage installed images: 1. View the images installed on the two boot partitions. 2. Click Switch Boot Partition if the image you want to install is in the other partition. 3.

  • Page 158: Configuring The Web Interface (Web Interface)

    2. Click Apply to complete operation; Cancel to revert to existing configuration. You can also Generate New HTTPS Certificate by clicking that button. 3. Click Save at the top of the page to make changes persistent across reboots. Configuring the Web Interface (Web Interface) Copyright © 2010, Juniper Networks, Inc.

  • Page 159: Configuring The Web Interface Proxy (Web Interface)

    Media Flow Controller Administrator’s Guide Media Flow Controller Configuration Tasks (Web Interface) Figure 38 Web Settings Page Detail (Web UI Configuration) Configuring the Web Interface Proxy (Web Interface) Configure the Web interface proxy, if needed. See Figure To set parameters for the Media Flow Controller Web interface when proxied: 1.

  • Page 160: Configuring Central Management Console Access (Web Interface)

    CMC client parameters. To configure CMC Access: • From the left navigation pane in the System Config tab, select CMC. The CMC Clients page is displayed. See Figure Configuring Central Management Console Access (Web Interface) Copyright © 2010, Juniper Networks, Inc.

  • Page 161: Figure 40 Cmc Clients Page

    Media Flow Controller Administrator’s Guide Media Flow Controller Configuration Tasks (Web Interface) Figure 40 CMC Clients Page Enable Configuration Changes If this Media Flow Controller is already managed by a CMC server, this area is displayed to allow you to temporarily override the CMC management and Enable configurations. See Figure Figure 41 CMC Clients Page Detail (Enable Configuration Changes)

  • Page 162: Service Configurations Overview

    “Configuring the Delivery Network (Web Interface)” on page 163 • “Configuring Delivery Protocols (Web Interface)” on page 164 • “Configuring Virtual Players (Web Interface)” on page 167 • “Configuring NameSpaces (Web Interface)” on page 179 Service Configurations Overview Copyright © 2010, Juniper Networks, Inc.

  • Page 163: Configuring The Delivery Network (Web Interface)

    Media Flow Controller Administrator’s Guide Media Flow Controller Configuration Tasks (Web Interface) • “Managing the Media-Cache (Web Interface)” on page 186 • “Configuring Service Logging (Web Interface)” on page 187 Configuring the Delivery Network (Web Interface) Set global network connection parameters; they may be overridden by a defined virtual player. To configure delivery network options: •...

  • Page 164: Configuring Delivery Protocols (Web Interface)

    To configure the HTTP delivery protocol: • From the left navigation pane in the Service Config tab, select Delivery Protocol. The Delivery Protocol Configuration page is displayed. See Figure Configuring Delivery Protocols (Web Interface) Copyright © 2010, Juniper Networks, Inc.

  • Page 165: Figure 43 Delivery Protocol Configuration Page

    Media Flow Controller Administrator’s Guide Media Flow Controller Configuration Tasks (Web Interface) Figure 43 Delivery Protocol Configuration Page Configuring Delivery Protocols (Web Interface)

  • Page 166: Set Http Listen Port

    1. Select the checkbox for the port you want to remove. Click Remove Selected Port. 2. Click Save at the top of the page to make changes persistent across reboots. Configuring Delivery Protocols (Web Interface) Copyright © 2010, Juniper Networks, Inc.

  • Page 167: Configuring Virtual Players (Web Interface)

    Media Flow Controller Administrator’s Guide Media Flow Controller Configuration Tasks (Web Interface) Configuring Virtual Players (Web Interface) Create a virtual player and set virtual player options. To configure virtual players: • From the left navigation pane in the Service Config tab, select Virtual Player. The Virtual Player Configuration page is displayed.

  • Page 168: Virtual Player Generic Type Configuration

    Verify your configurations by clicking Show in the virtual player list. Figure 45 Virtual Player Type generic Configuration Page Configuring Virtual Players (Web Interface) Copyright © 2010, Juniper Networks, Inc.
  • Page 169 Media Flow Controller Administrator’s Guide Media Flow Controller Configuration Tasks (Web Interface) To configure a generic type virtual player: 1. Enter this information to the text boxes or select the checkbox as described: • Full Download Configuration: Allow the delivery to download content at the fastest possible speed, limited by the set connection max-bandwidth and possibly exceeding the set assured-flow rate.

  • Page 170: Virtual Player Break Type Configuration

    Verify your configurations by clicking Show in the virtual player list. Figure 46 Virtual Player Type break Configuration Page Configuring Virtual Players (Web Interface) Copyright © 2010, Juniper Networks, Inc.

  • Page 171: Virtual Player Qss-Streamlet Type Configuration

    Media Flow Controller Administrator’s Guide Media Flow Controller Configuration Tasks (Web Interface) To configure a break type virtual player: 1. Enter this information to the text boxes or select the checkbox as described: • Assured Flow Configuration • Active—Select to activate the feature; de-select to de-activate it. •...

  • Page 172: Figure 47 Virtual Player Type Qss-Streamlet Configuration Page

    UOL Length—Not supported in Release 2.0.4. • UOL Offset—Not supported in Release 2.0.4. 2. Click Add/Update. 3. Click Save at the top of the page to make changes persistent across reboots. Configuring Virtual Players (Web Interface) Copyright © 2010, Juniper Networks, Inc.

  • Page 173: Example: Rate Map Configuration

    Media Flow Controller Administrator’s Guide Media Flow Controller Configuration Tasks (Web Interface) Example: Rate Map Configuration By default, the match string (length 2 bytes) is extracted by going to the end of the URL and skipping 12 Bytes from the end. The value in that location is mapped to the configured rate in kbps.

  • Page 174: Figure 48 Virtual Player Type Yahoo Configuration Page

    URI Query String, Shared Secret String, Stream ID Query String Param, and Time Interval values. • Shared Secret String—String value to be hashed. • Stream ID Query String Param—String value to be hashed. • Time Interval—Integer value. Configuring Virtual Players (Web Interface) Copyright © 2010, Juniper Networks, Inc.

  • Page 175: Virtual Player Smoothflow Type Configuration

    Media Flow Controller Administrator’s Guide Media Flow Controller Configuration Tasks (Web Interface) • Health-Probe Configuration (See “Terminology” on page 30 for explanation and example of uol offset and uol length. See “Using hash-verify” on page 76 explanation). • Active—Select to activate the feature; de-select to de-activate it. •...

  • Page 176: Figure 49 Virtual Player Type Smoothflow Configuration Page

    Max Session Rate (kbps)—Set the maximum bandwidth for a session. The actual session bandwidth is between the AFR (Assured Flow Rate) and this value. Even if there is available bandwidth in the link, Media Flow Controller does not Configuring Virtual Players (Web Interface) Copyright © 2010, Juniper Networks, Inc.

  • Page 177: Virtual Player Youtube Type Configuration

    Media Flow Controller Administrator’s Guide Media Flow Controller Configuration Tasks (Web Interface) allocate more than this value for a session. When it is a full download, Media Flow Controller tries to allocate the max-bandwidth to the session. Default it is 0 Kbps (unbounded) with the Media Flow Controller license.
  • Page 178 When it is a full download, Media Flow Controller tries to allocate the max-bandwidth to the session. Default it is 0 Kbps Configuring Virtual Players (Web Interface) Copyright © 2010, Juniper Networks, Inc.

  • Page 179: Virtual Player Smoothstream-Pub Type Configuration

    Media Flow Controller Administrator’s Guide Media Flow Controller Configuration Tasks (Web Interface) (unbounded) with the Media Flow Controller license. Important! You must have the Media Flow Controller license installed to change the default (200 kbps without the license). • Assured Flow Configuration •...

  • Page 180: Add Namespace

    “Configuring Namespace Pre-Stage User (Web Interface)” on page 184 • “Configuring Namespace HTTP Origin Fetch (Web Interface)” on page 184 • “Configuring Namespace RTSP Origin Fetch (Web Interface)” on page 185 Configuring NameSpaces (Web Interface) Copyright © 2010, Juniper Networks, Inc.
  • Page 181 Media Flow Controller Administrator’s Guide Media Flow Controller Configuration Tasks (Web Interface) Configuring Namespace Origin Server (Web Interface) Configure fetching content upon a cache-miss. In Release 2.0.4 only one (1) origin server is supported (either HTTP or NFS); multiple origin servers can be configured using a server- map;...

  • Page 182: Figure 53 Service Config > Namespace Configure Page Detail (Origin Server Configuration)

    (defined above). • header-name and header-value • header-regex • Query-string—A header name and value; can also be a regex. Optionally, set a precedence (defined above). • query-name and query-value • query-regex Configuring NameSpaces (Web Interface) Copyright © 2010, Juniper Networks, Inc.

  • Page 183: Figure 54 Service Config > Namespace Configure Page Detail (Match Details)

    Media Flow Controller Administrator’s Guide Media Flow Controller Configuration Tasks (Web Interface) • Virtual-host—Enter the address and port (optional) of a virtual host. • virtual-IP and virtual-port—The IP address must be a /32 address; it can be 0.0.0.0, which means any IP address. 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.

  • Page 184: Figure 55 Service Config > Namespace Configure Page Detail (Parameters)

    Cache-Control: max-age = <seconds> header, and the Age header sent from origin is maintained). De-select to disable (default); Media Flow Controller does not reset the Date header. Configuring NameSpaces (Web Interface) Copyright © 2010, Juniper Networks, Inc.

  • Page 185: Figure 57 Service Config > Namespace Configure Page (Http Origin Fetch Configuration)

    Media Flow Controller Administrator’s Guide Media Flow Controller Configuration Tasks (Web Interface) • Cache Directive—Choose follow (default) to tell Media Flow Controller to obey the cache-directive (Cache-control : no-cache or Pragma: no-cache) in the HTTP header when data is fetched from the origin. Choose override to tell Media Flow Controller to always cache.

  • Page 186: Managing The Media-Cache (Web Interface)

    When a new HDD is in the disk, it must be made active and (if so decided) enabled for caching. Figure 59 Service Config > Media-Cache Page Detail Managing the Media-Cache (Web Interface) Copyright © 2010, Juniper Networks, Inc.

  • Page 187: Configuring Service Logging (Web Interface)

    Media Flow Controller Administrator’s Guide Media Flow Controller Configuration Tasks (Web Interface) Configuring Service Logging (Web Interface) Set Media Flow Controller Access Log and Stream Log options, including automatic upload. Access Log Configuration The Accesslog records each HTTP transaction going through Media Flow Controller. See “Service Log (accesslog)”...

  • Page 188: Stream Log Configuration

    CLI details on log formatting. 2. Click Apply. 3. Click Save at the top of the page to make changes persistent across reboots. Figure 62 Log Configuration Page Detail (Stream Log Configuration) Configuring Service Logging (Web Interface) Copyright © 2010, Juniper Networks, Inc.

  • Page 189: Stream Log Copy/Auto Download Configuration

    Media Flow Controller Administrator’s Guide Media Flow Controller Configuration Tasks (Web Interface) Stream Log Copy/Auto Download Configuration Set automatic downloading of the streamlog. See Figure To download the streamlog: 1. Enter this information to the text boxes: • URL—The URL to which the streamlog should be downloaded when it reaches the download trigger size, by default when filesize reaches 100MB;...

  • Page 190: Viewing The Service Log (Web Interface)

    Current log, that day’s activity. Download log—Opens a File Open dialog so you can save the trace log locally. Archived (does not display if not applicable) log (1 - n), past logs. Viewing Logs Overview Copyright © 2010, Juniper Networks, Inc.

  • Page 191: Viewing The Trace Log (Web Interface)

    Media Flow Controller Administrator’s Guide Media Flow Controller Configuration Tasks (Web Interface) Example: [Fri Jun 26 19:37:09.754 2009] ADD "/http-cl18:ed239a85/100k-files/117/29" SAS dc_3 32768 [Fri Jun 26 19:38:14 2009] Fields (display according to event type): [Date] Event_Type "<URI_name>" Cache_Tier_Name Cache_Name Content_Length_In_Bytes [Expiry_time_for_this_URI] Viewing the Trace Log (Web Interface) Media Flow Controller includes a delivery trace facility to help diagnose the handling of a particular HTTP request;...

  • Page 192: Viewing The Fmsedge Log (Web Interface)

    Number of Requests—Total number of objects delivered form RAM or Disk / Total number of objects delivered (irrespective of size). • Objects Delivered—The total number of objects served by this Media Flow Controller since running. Viewing the Dashboard Copyright © 2010, Juniper Networks, Inc.

  • Page 193: Figure 65 Media Flow Controller Dashboard Example

    Media Flow Controller Administrator’s Guide Media Flow Controller Configuration Tasks (Web Interface) Graphs (see Figure 65): • Active Sessions— Media Flow Controller connections to the client, background connections (for example, fetching from origin) is not shown here. • Weekly Bandwidth Savings—Saved bandwidth is bandwidth used by traffic that did not come from origin.

  • Page 194: Figure 66 Media Flow Controller Disk Cache Graph Example

    Media Flow Controller Configuration Tasks (Web Interface) Media Flow Controller Administrator’s Guide Figure 66 Media Flow Controller Disk Cache Graph Example Viewing the Dashboard Copyright © 2010, Juniper Networks, Inc.

  • Page 195: Viewing Reports (Interface Statistics)

    Media Flow Controller Administrator’s Guide Media Flow Controller Configuration Tasks (Web Interface) Viewing Reports (Interface Statistics) Network Usage Last 24 hours (example) Network Usage Last 7 days (example) Viewing Reports (Interface Statistics)
  • Page 196 Media Flow Controller Configuration Tasks (Web Interface) Media Flow Controller Administrator’s Guide Network Usage Daily Stats Last 7 Days of Activity (example) Network Usage Last 24 hours (example) Network Usage Last 7 days (example) Viewing Reports (Interface Statistics) Copyright © 2010, Juniper Networks, Inc.

  • Page 197: Media Flow Controller Common Configuration Tasks (Cli)

    2. Ping the default gateway to ensure connectivity. Ping your origin server with the FQDN. Use Ctrl+c to stop. ping <default_gateway> Ctrl+c ping <origin_server_FQDN> Ctrl+c Copyright © 2010, Juniper Networks, Inc. Configuring Caching All Contents for a Website (CLI)
  • Page 198 Cache-Directive: follow Object Size Threshold: NONE (Always Cached) Modify Date Header: deny Origin Request Configuration: Cache-Revalidate: permit Use 'Date' Header when Last-Modified is not present: no Configuring Caching All Contents for a Website (CLI) Copyright © 2010, Juniper Networks, Inc.

  • Page 199: Configuring Youtube Video Caching (Cli)

    Media Flow Controller Administrator’s Guide Media Flow Controller Common Configuration Tasks (CLI) Convert HEAD to GET: permit Host-header Inherit: deny Set X-Forwaded-For Header : yes Client-Request Configuration: Allow objects with a query-string to be cached: no Client-Response Configuration : Delivery Protocol: RTSP Status Enabled: no Origin Fetch Configuration: Cache-Age (Default): 28800 (seconds)

  • Page 200: Configuring Nfs Fetch For Images (Cli)

    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. Configuring NFS Fetch for Images (CLI) Copyright © 2010, Juniper Networks, Inc.

  • Page 201: Configuring Http Fetch For Videos (Cli)

    Media Flow Controller Administrator’s Guide Media Flow Controller Common Configuration Tasks (CLI) Configuring HTTP Fetch for Videos (CLI) Configuring Media Flow Controller to fetch all video files, located in a particular directory on the origin server, via HTTP, requires another namespace configuration. In this example, all requests for videos at www.example.com/videos/ that incur a cache miss (necessitating an origin fetch) are fetched from the specified origin using HTTP.

  • Page 202: Configuring Smoothflow Restricted By File Path (Cli)

    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. Configuring SmoothFlow Restricted by File Path (CLI) Copyright © 2010, Juniper Networks, Inc.

  • Page 203: Configuring The Snmp Agent (Cli)

    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: •...

  • Page 204: Configuring Media Flow Controller For Smoothflow (Cli)

    (for profile). See “virtual-player type smoothflow” on page 378 for further information on SmoothFlow states. signals session-id query-string-parm <string> state query-string-parm <string> profile query-string-parm <string> Configuring Media Flow Controller for SmoothFlow (CLI) Copyright © 2010, Juniper Networks, Inc.
  • Page 205 Media Flow Controller Administrator’s Guide Media Flow Controller Common Configuration Tasks (CLI) 4. Configure hash verification options. Note! In Release 2.0.4, only md-5 digest is supported. Set a shared secret value to be appended or prefixed to the URL as specified, for matching against the hash value provided in the URL and indicated by the match query-string-parm you configure.

  • Page 206: Configuring Smoothflow Namespaces (Cli)

    <name> | <FQDN/path [<port#>]} 8. Configure parameters for pre-staging content from origin; not needed for crossdomain namespace. Authentication schemes must be pre-configured to be used. The ftp user is Configuring Media Flow Controller for SmoothFlow (CLI) Copyright © 2010, Juniper Networks, Inc.
  • Page 207 Media Flow Controller Administrator’s Guide Media Flow Controller Common Configuration Tasks (CLI) auto-generated as <namespace>_ftpuser, without a password. Set the password here; this entry overrides a user <namespace>_ftpuser password setting. pre-stage ftp user <name> password {RADIUS | TACACS | <password> [encrypt]} 9.

  • Page 208: Using Ssh In Automated Scripts (Cli)

    <trusted_user>@<Media_Flow_Controller_appliance> "cli enable\"<command>\"" • To execute CLI commands in Configure mode, use this syntax: ssh <trusted_user>@<Media_Flow_Controller_appliance> "cli enable\"configure terminal\"\"<command>\"" Enter as many commands as needed following the syntax. Using SSH in Automated Scripts (CLI) Copyright © 2010, Juniper Networks, Inc.

  • Page 209: Configuring And Using Media Flow Controller Logs And Alarms

    “SNMP Alarms” on page 237 • “Configuring Media Flow Controller Fault Notifications (CLI)” on page 240 Note! The Web interface name for the log is given, and the command line interface (CLI) name is given in parentheses. Copyright © 2010, Juniper Networks, Inc.

  • Page 210: Log Codes And Sub-Codes

    Requested Range Not Satisfiable Parameter Not Understood Conference Not Found Not Enough Bandwidth Session Not Found Method Not Valid in This State Header Field Not Valid for Resource Invalid Range Log Codes and Sub-Codes Copyright © 2010, Juniper Networks, Inc.

  • Page 211: Status/Error Sub-Codes

    Media Flow Controller Administrator’s Guide Configuring and Using Media Flow Controller Logs and Alarms Table 11 Logging Status (%s) Codes (Continued) Code Description Parameter Is Read-Only Aggregate operation not allowed Only aggregate operation allowed Unsupported transport Destination unreachable Internal Server Error Not Implemented Bad Gateway Service Unavailable...

  • Page 212: Service Log (Accesslog)

    CLI details including format options. accesslog copy <SCP> filename {access.log | <string>} format <field1 field2 …> on-the-hour {disable | enable} rotate {filesize-MB <integer> | time-interval <integer>} syslog replicate {enable | disable} Service Log (accesslog) Copyright © 2010, Juniper Networks, Inc.

  • Page 213: Viewing The Accesslog

    Media Flow Controller Administrator’s Guide Configuring and Using Media Flow Controller Logs and Alarms Viewing the Accesslog You can schedule automatic uploads of completed accesslogs with the accesslog copy command; a completed accesslog is one that has reached its set rotate criteria (default is filesize-MB = 100).

  • Page 214: Cache Log (Cachelog)

    Each URI has its own expiry time. If the re-validation indicates that a URI is still valid, the Attribute Update event updates the URI expiry time; this makes a log entry. Cache Log (cachelog) Copyright © 2010, Juniper Networks, Inc.

  • Page 215: Viewing The Cache Log

    Media Flow Controller Administrator’s Guide Configuring and Using Media Flow Controller Logs and Alarms Viewing the Cache Log To view the Media Flow Controller cache log: • Web interface—Media Flow Controller cache log entries are available for viewing on the Web interface Logs >...

  • Page 216: Table 14 Error Log Levels

    Informational only and do not indicate an error. Function worked incorrectly. Error (2) Function worked, but not as expected. Warning (3) System activity. MSG (4) Progressively more detailed messages. MSG2 (5), MSG3 (6) Error Log (errorlog) Copyright © 2010, Juniper Networks, Inc.

  • Page 217: Viewing The Errorlog

    Media Flow Controller Administrator’s Guide Configuring and Using Media Flow Controller Logs and Alarms errorlog copy <SCP> filename <name> level {1 | 2 | 3 | 4 | 5-7} module <module> on-the-hour {disable | enable} rotate {filesize-MB <integer> | time-interval <integer>} syslog replicate {disable | enable} Viewing the Errorlog To view the Media Flow Controller errorlog:...

  • Page 218: Viewing The Fmsaccess Log

    This log is generated by the FMS server (must be installed, see “Installing and Using FMS in Media Flow Controller (CLI)” on page 97). This log is written to /nkn/adobe/ fms/logs/edge.<nn>.log, by default (you can access this using application fms shell). See FMSEdge Log (fmsedgelog) Copyright © 2010, Juniper Networks, Inc.

  • Page 219: Viewing The Fmsedge Log

    Media Flow Controller Administrator’s Guide Configuring and Using Media Flow Controller Logs and Alarms fmsedgelog for CLI details. See “Configuring Media Flow Controller Service Logs (CLI)” on page 226 for implementation details. fmsedgelog copy <SCP> filename <filename> on-the-hour {disable | enable} rotate {filesize-MB <integer>...

  • Page 220: Viewing The Fmsconnector Log

    “Service Log (accesslog)” on page 212, “Cache Log (cachelog)” on page 214, and “Error Log (errorlog)” on page 215, “FMSAccess Log (fmsaccesslog)” on page 217, “FMSEdge Log (fmsedgelog)” on page 218, and “Stream Stream Log (streamlog) Copyright © 2010, Juniper Networks, Inc.

  • Page 221: System Baseline And Health

    Media Flow Controller Administrator’s Guide Configuring and Using Media Flow Controller Logs and Alarms Log (streamlog)” on page 220. The Trace Log can be used to track down problems with a specific delivery situation; see “Trace Log (tracelog)” on page 223 for details.

  • Page 222: Viewing The System Log

    (.tgz) file. There is no configuration. The contents of the nkn_tech-support.tgz file include the following: active.db active.txt build_version.sh build_version.txt config cpuinfo.log dmesg iomem.log ioports.log list-var_opt_tms.txt lsof.txt lspci-vvv.log lspci-vvvn.log messages messages.10.gz messages.1.gz messages.2.gz messages.3.gz messages.4.gz messages.5.gz messages.6.gz messages.7.gz messages.8.gz Tech-Support Log Copyright © 2010, Juniper Networks, Inc.

  • Page 223: Viewing The Tech-Support Output

    Media Flow Controller Administrator’s Guide Configuring and Using Media Flow Controller Logs and Alarms messages.9.gz mfdb mfdb.txt modprobe.d nkncnt.log.1 nkncnt.log.2 output root_cli_history running-config.txt scsi.log sysinfo.txt systemlog version.log Viewing the Tech-Support Output To view the Media Flow Controller tech-support output: • Web interface—Media Flow Controller Tech Support Report can be downloaded through the System Config >...

  • Page 224: Table 16 Delivery Protocol Http Trace Points

    NFS. Get successful. Success" "NFS GET: TRACE URI: %s. End NFS get: Error: NFS. Server busy. Server busy" "NFS GET: TRACE URI: %s. End NFS get: Error NFS. Error getting URI. getting uri" Trace Log (tracelog) Copyright © 2010, Juniper Networks, Inc.
  • Page 225 Media Flow Controller Administrator’s Guide Configuring and Using Media Flow Controller Logs and Alarms Table 16 Delivery Protocol HTTP Trace Points (Continued) Trace Point Description "OM returning %s bytes for object %s offset=%ld Origin Manager. Returning cacheable/non-cacheable length=%ld" given bytes to the buffer manager for the given object starting at the given offset and length.

  • Page 226: Viewing The Trace Log

    Most Media Flow Controller logs, allow you to enable/disable, copy (automatically), set filesize (for auto-copy), set filename, set format/field options, and set syslog replication. See “Media Flow Controller System Logging Overview” on page 228 for details on syslog options. Unless About Log Rotation Copyright © 2010, Juniper Networks, Inc.
  • Page 227 Media Flow Controller Administrator’s Guide Configuring and Using Media Flow Controller Logs and Alarms otherwise indicated, this procedure applies to the accesslog, cachelog, errorlog, fmsaccesslog, fmsedgelog, fuselog, streamlog, and tracelog (“<*>log” = any service log). Tip! You can schedule automatic uploads of completed logs with the <*>log copy command. A completed log is one that has reached its set filesize-MB (default is 100).

  • Page 228: Media Flow Controller System Logging Overview

    It does not record service activity or errors. The Media Flow Controller errorlog records service related errors but is mostly useful for debugging by Juniper Networks Support. Media Flow Controller provides several service- specific logs, detailed in Chapter 9, “Media Flow Controller Troubleshooting.”...

  • Page 229: Configuring Media Flow Controller System Logging (Cli)

    Media Flow Controller Administrator’s Guide Configuring and Using Media Flow Controller Logs and Alarms • —Informational messages (administrator actions) info • —Debug-level messages (all messages) debug Logging class options are: • —Management daemon (mgmtd) only mgmt-core • —Other back end components mgmt-back •...
  • Page 230 (config) # logging local override class mgmt-front priority info test-vos (config) # logging 123.54.10.12 trap override class mgmt-front priority info test-vos (config) # logging 123.54.10.12 trap none test-vos (config) # logging receive Media Flow Controller System Logging Overview Copyright © 2010, Juniper Networks, Inc.

  • Page 231: Configuring Log Statistics Thresholds (Cli)

    Media Flow Controller Administrator’s Guide Configuring and Using Media Flow Controller Logs and Alarms test-vos (config) # logging format standard test-vos (config) # logging fields seconds enable test-vos (config) # logging files rotation criteria frequency daily test-vos (config) # logging files rotation max-num 12 test-vos (config) # logging files rotation force test-vos (config) # logging files delete oldest 5 test-vos (config) # logging files upload current scp://joe@sv01/home/joe...

  • Page 232: Stats Reports Names Options

    CLI details. • memory—Memory utilization • paging—Paging I/O (input/output) • cpu_util—CPU utilization • bandwidth_day_avg—Average bandwidth usage • bandwidth_day_peak—Peak bandwidth usage • connection_day_avg—Average connection count • connection_day_peak—Peak connection count Configuring Log Statistics Thresholds (CLI) Copyright © 2010, Juniper Networks, Inc.

  • Page 233: Stats Measurement Counters

    Media Flow Controller Administrator’s Guide Configuring and Using Media Flow Controller Logs and Alarms Stats Measurement Counters These stats samples collect information used by stats alarms. The options for stats sample ID are shown in Table 17; sampling interval defaults shown in bold. For details, see stats Chapter 10, “Media Flow Controller CLI Commands.”...

  • Page 234: Stats Alarms

    “falling” basis: the alarm is triggered when something falls below the error- threshold and is cleared when it rises back to the clear-threshold. stats alarm <alarm_ID> rising error-threshold <threshold> Stats Alarms Copyright © 2010, Juniper Networks, Inc.

  • Page 235: Table 18 Media Flow Controller Stats Alarms

    Media Flow Controller Administrator’s Guide Configuring and Using Media Flow Controller Logs and Alarms stats alarm <alarm_ID> falling clear-threshold <threshold> stats alarm <alarm_ID> falling error-threshold <threshold> stats alarm <alarm_ID> rising clear-threshold <threshold> 5. Export statistics to csv (comma-separated value) file; the only format supported for Release 2.0.4.

  • Page 236: Configuring Stats Alarm Notifications

    (default). 1. Configure an email notify recipient for both failure and info event classes (by default). email notify recipient <email_address> 2. Disable an email notify recipient. no email notify recipient <email_address> Stats Alarms Copyright © 2010, Juniper Networks, Inc.

  • Page 237: Snmp Alarms

    Media Flow Controller Administrator’s Guide Configuring and Using Media Flow Controller Logs and Alarms 3. Limit the email notifications to a particular event class for an existing email notify recipient, by removing one of the event classes: no email notify recipient <email_address> class {failure | info} 4.
  • Page 238 Action (MIB/ stat Name) Process Crashed The Media Flow Controller process can restart if there Escalate to Juniper Networks Support to (procmgr) is a software problem. A core file is generated. This look at the core file. However, request event causes high-availability to kick in and requests...
  • Page 239 Media Flow Controller Administrator’s Guide Configuring and Using Media Flow Controller Logs and Alarms Table 19 SNMP Alarms, Possible Causes, and Recommended Actions (Continued) Event Name Cause Action (MIB/ stat Name) Disk I/O High Disk I/O per second has risen above 5 MB. Indicates Check if the amount of hot/popular (disk-io-high) that more content is served from disks.

  • Page 240: Configuring Media Flow Controller Fault Notifications (Cli)

    Networks support automatically receives an email. See email for CLI details including “email event name Options” on page 312 “email class Options” on page 312. To configure fault notifications with the CLI: Configuring Media Flow Controller Fault Notifications (CLI) Copyright © 2010, Juniper Networks, Inc.
  • Page 241 <port_number> email return-addr <username> email return-host 3. Disable or enable event emails sent to Juniper Networks for certain pre-configured events; default is enabled. Use no email autosupport enable to disable. email autosupport enable 4. Manage undeliverable emails. Use cleanup max-age to set when to permanently delete.
  • Page 242 Mail hub: mail.example.com Events to send: process-crash: A process in the system has crashed liveness-failure: A process in the system was detected as hung smart-warning: Smartd warnings Configuring Media Flow Controller Fault Notifications (CLI) Copyright © 2010, Juniper Networks, Inc.

  • Page 243: Server Map Configuration

    NFS publishing points for origin. You cannot use another server-map with this format-type. Note! For cluster-map and origin-escalation-map only, you can use as many, and in any combination, together or separately, as needed. Copyright © 2010, Juniper Networks, Inc. Server Map Overview...

  • Page 244: Creating The Host-Origin-Map Xml File

    Important! Do not change the Version from 1.0 or the Application from MapXML without explicit, new instructions. These values must be present or the XML file will be rejected. Creating the host-origin-map XML File Copyright © 2010, Juniper Networks, Inc.

  • Page 245: Example: Host-Origin-Map Dtd

    You can use this to validate your XML; see “Validating With the DTD,” for details. <!-- HostOriginMap 1.0 DTD, Copyright (c) 2010 by Juniper Networks, Inc. --> <!ELEMENT HostOriginMap (Header*, HostOriginEntry*)> <!ELEMENT Header (Version, Application)> <!ELEMENT Version (#PCDATA)>...

  • Page 246: Example: Cluster-Map Dtd

    You can use this to validate your XML; see “Validating With the DTD” on page 245 for details. <!-- ClusterMap 1.0 DTD, Copyright (c) 2010 by Juniper Networks, Inc --> <!ELEMENT ClusterMap (Header*, ClusterMapEntry*)> <!ELEMENT Header (Version, Application)> <!ELEMENT Version (#PCDATA)>...

  • Page 247: Creating The Origin-Escalation-Map Xml File

    Media Flow Controller Administrator’s Guide Server Map Configuration Creating the origin-escalation-map XML File The origin-escalation-map functionality determines which defined origins are online; if an origin is not online, it automatically moves to the next defined origin, based on defined weight. Under origin escalation, the specified weight each origin defined in the map denotes the order in which requests are tried until a success is received or all nodes have been tried.

  • Page 248: Example Origin-Escalation-Map Dtd

    XML parser fills in after reading your file. You can use this to validate your XML; see “Validating With the DTD” on page 245 for details. <!-- OriginEscalationMap 1.0 DTD, Copyright (c) 2010 by Juniper Networks, Inc --> <!ELEMENT OriginEscalationMap (Header*, OriginEscalationMapEntry*)>...

  • Page 249: Configuring Server Maps (Cli)

    Media Flow Controller Administrator’s Guide Server Map Configuration Tags: • Response Scode—The standard response code when indicating success in calling the NFS service; you can modify the description: • PublishingPoints Interval-Sec—The polling interval; you can modify the number of seconds. This can also be set in the Media Flow Controller CLI with the server-map command;...
  • Page 250 (config) # show server-map Server-map : newMap Format-type : host-origin-map Map File : http://example.com/vod/ Refresh Interval : 9000 test-vos (config) # namespace newTest uri / origin-server http server-map newMap test-vos (config) # Configuring Server Maps (CLI) Copyright © 2010, Juniper Networks, Inc.

  • Page 251: Smoothflow Deployment

    “Deployment Checklist” on page 269 SmoothFlow Deployment Overview To enable Juniper Networks Media Flow Controller SmoothFlow™, media assets (sets of multi-bitrate encoded video files along with metadata describing them) must be created and processed for SmoothFlow, and SmoothFlow functionality must be configured in Media Flow Controller and implemented in the client player.

  • Page 252: Evaluating Your Needs

    Requirements •   Creating SmoothFlow Media Assets Option One: An account with encoding.com or other Creating Assets Using an SaaS Saas, (must use Juniper Networks scripts) •   Python on a Linux 64bit system •   FTP service configured •   Origin server available with sufficient storage space •  ...

  • Page 253: Creating Smoothflow Media Assets

    Media Flow Controller Administrator’s Guide SmoothFlow Deployment Note! Juniper Networks SmoothFlow supports legacy containers and codecs like H.263, VP6 for video, and MP3 for audio in FLV formats, but we recommend using the more optimal H.264/AAC combination instead. General encoding requirements: •...

  • Page 254: Requirements For Creating Assets Using An Saas

    The entire multi-bitrate publishing workflow is not fully automated and requires content owners to take two steps of manual intervention to trigger the scripts and configure the encoding parameters. Creating Assets Using an SaaS Copyright © 2010, Juniper Networks, Inc.

  • Page 255: Steps For Creating Assets Using An Saas

    9. Check the Logs for Assets Created Using an SaaS. Scripts for Creating Assets Using an SaaS Juniper Networks has two Python scripts, SFAssetGenerator and SFSegmenter, that can be used to create media assets using encoding.com Saas. Obtain these scripts through Juniper Networks Customer Support (see “Requesting Technical Support”...

  • Page 256: Initiate Encoding Using An Saas

    Tags and Descriptions <service_provider> <name> – name of encoding service; for example, www.encoding.com. The "pre_process=1" corresponds to the encoding service; currently only encoding.com is supported. <login> – your encoding.com credentials Creating Assets Using an SaaS Copyright © 2010, Juniper Networks, Inc.
  • Page 257 Media Flow Controller Administrator’s Guide SmoothFlow Deployment Table 22 setup.xml File Parameters (Continued) Parameters Tags and Descriptions <ftp_source_location> Information regarding the output profiles with following attributes <ftp_dest_location> <username> – the authorized FTP user <password> – the authorized FTP user password <server_ip>...

  • Page 258: Table 23 Asset.xml File Parameters

    <profile_info> p= {index} 1 ab= {audio-bitrate in kbps} vb= {video-bitrate in kbps} width={width in pixels} height={height in pixels} deinterlace={true/ false, default = true} </profile_info> <fps> 25</fps> <format>flv</format> <keyframe_interval>50</keyframe_interval> </asset_parameters> Creating Assets Using an SaaS Copyright © 2010, Juniper Networks, Inc.

  • Page 259: Verify That Encoding Has Completed

    Media Flow Controller Administrator’s Guide SmoothFlow Deployment jobid.xml The SFAssetGenerator.py script run with the setup.xml and asset.xml files, outputs this file, jobid.xml, listing IDs provided by encoding.com and used as input to SFSegment.py. It also provides the number of profiles (equals number of job IDs) and the bitrates of each profile. The parameters for jobid.xml are described in Table 24, followed by an example file.

  • Page 260: Prepare Media Flow Controller For Assets Created Using An Saas

    (www/var/html) directory. This script can be run either on the origin server, or on another system where the doc root of the origin server is mounted as an NFS mount Creating Assets Using an SaaS Copyright © 2010, Juniper Networks, Inc.

  • Page 261: Logs For Assets Created Using An Saas

    Media Flow Controller Administrator’s Guide SmoothFlow Deployment Table 25 segment_config.xml Parameters (Continued) Parameters Tags and Descriptions <source-type > <ftp-location> – The location of the multi-bitrate files , if the location of these files is different from the system where it is being run. This node requires the following additional sub-nodes: <username>...

  • Page 262: Creating On-Demand Assets

    Conventions for On-Demand Assets. Step 2 – Create AssetDescription.dat File for On-Demand Assets. Step 3 – Pre-Stage On-Demand Assets (multi-bitrate files plus Asset Description file) to origin or Media Flow Controller. Creating On-Demand Assets Copyright © 2010, Juniper Networks, Inc.

  • Page 263: Steps For Creating On-Demand Assets

    SmoothFlow delivery. Requirements and Files for Creating On-Demand Assets Juniper Networks uses the multi-bitrate profiles, one file that you create, the AssetDescription.dat text file, and commands that you issue at the command line to create SmoothFlow assets on-demand. You must follow the bitrate profile naming conventions described.

  • Page 264: Create Assetdescription.dat File For On-Demand Assets

    AFR is a feature in Media Flow Controller that stands for Assured Flow Rate; see “Media Flow Controller AssuredFlow” on page 50 for overview). AFR guarantees that Media Flow Controller delivers at the specified bitrate and never goes below (or too much above) that rate. Creating On-Demand Assets Copyright © 2010, Juniper Networks, Inc.

  • Page 265: Pre-Stage On-Demand Assets

    Media Flow Controller Administrator’s Guide SmoothFlow Deployment The AFR Threshold value can be specified in the Asset Description File (.dat), if using the On- Demand Publishing scheme (or using a Python script if using encoding.com). It's unit is kbps. Do not specify this value in the Smoothflow Control File; it automatically picks up the value from the Asset Description File (.dat) when SmoothFlow processing is initiated.
  • Page 266 Your client player must know how to read it. You can imbue your client player with this intelligence through the Juniper Networks SmoothFlow SDK or API, available through Juniper Networks Customer Support (not necessary when using the Juniper Networks SmoothFlow Reference player).

  • Page 267: Deploying The Smoothflow Reference Client Player

    Deploying the SmoothFlow Reference Client Player A binary SmoothFlow client player is provided to you as a reference and for testing or evaluation purposes. This section details how to install the Juniper Networks Smoothflow Player for testing purposes onto your Web page.

  • Page 268: Troubleshooting

    The HTTP request includes the X-NKN-Trace header; for example if using Wget: wget --header “X-NKN-Trace:” <URL> The HTTP modules detect the above conditions and set the flag “HRF_TRACE_REQUEST” as well as other flags that direct each relevant module to log meaningful trace points. Troubleshooting Copyright © 2010, Juniper Networks, Inc.

  • Page 269: Deployment Checklist

    Media Flow Controller Administrator’s Guide SmoothFlow Deployment To view the delivery trace log: • Web interface—Media Flow Controller trace log entries are available for viewing on the Web interface Trace Logs page. • CLI—To upload a trace log, run upload tracelog scp://<URL>. Now you can access the trace log at the specified system, move it (if needed) and view its contents.
  • Page 270 “Initiate SmoothFlow Processing for On-Demand Assets” on page 265 to prepare the assets for on-demand SmoothFlow delivery. Finally, see “Deploying the SmoothFlow Reference Client Player” on page 267 to complete SmoothFlow deployment. Deployment Checklist Copyright © 2010, Juniper Networks, Inc.

  • Page 271: Media Flow Controller Troubleshooting

    Cache Ingest Last Eviction Time Diff—1 • Cache Evict Aging Time—10 • Cache Promotion Hotness Increment—100 • Cache Promotion Hotness Threshold—3 • Cache Promotion Hit Increment—100 • Cache Promotion Hit Threshold—10 Copyright © 2010, Juniper Networks, Inc. Displaying Information Using Show Commands...
  • Page 272 • Total number of HTTP 501 (not implemented) responses • Total number of HTTP Timeouts • Total HTTP Well finished count; incremented after the HTTP body has been sent Displaying Information Using Show Commands Copyright © 2010, Juniper Networks, Inc.
  • Page 273 Media Flow Controller Administrator’s Guide Media Flow Controller Troubleshooting • Total Number of Cache-Miss • HTTP TUNNEL STATS • Total Connections • Total Active Transactions • Total Bytes Served • Total Errors • ERROR COUNTERS • Number of Scheduler Errors on get data •...
  • Page 274 —On average, number of completed HTTP Avg HTTP Transactions per Sec transactions. • —On average, the data fetch rate from buffer to Avg Cache Bandwidth (MB/Sec) network for delivery. Displaying Information Using Show Commands Copyright © 2010, Juniper Networks, Inc.

  • Page 275: Testing Network Connectivity

    Media Flow Controller Administrator’s Guide Media Flow Controller Troubleshooting • —On average, the data fetch rate from disk. Avg Disk Bandwidth (MB/Sec) • —On average, the data fetch rate from origin Avg Origin Bandwidth (MB/Sec) (happens only when there is a cache miss). •...

  • Page 276: Testing Media Flow Controller Delivery Functions

    The actions for this example procedure are configuring a namespace (testHttp), requesting files via the Media Flow Controller (172.16.254.2 / test-vos), and observing results using show counters and the accesslog on the Media Flow Controller Web interface. Testing Media Flow Controller Delivery Functions Copyright © 2010, Juniper Networks, Inc.

  • Page 277: Testing Http Origin Fetch

    Media Flow Controller Administrator’s Guide Media Flow Controller Troubleshooting Testing HTTP Origin Fetch This test is illustrated in Figure MFD (172.16.254.2 / test-vos) Namespace: Media name: testHttp Flow delivery protocol: http Client and origin (172.16.254.1 / sv05) UNIX machine with wget Controller domain: any UNIX machine...
  • Page 278 RAM is moved to disk. Example: test-vos (config) # service restart mod-delivery [joe@sv05 joe]$ wget http://172.16.254.2/testresults/joe/test.txt --16:17:55-- http://172.16.254.2/testresults/joe/test.txt Connecting to 172.16.254.2:80... connected. Testing Media Flow Controller Delivery Functions Copyright © 2010, Juniper Networks, Inc.

  • Page 279: Testing Nfs Origin Fetch

    Media Flow Controller Administrator’s Guide Media Flow Controller Troubleshooting HTTP request sent, awaiting response... 200 OK Length: 165 [text/plain] Saving to: `test.txt.3' 100%[=======================================>] 165 --.-K/s in 0s 16:17:55 (13.1 MB/s) - `test.txt.3' saved [165/165] [joe@sv05 joe]$ test-vos-cl11 (config) # show counters Total number of Active Connections Total Bytes served from RAM cache : 0 Bytes...
  • Page 280 4. Run the test once more to see Media Flow Controller serve the content from Disk; first restart the delivery service so everything in RAM is moved to disk. Example: test-vos (config) # service restart mod-delivery [joe@sv05 joe]$ wget -O newtest http://172.16.254.2/nfs1/test.txt --16:17:55-- http://172.16.254.2/nfs1/test.txt Testing Media Flow Controller Delivery Functions Copyright © 2010, Juniper Networks, Inc.

  • Page 281: Testing A Specific Transaction

    Media Flow Controller Administrator’s Guide Media Flow Controller Troubleshooting Connecting to 172.16.254.2:80... connected. HTTP request sent, awaiting response... 200 OK Length: 165 [text/plain] Saving to: `newtest' 100%[=======================================>] 165 --.-K/s in 0s 16:17:55 (13.1 MB/s) - `newtest' saved [165/165] [joe@sv05 joe]$ test-vos-cl11 (config) # show counters Total number of Active Connections Total Bytes served from RAM cache...

  • Page 282: Common Media Flow Controller Configuration Errors

    HWaddr are what you need): show interface 3. Type the following command to name that interface as the eth0 management interface: management interface <MAC_address> Common Media Flow Controller Configuration Errors Copyright © 2010, Juniper Networks, Inc.

  • Page 283: Namespace Match Uri Configuration

    Media Flow Controller Administrator’s Guide Media Flow Controller Troubleshooting Namespace Match Uri Configuration Proper namespace configuration is required for smooth Media Flow Controller functioning. Namespace is how Media Flow Controller knows what to deliver and where to fetch it, if needed.
  • Page 284 Media Flow Controller Troubleshooting Media Flow Controller Administrator’s Guide Common Media Flow Controller Configuration Errors Copyright © 2010, Juniper Networks, Inc.

  • Page 285: Media Flow Controller Command And Mib Reference

    PART 2 Media Flow Controller Command and MIB Reference Copyright © 2010, Juniper Networks, Inc.
  • Page 286 Media Flow Controller Administrator’s Guide Copyright © 2010, Juniper Networks, Inc.

  • Page 287: Media Flow Controller Cli Commands

    Lists all FMS server command executions. fmsedgelog Lists transactions to the FMS edge server. fuselog Records RTMP transaction details. help View the interactive help system. hostname Set the system hostname. image Manage software images. Copyright © 2010, Juniper Networks, Inc.
  • Page 288 Upload the accesslog, errorlog, or a namespace object. username Configure user accounts and set capabilities. virtual-player Configure Media Flow Controller player management functions. Configure the Web interface, also known as the Management Console. write Save the running configuration to persistent storage. Copyright © 2010, Juniper Networks, Inc.

  • Page 289: Aaa

    Media Flow Controller Administrator’s Guide Media Flow Controller CLI Commands Configure AAA (authentication, authorization and accounting) settings; AAA accounting options are not supported at this time. RADIUS or TACACS+ authentication must be configured before these options can be specified with this command. aaa (authentication) Configure authentication settings.

  • Page 290: Accesslog

    • —Specify whether or not the access log messages are seen as part syslog replicate of SYSLOG also. Default is no (disabled), access log is not seen as part of SYSLOG. accesslog Copyright © 2010, Juniper Networks, Inc.

  • Page 291: Accesslog Format Options

    Media Flow Controller Administrator’s Guide Media Flow Controller CLI Commands show accesslog List access log settings. Note! Media Flow Controller accesslog is enabled by default and cannot be disabled. Note! View the Media Flow Controller accesslog through the Web interface, Logs > Service Log page.

  • Page 292: Analytics

    Configure cache analytics options. See “Media Flow Controller Hierarchical Caching” on page 49 for details. analytics cache-ingest size-threshold <bytes> cache-promotion [disable | enable | hotness-threshold <number>] analytics Copyright © 2010, Juniper Networks, Inc.

  • Page 293: Application

    Media Flow Controller Administrator’s Guide Media Flow Controller CLI Commands Notes: • —Set the maximum size of an object that can cache-ingest size-threshold <bytes> be optionally ingested into the fastest cache tier in the disk cache. Objects smaller than, or equal to, the configured size are automatically written to the fastest cache tier.

  • Page 294: Banner

    LACP- enabled links; supports load balancing and failover. • —Wait this long before enabling a slave after detecting a link recovery. up-delay-time banner Copyright © 2010, Juniper Networks, Inc.

  • Page 295: Boot

    Media Flow Controller Administrator’s Guide Media Flow Controller CLI Commands show bonds [<bonding_interface>] List configuration information about all or the specified bonding interface. Note! When any change is made to the Media Flow Controller delivery mechanism, including configuring bonded interfaces, you must restart the delivery service (service restart mod- delivery).

  • Page 296: Clear

    EXEC command. Clear dynamic entries from the arp-cache. Configure CLI shell options. clear-history default auto-logout <length_in_minutes> paging enable prefix-modes enable progress prompt confirm-reload confirm-reset confirm-unsaved empty-password show session auto-logout <length_in_minutes> paging enable clear Copyright © 2010, Juniper Networks, Inc.
  • Page 297 Media Flow Controller Administrator’s Guide Media Flow Controller CLI Commands prefix-modes enable terminal length resize type width x-display full Notes: • —EXEC command. Clears the command history of the current user. clear-history • —Configure default CLI options for all future sessions. default •...

  • Page 298: Clock

    • —Set the system time zone. Default is UTC. The no variant resets to default. timezone The timezone may be specified in one of three ways: clock Copyright © 2010, Juniper Networks, Inc.

  • Page 299: Cmc

    Media Flow Controller Administrator’s Guide Media Flow Controller CLI Commands • A nearby city whose timezone rules follow. The system has a large list of cities that can be displayed by the help and completion system. They are organized hierarchically because there are too many of them to display in a flat list. A given city may be required to be specified in two, three, or four words, depending on the city.

  • Page 300: Cmc Client

    List CMC identities. Can list all identities, all of a certain type, or just a specified one, depending on which parameters are used. show cmc auth ssh List CMC SSH global settings. cmc client Configure Central Management Console client. cmc client bw-limit limit <kbytes/sec> confirm-config cmc client Copyright © 2010, Juniper Networks, Inc.
  • Page 301 Media Flow Controller Administrator’s Guide Media Flow Controller CLI Commands connection connect [maintain] disconnect reconnect [maintain] enable server address <address> auth authtype <type> password {password [<password>] | username <name>} ssh-dsa2 identity <string> username <name> ssh-rsa2 identity <string> username <name> capabilities username <name> port <port>...

  • Page 302: Cmc Rendezvous

    List miscellaneous information about a CMC client. cmc rendezvous Configure Central Management Console rendezvous options. cmc rendezvous client auth default auto force server-addr service-name <name> cmc rendezvous Copyright © 2010, Juniper Networks, Inc.

  • Page 303: Collect Counters

    Media Flow Controller Administrator’s Guide Media Flow Controller CLI Commands Notes: • —Configure CMC client rendezvous options. client • —Specify the authentication method to use to log into the server to rendezvous. auth • —Configure the type of authentication to use. The no variant resets the authtype authtype to its default, which is none.

  • Page 304: Configuration

    <URL or SCP> generate active {running | saved} [save <filename>] [upload <URL_or_SCP>] file {<filename> | initial | initial.bak} [save <filename>] [upload <URL_or_SCP>] upload {active <URL> | initial.bak | initial} write [to <filename>] [no switch] configuration Copyright © 2010, Juniper Networks, Inc.
  • Page 305 Media Flow Controller Administrator’s Guide Media Flow Controller CLI Commands Notes: • —Copy a configuration file. This does not affect the current running configuration. copy The active configuration file may not be deleted or renamed, nor may it be the target of a move or copy.

  • Page 306: Configuration Text

    Not all configuration is included in the show configuration output, so a text configuration file generated and re-applied later may not fully recreate the same configuration. text fetch <URL_or_SCP> apply [discard][fail-continue][verbose] filename <filename> [apply [fail-continue][verbose]] configuration text Copyright © 2010, Juniper Networks, Inc.
  • Page 307 Media Flow Controller Administrator’s Guide Media Flow Controller CLI Commands file <filename> apply [fail-continue][verbose] delete rename <new_filename> upload <URL or SCP> generate active {running | saved} [save <filename>] [upload <URL_or_SCP>] file {<filename> | initial | initial.bak} [save <filename>] [upload <URL_or_SCP>] Notes: •...

  • Page 308: Configure

    See “Configuring Media Flow Controller Delivery Protocol (CLI)” on page 73 for task details. delivery protocol {http | rtsp} allow-req {all | <method1> [<method2>] [<method3>]... [<method16>]} conn-pool max-arp-entry <number> origin disable enable configure Copyright © 2010, Juniper Networks, Inc.
  • Page 309 Media Flow Controller Administrator’s Guide Media Flow Controller CLI Commands max-conn <number> timeout <seconds> connection [close use-reset | persistence num-requests <0 - 100>] file-type <suffix> content-type <type> interface {all | <interface> <interface> <interface> ...} listen port {80 | <port> <port> <port> ...} req-length maximum <bytes>...

  • Page 310: Email

    • —Sends emails to pre-configured vendor for certain failures. autosupport • —Enable or disable (with no email autosupport) the sending of email to enable vendor support when certain failures occur. Default is enable. email Copyright © 2010, Juniper Networks, Inc.
  • Page 311 Media Flow Controller Administrator’s Guide Media Flow Controller CLI Commands • —Specify which events to send autosupport notification emails for. See “email event event name Options," for details. • —Manage undeliverable emails: dead-letter • —Set a time limit after which undeliverable emails cleanup max-age <duration>...

  • Page 312: Email Event Name Options

    * Can be added to info events class with email notify event <event_name>. email class Options Email class options are as follows: • failure events: • —A process in the system has crashed. process-crash • —Unexpected system shutdown. unexpected-shutdown email Copyright © 2010, Juniper Networks, Inc.

  • Page 313: Enable

    “Configuring Media Flow Controller Service Logs (CLI)” on page 226 for task details including information on log rotation. Note! This log is mainly used for debugging purposes by Juniper Networks Support. errorlog copy <SCP> filename <name> level {1 | 2 | 3 | 4 | 5-7} module <module>...

  • Page 314: Errorlog Level Options

    The errorlog named and Hex code modules that can be set are shown in Table Table 30 errorlog module Options Module Description All modules The analytics module analytics The HTTP module http The media-cache module media-cache errorlog Copyright © 2010, Juniper Networks, Inc.
  • Page 315 Media Flow Controller Administrator’s Guide Media Flow Controller CLI Commands Table 30 errorlog module Options (Continued) Module Description The network module network The NFS module The RTSP module rtsp The system module system MOD_NETWORK (network) 0x0000000000000001 MOD_HTTP (HTTP subsystem) 0x0000000000000002 MOD_DM2 (disk manager) 0x0000000000000004 MOD_MM (media manager)

  • Page 316: Exit

    * Only FTP and TFTP URLs, as well as SCP pseudo-URLs are supported for the destination. “Terminology” on page 30 for the scp URL format and requirements. show files debug-dump [<filename>] stats [<filename>] tcpdump [<filename>] exit Copyright © 2010, Juniper Networks, Inc.

  • Page 317: Fmsaccesslog

    Media Flow Controller Administrator’s Guide Media Flow Controller CLI Commands Notes: • —List debug dump files. Use the filename option to list a summary of the debug-dump contents of a particular debug dump file. • —List statistics report files. Use the filename option to list the contents of a stats particular statistics report file.

  • Page 318: Fmsedgelog

    URL format); you must have an SCP server installed in order to SCP files to your machine. • —Configure the name of the file where the FMS edge log is stored. Default is filename fmsedgelog.<num>.yyyymmdd_hour:min:sec (numbered sequentially). • —Set hourly log rotation. Default is no (disabled). on-the-hour fmsedgelog Copyright © 2010, Juniper Networks, Inc.

  • Page 319: Fuselog

    Media Flow Controller Administrator’s Guide Media Flow Controller CLI Commands • —Media Flow Controller allows FMS edge log rotation based on file size or time. rotate • —Set rotation based on file size. Media Flow Controller creates filesize-MB "fmsedge.log.1," "fmsedge.log.2" and so on up to "fmsedge.log.10," after which it wraps around.

  • Page 320: Hostname

    • —override the CLI default for displaying progress (cli default progress progress enable): no-track overrides the set default value enabling tracking, and blocks hostname Copyright © 2010, Juniper Networks, Inc.

  • Page 321: Interface

    Media Flow Controller Administrator’s Guide Media Flow Controller CLI Commands progress tracking; track overrides the set value disabling tracking, and tracks installation progress. If the options are not specified the CLI default is in effect. • —The require-sig and ignore-sig options override the system-wide defaults verify for signature verification;...
  • Page 322 TX (transmissions out) statistics. Detailed information is given by default; use the subcommands to modify that. Notes: • —List abbreviated runtime state, the interface statistics are excluded. brief • —List configuration of the interface, rather than its runtime state. configured interface Copyright © 2010, Juniper Networks, Inc.
  • Page 323 Media Flow Controller Administrator’s Guide Media Flow Controller CLI Commands Configure Internet protocol (IP) settings. See “Configuring Interfaces, Hostname, Domain List, DNS, and Default Gateway (CLI)” on page 61 for task details. default-gateway {<next_hop_IP_address_or_Interface> [<interface>]} dhcp hostname <DHCP_hostname> primary-intf <interface_name> default-gateway yeild-to-static send-hostname <DHCP_hostname>...
  • Page 324 —Add or delete (with no) hostname/IP mappings for /etc/hosts. host • —Set or delete (with no) a static host mapping for the current hostname. map-hostname • —Add or delete (with no) DNS servers. name-server Copyright © 2010, Juniper Networks, Inc.

  • Page 325: Ip Filter Chain Rule Arguments

    Media Flow Controller Administrator’s Guide Media Flow Controller CLI Commands • —Set or delete (with no) a static route. If it is called with only a network prefix and route mask, this deletes all routes for that prefix. Note! If you change the IP address for a host, you must run the service restart command for the mod_delivery (progressive download) service for that host.
  • Page 326 —It is associated with an existing connection which has seen traffic in ESTABLISHED both directions. • —It opens a new connection, but one which is related to an established RELATED connection. • —It opens a new, unrelated connection. ip filter chain rule arguments Copyright © 2010, Juniper Networks, Inc.

  • Page 327: Ldap

    Media Flow Controller Administrator’s Guide Media Flow Controller CLI Commands ldap ldap base-dn <string> bind-dn <string> bind-password <string> host <IP_address> order {last | <order_number>} login-attribute {<string> | uid | sAMAccountName} port <port> scope {one-level | subtree} timeout <seconds> version {2 | 3} Notes: •...

  • Page 328: License

    It does not record service activity or errors. The Media Flow Controller errorlog records service related errors but is mostly useful for debugging by Juniper Networks Support. Media Flow Controller provides several service-specific logs, detailed in ”Chapter 9, “Media Flow Controller Troubleshooting.”...
  • Page 329 Media Flow Controller Administrator’s Guide Media Flow Controller CLI Commands welf [fw-name <firewall_name>] level cli commands {<severity_level> | none} local override [class <class> priority {<severity_level> | none}] {<severity_level> | none} recieve trap {<severity_level> | none} <IP_address> trap override [class <class> priority {<severity_level> | none}] <severity_level>...
  • Page 330 Use no logging receive to disable. • —Set minimum severity of log messages sent to syslog trap <severity_level> servers. This sets both the default for new servers, as well as the setting for all existing logging Copyright © 2010, Juniper Networks, Inc.

  • Page 331: Logging Severity Level

    Media Flow Controller Administrator’s Guide Media Flow Controller CLI Commands servers. The no variant sets the level to none, disabling logging to remote servers altogether (though the list of servers is not erased). This command does not affect console or local logging. See logging severity level, for details.

  • Page 332: Management

    Configure which interface is named eth0. The naming of the interfaces is done during installation. For Juniper Networks VXA Series appliances, the interface names are set automatically and eth0 will always be set properly. When installing on other machines, you normally configure the naming of the interfaces during installation, either interactively or by specifying the MAC address of the interfaces to be named eth0 and eth1.
  • Page 333 Media Flow Controller Administrator’s Guide Media Flow Controller CLI Commands controller) the disks may not be assigned the correct cache-type. Default is correct auto-assignment. • —EXEC command. Use when you insert a disk into a running Media Flow format Controller with the intent of not using the contents that exist in the disk. •...

  • Page 334: Mfdlog

    <number> interface <interface_name> tcp port <port_number> Notes: • —Number of lines allowed per log field. field-length • —Interface and port on which mfdlog listens, interface <interface_name> tcp port default port is 7957. mfdlog Copyright © 2010, Juniper Networks, Inc.

  • Page 335: Namespace

    Media Flow Controller Administrator’s Guide Media Flow Controller CLI Commands namespace A namespace is a named collection of parameters that set delivery policies in a granular manner; you can configure up to 256 namespaces. To set global delivery policies, see delivery for CLI details.
  • Page 336 82, for details. • —Choose to calculate the consistent hash using the complete-url of the cluster-hash incoming request or the base-url. Examples: complete-url: /a/b/c/myobject.html -> MD5 hash (/a/b/c//myobject.html); base-url: /a/b/c/myobject.html -> MD5 hash (/a/b/c/). namespace Copyright © 2010, Juniper Networks, Inc.
  • Page 337 Media Flow Controller Administrator’s Guide Media Flow Controller CLI Commands • —Set delivery protocol options; two delivery protocols and options delivery protocol may be configured. Entering the delivery protocol puts you into namespace delivery protocol configure mode; use exit when finished. •...
  • Page 338 —Set this namespace to be a Transparent Proxy proxy-mode transparent on-ip using the IP address of your Media Flow Controller that you enter. See “Using namespace for Proxy Configurations” on page 87 for more information. namespace Copyright © 2010, Juniper Networks, Inc.

  • Page 339: (Namespace) Delivery Protocol {Http | Rtsp} Origin-Fetch

    Media Flow Controller Administrator’s Guide Media Flow Controller CLI Commands • —Make active or inactive the namespace; you must deactivate the namespace to status make large changes, like the match value. Important! A newly-created namespace is in inactive by default; you must explicitly activate it. •...

  • Page 340: (Namespace) Delivery Protocol Http Origin-Request

    {deny | permit [use-date-header]} connect timeout <seconds> retry-delay <seconds> header <name> [<value>] action add ... host-header inherit incoming-req {deny | permit} read interval-timeout <seconds> retry-delay <seconds> x-forwarded-for {disable | enable} (namespace) delivery protocol http origin-request Copyright © 2010, Juniper Networks, Inc.

  • Page 341: (Namespace) Origin-Server

    Media Flow Controller Administrator’s Guide Media Flow Controller CLI Commands (Optional) Specify a list of policies for data requested from origin with delivery protocol http; enters you to namespace <name> origin-request mode, use exit to leave, use no namespace <name> origin-request to re-set configured values to defaults. Notes: •...
  • Page 342 —Use the destination IP address of the incoming request as the follow dest-ip origin server. Optionally, set use-client-ip to use the client IP address in place of the origin server’s IP address in the request. (namespace) origin-server Copyright © 2010, Juniper Networks, Inc.

  • Page 343: (Namespace) Object List | Delete | Revalidate

    Media Flow Controller Administrator’s Guide Media Flow Controller CLI Commands • —A hostname or IP address; and (optional) a port, default is 554. Optionally FQDN choose an RTP transport mechanism for MFD to use when fetching media data from the origin streaming server, either rtp-udp or rtp-rtsp (interleaved); default is to use what the client specifies.

  • Page 344: Network

    —Set the maximum bandwidth for a session. The actual session max-bandwidth bandwidth is between the network connection assured-flow-rate and this value. Even if there is available bandwidth in the link, Media Flow Controller does not network Copyright © 2010, Juniper Networks, Inc.
  • Page 345 Media Flow Controller Administrator’s Guide Media Flow Controller CLI Commands allocate more than this value for a session. When there is a full download, Media Flow Controller tries to allocate this value to the session. Default is 0 kbps (unbounded) with Media Flow Controller license, 200 kbps without it.

  • Page 346: Ntp

    It generates an error if NTP is enabled, as the socket it requires is already in use. Copyright © 2010, Juniper Networks, Inc.

  • Page 347: Ping

    Media Flow Controller Administrator’s Guide Media Flow Controller CLI Commands show ntp List NTP settings. ping ping [<options>] <hostname> EXEC command. Network diagnostic tool ping. Invokes standard binary, passing command line arguments straight through. radius-server RADIUS (Remote Authentication Dial In User Service) is a networking protocol that provides centralized access, authorization and accounting management for people or computers to connect and use a network service.

  • Page 348: Ram-Cache

    This prompt is contingent on a separate configuration setting, controlled with the [no] cli default prompt confirm-reload command. If both prompts are enabled, and the configuration was unsaved, you are prompted twice. ram-cache Copyright © 2010, Juniper Networks, Inc.

  • Page 349: Reset

    Media Flow Controller Administrator’s Guide Media Flow Controller CLI Commands • —Reboot the system immediately. This reboots the system, and there is no halt force variant. There is also never any confirmation, whether or not there are any unsaved changes to the configuration •...

  • Page 350: Server-Map Example For Nfs Origin

    Map File: http://mapfile.example.com/nfs/path/filemapA.xml Refresh Interval: 60 server-map Example for NFS Origin For an incoming URL of http://www.example.com/nfs_mnt1/video1.flv, and a server-map configuration of: test-vos (config) # server-map smNFS1 test-vos (config server-map smHTTP1) # format-type nfs-map server-map Copyright © 2010, Juniper Networks, Inc.

  • Page 351: Server-Map Example For Http Origin

    Media Flow Controller Administrator’s Guide Media Flow Controller CLI Commands test-vos (config server-map NFS1) # file-url http://mapfile.example.com/nfs/ path/filemapA.xml refresh-interval 300 test-vos (config server-map NFS1) # Media Flow Controller would scan the URL, extract nfs_mnt1 and use this defined namespace to index into the server-map file fetched from the set file-url. The fetched file (filemapA.xml) would have an entry (or multiple entries) with nfs_mnt1 indicating the NFS mount point.

  • Page 352: Show

    —Same as show configuration but includes commands that set default values. full • —Same as show configuration except that it applies to the currently running running configuration, rather than the active saved configuration. show Copyright © 2010, Juniper Networks, Inc.

  • Page 353: Slogin

    Media Flow Controller Administrator’s Guide Media Flow Controller CLI Commands Note! Commands that would set something to its default are not included—so this command on a fresh configuration produces no output, except the header. Note! This does not include changes that have not yet been written to persistent storage. show running-config [full] The show running-config commands perform the same functions as the show configuration commands and are included for ease-of-use.

  • Page 354: Snmp Traps

    Media Flow Controller generates a number of traps to notify you about critical system events. You can configure Media Flow Controller to send SNMP traps/alarms to a 3rd party network management system. SNMP traps notify-able events are described in Table snmp-server Copyright © 2010, Juniper Networks, Inc.

  • Page 355: Ssh

    Media Flow Controller Administrator’s Guide Media Flow Controller CLI Commands Table 32 SNMP Traps Notify-able Events Trap Description CPU utilization has risen too high. cpu-util-high CPU utilization has fallen back to acceptable levels. cpu-util-ave-ok Disk I/O per second has risen too high. disk-io-high Filesystem free space has fallen too low.
  • Page 356 —Delete a known host from the specified known-host <IP_address> remove user's .ssh known_hosts file. show ssh client SSH client identities (public/private keys) and the per user list of authorized keys for the users. ssh client Copyright © 2010, Juniper Networks, Inc.

  • Page 357: Ssh Server

    Media Flow Controller Administrator’s Guide Media Flow Controller CLI Commands ssh server Enable or disable, and configure SSH (secure sockets shell) server options. ssh server enable host-key generate <key_type> {private-key <key> | public-key <key>} listen [enable] [interface <interface_name>] min-version {1 | 2} ports <port>...

  • Page 358: Stats

    • —Set alarm for when specified statistic fall too low. falling • —This value terminates the alarm. clear-threshold <value> • —This value initiates the alarm. error-threshold <value> • —Set alarm event rate-limits: rate-limit stats Copyright © 2010, Juniper Networks, Inc.
  • Page 359 Media Flow Controller Administrator’s Guide Media Flow Controller CLI Commands • —Set the alarm event rate-limit maximum counts for the three types of count counts (short, medium, long) for alarms; defaults are short=5, medium=20, long=50. See “stats alarm rate-limit count," for more information.

  • Page 360: Stats Alarms

    Specify three time limits for tracking and, potentially, limiting how many of this type of alarm to send. The duration and count of each bucket for short, medium, and long are meant to be stats alarms Copyright © 2010, Juniper Networks, Inc.

  • Page 361: Stats Alarm States

    Media Flow Controller Administrator’s Guide Media Flow Controller CLI Commands ordered such that the short bucket has the smallest time duration (window) and smallest maximum allowed count. The rate-limit applies to all three buckets simultaneously. Separate counts of alarms are kept for error alarm events and clear alarm events. For each alarm type, a single skip count is kept and is reported when the alarm event is later sent.

  • Page 362: Stats Chds

    3600 seconds. High point of data fetched averaged over 7 days. Default interval is 3600 seconds, bandwidth_week_peak default range is 3600 seconds. Bandwidth served from RAM/buffer cache over last 24 hours. cache_bandwidth_day stats CHDs Copyright © 2010, Juniper Networks, Inc.
  • Page 363 Media Flow Controller Administrator’s Guide Media Flow Controller CLI Commands Table 34 Stats CHDs (Continued) Stat CHD Description Bandwidth served from RAM/buffer cache over last 7 days. cache_bandwidth_week Total data bandwidth being served from RAM/Buffer cache. cache_byte_rate Incoming connections average for 24 hours. Default interval is 900 seconds, connection_day_avg default range is 900 seconds.

  • Page 364: Stats Samples

    Bandwidth being served from Disk; default = 10 seconds. disk_byte_count Bandwidth being served from Disk for the last 24 hours; default = 5 minutes. disk_byte_count_day Bandwidth being served from Disk for the last 7 days; default = 30 minutes. disk_byte_count_week stats samples Copyright © 2010, Juniper Networks, Inc.

  • Page 365: Streamlog

    Media Flow Controller Administrator’s Guide Media Flow Controller CLI Commands Table 35 Stats Samples (Continued) Stat Sample Description Disk I/O (input/output, in kilobytes); default = 15 seconds. disk_io Filesystem usage, in bytes; default = 1 minute. fs_mnt_bytes Filesystem usage, in inodes; default = 1 minute. fs_mnt_inodes Number of HTTP transactions (GET requests) per second;...

  • Page 366: Streamlog Format Options

    Origin server IP address. 123.14.14.55 Length of the stream in seconds. (filelength) Client Source IP address. 207.19.19.20 (c-ip) Player information used in the header (User-Agent). NSPlayer Timestamp (seconds since Epoch) when transaction ended. 963873698.73 (timestamp) streamlog Copyright © 2010, Juniper Networks, Inc.
  • Page 367 Media Flow Controller Administrator’s Guide Media Flow Controller CLI Commands Table 36 streamlog format Options (Continued) Field Description Example s URI stem accessed; the URL up to the first question mark (?). rtsp://abc/hello.rm (cs-uri-stem) Client operating system. Windows (c-os) Client media player version. RealPlayer or 7.0.1.15 (player) Streaming URI (URL suffix) accessed.

  • Page 368: Tacacs-Server

    (*) character, and the user must enter the same string twice. • —Sets, or resets to 0 (zero) (with no), a global communication value for all retransmit TACACS+ servers. Can be overridden in a tacacs-server host command. Range is 0-5, tacacs-server Copyright © 2010, Juniper Networks, Inc.

  • Page 369: Tcpdump

    Media Flow Controller Administrator’s Guide Media Flow Controller CLI Commands default is 1. Sets the number of times the client attempts to authenticate with any TACACS+ server. To disable retransmissions set it to 0 (zero). • —Sets, or resets to the default (with no), a global communication value for all timeout TACACS+ servers.

  • Page 370: Terminal

    • —Specify whether (enable) or not trace log messages are seen as syslog replicate part of SYSLOG; default is disable (trace log is not seen as part of SYSLOG). terminal Copyright © 2010, Juniper Networks, Inc.

  • Page 371: Traceroute

    Media Flow Controller Administrator’s Guide Media Flow Controller CLI Commands traceroute EXEC command. Network diagnostic tool traceroute. Invokes standard binary, passing command line arguments straight through. traceroute [<options>] {<hostname>} upload Upload files. upload accesslog {current | all} {<SCP> | <SFTP>} cachelog {current | all} {<URL>...
  • Page 372 You can also optionally specify a username and only the history of that particular user is displayed. • —The username and capabilities of the currently logged-in user. whoami username Copyright © 2010, Juniper Networks, Inc.

  • Page 373: Virtual-Player

    Media Flow Controller Administrator’s Guide Media Flow Controller CLI Commands virtual-player Create a named virtual player in Media Flow Controller with policies for delivery; the virtual player can then be used in a namespace, see namespace for details. The different virtual player types correspond to those types of videos;...

  • Page 374: Virtual-Player Type Generic

    —Not supported in Release 2.0.4. auto • —Specify a string; referenced value must be in kilobytes. query-string-parm • —Define a static value, in kbps. A value of 0 (zero) means no throughput at all. rate virtual-player type generic Copyright © 2010, Juniper Networks, Inc.

  • Page 375: Virtual-Player Type Break

    Media Flow Controller Administrator’s Guide Media Flow Controller CLI Commands • —Set the maximum bandwidth for a session. The actual connection max-bandwidth session bandwidth is between the AFR (Assured Flow Rate) and this value. Even if there is available bandwidth in the link, Media Flow Controller does not allocate more than this value for a session.

  • Page 376: Virtual-Player Type Qss-Streamlet

    Useful for Adaptive Bit Rate video delivery where the URI format signals the assured flow rate. Use no virtual-player <name> to delete. In prefix mode, use no rate-map match <string> to delete one particular entry. See “Creating and Configuring Virtual Players (CLI)” virtual-player type qss-streamlet Copyright © 2010, Juniper Networks, Inc.

  • Page 377: Virtual-Player Type Yahoo

    “Creating and Configuring Virtual Players (CLI)” on page 74 for task details. Note! Requires a special license to create, see Juniper Networks Support for details. virtual-player <name> type yahoo assured-flow {auto | query-string-parm <string> | rate <kbps>} connection max-bandwidth <kbps>...

  • Page 378: Virtual-Player Type Smoothflow

    <name> type smoothflow connection max-bandwidth <kbps> control-point <string> signals session-id query-string-parm <string> state query-string-parm <string> profile query-string-parm <string> hash-verify digest <digest_type> shared-secret <string>{append | prefix} virtual-player type smoothflow Copyright © 2010, Juniper Networks, Inc.
  • Page 379 Media Flow Controller Administrator’s Guide Media Flow Controller CLI Commands match query-string-parm <string> seek query-string-parm <string> [enable-tunnel] [seek-length query- string-parm <string>] Notes: • —Set the maximum bandwidth for a session. The actual connection max-bandwidth session bandwidth is between the AFR (Assured Flow Rate) and this value. Even if there is available bandwidth in the link, Media Flow Controller does not allocate more than this value for a session.

  • Page 380: Virtual-Player Type Youtube

    • —Specify a string to implement FLV seek (allows the client player to seek to a seek specific location of the URL). In prefix mode, use no seek to disable. Optionally: virtual-player type youtube Copyright © 2010, Juniper Networks, Inc.

  • Page 381: Virtual-Player Type Smoothstream-Pub

    Media Flow Controller Administrator’s Guide Media Flow Controller CLI Commands • —Specify a name to signal the number of bytes seek-length query-string-parm of data to send from the seek start position; referenced value must be in bytes. • —If set, all seek requests to the origin server are tunneled; typically enable-tunnel this option needs to be selected only when the origin site changes their seek mechanism.

  • Page 382: Web Proxy

    The no variant resets the authtype to its default, which is none. • —No authentication required. none • —HTTP basic authentication. basic web proxy Copyright © 2010, Juniper Networks, Inc.

  • Page 383: Write

    Media Flow Controller Administrator’s Guide Media Flow Controller CLI Commands • —Configure HTTP basic authentication settings for the Web proxy. basic • —Specify a plaintext password for HTTP password <plaintext_password> basic authentication with an authenticating proxy. Only used if the web proxy auth authtype is set to basic.
  • Page 384 Media Flow Controller CLI Commands Media Flow Controller Administrator’s Guide write Copyright © 2010, Juniper Networks, Inc.

  • Page 385: Media Flow Controller Mib Definitions

    OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION "One-minute CPU load in hundreths" ::= { cpu 1 } cpuLoad5 OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION "Five-minute CPU load in hundreths" Copyright © 2010, Juniper Networks, Inc. Variables...
  • Page 386 OCTET STRING, procNumFailures Unsigned32 procIndex OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION "Synthetic numeric unique ID of process" ::= { procEntry 1 } procName OBJECT-TYPE SYNTAX OCTET STRING MAX-ACCESS read-only STATUS current DESCRIPTION Variables Copyright © 2010, Juniper Networks, Inc.
  • Page 387 Media Flow Controller Administrator’s Guide Media Flow Controller MIB Definitions "Unique name of process" ::= { procEntry 2 } procStatus OBJECT-TYPE SYNTAX OCTET STRING MAX-ACCESS read-only STATUS current DESCRIPTION "Current state of process" ::= { procEntry 3 } procNumFailures OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS...

  • Page 388: Notifications

    "The average CPU utilization in the past minute has gone above the acceptable threshold" ::= { notificationPrefix 3 } pagingActivityHigh NOTIFICATION-TYPE STATUS current DESCRIPTION "The system has been paging excessively (thrashing)" ::= { notificationPrefix 4 } smartError NOTIFICATION-TYPE NOTIFICATIONS Copyright © 2010, Juniper Networks, Inc.
  • Page 389 Media Flow Controller Administrator’s Guide Media Flow Controller MIB Definitions STATUS current DESCRIPTION "SMART has sent an event about a possible disk error" ::= { notificationPrefix 5 } unexpectedShutdown NOTIFICATION-TYPE STATUS current DESCRIPTION "The system has shut down unexpectedly" ::= { notificationPrefix 6 } diskSpaceLow NOTIFICATION-TYPE STATUS current...
  • Page 390 Media Flow Controller MIB Definitions Media Flow Controller Administrator’s Guide NOTIFICATIONS Copyright © 2010, Juniper Networks, Inc.

  • Page 391: Index

    SSH client known host SSH server listen interface auto-logout TACACS server users Management Console Admin up, interface state admin user default password banner command admission control, overview banners AES-128, about commands alarm rate-limit count Copyright © 2010, Juniper Networks, Inc.
  • Page 392 CMC rendezvous (Web Interface) options cut and paste for interfaces prefix mode DSR load balancing cli command email event notifications interfaces, hostname, domain list, DNS, and default client gateway (CLI) DHCP restart (CLI) Copyright © 2010, Juniper Networks, Inc.
  • Page 393 (CLI) AFR (AssuredFlow rate) protocol and interfaces (Web Interface) restarting connection limit, unlicensed SmoothFlow, about delivery protocol interface supported HTTP requests Copyright © 2010, Juniper Networks, Inc.
  • Page 394 Management Console interface information Management Console settings SNMP (CLI) namespaces SNMP (Web Interface) notification settings SSH server routing information stats alarms SNMP settings traps SSH client information encoding schemes, supported Copyright © 2010, Juniper Networks, Inc.
  • Page 395 SSH pre-staging content, How To add ⁄ delete second address requirement bond user, for namespace (CLI) bonding fuselog command changing IP addresses configuring (CLI) cut and paste configuring global delivery protocol delivery options (CLI) Copyright © 2010, Juniper Networks, Inc.
  • Page 396 HTTPD mfdlog command SNMP motd (message of the day) banner, set SSH, server moving listen port, delivery protocol configuration files listing image files namespace objects stats files namespaces MTU, interfaces Copyright © 2010, Juniper Networks, Inc.
  • Page 397 AssuredFlow rate delivery service reverting Copyright © 2010, Juniper Networks, Inc.
  • Page 398 UUID for namespace set clock severity level, logs system log (syslog) access log replication SFTP format and requirement interpreting SHA1, about uploading show command viewing ⁄ uploading shutdown interface signature, for image installs Copyright © 2010, Juniper Networks, Inc.
  • Page 399 Media Flow Controller license restrictions objects in cache minimum configurations version, system namespace configurations video players, supported namespaces, activating viewing notifications accesslog RAID arrays 227, accesslogs restarting the delivery service cache logs RTSP access methods error logs Copyright © 2010, Juniper Networks, Inc.
  • Page 400 HDDs excessive debugging output minimum configuration requirements removing disks reverting to factory defaults saving settings watermark, definition web command Web interface configuring (CLI) web proxy command write command YouTube, type youtube virtual players Copyright © 2010, Juniper Networks, Inc.

This manual is also suitable for:

Media flow controller 2.0.4

Table of Contents