media flow media flow controller installation guide · 2014-10-06 · test-vos (config) # image...

Media Flow

Media Flow Controller Installation Guide

Release

12.3.x

Published: 2014-10-06

Copyright © 2014, Juniper Networks, Inc.

Juniper Networks, Inc.1194 North Mathilda AvenueSunnyvale, California 94089USA408-745-2000www.juniper.net

Juniper Networks, Junos, Steel-Belted Radius, NetScreen, and ScreenOS are registered trademarks of Juniper Networks, Inc. in the UnitedStates and other countries. The Juniper Networks Logo, the Junos logo, and JunosE are trademarks of Juniper Networks, Inc. All othertrademarks, service marks, registered trademarks, or registered service marks are the property of their respective owners.

Juniper Networks assumes no responsibility for any inaccuracies in this document. Juniper Networks reserves the right to change, modify,transfer, or otherwise revise this publication without notice.

Media FlowMedia Flow Controller Installation GuideRelease 12.3.x, Revision 1Copyright © 2014, Juniper Networks, Inc.All rights reserved.

Revision HistoryAugust 2014 —Media Flow Controller Installation Guide

The information in this document is current as of the date on the title page.

YEAR 2000 NOTICE

Juniper Networks hardware and software products are Year 2000 compliant. Junos OS has no known time-related limitations through theyear 2038. However, the NTP application is known to have some difficulty in the year 2036.

ENDUSER LICENSE AGREEMENT

The Juniper Networks product that is the subject of this technical documentation consists of (or is intended for use with) Juniper Networkssoftware. Use of such software is subject to the terms and conditions of the End User License Agreement (“EULA”) posted athttp://www.juniper.net/support/eula.html. By downloading, installing or using such software, you agree to the terms and conditions ofthat EULA.

Copyright © 2014, Juniper Networks, Inc.ii

http://www.juniper.net/support/eula.html

Table of Contents

About This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v

Documentation and Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v

Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi

Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi

Supported Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi

Typographical Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi

Documentation Feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

Requesting Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii

Self-Help Online Tools and Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . viii

Opening a Case with JTAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

Part 1 Installing Media Flow Controller

