Juniper Networks, the Juniper Networks logo, NetScreen, and ScreenOS are registered trademarks of Juniper Networks, Inc. in the United States and other
countries. JUNOS and JUNOSe are trademarks of Juniper Networks, Inc. All other trademarks, 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.
Products made or sold by Juniper Networks or components thereof might be covered by one or more of the following patents that are owned by or licensed
to Juniper Networks: U.S. Patent Nos. 5,473,599, 5,905,725, 5,909,440, 6,192,051, 6,333,650, 6,359,479, 6,406,312, 6,429,706, 6,459,579, 6,493,347,
6,538,518, 6,538,899, 6,552,918, 6,567,902, 6,578,186, and 6,590,785.
Writing: Elizabeth Gardner, Jerry Isaac
Editing: Stella Hackell
Illustration: Faith Bradford Brown
Cover Design: Edmonds Design
Revision History
20 March 2007— 530-017393-01 Revision 2. Corrected the input operating voltage range for DC power supplies and AC power supplies. Corrected clearance
requirements. Updated the mounting hardware installation procedure.
20 October 2006— 530-017393-01 Revision 1. Added European Community EMC Declaration of Conformity.
28 June 2006—530-014302-01, Revision 4. Added torque limits for securing cable lugs to the DC power supplies.
30 May 2006—530-014302-01, Revision 3. Corrected maximum aggregate throughput. Added AC power cord warning in Japanese. Added Lithium battery
statement.
13 April 2006—530-014302-01, Revision 2. Deleted notes that erroneously stated power supplies must be installed in specific slots. Clarified DC power
supply requirements for full system power redundancy. Updated JUNOS Release recommendation for graceful switchover.
14 September 2005—530-014302-01, Revision 1.
9 November 2004—530-011255-01, Revision 2.
18 March 2004—530-011255-01, Revision 1.
The information in this document is current as of the date listed in the revision history.
YEAR 2000 NOTICE
Juniper Networks hardware and software products are Year 2000 compliant. The JUNOS software has no known time-related limitations through the year
2038. However, the NTP application is known to have some difficulty in the year 2036.
ii■
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. The Parties. The parties to this Agreement are Juniper Networks, Inc. and its subsidiaries (collectively “Juniper”), and 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”).
2. The Software. In this Agreement, “Software” means the program modules and features of the Juniper or Juniper-supplied software, and updates and
releases of such software, for which Customer has paid the applicable license or support fees to Juniper or an authorized Juniper reseller. “Embedded
Software” means Software which Juniper has embedded in the Juniper equipment.
3. 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 the 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 software on multiple computers requires multiple licenses, regardless of whether such computers are physically contained on a single
chassis.
c. 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.
d. 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.
4. 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 the Embedded Software on non-Juniper equipment; (j) use the 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.
5. 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.
6. 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.
■iii
7. 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.
8. 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 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 for the Software are exclusive of taxes, withholdings, duties, or levies (collectively “Taxes”). Customer shall be responsible for
paying Taxes arising from the purchase of the license, or importation or use of the Software.
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., 1194
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)).
This preface provides the following guidelines for using the M10i Internet Router
Hardware Guide.
■Objectives on page xvii
■Audience on page xvii
■Documentation Conventions on page xviii
■List of Technical Publications on page xix
■Documentation Feedback on page xxiii
■Requesting Support on page xxiv
Objectives
This manual describes hardware installation and basic troubleshooting procedures
for the Juniper Networks M10i Internet Router. It explains how to prepare your site
for router installation, unpack and install the hardware, power on the router, perform
initial software configuration, and perform routine maintenance. After completing
the installation and basic configuration procedures covered in this manual, refer to
the JUNOS Internet software configuration guides for information about further JUNOS
software configuration.
Audience
NOTE: For additional information about Juniper Networks Internet routers and the
Physical Interface Cards (PICs) they support—either corrections to or information
that might have been omitted from this guide—see the hardware release notes at
http://www.juniper.net/.
This guide is designed for network administrators who are installing and maintaining
a Juniper Networks router or preparing a site for router installation. To use this guide,
you need a broad understanding of networks in general, the Internet in particular,
networking principles, and network configuration. Any detailed discussion of these
concepts is beyond the scope of this guide.
Objectives■xvii
M10i Internet Router Hardware Guide
Documentation Conventions
Table 1 on page xviii defines the notice icons used in this guide.
Table 1: Notice Icons
DescriptionMeaningIcon
Indicates important features or instructions.Informational note
Caution
Table 2 on page xviii defines the text and syntax conventions used in this guide.
Table 2: Text and Syntax Conventions
Bold sans serif typeface
Fixed-width typeface
Italic typeface
Indicates a situation that might result in loss of data or hardware
damage.
Alerts you to the risk of personal injury or death.Warning
Represents text that you type.
Represents output that appears on the
terminal screen.
Introduces important new terms.
■
Identifies book names.
■
Identifies RFC and Internet draft
■
titles.
ExamplesDescriptionConvention
To enter configuration mode, type the
configure command:
user@host> configure
user@host> show chassis alarms
No alarms currently active
A policy term is a named structure
■
that defines match conditions and
actions.
JUNOS System Basics Configuration
■
Guide
Italic sans serif typeface
xviii■Documentation Conventions
Represents variables (options for which
you substitute a value) in commands or
configuration statements.
RFC 1997, BGP Communities
■
Attribute
Configure the machine’s domain name:
[edit]
root@# set system domain-name
domain-name
Table 2: Text and Syntax Conventions (continued)
About This Guide
ExamplesDescriptionConvention
Sans serif typeface
| (pipe symbol)
# (pound sign)
[ ] (square brackets)
Indention and braces ( { } )
; (semicolon)
Represents names of configuration
statements, commands, files, and
directories; IP addresses; configuration
hierarchy levels; or labels on routing
platform components.
Enclose optional keywords or variables.< > (angle brackets)
Indicates a choice between the mutually
exclusive keywords or variables on either
side of the symbol. The set of choices is
often enclosed in parentheses for clarity.
Indicates a comment specified on the
same line as the configuration statement
to which it applies.
Enclose a variable for which you can
substitute one or more values.
Identify a level in the configuration
hierarchy.
Identifies a leaf statement at a
configuration hierarchy level.
To configure a stub area, include
■
the stub statement at the [edit
protocols ospf area area-id]
hierarchy level.
The console port is labeled
■
CONSOLE.
stub <default-metric metric>;
broadcast | multicast
(string1 | string2 | string3)
rsvp { # Required for dynamic MPLS only
community name members [
community-ids ]
[edit]
routing-options {
static {
route default {
nexthop address;
retain;
}
}
}
J-Web GUI Conventions
Bold typeface
> (bold right angle bracket)
List of Technical Publications
Table 3 on page xx lists the software and hardware guides and release notes for
Juniper Networks J-series, M-series, MX-series, and T-series routing platforms and
Represents J-Web graphical user
interface (GUI) items you click or select.
Separates levels in a hierarchy of J-Web
selections.
In the Logical Interfaces box, select
■
All Interfaces.
To cancel the configuration, click
■
Cancel.
In the configuration editor hierarchy,
select Protocols>Ospf.
List of Technical Publications■xix
M10i Internet Router Hardware Guide
describes the contents of each document. Table 4 on page xxiii lists the books included
in the Network Operations Guide series.
Table 3: Technical Documentation for Supported Routing Platforms
DescriptionBook
JUNOS Internet Software for Supported Routing Platforms
Class of Service
Provides an overview of the class-of-service (CoS) functions of the
JUNOS software and describes how to configure CoS features,
including configuring multiple forwarding classes for transmitting
packets, defining which packets are placed into each output queue,
scheduling the transmission service level for each queue, and
managing congestion through the random early detection (RED)
algorithm.
CLI User Guide
Feature Guide
MPLS Applications
Multicast Protocols
Network Interfaces
Network Management
Policy Framework
Routing Protocols
Secure Configuration Guide for Common Criteria
and JUNOS-FIPS
Describes how to use the JUNOS command-line interface (CLI) to
configure, monitor, and manage Juniper Networks routing
platforms. This material was formerly covered in the JUNOS SystemBasics Configuration Guide.
Provides a detailed explanation and configuration examples for
several of the most complex features in the JUNOS software.
Provides an overview of traffic engineering concepts and describes
how to configure traffic engineering protocols.
Provides an overview of multicast concepts and describes how to
configure multicast routing protocols.
Provides an overview of the network interface functions of the
JUNOS software and describes how to configure the network
interfaces on the routing platform.
Provides an overview of network management concepts and
describes how to configure various network management features,
such as SNMP and accounting options.
Provides an overview of policy concepts and describes how to
configure routing policy, firewall filters, and forwarding options.
Provides an overview of routing concepts and describes how to
configure routing, routing instances, and unicast routing protocols.
Provides an overview of secure Common Criteria and JUNOS-FIPS
protocols for the JUNOS Internet software and describes how to
install and configure secure Common Criteria and JUNOS-FIPS on
a routing platform.
Services Interfaces
Software Installation and Upgrade Guide
xx■List of Technical Publications
Provides an overview of the services interfaces functions of the
JUNOS software and describes how to configure the services
interfaces on the router.
Provides a description of JUNOS software components and
packaging, and includes detailed information about how to initially
configure, reinstall, and upgrade the JUNOS system software. This
material was formerly covered in the JUNOS System BasicsConfiguration Guide.
Table 3: Technical Documentation for Supported Routing Platforms (continued)
DescriptionBook
About This Guide
System Basics
VPNs
JUNOS References
Hierarchy and RFC Reference
Interfaces Command Reference
Routing Protocols and Policies Command
Reference
System Basics and Services Command Reference
Describes Juniper Networks routing platforms, and provides
information about how to configure basic system parameters,
supported protocols and software processes, authentication, and
a variety of utilities for managing your router on the network.
Provides an overview and describes how to configure Layer 2 and
Layer 3 virtual private networks (VPNs), virtual private LAN service
(VPLS), and Layer 2 circuits. Provides configuration examples.
Describes the JUNOS configuration mode commands. Provides a
hierarchy reference that displays each level of a configuration
hierarchy, and includes all possible configuration statements that
can be used at that level. This material was formerly covered in
the JUNOS System Basics Configuration Guide.
Describes the JUNOS software operational mode commands you
use to monitor and troubleshoot interfaces.
Describes the JUNOS software operational mode commands you
use to monitor and troubleshoot routing policies and protocols,
including firewall filters.
Describes the JUNOS software operational mode commands you
use to monitor and troubleshoot system basics, including
commands for real-time monitoring and route (or path) tracing,
system software management, and chassis management. Also
describes commands for monitoring and troubleshooting services
such as class of service (CoS), IP Security (IPSec), stateful firewalls,
flow collection, and flow monitoring.
System Log Messages Reference
J-Web User Guide
J-Web Interface User Guide
JUNOS API and Scripting Documentation
JUNOScript API Guide
JUNOS XML API Configuration Reference
JUNOS XML API Operational Reference
NETCONF API Guide
Describes how to access and interpret system log messages
generated by JUNOS software modules and provides a reference
page for each message.
Describes how to use the J-Web graphical user interface (GUI) to
configure, monitor, and manage Juniper Networks routing
platforms.
Describes how to use the JUNOScript application programming
interface (API) to monitor and configure Juniper Networks routing
platforms.
Provides reference pages for the configuration tag elements in the
JUNOS XML API.
Provides reference pages for the operational tag elements in the
JUNOS XML API.
Describes how to use the NETCONF API to monitor and configure
Juniper Networks routing platforms.
List of Technical Publications■xxi
M10i Internet Router Hardware Guide
Table 3: Technical Documentation for Supported Routing Platforms (continued)
DescriptionBook
JUNOS Configuration and Diagnostic Automation
Guide
Hardware Documentation
Hardware Guide
PIC Guide
JUNOScope Documentation
JUNOScope Software User Guide
J-series Routing Platform Documentation
Getting Started Guide
Describes how to use the commit script and self-diagnosis features
of the JUNOS software. This guide explains how to enforce custom
configuration rules defined in scripts, how to use commit script
macros to provide simplified aliases for frequently used
configuration statements, and how to configure diagnostic event
policies.
Describes how to install, maintain, and troubleshoot routing
platforms and components. Each platform has its own hardware
guide.
Describes the routing platform's Physical Interface Cards (PICs).
Each platform has its own PIC guide.
Describes the JUNOScope software graphical user interface (GUI),
how to install and administer the software, and how to use the
software to manage routing platform configuration files and monitor
routing platform operations.
Provides an overview, basic instructions, and specifications for
J-series routing platforms. The guide explains how to prepare your
site for installation, unpack and install the router and its
components, install licenses, and establish basic connectivity. Use
the Getting Started Guide for your router model.
Basic LAN and WAN Access Configuration Guide
Advanced WAN Access Configuration Guide
Administration Guide
Release Notes
JUNOS Release Notes
Hardware Release Notes
Explains how to configure the interfaces on J-series Services Routers
for basic IP routing with standard routing protocols, ISDN backup,
and digital subscriber line (DSL) connections.
Explains how to configure J-series Services Routers in virtual private
networks (VPNs) and multicast networks, configure data link
switching (DLSw) services, and apply routing techniques such as
policies, stateless and stateful firewall filters, IP Security (IPSec)
tunnels, and class-of-service (CoS) classification for safer, more
efficient routing.
Shows how to manage users and operations, monitor network
performance, upgrade software, and diagnose common problems
on J-series Services Routers.
Summarize new features and known problems for a particular
software release, provide corrections and updates to published
JUNOS, JUNOScript, and NETCONF manuals, provide information
that might have been omitted from the manuals, and describe
upgrade and downgrade procedures.
Describe the available documentation for the routing platform and
summarize known problems with the hardware and accompanying
software. Each platform has its own release notes.
xxii■List of Technical Publications
Table 3: Technical Documentation for Supported Routing Platforms (continued)
DescriptionBook
About This Guide
JUNOScope Release Notes
Contain corrections and updates to the published JUNOScope
manual, provide information that might have been omitted from
the manual, and describe upgrade and downgrade procedures.
J-series Services Router Release Notes
Briefly describe Services Router features, identify known hardware
problems, and provide upgrade and downgrade instructions
Table 4: JUNOS Internet Software Network Operations Guides
DescriptionBook
Baseline
Describes the most basic tasks for running a network using Juniper
Networks products. Tasks include upgrading and reinstalling JUNOS
software, gathering basic system management information,
verifying your network topology, and searching log messages.
Interfaces
Describes tasks for monitoring interfaces. Tasks include using
loopback testing and locating alarms.
MPLS
Describes tasks for configuring, monitoring, and troubleshooting
an example MPLS network. Tasks include verifying the correct
configuration of the MPLS and RSVP protocols, displaying the status
and statistics of MPLS running on all routing platforms in the
network, and using the layered MPLS troubleshooting model to
investigate problems with an MPLS network.
MPLS Log Reference
Describes MPLS status and error messages that appear in the output
of the show mpls lsp extensive command. The guide also describes
how and when to configure Constrained Shortest Path First (CSPF)
and RSVP trace options, and how to examine a CSPF or RSVP
failure in a sample network.
Hardware
Documentation Feedback
We encourage you to provide feedback, comments, and suggestions so that we can
improve the documentation. You can send your comments to
techpubs-comments@juniper.net, or fill out the documentation feedback form at
http://www.juniper.net/techpubs/docbug/docbugreport.html. If you are using e-mail, be
sure to include the following information with your comments:
■Document name
■Document part number
■Page number
■Software release version
Describes tasks for monitoring M-series and T-series routing
platforms.
Documentation Feedback■xxiii
M10i Internet Router Hardware Guide
Requesting Support
For technical support, open a support case with the Case Manager link at
http://www.juniper.net/support/ or call 1-888-314-JTAC (from the United States, Canada,
or Mexico) or 1-408-745-9500 (from elsewhere).
xxiv■Requesting Support
Part 1
Product Overview
■System Overview on page 3
■Hardware Component Overview on page 7
■JUNOS Internet Software Overview on page 25
■System Architecture Overview on page 33
Product Overview■1
M10i Internet Router Hardware Guide
2■Product Overview
Chapter 1
System Overview
This chapter provides an overview of the Juniper Networks M10i Internet router,
discussing the following topics:
■System Description on page 3
■Field-Replaceable Units (FRUs) on page 3
■System Redundancy on page 4
■Safety Requirements, Warnings, and Guidelines on page 5
System Description
The M10i Internet router provides high-speed interfaces for medium and large
networks and network applications, such as those supported by Internet service
providers (ISPs). Application-specific integrated circuits (ASICs), a definitive part of
the router design, enable the router to forward data at the high speeds demanded
by current network media.
The M10i router supports up to eight Physical Interface Cards (PICs). The router
height of 8.7 in. (22.1 cm) enables stacked installation of eight M10i routers in a
single floor-to-ceiling rack, for increased port density per unit of floor space.
The router's maximum aggregate throughput is 3.2 gigabits per second (Gbps) full
duplex per FPC (6.4 Gbps full-duplex total throughput rate). Inserting a combination
of PICs with an aggregate higher than the maximum throughput per FPC is supported,
but constitutes oversubscription of the FPC.
The router architecture cleanly separates control operations from packet forwarding
operations, which helps to eliminate processing and traffic bottlenecks. Control
operations in the router are performed by the Routing Engine, which runs JUNOS
Internet software to handle routing protocols, traffic engineering, policy, policing,
monitoring, and configuration management. Forwarding operations in the router
are performed by the Packet Forwarding Engine, which consists of hardware, including
ASICs, designed by Juniper Networks.
Field-Replaceable Units (FRUs)
Field-replaceable units (FRUs) are router components that can be replaced at the
customer site. Replacing most FRUs requires minimal router downtime. The router
uses the following types of FRUs:
System Description■3
M10i Internet Router Hardware Guide
■Hot-removable and hot-insertable FRUs—You can remove and replace these
■Hot-pluggable FRUs—You can remove and replace these components without
■FRUs that require powering off the router—You must power off the router before
Table 5 on page 4 lists the FRUs for the M10i router.
Table 5: Field-Replaceable Units
components without powering off the router or disrupting the routing functions.
powering off the router, but the routing functions of the system are interrupted
when the component is removed. If a component is acting as a backup, it can
be removed without affecting router functions.
removing these components.
Hot-Removable and
Hot-Insertable FRUs
Fan tray
Physical Interface Card
(PIC)
Power supply (AC or DC)
Small form-factor pluggable
(SFP)
For FRU replacement instructions, see “Replacing Hardware Components” on page 87.
System Redundancy
You can configure the router for system redundancy by using three AC or four DC
load-sharing, fully-redundant power supplies to distribute power to the other
components.
AC System Redundancy
AC system redundancy requires three independent AC power outlets. If one power
supply fails, the other two power supplies provide full power to the router's
components indefinitely.
FRUs that require
powering off the routerHot-Pluggable FRUs
NoneCompact Forwarding
Engine Board (CFEB)
High-Availability Chassis
Manager (HCM)
Routing Engine
4■System Redundancy
You can set up increased AC system redundancy by using four AC power supplies.
In this case, two power supplies are powered from two AC outlets, and the other two
power supplies use two AC outlets from a UPS battery-backed power source. This
lets the router run during AC power outages for the amount of time that the UPS
allows.
DC System Redundancy
DC system redundancy requires two power sources from feed A and two power
sources from feed B. If one feed fails or is shut down for service, the other feed
powers two DC power supplies and can provide full power to the router's components
indefinitely.
Safety Requirements, Warnings, and Guidelines
To avoid harm to yourself or the router as you install and maintain it, you need to
follow the guidelines for working with and near electrical equipment, as well as the
safety procedures for working with Internet routers. For a discussion of how to make
the installation site a safe environment, see “Preparing for Router
Installation” on page 41. For a list of safety warnings, see “Safety and Regulatory
Compliance Information” on page 135 and particularly “Electrical Safety Guidelines and
Warnings” on page 142. However, providing an exhaustive set of guidelines for working
with electrical equipment is beyond the scope of this manual.
Chapter 1: System Overview
Safety Requirements, Warnings, and Guidelines■5
M10i Internet Router Hardware Guide
6■Safety Requirements, Warnings, and Guidelines
Loading...
+ 210 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.