Juniper E SERIES BROADBAND SERVICES ROUTERS 11.3.X - E120 AND E320 HARDWARE GUIDE REV 9-29-2010, E120, E320 Hardware Manual

E Series™ Broadband Services Routers

E120 and E320 Hardware Guide

Release

11.3.x

Published: 2010-09-29

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 E120 and E320 Hardware Guide, Release 11.3.x

Writing: Subash Babu Asokan, John Borelli, Krupa Chandrashekar Editing: Benjamin Mann, Alana Calapai 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.

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 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)).

Table of Contents

About the Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii

E Series and JunosE Documentation and Release Notes . . . . . . . . . . . . . . . . . . . . xiii

Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii

E Series and JunosE Text and Syntax Conventions . . . . . . . . . . . . . . . . . . . . . . . . . xiii

Obtaining Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv

Documentation Feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv

Requesting Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv

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

Opening a Case with JTAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvi

Part 1 Product Overview

Chapter 1 E120 and E320 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

System Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Chassis Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

E320 Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

E120 Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

E120 and E320 Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

SRP Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Module Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Nonvolatile Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

SFM Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Fabric Slices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

SRP IOA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Module Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Line Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Packet Classification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

I/O Adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Network Management Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

CLI Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

SNMP MIB Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Redundancy Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

SRP Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

NVS Cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Fans . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

E120 and E320 11.3.x Hardware Guide

Part 2 Initial Installation

Chapter 2 Unpacking and Inspecting the Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Chapter 3 Installing the Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Chapter 4 Installing Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Chapter 5 Cabling the Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Unpacking the Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Inspecting Router Components and Accessories . . . . . . . . . . . . . . . . . . . . . . . . . . 18

If You Detect or Suspect Damage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Contacting Juniper Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

The Next Step . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Freestanding Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Rack-Mounted Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Installation Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Preparing the Equipment Racks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Installing the Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

The Next Step . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Slot Numbering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

IOA Slot Combinations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Module Combinations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

IOAs Requiring SFPs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Proper Handling of ES2 4G LMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

ES2 10G Uplink Line Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Managing Modules Using the Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Order of Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Hot-Swapping Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Protecting Modules and Slots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Required Tools and Safety Items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Safety Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Installing an SRP Module or SFM Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Installing an IOA Shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Installing a Line Module or an IOA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Removing Modules and IOAs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Installing and Removing SFPs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Installing SFPs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Removing SFPs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

The Next Step . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Cabling Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Required Tools, Wires, and Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Cabling the SRP IOA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Network Timing Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Management Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Connecting to the Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Connecting to a Console Terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Table of Contents

Cabling IOAs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

LC Duplex Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

SFPs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Cabling the Router for Power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Task 1: Turn Off All Router Power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Task 2: Connect the Grounding Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Task 3: Connect the Power Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

The Next Step . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Chapter 6 Powering Up the Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Before You Power Up the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Powering Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Initialization Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Status LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Powering Down . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

The Next Step . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Chapter 7 Accessing E Series Routers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Setting Up Management Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Console Port Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Using HyperTerminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Connecting Directly to the Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Assigning an IP Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Telnet Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

SNMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

The Next Step . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Part 3 Hardware Maintenance, Replacement, and Troubleshooting

Procedures

Chapter 8 Maintaining the Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Required Tools and Items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Storing Modules and Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Cleaning the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Upgrading NVS Cards on SRP Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Upgrading a System That Contains One SRP Module . . . . . . . . . . . . . . . . . . 69

Upgrading a System That Contains Two SRP Modules . . . . . . . . . . . . . . . . . 69

Replacing an NVS Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Replacing Fan Trays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Removing an E320 Fan Tray . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Installing an E320 Fan Tray . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Installing an Air Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Replacing a Power Distribution Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Chapter 9 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Diagnosing Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Initialization Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Troubleshooting Power Failures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

E120 and E320 11.3.x Hardware Guide

Part 4 Appendixes

Appendix A System Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

Appendix B Installation Guidelines and Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Appendix C Cable Pinouts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

Appendix D Contacting Customer Support and Returning Hardware . . . . . . . . . . . . . . . . 111

