Media Flow Controller Configuration Tasks (CLI)
Media Flow Controller Administrator’s Guide
92
Managing the Media Flow Controller Disk Cache (CLI)
Copyright © 2010, Juniper Networks, Inc.
test-vos (config namespace test) #
show usernames
USERNAME FULL NAME CAPABILITY ACCOUNT STATUS
admin System Administrator admin No password required for login
cmcrendv CMC Rendezvous User cmcrendv Local password login disabled
monitor System Monitor monitor No password required for login
test_ftpuser ftpuser Password set
test-vos (config namespace test) # no pre-stage ftp user test_ftpuser
test-vos (config namespace test) # show usernames
USERNAME FULL NAME CAPABILITY ACCOUNT STATUS
admin System Administrator admin No password required for login
cmcrendv CMC Rendezvous User cmcrendv Local password login disabled
monitor System Monitor monitor No password required for login
test_ftpuser ftpuser Local password login disabled
8.
Also optional, add an existing virtual-player to the new namespace.
virtual-player <name>
9.
Activate the namespace. Verify configurations with show namespace <name>.
status active
10. Type exit to leave namespace configuration mode.
Example:
test-vos (config namespace test) #
virtual-player test
test-vos (config namespace test) #
status active
test-vos (config namespace test) #
exit
Note!
Configuration changes, including a namespace deletion, may not be updated for up to
30 seconds. This is due to a deferred update scheme that requires an HTTP request. An
internal probe ensures that such a request occurs at least every 30 seconds.
Managing the Media Flow Controller Disk Cache (CLI)
The media caches/disks are active and enabled by default and typically require no configuring.
However, you must deactivate and disable disks and caching to change disks. Before you
activate or enable a cache, run show media-cache disk list and get the name assigned to
the disk to use in configuration. See
media-cache
for CLI details.
Media Flow Controller supports 3 cache tiers corresponding to SSD (tier 1), SAS HDD (tier 2),
and SATA HDD (tier 3). "Hot" content generally stays in tier1 (the highest). Media Flow
Controller promotes contents between the cache tiers based on content hotness (see
““Hot”
Content (Short Tail vs. Long Tail)” on page 31
for definition). As content gets hotter, it is
promoted to the next higher tier. 1st time content is always put in the lowest cache tier. The
default values are: tier1 weight = 6, tier2 weight = 2, tier3 weight = 1. So, any content
requested once is cached in Tier 3; requested twice and it is promoted to Tier2; and, if
requested 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
Summary of Contents for MEDIA FLOW CONTROLLER 2.0.4 -
Page 6: ...Media Flow Controller Administrator s Guide VI Copyright 2010 Juniper Networks Inc...
Page 24: ...LIST OF FIGURES XXIV Copyright 2010 Juniper Networks Inc...
Page 37: ...Copyright 2010 Juniper Networks Inc 37 PART 1 Media Flow Controller Administration...
Page 38: ...Media Flow Controller Administrator s Guide 38 Copyright 2010 Juniper Networks Inc...
Page 285: ...Copyright 2010 Juniper Networks Inc 285 PART 2 Media Flow Controller Command and MIB Reference...
Page 286: ...Media Flow Controller Administrator s Guide 286 Copyright 2010 Juniper Networks Inc...
