Release 2.0.5
Media Flow Controller 2.0.5 Release Notes
12
Release Installation for Generic Hardware: Guidelines
Copyright © 2010, Juniper Networks, Inc.
VXA Series 2002 and 2010 Port Naming
When an Ethernet card is installed in the top slot, the ports are named left to right:
eth10 eth11 eth12 eth13 (when a four port card)
eth10 eth11 (when a two port card)
When an Ethernet card is installed in the middle slot, the ports are named left to right:
eth20 eth21 eth22 eth23 (when a four port card)
eth20 eth21 (when a two port card)
Release Installation for Generic Hardware: Guidelines
Complete procedures for installing the system software on generic hardware are available in
the
Juniper Networks Media Flow Controller and Media Flow Manager Installation Guide
.
New software releases are available for download from the Juniper Networks website at
http://www.juniper.net/support/products/mediaflow
. You can use the downloaded image
bundle to create your own software CDs (for generic hardware installations only).
This section provides information on how Media Flow Controller works with Host Bus
Adapters/Hard Drive Controllers.
Host Bus Adapter / Hard Drive Controller
Media Flow Controller does not natively support RAID of any kind on any hard drive or
combination of hard drives. We recommend that ALL hard disk drives (HDDs) are configured
in "Just a Bunch of Disks" (JBOD) mode with write-cache disabled, regardless of controller
battery.
At initialization, Media Flow Controller attempts to uniquely identify each HDD by its
manufacturer-given serial number. This allows caches, the physical disks to which Media Flow
Controller writes cached data, to be removed and reinserted into a system without data loss or
the need to re-initialize. Also, because Media Flow Controller is able to uniquely identify
caches, they may be transferred to to another Media Flow Controller (removed from one
physical server and inserted in another running the same version of Media Flow Controller).
This lets you hot-swap caches for either new HDDs (provided the controller supports
hot-swap) or existing caches—without interrupting content delivery or restarting Media Flow
Controller.
Media Flow Controller also attempts to identify the HDD type: SAS, SATA, or SSD. With this
information, Media Flow Controller assigns a cache tier to each cache. Cache tiers are how
Media Flow Controller divides the storage of “hot content” (frequently accessed) from “long-tail
content” (infrequently accessed).
Important!
With RAID enabled, Media Flow Controller cannot determine an HDD’s serial
number, or type.
Choosing a Controller for Your Media Flow Controller
Media Flow Controller has been tested with, and supports, a wide range of Host Bus Adapters
(HBAs) including those made by Intel™, 3ware™, LSI™, Adaptec™ as well as original
equipment manufacturer (OEM) cards by IBM™, HP™ (SmartArray™), Dell™ (Perc™),
Sun™, and the controllers typically found in SuperMicro™ based systems.