Understanding Status LEDs to Troubleshoot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

LED Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

LED Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Monitoring Temperatures of Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Resetting Line Modules and SRP Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Double-Bit Errors on SRP Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Detecting Double-Bit Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Fixing Double-Bit Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

E120 Broadband Services Router Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . 89

E320 Broadband Services Router Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Router Power Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Your Preinstallation Responsibilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Environmental Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Regulatory Compliances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Safety Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Equipment Rack Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Mechanical Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Space Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

Proper Rack Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

Cabling Recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Product Reclamation and Recycling Program . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

Hardware Compliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Federal Communications Commission (FCC) Statement . . . . . . . . . . . . . . . 101

FCC Requirements for Consumer Products . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Food and Drug Administration, Center for Devices and Radiological

Health . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

Canadian Department of Communications Radio Interference

Regulations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

Réglement sur le brouillage radioélectrique du ministère des

communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

Industry Canada Notice CS-03 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

Avis CS-03 d'Industrie Canada . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

D.O.C. Explanatory Notes: Equipment Attachment Limitations . . . . . . . . . . 103

Notes explicatives du ministère des Communications: limites visant les

accessoires . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

EC Declaration of Conformity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

Voluntary Control Council for Interference (VCCI) Statement for Japan . . . 105

SRP IOA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

Contacting Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

Return Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

Table of Contents

Locating Component Serial Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

Information You Might Need to Supply to JTAC . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

Tools and Parts Required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

Returning Products for Repair or Replacement . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

Packing Instructions for Returning a Chassis . . . . . . . . . . . . . . . . . . . . . . . . . 114

Appendix E Declaration of Conformity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

Declaration of Conformity – E120 Broadband Services Router . . . . . . . . . . . . . . . 117

Declaration of Conformity – E320 Broadband Services Router . . . . . . . . . . . . . . . 117

Part 5 Index

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

E120 and E320 11.3.x Hardware Guide

About the Documentation

•

E Series and JunosE Documentation and Release Notes on page xiii

•

Audience on page xiii

•

E Series and JunosE Text and Syntax Conventions on page xiii

•

Obtaining Documentation on page xv

•

Documentation Feedback on page xv

•

Requesting Technical Support on page xv

E Series and JunosE Documentation and Release Notes

For a list of related JunosE documentation, see

http://www.juniper.net/techpubs/software/index.html .

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.

E120 and E320 11.3.x Hardware Guide

Table 1: Notice Icons

Table 2 on page xiv defines text and syntax conventions that we use throughout the E Series and JunosE documentation.

DescriptionMeaningIcon

Indicates important features or instructions.Informational note

Indicates a situation that might result in loss of data or hardware damage.Caution

Alerts you to the risk of personal injury or death.Warning

Alerts you to the risk of personal injury from a laser.Laser warning

Table 2: Text and Syntax Conventions

Representscommandsand keywords intext.Bold text like this

Fixed-width text like this

Italic text like this

Plus sign (+) linking key names

Syntax Conventions in the Command Reference Guide

Representsinformationasdisplayedon your terminal’s screen.

•

Emphasizes words.

•

Identifies variables.

•

Identifies chapter, appendix, and book names.

keys simultaneously.

ExamplesDescriptionConvention

•

Issue the clock source command.

•

Specify the keyword exp-msg.

host1(config)#traffic class low-loss1Represents text that the user must type.Bold text like this

host1#show ip ospf 2

Routing Process OSPF 2 with Router ID 5.5.0.250

Router is an Area Border Router (ABR)

•

There are two levels of access: user and privileged.

•

clusterId, ipAddress.

•

Appendix A, System Specifications

Press Ctrl + b.Indicates that you must press two or more

terminal lengthRepresents keywords.Plain text like this

mask, accessListNameRepresents variables.Italic text like this

Table 2: Text and Syntax Conventions (continued)

About the Documentation

ExamplesDescriptionConvention

| (pipe symbol)

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

http://www.juniper.net/techpubs/resources/index.html

diagnostic | lineRepresents a choice to select one keyword

[ internal | external ]Represent optional keywords or variables.[ ] (brackets)

