Juniper networks T320 User Manual

T320 Core Router
Hardware Guide
Published: 2010-10-28
Copyright © 2010, Juniper Networks, Inc.
Juniper Networks, Inc. 1194 North Mathilda Avenue Sunnyvale, California 94089 USA 408-745-2000 www.juniper.net
This productincludes the Envoy SNMP Engine, developed by Epilogue Technology,an Integrated Systems Company.Copyright © 1986-1997, Epilogue Technology Corporation. All rights reserved. This program and its documentation were developed at private expense, and no part of them is in the public domain.
This product includes memory allocation software developed by Mark Moraes, copyright © 1988, 1989, 1993, University of Toronto.
This product includes FreeBSD software developed by the University of California, Berkeley, and its contributors. All of the documentation and software included in the 4.4BSD and 4.4BSD-Lite Releases is copyrighted by the Regents of the University of California. Copyright © 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994. The Regents of the University of California. All rights reserved.
GateD software copyright © 1995, the Regents of the University. All rights reserved. Gate Daemon was originated and developed through release 3.0 by Cornell University and its collaborators. Gated is based on Kirton’s EGP, UC Berkeley’s routing daemon (routed), and DCN’s HELLO routing protocol. Development of Gated has been supported in part by the National Science Foundation. Portions of the GateD software copyright © 1988, Regents of the University of California. All rights reserved. Portions of the GateD software copyright © 1991, D. L. S. Associates.
This product includes software developed by Maker Communications, Inc., copyright © 1996, 1997, Maker Communications, Inc.
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.
T320 Core Router Hardware Guide
Copyright © 2010, Juniper Networks, Inc. All rights reserved. Printed in USA.
Revision History October 2010—Corporate rebranding. August 2010—Corporate rebranding. May 2010—For Junos OS Release 10.0 and later, added support of the external clock inputs on the SCG. September 2009—Completed topic conversion. 18 March2008— 530-021111-01 Revision 2.Updated high-availability information. Updated recommendation for theminimum circuit breaker for each input. 22 June 2007— 530-021111-01 Revision 1. Removed the end-of-life CB, Added the first supported Junos OS release for each FPC. Corrected the description of the T-CB, clearance and rack requirements, mounting hardware procedures, output of the show chassis environment pem command, the note regarding matching voltage, and the gauge of the DC power and grounding cables. 20 October 2006— 530-017397-01 Revision 1. Added European Community EMC Declaration of Conformity. 28 June2006—530-014305-01 Revision3. CorrectedDC system current rating andFPC1, FPC2, andFPC3 current requirements, and updated the corresponding power calculation examples. Added how much torque to apply when securing the cable lugs to the DC power supplies. 13 April 2006—530-014305-01 Revision 2. Changed replacement procedures to reflect the fact that some Routing Engines might or might not have retaining screws. Updated Junos OS release recommendation for graceful switchover. 26 September 2005—530-014305-01 Revision 1. Added FPC handling and storage procedures. 05 April 2005—530-007470-01 Revision 2. Reorganized to conform to newly established standards. 01 April 2004—General updates and cleanup. 30 June 2003—Updated information and minor edits. 02 April 2002—Second edition. 03 December 2001—First edition.
Copyright © 2010, Juniper Networks, Inc.ii
The information in this document is current as of the date listed in the revision history.
YEAR 2000 NOTICE
Juniper Networks hardware and software products are Year 2000 compliant. The Junos OS has no known time-related limitations through the year 2038. However, the NTP application is known to have some difficulty in the year 2036.
iiiCopyright © 2010, Juniper Networks, Inc.
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 THISAGREEMENT. IF YOU DO NOT ORCANNOT AGREE TO THE TERMS CONTAINED HEREIN, THEN (A) DO NOT DOWNLOAD, INSTALL, OR USE THE SOFTWARE, AND (B) YOU MAY CONTACT JUNIPER NETWORKS REGARDING LICENSE TERMS.
1. The Parties. The parties to this Agreement are (i) Juniper Networks, Inc. (if the Customer’s principal office is located in the Americas) or Juniper Networks (Cayman) Limited (ifthe Customer’sprincipal officeis located outsidethe Americas) (such applicable entitybeing referred to herein as“Juniper”),and (ii) the person or organization thatoriginally purchased from Juniperor an authorized Juniperreseller 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 or an authorized Juniper reseller. “Software” also includes updates, upgrades and new releases of such software. “Embedded Software” means Software which Juniper has embedded in or loaded onto the Juniper equipment and any updates, upgrades, additions or replacements which are subsequently embedded in or loaded onto the equipment.
3. License Grant. Subject to paymentof the applicable fees and thelimitations andrestrictions set forth herein, Juniper grants toCustomer 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 limitsto Customer’s useof the Software. Suchlimits may restrictuse to amaximum numberof seats, registered endpoints, concurrent users, sessions, calls, connections, subscribers, clusters, nodes, realms, devices, links, ports or transactions, or require the purchase of separate licenses to use particular features, functionalities, services, applications, operations, or capabilities, or provide throughput, performance, configuration, bandwidth, interface, processing, temporal, or geographical limits. In addition, such limits may restrict the use of the Software to managing certain kinds of networks or require the Software to be used only in conjunction with other specific Software. Customer’s use of the Software shall be subject to all such limitations and purchase of all applicable licenses.
d. For any trial copy of the Software, Customer’s right to use the Software expires 30 days after download, installation or use of the Software. Customer may operate the Software after the 30-day trial period only if Customer pays for a license to do so. Customer may not extend or create an additional trial period by re-installing the Software after the 30-day trial period.
e. The Global Enterprise Edition of the Steel-Belted Radius software may be used by Customer only to manage access to Customer’s enterprise network. Specifically, service provider customers are expressly prohibited from using the Global Enterprise Edition of the Steel-Belted Radius software to support any commercial network access services.
The foregoing license is not transferable or assignable by Customer. No license is granted herein to any user who did not originally purchase the applicable license(s) for the Software from Juniper or an authorized Juniper reseller.
4. Use Prohibitions. Notwithstanding the foregoing, the license provided herein does not permit the Customer to, and Customer agrees not to and shall not: (a) modify, unbundle, reverse engineer, or create derivative works based on the Software; (b) make unauthorized copies of the Software (except as necessary for backup purposes); (c) rent, sell, transfer, or grant any rights in and to any copy of the Software,in any form, to any third party; (d) remove any proprietary notices,labels, or marks on or inany copyof the Software orany product in which the Software is embedded; (e) distribute any copy of the Software to any third party, including as may be embedded in Juniper equipment sold inthe secondhand market; (f)use any ‘locked’ orkey-restricted feature,function, service, application, operation, orcapability 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
Copyright © 2010, Juniper Networks, Inc.iv
Software in any manner that extends or is broader than the uses purchased by Customer from Juniper or an authorized Juniper reseller; (i) use Embedded Software on non-Juniper equipment; (j) use Embedded Software (or make it available for use) on Juniper equipment that the Customer did not originally purchase from Juniper or an authorized Juniper reseller; (k) disclose the results of testing or benchmarking of the Software to any third party without the prior written consent of Juniper; or (l) use the Software in any manner other than as expressly provided herein.
5. Audit. Customer shall maintain accurate records as necessary to verify compliance with this Agreement. Upon request by Juniper, Customer shall furnish such records to Juniper and certify its compliance with this Agreement.
6. Confidentiality. The Parties agree that aspects of the Software and associated documentation are the confidential property of Juniper. As such, Customer shall exercise all reasonable commercial efforts to maintain the Software and associated documentation in confidence, which at a minimum includes restricting access to the Software to Customer employees and contractors having a need to use the Software for Customer’s internal business purposes.
7. Ownership. Juniper and Juniper’s licensors, respectively, retain ownership of all right, title, and interest (including copyright) in and to the Software, associated documentation, and all copies 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 statementthat accompaniesthe Software (the“Warranty Statement”).Nothing inthis Agreement shallgive riseto any obligation to support the Software. Support services may be purchased separately. Any such support shall be governed by a separate, written support services agreement. TO THE MAXIMUM EXTENT PERMITTED BY LAW, JUNIPER SHALL NOT BE LIABLE FOR ANY LOST PROFITS, LOSS OF DATA, OR COSTS ORPROCUREMENT OFSUBSTITUTE GOODSOR SERVICES,OR FORANY SPECIAL, INDIRECT, ORCONSEQUENTIAL DAMAGES ARISING OUTOF THIS AGREEMENT,THE SOFTWARE,OR ANY JUNIPEROR JUNIPER-SUPPLIEDSOFTWARE. INNO EVENT SHALLJUNIPER 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.
vCopyright © 2010, Juniper Networks, Inc.
12. Commercial Computer Software. The Software is “commercial computer software” and is provided with restricted rights. Use, duplication, or disclosure by the United States government is subject to restrictions set forth in this Agreement and as provided in DFARS
227.7201 through 227.7202-4, FAR 12.212, FAR 27.405(b)(2), FAR 52.227-19, or FAR 52.227-14(ALT III) as applicable.
13. Interface Information. To the extent required by applicable law, and at Customer's written request, Juniper shall provide Customer with the interface information needed to achieve interoperability between the Software and another independently created program, on payment of applicable fee, if any. Customer shall observe strict obligations of confidentiality with respect to such information and shall use such information in compliance with any applicable terms and conditions upon which Juniper makes such information available.
14. Third Party Software. Any licensor of Juniper whose software is embedded in the Software and any supplier of Juniperwhose products or technology are embedded in (or services are accessed by) the Software shall be a third party beneficiary with respect to this Agreement, and such licensor or vendor shall have the right to enforcethis Agreement inits own name as if it were Juniper. In addition, certain third party software may be provided with the Software and is subject to the accompanying license(s), if any, of its respective owner(s). To the extent portions of the Software are distributed under and subject to open source licenses obligating Juniper to make the source code for such portions publicly available (such as the GNU General Public License (“GPL”) or the GNU Library General Public License (“LGPL”)), Juniper will make such source code portions (including Juniper modifications, as appropriate) available upon request for a period of up to three years from the date of distribution. Such request can be made in writing to Juniper Networks, Inc., 1194 N. Mathilda Ave., Sunnyvale, CA 94089, ATTN: General Counsel. You may obtain a copy of the GPL at http://www.gnu.org/licenses/gpl.html, and a copy of the LGPL
at http://www.gnu.org/licenses/lgpl.html .
15. Miscellaneous. This Agreement shall be governed by the laws of the State of California without reference to its conflicts of laws principles. The provisions of the U.N. Convention for the International Sale of Goods shall not apply to this Agreement. For any disputes arising under this Agreement, the Parties hereby consent to the personal and exclusive jurisdiction of, and venue in, the state and federal courts within Santa Clara County, California. This Agreement constitutes the entire and sole agreement between Juniper and the Customer with respect to the Software, and supersedes all prior and contemporaneous agreements relating to the Software, whether oral or written (including any inconsistent terms contained in a purchase order), except that the terms of a separate written agreement executed by an authorized Juniper representative and Customer shall govern to the extent such terms are inconsistent or conflict with terms contained herein. No modification to this Agreement nor any waiver of any rights hereunder shall be effective unless expressly assented to in writing by the party to be charged. If any portion of this Agreement is held invalid, the Parties agree that such invalidity shall not affect the validity of the remainder of this Agreement. This Agreement and associated documentation has been written in the English language, and the Parties agree that the English version will govern. (For Canada: Les parties aux présentés confirment leur volonté que cette convention de même que tous les documents y compris tout avis qui s'y rattaché, soient redigés en langue anglaise. (Translation: The parties confirm that this Agreement and all related documentation is and will be in the English language)).
Copyright © 2010, Juniper Networks, Inc.vi

Table of Contents

About the Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxi
Junos OS Documentation and Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxi
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxi
Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxii
Documentation Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxii
Documentation Feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxiii
Requesting Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxiv
Self-Help Online Tools and Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxiv
Opening a Case with JTAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxv
Part 1 T320 Router Product Overview
Chapter 1 T320 System Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
T320 Router Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Chapter 2 T320 Router System Architecture Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
System Architecture Description for M320, T320, T640, and T1600 Routers . . . . . 5
Routing Engine Functions for M320, T320, T640, and T1600 Routers . . . . . . . . . . 6
Packet Forwarding Engine Architecture for T320, T640, and T1600 Routers . . . . . 7
Packet Forward Engine Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Data Flow Through the T320, T640, and T1600 Router . . . . . . . . . . . . . . . . . . 7
Chapter 3 T320 Hardware Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
T320 Component Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
T320 Chassis Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
T320 Midplane Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
T320 Flexible PIC Concentrators (FPCs) Overview . . . . . . . . . . . . . . . . . . . . . . . . . 15
T320 Flexible PIC Concentrators (FPCs) Description . . . . . . . . . . . . . . . . . . . 16
T320 FPC Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
T320 FPC Slots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
T320 FPC Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
T320 FPC Edges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Identifying the T320 FPCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
T320 FPCs Supported . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
T320 PIC Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
T320 Switch Interface Boards (SIBs) Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
T320 Switch Interface Boards (SIBs) Description . . . . . . . . . . . . . . . . . . . . . . 23
T320 SIB LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
T320 Host Subsystem Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
viiCopyright © 2010, Juniper Networks, Inc.
T320 Core Router Hardware Guide
T320 Routing Engine Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
T320 Routing Engine Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
T320 RE-600 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
T320 RE-600 LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
T320 RE-1600 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
T320 RE-1600 LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
T320 RE-2000 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
T320 RE-2000 LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
T320 Control Boards Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
T320 T-CB Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
T320 T-CB LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
T320 SONET Clock Generators (SCGs) Overview . . . . . . . . . . . . . . . . . . . . . . . . . 33
T320 Standard SONET Clock Generator (SCG) Description . . . . . . . . . . . . . 34
T320 SCG LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
T320 Craft Interface Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
T320 Craft Interface Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
T320 Craft Interface Alarm LEDs and ACO/LT Button . . . . . . . . . . . . . . . . . . 36
T320 Craft Interface LCD and Navigation Buttons . . . . . . . . . . . . . . . . . . . . . 36
T320 Craft Interface Host Subsystem LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . 38
T320 Craft Interface SIB LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
T320 Craft Interface FPC LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
T320 Connector Interface Panel (CIP) Description . . . . . . . . . . . . . . . . . . . . 40
T320 Routing Engine Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
T320 Alarm Relay Contacts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
T320 Power System Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
T320 Power System Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
T320 Power Supply LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
T320 Cooling System Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
T320 Cable Management System Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Part 2 T320 Router Initial Installation
Chapter 4 Preparing for T320 Router Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
T320 Site Preparation Checklist Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
T320 Rack Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
T320 Clearance Requirements for Airflow and Hardware Maintenance . . . . . . . . 51
Chapter 5 Unpacking the T320 Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
T320 Router Installation Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Tools and Parts Required to Unpack the T320 Router . . . . . . . . . . . . . . . . . . . . . . 54
Unpacking the T320 Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Verifying the T320 Router Parts Received . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Chapter 6 Installing the T320 Router Mounting Hardware . . . . . . . . . . . . . . . . . . . . . . . 59
Verifying the T320 Rack-Mounting Hardware Received . . . . . . . . . . . . . . . . . . . . 59
Before You Install the T320 Rack-Mounting Hardware . . . . . . . . . . . . . . . . . . . . . 59
Installing the T320 Mounting Hardware for a Four-Post Rack or Cabinet . . . . . . 60
Installing the T320 Mounting Hardware for an Open-Frame Rack . . . . . . . . . . . . 63
Copyright © 2010, Juniper Networks, Inc.viii
Table of Contents
Chapter 7 Installing the T320 Router Using a Mechanical Lift . . . . . . . . . . . . . . . . . . . . 67
Safety Requirements, Warnings, and Guidelines for Installing the T320
Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Before You Install the T320 Router Using a Mechanical Lift . . . . . . . . . . . . . . . . . 67
Tools Required to Install the T320 Router Using a Mechanical Lift . . . . . . . . . . . . 68
Installing the T320 Router Using a Mechanical Lift . . . . . . . . . . . . . . . . . . . . . . . . 68
Attaching the T320 Router Installation Handle . . . . . . . . . . . . . . . . . . . . . . . . 70
Removing the T320 Router Installation Handle and Reinstalling the Power
Supplies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Chapter 8 Installing the T320 Router Without a Mechanical Lift . . . . . . . . . . . . . . . . . . 73
Before You Install the T320 Router Without a Mechanical Lift . . . . . . . . . . . . . . . 73
Tools and Parts Required to Install the T320 Router Without a Mechanical
Lift . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Removing T320 Components from the Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Removing the T320 Power Supplies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Removing the T320 SIBs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Removing the T320 T-CBs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Removing the T320 SCG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Removing the T320 Rear Fan Tray . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Removing the T320 Cable Management System . . . . . . . . . . . . . . . . . . . . . . 79
Removing the T320 FPCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Installing the T320 Chassis in the Rack Manually . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Reinstalling T320 Components in the Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Reinstalling the T320 Rear Fan Tray . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Reinstalling the T320 SCGs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Reinstalling the T320 T-CBs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Reinstalling the T320 SIBs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Reinstalling the T320 Power Supplies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Reinstalling the T320 FPCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Reinstalling T320 Front Fan Trays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Reinstalling the T320 Cable Management System . . . . . . . . . . . . . . . . . . . . . 92
Chapter 9 Connecting the T320 Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Tools and Parts Required to Connect the T320 Router . . . . . . . . . . . . . . . . . . . . . 93
Overview of Connecting the T320 Router to Management and Alarm Devices . . 94
Connecting the T320 Router to a Network for Out-of-Band
Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Connecting the T320 Router to a Management Console or Auxiliary
Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Connecting the T320 Router to an External Alarm-Reporting Device . . . . . . 96
Connecting PIC Cables to the T320 Router . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Chapter 10 Providing Power to the T320 Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Tools and Parts Required to Provide Power to the T320 Router . . . . . . . . . . . . . . 99
Connecting the T320 Grounding Cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Connecting DC Power to the T320 Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Powering On the T320 Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Powering Off the T320 Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
ixCopyright © 2010, Juniper Networks, Inc.
T320 Core Router Hardware Guide
Chapter 11 Performing the Initial T320 Junos OS Configuration . . . . . . . . . . . . . . . . . . 105
Part 3 T320 Router Hardware Maintenance, Troubleshooting, and
Chapter 12 Maintaining T320 Router Hardware Components . . . . . . . . . . . . . . . . . . . . . 111
Chapter 13 Troubleshooting T320 Router Hardware Components . . . . . . . . . . . . . . . . 127
Preparing to Configure the T320 Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Initially Configuring the T320 Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Entering Configuration Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Configuring User Accounts and Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Configuring System Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Committing the Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Replacement Procedures
Tools and Parts Required to Maintain the T320 Hardware Components . . . . . . . 111
Routine Maintenance Procedures for the T320 Router . . . . . . . . . . . . . . . . . . . . . . 111
Maintaining T320 Cooling System Components . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Maintaining the T320 Air Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Maintaining the T320 Fan Trays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
Maintaining the T320 Host Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
Maintaining the T320 Routing Engines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Maintaining the T320 T-CBs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Maintaining the T320 SCGs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Maintaining the T320 Packet Forwarding Engine Components . . . . . . . . . . . . . . 116
Maintaining T320 FPCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Holding and Storing T320 FPCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Holding T320 FPCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Storing T320 FPCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Maintaining T320 PICs and PIC Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Maintaining the T320 SIBs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Maintaining the T320 Power Supplies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Overview of Troubleshooting Resources for the T320 Router . . . . . . . . . . . . . . . . 127
Troubleshooting Using the T320 Command-Line Interface . . . . . . . . . . . . . . 127
Troubleshooting Using the T320 LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Troubleshooting Using the T320 Craft Interface LEDs . . . . . . . . . . . . . . 128
Troubleshooting Using the T320 Component LEDs . . . . . . . . . . . . . . . . 129
Troubleshooting Using the T320 Chassis and Interface Alarm Messages . . 129
Troubleshooting from the Juniper Networks Assistance Center . . . . . . . . . . 132
Troubleshooting the T320 Cooling System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Troubleshooting the T320 FPCs and PICs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Troubleshooting the T320 FPCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Troubleshooting the T320 PICs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Troubleshooting the T320 Power System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Copyright © 2010, Juniper Networks, Inc.x
Table of Contents
Chapter 14 Replacing the T320 Router Hardware Components . . . . . . . . . . . . . . . . . . . 137
T320 Router FRU Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
Tools and Parts Required to Replace the T320 Hardware Components . . . . . . . 138
Replacing the T320 CIP and Routing Engine Interface Port Cables . . . . . . . . . . . 139
Removing the T320 CIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
Installing the T320 CIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Replacing the T320 Connections to Routing Engine Interface Ports . . . . . . . 142
Replacing the T320 Management Ethernet Cables . . . . . . . . . . . . . . . . 143
Replacing the T320 Console or Auxiliary Cable . . . . . . . . . . . . . . . . . . . 145
Replacing the T320 Alarm Relay Wires . . . . . . . . . . . . . . . . . . . . . . . . . . 146
Replacing the T320 Cooling System Components . . . . . . . . . . . . . . . . . . . . . . . . 148
Replacing a T320 Fan Tray . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
Removing a T320 Front Fan Tray . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
Installing a T320 Front Fan Tray . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
Removing a T320 Rear Fan Tray . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
Installing a T320 Rear Fan Tray . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
Replacing a T320 Air Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
Removing a Front T320 Air Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
Installing a Front T320 Air Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
Removing a Rear T320 Air Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
Installing a Rear T320 Air Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
Replacing a T320 Craft Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
Removing a T320 Craft Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
Installing a T320 Craft Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
Replacing the T320 Host Subsystem Components . . . . . . . . . . . . . . . . . . . . . . . 160
Taking the T320 Host Subsystem Offline . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
Replacing a T320 T-CB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
Removing a T320 T-CB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
Installing a T320 T-CB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
Replacing a T320 PC Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
Removing a T320 PC Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
Installing a T320 PC Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
Replacing a DIMM Module in T320 Routing Engines . . . . . . . . . . . . . . . . . . . 166
Removing a T320 DIMM Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
Installing a T320 DIMM Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
Replacing a T320 Routing Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
Removing a T320 Routing Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
Installing a T320 Routing Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
Replacing a T320 SCG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
Removing a T320 SCG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
Installing a T320 SCG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
xiCopyright © 2010, Juniper Networks, Inc.
T320 Core Router Hardware Guide
Replacing a T320 SIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
Removing a T320 SIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
Installing a T320 SIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
Replacing T320 Packet Forwarding Engine Components . . . . . . . . . . . . . . . . . . . 176
Replacing a T320 FPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
Removing a T320 FPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
Installing a T320 FPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
Replacing a T320 PIC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
Removing a T320 PIC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
Installing a T320 PIC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
Replacing T320 PIC Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
Removing a T320 PIC Cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
Installing a T320 PIC Cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
Replacing a T320 SFP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
Removing a T320 SFP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
Installing a T320 SFP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
Replacing a T320 XENPAK Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
Removing a T320 XENPAK Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
Installing a T320 XENPAK Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
Replacing T320 Power System Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
Replacing a T320 DC Power Supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
Removing a T320 DC Power Supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
Installing a T320 DC Power Supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
Replacing a T320 DC Power Supply Cable . . . . . . . . . . . . . . . . . . . . . . . . . . 200
Removing a T320 DC Power Supply Cable . . . . . . . . . . . . . . . . . . . . . . 200
Installing a T320 DC Power Supply Cable . . . . . . . . . . . . . . . . . . . . . . . 200
Part 4 Appendixes
Appendix A T320 Safety and Regulatory Compliance Information . . . . . . . . . . . . . . . . 205
Definition of Safety Warning Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
T320 Safety Guidelines and Warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
General Safety Guidelines for M Series, MX Series, and T Series Routers . . 207 General Safety Warnings for M Series, MX Series, and T Series Routers . . . 208
Qualified Personnel Warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
Restricted Access Area Warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
Preventing Electrostatic Discharge Damage to a T320 Router . . . . . . . . . . . 210
Fire Safety Requirements for M Series, MX Series, and T Series Routers . . . . . . . 211
General Fire Safety Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
Fire Suppression . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
Fire Suppression Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
T320 Installation Safety Guidelines and Warnings . . . . . . . . . . . . . . . . . . . . . . . . 212
T320 Chassis Lifting Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
Installation Safety Warnings for M Series, MX Series, and T Series
Routers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
Installation Instructions Warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
Rack-Mounting Requirements and Warnings . . . . . . . . . . . . . . . . . . . . . 214
Ramp Warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
T320 General Laser Safety Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
Copyright © 2010, Juniper Networks, Inc.xii
Table of Contents
Laser Safety Warnings for M Series, MX Series, and T Series Routers . . . . . . . . . 218
Class 1 Laser Product Warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
Class 1 LED Product Warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219
Laser Beam Warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219
Radiation from Open Port Apertures Warning . . . . . . . . . . . . . . . . . . . . . . . . 220
Maintenance and Operational Safety Warnings for M Series, MX Series, and T
Series Routers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
Battery Handling Warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
Jewelry Removal Warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
Lightning Activity Warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223
Operating Temperature Warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
Product Disposal Warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
T320 Electrical Safety Guidelines and Warnings . . . . . . . . . . . . . . . . . . . . . . . . . 226
In Case of an Electrical Accident . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
General Electrical Safety Guidelines and Electrical Codes for M Series, MX
Series, and T Series Routers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
General Electrical Safety Warnings for M Series, MX Series, and T Series
Routers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
Grounded Equipment Warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
Grounding Requirements and Warning . . . . . . . . . . . . . . . . . . . . . . . . . . 228
Midplane Energy Hazard Warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
Multiple Power Supplies Disconnection Warning . . . . . . . . . . . . . . . . . . 229
Power Disconnection Warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230
DC Power Electrical Safety Warnings for M Series, MX Series, and T Series
Routers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231
DC Power Copper Conductors Warning . . . . . . . . . . . . . . . . . . . . . . . . . . 231
DC Power Disconnection Warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231
DC Power Wiring Terminations Warning . . . . . . . . . . . . . . . . . . . . . . . . . 233
T320 Agency Approvals and Compliance Statements . . . . . . . . . . . . . . . . . . . . 234
T320 Agency Approvals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
T320 Compliance Statements for NEBS . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
Compliance Statements for EMC Requirements for M Series, MX Series,
and T Series Routers (Canada) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
T320 Compliance Statements for EMC Requirements (European
Community) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237
Compliance Statements for EMC Requirements for M Series, MX Series,
and T Series Routers (Japan) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
Compliance Statements for EMC Requirements for M Series, MX Series,
and T Series Routers (United States) . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
Compliance Statements for Environmental Requirements for M Series, MX
Series, and T Series Routers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
T320 Compliance Statements for Acoustic Noise . . . . . . . . . . . . . . . . . . . . 239
Appendix B T320 Physical Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241
T320 Physical Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241
Appendix C T320 Environmental Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
T320 Environmental Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
xiiiCopyright © 2010, Juniper Networks, Inc.
T320 Core Router Hardware Guide
Appendix D T320 Power Guidelines, Requirements, and Specifications . . . . . . . . . . . . 245
Appendix E T320 Router Cable and Wire Guidelines and Specifications . . . . . . . . . . . . 251
Appendix F T320 Router Cable Connector Pinouts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257
Appendix G Contacting Customer Support and Returning T320 Router Hardware . . 259
T320 Power System Electrical Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
T320 Power Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
T320 Chassis Grounding Cable and Lug Specifications . . . . . . . . . . . . . . . . . . . . 247
T320 DC Power Cable Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248
T320 DC Power Distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
Site Electrical Wiring Guidelines for M Series and T Series Routers . . . . . . . . . . 249
Distance Limitations for Signaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
Radio Frequency Interference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
Electromagnetic Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
T320 Network Cable Specifications and Guidelines . . . . . . . . . . . . . . . . . . . . . . . 251
T320 Fiber-Optic and Network Cable Specifications . . . . . . . . . . . . . . . . . . 251
T320 Signal Loss in Multimode and Single-Mode Fiber-Optic Cable . . . . . . 251
T320 Attenuation and Dispersion in Fiber-Optic Cable . . . . . . . . . . . . . . . . 252
T320 Attenuation in SONET/SDH PICs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
Calculating Power Budget for Fiber-Optic Cable for M Series, MX Series,
and T Series Routers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254
Calculating Power Margin for Fiber-Optic Cable for M Series, MX Series, and
T Series Routers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254
T320 Routing Engine Interface Cable and Wire Specifications . . . . . . . . . . . . . . 256
T320 RJ-45 Connector Pinouts for the Routing Engine ETHERNET Port . . . . . . . 257
T320 DB-9ConnectorPinouts forthe Routing EngineAUXILIARYand CONSOLE
Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258
Locating T320 Component Serial Numbers Using the CLI . . . . . . . . . . . . . . . . . 259
Locating T320 Component Serial Number Labels . . . . . . . . . . . . . . . . . . . . . . . . 260
Locating the T320 T-CB Serial Number Label . . . . . . . . . . . . . . . . . . . . . . . . 261
Locating the T320 CIP Serial Number Label . . . . . . . . . . . . . . . . . . . . . . . . . 261
Locating the T320 Craft Interface Serial Number Label . . . . . . . . . . . . . . . . 262
Locating the T320 FPC Serial Number Label . . . . . . . . . . . . . . . . . . . . . . . . 262
Locating the T320 PIC Serial Number Label . . . . . . . . . . . . . . . . . . . . . . . . . 263
Locating the T320 Power Supply Serial Number Label . . . . . . . . . . . . . . . . 264
Locating the T320 Routing Engine Serial Number Label . . . . . . . . . . . . . . . 265
Locating the T320 SCG Serial Number Label . . . . . . . . . . . . . . . . . . . . . . . . 265
Locating the T320 SIB Serial Number Label . . . . . . . . . . . . . . . . . . . . . . . . . 266
Contacting Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266
T320 Return Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267
Tools and Parts Required to Remove Components from an M Series, MX Series,
or T Series Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268
Packing the T320 Router for Shipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268
Packing Router Components for Shipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269
Part 5 Index
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273
Copyright © 2010, Juniper Networks, Inc.xiv

List of Figures

Part 1 T320 Router Product Overview
Chapter 2 T320 Router System Architecture Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Figure 1: Router Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Figure 2: Control Packet Handling for Routing and Forwarding Table Updates
for the T320 Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Figure 3: Data Flow Through the Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Chapter 3 T320 Hardware Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Figure 4: Front View of the T320 Router Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Figure 5: Rear View of the T320 Router Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Figure 6: T320 Midplane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Figure 7: FPC Installed in T320 Router Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Figure 8: FPC Online/Offline Button on the Craft Interface . . . . . . . . . . . . . . . . . . 18
Figure 9: FPC Edges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Figure 10: Type 1 PIC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Figure 11: Type 2 PIC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Figure 12: Type 3 PIC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Figure 13: Standard FPC1, FPC2, and FPC3 Supported by the T320 Router . . . . . . 21
Figure 14: Enhanced II FPC1, FPC2, and FPC3 Supported by the T320 Router . . . . 21
Figure 15: T320 SIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Figure 16: T320 Routing Engine 600 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Figure 17: T320 Routing Engine 1600 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Figure 18: Routing Engine 2000 (RE-2000) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Figure 19: T320 control board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Figure 20: T320 SCG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Figure 21: Front Panel of the T320 Craft Interface . . . . . . . . . . . . . . . . . . . . . . . . . 35
Figure 22: T320 LCD in Idle Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Figure 23: T320 LCD in Alarm Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Figure 24: CIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Figure 25: T320 Power Supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Figure 26: Airflow Through the T320 Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Figure 27: T320 Cable Management System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Part 2 T320 Router Initial Installation
Chapter 4 Preparing for T320 Router Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Figure 28: Typical Open-Frame Rack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Figure 29: T320 Chassis Dimensions and Clearance Requirements . . . . . . . . . . . 52
Chapter 5 Unpacking the T320 Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Figure 30: Contents of the Shipping Crate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
xvCopyright © 2010, Juniper Networks, Inc.
T320 Core Router Hardware Guide
Chapter 6 Installing the T320 Router Mounting Hardware . . . . . . . . . . . . . . . . . . . . . . . 59
Chapter 7 Installing the T320 Router Using a Mechanical Lift . . . . . . . . . . . . . . . . . . . . 67
Chapter 8 Installing the T320 Router Without a Mechanical Lift . . . . . . . . . . . . . . . . . . 73
Chapter 9 Connecting the T320 Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Chapter 10 Providing Power to the T320 Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Figure 31: Positioning the Spacer Bar on the Rack . . . . . . . . . . . . . . . . . . . . . . . . . 62
Figure 32: Installing the Mounting Hardware for a Four-Post Rack or Cabinet . . . 63
Figure 33: Installing the Mounting Hardware for an Open-Frame Rack . . . . . . . . 65
Figure 34: Installing the T320 Router in the Rack . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Figure 35: Removing a Power Supply Before Installing the Installation
Handle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Figure 36: Attaching the Installation Handle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Figure 37: Reinstalling a Power Supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Figure 38: Removing a Power Supply Before Installing the Router . . . . . . . . . . . . 75
Figure 39: Removing a T320 SIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Figure 40: Removing a T320 T-CB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Figure 41: Removing a T320 SCG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Figure 42: Removing the Rear T320 Fan Tray . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Figure 43: Removing a T320 FPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Figure 44: Attaching the Installation Handle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Figure 45: Installing the T320 Router in the Rack . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Figure 46: Reinstalling the Rear T320 Fan Tray . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Figure 47: Reinstalling a T320 SCG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Figure 48: Reinstalling a T-CB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Figure 49: Reinstalling a SIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Figure 50: Reinstalling a T320 Power Supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Figure 51: Reinstalling an FPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Figure 52: Reinstalling a Front Fan Tray . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Figure 53: T320 Routing Engine Management Ports and Alarm Relay
Contacts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Figure 54: Routing Engine Ethernet Cable Connector . . . . . . . . . . . . . . . . . . . . . . 95
Figure 55: Console and Auxiliary Serial Port Connector . . . . . . . . . . . . . . . . . . . . . 96
Figure 56: Attach Cable to a PIC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Figure 57: Connecting DC Power to the T320 Router . . . . . . . . . . . . . . . . . . . . . . 102
Part 3 T320 Router Hardware Maintenance, Troubleshooting, and
Replacement Procedures
Chapter 12 Maintaining T320 Router Hardware Components . . . . . . . . . . . . . . . . . . . . . 111
Figure 58: Do Not Grasp the Connector Edge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Figure 59: Do Not Carry an FPC with Only One Hand . . . . . . . . . . . . . . . . . . . . . . . 119
Figure 60: Do Not Rest the FPC on an Edge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Figure 61: Holding an FPC Vertically . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Figure 62: Do Not Stack FPCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Chapter 14 Replacing the T320 Router Hardware Components . . . . . . . . . . . . . . . . . . . 137
Figure 63: Removing the CIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
Copyright © 2010, Juniper Networks, Inc.xvi
List of Figures
Figure 64: Installing a CIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
Figure 65: Routing Engine Interface Ports and Alarm Relay Contacts . . . . . . . . . 143
Figure 66: Ethernet Cable Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
Figure 67: Routing Engine Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
Figure 68: Routing Engine Alarm Relay Wires . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
Figure 69: Removing a Front T320 Fan Tray . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
Figure 70: Installing a Front T320 Fan Tray . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
Figure 71: Removing a Rear T320 Fan Tray . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
Figure 72: Installing a Rear T320 Fan Tray . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
Figure 73: Removing the Front Air Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
Figure 74: Replacing the Front Filter Element . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
Figure 75: Installing the Front Air Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
Figure 76: Removing the Rear Air Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
Figure 77: Removing the Rear Air Filter Element . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
Figure 78: Installing the Rear Air Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
Figure 79: Removing a T320 Craft Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
Figure 80: Installing a Replacement T320 Craft Interface . . . . . . . . . . . . . . . . . . 160
Figure 81: Removing a T320 T-CB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
Figure 82: Installing a T-CB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
Figure 83: Removing a PC Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
Figure 84: Installing a PC Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
Figure 85: Installing the DIMM Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
Figure 86: Removing the T320 Routing Engine Cover . . . . . . . . . . . . . . . . . . . . . . 169
Figure 87: Removing a T320 Routing Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
Figure 88: Installing a T320 Routing Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
Figure 89: Reinstalling the T320 Routing Engine Cover . . . . . . . . . . . . . . . . . . . . . 171
Figure 90: Removing a T320 SCG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
Figure 91: Installing a T320 SCG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
Figure 92: Removing a T320 SIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
Figure 93: Installing a T320 SIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
Figure 94: Removing a T320 FPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
Figure 95: Installing a T320 FPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
Figure 96: Connecting Fiber-Optic Cable to a T320 PIC . . . . . . . . . . . . . . . . . . . . 182
Figure 97: Removing a PIC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
Figure 98: Installing a PIC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
Figure 99: Connecting Fiber-Optic Cable to a T320 PIC . . . . . . . . . . . . . . . . . . . . 189
Figure 100: Small Form-Factor Pluggable (SFP) . . . . . . . . . . . . . . . . . . . . . . . . . 190
Figure 101: Removing a XENPAK Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
Figure 102: Installing a XENPAK Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
Figure 103: Disconnecting Power Cables from the DC Power Supply . . . . . . . . . . 196
Figure 104: Removing a T320 Power Supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
Figure 105: Rear of the Power Supply Showing Midplane Connectors . . . . . . . . . 197
Figure 106: Installing a Replacement T320 Power Supply . . . . . . . . . . . . . . . . . . 199
Figure 107: Connecting Power Cables to the T320 Power Supply . . . . . . . . . . . . 201
Part 4 Appendixes
Appendix A T320 Safety and Regulatory Compliance Information . . . . . . . . . . . . . . . . 205
Figure 108: Placing a Component into an Electrostatic Bag . . . . . . . . . . . . . . . . . 211
xviiCopyright © 2010, Juniper Networks, Inc.
T320 Core Router Hardware Guide
Appendix D T320 Power Guidelines, Requirements, and Specifications . . . . . . . . . . . . 245
Appendix G Contacting Customer Support and Returning T320 Router Hardware . . 259
Figure 109: DC Power and Grounding Cable Lug . . . . . . . . . . . . . . . . . . . . . . . . . 248
Figure 110: Typical DC Source Cabling to the Router . . . . . . . . . . . . . . . . . . . . . . 249
Figure 111: Serial Number ID Label . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
Figure 112: T-CB Serial Number Label . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261
Figure 113: CIP Serial Number Label . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262
Figure 114: Craft Interface Serial Number Label . . . . . . . . . . . . . . . . . . . . . . . . . . 262
Figure 115: Serial Number Label on FPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263
Figure 116: PIC Serial Number Label . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264
Figure 117: Power Supply Serial Number Label . . . . . . . . . . . . . . . . . . . . . . . . . . . 264
Figure 118: Routing Engine Serial Number Label . . . . . . . . . . . . . . . . . . . . . . . . . . 265
Figure 119: SCG Serial Number Label . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
Figure 120: SIB Serial Number Label . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266
Copyright © 2010, Juniper Networks, Inc.xviii

List of Tables

About the Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxi
Table 1: Notice Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxii
Table 2: Text and Syntax Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxii
Part 1 T320 Router Product Overview
Chapter 3 T320 Hardware Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Table 3: Identifying the FPCs Supported by the T320 Router . . . . . . . . . . . . . . . . 20
Table 4: FPCs Supported by the T320 Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Table 5: T320 SIB LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Table 6: RE-1600 LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Table 7: Routing Engine 2000 LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Table 8: T320 T-CB LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Table 9: T320 SCG LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Table 10: T320 Alarm LEDs and Alarm Cutoff/Lamp Test Button . . . . . . . . . . . . . 36
Table 11: T320 Host Subsystem LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Table 12: SIB LEDs on the Craft Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Table 13: FPC LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Table 14: T320 Power Supply LED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Part 2 T320 Router Initial Installation
Chapter 4 Preparing for T320 Router Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Table 15: T320 Site Preparation Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Chapter 5 Unpacking the T320 Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Table 16: T320 Router Parts List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Table 17: T320 Accessory Box Parts List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Chapter 6 Installing the T320 Router Mounting Hardware . . . . . . . . . . . . . . . . . . . . . . . 59
Table 18: T320 Four-Post or Cabinet Rack Mounting Hole Locations . . . . . . . . . . 60
Table 19: T320 Open-Frame Rack Mounting Hole Locations . . . . . . . . . . . . . . . . . 64
Part 3 T320 Router Hardware Maintenance, Troubleshooting, and
Replacement Procedures
Chapter 13 Troubleshooting T320 Router Hardware Components . . . . . . . . . . . . . . . . 127
Table 20: T320 Chassis Alarm Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Table 21: SONET/SDH Interface Alarm Messages . . . . . . . . . . . . . . . . . . . . . . . . . 131
Chapter 14 Replacing the T320 Router Hardware Components . . . . . . . . . . . . . . . . . . . 137
Table 22: T320 Field-Replaceable Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
xixCopyright © 2010, Juniper Networks, Inc.
T320 Core Router Hardware Guide
Part 4 Appendixes
Appendix B T320 Physical Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241
Appendix C T320 Environmental Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
Appendix D T320 Power Guidelines, Requirements, and Specifications . . . . . . . . . . . . 245
Appendix E T320 Router Cable and Wire Guidelines and Specifications . . . . . . . . . . . . 251
Appendix F T320 Router Cable Connector Pinouts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257
Table 23: Tools and Parts Required for Component Replacement . . . . . . . . . . . . 138
Table 24: Effect of Taking the T320 Host Subsystem Offline . . . . . . . . . . . . . . . 160
Table 25: T320 Physical Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241
Table 26: Router Environmental Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . 243
Table 27: Power System Electrical Specifications . . . . . . . . . . . . . . . . . . . . . . . . 245
Table 28: Component Power Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
Table 29: Grounding Cable Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247
Table 30: Power Cable Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248
Table 31: Estimated Values for Factors Causing Link Loss . . . . . . . . . . . . . . . . . 255
Table 32: Cable and Wire Specifications for Routing Engine Management and
Alarm Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256
Table 33: RJ-45 Connector Pinouts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257
Table 34: DB-9 Connector Pinouts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258
Copyright © 2010, Juniper Networks, Inc.xx

About the Documentation

Junos OS Documentation and Release Notes on page xxi
Objectives on page xxi
Audience on page xxii
Documentation Conventions on page xxii
Documentation Feedback on page xxiii
Requesting Technical Support on page xxiv

Junos OS Documentation and Release Notes

For a list of related Junos OS documentation, see
http://www.juniper.net/techpubs/software/junos/ .
If the information in the latest release notes differs from the information in the documentation, follow the Junos OS 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/.

Objectives

This documentation describes hardware components, installation, basic configuration, and basic troubleshooting procedures for the Juniper Networks T320 Internet Router. It explains how to prepare your site for router installation, unpack and install the hardware, power on the router, perform initial software configuration, and perform routine maintenance. After completing the installation and basic configuration procedures covered in this documentation, see the Junos OS configuration guides for information about further Junos OS configuration.
NOTE: For additional information about Juniper Networks routers and the
Physical Interface Cards (PICs) they support—either corrections to or informationthat mighthave been omitted from this guide—see the hardware release notes at http://www.juniper.net/.
xxiCopyright © 2010, Juniper Networks, Inc.
T320 Core Router Hardware Guide

Audience

This documentation is designed for network administrators who are installing and maintaining a Juniper Networks router or preparing a site for router installation. To use the documentation, you need a broad understanding of networks in general, the Internet in particular, networking principles, and network configuration. Any detailed discussion of these concepts is beyond the scope of this hardware documentation.

Documentation Conventions

Table 1 on page xxii defines the notice icons used in this guide.
Table 1: Notice Icons
DescriptionMeaningIcon
Indicates important features or instructions.Informational note
Table 2 on page xxii defines the text and syntax conventions used in this guide.
Table 2: Text and Syntax Conventions
Represents text that you type.Bold text like this
Fixed-width text like this
Italic text like this
Represents output that appears on the terminal screen.
Introduces important new terms.
Identifies book names.
Identifies RFC and Internet draft titles.
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
ExamplesDescriptionConvention
To enter configuration mode, type the
configure command:
user@host> configure
user@host> show chassis alarms
No alarms currently active
A policy term is a named structure that defines match conditions and actions.
Junos System Basics Configuration Guide
RFC 1997, BGP Communities Attribute
Copyright © 2010, Juniper Networks, Inc.xxii
Table 2: Text and Syntax Conventions (continued)
About the Documentation
ExamplesDescriptionConvention
Italic text like this
Text like this
| (pipe symbol)
# (pound sign)
[ ] (square brackets)
Indention and braces ( { } )
; (semicolon)
Represents variables (options for which you substitute a value) in commands or configuration statements.
Represents names of configuration statements, commands, files, and directories; IP addresses; configuration hierarchy levels; or labels on routing platform components.
Indicates a choice betweenthe mutually exclusivekeywords or variables on either side of the symbol. The set of choices is often enclosed in parentheses for clarity.
same lineas theconfiguration statement to which it applies.
Enclose a variable for which you can substitute one or more values.
Identify a level in the configuration hierarchy.
Identifies a leaf statement at a configuration hierarchy level.
Configure the machine’s domain name:
[edit] root@# set system domain-name
domain-name
To configure a stub area, include the
stub statement at the [edit protocols ospf area area-id] hierarchy level.
The console port is labeled CONSOLE.
stub <default-metric metric>;Enclose optional keywords or variables.< > (angle brackets)
broadcast | multicast
(string1 | string2 | string3)
rsvp { # Required for dynamic MPLS onlyIndicates a comment specified on the
community name members [ community-ids ]
[edit] routing-options {
static {
route default{
nexthop address; retain;
}
}
}
J-Web GUI Conventions
Bold text like this
> (bold right angle bracket)

Documentation Feedback

We encourage you to provide feedback, comments, and suggestions so that we can improve the documentation. You can send your comments to
techpubs-comments@juniper.net, or fill out the documentation feedback form at
Represents J-Web graphical user interface (GUI) items you click or select.
Separates levels in a hierarchy of J-Web selections.
In the Logical Interfaces box, select All Interfaces.
To cancel the configuration, click Cancel.
In the configuration editor hierarchy, select Protocols>Ospf.
xxiiiCopyright © 2010, Juniper Networks, Inc.
T320 Core Router Hardware Guide
https://www.juniper.net/cgi-bin/docbugreport/. If you are using e-mail, be sure to include
the following information with your comments:
Document or topic name
URL or page number
Software release version (if applicable)

Requesting Technical Support

Technical productsupport is available through the Juniper Networks Technical Assistance Center (JTAC). If you are a customer with an active J-Care or JNASC support contract, or are covered under warranty, and need post-sales technical support, you can access our tools and resources online or open a case with JTAC.
JTAC policies—For a complete understanding of our JTAC procedures and policies, review the JTAC User Guide located at
http://www.juniper.net/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 verifyservice entitlement by product serialnumber,use ourSerial NumberEntitlement (SNE) Tool: https://tools.juniper.net/SerialNumberEntitlementSearch/
Copyright © 2010, Juniper Networks, Inc.xxiv

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 .
About the Documentation
xxvCopyright © 2010, Juniper Networks, Inc.
T320 Core Router Hardware Guide
Copyright © 2010, Juniper Networks, Inc.xxvi
PART 1
T320 Router Product Overview
T320 System Overview on page 3
T320 Router System Architecture Overview on page 5
T320 Hardware Components on page 11
1Copyright © 2010, Juniper Networks, Inc.
T320 Core Router Hardware Guide
Copyright © 2010, Juniper Networks, Inc.2
CHAPTER 1
T320 System Overview
T320 Router Description on page 3

T320 Router Description

The T320 Core Router is a complete routing system that provides Gigabit Ethernet, SONET/SDH, and other high-speed interfacesfor large networksand networkapplications, such as those supported by Internet service providers (ISPs).
Application-specific integrated circuits (ASICs) are a definitive part of the router design; these ASICs enable the router to achieve data forwarding rates that match current fiber-optic capacity.
The router accommodates up to eight Flexible PIC Concentrators (FPCs), which can each be configured with a variety of network media types—altogether providing up to 64 Gigabit Ethernet, 64SONET/SDH OC-48/STM-16, or 16 SONET/SDHOC-192/STM-64 ports for the router.
Related
Documentation
The router's maximum aggregate throughput is 160 Gbps, full duplex. The router can forward traffic at high-performance rates for any combination of PICs that does not exceed 20 Gbps on a single FPC3. Any combination exceeding 20 Gbps is supported, but constitutes oversubscription. For information about the FPC types, see “T320 FPCs Supported” on page 22.
The router architecture cleanly separates control operations from packet forwarding operations. This design eliminates processing and traffic bottlenecks, permitting the router to achieve high performance. Control operations in the router are performed by the host subsystem, whichruns Junos OS tohandle routingprotocols, traffic engineering, policy, policing, monitoring, and configuration management. Forwarding operations in the router are performed by the Packet Forwarding Engines, which consist of hardware, including ASICs, designed by Juniper Networks.
T320 Chassis Description on page 12
T320 Physical Specifications on page 241
T320 Environmental Specifications on page 243
T320 Power Requirements on page 246
3Copyright © 2010, Juniper Networks, Inc.
T320 Core Router Hardware Guide
Copyright © 2010, Juniper Networks, Inc.4
CHAPTER 2
T320 Router System Architecture Overview
System Architecture Description for M320, T320, T640, and T1600 Routers on page 5
Routing Engine Functions for M320, T320, T640, and T1600 Routers on page 6
Packet Forwarding Engine Architecture for T320, T640, and T1600 Routers on page 7

System Architecture Description for M320, T320, T640, and T1600 Routers

The M320 Multiservice Edge Router and T320, T640, and T1600 Core Routers have two main architectural components:
Routing Engine—One or more Routing Engines provide Layer 3 routing services and network management.
PacketForwardingEngines—Thesehigh-performance,ASIC-basedcomponents provide Layer 2 and Layer 3 packet switching, route lookups, and packet forwarding.
Related
Documentation
The Routing Engines and the Packet Forwarding Engines perform their primary tasks independently, although theyconstantly communicate through multiple 100-Mbps links. This arrangement streamlines forwarding and routing control and runs Internet-scale backbone networks at high speeds. Figure 1 on page 5 shows the relationship between the Routing Engine and the Packet Forwarding Engines.
Figure 1: Router Architecture
Routing Engine Functions for M320, T320, T640, and T1600 Routers on page 6
Packet Forwarding Engine Architecture for T320, T640, and T1600 Routers on page 7
5Copyright © 2010, Juniper Networks, Inc.
T320 Core Router Hardware Guide

Routing Engine Functions for M320, T320, T640, and T1600 Routers

The Routing Engine handles all routing protocol processes, as well as the software processes that control the router's interfaces, the chassis components, system management, and user access to the router. The routing and software processes run on top of a kernel that interacts with the Packet Forwarding Engine. For more information about the processes, see the Junos OS System Basics and Services Command Reference.
The Routing Engine constructs and maintains one or more routing tables (see Figure 2 on page 6). From the routing tables, the Routing Engine derives a table of active routes, called the forwarding table, which is then copied into the Packet Forwarding Engine. The design of the ASICs allow the forwarding table in the Packet Forwarding Engine to be updated without interrupting forwarding performance.
Figure 2: Control Packet Handling for Routing and Forwarding Table Updates for the T320 Router
The Routing Engine includes the functions and features:
Processing of routing protocol packets—The Routing Engine handles all packets that concern routing protocols, freeing thePacketForwarding Engineto handle only packets that represent Internet traffic.
Softwaremodularity—Becauseeach software process is devoted to a different function and uses a separate process space, the failure of one process has little or no effect on the others.
In-depth Internet functionality—Each routingprotocolis implemented with a complete set ofInternet featuresand provides fullflexibility for advertising, filtering, and modifying routes. Routing policies are set according to route parameters (for example, prefix, prefix lengths, and Border Gateway Protocol [BGP] attributes).
Scalability—The Junos OS routing tables have been designed to hold all the routes in current networks with ample capacity for expansion. Additionally, the Junos OS can efficiently support large numbers of interfaces and virtual circuits.
Copyright © 2010, Juniper Networks, Inc.6
Chapter 2: T320 Router System Architecture Overview
Management interface—Different levels of system management tools are provided, including the Junos OS command-line interface (CLI), the Junos XML management protocol, the craft interface, and SNMP.
Storage and change management—Configuration files,system images, andmicrocode can be held and maintained in primary and secondary storage systems, permitting local or remote upgrades.
Monitoring efficiency and flexibility—The router supports functions such as alarm handling and packet counting on every port, without degrading packet-forwarding performance.
Related
Documentation
System Architecture Description for M320, T320, T640, and T1600 Routers on page 5
Packet Forwarding Engine Architecture for T320, T640, and T1600 Routers on page 7

Packet Forwarding Engine Architecture for T320, T640, and T1600 Routers

Packet Forward Engine Components on page 7
Data Flow Through the T320, T640, and T1600 Router on page 7
Packet Forward Engine Components
The Packet Forwarding Engines provide the Layer 2 and Layer 3 packet switching, forwarding,and route lookup functions.The Packet Forwarding Engines are implemented in ASICs that are physically located on the FPCs and the PICs.
Each Packet Forwarding Engine consists of the following components:
Layer 2/Layer 3 Packet Processing ASIC, which performs Layer 2 and Layer 3 encapsulationand decapsulation, and manages the division andreassembly ofpackets within the router.
Queuing and Memory Interface ASICs, which manage the buffering of data cells in memory and the queueing of notifications.
T Series Internet Processor, which provides the route lookup function.
Switch Interface ASICs, which extract the route lookup key and manage the flow of data cells across the switch fabric.
Media-specific ASICs on the PICs that perform control functions tailored to the PIC media types.
Data Flow Through the T320, T640, and T1600 Router
To ensure the efficient movement of data, the router is designed so that ASICs on the hardware components handle the forwarding of data. Data flows through the router in the following sequence (see Figure 3 on page 8):
7Copyright © 2010, Juniper Networks, Inc.
T320 Core Router Hardware Guide
Figure 3: Data Flow Through the Router
1. Packets arrive at an incoming PIC interface.
2. The PIC passes the packets to the FPC, where the Layer 2/Layer 3 Packet Processing
ASIC performs Layer 2 and Layer 3 parsing and divides the packets into 64-byte cells.
3. The Switch Interface ASIC extracts the route lookup key, places it in a notification and
passes the notification to the T Series Internet Processor. The Switch Interface ASIC also passes the data cells to the Queuing and Memory Interface ASICs for buffering.
4. The Queuing andMemory Interface ASICs pass thedata cells to memoryfor buffering.
5. The TSeries Internet Processorperforms theroute lookup and forwards thenotification
to the Queuing and Memory Interface ASIC.
6. The Queuingand MemoryInterfaceASIC sends the notification to the Switch Interface
ASIC facing the switch fabric, unless the destination is onthe samePacket Forwarding Engine. In this case, the notification is sent back to the Switch Interface ASIC facing the outgoing ports, and the packets are sent to the outgoing port without passing through the switch fabric (see Step 13).
7. The Switch Interface ASIC sends bandwidth requests through the switch fabric to the
destination port. The Switch Interface ASIC also issues read requests to the Queuing and Memory Interface ASIC to begin reading data cells out of memory.
8. The destination Switch Interface ASIC sends bandwidth grants through the switch
fabric to the originating Switch Interface ASIC.
Copyright © 2010, Juniper Networks, Inc.8
Chapter 2: T320 Router System Architecture Overview
9. Upon receipt of each bandwidth grant, the originating Switch Interface ASIC sends a
cell through the switch fabric to the destination Packet Forwarding Engine.
10. The destination Switch Interface ASIC receives cells from the switch fabric. It extracts
the route lookup key from each cell, places it in a notification, and forwards the notification to the T Series Internet Processor.
11. The T Series Internet Processor performs the route lookup, and forwards the
notification to the Queuing and Memory Interface ASIC.
12. The Queuingand MemoryInterfaceASIC forwards thenotification, including next-hop
information, to the Switch Interface ASIC.
13. The Switch Interface ASIC sends read requests to the Queuing and Memory Interface
ASIC to read the data cells out of memory, and passes the cells to the Layer 2/Layer 3 Packet Processing ASIC.
14. The Layer 2/Layer 3 Packet Processing ASIC reassembles the data cells into packets,
adds Layer 2 encapsulation, and sends the packets to the outgoing PIC interface.
15. The outgoing PIC sends the packets out into the network.
Related
Documentation
System Architecture Description for M320, T320, T640, and T1600 Routers on page 5
Routing Engine Functions for M320, T320, T640, and T1600 Routers on page 6
9Copyright © 2010, Juniper Networks, Inc.
T320 Core Router Hardware Guide
Copyright © 2010, Juniper Networks, Inc.10
CHAPTER 3
T320 Hardware Components
T320 Component Redundancy on page 11
T320 Chassis Description on page 12
T320 Midplane Description on page 14
T320 Flexible PIC Concentrators (FPCs) Overview on page 15
T320 PIC Description on page 22
T320 Switch Interface Boards (SIBs) Overview on page 23
T320 Host Subsystem Description on page 25
T320 Routing Engine Overview on page 25
T320 Control Boards Overview on page 32
T320 SONET Clock Generators (SCGs) Overview on page 33
T320 Craft Interface Overview on page 35
T320 Power System Overview on page 42
T320 Cooling System Description on page 44
T320 Cable Management System Description on page 45

T320 Component Redundancy

The T320 Core Router is designed so that no single point of failure can cause the entire system to fail. The following major hardware components are redundant:
Switch Interface Boards (SIBs)—The router has three SIBs. Each Type 1 FPC and Type 2 FPC has a dedicated ASIC with five high-speed links that connect to the SIBs (one link perSIB). AType3 FPChas two dedicated ASICs, andeach ASIC hasfive high-speed links that connect to the SIBs (a total of 10 links). One of the three SIBs—usually
SIB0—acts as a backup to the remaining two SIBs. In the event of a SIB failure, the
backup SIB becomes active and traffic forwarding continues without any degradation. When the failed SIB is replaced, it becomes the new backup.
Host subsystem—The host subsystem consists ofa Routing Enginefunctioning together with a T-CB. The router can have one or two host subsystems. If two host subsystems are installed, one functions as the master and the other functions as the backup. If the master host subsystem (or either of its components) fails, the backup can take over
11Copyright © 2010, Juniper Networks, Inc.
T320 Core Router Hardware Guide
as the master. To operate, each host subsystem requires a Routing Engine installed in an adjacent slot to a T-CB.
SONET Clock Generators (SCGs)—The router has a standard configuration of one SCG, but a second can be purchased to function as backup. If one SCG fails, the other becomes the masterSCG.Mastershipof the SCGs isindependent of the host subsystem, so routing functions are not affected.
Power supplies—The router has two power supplies, which share the load evenly. If one power supply fails, the other power supply can provide full power to the router indefinitely.
Cooling system—Thecooling system has redundantcomponents, whichare controlled by the host subsystem. If one of the fans fails, the host subsystem increases the speed of the remaining fans to provide sufficient cooling for the router indefinitely.
Related
Documentation
T320 Router Description on page 3
T320 System Architecture Description
Reinstalling T320 Components in the Chassis on page 85

T320 Chassis Description

The T320 Core Router chassis is a rigid sheet metal structure that houses all the other router components (see Figure 4 on page 13 and Figure 5 on page 14). The chassis measures 25.13 in. (63.82 cm) high, 31.4 in. (79.8 cm) deep, and 17.43 in. (44.3 cm) wide. The chassis can be installed into many types of racks or cabinets. For more information, see “T320 Rack Requirements” on page 50.
The chassis includes the following features (see Figure 4 on page 13 and Figure 5 on page 14):
Two pairs of metal brackets, one for center-mounting and one for front-mounting or mounting in a four-post rack or cabinet.
Handles on each side to facilitate positioning the router in the rack. Do not use the handles to lift the router.
Two electrostatic discharge (ESD) points (banana plug receptacles), one front and one rear.
WARNING: Before removingor installing any components of a functioning
router, attach an ESD strap to one of the two ESD points on the chassis and attach the other end of the strap around your bare wrist. Failure to use an ESD strap could result in damage to the router and its components.
Copyright © 2010, Juniper Networks, Inc.12
Chapter 3: T320 Hardware Components
Figure 4: Front View of the T320 Router Chassis
13Copyright © 2010, Juniper Networks, Inc.
T320 Core Router Hardware Guide
Figure 5: Rear View of the T320 Router Chassis
For chassis serial number information , see “Locating T320 Component Serial Numbers Using the CLI” on page 259.
Related
Documentation
Safety Requirements, Warnings, and Guidelines for Installing the T320 Router on
page 67
T320 Chassis Lifting Guidelines on page 213
T320 Chassis Grounding Cable and Lug Specifications on page 247

T320 Midplane Description

The T320 Core Router midplane is located in the center of the chassis and forms the rear of the FPC card cage (see Figure 6 on page 15). The FPCs install into the midplane from the front of the chassis, and the SIBs, Routing Engines, T-CBs, and SCGs install into the midplane from the rear ofthe chassis.The power supplies andcooling system components also connect to the midplane.
The midplane performs the following major functions:
Copyright © 2010, Juniper Networks, Inc.14
Chapter 3: T320 Hardware Components
Data path—Data packets are transferred across the midplane from the Packet Forwarding Engine on the originating FPC to the SIBs, and from the SIBs across the midplane to the Packet Forwarding Engine on the destination FPC.
Power distribution—The router power supplies are connected to the midplane, which distributes power to all the router components.
Signal path—The midplane providesthe signalpath to theFPCs, SIBs,Routing Engines, T-CBs, and other system components for monitoring and control of the system.
Figure 6: T320 Midplane
For chassis serial number information , see “Locating T320 Component Serial Numbers Using the CLI” on page 259.
Related
Documentation
T320 Router Description on page 3
Safety Requirements, Warnings, and Guidelines for Installing the T320 Router on
page 67
T320 Physical Specifications on page 241

T320 Flexible PIC Concentrators (FPCs) Overview

T320 Flexible PIC Concentrators (FPCs) Description on page 16
T320 FPCs Supported on page 22
15Copyright © 2010, Juniper Networks, Inc.
T320 Core Router Hardware Guide
T320 Flexible PIC Concentrators (FPCs) Description
T320 FPC Function on page 16
T320 FPC Slots on page 16
T320 FPC Components on page 17
T320 FPC Edges on page 18
Identifying the T320 FPCs on page 18
T320 FPC Function
FPCs house the PICs that connect the T320 Core Router to network media. The main function of an FPC is to connect the PICs installed in it to the other router components. The Packet Forwarding Engine receives incoming packets from the PICs installed on the FPC and forwards them through the switch planes to the appropriate destination port. In a maximum configuration with eight FPC3s installed, the Packet Forwarding Engines can forward up to 385 million packets per second (Mpps) for all packet sizes. The maximum aggregate throughput rate for the router is 160 Gbps (full duplex).
FPCs are hot-removable and hot-insertable. When you remove or install an FPC, packet forwarding is not interrupted. When you install an FPC into a functioning router, the Routing Engine downloads the FPC software, the FPC runs its diagnostics, and the PICs housed on the FPC are enabled. Forwarding continues uninterrupted during this process.
T320 FPC Slots
Up to eight Flexible PIC Concentrators (FPCs) install vertically in the front of the T320 Core router (see Figure 7 on page 17). The FPC slots are numbered left to right from FPC0 to FPC7. Each FPC has two connectors into which a PIC can be installed, allowing up to two PICs per FPC. An FPC can be installed into any FPC slot on the router, regardless of which PICs it contains. If a slot is not occupied by an FPC, an FPC blank panel must be installed to shield the empty slot and to allow cooling air to circulate properly through the router.
Copyright © 2010, Juniper Networks, Inc.16
Figure 7: FPC Installed in T320 Router Chassis
Chapter 3: T320 Hardware Components
T320 FPC Components
Each FPC consists of the following components:
FPC card carrier.
One Packet Forwarding Engine—Each Packet Forwarding Engine consists of Layer 2/Layer 3 PacketProcessing ASICs, Switch Interface ASICs, T Series Internet Processor ASICs, and a Memory Mezzanine Board (MMB)which includesthe Queuingand Memory Interface ASICs.
ProcessorMezzanine Board(PMB), which includes a 300-MHz CPU,system controller, 256 MB of SDRAM, and two Fast Ethernet interfaces.
Each FPC contains data memorythat ismanaged by the Queuing and Memory Interface ASICs.
Two LEDs, located on the craft interface above the FPC, that display the status of the FPC. For more information on the FPC LEDs, see “T320 Craft Interface FPC LEDs” on page 39.
FPC online/offline button, located on the craft interface above the FPC (see Figure 8 on page 18.
17Copyright © 2010, Juniper Networks, Inc.
T320 Core Router Hardware Guide
Figure 8: FPC Online/Offline Button on the Craft Interface
T320 FPC Edges
Regardless of whetheryou are holding anFPC vertically or horizontally, this documentation uses the same terms for all four edges of the FPC (see Figure 9 on page 18):
Faceplate—Edge of the FPC that has slots into which you insert the PICs
Connectoredge—Edge opposite the faceplate;this edgehas the connectorsthat attach to the midplane
Top edge—Edge at the top of the FPC when it is vertical
Bottom edge—Edge at the bottom of the FPC when it is vertical
Figure 9: FPC Edges
Identifying the T320 FPCs
Enhanced FPCs and Enhanced II FPCs are labeled. Check the label on the faceplate to identify the FPC. However, standard FPCs are not labeled. To determine the type of standard FPC, check the location of the installed PIC's online/offline button and how the PIC is secured to the FPC (Table 3 on page 20).
Copyright © 2010, Juniper Networks, Inc.18
Chapter 3: T320 Hardware Components
Type 1 and Type 2 PICs installed in a standard FPC look similar, because both have two captive screws to secure the PIC to the FPC. Therefore, you must check the location of the PIC online/offline button.
The PIC online/offline buttons are located on the Type 1 FPC abovethe PICs(see Figure 13 on page 21). Type 1 PICs do not have an online/offline button on the PIC faceplate (Figure 10 on page 19).
The PIC online/offline buttons are located directly on the Type 2 PIC faceplates (see Figure 11 on page 19), rather than on the Type 2 FPC faceplate.
Figure 11: Type 2 PICFigure 10: Type 1 PIC
Type 2 and Type 3 FPCs look similar, because both have the PIC online/offline buttons directly on the PIC faceplates. Therefore, you can distinguish between a Type 2 and Type 3 FPC by checking whether the installed PICs have a plastic ejector handle (Type 3) (see Figure 12 on page 20), or a captive screw (Type 2) (see Figure 11 on page 19), at the top of the PIC faceplate.
19Copyright © 2010, Juniper Networks, Inc.
g002378
T320 Core Router Hardware Guide
Figure 12: Type 3 PIC
Table 3: Identifying the FPCs Supported by the T320 Router
Location of PIC Offline ButtonLabelon theFPC FaceplateFPC
E FPC1Enhanced FPC1 (EOL)
E-II FPC1Enhanced II FPC1
E FPC2Enhanced FPC2 (EOL)
E-II FPC2Enhanced II FPC2
PIC faceplateNoneFPC3
E FPC3Enhanced FPC3 (EOL)
E-II FPC3Enhanced II FPC3
Figure 13 on page 21 shows the standard FPCs supported by the T320 router. The enhanced FPCs look similar to the standard FPCs.
Method of Securingthe PIC to the FPC
Two captive screwsFPC faceplate above thePICsNoneFPC1
Two captive screwsPIC faceplateNoneFPC2
Plastic ejector handle at the top of the PIC faceplate
Captive screw at the bottom of the PIC faceplate
Copyright © 2010, Juniper Networks, Inc.20
FPC2
FPC3
PIC0
PIC1
ONLINE/ OFFLINE
ONLINE/ OFFLINE
FPC1
g002274
Chapter 3: T320 Hardware Components
Figure 13: Standard FPC1, FPC2, and FPC3 Supported by the T320 Router
Figure 14 on page 21 shows the Enhanced II FPCs supported by the T320 router.
Figure 14: Enhanced II FPC1, FPC2, and FPC3 Supported by the T320 Router
Documentation
Related
T320 FPCs Supported on page 22
T320 Router FRU Overview on page 137
Maintaining T320 FPCs on page 116
Troubleshooting the T320 FPCs on page 133
21Copyright © 2010, Juniper Networks, Inc.
T320 Core Router Hardware Guide
Replacing a T320 FPC on page 177
T320 FPCs Supported
T320 routers support the Flexible PIC Concentrators (FPCs) listed in Table 4 on page 22.
Table 4: FPCs Supported by the T320 Router
FPC Type
Documentation
Related
T320 Flexible PIC Concentrators (FPCs) Description on page 16
T320 PICs Supported
Maximum Number of PICsFPC Model NumberFPC Name
Maximum Throughput (Full-Duplex)
First Junos OS Release Supported
5.52 Gbps2T320-FPC1FPC11
6.32 Gbps2T320-FPC1-EEnhanced FPC1 (EOL)1
7.42 Gbps2T320-FPC1-E2Enhanced II FPC11
5.48 Gbps2T320-FPC2FPC22
6.38 Gbps2T320-FPC2-EEnhanced FPC2 (EOL)2
7.48 Gbps2T320-FPC2-E2Enhanced II FPC22
5.420 Gbps2T320-FPC3FPC33
6.320 Gbps2T320-FPC3-EEnhanced FPC3 (EOL)3
7.420 Gbps2T320-FPC3-E2Enhanced II FPC33
T320 PIC/FPC Compatibility

T320 PIC Description

PICs provide the physical connection to various network media types,receiving incoming packets from the network and transmitting outgoing packets to the network. During this process, each PIC performs framing and line-speed signaling for its media type. Before transmitting outgoing data packets, the PICs encapsulate the packets received from the FPCs. Each PIC is equipped with an ASIC that performs control functions specific to the media type of that PIC.
PICs are hot-removable and hot-insertable. You can install up to two or four PICs into the slots in each FPC. PICs used in a Type 1 FPC or Type 2 FPC have captive screws at their upper and lower corners. Type 3 PICs have an upper ejector handle and a lower captive screw.
Copyright © 2010, Juniper Networks, Inc.22
Chapter 3: T320 Hardware Components
The router supportsvarious PICs,including ATM, Channelized, GigabitEthernet, IPServices, and SONET/SDH interfaces.
Blank PICs resemble other PICs but do not provide any physical connection or activity. When a slot is not occupied by a PIC, you must insert a blank PIC to fill the empty slot and ensure proper cooling of the system.
Related
Documentation
Maintaining T320 PICs and PIC Cables on page 121
Troubleshooting the T320 PICs on page 134
Replacing a T320 PIC on page 182

T320 Switch Interface Boards (SIBs) Overview

T320 Switch Interface Boards (SIBs) Description on page 23
T320 SIB LEDs on page 24
T320 Switch Interface Boards (SIBs) Description
The Switch Interface Boards (SIBs) provide the switching function to the destination FPC (see Figure 15 on page 24). The SIBs create the switch fabric for the router, providing up to a total of 385 million packets per second (Mpps) of forwarding.
Three SIBs are installed inthe router.The SIBsare locatedat thecenter rear of the chassis in the slots labeled SIB0 through SIB2 (top to bottom).
Each Type 1 FPC and Type 2 FPC has one dedicated ASIC with five high-speed links that connect to the SIBs (one link per SIB). SIB0 acts as a backup to SIB1 and SIB2.
Two high-speed links connect to SIB1 and SIB2.
One high-speed link connects to SIB0.
A Type 3 FPC has two dedicated ASICs, and each ASIC has five high-speed links that connect to the SIBs. One of the three SIBs—usually SIB0—acts as a backup to the remaining two SIBs. In the event of a SIB failure, the backup SIB becomes active and traffic forwarding continues without any degradation. When the failed SIB is replaced, it becomes the new backup.
SIBs are hot-insertable and hot-removable.
23Copyright © 2010, Juniper Networks, Inc.
T320 Core Router Hardware Guide
Figure 15: T320 SIB
Each SIB consists of the following components:
Switch Fabric ASICs.
High-speed links (HSLs) to each FPC.
Three LEDs located on the SIB faceplate that display the status of the SIB.“T320 SIB LEDs” on page 24 describes the functions of the SIB LEDs. If all three LEDs are off, the SIB is not receiving power. The OK and FAIL LEDs are replicated on the craft interface.
Related
Documentation
T320 SIB LEDs
SIB online/offline button, located on the SIB faceplate.
T320 SIB LEDs on page 24
Maintaining the T320 SIBs on page 123
Replacing a T320 SIB on page 174
Table 5 on page 24 describes the functions of theT320 SIB LEDs. If all three LEDs are off, the SIB is not receiving power. The craft interface has three additional LEDs that show the status of each SIB.
Table 5: T320 SIB LEDs
DescriptionStateColorLabel
SIB is in active mode.On steadilyGreenACTIVE
SIB is functioning normally.On steadilyGreenOK
SIB is starting up.Blinking
SIB has failed.On steadilyYellowFAIL
Related
Documentation
T320 Switch Interface Boards (SIBs) Description on page 23
Maintaining the T320 SIBs on page 123
Copyright © 2010, Juniper Networks, Inc.24
Replacing a T320 SIB on page 174

T320 Host Subsystem Description

The host subsystem provides the routing and system management functions of the router. You can install one or two host subsystems on the router. To operate, each host subsystem functions as a unit; the Routing Engine requires the corresponding T-CB, and vice versa.
NOTE: We recommend you install two host subsystems for redundant
protection.If you install only one host subsystem, we recommend you install it in slot RE0.
Each host subsystem has three LEDs that display its status. The host subsystem LEDs are located on the upper right of the craft interface. For more information about the host subsystem LEDs, see “T320 Craft Interface Host Subsystem LEDs” on page 38.
Chapter 3: T320 Hardware Components
The host subsystem consists of the following components:
One or two Routing Engines
One or two control boards
Related
Documentation
Maintaining the T320 Host Subsystem on page 113
Replacing the T320 Host Subsystem Components on page 160
Taking the T320 Host Subsystem Offline on page 160

T320 Routing Engine Overview

T320 Routing Engine Description on page 25
T320 RE-600 Description on page 26
T320 RE-600 LEDs on page 28
T320 RE-1600 Description on page 28
T320 RE-1600 LEDs on page 29
T320 RE-2000 Description on page 30
T320 RE-2000 LEDs on page 31
T320 Routing Engine Description
The Routing Engine runs Junos OS. Software processes that run on the Routing Engine maintain the routing tables, manage the routing protocols used on the router, control the router interfaces, control some chassis components, and provide the interface for system management and user access to the router.
25Copyright © 2010, Juniper Networks, Inc.
T320 Core Router Hardware Guide
You can install one or two Routing Engines in the router. The Routing Engines install into the upper rear of the chassis in the slots labeled RE0 and RE1. If two Routing Engines are installed, one functions as the master and the other acts as the backup. If the master Routing Engine fails or is removed,and the backup is configured appropriately, the backup takes over as the master.
If the host system is redundant, the backup Routing Engine is hot-removable and hot-insertable, but the master Routing Engine is hot-pluggable. A Routing Engine that is not redundant is hot-pluggable. Each Routing Engine requires a T-CB to be installed in the adjacent slot. RE0 installs below CB0, and RE1 installs above CB1. A Routing Engine does not power up without a T-CB present in the adjacent slot.
NOTE: The LEDs that report host module status (including Routing Engine
status) are on the craft interface rather than the Routing Engine faceplate.
NOTE: For specific information about Routing Engine components (for example, the amount of DRAM), issue the show chassis routing-engine command.
Related
Documentation
T320 Routing Engine Functions
Maintaining the T320 Routing Engines on page 114
Replacing a T320 Routing Engine on page 168
T320 RE-600 Description
The RE-600 Routing Engine boots from the storage media in this order: the PC Card (if present), then the CompactFlash card (if present), then the hard disk. The disk from which the router bootsis calledthe primary boot device, and the other diskis the alternate boot device.
NOTE: If two Routing Engines are installed, they must both be the same
hardware model.
NOTE: If the router boots froman alternateboot device,a yellow alarmlights the LED on the router’s craft interface.
Copyright © 2010, Juniper Networks, Inc.26
Chapter 3: T320 Hardware Components
Figure 16: T320 Routing Engine 600
The Routing Engine 600 (shown in Figure 16 on page 27) consists of the following components:
CPU—Runs Junos OS to maintain the router's routing tables and routing protocols.
DRAM—Provides storage for the routing and forwarding tables and for other Routing Engine processes.
CompactFlash card—Providesprimary storagefor software images, configuration files, and microcode. The driveis afixed CompactFlash card andis inaccessible from outside the router.
Hard disk—Provides secondary storage for log files, memory dumps, and rebooting the system if the CompactFlash card fails.
PC card slot labeled PC CARD—Accept a removable PC card, which stores software images for system upgrades. The PC card slot accepts a Type I PC Card, as defined in the PC Card Standard published by the Personal Computer Memory Card International Association (PCMCIA). The router is shipped with a PC Card that contains Junos OS. The PC Card can be used to copy Junos OS from the PC Card onto the Routing Engine. You can also copy Junos OS from the Routing Engine onto a PC Card, for example, to create a backup copy of upgrade software that you have obtained from Juniper Networks. Instructions for copying software to a PC Card are available at the Juniper NetworksSupport Web site (http://www.juniper.net/support/); after logging in, navigate to the Customer Support Center, then to the download page for Junos OS.
NOTE: The software on a PC Card is loaded only onto the Routing Engine
into which the PC Card is inserted. It is not automatically copied to the other Routing Engine.
LED—Indicatesdisk activityfor theinternal IDE interface. It does not necessarilyindicate routing-related activity.
Interfaces for out-of-band management access—Provide information about Routing Engine status to devices (console, laptop, or terminal server) that can be attached to access ports located on the Connector Interface Panel (CIP).
27Copyright © 2010, Juniper Networks, Inc.
T320 Core Router Hardware Guide
Each Routing Engine has one 10/100-Mbps Ethernet port for connecting to a management network, and two asynchronous serial ports—one for connecting to a console and one for connecting to a modem or other auxiliary device.
EEPROM—Stores the serial number of the Routing Engine.
Reset button—Reboots the Routing Engine when pressed.
Related
Documentation
T320 Routing Engine Functions
Maintaining the T320 Routing Engines on page 114
Replacing a T320 Routing Engine on page 168
T320 RE-600 LEDs
The HD LED indicates activity on the hard drive. It does not necessarily indicate routing-related activity.
Related
Documentation
T320 Routing Engine Functions
Maintaining the T320 Routing Engines on page 114
Replacing a T320 Routing Engine on page 168
T320 RE-1600 Description
Figure 17: T320 Routing Engine 1600
NOTE: The LEDs that report host module status (including Routing Engine status) are on the craft interface rather than the Routing Engine faceplate.
The Routing Engine 1600 (shown in Figure 17 on page 28) consists of the following components:
CPU—Runs Junos OS to maintain the router's routing tables and routing protocols.
DRAM—Provides storage for the routing and forwarding tables and for other Routing Engine processes.
Copyright © 2010, Juniper Networks, Inc.28
Chapter 3: T320 Hardware Components
EEPROM—Stores the serial number of the Routing Engine.
LED—Indicatesdisk activityfor theinternal IDE interface. It does not necessarilyindicate routing-related activity.
Interfaces for out-of-band management access—Provide information about Routing Engine status to devices (console, laptop, or terminal server) that can be attached to access ports located on the Connector Interface Panel (CIP).
Each Routing Engine has one 10/100-Mbps Ethernet port for connecting to a management network, and two asynchronous serial ports—one for connecting to a console and one for connecting to a modem or other auxiliary device.
Reset button—Reboots the Routing Engine when pressed.
CompactFlash card—Providesprimary storagefor software images, configuration files, and microcode. The driveis afixed CompactFlash card andis inaccessible from outside the router.
Hard disk—Provides secondary storage for log files, memory dumps, and rebooting the system if the CompactFlash card fails.
Related
Documentation
PC card slots—Accept a removable PC card, which stores software images for system upgrades.
The PC cardslots accept aTypeI PCCard,as definedin thePC Card Standard published by the Personal Computer Memory Card International Association (PCMCIA). The router is shipped with a PC Card that contains Junos OS. The PC Card can be used to copy Junos OS from the PC Card onto the Routing Engine. You can also copy Junos OS from the Routing Engine onto a PC Card, for example, to create a backup copy of upgrade software that you have obtained from Juniper Networks. Instructions for copying software to a PC Card are available at the Juniper Networks Support Web site (http://www.juniper.net/support/); after logging in, navigate to the Customer Support Center, then to the download page for Junos OS.
The disk from which the router boots is called the primary boot device, and the other disk is the alternate boot device.The RE-1600 Routing Engine boots from the storage media in this order: the PC Card in SLOT 0 (if present), then the PC Card in SLOT 1 (if present), then the CompactFlash card (if present), then the hard disk.
NOTE: If the router boots froman alternateboot device,a yellow alarmlights
the LED on the router’s craft interface.
T320 Routing Engine Functions
Maintaining the T320 Routing Engines on page 114
T320 RE-1600 LEDs
Replacing a T320 Routing Engine on page 168
Table 6 on page 30 describes the functions of these LEDs.
29Copyright © 2010, Juniper Networks, Inc.
T320 Core Router Hardware Guide
Table 6: RE-1600 LEDs
DescriptionStateColorLabel
Slot LEDs 0 and 1
Related
Documentation
T320 Routing Engine Functions
Maintaining the T320 Routing Engines on page 114
Replacing a T320 Routing Engine on page 168
T320 RE-2000 Description
Figure 18: Routing Engine 2000 (RE-2000)
YellowHD
Green alternately
blinking
BlinkingRed and
On steadilyGreen
Indicates activity on the hard drive.On steadily or
Indicates that the Routing Engine is booting and the firmware is checking if a PC card is installed.
Indicates that the RoutingEngine booted from the PC Card.
Each RE-2000 (shown in Figure 18 on page 30) consists of the following components:
CPU—Runs Junos OS to maintain the router's routing tables and routing protocols.
DRAM—Provides storage for the routing and forwarding tables and for other Routing Engine processes.
EEPROM—Stores the serial number of the Routing Engine.
Interfaces for management access—Provide information about Routing Engine status to devices (console, laptop, or terminal server) connected to the Routing Engine ports located on the CIP.
CompactFlash card—Providesprimary storagefor software images, configuration files, and microcode. The fixed CompactFlash card is inaccessible from outside the router.
Hard disk—Provides secondary storage for log files, memory dumps, and rebooting the system if the CompactFlash card fails.
Copyright © 2010, Juniper Networks, Inc.30
Chapter 3: T320 Hardware Components
The disk from which the router boots is called the primary boot device, and the other disk is the alternate boot device. The RE-2000 Routing Engine boots from the storage media in this order: the USB device, then the CompactFlash card (ifpresent), then the hard disk, then the LAN.
NOTE: If the router boots froman alternateboot device,a yellow alarmlights
the LED on the router’s craft interface.
The faceplate of the RE-2000 contains the following:
USB port—Provides a removable media interface through which you can install the Junos OS manually. Junos OS supports USB version 1.0.
Reset button—Reboots the Routing Engine when pressed.
Offline button—Takes the Routing Engine offline when pressed.
Extractor clips—Control the locking system that secures the Routing Engine.
LEDs—“T320 RE-2000 LEDs” on page 31 describes the functions of these LEDs.
Related
Documentation
T320 RE-2000 LEDs
T320 Routing Engine Functions
Maintaining the T320 Routing Engines on page 114
Replacing a T320 Routing Engine on page 168
Table 7 on page 31 describes the functions of the LEDs on the faceplate of the Routing Engine.
NOTE: The LEDs on the Routing Engine do not necessarily indicate
routing-related activity.
Table 7: Routing Engine 2000 LEDs
DescriptionStateColorLabel
Indicates disk activity for the hard disk drive.On steadilyBlueHDD
Routing Engine is functioning normally.On steadilyGreenONLINE
Routing Engine is transitioning online.Blinking
Related
Documentation
Routing Engine has failed.On steadilyRed
T320 Routing Engine Functions
Maintaining the T320 Routing Engines on page 114
31Copyright © 2010, Juniper Networks, Inc.
T320 Core Router Hardware Guide
Replacing a T320 Routing Engine on page 168

T320 Control Boards Overview

T320 T-CB Description on page 32
T320 T-CB LEDs on page 33
T320 T-CB Description
This chassis supports up to two control boards. The Routing Engine requires an adjacent control board to provide control and monitoring functions for the router (see Figure 19 on page 33). These functionsinclude determining Routing Engine mastership; controlling power and reset for the other router components; monitoring and controlling fan speed; and monitoring system status.
You can install upto two control boards inthe router.Control boards installinto theupper rear of the chassis in the slots labeled CB0 and CB1 (referred to as CB-0 and CB-1, top to bottom). If two control boards are installed, one functions as the master and the other as its backup. If the master fails or is removed, the backup restarts and becomes the master.
Each control board requires a Routing Engine to be installed in the adjacent slot. CB0 installs above RE0, and CB1 installs belowRE1. Controlboards can notfunction if a Routing Engine is not present in the adjacent slot.
If the host system is redundant, the backup control board is hot-removable and hot-insertable, but the master control board is hot-pluggable. A control board that is not redundant is hot-pluggable.
Each consists of the following components:
100-MB Ethernet switch for intermodule communication.
PCI bus to the Routing Engines.
Processor subsystem (SPMB).
Three LEDs, located on the control board faceplate, indicate its status.“T320 T-CB LEDs” on page 33 describes the functions of the control board LEDs.
The control board online/offline button, located on the its faceplate. This button is not functional.
Two configuration switches, located on the T-CB faceplate. On the T320 router, the M/S and CHASSIS ID switches must always be set to S and O.
Two RJ-45 ports labeled AUX and CIP on the T-CB faceplate. These ports are not used in a T320 router.
Copyright © 2010, Juniper Networks, Inc.32
Figure 19: T320 control board
Chapter 3: T320 Hardware Components
Related
Documentation
T320 T-CB LEDs
Related
Documentation
T320 Chassis Description on page 12
Maintaining the T320 T-CBs on page 115
Replacing a T320 T-CB on page 162
Table 8 on page 33 describes the functions of the T-CB LEDs.
Table 8: T320 T-CB LEDs
DescriptionStateColorLabel
T-CB is functioning as the master.On steadilyBlueMASTER
T-CB has failed.On steadilyYellowFAIL
T-CB is online and is functioning normally.On steadilyGreenOK
T-CB is powering up, but not online.Blinking
T320 Chassis Description on page 12
Maintaining the T320 T-CBs on page 115
Replacing a T320 T-CB on page 162

T320 SONET Clock Generators (SCGs) Overview

T320 Standard SONET Clock Generator (SCG) Description on page 34
T320 SCG LEDs on page 34
33Copyright © 2010, Juniper Networks, Inc.
T320 Core Router Hardware Guide
T320 Standard SONET Clock Generator (SCG) Description
The SONET Clock Generators (SCGs) provide 19.44-MHz Stratum 3 clock signal for the SONET/SDH interfaces on the router (see Figure 20 on page 34).
One SCG is shipped as part of the standard router configuration, but up to two SCGs can be installed to provide redundancy. SCGs are installed into the upper rear of the chassis in the slots labeled SCG0 and SCG1.
The SCGs are hot-pluggable.
Each standard SCG consists of the following components:
19.44-MHz Stratum 3 clock.
Field-programmable gate array (FPGA) that performs multiplexing of clock sources.
Three LEDs, located on the SCG faceplate, that display the status of the SCG.“T320 SCG LEDs” on page 34 describes the functions of the SCG LEDs.
SCG online/offline button, located on the SCG faceplate.
Related
Documentation
T320 SCG LEDs
Two external clock inputs.
NOTE: The external clock inputs on the standard SCG are not supported.
Figure 20: T320 SCG
Maintaining the T320 SCGs on page 115
Replacing a T320 SCG on page 171
Locating the T320 SCG Serial Number Label on page 265
Table 9 on page 34 describes the functions of the SCG LEDs.
Table 9: T320 SCG LEDs
DescriptionStateColorLabel
SCG is online and is functioning normally.On steadilyGreenOK
Copyright © 2010, Juniper Networks, Inc.34
Table 9: T320 SCG LEDs (continued)
DescriptionStateColorLabel
SCG has failed.On steadilyYellowFAIL
SCG is functioning as master.On steadilyBlueMASTER
Chapter 3: T320 Hardware Components
Related
Documentation
Maintaining the T320 SCGs on page 115
Replacing a T320 SCG on page 171
Locating the T320 SCG Serial Number Label on page 265

T320 Craft Interface Overview

T320 Craft Interface Description on page 35
T320 Craft Interface Alarm LEDs and ACO/LT Button on page 36
T320 Craft Interface LCD and Navigation Buttons on page 36
T320 Craft Interface Host Subsystem LEDs on page 38
T320 Craft Interface SIB LEDs on page 38
T320 Craft Interface FPC LEDs on page 39
T320 Connector Interface Panel (CIP) Description on page 40
T320 Routing Engine Ports on page 41
T320 Alarm Relay Contacts on page 42
T320 Craft Interface Description
The craft interface allows you to view status and troubleshooting information at a glance and to perform many system control functions. It is hot-insertable and hot-removable. The craft interface is located on the front of the router above the FPCs and contains:
Figure 21: Front Panel of the T320 Craft Interface
Related
Documentation
T320 Chassis Description on page 12
Troubleshooting Using the T320 Craft Interface LEDs on page 128
Replacing a T320 Craft Interface on page 158
35Copyright © 2010, Juniper Networks, Inc.
T320 Core Router Hardware Guide
T320 Craft Interface Alarm LEDs and ACO/LT Button
Two large alarm LEDs are located at the upper left of the craft interface (see Figure 21 on page 35). The circular red LED lights to indicate a critical condition that can result in a system shutdown. The triangular yellow LED lights to indicate a less severe condition that requires monitoring or maintenance. Both LEDs can be lit simultaneously.
A condition that causes an LED to light also activates the corresponding alarm relay contact on the connector interface panel (CIP), as described in “T320 Alarm Relay Contacts” on page 42. The LCD on the craft interface reports the cause of the alarm, as described in “T320 Craft Interface LCD and Navigation Buttons” on page 36.
To deactivate red and yellow alarms, press the button labeled ACO/LT (for “alarm cutoff/lamp test”), which is located to the right of the alarm LEDs. Deactivating analarm turns off both LEDs and deactivates the device attached to the corresponding alarm relay contact on the CIP. However, the LCD continues to report the alarm message until you clear the condition that caused the alarm.
Table 10 on page 36 describes the alarm LEDs and alarm cutoff button in more detail.
Table 10: T320 Alarm LEDs and Alarm Cutoff/Lamp Test Button
On steadilyRed
On steadilyYellow
Related
Documentation
T320 Chassis Description on page 12
Troubleshooting Using the T320 Craft Interface LEDs on page 128
Replacing a T320 Craft Interface on page 158
T320 Craft Interface LCD and Navigation Buttons
A four-line LCD is located in the craft interface, along with six navigation buttons. The LCD operates in two modes:
DescriptionStateColorShape
Critical alarm LED—Indicates a criticalcondition that can cause the router to stop functioning. Possible causes include component removal, failure, or overheating.
Warningalarm LED—Indicatesa seriousbut nonfatal error condition, such as a maintenance alert or a significant increase in component temperature.
Alarm cutoff/lamp test button—Deactivates red and yellowalarms. Causesall LEDs on the craft interface to light (for testing) when pressed and held.
LED Idle Mode
LED Alarm Mode
Copyright © 2010, Juniper Networks, Inc.36
Chapter 3: T320 Hardware Components
During normal operation, the LCD operates in idle mode and reports current status information, as shown in Figure 22 on page 37.
Figure 22: T320 LCD in Idle Mode
The lines in the display report the following information:
First line—Router name.
Second line—Length of time the router has been running, reported in the following form:
Up days + hours:minutes
Third and fourth lines—Status messages, which rotate at 2-second intervals. Some conditions, such as removal or insertion of a system component, can interrupt the messages.
To add a message that alternates every 2 seconds with the default status messages, use the set chassis display message command. For more information, see the Junos OS System Basics and Services Command Reference.
When a red or yellow alarm occurs, the LCD switches to alarm mode and reports about the alarm condition, as shown in Figure 23 on page 37.
Figure 23: T320 LCD in Alarm Mode
The lines in the display report the following information:
First line—Router name.
Second line—Number of active alarms.
Third and fourth lines—Individual alarm messages, with the most severe condition shown first. The prefix oneach line indicates whether the alarm isa red(R) or yellow (Y) alarm.
For a list of alarm messages that can appear on the LCD, see “Troubleshooting Using the T320 Chassis and Interface Alarm Messages” on page 129.
Related
Documentation
T320 Craft Interface Description on page 35
T320 Craft Interface Alarm LEDs and ACO/LT Button on page 36
37Copyright © 2010, Juniper Networks, Inc.
T320 Core Router Hardware Guide
T320 Craft Interface Host Subsystem LEDs on page 38
T320 Craft Interface Host Subsystem LEDs
Each host subsystem has three LEDs, located on the upper right of the craft interface, that indicate its status. The LEDs labeled HOST0 show the status of the Routing Engine in slot RE0 and the T-CB in slot CB0. The LEDs labeled HOST1 show the status of the Routing Engine in slot RE1 and the T-CB in slot 1. Table 11 on page 38 describes the functions of the host subsystem LEDs.
Table 11: T320 Host Subsystem LEDs
DescriptionStateColorLabel
Host is offline.On steadilyRedFAIL
Host is online and is functioning normally.On steadilyGreenOK
Host is functioning as the master.On steadilyGreenMASTER
Related
Documentation
T320 Chassis Description on page 12
Troubleshooting Using the T320 Craft Interface LEDs on page 128
Replacing a T320 Craft Interface on page 158
T320 Craft Interface SIB LEDs
Each SIBhas two LEDson the craft interfacethat indicate its status. The SIB LEDs, labeled
SIB0 through SIB4, are located on the upper right of the craft interface. The ACTIVE LED
is not replicated on the craft interface. Table 12 on page 38 describes the functions of the SIB LEDs.
Table 12: SIB LEDs on the Craft Interface
Related
Documentation
T320 Chassis Description on page 12
Troubleshooting Using the T320 Craft Interface LEDs on page 128
Replacing a T320 Craft Interface on page 158
DescriptionStateColorLabel
SIB has failed.On steadilyRedFAIL
SIB is functioning normally.On steadilyGreenOK
Copyright © 2010, Juniper Networks, Inc.38
T320 Craft Interface FPC LEDs
Each FPC slot has two LEDs that indicate its status.The FPC LEDs, labeled FPC0 through
FPC7, are located along the bottom of the craft interface. Table 13 on page 39 describes
the functions of the FPC LEDs.
Table 13: FPC LEDs
Chapter 3: T320 Hardware Components
DescriptionStateColorLabel
FPC has failed.On steadilyRedFAIL
FPC is functioning normally.On steadilyGreenOK
FPC is starting up.Blinking
39Copyright © 2010, Juniper Networks, Inc.
T320 Core Router Hardware Guide
Related
Documentation
T320 Chassis Description on page 12
Troubleshooting Using the T320 Craft Interface LEDs on page 128
Replacing a T320 Craft Interface on page 158
T320 Connector Interface Panel (CIP) Description
The Connector Interface Panel (CIP) consists of Ethernet, console, and auxiliary connectors for the Routing Engines and alarm relay contacts (see Figure 24 on page 41). The front electrostatic discharge point is located near the bottom of the CIP. The CIP is located at the left side of the FPC card cage.
The CIP is hot-pluggable.
Copyright © 2010, Juniper Networks, Inc.40
Figure 24: CIP
Chapter 3: T320 Hardware Components
Related
Documentation
T320 Chassis Description on page 12
Replacing the T320 CIP and Routing Engine Interface Port Cables on page 139
Locating the T320 CIP Serial Number Label on page 261
T320 Routing Engine Ports
The CIP has two sets of ports that you use to connect the Routing Engines to external management devices. Fromthese management devices, youcan use theCLI toconfigure the router.
41Copyright © 2010, Juniper Networks, Inc.
T320 Core Router Hardware Guide
The upper set of ports, labeled HOST 0, connects to the Routing Engine in slot RE0; and the lower set, labeled HOST 1, connectsto theRouting Enginein slotRE1. Eachset includes the following ports:
ETHERNET—Connects the Routing Engine through an Ethernet connection to a
management LAN (or any other device that plugs into an Ethernet connection) for out-of-band management. The port uses an autosensing RJ-45 connector to support both 10- and 100-Mbps connections. Two small LEDs on the left edge of the port indicate the connection in use: the yellow LED lights for a 10-Mbps connection and the green LED lights for a 100-Mbps connection.
CONSOLE—Connects the Routing Engine to a system console through an RS-232
(EIA-232) serial cable.
AUXILIARY—Connects theRouting Engine to a laptop,modem, or other auxiliary device
through an RS-232 (EIA-232) serial cable.
Related
Documentation
T320 Connector Interface Panel (CIP) Description on page 40
Replacing the T320 Connections to Routing Engine Interface Ports on page 142
T320 DB-9 Connector Pinouts for the Routing Engine AUXILIARY and CONSOLE Ports
on page 258
T320 RJ-45 Connector Pinouts for the Routing Engine ETHERNET Port on page 257
T320 Alarm Relay Contacts
The CIPhas two alarm relay contacts for connecting the router to external alarmdevices. Whenever a system condition triggers eitherthe red oryellowalarm onthe craft interface, the alarm relay contacts are also activated. The alarm relay contacts are located below the Routing Engine ports. The terminal blocks that plug into the alarm relay contacts are supplied with the router. They accept wire of any gauge between 28-AWG and 14-AWG (0.08 and 2.08 mm2), which is not provided. Use the gauge of wire appropriate for the external device you are connecting.
Related
Documentation
T320 Connector Interface Panel (CIP) Description on page 40
T320 Routing Engine Ports on page 41
Replacing the T320 Alarm Relay Wires on page 146
T320 Routing Engine Interface Cable and Wire Specifications on page 256

T320 Power System Overview

T320 Power System Description on page 42
T320 Power Supply LEDs on page 43
T320 Power System Description
The T320 Core Router supports DC power only. The routeris equippedwith two redundant, load-sharing DC power supplies (see Figure 25 on page 43), located at the lower rear of
Copyright © 2010, Juniper Networks, Inc.42
Chapter 3: T320 Hardware Components
the chassis in slots PEM0 and PEM1 (top to bottom). Each power supply has one input, which has its own circuit breaker, and which requires a dedicated DC power source. The power supplies connect to the midplane, which distributes the different output voltages produced by the power supplies to the router components, depending on their voltage requirements.
When the router is operating normally and both power supplies are switched on, load-sharing between them occurs automatically. When one power supply fails or is turned off, the other power supply immediately assumes the entire electrical load for the system. A single power supply can provide full power for as long as the router is operational.
Power supplies are hot-removable and hot-insertable. Each power supply is cooled by its own internal cooling system.
Figure 25: T320 Power Supply
For power supply and power system electrical specifications, see “T320 Power System Electrical Specifications” on page 245.
Related
Documentation
Powering On the T320 Router on page 102
Maintaining the T320 Power Supplies on page 124
T320 Power Supply LEDs
One LED on each power supply faceplate indicated the status of the power supply. In addition, a power supply failure triggers the red alarm LED on the craft interface. Table 14 on page 43 describes the functions of the power supply LEDs.
Table 14: T320 Power Supply LED
Blinking
DescriptionStateColorLED
No power applied to power supply.OffBlueDC OK
Power supply LED blinks for five seconds after initial power on.
Power supply is installed, but not powered on, and is receiving bias power from a powered on power supply.
Input voltage is invalid.
43Copyright © 2010, Juniper Networks, Inc.
T320 Core Router Hardware Guide
Table 14: T320 Power Supply LED (continued)
DescriptionStateColorLED
Power supply has failed.
Related
Documentation
T320 Power System Description on page 42
Powering On the T320 Router on page 102
Maintaining the T320 Power Supplies on page 124

T320 Cooling System Description

The cooling system consists of the following components:
Two front fan trays
Front air filter
Rear fan tray
Rear air filter
The cooling system components work together to keep all router components within the acceptable temperature range (see Figure 26 on page 44). All fan trays and filters are hot-insertable and hot-removable. The two front fan trays are interchangeable. The front and rear fan trays are not interchangeable.
On steadily
Power supply is installed correctly and is functioning normally.
Figure 26: Airflow Through the T320 Chassis
The host subsystem monitors the temperature of the router components. When the router is operating normally, the fans function at lower than full speed. If a fan fails or the ambient temperature rises above a threshold, the speed of the remaining fans is automatically adjusted to keep the temperature within the acceptable range. If the
Copyright © 2010, Juniper Networks, Inc.44
Chapter 3: T320 Hardware Components
ambient maximum temperature specification is exceeded and the system cannot be adequately cooled, the Routing Engine shuts down some or all of the hardware components.
Related
Documentation
Maintaining the T320 Air Filters on page 112
Maintaining the T320 Fan Trays on page 113
Troubleshooting the T320 Cooling System on page 132
Replacing the T320 Cooling System Components

T320 Cable Management System Description

The cable management system (see Figure 27 on page 45) consists of a row of nine semicircular plastic bobbins mounted on the front of therouter below the FPC card cage. The PIC cables pass between the bobbins and into the tray, keeping the cables organized and securely in place. The curvature of the bobbins also helps maintain the proper bend radius for optical PIC cables.
You can pull the cable management system up and outward to lock it into the maintenance position. This allows you to access the lower fan tray and the front air filter.
Figure 27: T320 Cable Management System
Related
Documentation
T320 Router Description on page 3
T320 Chassis Description on page 12
Removing the T320 Cable Management System on page 79
45Copyright © 2010, Juniper Networks, Inc.
T320 Core Router Hardware Guide
Copyright © 2010, Juniper Networks, Inc.46
PART 2
T320 Router Initial Installation
Preparing for T320 Router Installation on page 49
Unpacking the T320 Router on page 53
Installing the T320 Router Mounting Hardware on page 59
Installing the T320 Router Using a Mechanical Lift on page 67
Installing the T320 Router Without a Mechanical Lift on page 73
Connecting the T320 Router on page 93
Providing Power to the T320 Router on page 99
Performing the Initial T320 Junos OS Configuration on page 105
47Copyright © 2010, Juniper Networks, Inc.
T320 Core Router Hardware Guide
Copyright © 2010, Juniper Networks, Inc.48
CHAPTER 4
Preparing for T320 Router Installation
T320 Site Preparation Checklist Requirements on page 49
T320 Rack Requirements on page 50
T320 Clearance Requirements for Airflow and Hardware Maintenance on page 51

T320 Site Preparation Checklist Requirements

The checklist in Table 15 on page 49 summarizes the tasks you need to perform when preparing a site for router installation.
Table 15: T320 Site Preparation Checklist
DatePerformed ByFor More InformationItem or Task
Environment
Verify that environmental factors such as temperatureand humidity donot exceedrouter tolerances.
“T320 Physical Specifications” on page 241
Power
Measure distance between external power sources and router installation site.
Locate sites for connection of system grounding.
Calculate the power consumption and requirements.
Rack
Verify that your rack meets the minimum requirements for the installation of the router.
Plan rack location, including required space clearances.
If arack isused, secure rack tofloor andbuilding structure.
“T320 DC Power Cable Specifications” on page 248
“T320 Chassis Grounding Cable and Lug Specifications” on page 247
“T320 Power Requirements” on page 246
“T320 Rack Requirements” on page 50
“T320 Clearance Requirements for Airflow and Hardware Maintenance” on page 51
“T320 Rack Requirements” on page 50
49Copyright © 2010, Juniper Networks, Inc.
T320 Core Router Hardware Guide
Table 15: T320 Site Preparation Checklist (continued)
Cables
Acquire cables and connectors:
Determine the number of cables needed based on your planned configuration.
Review the maximum distance allowed for each cable. Choose the length ofcable based on the distance between the hardware components being connected.
“Calculating Power Budget for Fiber-Optic Cable for M Series, MX Series, and T Series Routers” on page 254
“Calculating Power Margin for Fiber-Optic Cable for M Series, MX Series, and T Series Routers” on page 254
DatePerformed ByFor More InformationItem or Task
Plan the cable routing and management.
Related
Documentation
T320 Router Installation Summary on page 53
Safety Requirements, Warnings, and Guidelines for Installing the T320 Router on
page 67
T320 Chassis Lifting Guidelines on page 213

T320 Rack Requirements

The T320 Core router can be installed many types of racks, including four-post racks or cabinets and open-frame racks. An example of an open-frame rack appears in Figure 28 on page 51.
The router isdesigned forinstallation in a 19-in. rack as defined in Cabinets, Racks, Panels, and Associated Equipment (document number EIA-310-D) published by the Electronics Industry Association (http://www.eia.org).
With the use of adapters, the router is designed to fit into a 600-mm-wide rack , as defined in the four-part Equipment Engineering (EE); European telecommunications standard for equipment practice (document numbers ETS 300 119-1 through 119-4) published by theEuropean TelecommunicationsStandardsInstitute (http://www.etsi.org). Use approved wing devices to narrow the opening between the rails.
“Maintaining T320 PICs and PIC Cables” on page 121
The rack rails must be spaced widely enough to accommodate the router chassis's external dimensions: 25.13 in. (63.82 cm) high, 31.4 in. (79.8 cm) deep, and 17.43 in. (44.3 cm) wide. The outer edges of the front-mounting flanges and center-mounting brackets extend the width to 19 in. (48.3 cm). The spacing of rails and adjacent racks must also allow for the clearances around the router and rack that are specified in “T320 Clearance Requirements for Airflow and Hardware Maintenance” on page 51.
The chassis height of 25.13 in. (63.82 cm) is approximately 14.4 U. A U is the standard rack unit defined in Cabinets, Racks, Panels, and Associated Equipment (document number EIA-310-D) published by the Electronics IndustryAssociation. Youcan stack three routers in a rack that has at least 44 U (77 in. or 1.96 m) of usable vertical space.
Copyright © 2010, Juniper Networks, Inc.50
Chapter 4: Preparing for T320 Router Installation
The rack must be strong enough to support the weight of the fully configured router, up to approximately 370 lb (168 kg). If you stack three fully configured routers in one rack, it must be capable of supporting about 1110 lb (504 kg).
Figure 28: Typical Open-Frame Rack
Related
Documentation
T320 Chassis Description on page 12
Installing the T320 Mounting Hardware for a Four-Post Rack or Cabinet on page 60
Installing the T320 Mounting Hardware for an Open-Frame Rack on page 63
Safety Requirements, Warnings, and Guidelines for Installing the T320 Router on
page 67

T320 Clearance Requirements for Airflow and Hardware Maintenance

When planning the installation site, you must allow sufficient clearance around the rack (see Figure 29 on page 52):
For the cooling system to function properly, the airflow around the chassis must be unrestricted. Figure 26 on page 44 depicts the airflow in the router.
51Copyright © 2010, Juniper Networks, Inc.
T320 Core Router Hardware Guide
Figure 29: T320 Chassis Dimensions and Clearance Requirements
NOTE: If you mount the router in a cabinet, be sure that ventilation is sufficient to prevent overheating.
For service personnel to remove and install hardware components, there must be adequate space at the front and back of the router. At least 24 in. (61 cm) is required both in front of and behind the router. NEBS GR-63 recommends that you allow at least 30 in. (72.6 cm) in front of the rack.
Related
Documentation
T320 Cooling System Description on page 44
T320 Chassis Description on page 12
Safety Requirements, Warnings, and Guidelines for Installing the T320 Router on
page 67
T320 Physical Specifications on page 241
Copyright © 2010, Juniper Networks, Inc.52
CHAPTER 5
Unpacking the T320 Router
T320 Router Installation Summary on page 53
Tools and Parts Required to Unpack the T320 Router on page 54
Unpacking the T320 Router on page 54
Verifying the T320 Router Parts Received on page 55

T320 Router Installation Summary

Proceed through the installation process in the following order:
1. Prepare your installation site.
See “T320 Site Preparation Checklist Requirements” on page 49 when you are ready to unpack and install the router.
2. Review the safety guidelines.
See “Installation Safety Warnings for M Series, MX Series, and T Series Routers” on page 213.
Related
Documentation
3. Unpack the router and verify the parts received.
4. Install the mounting hardware.
See “Installing the T320 Mounting Hardware for a Four-Post Rack or Cabinet” on page 60 or “Installing the T320 Mounting Hardware for an Open-Frame Rack” on page 63.
5. Install the router.
See “Installing the T320 Router Using a Mechanical Lift” on page 68 or “Installing the T320 Chassis in the Rack Manually” on page 81.
6. Perform the initial system startup.
See “Initially Configuring the T320 Router” on page 105.
T320 Chassis Description on page 12
Safety Requirements, Warnings, and Guidelines for Installing the T320 Router on
page 67
T320 Chassis Lifting Guidelines on page 213
53Copyright © 2010, Juniper Networks, Inc.
T320 Core Router Hardware Guide

Tools and Parts Required to Unpack the T320 Router

To unpack the router and prepare for installation, you need the following tools:
Phillips (+) screwdriver, number 2
1/2-in. or 13-mm open-end orsocket wrench toremove bracket bolts fromthe shipping pallet
Blank panels to cover any slots not occupied by a component
Related
Documentation
T320 Chassis Description on page 12
Safety Requirements, Warnings, and Guidelines for Installing the T320 Router on
page 67
T320 Chassis Lifting Guidelines on page 213

Unpacking the T320 Router

The router is shipped in a wooden crate. A wooden pallet forms the base of the crate. The router chassis is bolted to this pallet. Quick Start installation instructions and a cardboard accessory box are also included in the shipping crate.
The shipping cratemeasures 50 in. (127 cm)high, 30 in. (76.2 cm) wide, and 41 in.(104 cm) deep. The total weight of the crate containing the router and accessories can range from 582 lb (267 kg) to 650 lb (295 kg).
To unpack:
1. Move the shipping crate to a staging area as close to the installation site as possible,
where you have enough room to remove the components from the chassis. While the chassis is bolted to the pallet, you can use a forklift or pallet jack to move it.
NOTE: The router is maximally protected inside the shipping crate. Do not
unpack it until you are ready to begin installation.
2. Position the shipping crate with the arrows pointing up.
3. Open all the latches on the shipping crate.
4. Remove the front door of the shipping crate cover and set it aside.
5. Slide the remainder of the shipping crate cover off the pallet.
6. Remove the foam covering the top of the router.
7. Remove the accessory box and the Quick Start documentation.
8. Verify the parts received.
9. Remove the vapor corrosion inhibitor (VCI) packs attached to the pallet, being careful
not to break the VCI packs open.
Copyright © 2010, Juniper Networks, Inc.54
Chapter 5: Unpacking the T320 Router
10. To remove the brackets holding the chassis on the pallet, use a 1/2-in. socket wrench
and anumber 2 Phillips screwdriver to remove the boltsand screws fromthe brackets.
11. Store the brackets and bolts inside the accessory box.
12. Save the shipping crate cover, pallet, and packing materials in case you need to move
or ship the router at a later time.
13. Proceed with the installation.
Figure 30: Contents of the Shipping Crate
Related
Documentation
T320 Chassis Description on page 12
Verifying the T320 Router Parts Received on page 55
Installing the T320 Router Using a Mechanical Lift on page 68
Installing the T320 Chassis in the Rack Manually on page 81

Verifying the T320 Router Parts Received

A packing list is included in each shipment. Check the parts in the shipment against the items on the packing list. The packing list specifies the part numbers and descriptions of each part in your order.
If any part is missing, contact a customer service representative.
The main shipment contains therouter chassis with installed components,listed inTable 16 onpage 56,and an accessory box, which containsthe partslisted inTable 17 on page 57.
55Copyright © 2010, Juniper Networks, Inc.
T320 Core Router Hardware Guide
Table 16: T320 Router Parts List
QuantityComponent
1Chassis, including midplane, craft interface, and
center-mounting brackets
Up to 8FPCs
Up to 2 per FPCPICs
3SIBs
1 or 2Routing Engines
1 or 2T-CBs
1 or 2SCGs
2Power supplies
Blank panels for slots without components installed
1CIP
2Front fan trays
1Rear fan tray
1Quick start installation
1Front mounting shelf
1Rear mounting shelf
2Spacer bars
One blank panel for each slot not occupied by a component
Copyright © 2010, Juniper Networks, Inc.56
Table 17: T320 Accessory Box Parts List
QuantityPart
1Affidavit for T1 connection
2Connectors for alarm relay cables
1DB-9 (male) to DB-25 (female) adapter
1ESD wrist strap with cable
1Ethernet cable, 15-ft length, to connect
Routing Engine to management device
1 of eachPCMCIA card holder and hook-and-loop
fasteners (male and female)
5DC Power and grounding cable lugs
Chapter 5: Unpacking the T320 Router
Related
Documentation
1Read me first document
2Screws to fasten grounding cable to chassis
Bag of 14Screws to mount chassis
1Serial cable, 6-ft length, to connect Routing
Engine to management console
1Software license agreement
2Washers for grounding cable lug
T320 Chassis Description on page 12
Installing the T320 Router Using a Mechanical Lift on page 68
Installing the T320 Chassis in the Rack Manually on page 81
57Copyright © 2010, Juniper Networks, Inc.
T320 Core Router Hardware Guide
Copyright © 2010, Juniper Networks, Inc.58
CHAPTER 6
Installing the T320 Router Mounting Hardware
Verifying the T320 Rack-Mounting Hardware Received on page 59
Before You Install the T320 Rack-Mounting Hardware on page 59
Installing the T320 Mounting Hardware for a Four-Post Rack or Cabinet on page 60
Installing the T320 Mounting Hardware for an Open-Frame Rack on page 63

Verifying the T320 Rack-Mounting Hardware Received

The following mounting hardware is supplied with the T320 Core Router:
Large mounting shelf—Required for all mounting options
Small mounting shelf—Required only for a four-post rack or cabinet
Front-mounting flanges on the chassis—Required for a four-post rack or cabinet, or for front-mounting in an open-frame rack
Spacer bars attached to the rear of the front-mounting flanges—Required only for a four-post rack or cabinet
Center-mounting brackets—Required for center-mounting in an open-frame rack
Figure 4 on page 13 shows thecenter-mounting brackets and the front-mounting flanges.
Related
Documentation
T320 Chassis Description on page 12
Unpacking the T320 Router on page 54
Verifying the T320 Router Parts Received on page 55

Before You Install the T320 Rack-Mounting Hardware

The router can be installed in a four-post rack or cabinet or an open-frame rack. Before you install the T320 router, you install the mounting hardware on the rack. The procedure for installing the mounting hardware depends on the type of rack and how you are mounting the router.
59Copyright © 2010, Juniper Networks, Inc.
T320 Core Router Hardware Guide
In anopen-frame rack, center-mounting is generally preferableto front-mounting because the more even distribution of weight provides greater stability. If you center-mount the chassis, you use the center-mounting brackets attached to thechassis; ifyou front-mount the chassis, you use the front-mounting flanges.
If you are mounting the router in a four-post rack or cabinet, you must install the spacer bars on the rack before you mount the chassis. For instructions about installing the mounting hardware, see “Installing the T320 Mounting Hardware for a Four-Post Rack or Cabinet” on page 60 or “Installing the T320 Mounting Hardware for an Open-Frame Rack” on page 63, depending on your type of installation.
After the mounting hardware is installed, proceed to “Installing the T320 Router Using a Mechanical Lift” on page 68 or “Installing the T320 Chassis in the Rack Manually” on page 81, depending on your type of installation.
Related
Documentation
T320 Chassis Description on page 12
T320 Clearance Requirements for Airflow and Hardware Maintenance on page 51
Verifying the T320 Router Parts Received on page 55

Installing the T320 Mounting Hardware for a Four-Post Rack or Cabinet

To prepare to install the T320 router into a four-post rack or cabinet:
Install cage nuts, if needed.
Install the large mounting shelf and spacer bars on the front rail.
Install the small mounting shelf on the rear rail.
Remove the center-mounting brackets from the chassis.
Table 18 on page60 specifies the holesin which you insert mounting screws(an X indicates a mounting hole location), and cage nuts if needed. The hole distances are relative to one of the standard U divisions on the rack. The bottom of all mounting shelves is at
0.0015 in. (0.01 U) above a U division.
Table 18: T320 Four-Post or Cabinet Rack Mounting Hole Locations
Large ShelfDistance Above U DivisionHole
Spacer Bars
Small Shelf
X13.86 U24.26 in. (61.6 cm)42
X10.86 U19.01 in. (48.3 cm)33
X7.86 U13.76 in. (34.9 cm)24
XX4.86 U8.51 in. (21.6 cm)15
X3.86 U6.76 in. ( 17.1 cm)12
Copyright © 2010, Juniper Networks, Inc.60
Chapter 6: Installing the T320 Router Mounting Hardware
Table 18: T320 Four-Post or Cabinet Rack Mounting Hole Locations (continued)
Large ShelfDistance Above U DivisionHole
Spacer Bars
Small Shelf
X4.86 U5.01 in. ( 12.7 cm)9
XX1.86 U3.26 in. (8.3 cm)6
X0.86 U1.51 in. (3.8 cm)3
X0.50 U0.88 in. (2.2 cm)2
To install the mounting shelves and spacer bars:
1. Install cage nuts, if needed, in the mounting holes specified in Table 18 on page 60:
On the front rack rails, install cage nuts in the holes specified for the large shelf and the spacer bars.
On the rear rack rails, install cage nuts in the holes specified for the small shelf.
2. On the front of each front rack rail, partially insert a mounting screw into the lowest
hole specified in Table 18 on page 60 for the large shelf and the spacer bars.
3. Install the large shelf on the front rack rails. Rest the bottom slot of each flange on a
mounting screw.
4. Tighten all the screws completely.
5. The router is shipped witheach spacer barattachedto therear ofeach front-mounting
flange. Remove each spacer bar by removing the screws that fasten the spacer bar to the front-mounting flange.
6. Place one of the spacer bars over a flange of the installed large shelf. Position the
notch in the rear of the spacer bar so the upper part of the bar is flush with the rack rail and the lower part is flush with the flange of the shelf (see Figure 31 on page 62).
7. Insert a mounting screw into each of the nonthreaded holes in the recesses of the
spacer bar to secure the spacer bar. Each hole should have a cage nut behind it.
8. Repeat Steps 6 and 7 for the other spacer bar.
9. Tighten all the screws completely.
10. On the back of each rear rack rail, partially insert a mounting screw into the lowest
hole specified in Table 18 on page 60 for the small shelf.
11. Install the small shelf on the back rack rails. Rest the bottom slot of each flange on a
mounting screw.The small shelf installs on the back of the rear rails, extending toward the center of the rack. The bottom of the small shelf on the rear rack rails must align with the bottom of the large shelf on the front rack rails.
12. Partially insert screws into the open holes in the ears of the small shelf.
61Copyright © 2010, Juniper Networks, Inc.
T320 Core Router Hardware Guide
13. Tighten all the screws completely.
14. Remove the mounting brackets from the chassis by loosening the screws at the top
Figure 31: Positioning the Spacer Bar on the Rack
and bottom of each bracket.
Copyright © 2010, Juniper Networks, Inc.62
Chapter 6: Installing the T320 Router Mounting Hardware
Figure 32: Installing the Mounting Hardware for a Four-Post Rack or Cabinet
Related
Documentation
T320 Chassis Description on page 12
T320 Site Preparation Checklist Requirements on page 49
T320 Clearance Requirements for Airflow and Hardware Maintenance on page 51

Installing the T320 Mounting Hardware for an Open-Frame Rack

To prepare to mount the T320 Core Router into an open-frame rack, install the large mounting shelf on the rack. Install cage nuts, if needed. The small mounting shelf and the spacer bars are not needed.
For open-frame racks, center-mounting the chassis is preferable to front-mounting because the more even distribution of weight provides greater stability. You use the center-mounting brackets to center-mount the chassis in an open-frame rack; you use the front-mounting flanges to front-mount the chassis in an open-frame rack.
For an open-frame rack, Table 19 on page 64 specifies the holes in which you insert mounting screws (an X indicates a mounting hole location), and cage nuts if needed. The hole distances are relative to one of the standard U divisions onthe rack.For reference, the bottom of all mounting shelves is at 0.0015 in. (0.01 U) above a U division.
63Copyright © 2010, Juniper Networks, Inc.
T320 Core Router Hardware Guide
Table 19: T320 Open-Frame Rack Mounting Hole Locations
Large ShelfDistance Above U DivisionHole
Chassis
X12.86 U22.51 in. (57.2 cm)39
XX9.86 U17.26 in. (43.8 cm)30
XX6.86 U12.01 in. (30.5 cm)21
XX3.86 U6.76 in. (17.1 cm)12
XX0.86 U1.51 in. (3.8 cm)3
To install the large mounting shelf (see Figure 33 on page 65):
1. Install cage nuts, if needed, in the mounting holes specified in Table 19 on page 64:
2. On the front side of the rack rails, install cage nuts for the chassis.
On the rear side of the rack rails, install cage nuts for the large shelf.
3. On the rear of each rack rail, partially insert a mounting screw into the highest hole
specified for the large shelf in Table 19 on page 64.
4. Install the large shelf on the rack. Hang the shelf over the mounting screws using the
keyhole slots located near the top of the large shelf flanges.
5. Partially insert screws into the open holes in the ears of the large shelf.
6. Tighten all the screws completely.
7. Remove the center-mounting brackets by loosening the screws atthe topand bottom
of each bracket.
8. Optionally, remove thescrews the fasten thespacer bars to thefront-mounting flange.
The router is shipped with a spacer bar attached to the rear of each front-mounting flange, and two center-mounting brackets attached to the chassis.
Copyright © 2010, Juniper Networks, Inc.64
Chapter 6: Installing the T320 Router Mounting Hardware
Figure 33: Installing the Mounting Hardware for an Open-Frame Rack
Related
Documentation
T320 Chassis Description on page 12
T320 Site Preparation Checklist Requirements on page 49
T320 Clearance Requirements for Airflow and Hardware Maintenance on page 51
65Copyright © 2010, Juniper Networks, Inc.
T320 Core Router Hardware Guide
Copyright © 2010, Juniper Networks, Inc.66
CHAPTER 7
Installing the T320 Router Using a Mechanical Lift
Safety Requirements, Warnings, and Guidelines for Installing the T320 Router on page 67
Before You Install the T320 Router Using a Mechanical Lift on page 67
Tools Required to Install the T320 Router Using a Mechanical Lift on page 68
Installing the T320 Router Using a Mechanical Lift on page 68

Safety Requirements, Warnings, and Guidelines for Installing the T320 Router

To avoid harm to yourself or the routeras youinstall and maintain it, follow the guidelines for working with and near electrical equipment, as well as the safety procedures for working with routers. However, providing an exhaustive set of guidelines for working with electrical equipment is beyond the scope of this documentation.
Related
Documentation
T320 Site Preparation Checklist Requirements on page 49
General Electrical Safety Guidelines and Electrical Codes for M Series, MX Series, and
T Series Routers
General Electrical Safety Warnings for M Series, MX Series, and T Series Routers on
page 227

Before You Install the T320 Router Using a Mechanical Lift

Because of the router's size and weight—up to 370 lb (168 kg) depending on configuration—we strongly recommend that you installthe router usinga lift., as described in “Installing the T320 Router Using a Mechanical Lift” on page 68. If you do not use a lift to install the router, refer to “Installing the T320Chassis in the Rack Manually” on page 81 for complete instructions to safely install the router.
Before installing the router in the rack:
“T320 Site Preparation Checklist Requirements” on page 49 which summarizes the tasks you need to perform when preparing a site for router installation.
67Copyright © 2010, Juniper Networks, Inc.
T320 Core Router Hardware Guide
Removethe router from theshipping crate as described in “Unpacking the T320 Router” on page 54.
Related
Documentation
T320 Router Installation Summary on page 53
Safety Requirements, Warnings, and Guidelines for Installing the T320 Router on
page 67
T320 Chassis Lifting Guidelines on page 213

Tools Required to Install the T320 Router Using a Mechanical Lift

To install the T320 chassis using a mechanical lift, you need the following tools:
Mechanical lift
Phillips (+) screwdrivers, number 2
Related
Documentation
T320 Chassis Lifting Guidelines on page 213
Safety Requirements, Warnings, and Guidelines for Installing the T320 Router on
page 67
T320 Router Installation Summary on page 53

Installing the T320 Router Using a Mechanical Lift

CAUTION: Before front-mounting the router in a rack, have a qualified technician verify that the rack is strong enough to support the router's weight and is adequately supported at the installation site.
To install the router using a lift (see Figure 34 on page 69):
1. Ensure that the rack is in its permanent location and is secured to the building. Ensure
that the installationsite allows adequate clearance for both airflow and maintenance. For details, see “T320 Site Preparation Checklist Requirements” on page 49.
2. Load the router onto the lift, making sure it rests securely on the lift platform.
CAUTION: Do not lift the router using the craft interface, installation
handle, or the handles on the sides of the chassis. Use these handles only to help position the router.
3. Using the lift, position the router in front of the rack or cabinet, centering it in front of
the mounting shelves.
4. Lift the chassis approximately 0.75 in. above the surface of the mounting shelves and
position it as close as possible to the shelves.
Copyright © 2010, Juniper Networks, Inc.68
Chapter 7: Installing the T320 Router Using a Mechanical Lift
5. Carefully slide the router onto the mounting shelves so that the bottom of the chassis
and the mounting shelves overlap by approximately two inches.
6. With one person pulling on the installation handle from the rear of the rack or cabinet
while two people push on the front-mounting flanges, slide the router onto the mounting shelves until the center-mounting brackets or front-mounting flanges contact the rack rails or spacer bars (depending on your type of installation). The shelvesensure thatthe holes inthe mounting brackets and the front-mounting flanges of the chassis align with the holes in the rack rails.
7. Move the lift away from the rack.
8. Install the mounting screws:
Four-post rack or cabinet—Install a mounting screw into each of the holes in the spacer bars.
Open-frame rack—Install a mounting screw into each of the open mounting holes aligned with the rack, starting from the bottom.
9. Visually inspect the alignment of the router. If the router is installed properly in the
rack, all the mounting screws on one side of the rack should be aligned with the mounting screws on the opposite side and the router should be level.
Figure 34: Installing the T320 Router in the Rack
69Copyright © 2010, Juniper Networks, Inc.
T320 Core Router Hardware Guide
NOTE: This illustration depicts the router being installed in a four-post rack.
For anillustrationof the mounting hardwarerequiredfor an open-frame rack, see Figure 33 on page 65.
Attaching the T320 Router Installation Handle on page 70
Removing the T320 Router Installation Handle and Reinstalling the Power Supplies on page 71
Attaching the T320 Router Installation Handle
To assist you with the installation of the T320 router, attach the installation handle over the power supply slots of the chassis. Remove the upper power supply first. To remove the power supplies and attach the handle:
1. Attach an electrostaticdischarge (ESD) grounding strap to your bare wrist,and connect
the strap to an approved site ESD grounding point. See the instructions for your site.
2. Switch the circuit breaker on the power supply faceplate to the off position (O). We
recommend this even though the power supplies are notconnected to powersources.
3. Loosen the captive screws on the lower corners of the power supply faceplate
completely. Twist the ejector handles on the upper corners of the faceplate counterclockwise to unseat the power supply.
4. Twist the ejector handles on the upper corners of the faceplate counterclockwise to
unseat the power supply.
5. Grasp the handle on the power supply faceplate and pull firmly to start removing the
power supply. Slide it halfway out of the chassis (see Figure 35 on page 71).
6. Place one hand underneath the power supply to support it and slide it completely out
of the chassis.
CAUTION: Each power supply weighs approximately 12 lb (5.4 kg). Be
prepared to support the full weight of the power supply as you remove it from the router.
7. Repeat the procedure for the other power supply.
8. Attach the installation handle by tightening the captive screws of the handle into the
holes previously occupied by the captive screws of the power supplies (see Figure 36 on page 71).
Copyright © 2010, Juniper Networks, Inc.70
Chapter 7: Installing the T320 Router Using a Mechanical Lift
Figure 35: Removing a Power Supply Before Installing the Installation Handle
Figure 36: Attaching the Installation Handle
Removing the T320 Router Installation Handle and Reinstalling the Power Supplies
After you have installed the T320 router, remove the installation handle and reinstall the two power supplies in the chassis by following this procedure, starting with the lower power supply (see Figure 37 on page 72):
1. Attach an electrostaticdischarge (ESD) grounding strap to your bare wrist,and connect
the strap to one of the ESD points on the chassis. For more information about ESD, see “Preventing Electrostatic Discharge Damage to a T320 Router” on page 210.
2. Loosen the captive screws on the installation handle completely, and remove the
handle from the chassis.
3. Make sure that the circuit breaker on the power supply faceplate is in the off
position (O).
4. Using both hands, slide the power supply into the chassis until you feel resistance.
71Copyright © 2010, Juniper Networks, Inc.
T320 Core Router Hardware Guide
5. Twist theejector handles at theupper corners ofthe powersupply faceplate clockwise
6. Tighten the captive screws at the lower corners of the power supply faceplate to
7. Repeat the procedure for the upper power supply.
Figure 37: Reinstalling a Power Supply
until they stop.
secure the power supply in the chassis.
Related
Documentation
Preventing Electrostatic Discharge Damage to a T320 Router on page 210
T320 Router Installation Summary on page 53
Safety Requirements, Warnings, and Guidelines for Installing the T320 Router on
page 67
T320 Chassis Lifting Guidelines on page 213
Copyright © 2010, Juniper Networks, Inc.72
CHAPTER 8
Installing the T320 Router Without a Mechanical Lift
Before You Install the T320 Router Without a Mechanical Lift on page 73
Tools and Parts Required to Install the T320 Router Without a Mechanical Lift on page 73
Removing T320 Components from the Chassis on page 74
Installing the T320 Chassis in the Rack Manually on page 81
Reinstalling T320 Components in the Chassis on page 85

Before You Install the T320 Router Without a Mechanical Lift

If you cannot use a mechanical lift to install the T320 router, you can install it manually. Beforeinstalling the router manually,you mustfirst remove components from the chassis, and you must reinstall the components once the router is installed in the rack. At least four people areneeded to safely lift the chassis intothe rack or cabinet. With components removed, the chassis weighs approximately 131.4 lb (59.6 kg).
Before installing the router in the rack, read the safety information in “T320Chassis Lifting Guidelines” on page 213. Remove the router from the shipping crate as described in “Unpacking the T320 Router” on page 54. Install the mounting hardware as described in “Installing the T320 Mounting Hardware for a Four-Post Rack or Cabinet” on page 60 or “Installing the T320 Mounting Hardware for an Open-Frame Rack” on page 63.
Related
Documentation
T320 Router Installation Summary on page 53
Safety Requirements, Warnings, and Guidelines for Installing the T320 Router on
page 67

Tools and Parts Required to Install the T320 Router Without a Mechanical Lift

To install the T320 router, you need the following tools and parts:
Phillips (+) screwdrivers, numbers 1 and 2
Flat-blade (–) screwdriver, number 1
7/16-in. socket wrench
73Copyright © 2010, Juniper Networks, Inc.
T320 Core Router Hardware Guide
3/8-in. nut driver
ESD grounding wrist strap
Related
Documentation
T320 Router Installation Summary on page 53
Safety Requirements, Warnings, and Guidelines for Installing the T320 Router on
page 67
T320 Chassis Lifting Guidelines on page 213

Removing T320 Components from the Chassis

To make the T320 router light enough to install manually, you first remove most components from the chassis. The procedures in this section for removing components from the chassis are for initial installation only, and assume that you have not connected power cables to the router.The followingprocedures describe howto remove components from the chassis, first from the rear and then from the front:
1.
Removing the T320 Power Supplies on page 74
2.
Removing the T320 SIBs on page 75
3.
Removing the T320 T-CBs on page 76
4.
Removing the T320 SCG on page 77
5.
Removing the T320 Rear Fan Tray on page 78
6.
Removing the T320 Cable Management System on page 79
7.
Removing the T320 FPCs on page 79
Removing the T320 Power Supplies
The power supplies are located at the rear of the T320 chassis below the SIBs. Each power supply weighs approximately 12 lb (5.4 kg).
To remove the power supplies, starting with the upper power supply:
1. Attach an electrostaticdischarge (ESD) grounding strap to your bare wrist,and connect
the strap to an approved site ESD grounding point. See the instructions for your site.
2. Switch the circuit breaker on the power supply faceplate to the off position (O). We
recommend this even though the power supplies are notconnected to powersources.
3. Loosen the captive screws on the lower corners of the power supply faceplate
completely. Twist the ejector handles on the upper corners of the faceplate counterclockwise to unseat the power supply.
4. Twist the ejector handles on the upper corners of the faceplate counterclockwise to
unseat the power supply.
5. Grasp the handle on the power supply faceplate and pull firmly to start removing the
power supply. Slideit halfwayout of thechassis (see “Remove aPower Supply Before Installing the Installation Handle” on page 70).
Copyright © 2010, Juniper Networks, Inc.74
Loading...