Juniper Networks Media Flow Controller, Media Flow Manager Installation Guide
Werbung
Werbung
Media Flow Controller and Media Flow Manager
Installation Guide
Release
2.0.1
Published: 2010-5-14
Copyright © 2010, Juniper Networks, Inc.
Media Flow Controller / Media Flow Manager Installation Guide
End User License Agreement
READ THIS END USER LICENSE AGREEMENT (“AGREEMENT”) BEFORE DOWNLOADING, INSTALLING, OR USING THE SOFTWARE. BY
DOWNLOADING, INSTALLING, OR USING THE SOFTWARE OR OTHERWISE EXPRESSING YOUR AGREEMENT TO THE TERMS CONTAINED
HEREIN, YOU (AS CUSTOMER OR IF YOU ARE NOT THE CUSTOMER, AS A REPRESENTATIVE/AGENT AUTHORIZED TO BIND THE CUSTOMER)
CONSENT TO BE BOUND BY THIS AGREEMENT. IF YOU DO NOT OR CANNOT AGREE TO THE TERMS CONTAINED HEREIN, THEN (A) DO NOT
DOWNLOAD, INSTALL, OR USE THE SOFTWARE, AND (B) YOU MAY CONTACT JUNIPER NETWORKS REGARDING LICENSE TERMS.
1.
2.
3.
4.
5.
6.
7.
8.
The Parties. The parties to this Agreement are (i) Juniper Networks, Inc. (if the Customer’s principal office is located in the Americas) or Juniper Networks
(Cayman) Limited (if the Customer’s principal office is located outside the Americas) (such applicable entity being referred to herein as “Juniper”), and (ii) the person or organization that originally purchased from Juniper or an authorized Juniper reseller the applicable license(s) for use of the Software (“Customer”)
(collectively, the “Parties”).
The Software. In this Agreement, “Software” means the program modules and features of the Juniper or Juniper-supplied software, for which Customer has paid the applicable license or support fees to Juniper or an authorized Juniper reseller, or which was embedded by Juniper in equipment which Customer purchased from Juniper or an authorized Juniper reseller. “Software” also includes updates, upgrades and new releases of such software. “Embedded Software” means
Software which Juniper has embedded in or loaded onto the Juniper equipment and any updates, upgrades, additions or replacements which are subsequently embedded in or loaded onto the equipment.
License Grant. Subject to payment of the applicable fees and the limitations and restrictions set forth herein, Juniper grants to Customer a non-exclusive and non-transferable license, without right to sublicense, to use the Software, in executable form only, subject to the following use restrictions: a.
Customer shall use Embedded Software solely as embedded in, and for execution on, Juniper equipment originally purchased by Customer from Juniper or an authorized Juniper reseller.
b.
Customer shall use the Software on a single hardware chassis having a single processing unit, or as many chassis or processing units for which Customer has paid the applicable license fees; provided, however, with respect to the Steel-Belted Radius or Odyssey Access Client software only, Customer shall use such Software on a single computer containing a single physical random access memory space and containing any number of processors. Use of the
Steel-Belted Radius or IMS AAA software on multiple computers or virtual machines (e.g., Solaris zones) requires multiple licenses, regardless of whether such computers or virtualizations are physically contained on a single chassis. c.
d.
Product purchase documents, paper or electronic user documentation, and/or the particular licenses purchased by Customer may specify limits to
Customer’s use of the Software. Such limits may restrict use to a maximum number of seats, registered endpoints, concurrent users, sessions, calls, connections, subscribers, clusters, nodes, realms, devices, links, ports or transactions, or require the purchase of separate licenses to use particular features, functionalities, services, applications, operations, or capabilities, or provide throughput, performance, configuration, bandwidth, interface, processing, temporal, or geographical limits. In addition, such limits may restrict the use of the Software to managing certain kinds of networks or require the Software to be used only in conjunction with other specific Software. Customer’s use of the Software shall be subject to all such limitations and purchase of all applicable licenses.
For any trial copy of the Software, Customer’s right to use the Software expires 30 days after download, installation or use of the Software. Customer may operate the Software after the 30-day trial period only if Customer pays for a license to do so. Customer may not extend or create an additional trial period by re-installing the Software after the 30-day trial period.
e.
The Global Enterprise Edition of the Steel-Belted Radius software may be used by Customer only to manage access to Customer’s enterprise network.
Specifically, service provider customers are expressly prohibited from using the Global Enterprise Edition of the Steel-Belted Radius software to support any commercial network access services.
The foregoing license is not transferable or assignable by Customer. No license is granted herein to any user who did not originally purchase the applicable license(s) for the Software from Juniper or an authorized Juniper reseller.
Use Prohibitions. Notwithstanding the foregoing, the license provided herein does not permit the Customer to, and Customer agrees not to and shall not: (a) modify, unbundle, reverse engineer, or create derivative works based on the Software; (b) make unauthorized copies of the Software (except as necessary for backup purposes); (c) rent, sell, transfer, or grant any rights in and to any copy of the Software, in any form, to any third party; (d) remove any proprietary notices, labels, or marks on or in any copy of the Software or any product in which the Software is embedded; (e) distribute any copy of the Software to any third party, including as may be embedded in Juniper equipment sold in the secondhand market; (f) use any ‘locked’ or key-restricted feature, function, service, application, operation, or capability without first purchasing the applicable license(s) and obtaining a valid key from Juniper, even if such feature, function, service, application, operation, or capability is enabled without a key; (g) distribute any key for the Software provided by Juniper to any third party; (h) use the Software in any manner that extends or is broader than the uses purchased by Customer from Juniper or an authorized Juniper reseller; (i) use Embedded Software on non-
Juniper equipment; (j) use Embedded Software (or make it available for use) on Juniper equipment that the Customer did not originally purchase from Juniper or an authorized Juniper reseller; (k) disclose the results of testing or benchmarking of the Software to any third party without the prior written consent of Juniper; or (l) use the Software in any manner other than as expressly provided herein.
Audit. Customer shall maintain accurate records as necessary to verify compliance with this Agreement. Upon request by Juniper, Customer shall furnish such records to Juniper and certify its compliance with this Agreement.
Confidentiality. The Parties agree that aspects of the Software and associated documentation are the confidential property of Juniper. As such, Customer shall exercise all reasonable commercial efforts to maintain the Software and associated documentation in confidence, which at a minimum includes restricting access to the Software to Customer employees and contractors having a need to use the Software for Customer’s internal business purposes.
Ownership. Juniper and Juniper’s licensors, respectively, retain ownership of all right, title, and interest (including copyright) in and to the Software, associated documentation, and all copies of the Software. Nothing in this Agreement constitutes a transfer or conveyance of any right, title, or interest in the Software or associated documentation, or a sale of the Software, associated documentation, or copies of the Software.
Warranty, Limitation of Liability, Disclaimer of Warranty. The warranty applicable to the Software shall be as set forth in the warranty statement that accompanies the Software (the “Warranty Statement”). Nothing in this Agreement shall give rise to any obligation to support the Software. Support services may be purchased separately. Any such support shall be governed by a separate, written support services agreement. TO THE MAXIMUM EXTENT PERMITTED
BY LAW, JUNIPER SHALL NOT BE LIABLE FOR ANY LOST PROFITS, LOSS OF DATA, OR COSTS OR PROCUREMENT OF SUBSTITUTE GOODS
II Copyright © 2010, Juniper Networks, Inc.
Media Flow Controller / Media Flow Manager Installation Guide
OR SERVICES, OR FOR ANY SPECIAL, INDIRECT, OR CONSEQUENTIAL DAMAGES ARISING OUT OF THIS AGREEMENT, THE SOFTWARE, OR
ANY JUNIPER OR JUNIPER-SUPPLIED SOFTWARE. IN NO EVENT SHALL JUNIPER BE LIABLE FOR DAMAGES ARISING FROM
UNAUTHORIZED OR IMPROPER USE OF ANY JUNIPER OR JUNIPER-SUPPLIED SOFTWARE. EXCEPT AS EXPRESSLY PROVIDED IN THE
WARRANTY STATEMENT TO THE EXTENT PERMITTED BY LAW, JUNIPER DISCLAIMS ANY AND ALL WARRANTIES IN AND TO THE
SOFTWARE (WHETHER EXPRESS, IMPLIED, STATUTORY, OR OTHERWISE), INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE, OR NONINFRINGEMENT. IN NO EVENT DOES JUNIPER WARRANT THAT THE SOFTWARE, OR ANY
EQUIPMENT OR NETWORK RUNNING THE SOFTWARE, WILL OPERATE WITHOUT ERROR OR INTERRUPTION, OR WILL BE FREE OF
VULNERABILITY TO INTRUSION OR ATTACK. In no event shall Juniper’s or its suppliers’ or licensors’ liability to Customer, whether in contract, tort
(including negligence), breach of warranty, or otherwise, exceed the price paid by Customer for the Software that gave rise to the claim, or if the Software is embedded in another Juniper product, the price paid by Customer for such other product. Customer acknowledges and agrees that Juniper has set its prices and entered into this Agreement in reliance upon the disclaimers of warranty and the limitations of liability set forth herein, that the same reflect an allocation of risk between the Parties (including the risk that a contract remedy may fail of its essential purpose and cause consequential loss), and that the same form an essential basis of the bargain between the Parties.
9.
Termination. Any breach of this Agreement or failure by Customer to pay any applicable fees due shall result in automatic termination of the license granted herein. Upon such termination, Customer shall destroy or return to Juniper all copies of the Software and related documentation in Customer’s possession or control.
10.
Taxes. All license fees payable under this agreement are exclusive of tax. Customer shall be responsible for paying Taxes arising from the purchase of the license, or importation or use of the Software. If applicable, valid exemption documentation for each taxing jurisdiction shall be provided to Juniper prior to invoicing, and Customer shall promptly notify Juniper if their exemption is revoked or modified. All payments made by Customer shall be net of any applicable withholding tax. Customer will provide reasonable assistance to Juniper in connection with such withholding taxes by promptly: providing Juniper with valid tax receipts and other required documentation showing Customer’s payment of any withholding taxes; completing appropriate applications that would reduce the amount of withholding tax to be paid; and notifying and assisting Juniper in any audit or tax proceeding related to transactions hereunder. Customer shall comply with all applicable tax laws and regulations, and Customer will promptly pay or reimburse Juniper for all costs and damages related to any liability incurred by
Juniper as a result of Customer’s non-compliance or delay with its responsibilities herein. Customer’s obligations under this Section shall survive termination or expiration of this Agreement.
11.
Export. Customer agrees to comply with all applicable export laws and restrictions and regulations of any United States and any applicable foreign agency or authority, and not to export or re-export the Software or any direct product thereof in violation of any such restrictions, laws or regulations, or without all necessary approvals. Customer shall be liable for any such violations. The version of the Software supplied to Customer may contain encryption or other capabilities restricting Customer’s ability to export the Software without an export license.
12.
Commercial Computer Software. The Software is “commercial computer software” and is provided with restricted rights. Use, duplication, or disclosure by the
United States government is subject to restrictions set forth in this Agreement and as provided in DFARS 227.7201 through 227.7202-4, FAR 12.212, FAR
27.405(b)(2), FAR 52.227-19, or FAR 52.227-14(ALT III) as applicable.
13.
Interface Information. To the extent required by applicable law, and at Customer's written request, Juniper shall provide Customer with the interface information needed to achieve interoperability between the Software and another independently created program, on payment of applicable fee, if any. Customer shall observe strict obligations of confidentiality with respect to such information and shall use such information in compliance with any applicable terms and conditions upon which Juniper makes such information available.
14.
Third Party Software. Any licensor of Juniper whose software is embedded in the Software and any supplier of Juniper whose products or technology are embedded in (or services are accessed by) the Software shall be a third party beneficiary with respect to this Agreement, and such licensor or vendor shall have the right to enforce this Agreement in its own name as if it were Juniper. In addition, certain third party software may be provided with the Software and is subject to the accompanying license(s), if any, of its respective owner(s). To the extent portions of the Software are distributed under and subject to open source licenses obligating Juniper to make the source code for such portions publicly available (such as the GNU General Public License (“GPL”) or the GNU Library General
Public License (“LGPL”)), Juniper will make such source code portions (including Juniper modifications, as appropriate) available upon request for a period of up to three years from the date of distribution. Such request can be made in writing to Juniper Networks, Inc., 1 194 N. Mathilda Ave., Sunnyvale, CA 94089,
ATTN: General Counsel. You may obtain a copy of the GPL at http://www.gnu.org/licenses/gpl.html, and a copy of the LGPL at http://www.gnu.org/licenses/ lgpl.html.
15.
Miscellaneous. This Agreement shall be governed by the laws of the State of California without reference to its conflicts of laws principles. The provisions of the
U.N. Convention for the International Sale of Goods shall not apply to this Agreement. For any disputes arising under this Agreement, the Parties hereby consent to the personal and exclusive jurisdiction of, and venue in, the state and federal courts within Santa Clara County, California. This Agreement constitutes the entire and sole agreement between Juniper and the Customer with respect to the Software, and supersedes all prior and contemporaneous agreements relating to the Software, whether oral or written (including any inconsistent terms contained in a purchase order), except that the terms of a separate written agreement executed by an authorized Juniper representative and Customer shall govern to the extent such terms are inconsistent or conflict with terms contained herein. No modification to this Agreement nor any waiver of any rights hereunder shall be effective unless expressly assented to in writing by the party to be charged. If any portion of this Agreement is held invalid, the Parties agree that such invalidity shall not affect the validity of the remainder of this Agreement. This Agreement and associated documentation has been written in the English language, and the Parties agree that the English version will govern. (For Canada: Les parties aux présentés confirment leur volonté que cette convention de même que tous les documents y compris tout avis qui s'y rattaché, soient redigés en langue anglaise.
(Translation: The parties confirm that this Agreement and all related documentation is and will be in the English language)).
III
Document History
Media Flow Controller / Media Flow Manager Installation Guide
Date
2010-5-14
Media Flow Controller Version
Release 2.0.1
Comments
Document Version 2.0a
IV Copyright © 2010, Juniper Networks, Inc.
TABLE OF CONTENTS Media Flow Controller / Media Flow Manager Installation Guide
TABLE OF CONTENTS
End User License Agreement ...................................................................... II
1
2
Upgrading with the Web-Based Management Console ............................................... 2.22
Copyright © 2010, Juniper Networks, Inc.
V
TABLE OF CONTENTS Media Flow Controller / Media Flow Manager Installation Guide
3
Installation with CD-ROM or USB Drive ................................................. 3.25
Installing Media Flow Controller Software—CD-ROM/USB........................................ 3.26
4
Installing Media Flow Controller Software from Network—PXE ................................. 4.30
5
Installation on a Hypervisor—Evaluation Deployments Only ................. 5.33
6
Installing Media Flow Manager .............................................................. 6.35
Installing Media Flow Manager Software from Network—PXE................................... 6.36
VI Copyright © 2010, Juniper Networks, Inc.
CHAPTER 1 Preface Media Flow Controller / Media Flow Manager Installation Guide
CHAPTER 1
Preface
Juniper Networks Media Flow Controller / Media Flow Manager Installation Guide is written for system and network administrators who plan, implement, and manage media content delivery
environments. In addition to Guide to this Document , next, this preface includes these topics:
•
Documentation and Release Notes
•
•
•
•
•
Guide to this Document
This document provides information on the following topics:
•
Getting Started —Describes pre-installation planning and system requirements applicable
to all installs, and upgrade/reboot procedures.
•
Installation with CD-ROM or USB Drive
—Describes how to create USB install drives, how to install Juniper Networks Media Flow Controller using a CD-ROM or USB drive, and how to configure basic network connections.
•
—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.
•
Installation on a Hypervisor—Evaluation Deployments Only
—Describes how to set up your Hypervisor for a Media Flow Controller installation, how to install Media Flow
Controller on a Hypervisor, and how to configure basic network connections.
•
—Describes how to install Media Flow Manager using PXE, and how to configure basic network connections.
Documentation and Release Notes
To obtain the most current version of all Juniper Networks® technical documentation, see the product documentation page on the Juniper Networks website at http://www.juniper.net/techpubs/ .
Juniper Networks supports a technical book program to publish books by Juniper Networks engineers and subject matter experts with book publishers around the world. These books go
Copyright © 2010, Juniper Networks, Inc.
Guide to this Document 9
CHAPTER 1 Preface Media Flow Controller / Media Flow Manager Installation Guide beyond the technical documentation to explore the nuances of network architecture, deployment, and administration using JUNOS 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 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 .
Typographical Conventions
Table 1
Table 1 describes the typefaces used in this book.
Typefaces Used in This Book
Typeface
Arial
Arial Bold
Arial Italic
Ordinary text.
Use
Commands in running text, and screen elements such as page titles, and option labels.
Book titles, and emphasis.
Courier New
Text displayed online at a command line.
Courier New
Bold
Text that you type exactly as shown; variables are shown in chevrons (< > ), parameters (which may include variables) are shown in box brackets ([ ]), options are shown in curly brackets ({ }). Runon lines are indicated by an indent
(as shown at right).
Example
The origin server organizes media content hierarchically.
Use the interface command to configure IP addresses.
In the Management Console, use the Setup > Date and time page.
See the Juniper Networks Media
Flow Controller Administrator’s
Guide
Please enter your IP address
interface eth0 ip address
<IP address>
Terminology
This section provides definitions for Juniper Networks and industry-standard terms that may be unfamiliar to the reader.
Edge cache:
An appliance placed between the Internet and the Web server which caches content (like Java Script, CSS, images, etc.) and delivers them for the server, freeing up the
Web server for other processes. Media Flow Controller as an edge cache is effectively a
“reverse proxy,” that provides these benefits: reduces the load (network and CPU) on an origin server by servicing previously retrieved content and enhances the user experience due to a decrease in latency.
NIC
Network Interface Controller/Card.
10 Typographical Conventions Copyright © 2010, Juniper Networks, Inc.
Media Flow Controller / Media Flow Manager Installation Guide CHAPTER 1 Preface
Origin Library
The source of media content.
Origin Server
The media content server. Juniper Networks Media Flow Controller is available as an Origin Server as well as an Edge Cache.
SAS
Serial attached SCSI. A data transfer technology designed to move data to and from computer storage devices such as hard drives and tape drives.
SATA
Serial Advanced Technology Attachment. A computer bus technology primarily designed for transfer of data to and from a hard disk.
Command Arguments Key
This section is a key to the meaning and format of the angle-bracketed options described in this document.
EXEC The command can be executed without entering Configure mode, which is reserved for privileged users. EXEC commands are only executed once; for example, re-formatting a disk is an EXEC command. EXEC commands can’t be saved across reboots.
<domain>
A domain name; for example, example.com
<hostname>
A hostname; for example, sedona.example.com
<IP_address>
An IPv4 address; for example, 192.168.0.1.
<MAC_address>
A MAC address. The segments may be 8 bits or 16 bits at a time, and may be delimited by colon (:) or dot (.). Examples: 11:22:33:44:55:66, 1122:3344:5566,
11.22.33.44.55.66
, or1122.3344.5566.
<netmask>
A netmask (for example, 255.255.255.0) or mask length prefixed with a slash (for example, /24). These two express the same information in different formats.
<network prefix>
An IPv4 network prefix specifying a network. Used in conjunction with a netmask to determine which bits are significant.e.g. "192.168.0.0".
<regex>
An extended regular expression as defined by the grep man page. The value you provide here is passed on to grep -E.
<port>
TCP/UDP port number
<TCP_port>
A TCP port number in the full allowable range [0..65535].
<URL>
A normal URL, using any protocol that WGET supports, including HTTP, HTTPS,
FTP, and TFTP; or a pseudo-URL specifying an SCP file transfer.
The SCP (secure channel protocol) pseudo-URL format is
scp://<username>[:<password>]@<hostname>/<path>[</filename>]
The path is an absolute path. Paths relative to the user's home directory are not currently supported.
Important!
You must have an SCP or FTP server installed in order to SCP or FTP, respectively, files to your machine.
Note!
Media Flow Controller does not support outbound FTP transactions.
Note!
If you omit the :password part, you may be asked for the password in a follow-up prompt, where you can type it securely (without the characters being echoed). This prompt occurs if the cli default prompt empty-password setting is true; otherwise, the CLI assumes you do not want any password. If you include the colon (:) character, this is taken as an explicit declaration that the password is empty, and you are not prompted in any case.
Command Arguments Key 11
CHAPTER 1 Preface Media Flow Controller / Media Flow Manager Installation Guide
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
■ 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
•
Product Warranties
—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: http://www.juniper.net/techpubs/
•
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/
12 Documentation Feedback Copyright © 2010, Juniper Networks, Inc.
Media Flow Controller / Media Flow Manager Installation Guide CHAPTER 1 Preface
•
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/
Opening a Case with JTAC
You can open a case with JTAC on the Web or by telephone.
•
Use the Case Manager tool in the CSC at http://www.juniper.net/cm/
•
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
Requesting Technical Support 13
CHAPTER 1 Preface Media Flow Controller / Media Flow Manager Installation Guide
14 Requesting Technical Support Copyright © 2010, Juniper Networks, Inc.
CHAPTER 2 Getting Started Media Flow Controller / Media Flow Manager Installation Guide
CHAPTER 2
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. There are two ways you can obtain the Media Flow Controller or Media Flow Manager 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, or download files to an empty USB drive. How to install from
CD or USB drive is described in this guide.
•
You use PXE to obtain the software image. You must have a PXE server configured in order to use the PXE install option and a Web server to serve the image. How to configure your PXE server for Media Flow Controller or Media Flow Manager installation and how to install with PXE is described in this guide.
See
“Requesting Technical Support” on page 1-12
for PXE, USB, or CD install packages.
See
if all you need to do is an upgrade.
Installation steps for installing Media Flow Controller with specific media are provided in the following chapters:
•
Installation with CD-ROM or USB Drive
•
•
Installation on a Hypervisor—Evaluation Deployments Only
Installation steps for installing Media Flow Manager using PXE are given in
Flow Manager . Media Flow Manager installation is similar to Media Flow Controller installation
with fewer requirements and the command changes from install-mfd to install-mfc.
Juniper Networks VXA Series
Juniper Networks offers Media Flow Controller and Media Flow Manager on VXA series appliances. If you purchase Media Flow Controller or Media Flow Manager this way, the software comes pre-installed; just power up the box and login with the default credentials
admin
and no (empty) password.
For details on Juniper Networks Media Flow Solution, including technical specifications, please see the Media Flow Controller With VXA Series and Media Flow Manager datasheet .
Copyright © 2010, Juniper Networks, Inc.
Juniper Networks VXA Series 15
CHAPTER 2 Getting Started Media Flow Controller / Media Flow Manager Installation Guide
Pre-Installation Planning
Before installing Juniper Networks software, ensure that your hardware meets the following conditions:
•
Running optimally (all hardware diagnostics have been run and passed successfully).
•
All data on all hard drives is or can be removed; Juniper Networks Media Flow Controller and Media Flow Manager completely format all disks when installed.
•
Top-quality cables are used. Juniper Networks recommends CAT5e or CAT6 for GbE,
CAT6A for 10GbE. However, CAT5 cables can be used for GbE if the cable lengths are expected to be short (ex. 5’ or less). A poorly functioning cable can inhibit performance.
•
Single, Dual, or Quad Port Server GbE NIC for traffic, available (recommended for Media
Flow Controller installation).
•
Console server / terminal server available (recommended).
Additionally, you’ll need:
•
Hostnames/IP addresses (including but not limited to, Subnet Mask, Default Gateway) for traffic and management ports.
•
Domain name for the for resolving hostnames.
•
Hostnames/IP addresses for external servers such as origin servers/libraries, DNS, NTP, logging, and/or storage servers.
Tip!
As you install the software some install messages pass the screen very quickly. The log of all the install messages can be found in the file /tmp/install-mfd.log for Media Flow
Controller or /tmp/install-mfc.log for Media Flow Manager, so you can go back and see all the messages.
Tip!
Go to NTP Servers Web to find public NTP servers.
Important!
Media Flow Controller and Media Flow Manager do not support RAID arrays.
Accessing 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)
System Requirements
The following are required and/or recommended for Media Flow Controller optimal performance. For the most up-to-date and complete information, see the Media Flow
Controller With VXA Series and Media Flow Manager datasheet .
16 Pre-Installation Planning Copyright © 2010, Juniper Networks, Inc.
Media Flow Controller / Media Flow Manager Installation Guide CHAPTER 2 Getting Started
Table 2 Media Flow Controller System Requirements
Hardware Description
Processor
RAM
Direct Attached Storage
(DAS)
One quad-core (2.0 GHz or higher) x86 64-bit processor (second quadcore processor recommended for future capacity expansion).
8GB to 16GB depending on throughput requirements.
Up to 16 DAS drives (SATA or SAS), either hard disk or solid state disks, depending on server model and amount of cache.
72 GB minimum for boot drive.
32 GB minimum recommended for additional drives (used for cache only).
Network Attached Storage NFS (Network File System) supported for handling cache misses.
Network Interfaces Up to ten 1GbE ports or one 10GbE port for content delivery.
Management Interface Dedicated 1GbE port. Note that network ports on the motherboard use lower performance controllers adequate for a management interface that typically does not require the full GbE capacity.
Example Machine Setup
Table 3 provides details of an example configuration; your configuration may differ considerably. In Table 3, and Figure 1, the appliance wiring logic is:
•
Eth 0
—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
—Service 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 GbE.
These are the minimum TCP/UDP port requirements, other ports can be opened up on an asneeded basis. By default, the Media Flow Controller management port is 8080.
Pre-Installation Planning 17
CHAPTER 2 Getting Started Media Flow Controller / Media Flow Manager Installation Guide
Figure 1 Example Connectivity
Table 3 Example Machine Setup of Management and Traffic Ports
Interface Connectivity IP Address Subnet Mask Gateway
Open
Ports
Internet
Access
Eth 0
Eth 1
Eth 2
Eth 3
Eth 4
Eth 5 onboard onboard
PCIe card
PCIe card
PCIe card
PCIe card
192.168.1.100
172.20.46.10*
10.1.1.11
10.1.2.11
10.1.3.11
10.1.4.11
255.255.255.0 192.168.1.1
255.255.255.0 n/a
255.255.255.0 n/a
255.255.255.0 n/a
255.255.255.0 n/a
255.255.255.0 n/a
8080, 22 yes
80 yes
80
80 n/a n/a
80
80
LO** onboard 192.168.1.101
255.255.255.0 192.168.1.1
80, 22
*Eth0 AND Eth1 can be on the same subnet; this examples indicates they are not.
**LO stands for “Lights Out” remote management. n/a n/a yes
Purpose
Management
Origin fetch
Traffic
Traffic
Traffic
Traffic
Management
Assigning eth0 and eth1
By default, eth0 and eth1 interfaces are assigned in the order that the drivers are loaded and eth0 might not be assigned to the port that you want and/or the port that PXE boot uses. A command eth-setup, used at installation only (not available after installation), allows you to manually assign eth0 and eth1, or set a method by which they are assigned.
18 Pre-Installation Planning Copyright © 2010, Juniper Networks, Inc.
Media Flow Controller / Media Flow Manager Installation Guide CHAPTER 2 Getting Started
Important!
For first time installations, if you do not have any Media Flow Controller licenses, follow the steps outlined in this section to choose which port to make eth0. If you do already have licenses, follow these steps to make sure that the correct interface is made eth0.
Licenses are tied to MAC addresses, so the correct interface must be assigned eth0 in order for them work.
Determining Which Interface to Use for eth0
Determining what device will be the default eth0 can be difficult; it depends on the particular
NICs and the version of the drivers. One way to find out is to only have an ethernet cable connected; for the case of PXE booting, have it connected to the port that PXE boot uses, normally one of the built-in ports. Then use either eth-setup or ifconfig to see which port was assigned an IP address. Example:
# eth-setup
Installed ethernet devices: eth0 Link encap:Ethernet HWaddr 00:15:17:AB:C5:D5
UP BROADCAST MULTICAST MTU:1500 Metric:1 eth1 Link encap:Ethernet HWaddr 00:15:17:AB:C5:D4
UP BROADCAST MULTICAST MTU:1500 Metric:1 eth2 Link encap:Ethernet HWaddr 00:15:17:AB:C5:D7
UP BROADCAST MULTICAST MTU:1500 Metric:1 eth3 Link encap:Ethernet HWaddr 00:15:17:AB:C5:D6
UP BROADCAST MULTICAST MTU:1500 Metric:1 eth4 Link encap:Ethernet HWaddr 00:30:48:B8:F8:22
inet addr:172.19.172.187 Bcast:172.19.172.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 eth5 Link encap:Ethernet HWaddr 00:30:48:B8:F8:23
UP BROADCAST MULTICAST MTU:1500 Metric:1 eth-setup syntax: default|least-ports|most-ports|<URL>|url|eth<num>
[eth<num>|<HWaddr>]|<HWaddr> [eth<num>|<HWaddr>]
In the example, the Hwaddrs show that the 4 port NIC was assigned eth0 thru eth3 and the two built-in ports were given eth4 and eth5; and eth4 is the only port that is connected because it has an inet addr assigned. If other ports were connected to networks, they also would have assigned INET addresses; in that case, depending on the network design, you might be able to see which ports were connected to which networks by the left-most part of the assigned INET addresses. (In the installation guide example, eth0 is assigned 192.168.1.100, eth1 172.20.46.10, and the others were assigned 10.1.*.*)
Usage examples:
•
eth-setup url
—Use if installation is done via specifying an image URL and access to that
URL is only available on the ethernet port that you want to be eth0.
•
eth-setup least-ports
—Use if you know that the on-board NIC has two ports and the expansion card has 4 ports, and you want eth0 to use the on-board NIC. If there are two or more parts on that NIC, eth1 is assigned the second port that loads.
Pre-Installation Planning 19
CHAPTER 2 Getting Started Media Flow Controller / Media Flow Manager Installation Guide
•
eth-setup most-ports
—Use if the hardware has a built-in 2-port NIC and a single port expansion NIC, and you want eth0 to use the on-board NIC; eth1 is assigned the second port.
•
If you know the hardware address of the port you want for eth0, use it; for example
eth-setup 00:23:7D:61:06:C8
. You can repeat this command to set eth1.
•
If access to some other URL is available only via the device you want for eth0, such as an
"MFC" machine, you can specify that URL; e.g. eth-setup http://172.20.172.55/index.html.
Tip!
For the <HWaddr>, aka MAC addr, you do not have to specify all the octets, you can specify as little as two of the right most octets as long as that is unique across all the installed ethernet devices.
eth-setup [default | least-ports | most-ports | <URL> | url | eth <num> [eth
<num> | <HWaddr>] | <HWaddr> [eth <num> | <HWaddr>]
Examples of all the forms:
eth-setup default
eth-setup least-ports eth-setup most-ports eth-setup http://66.224.165.46/mfd-images/1.0.0-45.img
eth-setup url eth-setup eth4 eth-setup 00:30:48:B8:F8:22 eth-setup F8:22 eth-setup eth4 eth2 eth-setup eth4 f8:23 eth-setup f8:22 eth2 eth-setup f8:23 ca:A8
Upgrading and Rebooting
Before upgrading you may want to save your current configuration off-box first. If you re-install the software (as opposed to upgrade only), must save your current configuration off-box if you want to keep it, because the installation process deletes all the information on the root drive where the configuration data is stored. If it is saved off-box, you can then restore your configuration data from the saved file after the installation is complete.
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.
1. Save a configuration to a file; use no-switch to leave the current configuration active. Use
show configuration files
to see the saved file name.
configuration write to <file_name> no-switch
2. Use SCP to send the just-saved configuration file to a server (must have SCP installed);
See the
“Command Arguments Key” on page 1-11 for the scp URL format).
configuration upload <file_name> <URL>
20 Upgrading and Rebooting Copyright © 2010, Juniper Networks, Inc.
Media Flow Controller / Media Flow Manager Installation Guide CHAPTER 2 Getting Started
3. When you are ready, fetch the saved configuration file.
configuration fetch <URL>/<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-switch test-vos (config) # show configuration files
04_01_09 initial (active) initial.bak
test-vos (config) # configuration upload 04_01_09 scp://joe@sv05/home/joe
Password: ******* test-vos (config) # configuration delete 04_01_09 test-vos (config) # show configuration files initial (active) initial.bak
test-vos (config) # configuration fetch scp://joe@sv05/home/joe/04_01_09
Password: ******* test-vos (config) # show configuration files
04_01_09 initial (active) initial.bak
test-vos (config) # configuration switch-to 04_01_09 test-vos (config) # show configuration files
04_01_09 (active) initial initial.bak
test-vos (config) #
6. Merge the common settings from a given configuration file to the active configuration file.
configuration merge <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]
Upgrading
When upgrades are available, Juniper Networks will broadcast the upgrade URL to use in this procedure. Note that the upgrade preserves the current, saved, configurations; however, you may still want to save the current configuration to a file off-box by following the previous procedure,
“Saving and Applying a Configuration” on page 2-20 .
Note!
If disk partitions are changing then a re-manufacture is required; follow
Applying a Configuration” on page 2-20
steps along with the appropriate installation instructions given in the following chapters.
Upgrading and Rebooting 21
CHAPTER 2 Getting Started Media Flow Controller / Media Flow Manager Installation Guide
Upgrading with the Web-Based Management Console
You can use the Web-based Management Console, System Config > Upgrade page to easily upgrade your system if you have an install image URL or have obtained the image and installed it locally.
Important!
After upgrading to the image using the System Config >
Upgrade
page, you must go to the System Config > Reboot page and reboot your system for the upgrade to complete.
To install Media Flow Controller or Media Flow Manager, which means removing all the data on the root drive for a fresh install, see the following installation chapters as appropriate.
Upgrading with the CLI
Follow these steps to upgrade your system using the CLI.
1. Fetch the configuration upgrade image file with the Juniper Networks URL.
image fetch <URL>/<filename>
2. Install the image.
image install <filename>
3. Verify which boot image contains the upgrade.
show images
4. Switch to the boot partition containing the upgrade image, if needed.
image boot next
5. Reboot to that partition.
reload
6. Verify that the new image is booted.
show version
Rebooting
You can either reboot or shutdown the software; if you use shutdown, the system does not reboot until it is power-cycled. In the CLI, use these commands; in the Management Console, use the System Config > Reboot page.
1. Reboot or shutdown the system.
reload
2. Set boot parameters; optionally specify from which location the image should boot by default; there are only two locations to choose from so the options are 1 and 2 for location
ID. If next is used, 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 ?
4. View current settings.
show boot
22 Upgrading and Rebooting Copyright © 2010, Juniper Networks, Inc.
Media Flow Controller / Media Flow Manager Installation Guide CHAPTER 2 Getting Started
Configuration File Management
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.
1. View configuration file options.
configuration ?
2. View current settings.
show configuration
3. View configuration file viewing options.
show configuration ?
4. Save the current configuration through reboots.
write memory
In the Management Console, use the Setup > Configurations page to upload a text file with
CLI commands (executed immediately in the running configuration), or enter directly to the
Management Console CLI commands to be executed immediately.
Upgrading and Rebooting 23
CHAPTER 2 Getting Started Media Flow Controller / Media Flow Manager Installation Guide
24 Upgrading and Rebooting Copyright © 2010, Juniper Networks, Inc.
CHAPTER 3 Installation with CD-ROM or USB Drive Media Flow Controller / Media Flow Manager Installation Guide
CHAPTER 3
Installation with CD-ROM or USB Drive
This chapter describes
Installing Media Flow Controller Software—CD-
ROM/USB , and configuring the needed network connections. To obtain the Media Flow
Controller CD-ROM or USB install package, see “Requesting Technical Support” on page 1-
Important!
Before beginning, be sure to review “ Pre-Installation Planning” 16
for important information.
Tip!
If you received a USB drive or CD-ROM with the Media Flow Controller install package already installed, skip the next section and go directly to
Installing Media Flow Controller
You can request a CD-ROM or a USB drive with the Juniper Networks software, or download the ISO image and burn your own CD-ROM and/or create a USB drive, and install using it.
Creating CD-ROMs
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>
Creating USB Images
The files in the Juniper Networks installation zip allow you to manufacture a Media Flow
Controller appliance using a bootable USB storage device, like a jumpdrive, pendisk, etc.; from Windows or Linux.
Windows Instructions
1. Plug in your USB drive. See that it shows up in My computer.
2. Note the drive letter that Windows has given your USB drive. It will be something like d: e: or f:.
Important!
Make absolutely certain you know which drive letter is your USB drive, or you may seriously damage your computer with the following instructions.
3. Unzip the Juniper Networks mfgusb.zip file into the top folder (root directory) of your USB drive. Choose extract all.
4. Double-click on the relevant install file (inst_X.bat). For example, for drive d:, double click on inst_d.bat. A window will flash up on your screen and disappear. You have made your
USB drive bootable.
5. Power off (not just reboot) your computer. Start > Shut Down.
Copyright © 2010, Juniper Networks, Inc.
Creating CD-ROMs 25
CHAPTER 3 Installation with CD-ROM or USB Drive Media Flow Controller / Media Flow Manager Installation Guide
Linux Instructions
1. Plug in your USB drive. Become root. The rest of these instructions are done as root.
2. Mount the USB drive somewhere of your choosing. These instructions use /dev/sda1, with the USB drive mounted on /mnt/flash. You may need to look at /etc/fstab, dmesg, or the /var/log/messages file to discover the partition name. Depending on how your USB drive is set up, the drive may be all one partition with no partition table (like /dev/sda), or may be a partition inside a partition table (like /dev/sda1).
mount /dev/sda1 /mnt/flash
3. Unzip the Juniper Networks mfgusb.zip file into the root directory of your USB drive, and then unmount it:
cd /mnt/flash unzip ~/Work/tree/output/product-demo-i386/release/mfgusb/mfgusb-demoi386-20050710-090757.zip
cd ~ umount /mnt/flash
4. Install syslinux on the drive to make it bootable. The default version of syslinux included is 3.09 (as syslinux.exe), and an older version 2.11 is also included (as sysln211.exe).
Important!
Remember to substitute your device name here, is it may be different than
/dev/sda1
. If you use the wrong device name you could seriously damage your computer!
syslinux /dev/sda1
5. Power off (not just reboot) your computer.
shutdown -h now
Installing Media Flow Controller Software—CD-ROM/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, at times 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 have a choice to retain the data in the caches.
1. Put in the CD-ROM, or plug in the USB drive, and login as admin (no password), enter
enable
and then configure terminal to get the configuration prompt.
2. Reboot (reload command). Note the shutdown initiated with reload can take several minutes. During this time, a login prompt displays. Do not log in to Media Flow Controller
while reload is taking place
. If necessary, press the relevant function key at boot time to get to the boot menu. On Dell boxes, F11 takes you to the boot menu. In the boot menu, choose either CD-ROM or USB as appropriate. When it finishes booting, you will be at a #
(configure) prompt.
3. To specify how the ports are assigned (can affect assignation of eth0 and eth1) or to assign the ports manually, use eth-setup. If not specified, the default assignation of ports
(eth-setup default) is the order in which the drivers are loaded. First, determine which port to use with the following command that shows which port has an inet address (the last two octets of the HWaddr are what you need).
eth-setup
26 Installing Media Flow Controller Software—CD-ROM/USB Copyright © 2010, Juniper Networks, Inc.
Media Flow Controller / Media Flow Manager Installation Guide CHAPTER 3 Installation with CD-ROM or USB Drive
4. Type the following command to get the Media Flow Controller image file installed, this includes specifying how to handle the cache: either initialize it (init-cache) or retain it
(keep-cache). Note that choosing keep-cache only preserves the cache on a drive when it has a Media Flow Controller cache on the drive that uses the same partition layout that the previous Media Flow Controller version used. For drives without existing Media Flow
Controller caches, or incompatible caches, the cache is cleared even if keep-cache is specified. Use eth-setup and the information you obtained in the previous step to set the
management interface; for details on eth-setup usage, see “Assigning eth0 and eth1” on page 2-18
.
install-mfd {init-cache | keep-cache} eth-setup <port_specification>
5. The end-user license agreement (EULA) displays. You must type yes to proceed. You can also type no, in which case the installation is cancelled; or again to see the EULA again.
The following message displays:
Installation is done at <number>
6. Reboot by typing reboot. When prompted for build choice, do nothing; this brings up the
Media Flow Controller platform now on the local disk.
7. Log in as User admin; there is no default password.
8. Enter configuration mode.
enable configure terminal
9. Set the IP address, hostname, default gateway, DNS server, and a domain list (to resolve unqualified hostnames). Install licenses, if you have the license keys.
interface eth0 ip address <management_port_IP_address> <netmask> hostname <hostname_for_machine> ip default-gateway <gateway_server_IP_address> ip name-server <DNS_server_IP_address> ip domain-list <domain_name_for_resolving_hostnames> ...
ntp server <NTP_server_IP_address> license install <license_key>
10. Save these settings through a reboot.
configuration write
11. As you have just changed the network information for your system, you must re-associate
Media Flow Controller with the interfaces. Either reboot (reload command) or enter this command:
service restart mod_delivery
12. Display the software version. If you have installed licenses, check those, too.
show version show license
13. 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, “Example Machine Setup of Management and
Traffic Ports,” on page 18 shows a typical Media Flow Controller configuration.
14. Sanity check: From another machine attempt to ping each address, and open an SSH session to the server as Admin.
You are now ready to begin configuring Media Flow Controller. See the Juniper Networks
Media Flow Controller Administrator’s Guide and CLI Command Reference
.
Installing Media Flow Controller Software—CD-ROM/USB 27
CHAPTER 3 Installation with CD-ROM or USB Drive Media Flow Controller / Media Flow Manager Installation Guide
Note!
Using keep-cache during installation cannot always preserve some or all of the caches.
Note!
If an unexpected interface is assigned eth0, your installed licenses will be invalid since they rely on the MAC address of an assigned interface and that interface changed. If that is the case, you need to manually assign the interfaces; see
“Assigning eth0 and eth1” on page 2-18
for details.
Troubleshooting
This section offers some troubleshooting tips for CD/USB installations.
USB Won’t Boot
If your USB seems messed up, or won't boot, you may want to try these steps, which will destroy everything on the USB.
From Linux
1. Figure out which raw device is yours, WITHOUT the partition number. We'll assume it's
/dev/sda
. If you think it's /dev/sda1, use /dev/sda.
2. As root do the following: (Note that mbr.bin is included in the zip file, so the instructions assume you start out as root in the mfgusb zip, unzipped on your hard disk.)
dd if=/dev/zero of=/dev/sda bs=512 count=100 sfdisk -R /dev/sda dd if=mbr.bin of=/dev/sda bs=1 echo ',,6,*' | sfdisk /dev/sda mkdosfs / dev/sda1 syslinux /dev/sda1
3. Unzip the image, as in the instructions above. In the example, your device name is
/dev/sda1
, not /dev/sda.
mount /dev/sda1 /mnt/flash cd /mnt/flash unzip ~/Work/tree/output/product-demo-i386/release/mfgusb/mfgusb-demoi386-20050710-090757.zip
cd ~ umount /mnt/flash
4. Continue on with step 5 for either Windows or Linux, above
USB Won’t Mount
In cases where the USB CD-ROM drive is not recognized/mounted during manufacture, use the following Linux commands:
mknod /dev/sr0 –b 11 0 mount /dev/sr0 /mnt/cdrom
Then run the regular install command, i.e. install-mfd mfg/<image>.img init-cache.
28 Troubleshooting Copyright © 2010, Juniper Networks, Inc.
CHAPTER 4 Installation with PXE Media Flow Controller / Media Flow Manager Installation Guide
CHAPTER 4
Installation with PXE
This chapter describes
Installing Media Flow Controller Software from Network—PXE
, and configuring the needed network connections. To obtain the Media
Flow Controller PXE install package, contact Juniper Networks Support; see “Requesting
Technical Support” on page 1-12
.
Important!
Before beginning, be sure to review “ Pre-Installation Planning” 16
for important information.
Preparing Your PXE Server
PXE (Preboot eXecution Environment) is a way for an un-configured machine to find a server, download an image from it, and boot. PXE works by the BIOS first making a DHCP request. In the DHCP response it gets network information for itself as well as the IP of a TFTP server and the name of an image. It then pulls down from the TFTP server a mini-image that is interactive over the console and serial console of the machine, and allows selection of the real image to boot. The real image consists of the boot floppy kernel and rootfloppy file system image.
Setup Instructions
There are two parts to setting up PXE for installing Media Flow Controller. First, follow these steps to set up your PXE server, then see the following note for managing the installation software.
1. Put these two PXE install package files, both have the same <unique ID> string, into your
PXE server tree:
rootflop-mfd-x86_64-<uniqueID>.img vmlinuz-bootflop-mfd-x86_64-<uniqueID>
2. Next, edit the PXE server configuration files on your system to make these available for booting from. For example, if the uniqueID string in the Juniper Networks filenames is
rel1.1
, and you place them in a directory named mfd-install, you make these available via the name “mfd-install” on a Redhat Linux PXE server by editing pxelinux.cfg/default to add a “LABEL” line, a “kernel” line, and an “append” line like this:
LABEL mfd-install kernel mfd-install/vmlinuz-bootflop-mfd-x86_64-rel1.1
append initrd=mfd-install/rootflop-mfd-x86_64-rel1.1.img panic=10 noexec=off console=ttyS0,9600n8 console=tty0 ramdisk_size=16384 rw
3. Next, edit the bootmsg.txt file to add a line that references the label you used:
<uniqueLabel> <description text>
Using the values above, this would be like this:
mfd-install Juniper Networks Media Flow Controller installation
Copyright © 2010, Juniper Networks, Inc.
Preparing Your PXE Server 29
CHAPTER 4 Installation with PXE Media Flow Controller / Media Flow Manager Installation Guide
The Media Flow Controller installation image must be accessible to the machine with the PXE server. For example, if the machine being installed has the eth0 network connected to a
Juniper Networks download site, the installation image file would be put on a Web server that is accessible; this is typically the PXE server.
Important!
For Media Flow Controller PXE installations only, an additional file, manufacture.tgz, that you can download or access with the image file, must be placed in the same directory as the image file; this is not optional. You can specify the directory where the two files are if they are named a certain way. When you specify the directory, the image file needs to be named image.img, and the manufacture TGZ file needs to be named
manufacture.tgz
. If you specify the image file without specifying a directory, the manufacture
TGZ file must be in the same directory and follow the same naming convention:
Specified
image-<something>.img
<something>.img
Manufacture.tgz Required Name
manufacture-<same something>.tgz
<same something>.tgz
Installing Media Flow Controller Software from Network—PXE
You must have a configured PXE server (see
Setup Instructions , above) and the URL of the
Juniper Networks Media Flow Controller software image in order to use this procedure.
Before you begin: Plug your machine into a serial console, with flow control disabled, and configure your BIOS to PXE boot. Juniper Networks recommends connecting the console to the terminal server and opening a TELNET session for this procedure.
1. Access the console connected to the Media Flow Controller and login as admin (no password), enter enable and then configure terminal to get the configuration prompt.
2. Boot the machine (reload command) in PXE boot mode. Note the shutdown initiated with
reload
can take several minutes. During this time, a login prompt displays. Do not log in to
Media Flow Controller while reload is taking place
. If necessary, press the relevant function key at boot time to get to the boot menu and choose PXE; on Dell boxes, F11 takes you to the boot menu. When you get the PXE boot prompt, type in the label that you configured in the PXE server for the Media Flow Controller installation boot files (e.g.
install-mfd
).
Tip!
When it finishes booting, you will be at a # (configure) prompt unless you are on a serial console, where, instead, you will see a login prompt; in this case, enter root to bring you to the # prompt.
3. To specify how the ports are assigned (can affect assignation of eth0 and eth1) or to assign the ports manually, use eth-setup. If not specified, the default assignation of ports
(eth-setup default) is the order in which the drivers are loaded. First, determine which port to use with the following command that shows which port has an inet address (the last two octets of the HWaddr are what you need).
eth-setup
4. Type the following command to get the Juniper Networks Media Flow Controller image file installed, this includes specifying the URL of the image and how to handle the cache: either initialize it (init-cache) or retain it (keep-cache). Note that choosing keep-cache only preserves the cache on a drive when it has an Media Flow Controller cache on the
30 Installing Media Flow Controller Software from Network—PXE Copyright © 2010, Juniper Networks, Inc.
Media Flow Controller / Media Flow Manager Installation Guide CHAPTER 4 Installation with PXE drive that uses the same partition layout that the previous Media Flow Controller version used. For drives without existing Media Flow Controller caches, or incompatible caches, the cache is cleared even if keep-cache is specified. Use eth-setup and the information you obtained in the previous step to set the management interface; for details on eth-
setup
usage, see
“Assigning eth0 and eth1” on page 2-18 )
install-mfd <URL_of_image_file> {init-cache | keep-cache} eth-setup
<port_specification>
5. The end-user license agreement (EULA) displays. You must type yes to proceed. You can also type no, in which case the installation is cancelled; or again to see the EULA again.
The following message displays:
Installation is done at <number>
6. Reboot by typing reboot. When prompted for build choice, do nothing; this brings up the
Media Flow Controller platform now on the local disk.
7. Log in: Use these login credentials:
User: admin
There is no default password.
8. To enter configuration mode, enter these commands:
enable configure terminal
9. Set the IP address, hostname, gateway, DNS server, and a domain list (to resolve unqualified hostnames). Install licenses, if you have the license keys.
interface eth0 ip address <management_port_IP_address> <netmask> hostname <hostname_for_machine> ip default-gateway <gateway_server_IP_address> ip name-server <DNS_server_IP_address> ip domain-list <domain_name_for_resolving_hostnames> ...
ntp server <NTP_server_IP_address> license install <license_key>
10. Save these settings through a reboot.
configuration write
11. As you have just changed the network information for your system, you must re-associate
Media Flow Controller with the interfaces. Either reboot (reload command) or enter this command:
service restart mod_delivery
12. Display the software version. If you have installed licenses, check those, too.
show version show license
13. 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, “Example Machine Setup of Management and
Traffic Ports,” on page 18 shows a typical Media Flow Controller configuration.
14. Sanity check: From another machine attempt to ping each address, and open an SSH session to the server as Admin.
You are now ready to begin configuring Juniper Networks Media Flow Controller. See the
Juniper Networks Media Flow Controller Administrator’s Guide and CLI Command Reference.
Installing Media Flow Controller Software from Network—PXE 31
CHAPTER 4 Installation with PXE Media Flow Controller / Media Flow Manager Installation Guide
Note!
Using keep-cache during installation cannot always preserve some or all of the caches.
Note!
If an unexpected interface is assigned eth0, your installed licenses will be invalid since they rely on the MAC address of an assigned interface and that interface changed. If that is the case, you need to manually assign the interfaces; see
“Assigning eth0 and eth1” on page 2-18
for details.
32 Installing Media Flow Controller Software from Network—PXE Copyright © 2010, Juniper Networks, Inc.
CHAPTER 5 Installation on a Hypervisor—Evaluation Deployments Only Media Flow Controller / Media Flow Manager
CHAPTER 5
Installation on a Hypervisor—Evaluation Deployments Only
This chapter provides information on Preparing Your Hypervisor ,
Controller Software—Virtual Machine
, and and configuring the needed network connections.
To obtain the Media Flow Controller VM install package, contact Juniper Networks Support;
see “Requesting Technical Support” on page 1-12 .
Important!
Before beginning, be sure to review “ Pre-Installation Planning” 16
for important information.
Preparing Your Hypervisor
VMware Server 2 by VMware™, is supported for Media Flow Controller evaluations; additional hypervisor servers may be usable, but have not been tested.
Important!
Juniper Networks does not support production deployments of Media Flow
Controller on hypervisors.
System Requirements—VM Installation
The following are required and/or recommended for Media Flow Controller optimal performance on a virtual machine.
Table 4 System Requirements—VM Installation
Element
Processor
RAM
Hard Disk
Virtual Device Node
Virtual Machine
Description
Two core minimum, four recommended
3GB minimum, 8GB recommended
32GB minimum
SCSII
64 bit required
Note!
By default, disk caches are disabled on VMware systems. Please contact Juniper
Networks Support ([email protected]) for assistance on enabling them.
Copyright © 2010, Juniper Networks, Inc.
Preparing Your Hypervisor 33
CHAPTER 5 Installation on a Hypervisor—Evaluation Deployments Only Media Flow Controller / Media Flow Manager
Installing Media Flow Controller Software—Virtual Machine
The principal difference in installation of Media Flow Controller on a virtual machine vs. on a real machine, is that you must use the VM console and set the boot device to boot appropriately.
1. Once you access the VM console, login as admin (no password), enter enable and then
configure terminal
to get the configuration prompt.
2. Enter reload, and be prepared to press the VM Bios hotkey for the boot menu (F2 on
Linux) if you have not already set the boot appropriately; the window for choosing the boot device is very small; if you miss it, you must issue reload again. If using PXE (network boot), you can also press the F12 key to force a PXE boot.
Note!
The shutdown initiated with the reload command can take several minutes. During this time, a login prompt displays. Do not log in to Media Flow Controller while reload is taking place.
3. Once the installation starts, it proceeds just like a regular installation for PXE, or an ISO image. If using an ISO image, there is the advantage of simply choosing the image and
installing it directly without the need to burn a CD or create a USB drive. See Chapter 3,
“Installation with CD-ROM or USB Drive”
or Chapter 4, “Installation with PXE”
for remaining installation instructions including how to specify the eth0 and eth1 interface selection, and basic Media Flow Controller setup instructions.
Tip!
At the VM Console, assign the eth0 IP address (interface eth0 ip address
<address><netmask>
) and then you can exit the VM Console and open a SSH session for the rest of the setup.
Important!
If you are installing for test purposes on a 32GB HD, then you must add the “32G” flag to the installation command, like this:
install-mfd 32g http://<host>/<path>/<filename>.img {init-cache | keep-cache}
34 Installing Media Flow Controller Software—Virtual Machine Copyright © 2010, Juniper Networks, Inc.
CHAPTER 6 Installing Media Flow Manager Media Flow Controller / Media Flow Manager Installation Guide
CHAPTER 6
Installing Media Flow Manager
Media Flow Manager is the tool that lets you remotely manage individual Media Flow
Controllers, group them into logical groups, create profiles (sets of commands) and apply them to nodes or groups, and take other actions. Media Flow Manager also provides features such as Service Locator, lets you direct requests to the closest Media Flow Controller;
Admission Control, lets you remotely set bandwidth parameters, and awStats Reports consolidator.
Figure 2 Media Flow Manager Interaction
Installing Media Flow Manager is very similar in procedure to installing Media Flow Controller.
All of the information in the previous chapters of this book apply, with the exception of the cache directives and ethernet naming guidelines (Media Flow Manager does not handle traffic, it is only a management device). If necessary, review this information:
•
“Accessing the Console Port” on page 2-16
, and “Upgrading and Rebooting” on page 2-20 .
•
Chapter 3, “Installation with CD-ROM or USB Drive"— “Creating CD-ROMs” on page 3-25
,
“Creating USB Images” on page 3-25
, and
“Troubleshooting” on page 3-28
.
•
Chapter 4, “Installation with PXE"— “Preparing Your PXE Server” on page 4-29 .
Copyright © 2010, Juniper Networks, Inc.
35
CHAPTER 6 Installing Media Flow Manager Media Flow Controller / Media Flow Manager Installation Guide
•
Chapter 5, “Installation on a Hypervisor—Evaluation Deployments Only"— “Preparing Your
Installing Media Flow Manager Software from Network—PXE
You must have a configured PXE server (see
“Preparing Your PXE Server” on page 4-29
) and the URL of the Juniper Networks Media Flow Manager software image in order to use this procedure. To obtain the Media Flow Manager install package, contact Juniper Networks
Support; see “Requesting Technical Support” on page 1-12 .
Before you begin: Plug your machine into a serial console, with flow control disabled, and configure your BIOS to PXE boot. Juniper Networks recommends connecting the console to the terminal server and opening a TELNET session for this procedure.
1. Access the console connected to the Media Flow Manager and login as admin (no password), enter enable and then configure terminal to get the configuration prompt.
2. Boot the machine (reload command) in PXE boot mode. Note the shutdown initiated with
reload
can take several minutes. During this time, a login prompt displays. Do not log in to
Media Flow Manager while reload is taking place
. If necessary, press the relevant function key at boot time to get to the boot menu and choose PXE; on Dell boxes, F11 takes you to the boot menu. When you get the PXE boot prompt, type in the label that you configured in the PXE server for the Media Flow Manager installation boot files (e.g. install-mfd).
Tip!
When it finishes booting, you will be at a # (configure) prompt unless you are on a serial console, where, instead, you will see a login prompt; in this case, enter root to bring you to the # prompt.
3. Type the following command to get the Juniper Networks Media Flow Manager image file installed.
install-mfc <URL_of_image_file>
4. The end-user license agreement (EULA) displays. You must type yes to proceed. You can also type no, in which case the installation is cancelled; or again to see the EULA again.
The following message displays:
Installation is done at <number>
5. Reboot by typing reboot. When prompted for build choice, do nothing; this brings up the
Media Flow Manager platform now on the local disk.
6. Log in: Use these login credentials:
User: admin
There is no default password.
7. To enter configuration mode, enter these commands:
enable configure terminal
8. Set the IP address, hostname, gateway, DNS server, and a domain list (to resolve unqualified hostnames). Install licenses, if you have the license keys.
interface eth0 ip address <management_port_IP_address> <netmask> hostname <hostname_for_machine> ip default-gateway <gateway_server_IP_address> ip name-server <DNS_server_IP_address> ip domain-list <domain_name_for_resolving_hostnames> ...
36 Installing Media Flow Manager Software from Network—PXE Copyright © 2010, Juniper Networks, Inc.
Media Flow Controller / Media Flow Manager Installation Guide CHAPTER 6 Installing Media Flow Manager
ntp server <NTP_server_IP_address> license install <license_key>
9. Save these settings through a reboot.
configuration write
10. Display the software version. If you have installed licenses, check those, too.
show version show license
11. Sanity check: From another machine attempt to ping each address, and open an SSH session to the server as Admin.
You are now ready to begin configuring Media Flow Manager. See the Juniper Networks
Media Flow Manager Administrator’s Guide and CLI Command Reference
.
Installing Media Flow Manager Software from Network—PXE 37
CHAPTER 6 Installing Media Flow Manager Media Flow Controller / Media Flow Manager Installation Guide
38 Installing Media Flow Manager Software from Network—PXE Copyright © 2010, Juniper Networks, Inc.
Herunterladen
Öffentlicher Link aktualisiert
Der öffentliche Link zu Ihrem Chat wurde aktualisiert. Sie können Ihre Chat-Links nach der Registrierung hier einsehen und verwalten.
Öffentlicher Dokumentenlink
Werbung