[ level1 | level2 | l1 ]*Represent optional keywords or variables

{ permit | deny } { in | out }

{ clusterId | ipAddress }

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,

E120 and E320 11.3.x Hardware Guide

or are covered under warranty, and need post-sales technical support, you can access our tools and resources online or open a case with JTAC.

•

JTAC policies—For a complete understanding of our JTAC procedures and policies, review the JTAC User Guide located at

http://www.juniper.net/us/en/local/pdf/resource-guides/7100059-en.pdf .

•

Product warranties—For product warranty information, visit

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

•

JTAC hours of operation—The JTAC centers have resources available 24 hours a day, 7 days a week, 365 days a year.

Self-Help Online Tools and Resources

For quick and easy problem resolution, Juniper Networks has designed an online self-service portal called the Customer Support Center (CSC) that provides you with the following features:

•

Find CSC offerings: http://www.juniper.net/customers/support/

•

Search for known bugs: http://www2.juniper.net/kb/

•

Find product documentation: http://www.juniper.net/techpubs/

•

Find solutions and answer questions using our Knowledge Base: http://kb.juniper.net/

•

Download the latest versions of software and review release notes:

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

•

Search technical bulletins for relevant hardware and software notifications:

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

•

Join and participate in the Juniper Networks Community Forum:

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

•

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

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

PART 1

Product Overview

•

E120 and E320 Overview on page 3

E120 and E320 11.3.x Hardware Guide

CHAPTER 1

E120 and E320 Overview

This chapter provides introductory information about the Juniper Networks E120 and E320 Broadband Services Routers. It contains the following sections:

•

System Description on page 3

•

Chassis Overview on page 3

•

E120 and E320 Modules on page 7

•

Network Management Tools on page 12

•

Redundancy Features on page 13

System Description

E Series routers are modular, carrier-class networking devices that deliver performance, reliability, and service differentiation to both enterprise and residential Internet users. The E120 router and E320 router are next-generation, high-capacity additions to the E Series productfamilyofferinghigh-port density andhighbandwidth inafully redundant system, supporting evolving IP-based broadband services. The E120 router supports the same services as the E320 router, but with smaller capacity and scaling capabilities for smaller configurations.

The routers utilize the same JunosE™ Software architecture and provide a single IPentry point into the service provider network with the same IP-based protocols and services that are available on existing E Series products. They address a wide range of edge applications, including subscriber management (including 802.11 hotspots), video on demand, Voiceover IP (VoIP), Metro Ethernet, customercircuitaggregation,virtual private networks (VPNs), and wholesale services.

E Series routers offer the complete edge solution for IP-optimized carriers.

Chassis Overview

Two models are available:

•

E120 router

•

E320 router

E120 and E320 11.3.x Hardware Guide

Both models use the same software and share a system architecture and common components:

•

Switch route processors (SRPs)—Perform system management, routing table calculations maintenance, forwarding table computations, and other control plane functions

•

Switch fabric modules (SFMs)—Create a distributed shared memory switching fabric

•

Line modules (LMs)—Are frame processing and forwarding engines for IOAs

•

Input/output adapter (IOA)—Provide the physical connection to the network via 10–Gigabit Ethernet, Ethernet, ATM, and Packet over SONET (PoS) interfaces

•

Power modules—Distribute redundant power feeds through the system to all components

E320 Model

A fully configured E320 router consists of 2 switch route processors (SRPs), 3 switch fabric modules (SFMs), 12 line modules, and up to 2 I/O adapters (IOAs) per line module. See Figure 1 on page 5 and Figure 2 on page 5.

An IOA shelf (bracket) can be installed on a slot-by-slot basis to create an upper IOA bay and lower IOA bay, enabling you to use up to two IOAs in the same slot. This architecture enables you to combine different IOA types in the same slot and to support oversubscribed configurations.

NOTE: The routers illustrated in this book might look different than your

router due to configuration variations.

Figure 1: E320 Router, Front View

Chapter 1: E120 and E320 Overview

