Juniper Ne tworks, the Juniper Networks logo, NetScreen, and ScreenOS are registered trademarks of Juniper Networks, Inc. in the
United States and other countries. JU NOS 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, m o d ify, transfer, or otherwise revise this publication without notice.
e or sold by Juniper Networks or components thereof might be covered by one or more of the following patents that are
censed 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,
,459,579, 6,493,347, 6,538,518, 6,538,899, 6,552,918, 6,567,902, 6,578,186, and 6,590,785.
n Borelli, Helen Shaw
Mann
n: John Borelli
: Edmonds Design
Revision History
15 December 2006—Revision 1
The information in this document is current as of the date listed in the revision history.
SOFTWARE LIC
The terms and conditions for using this software are described in the software license contained in the acknowledgment to your purchase order or, to the
extent applicable, to any reseller agreement or end-user purchase a greement executed between you and Juniper Networks. By using this software, you
indicate that you understand and agree to be bound by those terms and conditions.
Generally speaking, the software license restricts the manner in which you are permitted to use the software and may contain prohibitions against certain
uses. The software license may state conditions under which the license is automatically terminated. You should consult the license for further details.
For comple
ENSE
te product documentation, please see the Juniper Networks Web site at www.juniper.net/techpubs.
End User License Agreement
READ THIS END US
INSTALLING, O
OR IF YOU ARE NO
AGREEMENT. IF
SOFTWARE, AN
1. The Partie
originally p
2. The Softwa
releases of
Software” m
3. License G
non-exclus
a. Custome
Juniper or
b. Custome
has paid th
use such So
-Belted Radius software on multiple computers requires multiple licenses, regardless of wh ether such computers are physically contained on a
the Steel
assis.
single ch
c. Produc
r’s use of the Software. Such limits may restrict use to a maximum number of seats, registered endpoints, concurrent users, sessions, calls,
nalities, services, applications, operations, or capabilities, or provide throughput, performance, configuration, bandwidth, interface, processing,
functio
al, or geographical limits. In addition, such limits may restrict the use of the Software to managing certain kinds of networks or require the
tempor
re 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
Softwa
pplicable licenses.
of all a
ny trial copy of the Software, Customer’s right to use the Software expires 30 days after download, installation or use of the Software. Customer
d. For a
erate 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
may op
period by re-installing the Software after the 30-day trial period.
trial
ER LICENSE AGREEMENT (“AGREEMENT”) BEFORE DOWNLOADING, INSTALLING, OR USING THE SOFTWARE. BY DOWNLOADING,
R USING THE SOFTWARE OR OTHERWISE EXPRESSING YOUR AGREEMENT TO THE TERMS CONTAINED HEREIN, YOU (AS CUSTOMER
T THE CUSTOMER, AS A REPRESENTATIVE/AGENT AUTHORIZED TO BIND THE CUSTOMER) CONSENT TO BE BOUND BY THIS
YOU DO NOT OR CANNOT AGREE TO THE TERMS CONTAINED HEREIN, THEN (A) DO NOT DOWNLOAD, INSTALL, OR USE THE
D (B) YOU MAY CONTACT JUNIPER NETWORKS REGARDING LICENSE TERMS.
s. The parties to this Agreement are Juniper Networks, Inc. and its subsidiaries (collectively “Juniper”), and the person or organization that
urchased from Juniper or an authorized Juniper reseller the applicable license(s) for use o f the Software (“Customer”) (collectively, the “Parties”).
re. In this Agreement, “Software” means t he program modules and features of the Juniper or Juniper-supplied software, and updates and
such software, for which Customer has paid the applicable license or support fees to Juniper or an authorized Juniper reseller. “Embedded
eans Software which Juniper has embedded in the Juniper equipment.
rant. Subject to payment of the applicable fees and the limitations and restrictions set forth herein, Juniper grants to Customer a
ive and non-transferable license, without right to sublicense, to use the Software, in executable form only, subject to the following use restrictions:
r shall use the Embedded Software solely as embedded in, and for execution on, Juniper equipment originally purchased by Customer from
an authorized Juniper reseller.
r shall use the Software on a single hardware chassis having a single processing unit, or as m any chassis or processing units for which Customer
e applicable license fees; provided, however, with respect to the Steel-Belted Radius or Odyssey Access Client software only, Customer shall
ftware on a single computer containing a single physical random access memory space and containing any number of processors. Use of
t purchase documents, paper or electronic user documentation, and/or the particular licenses purchased by Customer may specify limits to
Global Enterprise Edition of the Steel-Belted Radius software may be used by Customer only to manage access to Customer’s enter pr ise network.
e. The
fically, service provider customers are expressly prohibited from using the Global Enterprise Edition of the Steel-Belted Radius software to support
Speci
ommercial network access services.
any c
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)fortheSoftwarefromJuniperoranauthorizedJuniperreseller.
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 So ftware on non-Juniper equipment; (j) use the Software (or make it available for use) on Juniper equipment thatthe
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 o ther 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.
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 o f 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 O F 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 neg ligence), 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 liabilityset
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. Term i nat ion . 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 w ith 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 n ame as if it were Juniper. In addition, certain third party software may be provided with the
Software and is subject to the accompanying li cense(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 wri tten (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 unl ess
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 t his 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)).
Table of Cont
ents
About This G
Objectives ............................................................................ xi
This preface provides the following guidelines for using the E-series™ Routing
Platforms ERX™ Hardware Guide:
Objectives on p a ge xi
ide
Objective
Audience on
E-series Routers on page xii
Documentation Conventions on page xii
List of Tech
Obtaining Documentation on page xvii
Documentation Feedback on page xvii
Requesting
page xi
nical Publications on page xiii
Support on page xviii
s
This guide p
An E-serie
a future release or reinstall the system software, see JUNOSe System BasicsConfiguration Guide, Chapter 3, Installing JUNOSe Software.
NOTE: If the
information in this guide, follow the JUNOSe Release Notes.
rovides the information you need to install and start the E-series router.
s router is shipped with the latest system software installed. To install
information in the latest JUNOSe Release Notes differs f rom the
Audience
This guide is intended for experienced system and network special ists working with
E-series routers in an Internet access environment.
Audiencexi
ERX 8.0.x Hardware Guide
E-series Routers
Five models of E-series routers are available:
ERX-1440 router
ERX-1410 router
ERX-710 router
ERX-705 router
ERX-310 router
All models use the same software.
In the E-series documentation, the term ERX-14xx models refers to both the
ERX-1440 rout
er and the ERX-1410 router. Similarly, the term ERX-7xx models
refers to both the ERX-710 router and the ERX-705 router. Other E-series router
designations refer to specific models.
Documentation Conventions
Table 1 defines the notice icons used in this guide.
Table 1: Notice Icons
IconMeaningDescription
Informational noteIndicates important features or
instructions.
Table 2: T
Table 2 def
conventions used primarily in the JUNOSe Command Reference Guide.Formore
information about command syntax, see the JUNOSe System Basics Configuration
Guide, Ch
ext and Syntax Conventions
Caution
Warning
ines text conventions used in this guide and the command syntax
apter 2, Command Line Interface.
Indicates a situation that might result in
loss of data or hardware damage.
Alertsyoutotheriskofpersonalinjury
or death.
ConventionDescriptionExamples
Text Conventions
xiiDocumentation Conventions
ConventionDescriptionExamples
Bold typefaceRepresents names of commands and
keywords in text.
Represents text that you m ust type.
Bold sans serif typeface
Fixed-width typeface
Italic typef
+ (plus sign) linking key namesIndicates that you must press two or
Syntax Conventions in the Command Reference Guide
Plain typefaceRepresents keywords.terminal length
Italic typeface
|(pipesymbol)
[ ] (square brackets)Enclose an optional choice of a single
[ ]* (square brackets and the asterisk)Enclose an optional choice of one or
{}(braces)
ace
Represents output on the terminal
screen.
Emphasizes words.
Identifies variables.
Identifies chapter, appendix,
and book names.
more keys simultaneously.
Represents variables.
Indicates a choice between the
keywords or variables on either side of
the symbol. (Specifying a choice can be
either optional or required.)
keyword or variable.
more keywords or variables.
Enclosearequiredchoiceofasingle
keyword or variable.
Issue the clock source
command.
Specify the keyword exp-msg.
host1(config)#traffic class low-loss1
host1#show ip community list
Community standard list 1
permit 0:100 0:200 0:300
There are two levels of access,
user and privileged .
clusterId , ipAddress.
Appendix A, System
Specifications.
Press Ctrl+b.
mask , accessListName
diagnostic | line
[ internal | external ]
[level1|level2|l1]*
{ permit | deny } { in | out }
{ clusterId | ipAddress }
About This Guide
List of Technical Publications
The E-series and JUNOSe documentation set consists of several hardware and
software guides, which are available in electronic and printed formats.
Table 3 lists and describes the E-series and JUNOSe document set. For a complete
list of abbreviations used in this document set, along with their spelled-out terms,
see JUNOSe System Basics Configuration Guide, Appendix A, Abbreviations andAcrony ms .
List of Technical Publicationsxiii
ERX 8.0.x Hardware Guide
Table 3: Juniper Networks E-series and JUNOSe Technical Publications
DocumentDescription
E-series Hardware Documentation
E320 Quick Start Guide
E320 Hardware Guide
Shipped in the box with all new E320 routers. Provides the basic
procedures to help you get an E320 router up and running quickly.
Provides the necessary procedures for getting the E320 router
operational
, including information about:
Installing the chassis a nd modules
Connecting cables
E320 Module Guide
E-series Installation Quick Start poster or ERX Quick
Start Guide
ERX Hardware Guide
Powering up t
Configuring the router for management access
Troubleshooting common issues
Describes sw
adapters (IOAs) available for the E320 router.
Provides detailed specifications for line modules and IOAs in E320
routers, and information about the compatibility of these modules
with JUNOSe software releases.
Lists the layer 2 protocols, layer 3 protocols, and applications that line
modules and their corresponding IOAs support.
Provides module LED information.
Shipped in the box with all new ERX routers. Provides the basic
procedures to help you get an ERX router up and running quickly.
Provides the necessary procedures for getting ERX-14xx models,
ERX-7xx models, and ERX-310 routers operational, including
information about:
itch route processor (SRP) modules, line modules, a nd I/O
Installing the chassis a nd modules
Connecting cables
Powering up the router
Configuring the router for management access
he router
ERX M odule Guide
xivList of Technical Publications
Troubleshooting common issues
Describes switch router processor (SRP) modules, line modules, and
I/O modules available for the ERX routers.
Provides detailed specifications for line modules and I/O modules
in ERX-14xx models, ERX-7xx models, and ERX-310 routers, and
informati
software releases.
Lists the l
modules and their corresponding I/O modules support.
Provides m
on about the compatibility of these modules with JUNOSe
ayer 2 protocols, layer 3 protocols, and applications that line
odule LED information.
DocumentDescription
ERX End-of-Life Module Guide
Provides an overview and description of ERX modules that are
end-of-life (EOL) and can no longer be ordered for the following routers:
ERX-7xx models
ERX-14xx models
ER-310 router
JUNOSe Software Guides
JUNOSe System Basics Configuration Guide
Provides information about:
About This Guide
JUNOSe Physical Layer Configuration Guide
JUNOSe Link Layer Configuration Guide
JUNOSe IP, IPv6, and IGP Configuration Guide
JUNOSe IP Services Configuration Guide
Planning and c
onfiguring your network
Using the command-line interface (CLI)
Installing JUNOSe software
Configuring t
he Simple Network Management Protocol (SNMP)
Managing the router and its modules, including the use of high
availability
(HA) for SRP redundancy
Configuring passwords and security
Configuring the router clock
Configuring v
irtual routers
Explains how to configure, test, and monitor physical layer interfaces.
Explains how to configure and monitor static and dynamic link layer
interfaces.
Explains how to configure and monitor IP, IPv6 and Neighbor
Discovery, and interior gateway protocols (RIP, OSPF, and IS-IS).
Explains how
to configure and monitor IP routing services. Topics
include:
Routing poli
cies
Firewalls
Network Address Translation (NAT)
J-Flow stati
stics
Bidirectional forwarding detection (BFD)
Internet Protocol Security (IPSec)
Digital cert
ificates
IP tunnels
Layer 2 services over GRE and over MPLS
Virtual Rout
er Redundancy Protocol (VRRP)
List of Technical Publicationsxv
ERX 8.0.x Hardware Guide
DocumentDescription
JUNOSe Multicast Routing Configuration Guide
JUNOSe BGP and MPLS Configuration Guide
JUNOSe Policy Management Configuration Guide
JUNOSe Quality of Service Configuration Guide
Explains how to configure and monitor IP multicast routing and IPv6
multicast routing. Topics include:
Explains how to configure and monitor Border Gateway Protocol (BGP)
routing, Multiprotocol Label Switching (MPLS), and related applications,
and configure
Explains how to configure, manage, and monitor customized policy
rules for packet classification, forwarding, filtering, and flow rates.
Also describes the packet mirroring feature, which uses secure policies.
Explains how to configure quality of service (QoS) features to queue,
schedule, and monitor traffic flow. These features include:
and monitor the Virtual Private LAN Service (VPLS).
JUNOSe Broadband Access Configuration Guide
JUNOSe System Event Logging Reference Guide
Traffic classes and traffic-class groups
Drop, queue, QoS, and scheduler profiles
QoS parameters
Statistics
Explains how to configure and monitor a remote access environment,
which can include the following features:
Authentication, authorization, and accounting (AAA)
Dynamic Host Configuration Protocol (DHCP)
Remote Authentication Dial-In User Service (RADIUS)
Terminal Access Controller Access Control System (TACACS+)
Layer 2 Tunneling Protocol (L2TP)
Subscriber management
Describes the JUNOSe system logging feature and describes how to use
the CLI to monitor your system’s log configuration and system events.
xviList of Technical Publications
DocumentDescription
JUNOSe Command Reference Guide
AtoM
JUNOSe Command Reference Guide N to Z
JUNOSe Comprehensive Index
Release Notes
JUNOSe Release Notes
Together c onstitute the JUNOSe Command Reference Guide.Contain
important information about commands implemented in the system
software. Use to look up:
Descriptions of commands and command parameters
Command syntax
A command’s related mode
Starting with JUNOSe Release 7.1.0, a history of when a
command, its keywords, and its variables were introduced
or added
Use with the JUNOSe configuration guides.
Provides a complete index of the JUNOSe software documentation set.
Provide the latest information about features, changes, known
problems, resolved problems, and system maximum values. If the
information in the Release Notes differs from the information found in
the documentation set, follow the Release Notes .
About This Guide
Obtaining Documentation
To obtain the most current version of all Juniper Networks technical documentation,
see the products documentation page on the Juniper Networks Web site at
http://www.juniper.net/.
To order printed copies of this guide and other Juniper Networks technical
documents, or to order a documentation CD, which contains th is guide, contact
your sales representative.
Copies of the Management Information Bases (MIBs) available in a software release
are included on the documentation CDs and at
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 com ments:
Release notes are included on the corresponding software CD and
are available on the Web.
http://www.juniper.net/.
Document name
Document part number
Documentation Feedbackxvii
ERX 8.0.x Hardware Guide
Requesting Suppor t
Page number
Software release version
For technical support, open a support case with the Case Manager link at
http://www.j
uniper.net/support/
or call 1-888-314-JTAC (from the United States,
Canada, or Mexico) or 1-408-745-9500 (from elsewhere).
xviiiRequesting Suppor t
Part 1
Product Overview
ERX Overview on p age 3
Product Overview1
2Product O ver view
Chapter 1
ERX Overview
This chapter provides introductory information about th e ERX routers. It contains
the following sections:
Overview on page 3
Overview
ERX Router
ERX Routers
ERX Modules on page 9
Network Management Tools on page 16
Redundancy
ERX routers are modular, carrier-class networking devices that deliver performance,
reliabilit
users. The ERX-7xx and ERX–14xx models offer high port density, low power
consumption, and fully redundant Internet access routing and edge a ggregation. The
ERX-310 ro
capabilities. ERX routers offer the complete edge solution for IP-optimized carriers.
y, and service differentiation to both business and consum er Internet
uter supports the same services, but with smaller capacity and scaling
on p a ge 3
Features on page 16
s
Five mode
ls of ERX routers are available:
ERX-1440
ERX-1410
router
router
ERX-710 r
ERX-705 r
ERX-310 r
All model
Combinat
outer
outer
outer
susethesamesoftware.However,the specific model determines the:
ion of line modules supported
ERX Routers3
ERX 8.0.x Hardware Guide
ERX-14xx Models
Conditions for line rate performance of line modules
Type, capacity, and number of SRP modules used
NOTE: In the E-s
eries documentation, the term ERX-14xx models refers to both
the ERX-1440 router and the ERX-1410 router. The terms ERX-1440 router and
ERX-1410 router refer to the specific models. See Figure 1 and Figure 2.
The ERX-1440 router manages an extremely high volume of network traffic,
and uses a 40-Gbps switch route processor (SRP) module, either the SRP-40 G or
SRP-40G+ modu
le. (The SRP-40G+ module obsoletes the SRP-40G module;
however, the software continues to support both modules.) In this model, all
line modules operate at full wire speed simultaneously.
The E RX-1410 router manages high levels of network traffic, and uses the
10-Gbps SRP m
odule (SRP-10G). You can configure the ERX-1410 router to
enable the line modules either to operateatfulllinerateperformanceorto
allow line modules to operate at a rate dependent on the resources available.
The former op
tion restricts the allowed combinations of line modules. For
information on configuring performanceoflinemodules,seeJUNOSe SystemBasics Configuration Guide, Chapter 6, Managing Modules.
NOTE: The 10-
Gbps SRP module used in the ERX-310 router is different from the
10-Gbps SRP module used in the ERX-1410 router. See “SR P Module” on page 10
for more information.
Externally, the ERX-1440 chassis is the same as the ERX-1410 chassis. (See Figure 1
and Figure 2
.) Both routers contain 14 vertical slots to accommodate modules.
4ERX R outer s
Internally
, the ERX-1440 chassis differs from the ERX-1410 chassis, and
includes a special midplane for the 40-Gbps SRP module.
Installation procedures and operating procedures are identical for both
systems. All ERX-7xx and ERX-14xx models use the same SRP I/O module,
but differ
ent power input modules are used .
NOTE: The router may look different from the routers shown in the figures in this
chapter, depending on the line modules in the slots.
Figure 1: ERX-14xx Models, Front View
Fan tray
behind bezel
Line module
SRP module
PCMCIA slot
ERX Over view
Air filter (optional)
behind bezel
Bezel
g013727
Cable
management
bracket
ERX Routers5
ERX 8.0.x Hardware Guide
Figure 2: ERX-14xx Models, Rear View
I/O
module
SRP I/O
module
Power input
module
Fan tray
ERX-7xx
Models
Cable
management
bracket
Plenum
g013728
NOTE: In the E-series documentation, the term ERX-7xx models refers to both the
ERX-705
router and the ERX-710 router. The terms ERX-705 router and ERX-710
router refer to the specific models. See Figure 3 and Figure 4.
The ERX-
7xx models are robust, high-density routers with less capacity
than the ERX-14xx models. The ERX-7xx models use either the
SRP-10G module or the SRP-5G module.
at full line rate performance or at a rate dependent on the resources available.
either
For information abo ut configurin g performance of line modules, see JUNOSeSystem Basics Configuration Guide, Chapter 6, M a na gin g Modules.
6ERX R outer s
NOTE: Th
e 10-Gbps SRP module used in the ERX-310 router is different from the
10-Gbps SRP module used in the ERX-710 router. See “SRP Module” on page 10
for more information.
ERX Over view
The ERX-705 chassis is the same as the ERX-710 chassis. (See Figure 3 and Figure 4.)
The chassis co
ntains seven slots to accom m odate modules. In stallation procedures
and operating procedures are identical for both systems. All ERX-7xx and ERX-14xx
models use the same SRP I/O module, but different power input modules are used.
NOTE: The rout
chapter, depending on the line modules in the slots.
Figure 3: ERX-7xx Models, Front View
Line module
Fan tray
SRP module
Figure 4: E
RX-7xx Models, Rear View
er may loo k different from the routers shown in the figures in this
PCMCIA slot
g013729
I/O
modules
Power input
module
Power switches
SRP I/O module
g013730
ERX Routers7
ERX 8.0.x Hardware Guide
ERX-310 Router
The ERX-310 router is a low-end platform that supports all of t he same services
as the ERX-7xx
and ERX-14xx models, but with smaller capacity and scaling
capabilities. Like the ERX-7xx and ERX-14xx models, the ERX-310 router
uses the s am e software architecture, providing a single IP entry point into
the network w
ith the same IP-based protocols and services that are available
on other ERX routers. The ERX-310 router is designed to be used as a small
distributed POP router as well as a high-end CPE router.
The ERX-310 router is a three-slot chassis with a midplane architecture. One slot
supports one
nonredundant 10-Gbps SRP module, while the other two slots support
line modules. The router supports existing E-series ASIC-based lin e modules (except
the OC48/STM16 line module), as well a s a select number of combination cards.
The combina
tion cards provide a fixed combination of interfaces on the I/O module
so that a single slot can suppo r t multiple interfaces (ATM OC3 and GE, for example).
NOTE: The 10-Gbps SRP module used in the ERX-310 router is different from
the 10-Gbps
SRP module used in the ERX-7xx and ERX-14xx models. See “SRP
Module” on page 10 for more information.
Figure 5: ER
The ERX-310
X-310 Router, Front View (AC Model)
Fan tray
NOTE: Th
router is available in either redundant AC- or DC-powered models.
SRP module
AC power
supply A
e DC model has blank filler panels in power supply slots.
Line modules
AC power
supply B
PCMCIA slot
g013731
8ERX R outer s
Figure 6: ERX-310 Router, Rear View (AC Model)
g013732
ERX Over view
I/O module
SRP I/O
module
ESD grounding jack
AC power inputs and
switches A and B
Grounding posts
Figure 7: E
ERX Mod
RX-310 Router, Rear View (DC Model)
g013733
ules
Each sy
use any line module for access or uplink . Access line modules receive traffic
from low-speed circuits, and the system routes the traffic onto higher-speed
uplin
stem supports an SRP mod ule and a se lection of line mod ules. You can
k line modules and then to the core of the network.
I/O
module
SRP I/O
module
ESD grounding jack
DC power inputs
and switches A and B
Grounding posts
Each m
oduleconnectstoacorrespondingI/Omoduleviaapassive
midplane. See Figure 8.
The front panel of each module contains a collection of status LEDs
(light-emitting diodes). For information about how to interpret the
see “Troubleshooting” on page 103.
LEDs,
ERX Modules9
ERX 8.0.x Hardware Guide
Figure 8: Modules in ERX-14xx Models
Line modules
SRP modules
Line modules
I/O modules
SRP I/O
module
I/O modules
Connection via
passive midplane
g013734
SRP Module
NOTE: So
me line modules require a minimum amount of memory to be used
with JUNOSe Release 5.3.0 or a higher-numbered release. See the ERX ModuleGuide for line module specifications.
Switch route processor (SRP) modules perform system management, routing
alculations and mainten an c e, forwarding table com pu tations, statistics
table c
processing, configuration storage, and other control plane functions. Each
SRP module is a PowerPC-based system with its own memory, no nvolatile
orage, and p ower supply. (See Figure 9 and Figure 10.)
disk st
10ERX M odules
Figure 9: SRP Module for ERX-7xx and ERX-14xx Models
Fabric board
Ejector
Status LEDs
ERX Over view
Midplane
connectors
Board reset
button
NMI button
PCMCIA
NVS card
System
processor board
g013735
ERX Modules11
ERX 8.0.x Hardware Guide
Figure 10: SRP Module for ERX-310 router
Ejector
Status
LEDs
g013736
Midplane
connectors
PCMCIA
NVS card
Board reset
button
NMI button
Integrated fabric system
processor board
Module Details
ERX-7xx and ERX-14xx models use up to two redundant SRP modules operating
in an ac
An SRP module must be present for any system to boot.
SRP modules ranging from 5 Gbps to 40 Gbps can be used in ERX-7xx and
ERX-14xx models. Only a 10-Gbps SRP module (SRP-SE10G) can be used in
ERX-3
NOTE: Because of different physical dimen s io ns and switch fabric capabilities, SRP
modules are not interchangeable between systems. For example, the 10-Gbps SRP
module
router, and vice versa.
tive/standby configuration. ERX-310 routers use o nly one SRP module.
10 routers. See the ERX Module Guide for complete information.
used in ERX-7xx and ERX-14xx models cannot be used in th e ERX-310
12ERX M odules
Loading...
+ 153 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.