Chapter 1 Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Obtaining Software for Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Upgrading Media Flow Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Upgrading (Web Interface) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Upgrading (CLI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Upgrade Order Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Upgrading Media Flow Controller to Release 12.3.x . . . . . . . . . . . . . . . . . . . . . . 7

Upgrading Versus Installing Media Flow Controller . . . . . . . . . . . . . . . . . . . . . . . . . 9

Pre-installation Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Release Installation Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Host Bus Adapter or Hard Drive Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Choosing a Controller for Your Media Flow Controller . . . . . . . . . . . . . . . . . . . 11

Configuring the Controller and Arrays for Optimum Performance . . . . . . . . . 12

Accessing the Console Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Media Flow Controller Minimum System Requirements . . . . . . . . . . . . . . . . . . . . . 12

Example: Machine Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Connecting and Logging In . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Changing Ethernet Name Assignments After Installation . . . . . . . . . . . . . . . . . . . 15

Rebooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Managing Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Saving and Applying a Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Known Installation Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Known Upgrade Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Using the DMI Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Unable to Fall Back from Media Flow Controller 12.3 to Release 11.B.3 . . . . . . 19

Other Upgrade Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

iiiCopyright © 2014, Juniper Networks, Inc.

Media Flow Controller Software Fallback Overview . . . . . . . . . . . . . . . . . . . . . . . . 21

Boot Disk Mirroring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Boot Disk Mirroring Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Configuring the VXA2000 Series Content Engine BIOS for Boot Disk

Mirroring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Installing Media Flow Controller Software on a VXA2000 Series Content

Engine for Boot Disk Mirroring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Resilvering a Failed Mirrored Boot Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Monitoring Boot Disk Mirroring Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Viewing Boot Disk Mirroring Events in the System Log . . . . . . . . . . . . . . 34

Viewing Boot Disk Mirroring Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Rebooting Media Flow Controller (CLI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Chapter 2 Installing Media Flow Controller with a CD or USB . . . . . . . . . . . . . . . . . . . . . 37

Before Installing Media Flow Controller with a CD or USB . . . . . . . . . . . . . . . . . . . 37

Creating CDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Ethernet Naming Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Flash Ethernet Port LEDs, Ethernet Naming Option 3 . . . . . . . . . . . . . . . . . . . 38

Configure Ethernet Names Interactively, Ethernet Naming Option 4 . . . . . . . 39

Specify Devices to Use For eth0 and eth1, Ethernet Naming Option 5 . . . . . . 41

Reset Ethernet Device Naming Back to Default, Ethernet Naming Option

6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Choosing to Cache on the First Drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Installing Media Flow Controller Software—CD or USB . . . . . . . . . . . . . . . . . . . . . 44

Setting Up Basic System Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Chapter 3 Installing Media Flow Controller with PXE . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

PXE Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Before Installing Media Flow Controller with PXE . . . . . . . . . . . . . . . . . . . . . . . . . 49

Setting Up PXE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

PXE Configuration File Installation Options . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Setting Up Your PXE Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Installing Media Flow Controller Software from the Network—PXE . . . . . . . . . . . 52

Part 2 Index

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Copyright © 2014, Juniper Networks, Inc.iv


About This Guide

The Juniper Networks Media Flow Controller Installation Guide is written for system and

network administrators who plan, implement, and manage media content delivery

environments. Its purpose is to guide you through the installation of Media Flow Controller

software on servers.

This guide is designed for network system administrators who are configuring and

monitoring a Juniper Networks Media Flow Controller media delivery and caching

appliance. To use this guide you need a broad understanding of networks in general,

networking principles, and networking configuration.

• Documentation and Release Notes on page v

• Objectives on page vi

• Audience on page vi

• Supported Platforms on page vi

• Typographical Conventions on page vi

• Documentation Feedback on page vii

• Requesting Technical Support on page viii

Documentation and Release Notes

For a list of related Media Flow Controller documentation, see theTechnicalDocumentation

page for Media Flow.

This document provides information about the following topics:

• “Getting Started” on page 3—Describes pre-installation planning and system

requirements applicable to all installations, and upgrade and reboot procedures.

• “Installing Media Flow Controller with a CD or USB” on page 37—Describes how to

create CD-ROM installation drives, how to use the Ethernet naming options, how to

install Juniper Networks Media Flow Controller using a CD-ROM or USB drive, and how

to configure basic network connections.

• “Installing Media Flow Controller with PXE” on page 49—Describes how to set up your

PXE server for a Media Flow Controller installation, how to install Media Flow Controller

using PXE, and how to configure basic network connections.

To obtain the most current version of all Juniper Networks®

technical documentation,

see the product documentation page on the Juniper Networks website at

vCopyright © 2014, Juniper Networks, Inc.

http://www.juniper.net/techpubs/en_US/release-independent/media-flow/information-products/pathway-pages/product/index.html


http://www.juniper.net/techpubs/ .

Juniper Networks supports a technical book program to publish books by Juniper Networks

engineers and subject matter experts with book publishers around the world. These

books go beyond the technical documentation to explore the nuances of network

architecture, deployment, and administration using Junos OS software and Juniper

Networks devices. In addition, the Juniper Networks Technical Library, published in

conjunction with O'Reilly Media, explores improving network security, reliability, and

availability using Junos OS configuration techniques. All the books are for sale at technical

bookstores and book outlets around the world. The current list can be viewed at

http://www.juniper.net/books .

Objectives

This document guides you through the installation of the Media Flow Controller software

on servers.

NOTE: For additional information about Junos OS—either corrections to, orinformation thatmight have been omitted from this guide—see the softwareReleaseNotes for your version on theTechnical Documentation page forMedia

Flow.

Audience

This guide is designed for network system administrators who are configuring and

monitoring a Juniper Networks Media Flow Controller media delivery and caching

appliance.

To use this guide you need a broad understanding of networks in general, the Internet in

particular, networking principles, and networking configuration.

Supported Platforms

For the features described in this guide, Juniper Networks Media Flow Controller currently

supports installation on the Juniper Networks VXA Series and generic x86 servers. For

details, see theMediaFlowControllerWithVXASeriesandMediaFlowControllerdatasheet.

Typographical Conventions

Table 1 describes the typefaces used in this book.

Table 1: Text and Syntax Conventions Used in This Book

ExampleDescriptionConvention

The origin server organizes media contenthierarchically.

Ordinary text.Plain Text

Copyright © 2014, Juniper Networks, Inc.vi


http://www.juniper.net/techpubs/

http://www.juniper.net/books



http://www.juniper.net/us/en/local/pdf/datasheets/1000316-en.pdf

Table 1: Text and Syntax Conventions Used in This Book (continued)

ExampleDescriptionConvention

Use the interface command to configure IPaddresses.

In the Management Console, use the Setup >Date and time page.

Commands in running text, and screen elementssuch as page titles, and option labels.

Bold Text

See the Juniper Networks Media Flow ControllerAdministrator’s Guide and CLI CommandReference.

show file file_name

Book titles, emphasis, and variables.

For variables the text must be replaced bywhatever it represents. In the second exampleto the right, the user would replace file_namewith the name of the specific file.

Italic Text

interface interface_name

Please enter your IP address.

Command keywords.

Text displayed online at a command line.

Fixed-width Text

interface eth0 ip address IP addressCommand text that you type.Fixed-width Bold Text

web proxy host IP_address[port TCP_port]

Optional commands. Anything not enclosed inbrackets must be specified.

[ ] (square brackets)

web proxy auth authtype(none | basic)

Represent a set of mutually exclusive options,where one option is required.

( ) (parentheses)

analytics last-evict-timediff (1 | seconds)

Separates mutually exclusive options.

You can enter one of the options separated bythe vertical bar, but you cannot enter multipleoptions in a single use of the command.

A vertical bar can be used to separate optionalor required options.

| (pipe symbol)

clock timezone zone[zone] ...

An ellipsis (...) indicates that the previous optioncan be repeated multiple times with differentvalues. It can be used inside or outside ofbrackets.

... (ellipsis)

Documentation Feedback

We encourage you to provide feedback, comments, and suggestions so that we can

improve the documentation. You can send your comments to

[email protected], or fill out the documentation feedback form at

https://www.juniper.net/cgi-bin/docbugreport/. If you are using e-mail, be sure to include

the following information with your comments:

• Document or topic name

• URL or page number

viiCopyright © 2014, Juniper Networks, Inc.

About This Guide

https://www.juniper.net/cgi-bin/docbugreport/

• Software release version (if applicable)

Requesting Technical Support

Technical product support is available through the Juniper Networks Technical Assistance

Center (JTAC). If you are a customer with an active J-Care or JNASC support contract,

or are covered under warranty, and need post-sales technical support, you can access

our tools and resources online or open a case with JTAC.

• JTAC Policies—For a complete understanding of our JTAC procedures and policies,

review the JTAC User Guide located at

http://www.juniper.net/customers/support/downloads/710059.pdf

• ProductWarranties—For product warranty information, visit

http://www.juniper.net/support/warranty/

• JTAC Hours of Operation—The JTAC centers have resources available 24 hours a day,

7 days a week, 365 days a year.

Self-Help Online Tools and Resources

For quick and easy problem resolution, Juniper Networks has designed an online

self-service portal called the Customer Support Center (CSC) that provides you with the

following features:

• Find CSC offerings:

http://www.juniper.net/customers/support/

• Search for known bugs:

http://www2.juniper.net/kb/

• Find product documentation:


• Find solutions and answer questions using our Knowledge Base:

http://kb.juniper.net/

• Download the latest versions of software and review release notes:

http://www.juniper.net/customers/csc/software/

• Search technical bulletins for relevant hardware and software notifications:

https://www.juniper.net/alerts/

• Join and participate in the Juniper Networks Community Forum:

http://www.juniper.net/company/communities/

• Open a case online in the CSC Case Manager:

http://www.juniper.net/cm/

To verify service entitlement by product serial number, use our Serial Number Entitlement

(SNE) Tool located at

https://tools.juniper.net/SerialNumberEntitlementSearch/

Copyright © 2014, Juniper Networks, Inc.viii




http://www.juniper.net/customers/support/

http://www2.juniper.net/kb/



http://www.juniper.net/customers/csc/software/

https://www.juniper.net/alerts/

http://www.juniper.net/company/communities/


https://tools.juniper.net/SerialNumberEntitlementSearch/

Opening a Casewith JTAC

You can open a case with JTAC on the Web or by telephone.

• Use the Case Manager tool in the CSC at


• Call 1-888-314-JTAC

(1-888-314-5822—toll free in the USA, Canada, and Mexico)

For international or direct-dial options in countries without toll-free numbers, visit

http://www.juniper.net/support/requesting-support.html

ixCopyright © 2014, Juniper Networks, Inc.

About This Guide


http://www.juniper.net/support/requesting-support.html

PART 1

Installing Media Flow Controller

• Getting Started on page 3

• Installing Media Flow Controller with a CD or USB on page 37

• Installing Media Flow Controller with PXE on page 49

1Copyright © 2014, Juniper Networks, Inc.

CHAPTER 1

Getting Started

This chapter describes pre-installation planning and requirements that applies to all

types of installations; as well as upgrading, rebooting, and basic configuration file

management.

• Obtaining Software for Installation on page 3

• Upgrading Media Flow Controller on page 4

• Upgrading Versus Installing Media Flow Controller on page 9

• Pre-installation Planning on page 9

• Release Installation Guidelines on page 10

• Accessing the Console Port on page 12

• Media Flow Controller Minimum System Requirements on page 12

• Example: Machine Setup on page 13

• Connecting and Logging In on page 15

• Changing Ethernet Name Assignments After Installation on page 15

• Rebooting on page 16

• Managing Configuration Files on page 17

• Saving and Applying a Configuration on page 17

• Known Installation Issues on page 19

• Known Upgrade Issues on page 19

• Media Flow Controller Software Fallback Overview on page 21

• Boot Disk Mirroring on page 22

Obtaining Software for Installation

There are two ways you can obtain the Media Flow Controller software for installation

from Juniper Networks Support:

• Juniper Networks ships you a CD or USB drive with the software; you can also download

an ISO image and burn a CD. This guide describes how to install from a CD or USB

drive.

• You use preboot execution environment (PXE) to obtain the software image. You must

have a PXE server configured in order to use the PXE installation option and a Web


server to serve the image. How to configure your PXE server for Media Flow Controller

installation and how to install with PXE is described in this guide.

RelatedDocumentation

Requesting Technical Support on page viii (for PXE, USB, or CD installation packages).•

• Upgrading (Web Interface) on page 4

• Upgrading (CLI) on page 5

• Installing Media Flow Controller with a CD or USB on page 37

• Installing Media Flow Controller with PXE on page 49

UpgradingMedia Flow Controller

Media Flow Controller upgrades maintain saved data and configurations. However, if

you reinstall the software (as opposed to upgrade only), you must save your current

configuration to another system if you want to keep it, because the installation process

deletes all the information on the root drive where the configuration data is stored.



• Upgrade Order Requirements on page 7

• Upgrading Media Flow Controller to Release 12.3.x on page 7

Upgrading (Web Interface)

When upgrades are available, Juniper Networks will broadcast the upgrade URL to use

in this procedure. The upgrade preserves the current, saved, configurations; however,

you may still want to save the current configuration to a file on another system by

following this procedure, “Saving and Applying a Configuration” on page 17.

You can use the Web-based Management Console, SystemConfig > Upgrade page to

easily upgrade your system if you have an install image URL or have obtained the image

and installed it locally.

NOTE: After upgrading to the imageusing theSystemConfig>Upgradepage,

youmust go to the SystemConfig > Reboot page and reboot your system for

the upgrade to complete.

To install Media Flow Controller, which means removing all the data on the root drive for

a fresh installation, see the following installation chapters, as appropriate.

• Saving and Applying a Configuration on page 17






Upgrading (CLI)

When upgrades are available, Juniper Networks will broadcast the upgrade URL to use

in this procedure. The upgrade preserves the current, saved, configurations; however,

you may still want to save the current configuration to a file on another system by

following this procedure, “Saving and Applying a Configuration” on page 17.

To upgrade your system using the CLI:

1. Log in and enter Configure mode.

enableconfigure terminal

You can now fetch and install the upgrade image.

2. Fetch the configuration upgrade image file with the Juniper Networks URL.

Although there may be two upgrade files located at the Juniper Networks URL, the

zipped tar file (.tgz) and the image file (.img), you should disregard the zipped tar file

(.tgz) and download only the image (.img) file.

image fetchURL/filename

The upgrade image is now locally available.

3. Install the image.

image install filename

The upgrade image is installed.

4. Verify which boot image contains the upgrade.

show images

The boot partitions are displayed showing image locations and which partition is set

to boot next.

5. Switch to the boot partition containing the upgrade image, if needed; you can verify

that the correct partition is set to boot next by repeating Step 4.

boot system next OR image boot next

You can now reboot the system with the installed image.

6. Reboot to that partition.

reload

The system boots to the upgrade image.

7. Verify that the new image is booted.

show version

Example:

test-vos (config) # image fetch http://123.45.678.9/mfg/mfc-12.2.0-rc-latest/image-mfc-12.2.0-rc-1_11818_184.img100.0% [#################################################################]


Chapter 1: Getting Started

test-vos (config) # image install ?<image filename>image-mfc-12.2.0-rc-1_11818_184.imgtest-vos (config) # image install image-mfc-12.2.0-rc-1_11818_184.imgStep 1 of 4: Verify Image 100.0% [#################################################################]Step 2 of 4: Uncompress Image 100.0% [#################################################################]Step 3 of 4: Create Filesystems 100.0% [#################################################################]Step 4 of 4: Extract Image 100.0% [#################################################################]test-vos (config) #test-vos (config) # show imageImages available to be installed: image-mfc-12.2.0-rc-1_11818_184.img mfc-12.2.0-rc 1_11818_184Installed images: Partition 1: mfc-2.0.2-rc 73_10732_170 Partition 2: mfc-12.2.0-rc 1_11818_184Last boot partition: 1Next boot partition: 1No boot manager password is set.No image install currently in progress.test-vos (config) # boot system nexttest-vos (config) # show imageImages available to be installed: image-mfc-12.2.0-rc-1_11818_184.img mfc-12.2.0-rc 1_11818_184Installed images: Partition 1: mfc-2.0.2-rc 73_10732_170 Partition 2: mfc-12.2.0-rc 1_11818_184Last boot partition: 1Next boot partition: 2No boot manager password is set.No image install currently in progress.test-vos (config) # reloadlogin as: adminJuniper Networks Media Flow ControllerLast login: Fri Aug 13 22:56:40 2010 from 172.23.7.251Juniper Networks Media Flow Controllertest-vos > entest-vos # configure terminaltest-vos (config) # show versionCopyright (c) 2008-2010 by Juniper Networks, IncProduct name: mfcProduct release: mfc-12.2.0-rcBuild ID: 1_23456_789Build date: 2010-08-12 13:59:35Target arch: x86_64Built by: build@build04Uptime: 4m 42.860sProduct model: standardHost ID: 44454C4C-1234-C6C04F443931System memory: 477 MB used / 1532 MB free / 2009 MB totalSwap: 0 MB used / 1028 MB free / 1028 MB totalNumber of CPUs: 2



CPU load averages: 2.41 / 1.10 / 0.44test-vos (config) #

Upgrade Order Requirements

You cannot upgrade directly from Media Flow Controller Release 11.X to 12.3. You must

first upgrade to Release 12.2 and then upgrade to Release 12.3. If you do not follow this

upgrade path, you might have to reinstall the device.

Upgrading Directly FromMedia Flow Controller Release 11.X to 12.3

An alternative method to first upgrading to Media Flow Controller Release 12.2 is as

follows while Release 11.X is still installed:

• Install the restricted license.

• In the Linux shell (_shell), execute the command mount -o rw,remount /bootmgr.

• Edit the file /bootmgr/boot/grub/grub.conf.

• Remove the two instances of the string intel_iommu=on iommu=ptfrom the kernel

lines.

• Execute the command mount -o ro,remount /bootmgr.

UpgradingMedia Flow Controller to Release 12.3.x

Use the criteria below to determine how to upgrade to Media Flow Controller 12.3.x:

NOTE: You cannot upgrade directly fromMedia Flow Controller Release 11.Xto 12.3. Youmust first upgrade to Release 12.2 and then upgrade to Release12.3. If you do not follow this upgrade path, youmight have to reinstall thedevice. An alternativemethod to first upgrading to Media Flow ControllerRelease 12.2 is explained in “Upgrade Order Requirements” on page 7.

• Non-VXA hardware users should use the standard upgrade procedure documented in

“Upgrading (Web Interface)” on page 4 or “Upgrading (CLI)” on page 5 to upgrade

to Release 12.3.

• VXA customers upgrading from Media Flow Controller 12.1 or later should use the

standard upgrade procedure documented in “Upgrading (Web Interface)” on page 4

or “Upgrading (CLI)” on page 5 to upgrade to Release 12.3.

• VXA customers upgrading from any version prior to Release 12.1 must follow the

procedure below. Customers upgrading from Media Flow Controller prior to Release

11.B.3 must upgrade to Media Flow Controller 11.B.3 or 11.B.4 before following the

procedure in this section.

To upgrade to Media Flow Controller Release 11.B.3-4, follow the instructions in theMedia

Flow Controller Installation Guide.

When it is not feasible to upgrade to Media Flow Controller Release 11.B.3-4, contact

JTAC for a possible workaround.



After the Media Flow Controller is upgraded to Release 11.B.3-4, complete the following

steps at the CLI prompt on the serial console:

1. Log in as “admin.”

2. Enter these commands:

enable

image remanufacture resize

3. After a delay of a minute or two, the following appears:

%*** Starting resize. Expect long delays.Save bootmgrSave boot1Save boot2Save root1Save root2Save configSave var

ShutdownMFC and switch to remanufacturing environment.

Remanufacture starting in background. You will be logged off,and the systemwill reboot when the remanufacture is complete.

Wait for login promptSystem shutdown initiated -- logging off.

Login as 'resize' to complete the boot disk resize operation.Wait until you see this message: 'INIT: Switching to runlevel: 4'Then press enter and then login as 'resize' or 'restore'

Stopping portmap: [FAILED]INIT: nomore processes left in this runlevelEXT3 FS on sd__, internal journalINIT: version 2.86 reloadingINIT: nomore processes left in this runlevelINIT: Switching to runlevel: 4

Login as 'resize' to complete the boot disk resize operation.Wait until you see this message: 'INIT: Switching to runlevel: 4'Then press enter and then login as 'resize' or 'restore'

INIT: version 2.86 reloading

4. Press enter and log in as “resize.”

The “Resize Root operation” starts, which can take several minutes. When the operation

is complete, the Media Flow Controller reboots.



If you are upgrading from Media Flow Controller version 11.X or earlier, you must now

follow the “Upgrading Directly From Media Flow Controller Release 11.x to 12.3”

instructions, found in “Upgrade Order Requirements” on page 7.

5. Upgrade to Media Flow Controller Release 12.3.2 using the standard upgrade procedure

documented in “Upgrading (Web Interface)” on page 4 or “Upgrading (CLI)” on

page 5.


Saving and Applying a Configuration on page 17•




Upgrading Versus Installing Media Flow Controller

There are restrictions on the versions of Media Flow Controller from which you can

upgrade. See the Media Flow Controller Release Notes for release-specific upgrade

requirements.

When upgrading to a newer Media Flow Controller version rather than reinstalling the

device with a new Media Flow Controller version, all configuration and cached data is

maintained. When reinstalling Media Flow Controller software all configuration data is

deleted, but you have the option to keep the cache data. Even when you choose this

option, in most cases, all cache data that is on the root drive is deleted.

Thus when reinstalling, you should first save the configuration data to another device so

that you can restore it after the reinstallation is completed. See “Saving and Applying a

Configuration” on page 17.

When applying a configuration from an older version there are some known issues. Please

refer to “Known Upgrade Issues” on page 19.






Pre-installation Planning

Before installing Juniper Networks software, ensure that your hardware meets these

conditions:

• Running optimally (all hardware diagnostics have been run and passed successfully).

• All data is backed up; Juniper Networks Media Flow Controller completely formats all

disks when installed.



• Top-quality cables are used. We recommend Category 5e or Category 6 for Gigabit

Ethernet, CAT6A for 10-Gigabit Ethernet, or Fiber cables. However, Category 5 cables

can be used for Gigabit Ethernet if the cable lengths are expected to be short (for

example, 5 feet or shorter). A poorly functioning cable can inhibit performance.

• NIC is present.

• Console server or terminal server is available (recommended).

You also need to know:

• Which physical ports you want named eth0 and eth1. This is important because eth0

(management interface) and eth1 (recommended origin-fetch interface) are usually

not automatically assigned to the optimal ports (non-traffic bearing); instead, you

must make this assignment a part of the installation.

• Hostnames or IP addresses (including but not limited to subnet mask, default gateway)

for traffic, and management ports.

• Hostnames or IP addresses for external servers such as origin servers or libraries, DNS,

NTP, logging, or storage servers.

NOTE: Media Flow Controller does not support RAID arrays.


Obtaining Software for Installation on page 3•


Release Installation Guidelines

This section provides information about the way Media Flow Controller works with Host

Bus Adapters or Hard Drive Controllers.

• Host Bus Adapter or Hard Drive Controller on page 11

• Choosing a Controller for Your Media Flow Controller on page 11

• Configuring the Controller and Arrays for Optimum Performance on page 12



Host Bus Adapter or 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 thatallhard disk drives (HDDs) are configured

in “Just a Bunch of Disks” (JBOD) mode withwrite-cachedisabled, 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 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 the way Media Flow Controller divides the storage of “hot content” (frequently

accessed) from “long-tail content” (infrequently accessed).

NOTE: With RAID enabled, Media Flow Controller cannot determine theHDD’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 OEM

(original equipment manufacturer) cards by IBM, HP (SmartArray), Dell (Perc), Sun, and

the controllers typically found in SuperMicro-based systems.

The best controller for your Media Flow Controller depends upon the number and type

of HDDs in your system, as well as factors such as connecting to an external JBOD.

Generically, Media Flow Controller is most compatible with HBAs that support standard

SCSI passthrough, assign standard Linux device names (that is, /dev/sda, /dev/sdb, and

so forth), and allow arrays of one physical disk to be created.



Configuring the Controller and Arrays for OptimumPerformance

For controllers that require arrays or virtual disks to be defined before physical disks are

presented to the BIOS, and to the operating system, and are set as bootable, you must

configure the Controller BIOS to prepare the hard drives to be caches. To do this:

• Set up each physical HDD as an individual array or virtual disk (sometimes you must

set up a RAID 0 of one drive).

• Disable write-cache.

For controllers that do not require arrays or virtual disks to be defined (that is, LSI 1068e

with Software RAID disabled), no explicit configuration is required.


Accessing the Console Port on page 12•



Accessing the Console Port

We recommend you use the Serial Console for first-time access and installation. To

access the console port:

• Set your initial console terminal settings to match the default console settings on

Juniper Networks Media Flow Controller:

• 9600 baud rate

• No parity

• 8 data bits

• 1 stop bit

• No flow control (console port only)


Pre-installation Planning on page 9•

• Connecting and Logging In on page 15

Media Flow Controller MinimumSystemRequirements

NOTE: This section provides a high-level overview of Media Flow Controllerminimum system requirements. For themost up-to-date and completeinformation, see theMedia Flow Controller With VXA Series andMedia Flow

Controller datasheet.





Media Flow Controller can run on Juniper Networks VXA Series appliances or standard

x86 64-bit servers. Table 2 on page 13 shows the configuration that is either required or

recommended for optimal performance when running the Media Flow Controller software

on generic (non-Juniper Networks) x86 servers.

Table 2: Media Flow Controller Recommended Hardware Configuration

Transparent ProxyReverse ProxyItem

64-bit x86, Dual Quad Core or more,minimum of 2.4 GHz speed

64-bit x86, Dual Quad Core or more,minimum of 2.4 GHz speed

Processor

36 GB or more8 GB or moreRAM

Up to 16 direct attached storage (DAS) drives such as SATA, SAS, or SSD, configuredas JBODs (just a bunch of disks)

Direct Attached Storage

Intel Extreme, or Intel Mainstream, for higher performanceSolid State Drives

Dell SAS 6/ir, HP SC44Ge

LSI SAS 3442E-R/3081E-R

LSI 1068/1064/1078

LSI SAS2008

LSI Logic or Symbios Logic SAS1068E PCI-Express Fusion-MPT SAS

HP Smart Array G6 controllers (rev01)

3Ware 9690SA

Disk Controllers (RAID should bedisabled.)

Intel 1 GbE (82574, 82580, 82571 (will be EOLed), 82576, 82575eb), Intel 10 GbE82599

Chelsio 10 GbE

Network Controllers

One 100 Mbps or 1 Gbps management interface

Up to 10 x 1 Gbps or 2 x 10 Gbps media delivery interfaces

Network Interfaces




Example: Machine Setup

Table 3 on page 14 provides details of a sample configuration; your configuration can

differ considerably. In Table 3 on page 14 and Figure 1 on page 14, the appliance wiring

logic is:

• Eth0—Running SNMP, sending analytics to another machine, Web management, SSH,

and Telnet; connected to your internal network.



• Eth 1—Upstream fetching content from origin; connected to the network that connects

to the origin server.

• Eth 2 - 5—Servicing traffic; connected to the public Internet.

Eth 0 and Eth 1 are onboard interfaces whereas Eth 2-5 traffic port recommendations

are Intel Pro/1000 PT/VT dual- or quad-port NIC for Gigabit Ethernet. These are the

minimum TCP/ UDP port requirements; other ports can be opened up on an as-needed

basis. By default, the Media Flow Controller management port is 8080.

NOTE: The installation procedure provides several options for correctlyidentifying and naming the Ethernet interfaces. See “Ethernet NamingOptions” on page 38 in“Installing Media Flow Controller with a CD or USB” on page 37 for details.

Figure 1: Example Connectivity

Table 3: ExampleMachine Setup of Management and Traffic Ports

PurposeInternetAccess

OpenPortsGatewaySubnet MaskIP AddressConnectivityInterface

Managementyes8080,22

192.168.1.1255.255.255.0192.168.1.100onboardEth 0

Origin fetchyes80not applicable255.255.255.0172.20.46.10*onboardEth 1

Trafficnot applicable80not applicable255.255.255.010.1.1.11PCIe cardEth 2





Table 3: ExampleMachine Setup of Management and Traffic Ports (continued)

PurposeInternetAccess

OpenPortsGatewaySubnet MaskIP AddressConnectivityInterface


* Eth0 AND Eth1 can be on the same subnet; this examples indicates they are not.




Connecting and Logging In

You can connect to the command-line interface (CLI) with SSH, Telnet (once enabled,

Telnet is disabled by default), or serial console using the IP address of your Media Flow

Controller. The appliance responds with a login prompt.

To connect to the CLI:

1. Enter admin as the user; there is no default password.

2. After you have connected, enterenable (for Enable mode) and thenconfigure terminal(for Configure mode) to begin configuring Media Flow Controller.

Likewise, you can log in to the Web-based Management Console by entering the IP

address and port 8080 in a browser window and using admin as the login name.


Accessing the Console Port on page 12•

Changing Ethernet Name Assignments After Installation

When installing Media Flow Controller 2.0 or earlier software to restore or upgrade it, if

you do not assign the correct port to eth0 during installation, your licenses may not work

because the 2.0 and earlier licenses are tied to the MAC address of the management

interface (eth0). The installation process gives you several Ethernet naming options to

configure the eth0 port and to verify that all the interfaces are named correctly; however,

if you misconfigure eth0 during installation, and you choose to not do a reinstallation to

correct the naming, there is a workaround using the CLI.

NOTE: The CLI to set eth0 automatically renames some or all of the other

interfaces as well.

To use the CLI to name the interface to use as eth0:

1. Enter enable on one line and configure terminal on the next to enter Configure mode.

2. Enter show license to see what MAC address your licenses are tied to.



3. Enter show interface to see which interfaces the system discovered and determine

which one you want for eth0.

4. Usemanagement interfaceMAC_address to name the interface with the correct MAC

address to be eth0. All interfaces are renamed.

5. Enter reload reboot.

6. After the machine is rebooted, enter show interface again to determine what the new

Ethernet name assignments are.

7. Enter show license to confirm that your licenses are working.




• Ethernet Naming Options on page 38

Rebooting

You can either reboot or shut down the software; if you use shutdown, the system does

not reboot until it is power-cycled. To reboot using the CLI:

1. From Enable mode or Configure mode, reboot or shut down the system.

reload

2. Set boot parameters; optionally specify from which location the image boots by

default. There are only two locations to choose from so the options are 1 and 2 for

location ID. If you use next, set the boot location to be the next one after the one

currently booted from.

boot system {location location_ID | next}

3. View boot parameters.

boot ?

4. View current settings.

show bootvar

To reboot the system after an upgrade, using the Web interface, go to the SystemConfig

> Reboot page.








Managing Configuration Files

You can save a binary file with all current configuration data that can be used to restore

the system configuration. You can also reset custom configurations to their factory

defaults, upload a saved configuration, and import a configuration from another Media

Flow Controller.

To manage configuration files using the CLI:

1. From Configure mode, view configuration file options.

configuration ?


show configuration

3. View configuration file viewing options.

show configuration ?

4. Make a configuration file active.

configuration switch-to filename

5. Save the current configuration through reboots.

write memory

To upload a text file with CLI commands (executed immediately in the running

configuration), or to enter CLI commands to be executed immediately, using the

Management Console, go to the Setup > Configurations page.






Saving and Applying a Configuration

You can save a binary file with all current configuration data that can be used to restore

the system configuration. You can also reset custom configurations to their factory

defaults, upload a saved configuration, and import a configuration from another Media

Flow Controller.

To save and apply a configuration using the CLI:

1. From Enable or Configure mode, save a configuration to a file; use no-switch to leave

the current configuration active. Use showconfiguration files to see the saved filename.

configuration write to file_name no-switch

2. Use SCP to send the just-saved configuration file to a server (must have SCP installed).



configuration upload file_name URL

3. When you are ready, fetch the saved configuration file.

configuration fetchURL/file_name

4. Verify that you have the saved configuration file.

show configuration files

5. Switch to the saved configuration.

configuration switch-to file_name

Example:

test-vos (config) # configuration write to 04_01_09 no-switchtest-vos (config) # show configuration files04_01_09initial (active)initial.baktest-vos (config) # configuration upload 04_01_09 scp://joe@sv05/home/joePassword: *******test-vos (config) # configuration delete 04_01_09test-vos (config) # show configuration filesinitial (active)initial.baktest-vos (config) # configuration fetch scp://joe@sv05/home/joe/04_01_09Password: *******test-vos (config) # show configuration files04_01_09initial (active)initial.baktest-vos (config) # configuration switch-to 04_01_09test-vos (config) # show configuration files04_01_09 (active)initialinitial.baktest-vos (config) #

6. Merge the common settings from a given configuration file to the active configuration

file.

configurationmerge file_name

7. Revert the active configuration to either the factory defaults or the last saved

configuration. Use keep-basic to preserve licenses and SSH host keys, use

keep-connect to preserve anything necessary to maintain network connectivity to

the system: interfaces, routes, and ARP; either or both may be used.

configuration revert {factory | saved} [keep-basic] [keep-connect]

You can use the Web interface, also referred to as the Management Console, System

Config > Config Mgmt page to save a current configuration to a binary file and download

it to another system. Later you can use the same page to upload the file and make it

active.


Upgrading (Web Interface) on page 4•






Known Installation Issues

Installation on the VXA2000

While installing Media Flow Controller software on the VXA2000 Series Media Flow

Engine using a CD-ROM or USB, sometimes the CD-ROM and USB might get bypassed

and the system might fall back to the existing image in the system. Rebooting the system

helps to restore the correct boot sequence. However, this action might not be an issue

in normal deployment scenarios as the system is installed with an image when the

hardware is shipped initially and you might need to upgrade the image thereafter. Reboot

the system to restore it.


Media Flow Controller Minimum System Requirements on page 12•

• Known Upgrade Issues on page 19

KnownUpgrade Issues

The following sections describe the known issues when upgrading the Media Flow

Controller software.

• Using the DMI Service on page 19

• Unable to Fall Back from Media Flow Controller 12.3 to Release 11.B.3 on page 19

• Other Upgrade Issues on page 20

Using the DMI Service

This issue is applicable only for users who are managing Media Flow Controller with Junos

Space Content Director (formerly Media Flow Activate).

For Media Flow Controller images 12.2.x, 12.3.x and later, the service start mod-dmi CLI

command starts all dependent processes. If you issue the service start mod-dmi CLI

command in Media Flow Controller running a 12.1.0 image before upgrading to a recent

12.2.x, 12.3.x, or later image, you must ensure to issue the service stopmod-dmi CLI

command to avoid upgrade failures. After upgrading Media Flow Controller, enable DMI

services using the service start mod-dmi.

Unable to Fall Back fromMedia Flow Controller 12.3 to Release 11.B.3

You might be unable to reload or revert the Media Flow Controller 12.3 software to Release

11.B.3 when you do the following:

1. In Media Flow Controller Release 11.B.3, create an R-proxy namespace and a resource

pool.

2. Bind the resource pool to that namespace.



3. Perform a config write command to file1.

4. Upgrade Media Flow Controller Release 11.B.3 to Release 12.3.

5. In Media Flow Controller Release 12.3, create an R-proxy namespace and a resource

pool.

6. Bind the resource pool to that namespace.

7. Perform a config write command to file2.

8. Perform an image boot next command.

9. Perform a reload command to revert from Media Flow Controller Release 12.3 to

Release 11.B.3.

Other Upgrade Issues

• In release 12.3.2 and later, the default value for “network connection concurrent session”

CLI has been changed to 128000. For this reason, if you upgrade from a pre-12.3.2

release to 12.3.2 or later, then you need to issue the network connection concurrentsession 128000 command to take advantage of the increased connection limits.

• The default value for the watch-dog grace-period CLI command has been changed to

120. As a result, if you upgrade from a pre-12.3.2 release to 12.3.2 or later, then you need

to configure the watch-dog grace-period 120 command explicitly.

• After upgrading from Media Flow Controller 2.0.x releases to the 11.A.1 or later release,

external disk eviction takes priority over internal disk eviction. In the Media Flow

Controller release 2.0.x, the eviction watermarks are configured by default so that

external eviction takes priority and evicts objects from disks before internal eviction.

Internal eviction is configured to evict objects only if external eviction is not able to free

sufficient space before disk usage grows to the internal eviction HWM. Media Flow

Controller 11.A.1 or later release has a more optimized and accurate internal eviction

scheme, and by default, it is recommended to prioritize internal eviction over external

eviction. In systems manufactured with Media Flow Controller 11.A.1 or later release,

prioritized internal eviction over external eviction occurs automatically. In systems

upgraded from Media Flow Controller release 2.0.x to 11.A.1 or later release, the

administrator should enter the following commands:

media-cache internal-eviction sata watermark 95 90media-cache internal-eviction sata watermark 90 85media-cache internal-eviction sata watermark 90 85media-cache external-eviction sata watermark 99 90media-cache external-eviction sata watermark 99 90media-cache external-eviction sata watermark 99 90

• When you upgrade from Media Flow Controller release 2.0.x to 11.A.1 or later release

directly or indirectly through other releases, throughput drop is observed when fetches

are performed from disk cache.

This problem is noticed only during the upgrade. To avoid this problem after a software

upgrade, configure no scheduler threads deadline to allow automatic scaling of Media

Flow Controller's core engine across available CPUs. Then, perform a mod_delivery

service restart.



• If a command-line interface (CLI) command has the default value X in one release

and has been changed to Y in a later release, you must explicitly change the value of

the CLI to the new value after upgrading to the later release.

The following are examples of default values to be aware of when upgrading from one

release to a later release:

Prior to Release 2.0.4, the default value for the delivery protocol http conn-pool origin

timeout command is 300 seconds. In Release 2.0.6, the default value is changed to

90 seconds. If you upgrade the Media Flow Controller from Release 2.0.4 or 2.0.5 to

Release 2.0.6 or 2.1.0 and then upgrade to Release 11.A.1 or 11.B.3 or a later release, the

default value remains set to 300 seconds. You must explicitly change the default value

to 90. Prior to Release 2.0.4, asynchronous DNS was disabled by default. In Release

2.0.6 and later releases, the asynchronous DNS was enabled by default. If you upgrade

the Media Flow Controller from Release 2.0.4 or 2.0.5 to Release 2.0.6 or later releases,

then asynchronous DNS remains disabled. You must explicitly enable asynchronous

DNS.

• The acceptable minimum and maximum threshold values for the namespace name

delivery protocol http origin-fetch cache-ingest hotness-threshold command have

changed. The values have changed from a minimum value of 0 and maximum value

of 100,000 in Release 11.A.1 to a minimum value of 3 and a maximum value of 65,536

in Release 11.B.3.

If you already have threshold values configured in the range of 0 or 2 to 65,536 for this

command in Release 11.A.1, the range must be changed to 3 to 65,536 before upgrading

to Release 11.B.3 or later release to avoid upgrade failures.

• When performing a downgrade from Release 12.1.0 or later to Release 11.B.x or earlier,

Media Flow Controller reboots three times. This is because Media Flow Controller needs

to change its internal configuration database to support the downgrade.


Known Installation Issues on page 19•

Media Flow Controller Software Fallback Overview

This topic discusses the system behavior when the software falls back from a higher

version to a lower version.

You might find this useful if you find issues with the higher version of the software and

want to return to a previously known good configuration.

When you upgrade the Media Flow Controller from a lower version of the software (Version

A) to the higher version (Version B), the system builds the higher version’s configuration

(Config B) derived from the lower version’s configuration (Config A). In case the system

must fall back to the lower version (Version A) after the upgrade, the Media Flow

Controller loads the lower version of the configuration (Config A).

When you switch again to the higher version of the software (Version B), the system

builds the higher version’s configuration (Config B_new) once again, from the lower

version’s configuration (Config A). It is designed this way because the lower version’s



configuration (Config A) is known to be working well, so that configuration is safe to use

as the initial running configuration, whenever you are switching or upgrading from a lower

version to a higher version. Also, if you have added or modified anything from the previously

well-known configuration (Config A), the system preserves those modifications in the

higher version.

Before falling back to an earlier version of the software, the system preserves a snapshot

of the current higher version’s configuration (Config B). After you return to the higher

version (Version B), you can use either the newly built configuration (Config B_new) or

your previously known higher version configuration (Config B). To use the previously

known higher version, enter the configuration switch-to Config B snapshot filename

command.


Upgrading (Web Interface) on page 4•



Boot Disk Mirroring

• Boot Disk Mirroring Overview on page 22

• Configuring the VXA2000 Series Content Engine BIOS for Boot Disk Mirroring on page 24

• Installing Media Flow Controller Software on a VXA2000 Series Content Engine for

Boot Disk Mirroring on page 31

• Resilvering a Failed Mirrored Boot Device on page 32

• Monitoring Boot Disk Mirroring Operation on page 34

• Rebooting Media Flow Controller (CLI) on page 35

Boot Disk Mirroring Overview

RAID1 boot disk mirroring, supported only on VXA2000 Series Content Engines, creates

an exact copy (or mirror) of a set of data from the writable system drive and the eUSB,

thus creating a boot storage device. The boot storage device includes data, such as

special add-on application packages, core files, logs, and writable private directories on

a mirrored disk pair over a single disk, increasing the availability of that data. The boot

storage device continues to operate when one disk fails in the same mirrored set, however

if both drives fail on both sides of the mirror, the data on the RAID is lost.

The VXA Series Content Engines have three types of storage drives for Media Flow

Controller data. The boot storage device includes the boot drive and the writeable system

drive.

• Cache drives—Are redundant at the application level. The data stored on cache drives

is also available on an origin server, so storing content in a cache drive is an optimization.

In addition, Media Flow Controller cache drives operate independently, which means

that the failure of any cache drive cannot bring down the system.

• Boot drive—VXA Series Content Engines have an eUSB device with high mean time

between failure (MTBF). This device contains the entire operating system (including



command binaries, libraries, kernel, and so on) and everything required to boot the

Media Flow Controller. When the VXA Series Content Engine supports boot disk

mirroring, the eUSB is no longer supported.

• Writable system drive—Stores the last piece of Media Flow Controller data, such as

special add-on application packages, core files, logs, and writable private directories.

The data on this drive is not highly available.

Only the first and second disk drives in the VXA2000 Series Content Engines are

considered for boot device mirroring. You must create the mirror with drives in the first

two slots. It is recommended that the two drives be of the same size and have the same

RPM.

After partial boot device failure:

• There should be no interruption of media delivery.

• Access log generation should not be affected.

• Any critical data such as configuration files, Policy Engine scripts, and SSL certificates

stored in the boot device partition should be available.

• The system notifies the administrator by generating a log message in the system log

and by generating a SNMP trap in the following conditions:

• Drive failure (when either drive in mirror fails.

• Breakage of a mirror, such as when there is a failure of mirroring activity across the

disks.

With boot disk mirroring the following performance might occur:

• Peak transactions per second (TPS) might drop by 3 to 5 percent.

• Peak bandwidth (for large objects and chunked video) will not be affected.

• Total CPU usage might increase by 5 to 10 percent.

• Applications using the mirrored drive might see a reduction of write performance by

up to 5 percent.

To set up, configure, and monitor boot disk mirroring, perform the following tasks:

1. Configure the VXA2000 Series Content Engine BIOS for RAID1. See “Configuring the

VXA2000 Series Content Engine BIOS for Boot Disk Mirroring” on page 24.

2. Install Media Flow Controller Release 12.3 software. See “Installing Media Flow

Controller Software on a VXA2000 Series Content Engine for Boot Disk Mirroring” on

page 31.

3. Resynchronize when a mirror breaks or a disk fails. See “Resilvering a Failed Mirrored

Boot Device” on page 32



4. Monitor the boot disk mirroring events. See “Monitoring Boot Disk Mirroring Operation”

on page 34

5. If necessary, perform system recovery. See “Rebooting Media Flow Controller (CLI)”

on page 35


Configuring the VXA2000 Series Content Engine BIOS for Boot Disk Mirroring on page 24•






Configuring the VXA2000 Series Content Engine BIOS for Boot Disk Mirroring

For boot disk mirroring, you must modify BIOS settings during the VXA2000 Series Content

Engine hardware setup. Boot disk mirroring creates an exact copy (or mirror) of data,

such as the Media Flow Controller special add-on application packages, core files, logs,

and writable private directories, plus the contents of the root device on two disks, thereby

increasing the availability of that data.

Configuring the VXA2000 Series Content Engine BIOS enables the following:

• Booting from the hard disk drive.

• Selecting the boot disk from slot 0 or 1.

Before you begin:

• Place disk drives of the same size and RPM in slot 0 and slot1 of the VXA2000 Series

Content Engine.

To enter and configure the VXA2000 Series Content Engine BIOS:

1. Boot the VXA2000 Series Content Engine.

When the system is booting, you see:

AMIBIOS(C)2008 American Megatrends, Inc. BIOS Date: 07/29/10 20:42:22 Ver: 08.00.16 Juniper Networks HE2 Production BIOS V1.00 CPU : Intel(R) Xeon(R) CPU L5518 @ 2.13GHz Speed : 2.13 GHz ,Dram Clocking = 800MHz Count : 2 Press DEL to run Setup (F4 on Remote Keyboard) Press F12 if you want to boot from the network Press F11 for BBS POPUP (F3 on Remote Keyboard)

2. When you see the following, press Ctrl+C to enter the LSI BIOS Configuration Utility

and configure BIOS settings.

LSI Corporation MPT SAS2 BIOS MPT2BIOS-7.23.01.00 (2011.11.17)



Copyright 2000-2011 LSI Corporation. Press Ctrl-C to start LSI Corp Configuration Utility...

The Adapter Global Properties screen appears.

3. Select SAS9201-16i and change Boot support to Enabled BIOS&OS.

4. Save the changes and reboot.



You can save the current changes and go back to original menu.

The boot support in now enabled for the controller under the Status column.



5. Exit the LSI BIOS Configuration Utility and reboot.

The system reboots.

6. When you see the following, press Delete, F4, or Ctrl+Backspace to enter VXA BIOS

settings:

AMIBIOS(C)2008 American Megatrends, Inc. BIOS Date: 07/29/10 20:42:22 Ver: 08.00.16 Juniper Networks HE2 Production BIOS V1.00 CPU : Intel(R) Xeon(R) CPU L5518 @ 2.13GHz Speed : 2.13 GHz ,Dram Clocking = 800MHz Count : 2 Press DEL to run Setup (F4 on Remote Keyboard) Press F12 if you want to boot from the network Press F11 for BBS POPUP (F3 on Remote Keyboard)

7. In the Boot tab, select Hard Disk Drives.

8. For the 1st Drive choose the drive in slot 0.



The drives in slot 0 and 1 are the drives with lowest ID numbers.

For the 2nd Drive, choose the drive in slot 2.

After setting 2nd drive as the drive in slot 1, the following screen appears.

9. From the Boot tab, select Boot Device Priority.



If you want to install Media Flow Controller using a CD-ROM or network, set that with

the higher priority.

Here, the first device is the USB CD-ROM (if you want to install using the USB

connection), the second device is Network (to install using PXE), and the third device

is the drives enabled for boot disk mirroring.

The boot order depends on the medium used to install Media Flow Controller. If you

are installing using USB CD-ROM, you can set the first boot device as USB CD-ROM

and second device as the boot disk mirror drive.

10. For the 1st Boot device, select the drive you selected in the Hard Disk Drives screen.

The hard disk drives are shown.



The boot device priority is shown.

11. Save the settings and exit.


Boot Disk Mirroring Overview on page 22•






Installing Media Flow Controller Software on a VXA2000 Series Content Engine for Boot DiskMirroring

When installing or upgrading the Media Flow Controller Release 12.3 software on a

VXA2000 Series Content Engine, the installation program prompts you to create a

mirrored disk pair over a single boot storage device to increase the availability of data,

such as special add-on application packages, core files, logs, and writable private

directories.

To install the Media Flow Controller software:

1. Boot the install media (the USB stick or CD-ROM).

The default Media Flow Controller installation menu appears:

Enter 1 to Install Media Flow Controller.Enter 2 to Restore Media Flow Controller.Enter 3 to Reboot without installing or restoring.Enter 4 to Halt without installing or restoring.Enter 5 to Change the first drive cache choice. (currently with no cache)Enter 6 to Change the boot drive choice. (currently: Internal Flash)Enter 0 to Exit without installing or restoring.Or enter special options as instructed by support personnel.Current special options:

Note:Install will delete all cached data.Restore attempts to keep cached data.

2. Enter 6 to change the boot device config.

Enter 0, 1, 2, 3, 4, 5, 6 : 6

The following menu appears:

Enter 1 to use the first two HDDs for Mirror Boot drive.Enter 3 to use the internal Flash drive for boot drive.Enter 0 to Exit without installing or restoring.

3. Enter 1 to choose the first two hard disks (HDDs) for the mirror boot drive.

Enter 0, 1, 3 : 1

The original menu reappears with the updated option 6 showing as the HDD mirror.

Install on disk sdd

Enter 1 to Install Media Flow Controller.Enter 2 to Restore Media Flow Controller.Enter 3 to Reboot without installing or restoring.Enter 4 to Halt without installing or restoring.Enter 6 to Change the boot drive choice. (currently: HDDMirror)Enter 0 to Exit without installing or restoring.Or enter special options as instructed by support personnel.Current special options:



Note:Install will delete all cached data.Restore attempts to keep cached data

4. Install the Media Flow Controller software by selecting option 1.

Enter 0, 1, 2, 3, 4, 6 : 1

You see the following:

Starting the install/restore process >>>

Warning : Installation process could take anywhere from 10minutes toevenmore than an hour depending on the number and size of the disks.In between youmight not see anymessages being printed and that is normal.Please expect long pauses and be patient.

Thanks for installing Media Flow ControllerUsing /dev/sdd + /dev/sdc for Mirror Boot+Data drive




Resilvering a FailedMirrored Boot Device

When a VXA2000 Series Content Engine boot disk mirror breaks (or a disk fails), you can

resilver or resynchronize that drive. Resilvering is the process of copying data from one

disk pair of a mirror (or boot device) to another. The boot device continues to operate

when one or more drives fail in the mirrored set, however if both disks fail on both sides

of the mirror, the data on the boot device is lost.

The boot storage device includes data, such as special add-on application packages,

core files, logs, and writable private directories, on a mirrored disk pair over a single disk,

thereby increasing the availability of that data.

• The system notifies the administrator by generating a log message in the system log

and by generating a SNMP trap under the following conditions:

• Drive failure (either drive in the mirror fails)


disks

To resilver a broken boot disk mirror:

1. Check the status of the boot disk mirror.

In Config CLI mode, use the (config) # show systemmirror boot-device status CLI

command.

Boot drivemirror is in degraded state.Disk in slot 1 is bad and needs replacement.Administrative action: Replace bad drive in slot 1 and start resync by issuing 'systemmirror boot-device resync'



2. Pull the bad VXA2000 Series Content Engine boot storage drive.

See Replacing Bad Disks or “Replacing a Storage Drive on VXA2U Series Media Flow

Engines” in the VXA2U Series Media Flow Engine Installation Guide.

3. Replace the bad boot storage drive with an identical size and type of storage drive.

See Inserting New Disks into a VXA Series Media Flow Engine or “Replacing a Storage

Drive on VXA2U Series Media Flow Engines” in the VXA2U Series Media Flow Engine

Installation Guide.

4. Resilver (or resynchronize) the replaced boot storage drive.

In the CLI Configure mode, use the systemmirror boot-device resync CLI command.

For example:

enableconfigure terminal(config) # systemmirror boot-device resync

Mirror resync started

When the resynchronization is in progress use the following CLI command: Resync is

in progress for boot drive mirror. No administrative action required at this point of time.

(config) # show systemmirror boot-device status

Resync is in progress for boot drivemirror.No administrative actionrequired at this point of time.

5. View the resilvering status.

(config) # show systemmirror boot-device status

This command displays whether the mirror is good, whether resilvering is in process,

and the resilvering process percentage of completion. For example:

• When the mirror is good:


• When resynchronization is in progress:


• When the mirror is broken:

The slot number can be 0 or 1, depending on which disk failed

Boot drivemirror is in degraded state. Disk in slot 0 is badand needs replacement.Administrative action: Replace bad drive in slot 0 and startresync by issuing 'systemmirror boot-device resync'








Monitoring Boot Disk Mirroring Operation

The system notifies the administrator by generating a log message in the system log and

by generating a SNMP trap under the following conditions:

• Drive failure when either drive in a mirror fails.


disks.

• Viewing Boot Disk Mirroring Events in the System Log on page 34

• Viewing Boot Disk Mirroring Traps on page 34

Viewing Boot Disk Mirroring Events in the System Log

The system log displays the following information when a boot disk fails or mirror breaks:

Mirrorbroken event is detected on device /dev/md6

Viewing Boot Disk Mirroring Traps

The following SNMP traps are generated when a boot disk fails or a mirror breaks.

DescriptionSNMP Trap

Notification sent when the root disk re-mirroring is complete.jmfcRootDiskMirrorComplete

Variable that says which root disk was re-mirrored.jmfcRootDiskMirrorComplete.jmfcMirrorCompletionDescr

Notification sent when the root disk mirror is broken.jmfcRootDiskMirrorBroken

Variable that says what caused the root disk mirror to break.jmfcRootDiskMirrorBroken.jmfcErrorDescr


Boot Disk Mirroring Overview on page 22•

• Configuring the VXA2000 Series Content Engine BIOS for Boot Disk Mirroring on page 24







RebootingMedia Flow Controller (CLI)

You can either reboot or shut down the Media Flow Controller. If you use the shutdown

command, the system does not reboot until it is power cycled.

To reboot Media Flow Controller using the CLI:

1. Reboot or shut down the system.

reload

2. Set boot parameters. Optionally specify a default location from which the image

boots; since there are only two locations to choose from, the options are 1 and 2 for

location ID. If you use the next option, set the boot location to be the next one after

the one currently booted from.

boot (location location_ID | next)

3. View boot parameters.

boot ?


show boot






CHAPTER 2

InstallingMedia FlowControllerwith aCDor USB

This chapter describes installing Media Flow Controller.

• Before Installing Media Flow Controller with a CD or USB on page 37

• Creating CDs on page 38

• Ethernet Naming Options on page 38

• Choosing to Cache on the First Drive on page 44

• Installing Media Flow Controller Software—CD or USB on page 44

• Setting Up Basic System Connectivity on page 46

Before Installing Media Flow Controller with a CD or USB

You can request a CD or a USB drive with the software, or download an ISO image and

burn your own CD, and use it to install. You cannot create your own USB drive.

Before you install Media Flow Controller with a CD or USB drive:

• Obtain the Media Flow Controller installation image from Juniper Networks Support.

See “Requesting Technical Support” on page viii.

• Review “Pre-installation Planning” on page 9 for important information.

TIP: If you received aMedia FlowController installationCDorUSBdrive, skipthe next section and go directly to “Installing Media Flow ControllerSoftware—CD or USB” on page 44.


Media Flow Controller Minimum System Requirements on page 12•



Creating CDs

There are many applications for creating CDs. For example, to burn the ISO image onto

a CD, in Linux, you can use a command like this;

sudo cdrecord -v -tao dev=/dev/cdrom filename


Before Installing Media Flow Controller with a CD or USB on page 37•

Ethernet Naming Options

You need to know what naming you want for all the ports before beginning installation

because most installations require manual naming of the Ethernet ports (also known as

interfaces or devices). This is because the default naming order is often confusing or not

completely useful, based on the internal PCI hardware address that each device uses.

The most important port to name is eth0, because that port name must be used to access

the Web-based Management Console, and for SSH to get to the command-line interface

(CLI). Juniper Networks suggests that the built-in ports use single digits, and for each

add-in card, use numbers that start with multiples of ten. For example, if the first add-in

card is a 4-port card, then use 10, 11, 12, and 13, and if the second add-in card is a 2-port

card, then use 20 and 21.

After the first phase of the installation is done, the installation procedure offers four

options to help you correctly identify and name your Ethernet interfaces:

NOTE: Media Flow Controller licenses are tied to either the Host ID of thesystemor theMACaddressof the eth0 interface. If youalreadyhavea license

that is tied to aMACaddress, ensure that the correct interface is eth0, or your

license will not work.

• Flash Ethernet Port LEDs, Ethernet Naming Option 3 on page 38

• Configure Ethernet Names Interactively, Ethernet Naming Option 4 on page 39

• Specify Devices to Use For eth0 and eth1, Ethernet Naming Option 5 on page 41

• Reset Ethernet Device Naming Back to Default, Ethernet Naming Option 6 on page 43

Flash Ethernet Port LEDs, Ethernet Naming Option 3

If you are at the machine console, press 3 (Flash Ethernet Port LEDs) during installation

to see which ports have been assigned what.

To make the assignments, use option 4 or option 5.

NOTE: The flashingof theport LEDsworksonmostEthernet devices; if thereis a problem, a warning is displayed.



Example:

1. Enter 3

Enter 1, 2, 3, 4, 5 or 6 : 3Flashing eth leds in this order:0000:01:00.0,00:15:17:8A:49:90,eth00000:01:00.1,00:15:17:8A:49:91,eth10000:04:00.0,00:13:72:3C:33:56,eth100000:05:00.0,00:13:72:3C:33:57,eth11Flashing each for 3 seconds, then a 6 second pause, for 3 timesLoop 1Flashing eth0Flashing eth1Flashing eth10Flashing eth11PauseLoop 2Flashing eth0Flashing eth1Flashing eth10Flashing eth11PauseEnter 1 to Reboot to complete the installation.Enter 2 to Halt. Installation will continue when rebooted.Enter 3 to Flash ethernet port LEDs.Enter 4 to Configure ethernet device names interactively.Enter 5 to Specify devices to use for eth0 and eth1.Enter 6 to Reset ethernet device naming back to default.Enter 1, 2, 3, 4, 5 or 6 :

Configure Ethernet Names Interactively, Ethernet Naming Option 4

To see which ports have been assigned what and make custom assignments, press 4

(Configure Ethernet Names Interactively) during the installation.

This example shows a machine with a 2-port add-in card that has lower PCI addresses,

assigned by default, than the built-in ports. The default assignments use the add-in card

but the desired assignments are the built-in ports: the third default (eth10) device for

eth0, and the fourth default (eth11) device for eth1. This example shows assigning the

interfaces.

Example:

1. Enter 4.

Enter 1, 2, 3, 4, 5 or 6 : 4==============================================================Current ethernet device naming:eth0PCI address: 0000:01:00.0 HW address: 00:15:17:8A:49:90Intel Corporation 82571EB Gigabit Ethernet Controller (rev 06)eth1PCI address: 0000:01:00.1 HW address: 00:15:17:8A:49:91Intel Corporation 82571EB Gigabit Ethernet Controller (rev 06)eth10PCI address: 0000:04:00.0 HW address: 00:13:72:3C:33:56inet addr: 172.12.172.238Broadcom Corporation NetXtreme BCM5721 Gigabit Ethernet PCI Express (rev 11)


Chapter 2: Installing Media Flow Controller with a CD or USB

eth11PCI address: 0000:05:00.0 HW address: 00:13:72:3C:33:57Broadcom Corporation NetXtreme BCM5721 Gigabit Ethernet PCI Express (rev 11)==============================================================BEGIN update namingPCI address: 0000:01:00.0 HW addr: 00:15:17:8A:49:90Intel Corporation 82571EB Gigabit Ethernet Controller (rev 06)Currently assigned name: eth0Enter one of the following:a: Keep the current name (eth0)b: Flash the LED for 4 secondsc: Flash the LED for 16 secondsd: Flash the LED for 64 secondse: Flash the LED for 128 secondsThe eth number you want for the name of this device.>

2. Enter 10.

PCI address: 0000:01:00.1 HW addr: 00:15:17:8A:49:91Intel Corporation 82571EB Gigabit Ethernet Controller (rev 06)Currently assigned name: eth1Enter one of the following:a: Keep the current name (eth1)b: Flash the LED for 4 secondsc: Flash the LED for 16 secondsd: Flash the LED for 64 secondse: Flash the LED for 128 secondsThe eth number you want for the name of this device.>

3. Enter 11.

PCI address: 0000:04:00.0 HW addr: 00:13:72:3C:33:56inet addr: 172.12.172.238Broadcom Corporation NetXtreme BCM5721 Gigabit Ethernet PCI Express (rev 11)Currently assigned name: eth10Enter one of the following:a: Keep the current name (eth10)b: Flash the LED for 4 secondsc: Flash the LED for 16 secondsd: Flash the LED for 64 secondse: Flash the LED for 128 secondsThe eth number you want for the name of this device.>

4. Enter 0.

PCI address: 0000:05:00.0 HW addr: 00:13:72:3C:33:57Broadcom Corporation NetXtreme BCM5721 Gigabit Ethernet PCI Express (rev 11)Currently assigned name: eth11Enter one of the following:a: Keep the current name (eth11)b: Flash the LED for 4 secondsc: Flash the LED for 16 secondsd: Flash the LED for 64 secondse: Flash the LED for 128 secondsThe eth number you want for the name of this device.>

5. Enter 1.



Done specifying the device to eth number mapping.The new mapping is:0000:04:00.0,00:13:72:3C:33:56 eth00000:05:00.0,00:13:72:3C:33:57 eth10000:01:00.0,00:15:17:8A:49:90 eth100000:01:00.1,00:15:17:8A:49:91 eth11Use this mapping? (y/n)

6. Enter y.

Saving...Enter 1 to Reboot to complete the installation.Enter 2 to Halt. Installation will continue when rebooted.Enter 3 to Flash ethernet port LEDs.Enter 4 to Configure ethernet device names interactively.Enter 5 to Specify devices to use for eth0 and eth1.Enter 6 to Reset ethernet device naming back to default.Enter 1, 2, 3, 4, 5 or 6 :

Specify Devices to Use For eth0 and eth1, Ethernet Naming Option 5

If you are satisfied with the interfaces being automatically assigned and only need to set

up eth0 and perhaps eth1, and do not want to use the interactive method (option 4), you

can use option 5. Option 5 lets you specify which devices to use for eth0 and optionally

eth1. This example shows the assigning of the interfaces.

NOTE: Theeth-setupoptions, or “forms”:default, least-ports,most-ports,pxe,

URL, url, and HWaddress are described in this section.

Example:

1. Enter 5.

Enter 1, 2, 3, 4, 5 or 6 : 5==============================================================Current ethernet device naming:eth0 PCI address: 0000:01:00.0 HW address: 00:15:17:8A:49:90 Intel Corporation 82571EB Gigabit Ethernet Controller (rev 06)eth1 PCI address: 0000:01:00.1 HW address: 00:15:17:8A:49:91 Intel Corporation 82571EB Gigabit Ethernet Controller (rev 06)eth10 PCI address: 0000:04:00.0 HW address: 00:13:72:3C:33:56 inet addr: 172.12.172.238 Broadcom Corporation NetXtreme BCM5721 Gigabit Ethernet PCI Express (rev 11)eth11 PCI address: 0000:05:00.0 HW address: 00:13:72:3C:33:57 Broadcom Corporation NetXtreme BCM5721 Gigabit Ethernet PCI Express (rev 11)==============================================================Enter 0 to not make any ethernet device naming changes. Otherwise enter thespecification for eth0, and optionally eth1, and then press return togenerate the new port to name mapping. For an explanation of thespecifications that can be used enter 'help'.Enter 0, help or the spec >



2. Enter help.

Enter 0, help or the spec > helpSyntax forms: default|least-ports|most-ports|pxe|URL|url

HWaddr [HWaddr]Examples of all the forms: default least-ports most-ports pxe http://66.224.165.46/mfd-images/1.0.0-45.img url 00:30:48:B8:F8:22 F8:22 f8:23-ca:A8When "default" is specified, eth0 and eth1 are assigned in the order that thedevices are on the PCI bus. eth0 might not be assigned to the port that youwant it to be. The other options allow you to specify which port to use aseth0 (and eth1).When "least-ports" is specified, the first NIC card with the least number ofports is used for eth0 (and eth1 if there are two or more ports on that NIC).When "most-ports" is specified, the first NIC card with the most number ofports is used for eth0 and eth1.When "pxe" is specified, the interface used to PXE boot from is used for eth0.You may specify an http or https URL, and the ethernet device that providesaccess to that URL will be used for eth0.In the situation where you installed from a URL, you can specify the word"url", and it will use that URL to select eth0 as described above.You may specify a HWaddr to force eth0 to use that device. You can specify asecond HWaddr to be used for eth1. For the HWaddr, aka MAC addr, you do nothave to specify all the octets, you may specify as little as two of the rightmost octets as long as that is unique across all the installed ethernetdevices.Enter 0 to not make any ethernet device naming changes. Otherwise enter thespecification for eth0, and optionally eth1, and then press return togenerate the new port to name mapping. For an explanation of thespecifications that can be used enter 'help'.Enter 0, help or the spec >

3. Enter 33:56-33:57.

= Assigning interface names-- MAC: 00:13:72:3C:33:56 Mapping from: eth2 to: eth0-- MAC: 00:13:72:3C:33:57 Mapping from: eth3 to: eth1-- MAC: 00:15:17:8A:49:90 Mapping from: eth0 to: eth10-- MAC: 00:15:17:8A:49:91 Mapping from: eth1 to: eth11The new mapping is:eth10 PCI address: 0000:01:00.0 HW address: 00:15:17:8A:49:90 Intel Corporation 82571EB Gigabit Ethernet Controller (rev 06)eth11 PCI address: 0000:01:00.1 HW address: 00:15:17:8A:49:91 Intel Corporation 82571EB Gigabit Ethernet Controller (rev 06)eth0 PCI address: 0000:04:00.0 HW address: 00:13:72:3C:33:56 inet addr: 172.12.172.238 Broadcom Corporation NetXtreme BCM5721 Gigabit Ethernet PCI Express (rev 11)eth1 PCI address: 0000:05:00.0 HW address: 00:13:72:3C:33:57



Broadcom Corporation NetXtreme BCM5721 Gigabit Ethernet PCI Express (rev 11)Enter 0 to NOT USE this new ethernet port naming.Enter 1 to USE this new ethernet port naming.Otherwise enter the specification for eth0, and optionally eth1,and then press return to generate the new port to name mapping.For an explanation of the specifications that can be used enter 'help'.Enter 0, 1, help or the spec >

4. Enter 1.


Reset Ethernet Device Naming Back to Default, Ethernet Naming Option 6

If at any time in the Ethernet naming process you want to revert to the default names

assigned by the system, you can use option 6.

Example after assigning interfaces names using option 4 or 5:

Done specifying the device to eth number mapping.The new mapping is:0000:04:00.0,00:13:72:3C:33:56 eth00000:05:00.0,00:13:72:3C:33:57 eth10000:01:00.0,00:15:17:8A:49:90 eth100000:01:00.1,00:15:17:8A:49:91 eth11Use this mapping? (y/n)

1. Enter y.


2. Enter 6.

DoneEnter 1 to Reboot to complete the installation.Enter 2 to Halt. Installation will continue when rebooted.Enter 3 to Flash ethernet port LEDs.Enter 4 to Configure ethernet device names interactively.Enter 5 to Specify devices to use for eth0 and eth1.Enter 6 to Reset ethernet device naming back to default.Enter 1, 2, 3, 4, 5 or 6 :



Choosing to Cache on the First Drive

Step 4 in “Installing Media Flow Controller Software—CD or USB” on page 44 and Step

6 in “Installing Media Flow Controller Software from the Network—PXE” on page 52

prompt you to decide whether you want to cache on the first drive; use option 3 to view

these explanations:

• If you choose not to cache on the first drive:

• For drives up to 244 GB:

• Between 30 and 40 percent of the drive will be used for the log partition.

• Precisely: (drive size - 38 GB)/2.

• For drives larger than 244 GB:

• The log partition will be about 103 GB + the size of the drive over 244 GB.

• If you choose to cache on the first drive:

• For drives up to 347 GB:

• Between 20 and 30 percent of the drive will be used for the log partition.

Between 20 and 30 percent the drive will be used for cache.

Precisely: (drive size - 38 GB)/3

• For drives larger than 347 GB:

• The log partition will be about 103 GB.

The cache will use about 103 GB + the size of the drive over 347 GB.


Installing Media Flow Controller Software—CD or USB on page 44•

• Installing Media Flow Controller Software from the Network—PXE on page 52

Installing Media Flow Controller Software—CD or USB

When the Media Flow Controller software is installed on a machine that does not currently

have Media Flow Controller installed, it completely formats all disks in the system. While

the software is installing, no progress indicator is given while formatting the drives. Please

be patient. When installing on a machine that has Media Flow Controller currently

installed, you can choose to retain the data in the caches.



To install Media Flow Controller with a CD or USB:

1. Insert the CD, or plug in the USB drive, and reboot the machine from the installation

media. After it finishes booting, a welcome message is displayed. If you see a login

prompt, enter root. You typically see the first installation prompt about the end-user

license agreement (EULA).

If your computer shares the CD boot drive or USB boot port with other computers,

then the CD or USB drive might not be immediately available. If this happens, the

following installation menu is displayed first, before the EULA agreement prompt:

Enter 1 to Reboot without installing or restoringEnter 2 to Halt without installing or restoringEnter 3 to Attempt to install from Installation Media

2. Enter 3. A prompt for the EULA is displayed:

Enter 1 to Read the EULA agreement and continue with installation.Enter 2 to Reboot without installing or restoring.Enter 3 to Halt without installing or restoring.Enter 1, 2, or 3 :

3. Enter 1. The EULA is displayed; press the Space bar to page through it. You can enter

q to skip to the end of the EULA.

Enter 1 to Read the EULA agreement again.Enter 'accept' to accept the EULA agreement and continue withinstallation.Enter 2 to Reboot without installing or restoring.Enter 3 to Halt without installing or restoring.Enter 1, 2, 3, or 'accept' :

4. Enter accept. The following menu is displayed:

Enter 1 to NOT use part of the first disk for cache.Enter 2 to use part of the first disk for cache.Enter 3 for an explanation of this choice.Enter 1, 2, or 3 :

5. Enter 1or2 (see “Choosing to Cache on the First Drive” on page 44 for the explanation).

The following menu is displayed:

Enter 1 to Install Media Flow Controller.Enter 2 to Restore Media Flow Controller.Enter 3 to Reboot without installing or restoring.Enter 4 to Halt without installing or restoring.Or enter special options as instructed by support personnel.Note:Install will delete all cached data.Restore attempts to keep cached data.Enter 1, 2, 3 or 4 :

6. If this is a first-time installation, enter 1.

If this is not a first-time installation, and you want to erase all the cached data, enter

1.

If this is not a first-time installation, and you want to preserve cached data, enter 2.

In some situations some or all of the cached data still might not be preserved.



If you think you need special partitioning for your root drive, call Customer Support to

access the special options. Typically, this is not needed.

The installation proceeds; it can take 10 minutes or longer depending on how many

disks Media Flow Controller needs to format. When completed, the following menu

is displayed:

Installation is done at number>>> Phase 1 Installation Done <<<Enter 1 to Reboot to complete the installation.Enter 2 to Halt. Installation will continue when rebooted.Enter 3 to Flash ethernet port LEDs.Enter 4 to Configure ethernet names interactively.Enter 5 to Specify device for eth0 and eth1.Enter 6 to Reset ethernet naming back to default.

Most systems need the interface names assigned manually; the Ethernet naming

default is based on the device’s PCI bus address order and often is not optimally

assigned. It is very important that eth0 be assigned to the proper port. Use options 4

or 5 to configure the interface naming. See “Ethernet Naming Options” on page 38 for

details.

7. After you have assigned the interface names, at the menu prompt, press 1 to reboot

and finish the installation. The installation completes and an “unconfigured” prompt

is displayed:

mfc-unconfigured-8a4990 login:

Continue to “Setting Up Basic System Connectivity” on page 46.


Before Installing Media Flow Controller with a CD or USB on page 37•


Setting Up Basic SystemConnectivity

After Media Flow Controller is installed, follow these steps to set basic network

connectivity. At a minimum, you must assign eth0 an IP address; then the appliance can

be remotely accessed and configured.

To set up basic system connectivity on Media Flow Controller:

1. Log in as admin.

There is no default password.

2. Enter configuration mode with these commands:

enableconfigure terminal

3. Set the IP address, hostname, gateway, DNS server, and a domain list (to resolve

unqualified hostnames). Install licenses, if you have the license keys. Save the settings

after you finish.

interface eth0 ip addressmanagement_port_IP_address netmaskhostname hostname_for_machine



ip default-gateway gateway_server_IP_addressip name-server DNS_server_IP_addressip domain-list domain_name_for_resolving_hostnames...ntp serverNTP_server_IP_addresslicense install license_keyconfiguration write

4. As you have just changed the network information for your system, you must

reassociate Media Flow Controller with the interfaces. Either reboot (reload command)

or enter this command:

service restart mod_delivery

5. Display the software version. If you have installed licenses, check those too.

show versionshow license

6. From another machine, attempt to ping each address and open an SSH session to

the server as Admin.

To complete connecting the machine to your network, plug in the traffic ports Eth2, 3, 4,

5, and configure with static IP addresses, or skip this step and hand off further

configurations to your system administrator. Table 3 on page 14 shows a typical Media

Flow Controller configuration.

You are now ready to begin configuring Juniper Networks Media Flow Controller. See the

Juniper Networks Media Flow Controller Administrator’s Guide and Media Flow Controller

CLI Command Reference.

NOTE: If an unexpected interface is assigned eth0, your installed licenseswill be invalid because they rely on theMACaddress of an assigned interfaceand that interface has changed. If that is the case, you need tomanuallyassign the interfaces; see “Changing Ethernet Name Assignments AfterInstallation” on page 15 for details.


• Changing Ethernet Name Assignments After Installation on page 15



CHAPTER 3

Installing Media Flow Controller with PXE

• PXE Overview on page 49

• Before Installing Media Flow Controller with PXE on page 49

• Setting Up PXE on page 50


PXEOverview

Preboot execution environment (PXE) allows a machine to boot from a server on the

network. PXE works using firmware on the NIC and makes a DHCP request for network

information, the IP address of a TFTP server, and the name of the OS boot image. It finds

an HTTP server containing the OS boot image, downloads the image from the server,

and then boots the machine from it.

PXE can be used to install Media Flow Controller without needing to physically load an

installation CD into the CD drive or physically plug in an installation USB flash drive.

Multiple machines can be installed at the same time as well.

Installing the Media Flow Controller using PXE requires a set of matched files. These files

are supplied in a single gzipped Tar file, which includes a set of files for booting an

installation program and the actual Media Flow Controller installation image file. The

installation program set consists of the boot kernel image, root file system image, and a

.tgz file with additional files needed to perform the installation. The Media Flow Controller

installation image file is also used for upgrading.


Before Installing Media Flow Controller with PXE on page 49•

• Setting Up PXE on page 50


Before Installing Media Flow Controller with PXE

Before you install Media Flow Controller with PXE:

• You must have a TFTP or PXE server.

• You must have a DHCP server.


• You must have an HTTP server to provide access to files on the TFTP or PXE server.

• Obtain the Media Flow Controller PXE installation package from Juniper Networks

Support. See “Requesting Technical Support” on page viii.

• Review “Pre-installation Planning” on page 9 for important information.

• Set up your PXE installation configuration file and install the image files appropriately.

See “Setting Up PXE” on page 50.


Installing Media Flow Controller Software from the Network—PXE on page 52•

Setting Up PXE

There are two parts to setting up PXE for installation in Media Flow Controller: configuring

the PXE configuration file and setting up the software images. When setting up your PXE

server, you have several installation options that you can build into the PXE installation

menu.

• PXE Configuration File Installation Options on page 50

• Setting Up Your PXE Server on page 51

PXE Configuration File Installation Options

Media Flow Controller installation options can be added on the append initrd line that

you add to the PXE configuration file.

Use the installopt=option setting to specify one or more installation options, separated

by commas without spaces. See Table 4 on page 50 for a description of the options.

For example, to specify certain ETH naming selections, use the following commands in

the PXE configuration file on the append initrd line:

installopt=ethsetup-pxe,auto-eth

Table 4: PXE Installation Options for the PXE Configuration File

DescriptionOption

Accept the EULA automatically. When this is used, the EULA is not displayed. Step 4 of the MediaFlow Controller installation procedure is skipped.

accept-eula

Do not show any selections to set up the eth device naming on the installation menu; instead,automatically use the interface you specified with the ethsetup option. Options 3, 4, 5, and 6 in Step9 of the Media Flow Controller installation procedure are omitted.

auto-eth

This option has an effect only ifauto-eth is also specified. When set, the machine automatically rebootsafter the Media Flow Controller installation procedure is finished.

auto-reboot

Add an additional option, Enter 8 to Use the PXE-boot specification for eth0, to the installation menu,to choose the setting you specified with ethsetup. The options default, leastports, most-ports, pxe,URL, url, andHWaddress are described in “Specify Devices to Use For eth0 and eth1, Ethernet NamingOption 5” on page 41.

ethsetup=option



Table 4: PXE Installation Options for the PXE Configuration File (continued)

DescriptionOption

Set init-cache or keep-cache to bypass options 1 and 2 of the Media Flow Controller installationprocedure. Set init-cache for a first-time installation or if you want to empty the cache. Set keep-cachefor a restoration installation of Media Flow Controller; in some situations some or all of the cacheddata still might not be preserved. When set, the options to Install or Restore the Media Flow Controllerinstallation are omitted.

init-cache

keep-cache

Setting Up Your PXE Server

To set up your PXE server for Media Flow Controller installation:

1. From the Juniper technical support website (see “Requesting Technical Support” on

page viii), download the Media Flow Controller PXE installation package:

pxe-mfc-version.tgz

The files in this .tgz are:

• vmlinuz-bootflop-mfc-version—PXE boot kernel image

• rootflop-mfc-version.img—PXE root filesystem image

• manufacture-mfc-version.tgz—Installation files

• image-mfc-version.img—Media Flow Controller image file

2. Extract all the files into a new directory in your PXE server directory tree.

For example, to keep things simple make the directory name using the MFC version

of the version string from the pxe-mfc-version.tgz file name (for example, mfc-11.B.3).

This directory is referred to as directory. This needs to be the directory path where the

PXE boot and root image files are accessed from the TFTP server. Additionally, you

must set up an HTTP server to provide access to the same directory so that the Media

Flow Controller installation and image files can be downloaded from HTTP.

3. Edit the PXE server configuration file on your system to make the installation package

files available from which to boot.

For example, on a Redhat Linux PXE server, edit pxelinux.cfg/default.

4. The minimal number of settings to add to the configuration file are a label line, a kernel

line, an append initrd line, and an ipappend line:

label directorykernel directory/vmlinuz-bootflop-mfc-versionappend initrd=directory/rootflop-mfc-version.imginstallfrom=http_URL_to_the_directoryipappend 3

If the HTTP server and TFTP server use the same IP address, then in the “installfrom=”

setting, the “http://IP_address/” portion of the http_URL_to_the_directory can be

omitted.

The following is a complete installation example:


Chapter 3: Installing Media Flow Controller with PXE

/tftpboot/pxelinux.cfg/default:DEFAULT menu.c32TIMEOUT 600ONTIMEOUT BootLocalPROMPT 0MENU INCLUDE pxelinux.cfg/pxe.confNOESCAPE 1LABEL BootLocallocalboot 0TEXT HELPBoot to local hard diskENDTEXTMENU SEPARATORMENU BEGIN MFCMENU TITLE Media Flow ControllerLABEL PreviousMENU LABEL Previous MenuTEXT HELPReturn to previous menuENDTEXTMENU EXITMENU SEPARATORMENU INCLUDE MFC/MFC.menuMENU END/tftpboot/pxelinux.cfg/pxe.confMENU TITLE PXE ServerNOESCAPE 1ALLOWOPTIONS 1PROMPT 0/tftpboot/MFC/MFC.menuLABEL 1MENU INCLUDE MFC/mfc/<version>/mfc_boot.menu/tftpboot/MFC/mfc/<version>/mfc_boot.menuMENU LABEL MFC<version>KERNEL MFC/mfc/<version>/linuxAPPEND initrd=MFC/mfc/<version>/initrd panic=10 noexec=off console=ttyS0,9600n8console=tty0 ramdisk_size=16384 rw installopt=accept-eula,ethsetup=pxe,auto-eth installfrom=http://172.168.21.254/MFC/mfc/<version>IPAPPEND 3TEXT HELPInstall Media Flow Controller 11.B.2 imageENDTEXT

Installing Media Flow Controller Software from the Network—PXE

Before you begin:

• See “Before Installing Media Flow Controller with PXE” on page 49.

• Plug your machine into a serial console, with flow control disabled, and configure the

BIOS to PXE boot. We recommend connecting the console to the terminal server and

opening a Telnet session for this procedure.

• Decide and implement the installation options that you want; these are described in

“PXE Configuration File Installation Options” on page 50. This procedure assumes that

no installation options have been configured in the PXE installation configuration file.



However, the PXE installation configuration file must still be modified as described in

“Setting Up Your PXE Server” on page 51 for successful installation.

To install Media Flow Controller from PXE:

1. Reboot the machine in PXE boot mode. The PXE boot prompt is displayed.

2. Enter the label that you configured in the PXE server for the Media Flow Controller

installation boot files and press Enter. If installing from a serial console, you are first

prompted to log in as root.

3. Log in as root.

A welcome message is displayed followed by an installation menu:

Enter 1 to Reboot without installing or restoringEnter 2 to Halt without installing or restoringEnter 3 to Start the installation from PXEEnter 1, 2, or 3 and press return :

4. Enter 3.

If the files are accessible, the following message is displayed followed by the end-user

license agreement (EULA) :

Ready to install or restore:<URL of image file>Enter 1 to Read the EULA agreement and continue with installation.Enter 2 to Reboot without installing or restoring.Enter 3 to Halt without installing or restoring.Enter 1, 2, or 3 :

5. Enter 1.

The EULA is displayed and then the following menu. Press the Space bar to scroll

through the EULA or enter q to jump to the end of the EULA.

Enter 1 to Read the EULA agreement again.Enter 'accept' to accept the EULA agreement and continue withinstallation.Enter 2 to Reboot without installing or restoring.Enter 3 to Halt without installing or restoring.Enter 1, 2, 3, or 'accept' : accept

6. Enter accept.

The following menu is displayed:

Enter 1 to NOT use part of the first disk for cache.Enter 2 to use part of the first disk for cache.Enter 3 to for an explanation of this choice.Enter 1, 2, or 3 :

7. Enter 1or2 (see “Choosing to Cache on the First Drive” on page 44 for the explanation).

The following menu is displayed unless you set init-cache or keep-cache in the PXE

configuration file:

Enter 1 to Install Media Flow Controller.Enter 2 to Restore Media Flow Controller.Enter 3 to Reboot without installing or restoring.Enter 4 to Halt without installing or restoring.



Or enter special options as instructed by support personnel.Note:Install will delete all cached data.Restore attempts to keep cached data.Enter 1, 2, 3 or 4 :

8. If this installation is:

• A first-time installation, enter 1.

If you have set both auto-eth and auto-reboot in the PXE configuration file, the

system reboots using the assignment you made with the ethsetup command.

• Not a first-time installation but you want to erase all the cached data, enter 1.

• Not a first-time installation and you want to preserve cached data, enter 2.

(In rare situations, some or all of the cached data might not be preserved. If you

need special partitioning for your root drive, which is typically not the case, call

Customer Support to access the special options.)

As the installation continues, it can take 10 minutes or more to complete, depending

on the number of disks Media Flow Controller needs to format. When completed, the

following menu is displayed. (Options 3 through 6 are omitted if you set an ethsetup

option in the PXE configuration file):

Installation is done at number>>> Phase 1 Installation Done <<<Enter 1 to Reboot to complete the installation.Enter 2 to Halt. Installation will continue when rebooted.Enter 3 to Flash ethernet port LEDs.Enter 4 to Configure ethernet names interactively.Enter 5 to Specify device for eth0 and eth1.Enter 6 to Reset ethernet naming back to default.Enter 7 to Use the PXE-boot interface for eth0.(<MAC_address_of_eth0)

9. If the:

• Correct interface naming is automatically assigned, enter 1.

The installation is completed and an “unconfigured” prompt is displayed as follows:


Continue with “Setting Up Basic System Connectivity” on page 46.

• PXE-boot interface (option 7) is the correct interface for eth0 (management

interface) and you want all the other interfaces to be automatically assigned, enter

7.

• PXE-boot interface (option 7) is not the correct interface for eth0, you must manually

assign the correct interface (typically, interface names must be manually assigned).

The Ethernet naming default is based on the order of the device’s PCI bus addresses

and often is not optimally assigned. It is very important that eth0 be assigned to

the proper port.

• Ethernet names are configured interactively, or to specify a device for eth0 or eth1,

enter 4 or 5, respectively. (See “Ethernet Naming Options” on page 38, for details.)



The interface assignments are displayed (options 3 through 6 are omitted if you

set that ethsetup option in the PXE configuration file) and the installation menu

reappears:

Enter 1 to Reboot to complete the installation.Enter 2 to Halt. Installation will continue when rebooted.Enter 3 to Flash ethernet port LEDs.Enter 4 to Configure ethernet names interactively.Enter 5 to Specify device for eth0 and eth1.Enter 6 to Reset ethernet naming back to default.Enter 7 to Use the PXE-boot interface for eth0.(<MAC_address_of_eth0)

• If the interface assignments are correct, enter 1 to reboot and complete the

installation.

The installation is completed and an “unconfigured” prompt is displayed as follows:


Continue with “Setting Up Basic System Connectivity” on page 46.





PART 2

Index

• Index on page 59


Index

Aarrays, configuring for optimum performance..............12

Bbasic system connectivity...................................................46

boot

system (CLI).....................................................................35

boot disk mirroring..................................................................22

configuration and monitoring tasks........................23

configuring VXA2000 Series Content Engine

BIOS................................................................................24

drive requirements.........................................................23

failure operation..............................................................23

installing Media Flow Controller on VXA2000

Series Content Engine...............................................31

performance.....................................................................23

resilvering...........................................................................32

resilvering status.............................................................33

SNMP trap notifications..............................................34

system logging................................................................34

troubleshooting..............................................................32

Ccache, choosing on the first drive.....................................44

CD

creating..............................................................................38

installation prerequisites.............................................37

installing Media Flow Controller..............................44

obtaining Media Flow Controller.................................3

CLI

connecting to....................................................................15

system reboot..................................................................16

upgrading.............................................................................5

configuration files, managing..............................................17

configuration, saving and applying....................................17

Configure mode.......................................................5, 15, 16, 17

connecting to and logging in to Media Flow

Controller................................................................................15

console port, accessing.........................................................12

controller

choosing for Media Flow Controller..........................11

configuring for optimum performance...................12

EEnable mode.................................................................15, 16, 17

end-user license agreement See EULA

Ethernet

configuring names interactively...............................39

device

resetting to default...............................................43

eth0

specifying devices to use for..............................41

eth1

specifying devices to use for..............................41

flash port LEDs................................................................38

naming option 3.............................................................38

naming option 4.............................................................39

naming option 5..............................................................41

naming option 6.............................................................43

naming options...............................................................38

Ethernet name assignment, changing after

installation.............................................................................15

EULA (end-user license agreement)...............44, 50, 52

example connectivity.............................................................13

example machine setup of management and traffic

ports..........................................................................................13

Fflash Ethernet port LEDs......................................................38

Hhard disk drives..........................................................................11

hard drive controller.................................................................11

hardware requirements, Media Flow Controller............9

host bus adapters.....................................................................11

Iinstallation issues, known....................................................19

installation planning

hardware requirements..................................................9

installing Media Flow Controller on VXA2000 Series

Content Engine for boot disk mirroring.......................31

JJBOD (Just a Bunch of Disks) mode..................................11

Mmachine setup example, Media Flow Controller.........13


Management Console...............................................15, 17, 38

Media Flow Controller

installing from the network, PXE..............................52

installing, CD or USB....................................................44

obtaining CD.......................................................................3

obtaining USB....................................................................3

upgrading CLI.....................................................................5

upgrading Web interface...............................................4

minimum system requirements, reverse and

transparent proxy................................................................12

Ppreboot execution environment See PXE

PXE

boot mode........................................................................52

configuration file options............................................50

configuring for installation.........................................50

installing Media Flow Controller from the

network..........................................................................52

obtaining Media Flow Controller software.............3

overview............................................................................49

prerequisites....................................................................49

server configuration.......................................................51

Rreboot system...........................................................................16

rebooting (CLI)........................................................................35

resilvering boot disk

...............................................................................................32

reverse proxy

minimum system requirements.................................12

SSerial Console............................................................................12

software

fallback................................................................................21

software, Media Flow Controller

obtaining..............................................................................3

system

basic connectivity, configuring.................................46

reboot (CLI)......................................................................35

system reboot...........................................................................16

Ttransparent proxy

minimum system requirements.................................12

troubleshooting installation................................................19

Uupgrading

CLI...........................................................................................5

Web interface.....................................................................4

USB

installation, prerequisites............................................37

installing Media Flow Controller..............................44

obtaining Media Flow Controller.................................3

VVXA2000 Series Content Engine

BIOS, configuring for boot disk mirroring..............24

WWeb interface, Media Flow Controller,

upgrading.................................................................................4



media flow media flow controller installation guide · 2014-10-06 · test-vos (config) # image...

Documents