Figure 2: E320 Router, Rear View

E120 and E320 11.3.x Hardware Guide

E120 Model

A fully configured E120 router consists of 2 switch route processors (SRPs), 3 switch fabric modules (SFMs), 6 line modules, and up to 2 I/O adapters (IOAs) per line module. See Figure 3 on page 6 and Figure 4 on page 6.

An IOA shelf (bracket) can be installed on a slot-by-slot basis to create a left and right IOA bay, enabling you to use up to two IOAs in the same slot. This architecture enables you to combine different IOA types in the same slot and to support oversubscribed configurations.Air is pulled in from the right of the router by the fan tray and is exhausted out the left side.

Figure 3: E120 Router, Front View

NOTE: The routers illustrated in this book might look different than your router due to configuration variations.

Figure 4: E120 Router, Rear View

E120 and E320 Modules

The routers support SRP modules, SFM modules, line modules, and IOAs. You can use a 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 thecore ofthe network. Line modules act asframe forwarding engines for the physical interfaces (the IOAs) via a passive midplane.

Most line modules, IOAs, SFMs, and SRP modules can be installed in either router. There are a few exceptions, however:

•

Similar-capacity modules must be used in the same router. For example, you cannot install an SRP-100 in a router that contains an SFM-320. You can only use a SRP–100 module with a SFM-100 module.

•

Higher-capacitySRP modules can beused in lower-capacityrouters,but lower-capacity SRP modules cannot be used in high-capacity routers. For example, an SRP-320 can be used in an E120 router, but an SRP-120 cannot be used in an E320 router.

Chapter 1: E120 and E320 Overview

SRP Module

•

The SRP-100 module and the SFM-100 module are not supported in the E120 router.

See the E120 and E320 Module Guide for module and chassis compatibility.

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 77. For complete module specifications, see the E120 and E320 Module Guide.

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. The SRP module identifies which line modules are physically present in the chassis and monitors and controls vital functions on the line modules.

Each SRPmodule(Figure 5 on page 8)is aPowerPC-based system with itsown memory, nonvolatile storage (NVS), and power converter. The SRP module works with the SFM modules and contains aswitch fabric slice common to both modules. See “Fabric Slices” on page 9 for more information.

NOTE: Because of different physical dimensions and switch fabric capabilities,

SRP modules are not interchangeable between all routers. For example, the SRP–100 used in the E320 router cannot be used in other E Series routers, and vice versa. See the E120 and E320 Module Guide for SRP module compatibility.

E120 and E320 11.3.x Hardware Guide

Figure 5: Representative SRP Module

Module Details

An SRP module must be present for the router to boot. The routers support up to two redundant SRP modules operating in an active/standby configuration. The redundant SRP module takes control when a failoveroccurs. See “Redundancy Features”on page 13 and the E120 and E320 Module Guide for more SRP module information.

CAUTION: Do not remove the SRP module while the system is running, unless

you have properly issued the halt command. See JunosE System Basics Configuration Guide, Chapter 6, Managing Modules for information about the

halt commands.

NOTE: You cannot use SRP modules of different capacities in the same configuration. For example, you cannot install a SRP-100 module and a SRP-320 module in the same router.

For details about installing SRP modules, see “Installing Modules” on page 25.

Nonvolatile Storage

Depending on the model, each SRP module has either two Type II PCMCIA nonvolatile storage (NVS) cards or two ATA flash cards (0, 1). (See Figure 5 on page 8.) One card is loaded with the system's software and configuration files while the other card holds core dumps. The NVS cards in the active SRP module are designated disk0 and disk1. The NVS cards in the redundant SRP module are designated standby-disk0 and standby-disk1. The PCMCIA card is factory installed.

CAUTION: Before you insert or remove flash cards from a running router, we strongly recommend that you halt the SRP module or shut down the router.

SFM Module

Chapter 1: E120 and E320 Overview

Failure to do this can result in file corruption in one or both cards. See “Replacing an NVS Card” on page 70 for more information.

