Juniper Networks, Inc.
1194 North Mathilda Avenue
Sunnyvale, California 94089
USA
408-745-2000
www.juniper.net
Juniper Networks, Junos, Steel-Belted Radius, NetScreen, and ScreenOS are registered trademarks of Juniper Networks, Inc. in the United
States and other countries. The Juniper Networks Logo, the Junos logo, 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.
E Series™ Broadband Services Routers ERX™ Hardware Guide, Release 11.3.x
Writing: John Borelli, Helen Shaw, Krupa Chandrashekar
Editing: Ben Mann
Illustration: John Borelli
Cover Design: Edmonds Design
Revision History
October 2010—FRS JunosE 11.3.x
The information in this document is current as of the date listed in the revision history.
SOFTWARE LICENSE
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 agreement 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 complete product documentation, please see the Juniper Networks Web site at www.juniper.net/techpubs.
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 YOUDO NOT OR CANNOTAGREE 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 (i) Juniper Networks, Inc. (if the Customer’s principal office is located in the Americas) or
Juniper Networks(Cayman)Limited (if theCustomer’s principalofficeislocated outside theAmericas) (suchapplicableentitybeing referred
to herein as“Juniper”), and (ii)the person or organizationthat originally purchased from Juniperor anauthorized 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, 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 oran authorized Juniper reseller. “Software” also includesupdates, 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.
3. License Grant. Subject to payment ofthe applicable fees and thelimitationsand restrictions setforth 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. Product purchase documents, paper or electronic user documentation, and/or the particular licenses purchased by Customer may
specify limitstoCustomer’suse of the Software. Such limits mayrestrict use toa maximum numberof seats, registeredendpoints, 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 anyform,to anythird party; (d) removeany proprietary notices,labels, or marks on orin anycopyof theSoftwareor anyproduct
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 thesecondhandmarket;(f) use any‘locked’ orkey-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 anythird party withoutthe prior writtenconsent of Juniper;or (l) use the Software inany 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, Customershall exercise all reasonable commercial efforts to maintain the Software and associated documentation in confidence,
which at a minimumincludes restricting access to the Software to Customer employees and contractors having a needto 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 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
statementthataccompaniesthe Software(the “Warranty Statement”). Nothing inthis Agreement shallgive rise toany obligationtosupport
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 ORPROCUREMENT OFSUBSTITUTE GOODSOR SERVICES,OR FORANY SPECIAL,INDIRECT, OR CONSEQUENTIALDAMAGES
ARISING OUTOF THIS AGREEMENT,THE SOFTWARE,OR ANY JUNIPEROR JUNIPER-SUPPLIED SOFTWARE. IN NOEVENT 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 observestrict obligationsof confidentiality with respect to such information and shalluse
such information in compliance with any applicable terms and conditions upon which Juniper makes such information available.
14. Third Party Software. Any licensor ofJuniper whose software is embedded in theSoftwareand any supplierof Juniper whoseproducts
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 licensoror vendor shallhave the right toenforcethis Agreement in its own name asif it were Juniper. In addition, certain thirdparty
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 confirmthat
this Agreement and all related documentation is and will be in the English language)).
If the information in the latest release notes differs from the information in the
documentation, follow the JunosE 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/.
Audience
This guide is intended for experienced system and network specialists working with
Juniper Networks E SeriesBroadbandServices Routersin anInternet access environment.
E Series and JunosE Text and Syntax Conventions
Table 1 on page xiv defines notice icons used in this documentation.
or variable to the left or to the right of this
symbol. (The keyword or variable can be
either optional or required.)
[ ]* (brackets and asterisk)
that can be entered more than once.
Represent required keywords or variables.{ } (braces)
Obtaining Documentation
To obtain the most current version of all Juniper Networks technical documentation, see
the Technical Documentation page on the Juniper Networks Web site at
http://www.juniper.net/.
To download complete sets of technical documentation to create your own
documentation CD-ROMs or DVD-ROMs, see the Portable Libraries page at
Copies of the Management Information Bases (MIBs) for a particular software release
are available for download in the software image bundle from the Juniper Networks Web
site athttp://www.juniper.net/.
Documentation Feedback
We encourage you to provide feedback, comments, and suggestions so that we can
improve the documentation to better meet your needs. Send your comments to
techpubs-comments@juniper.net, 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
Requesting Technical Support
Technical productsupport isavailable through theJuniper NetworksTechnical Assistance
Center (JTAC). If you are a customer with an active J-Care or JNASC support contract,
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 solutions and answer questions using our Knowledge Base: http://kb.juniper.net/
•
Download the latest versions of software and review release notes:
http://www.juniper.net/customers/csc/software/
•
Search technical bulletins for relevant hardware and software notifications:
https://www.juniper.net/alerts/
•
Join and participate in the Juniper Networks Community Forum:
http://www.juniper.net/company/communities/
•
Open a case online in the CSC Case Management tool: http://www.juniper.net/cm/
To verifyserviceentitlement by product serial number, use ourSerialNumber Entitlement
(SNE) Tool: 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 Management 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, see
This chapter provides introductory information about the ERX routers. It contains the
following sections:
•
Overview on page 3
•
ERX Routers on page 3
•
ERX Modules on page 9
•
Network Management Tools on page 13
•
Redundancy Features on page 14
Overview
ERX routers are modular, carrier-class networking devices that deliver performance,
reliability, and service differentiation to both business and consumer Internet users. The
ERX7xx and ERX14xx models offer high port density, low power consumption, and fully
redundant Internet access routing and edge aggregation. The Juniper Networks ERX310
Broadband Services Router supports the same services, but with smaller capacity and
scaling capabilities. ERX routers offer the complete edge solution for IP-optimized carriers.
NOTE: In the E Series documentation, the term ERX14xx models refers to
both the ERX1440 and ERX1410 routers. The terms ERX1440 and ERX1410
routers refer to the specific models. See Figure 1 on page 5 and Figure 2 on
page 5.
The ERX1440 router manages an extremely high volume of network traffic, and uses a
40-Gbps switch route processor (SRP) module, either the SRP-40G or SRP-40G+
module.(The SRP-40G+moduleobsoletesthe SRP-40G module;however, thesoftware
continues to support both modules.) In this model, all line modules operate at full wire
speed simultaneously.
The ERX1410 router manages high levels of network traffic, and uses the 10-Gbps SRP
module (SRP-10G). You can configure the ERX1410 router to enable the line modules
either to operate at full line rate performance or to allow line modules to operate at a
rate dependent on the resources available. The former option restricts the allowed
combinationsof linemodules.For information on configuringperformanceof linemodules,
see JunosE System Basics Configuration Guide, Chapter 6, Managing Modules.
NOTE: The 10-Gbps SRP module used in the ERX310 router is different from
the 10-Gbps SRP module used in the ERX1410 router. See “SRP Module” on
page 9 for more information.
Externally, the ERX1440 chassis is the same as the ERX1410 chassis. (See Figure 1 on
page 5 and Figure 2 on page 5.) Both routers contain 14 vertical slots to accommodate
modules.
Internally, the ERX1440 chassis differs from the ERX1410 chassis, and includes a special
midplane for the 40-Gbps SRP module.
Installation procedures and operating procedures are identical for both systems. All
ERX7xx and ERX14xx models use the same SRP I/O module, but different 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.
NOTE: In the E Series documentation,the term ERX7xx models refers to both
the ERX705 and ERX710 routers.The terms ERX705 and ERX710 routers refer
to the specific models. See Figure 3 on page 6 and Figure 4 on page 7.
The ERX7xx models are robust, high-density routers with less capacity than the ERX14xx
models. The ERX7xx models use either the SRP-10G module or the SRP-5G module.
You can configure the ERX7xx models to enable the line modules (LM) to operate either
at full line rate performance or at a rate dependent on the resources available. For
information about configuring performance of line modules, see JunosE System BasicsConfiguration Guide, Chapter 6, Managing Modules.
NOTE: The 10-Gbps SRP module used in the ERX310 router is different from
the 10-Gbps SRP module used in the ERX710 router. See “SRP Module” on
page 9 for more information.
The ERX705 chassis is the same as the ERX710 chassis. (See Figure 3 on page 6 and
Figure 4 on page 7.) The chassis contains seven slots to accommodate modules.
Installation procedures and operating procedures are identical for both systems. All
ERX7xx and ERX14xx models use the same SRP I/O module, but different 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.
The ERX310 router is a low-end platform that supports all of the same services as the
ERX7xx and ERX14xx models, but with smaller capacity and scaling capabilities. Like the
ERX7xx and ERX14xx models, the ERX310 router uses the same software architecture,
providing a single IP entry point into the network with the same IP-based protocols and
services that are available on other ERX routers. The ERX310 router is designed to be
used as a small distributed POP router as well as a high-end CPE router.
Chapter 1: ERX Overview
The ERX310 routeris athree-slot chassis witha midplane architecture.One slot supports
one nonredundant10-Gbps SRPmodule, while the other twoslots support line modules.
The router supportsexisting E Series ASIC-based line modules(except theOC48/STM16
line module), as well as a select number of combination cards. The combination cards
provide a fixed combination of interfaces on the I/O module so that a single slot can
support multiple interfaces (ATM OC3 and GE, for example).
NOTE: The 10-Gbps SRP module used in the ERX310 router is different from
the 10-Gbps SRP module used in the ERX7xx and ERX14xx models. See “SRP
Module” on page 9 for more information.
The ERX310 router is available in either redundant AC- or DC-powered models.
Each system supports an SRP module and a selection of line modules. You can use any
line module for access or uplink. Access line modules receive traffic from low-speed
circuits, and thesystem routes the traffic onto higher-speed uplinkline modules andthen
to the core of the network.
Each module connects to a correspondingI/O module via a passive midplane. See Figure
8 on page 9.
The front panel of each module contains a collection of status LEDs (light-emitting
diodes). For information about how to interpret the LEDs, see “Troubleshooting” on
page 95.
Figure 8: Modules in ERX14xx Models
SRP Module
Switch route processor (SRP) modules perform system management, routing table
calculations and maintenance, forwarding table computations, statistics processing,
configuration storage, and other control plane functions. Each SRP module is a
NOTE: Some line modules require a minimum amount of memory to be used
with JunosE Release5.3.0or a higher-numbered release. See the ERX ModuleGuide for line module specifications.
ERX7xx and ERX14xx models use up to two redundant SRP modules operating in an
active/standby configuration. ERX310 router use only one SRP module. An SRP module
must be present for any system to boot.
SRP modules ranging from 5 Gbps to 40 Gbps can be used in ERX7xx and ERX14xx
models. Only a 10-Gbps SRP module (SRP-SE10G) can be used in ERX310 router. See
the ERX Module Guide for complete information.
NOTE: Because of different physical dimensions and switch fabric capabilities,
SRP modules are not interchangeable between systems. For example, the
10-Gbps SRP module used in ERX7xx and ERX14xx models cannot be used
in the ERX310 router, and vice versa.
CAUTION: Do not remove the SRP module while the system is running.
NOTE: SomeSRP modules require a minimum amount of memory to be used
with JunosE Release5.3.0or a higher-numbered release. See the ERX Module
Guide for module specifications.
For details about installing SRP modules, see “Installing Modules” on page 31.
SRP Module Redundancy
SRP module redundancy is available only for ERX7xx and ERX14xx models. See
“Redundancy Features” on page 14
Nonvolatile Storage
The PCMCIA slot on the front of the SRP module holds a Type II PCMCIA nonvolatile
storage (NVS) card. (See Figure 9 on page 10 and Figure 10 on page 11.) This card is
loaded with the system's software and configuration files. The PCMCIA card is factory
installed.
CAUTION: Although you can remove PCMCIA NVS (Flash) cards from a
running router, we recommend that you do not do so. If you remove the card
while data is being written to or copied from the NVS card, data can be lost
or corrupted. Therefore, we strongly recommend that you shut down the
router before removing a PCMCIA NVS card.
SRP I/O Module
The SRP I/O module is a single corresponding input/output module that interfaces with
the SRP modules through the system's midplane. The same SRP I/O module works with
all SRP modules, but is router specific. The I/O module used in ERX7xx and ERX14xx
models cannot be used in the ERX310 router, and vice versa. See Figure 2 on page 5,
Figure 4 on page 7, and Figure 6 on page 8 for locations.
Module Details
The SRP I/O module provides standard craft management interfaces, including:
•
10/100Base-T—The port enables access to the ERX router for Ethernet management
functions via CLI or SNMP, for example.
•
RS-232—The port provides a serial connection for monitoring the system's hardware
configuration through a PC (running terminal emulation software) or ASCII terminal.
Allows direct CLI access.
•
Alarm contacts—The contacts provide for remote indication of critical, major, and
minor router alarms (ERX7xx and ERX14xx models only; currently not implemented)
•
External timing inputs—The inputs provide a method of ensuring that the clock timing
used by the router remains synchronized with the network's system clock. BNC
connectors and wire wraps are available for ERX7xx and ERX14xx models only.
For details about installing the SRP I/O module, see “Installing Modules” on page 31.
Line Modules
Line modules (LM) process data from different types of network connections. For
information about available line modules and which SRP modules support specific line
modules, see the ERX Module Guide.
Figure 11 on page 13 shows a representative line module. For details about installing line
modules, see “Installing Modules” on page 31.
Figure 11: Representative Line Module
Packet Classification
Most linemodules support packetclassification on ingress;some non-ASICline modules
do not. A classification engine on theline modulematches specific fields (such as source
and destination IP address, source and destination port, and protocol), the ingress IP
interface, layer 2 fields, or some combination of these against user-configured filters at
wire speed.
I/O Modules
Most line modules have a corresponding input/output (I/O) module that provides the
physical interconnection to the network. Insert each I/O module into the back of the
system, directly behind its corresponding line module.
For information about which line modules pair with which I/O modules, see the ERXModule Guide. See Figure 2 on page 5, Figure 4 on page 7, and Figure 6 on page 8 for
locations. For details about installing I/O modules, see “Installing Modules” on page 31.
Network Management Tools
You can use different management tools to configure the system to meet the specific
networking requirements.
The CLI provides fully developed and automated configuration and status functionality
through a localRS-232 port, Telnet, orSSH via any reachablenetwork. For a full discussion
of the CLI, see JunosE System Basics Configuration Guide, Chapter 2, Command-LineInterface.
SNMP MIB Management
The system offers a complete SNMP interface for configuration, status, and alarm
reporting. The system supports both Standard and Enterprise MIBs (Management
Information Bases). The Juniper Networks E Series Enterprise MIB is ASN.1 notated for
easy importing into third-party SNMP management applications. For more information,
see JunosE System Basics Configuration Guide, Chapter 4, Configuring SNMP.
NMC-RX Device Management System
The NMC-RX application provides a global methodof managing allrouters,line modules,
and ports through a graphical user interface.
Redundancy Features
This section describes system redundancy features.
SRP Modules
ERX7xx and ERX14xx models use a 1:1 redundancy scheme for the SRP module. When
two SRP modules of the same type are installed in the chassis, one acts as a primary
(active) and the second as a redundant (standby) module. Both SRP modules share a
single SRP I/O module located in the rear of the chassis.
If the standby SRP module detects that the primary SRP module is not active (and
high-availability mode is not enabled), it reboots the system and takes control. If
high-availability mode has been enabled, automatic switchover occurs with near hitless
failover. If you upgrade software, you must copy the software to the redundant SRP and
reboot it. For information about configuring and managing SRP module redundancy, see
JunosE System Basics Configuration Guide, Chapter 6, Managing Modules.
After you install two SRP modules, the modules negotiate for the primary role.A number
of factors determine which module becomes the primary; however, preference is given
to the module in the lower-numbered slot. The SRP modules record their latest roles
and retain them the next time you switch on the system. For information about installing
SRP modules, see “Installing Modules” on page 31.
NOTE: This section applies to ERX7xx and ERX14xx models only. ERX310
routers contain one SRP module and therefore do not offer SRP module
redundancy.