The switch fabric modules (SFMs) workwith theSRP module to create ashared memory fabric for the router. Each SFM module (Figure 6 on page 9) has its own memory and powerconverter. Likethe SRPmodule,the SFMmodulecontains a fabricsystemprocessor board (slice). See “Fabric Slices” on page 9.

NOTE: You must use a SRP module that corresponds with the fabric type

(SFM module) that is installed. For example, you can only use a SRP–100 module with a SFM-100 module. You cannot use a SRP–100 module with a SFM-320 module.

Figure 6: SFM Module

Fabric Slices

The router's switch fabric is distributed acrosstwo SRP modulesand three SFMmodules. Each module has a fabric slice on it. For the router to operate, at least four of the five slices must be operational.

When allfive modules are installed,the fabric slice ofthe standby SRPactsas aredundant module. For example, the router can operate with:

•

Two SRP modules (the second of which is redundant) and three SFM modules

•

One SRP module (non-redundant) and three SFM modules

•

Two SRP modules and two SFM modules

NOTE: You cannot use SFM modules of different capacities in the same

configuration. For example, you cannot install a SFM-100 module and a SFM-320 module in the same router.

E120 and E320 11.3.x Hardware Guide

SRP IOA

The SRP I/O adapter (IOA) is a single input/output adapter that interfaces with the SRP modules through the system's midplane. See Figure 2 on page 5 and Figure 4 on page 6 for its location.

Module Details

The SRP IOA provides standard management interfaces, including:

•

10/100Base-T—The port enables access to the router for Ethernet management functions through Telnet, Secure Shell Server (SSH), command-line interface (CLI), or Simple Network Management Protocol (SNMP), for example.

•

RS-232—One port (console) provides a serial connection for monitoring the system's hardware configuration through a PC (running terminal emulation software) or ASCII terminal and enables direct CLI access. The second port (auxiliary) provides access to debug ports on specific processors (SRP module, line module). Juniper Networks customer support engineers use the auxiliary port. We recommend that users do not use the auxiliary port.

•

External timing inputs—The BNC connectors provide a method of ensuring that the clock timing used by the router remains synchronized with the network's system clock.

You can hot-swap SRP IOAs. Hot-swapping enables you to add or remove SRP IOAs without powering down the system. When you complete hot-swapping an SRP IOA, its MAC address in the subnet is automatically refreshed without rebooting the SRP or the chassis. Also, you can re-insert an SRP IOA that you had taken outpreviously to the same network without refreshing the MAC address of the SRP IOA.

NOTE: Hot-swapping an SRP IOA is unsupported during a unified in-service

software upgrade (ISSU).

If you have configured RADIUS server on an SRP IOA that you want to replace, you can perform either of the following actions topreventloss of accounting orlogoutinformation:

•

Disable accounting and, when there is no subscriber login or logout activity, hot-swap SRP IOA.

•

Increase the timeout value of the RADIUS server configured depending on the time used for IOA replacement. The maximum timeout value is 1000 seconds.

Afteryou complete hot-swapping theSRP IOA, you can usethe show version all command to display the state of the SRP IOA.

The SRP IOA hot-swapping is supported on the following routers:

•

E320 router with SRP-100 or SRP-320

•

E120 router

Line Modules

Chapter 1: E120 and E320 Overview

NOTE: You must complete the hot-swapping of the SRP IOA within 1800

seconds.

For details about installing the SRP IOA, see “Installing Modules” on page 25.

Line modules (LMs) act as frame forwarding engines for the physical interfaces (the IOAs) and process data from different types of network connections. For information about available line modules, and which SRP modules support specific line modules, see the E120 and E320 Module Guide.

Figure 7 on page 11 shows a representative line module. For details about installing line modules, see “Installing Modules” on page 25.

Figure 7: Representative Line Module

Packet Classification

The line module supports packet classification on ingress. A classification engine on the line module matches 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 Adapters

Most input/output adapters (IOA) provide the physical interconnection to the network via small form-factorpluggabletransceivers(SFPs). You insert each IOAinto the passive midplane in the rear of the chassis, directly behind a line module. See Figure 2 on page 5

E120 and E320 11.3.x Hardware Guide

for IOA location in the router and Figure 8 on page 12 for a representative IOA model. See “Installing and Removing SFPs” on page 41 and the E120 and E320 Module Guide for information on SFPs.

For a list of hot-swappable IOAs, see Table 4 on page 30.

Figure 8: Representative IOA

An IOA bracket can be installed to create upper and lower IOA bays (E320 router) or left and right IOA bays (E120 router), enabling you to use two IOAs in the same slot. This architecture enables you to combine different IOA types in the same slot and to support oversubscribed configurations.

Restrictions exist concerning which IOAs can be combined in the same slot and which bay (upper or lower, left or right) they may be installed in. See “IOA Slot Combinations” on page 30 and the E120 and E320 Module Guide for information. For details about installing IOAs, see “Installing Modules” on page 25.

Network Management Tools

You can use different management tools to configure the system to meet the specific networking requirements.

CLI Management

The command-line interface (CLI)provides fully developedand automated configuration and status functionality through a local RS-232 port, Telnet, or SSH over any reachable network. For a full discussion of the CLI, see JunosE System Basics Configuration Guide, Chapter 2, Command-Line Interface.

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.

Redundancy Features

This section describes system redundancy features.

SRP Modules

The router uses a 1:1 redundancy scheme for the SRP module. When two SRP modules are installed in therouter, one actsas the primary (active) andthe second as aredundant (standby) module. Both SRP modules share a single SRP IOA located in the rear of the chassis. After you install two SRP modules, the modules negotiate for the primary role. A number of factors determine whichmodule 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 power up the system.

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. For information about configuring and managing SRP module redundancy, see JunosE System Basics Configuration Guide, Chapter 6, Managing Modules.

Chapter 1: E120 and E320 Overview

Power

Fans

NVS Cards

Each SRP module has two NVS cards (0, 1). The NVS cards in the active SRP module are designated disk0 and disk1. The NVS cards in the redundant SRP module are designated standby-disk0 and standby-disk1. After you install new NVS cards or SRP modules, you must issue the synchronize command to match the file system of the NVS card on the redundant SRP module with the file system of the NVS card on the active SRP module. See “Replacing an NVS Card” on page 70 for more information.

The routers provide a power architecture that distributes redundant –48 VDC feeds through the router to each line module, IOA, SRP module, SFM module, and fan module where DC-to-DC converters provide local conversion to the required secondary voltages.

The E320 router employs a bottom-to-top cooling system to keep the temperature of the modules and components within normal operating limits. Eight cooling fans are located in a tray at the top of the router. (See Figure 1 on page 5 and Figure 2 on page 5.) Air is pulled in from the front of the router at the bottom and is exhausted out the top.

The E120 router employs a right-to-left cooling system. Nine cooling fans are located in a tray at the left of the router. (See Figure 3 on page 6.) Air is pulled in from the right of the router and is exhausted out the left.

The system monitors the temperature of each module. If the temperature of a module exceeds the maximum limit, the system immediately goes into thermal protection mode and the LMs and SFM modules are powered off. The system controllers remain active and respond on all management interfaces. All other modules remain in a power-off

E120 and E320 11.3.x Hardware Guide

condition. The failure of any two components (fan or converter), or the absence of the fan tray, causes the chassis to enter thermal protection mode to prevent hardware damage. For information about troubleshooting high operating temperatures, see “Troubleshooting” on page 77.

The E320 fan tray has two primary converters that power four fans each. If a primary converter fails, a third redundant converter takes over. The E120 fan tray has dual converters that load share for redundancy. If one converter fails, the other redundant convertertakesover. The systemsoftware reports analarm if any of the fans orconverters fail.

+ 112 hidden pages

Juniper E SERIES BROADBAND SERVICES ROUTERS 11.3.X - E120 AND E320 HARDWARE GUIDE REV 9-29-2010, E120, E320 Hardware Manual

Specifications and Main Features

Frequently Asked Questions

User Manual