Juniper Internet Router M160 Hardware Manual

PDF

Document

M160 Internet Router

Hardware Guide

Juniper Networks®, Inc.

1194 North Mathilda Avenue

Sunnyvale, California

94089

USA

408-745-2000

www.juniper.net

Part Number: 530-007250-01, Revision 5

This product includes the Envoy SNMP Engine, developed by Epilogue Technology, an Integrated Systems Company. Copyright

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,

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,

Juniper Networks, the Juniper Networks logo, NetScreen, NetScreen Technologies, the NetScreen logo, NetScreen-Global Pro, ScreenOS, and

GigaScreen are registered trademarks of Juniper Networks, Inc. in the United States and other countries.

The following are trademarks of Juniper Networks, Inc.: ERX, ESP, E-series, Instant Virtual Extranet, Internet Processor, J2300, J4300, J6300, J-Protect,

J-series, J-Web, JUNOS, JUNOScope, JUNOScript, JUNOSe, M5, M7i, M10, M10i, M20, M40, M40e, M160, M320, M-series, MMD, NetScreen-5GT,

NetScreen-5XP, NetScreen-5XT, NetScreen-25, NetScreen-50, NetScreen-204, NetScreen-208, NetScreen-500, NetScreen-5200, NetScreen-5400,

NetScreen-IDP 10, NetScreen-IDP 100, NetScreen-IDP 500, NetScreen-Remote Security Client, NetScreen-Remote VPN Client, NetScreen-SA 1000 Series,

NetScreen-SA 3000 Series, NetScreen-SA 5000 Series, NetScreen-SA Central Manager, NetScreen Secure Access, NetScreen-SM 3000, NetScreen-Security

Manager, NMC-RX, SDX, Stateful Signature, T320, T640, T-series, and TX Matrix. All other trademarks, service marks, registered trademarks, or registered service marks are the property of their respective owners. All specifications are subject to change without notice.

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.

M160 Internet Router Hardware Guide

Writing: Sheila Nolte, Tony Mauro, Jerry Isaac

Editing: Stella Hackell

Illustration: Faith Bradford

Cover Design: Edmonds Design

Revision History

25 February 2005—530-007250-01 Revision 5. Correct DC power illustration and replacement procedure.

12 November 2004—530-007250-01 Revision 4. Revised fuse replacement procedure.

30 June 2003—530-007250-01 Revision 3. Corrected and added component information.

15 October 2002—530-007250-01 Revision 2. Incorporated updated technical information; synchronized with M40e Internet Router Hardware Guide.

15 March 2002—530-007250-01 Revision 1. Incorporated updated technical information.

15 October 2001—Incorporated updated technical information.

15 May 2001—Adopted new template.

28 February 2001—Incorporated updated technical information.

31 August 2000—Incorporated updated technical information.

31 March 2000—First edition.

The information in this document is current as of the date listed in the revision history.

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 (including the ERX-310, ERX-705, ERX-710, ERX-1410, ERX-1440, M5, M7i, M10, M10i, M20, M40, M40e,

M160, M320, and T320 routers, T640 routing node, and the JUNOS and SDX-300 software) 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.

YEAR 2000 NOTICE

Juniper Networks hardware and software products are Year 2000 compliant. The JUNOS software has no known time-related limitations through the year

2038. However, the NTP application is known to have some difficulty in the year 2036.

End User License Agreement

READ THIS END USER LICENSE AGREEMENT ("AGREEMENT") BEFORE DOWNLOADING, INSTALLING, OR USING THE SOFTWARE. BY DOWNLOADING,

INSTALLING, OR USING THE SOFTWARE OR OTHERWISE EXPRESSING YOUR AGREEMENT TO THE TERMS CONTAINED HEREIN, YOU (AS CUSTOMER

OR IF YOU ARE NOT THE CUSTOMER, AS A REPRESENTATIVE/AGENT AUTHORIZED TO BIND THE CUSTOMER) CONSENT TO BE BOUND BY THIS

AGREEMENT. IF YOU DO NOT OR CANNOT AGREE TO THE TERMS CONTAINED HEREIN, THEN (A) DO NOT DOWNLOAD, INSTALL, OR USE THE

SOFTWARE, AND (B) YOU MAY CONTACT JUNIPER NETWORKS REGARDING LICENSE TERMS.

The Parties. The parties to this Agreement are Juniper Networks, Inc. and its subsidiaries (collectively "Juniper"), and the person or organization that originally purchased from Juniper or an authorized Juniper reseller the applicable license(s) for use of the Software ("Customer") (collectively, the "Parties").

The Software. In this Agreement, "Software" means the program modules and features of the Juniper or Juniper-supplied software, and updates and releases of such software, for which Customer has paid the applicable license or support fees to Juniper or an authorized Juniper reseller.

License Grant. Subject to payment of the applicable fees and the limitations and restrictions set forth herein, Juniper grants to Customer a non-exclusive and non-transferable license, without right to sublicense, to use the Software, in executable form only, subject to the following use restrictions: a.

Customer shall use the Software solely as embedded in, and for execution on, Juniper equipment originally purchased by Customer from

Juniper or an authorized Juniper reseller, unless the applicable Juniper documentation expressly permits installation on non-Juniper equipment.

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.

Other Juniper documentation for the Software (such as product purchase documents, documents accompanying the product, the

Software user manual(s), Juniper’s website for the Software, or messages displayed by the Software) may specify limits to Customer’s use of the

Software. Such limits may restrict use to a maximum number of seats, concurrent users, sessions, subscribers, nodes, or transactions, or require the purchase of separate licenses to use particular features, functionalities, or capabilities, or provide temporal or geographical limits.

Customer’s use of the Software shall be subject to all such limitations and purchase of all applicable licenses.

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.

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, transfer, or grant any rights in and to any copy of the Software, in any form, to any third party; (d) remove any proprietary notices, labels, or marks on or in any copy of the Software; (e) distribute any copy of the Software to any third party, including as may be embedded in Juniper equipment sold in the secondhand market; (f) use any ’locked’ or key-restricted feature, function, or capability without first purchasing the applicable license(s) and obtaining a valid key from Juniper, even if such feature, function, or capability is enabled without a key; (g) distribute any key for the Software provided by Juniper to any third party; (h) use the Software in any manner that extends or is broader than the uses purchased by Customer from Juniper or an authorized Juniper reseller; (i) use the Software on non-Juniper equipment where the Juniper documentation does not expressly permit installation on non-Juniper equipment; (j) use the Software (or make it available for use) on Juniper equipment that the Customer did not originally purchase from Juniper or an authorized Juniper reseller; or (k) use the Software in any manner other than as expressly provided herein.

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.

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.

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.

Warranty, Limitation of Liability, Disclaimer of Warranty. If the Software is distributed on physical media (such as CD), Juniper warrants for 90 days from delivery that the media on which the Software is delivered will be free of defects in material and workmanship under normal use. This limited warranty extends only to the Customer. Except as may be expressly provided in separate documentation from Juniper, no other warranties apply to the Software, and the Software is otherwise provided AS IS. Customer assumes all risks arising from use of the Software. Customer’s sole remedy and

Juniper’s entire liability under this limited warranty is that Juniper, at its option, will repair or replace the media containing the Software, or provide a refund, provided that Customer makes a proper warranty claim to Juniper, in writing, within the warranty period. Nothing in this Agreement shall give rise to any obligation to support the Software. Any such support shall be governed by a separate, written agreement. To the maximum extent permitted by law,

Juniper shall not be liable for any liability for lost profits, loss of data or costs or procurement of substitute goods or services, or for any special, indirect, or consequential damages arising out of this Agreement, the Software, or any Juniper or Juniper-supplied software. In no event shall Juniper be liable for damages arising from unauthorized or improper use of any Juniper or Juniper-supplied software.

EXCEPT AS EXPRESSLY PROVIDED HEREIN OR IN SEPARATE DOCUMENTATION PROVIDED FROM JUNIPER AND 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 iii

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.

Termination. Any breach of this Agreement or failure by Customer to pay any applicable fees due shall result in automatic termination of the license granted herein. Upon such termination, Customer shall destroy or return to Juniper all copies of the Software and related documentation in

Customer’s possession or control.

10.

Taxes. All license fees for the Software are exclusive of taxes, withholdings, duties, or levies (collectively "Taxes"). Customer shall be responsible for paying Taxes arising from the purchase of the license, or importation or use of the Software.

11.

Export. Customer agrees to comply with all applicable export laws and restrictions and regulations of any United States and any applicable foreign agency or authority, and not to export or re-export the Software or any direct product thereof in violation of any such restrictions, laws or regulations, or without all necessary approvals. Customer shall be liable for any such violations. The version of the Software supplied to you may contain encryption or other capabilities restricting your ability to export the Software without an export license.

12.

Commercial Computer Software. The Software is "commercial computer software" and is provided with restricted rights. Use, duplication, or disclosure by the United States government is subject to restrictions set forth in this Agreement and as provided in DFARS 227.7201 through 227.7202-4,

FAR 12.212, FAR 27.405(b)(2), FAR 52.227-19, or FAR 52.227-14(ALT III) as applicable.

13.

Miscellaneous. This Agreement shall be governed by the laws of the State of California without reference to its conflicts of laws principles. 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.

If you have any questions about this agreement, contact Juniper Networks at the following address:

Juniper Networks, Inc.

1194 North Mathilda Avenue

Sunnyvale, CA 94089

USA

Attn: Contracts Administrator iv

Part 1

About This Guide xix

Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xix

Audience. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xix

Documentation Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xix

List of Technical Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xxi

Documentation Feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxiii

Requesting Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxiii

Product Overview

Chapter 1

Chapter 2

System Overview . .

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

Field-Replaceable Units (FRUs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4

System Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4

Safety Requirements, Warnings, and Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5

Hardware Component Overview . .

Chassis. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7

Packet Forwarding Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11

Midplane. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Physical Interface Cards (PICs). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

PIC Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Flexible PIC Concentrators (FPCs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

FPC Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

FPC Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Packet Forwarding Engine Clock Generators (PCGs) . . . . . . . . . . . . . . . . . . . . . . . . 18

PCG Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Switching and Forwarding Module (SFM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

SFM Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Host Module. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Routing Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Routing Engine Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Miscellaneous Control Subsystem (MCS). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

MCS Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Craft Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Alarm LEDs and Alarm Cutoff/Lamp Test Button. . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

LCD and Navigation Buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

LCD Idle Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

LCD Alarm Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Table of Contents v

M160 Internet Router Hardware Guide

Part 2

Chapter 3

Chapter 4

Host Module LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

FPC LEDs and Offline Button . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Connector Interface Panel (CIP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Routing Engine Management Ports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

BITS Input Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Alarm Relay Contacts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Power System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Power Supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Circuit Breaker Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Fuses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Cooling System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Cooling System Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Airflow through the Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Cable Management System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

JUNOS Internet Software Overview . .

Routing Engine Software Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Routing Protocol Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

IPv4 Routing Protocols. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

IPv6 Routing Protocols. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Routing and Forwarding Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Routing Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

VPNs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Interface Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Chassis Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

SNMP and MIB II Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Management Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Routing Engine Kernel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Tools for Accessing and Configuring the Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Tools for Monitoring the Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Software Upgrades. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

System Architecture Overview . .

Packet Forwarding Engine Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Data Flow through the Packet Forwarding Engine . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Routing Engine Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Routing Engine Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Initial Installation

Chapter 5 Preparing for Router Installation . .

Rack Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Rack Size and Strength . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Spacing of Mounting Holes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Connection to Building Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Clearance Requirements for Airflow and Hardware Maintenance . . . . . . . . . . . . . . 62

Routing Node Environmental Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Fire Safety Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 vi Table of Contents

Table of Contents

Chapter 6

Chapter 7

Chapter 8

Fire Suppression . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Fire Suppression Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Power Guidelines, Requirements, and Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Site Electrical Wiring Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Distance Limitations for Signaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Radio Frequency Interference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Electromagnetic Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Router Power Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Chassis Grounding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Power, Connection, and Cable Specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Network Cable Specifications and Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Fiber Optic and Network Cable Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Signal Loss in Multimode and Single-Mode Fiber-Optic Cable . . . . . . . . . . . . . 71

Attenuation and Dispersion in Fiber-Optic Cable . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Calculating Power Budget for Fiber-Optic Cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Calculating Power Margin for Fiber-Optic Cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Attenuating to Prevent Saturation at SONET/SDH PICs . . . . . . . . . . . . . . . . . . . . . 74

Routing Engine Interface Cable and Wire Specifications . . . . . . . . . . . . . . . . . . . . . . . . 74

Site Preparation Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Unpacking the Router . .

Tools and Parts Required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Unpacking the Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Installing the Router Using a Mechanical Lift . .

Tools and Parts Required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Installing the Chassis Using a Mechanical Lift . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Installing the Router without a Mechanical Lift . .

Tools and Parts Required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Removing Components from the Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Removing the Power Supplies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Removing the Rear Component Cover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Removing the SFMs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Removing the MCSs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

Removing the PCGs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

Removing the Routing Engines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

Removing the Rear Upper Impeller Assembly. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Removing the Rear Lower Impeller Assembly. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Removing the Fan Tray . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Removing the FPCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

Removing the Front Impeller Assembly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Installing the Chassis into the Rack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Reinstalling Components into the Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Reinstalling the Front Impeller Assembly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

Reinstalling the FPCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Reinstalling the Fan Tray . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

Reinstalling the Rear Lower Impeller Assembly . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Reinstalling the Rear Upper Impeller Assembly . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

Reinstalling the Routing Engines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Reinstalling the PCGs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

Reinstalling the MCSs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

Table of Contents vii

M160 Internet Router Hardware Guide

Part 3

Reinstalling the SFMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

Reinstalling the Rear Component Cover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

Reinstalling the Power Supplies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

Chapter

Connecting the Router and Performing Initial Configuration . .

111

Tools and Parts Required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

Connecting the Router to Management and Alarm Devices . . . . . . . . . . . . . . . . . . . 112

Connecting to a Network for Out-of-Band Management. . . . . . . . . . . . . . . . . . . 114

Connecting to a Management Console or Auxiliary Device . . . . . . . . . . . . . . . 114

Connecting to an External Alarm-Reporting Device . . . . . . . . . . . . . . . . . . . . . . . 115

Connecting PIC Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

Providing Power to the Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

Connecting Power to the Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

Powering On the Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

Configuring the JUNOS Internet Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

Hardware Maintenance, Replacement, and Troubleshooting

Procedures

Chapter 10

Chapter 11

Maintaining Hardware Components . .

127

Routine Maintenance Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .127

Maintaining Cooling System Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .127

Maintaining the Air Filter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .128

Removing the Air Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .128

Cleaning the Air Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .129

Installing the Air Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .129

Maintaining the Fan Tray and Impellers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .130

Maintaining Host Module Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

Maintaining Packet Forwarding Engine Components . . . . . . . . . . . . . . . . . . . . . . . . . . .132

Maintaining FPCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .133

Maintaining PICs and PIC Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .134

Maintaining the PCGs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .135

Maintaining SFMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .136

Maintaining Power Supplies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .137

Replacing Hardware Components . .

139

Tools and Parts Required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .139

Replacing the CIP and Routing Engine Interface Port Cables . . . . . . . . . . . . . . . . . . 141

Removing the CIP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

Installing the CIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .143

Replacing Connections to Routing Engine Interface Ports . . . . . . . . . . . . . . . . .145

Replacing the Management Ethernet Cable. . . . . . . . . . . . . . . . . . . . . . . . . . . .146

Replacing the Console or Auxiliary Cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .146

Replace Alarm Relay Wires. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .147

Replacing Cooling System Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .148

Replacing the Fan Tray . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .148

viii Table of Contents

Table of Contents

Removing the Fan Tray . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .148

Installing the Fan Tray . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .149

Replacing the Front Impeller Assembly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .150

Removing the Front Impeller Assembly. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

Removing the Craft Interface from the Front Impeller Assembly . . . .152

Installing the Craft Interface on the Front Impeller Assembly . . . . . . . .153

Installing the Front Impeller Assembly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .154

Replacing the Rear Lower Impeller Assembly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .154

Removing the Rear Lower Impeller Assembly . . . . . . . . . . . . . . . . . . . . . . . . .155

Installing the Rear Lower Impeller Assembly . . . . . . . . . . . . . . . . . . . . . . . . . .155

Replacing the Rear Upper Impeller Assembly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .156

Removing the Rear Upper Impeller Assembly . . . . . . . . . . . . . . . . . . . . . . . . .157

Installing the Rear Upper Impeller Assembly . . . . . . . . . . . . . . . . . . . . . . . . . .158

Replacing Host Module Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .159

Replacing an MCS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .159

Removing an MCS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .159

Installing an MCS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161

Removing and Insert the PC Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .163

Removing the PC Card. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .163

Insert the PC Card. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .164

Replacing a Routing Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .165

Removing a Routing Engine. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .165

Installing a Routing Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .168

Replacing Packet Forwarding Engine Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . .169

Replacing an FPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .169

Removing an FPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170

Installing an FPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .172

Replacing a PCG. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .176

Removing a PCG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .176

Installing a PCG. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .178

Replacing a PIC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .179

Removing a PIC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .179

Installing a PIC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181

Replace PIC Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .185

Removing a PIC Cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .185

Installing a PIC Cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .186

Replacing an SFM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .188

Removing an SFM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .188

Installing an SFM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .189

Replace an SFP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .190

Removing an SFP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .190

Installing an SFP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191

Replacing Power System Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .193

Replacing the Circuit Breaker Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .193

Removing the Circuit Breaker Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .193

Installing the Circuit Breaker Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .195

Replacing a Power Supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .197

Removing a Power Supply. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .197

Installing a Power Supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .199

Disconnecting and Connecting Power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .200

Disconnecting Power from the Router. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .200

Connecting Power to the Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .202

Replacing a Fuse . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .204

Table of Contents ix

M160 Internet Router Hardware Guide

Part 4

Chapter 12 Troubleshooting Hardware Components . .

207

Overview of Troubleshooting Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207

Command-Line Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207

LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .208

LEDs on the Craft Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .208

LEDs on Hardware Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .209

Chassis and Interface Alarm Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .209

Blown Fuse Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211

Juniper Networks Technical Assistance Center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212

Troubleshooting the Cooling System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212

Troubleshooting Packet Forwarding Engine Components . . . . . . . . . . . . . . . . . . . . . . 213

Troubleshooting FPCs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214

Troubleshooting PICs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215

Troubleshooting the Power System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215

All LEDs on Both Supplies Are Off . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215

All LEDs on One Supply Are Off or LED States Are not Correct. . . . . . . . . . . 216

Appendixes

Appendix A Safety and Regulatory Compliance Information . .

221

Definition of Safety Warning Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221

Safety Guidelines and Warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .222

General Safety Guidelines and Warnings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .224

Qualified Personnel Warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .225

Restricted Access Area Warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .225

Preventing Electrostatic Discharge Damage . . . . . . . . . . . . . . . . . . . . . . . . . . .226

Electrical Safety Guidelines and Warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .227

General Electrical Safety Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .229

DC Power Electrical Safety Guidelines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .229

Copper Conductors Warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .230

DC Power Disconnection Warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231

DC Power Grounding Requirements and Warning. . . . . . . . . . . . . . . . . . . . .232

DC Power Wiring Sequence Warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .233

DC Power Wiring Terminations Warning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .234

Grounded Equipment Warning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .235

In Case of Electrical Accident . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .236

Midplane Energy Hazard Warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .236

Multiple Power Supplies Disconnection Warning . . . . . . . . . . . . . . . . . . . . . .236

Power Disconnection Warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .237

TN Power Warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .238

Installation Safety Guidelines and Warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .239

Chassis Lifting Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .239

Installation Instructions Warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .239

Rack-Mounting Requirements and Warnings . . . . . . . . . . . . . . . . . . . . . . . . . .240

Ramp Warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .244

Laser and LED Safety Guidelines and Warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . .244

General Laser Safety Guidelines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .245

Class 1 Laser Product Warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .245

Class 1 LED Product Warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .245

x Table of Contents

Table of Contents

Part 5

Appendix B

Appendix C

Laser Beam Warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .246

Radiation From Open Port Apertures Warning . . . . . . . . . . . . . . . . . . . . . . . .247

Maintenance and Operational Safety Guidelines and Warnings . . . . . . . . . .247

Battery Handling Warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .248

Jewelry Removal Warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .249

Lightning Activity Warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .250

Operating Temperature Warning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251

Product Disposal Warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .252

Agency Approvals. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .253

Compliance Statements for EMC Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .254

Canada. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .254

European Community . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .254

Japan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .254

United States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .254

Contacting Customer Support and Returning Hardware . .

255

Locating Component Serial Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .255

CIP Serial Number ID Label . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .257

Craft Interface Serial Number ID Label. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .257

DC Power Supply Serial Number ID Label . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .258

FPC Serial Number ID Label . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .259

MCS Serial Number ID Label . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .259

PCG Serial Number ID Label . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .260

PIC Serial Number ID Label . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .260

Routing Engine Serial Number ID Label. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261

SFM Serial Number ID Label . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .262

Contacting Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .262

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

Return Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .263

Tools and Parts Required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .264

Packing the Routing Node for Shipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .265

Packing Components for Shipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .267

Cable Connector Pinouts . .

269

RJ-45 Connector Pinouts for the Routing Engine ETHERNET Port. . . . . . . . . . . . .269

DB-9 Connector Pinouts for the Routing Engine AUXILIARY and CONSOLE

Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270

RJ-48 Cable Pinouts for E1 and T1 PICs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270

X.21 and V.35 Cable Pinouts for EIA-530 PIC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .273

Fast Ethernet 48-port Cable Pinouts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .274

Index

Index. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .279

Table of Contents xi

M160 Internet Router Hardware Guide xii Table of Contents

List of Figures

Figure 1: Front of Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Figure 2: Rear of Chassis with Component Cover in Place . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Figure 3: Rear of Chassis with Component Cover Removed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Figure 4: Midplane. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Figure 5: Front of Chassis with Four-PIC FPC Installed in Slot FPC0 . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Figure 6: FPC1 and FPC2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Figure 7: Packet Forwarding Engine Clock Generator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Figure 8: Switching and Forwarding Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Figure 9: Routing Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Figure 10: Miscellaneous Control Subsystem. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Figure 11: Craft Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Figure 12: LCD in Idle Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Figure 13: LCD in Alarm Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Figure 14: Connector Interface Panel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Figure 15: Routing Engine Interface Ports for Host Module 0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Figure 16: Alarm Relay Contacts and BITS Input Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Figure 17: Original Power Supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Figure 18: Enhanced Power Supply. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Figure 19: Circuit Breaker Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Figure 20: Airflow through the Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Figure 21: Cable Management System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Figure 22: System Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Figure 23: Packet Forwarding Engine Components and Data Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Figure 24: Routing Engine Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Figure 25: Control Packet Handling for Routing and Forwarding Table Updates . . . . . . . . . . . . . 55

Figure 26: Typical Center-Mount Rack. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Figure 27: Chassis Dimensions and Clearance Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Figure 28: Power and Grounding Cable Lug . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Figure 29: Typical Source Cabling to the Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Figure 30: Power and Grounding Cable Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Figure 31: Unpacking the Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Figure 32: Removing a Power Supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Figure 33: Removing an SFM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

Figure 34: Removing an MCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

Figure 35: Removing a PCG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

Figure 36: Removing a Routing Engine. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Figure 37: Removing the Rear Upper Impeller Assembly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Figure 38: Removing the Rear Upper Impeller Assembly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Figure 39: Removing the Rear Lower Impeller Assembly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Figure 40: Removing the Fan Tray . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

Figure 41: Removing an FPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Figure 42: Removing the Front Impeller Assembly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Figure 43: Attaching the Lifting Handle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

Figure 44: Installing the Chassis in a Rack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Figure 45: Reinstalling the Front Impeller Assembly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Figure 46: Reinstalling an FPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

Figure 47: Reinstalling the Fan Tray . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Figure 48: Reinstalling the Rear Lower Impeller Assembly. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

Figure 49: Reinstalling the Rear Upper Impeller Assembly. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

List of Figures xiii

M160 Internet Router Hardware Guide xiv List of Figures

Figure 50: Reinstalling the Rear Upper Impeller Assembly. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Figure 51: Reinstalling a Routing Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

Figure 52: Reinstalling a PCG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

Figure 53: Reinstalling an MCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

Figure 54: Reinstalling an SFM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

Figure 55: Reinstalling a Power Supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

Figure 56: Routing Engine Management Ports and Alarm Relay Contacts . . . . . . . . . . . . . . . . . . 113

Figure 57: Routing Engine Ethernet Cable Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

Figure 58: Console and Auxiliary Serial Port Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

Figure 59: Attaching Cable to a PIC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

Figure 60: Connecting Power and Grounding Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

Figure 61: Removing the Air Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .129

Figure 62: Removing the Filter from the Air Filter Cover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .129

Figure 63: Installing the Air Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .130

Figure 64: Removing the CIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .143

Figure 65: Installing the CIP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .144

Figure 66: Routing Engine Interface Ports and Alarm Relay Contacts . . . . . . . . . . . . . . . . . . . . . . .145

Figure 67: Ethernet Cable Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .146

Figure 68: Serial Port Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .147

Figure 69: Removing the Fan Tray . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .149

Figure 70: Installing the Fan Tray . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .150

Figure 71: Removing the Front Impeller Assembly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .152

Figure 72: Removing the Screws along the Top Front Edge of the Front Impeller

Assembly. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .153

Figure 73: Removing the Craft Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .153

Figure 74: Installing the Front Impeller Assembly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .154

Figure 75: Removing the Rear Lower Impeller Assembly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .155

Figure 76: Installing the Rear Lower Impeller Assembly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .156

Figure 77: Removing the Rear Upper Impeller Assembly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .157

Figure 78: Removing the Rear Upper Impeller Assembly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .158

Figure 79: Installing the Rear Upper Impeller Assembly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .158

Figure 80: Installing the Rear Upper Impeller Assembly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .159

Figure 81: Removing an MCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161

Figure 82: Installing an MCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .162

Figure 83: Removing the PC Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .164

Figure 84: Insert the PC Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .165

Figure 85: Removing a Routing Engine. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .167

Figure 86: Installing a Routing Engine. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .169

Figure 87: Removing an FPC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .172

Figure 88: Installing an FPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .175

Figure 89: Connecting Fiber-Optic Cable to a PIC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .176

Figure 90: Removing a PCG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .177

Figure 91: Installing a PCG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .179

Figure 92: Removing a PIC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181

Figure 93: Installing a PIC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .184

Figure 94: Connecting Fiber-Optic Cable to a PIC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .184

Figure 95: Connecting Fiber-Optic Cable to a PIC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .187

Figure 96: Removing an SFM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .189

Figure 97: Installing an SFM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .190

Figure 98: Small Form Factor Pluggable (SFP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .190

Figure 99: Removing the Circuit Breaker Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .195

Figure 100: Installing the Circuit Breaker Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .197

Figure 101: Removing a Power Supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .198

Figure 102: Rear of Power Supply Showing Midplane Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . .199

List of Figures

Figure 103: Installing a Power Supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .200

Figure 104: Disconnecting Power Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .202

Figure 105: Connecting Power and Grounding Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .204

Figure 106: Fuse Locations in the Fuse Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .206

Figure 107: Fuse Locations in the Fuse Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211

Figure 108: Placing a Component into an Electrostatic Bag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .227

Figure 109: Serial Number ID Label . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .256

Figure 110: CIP Serial Number ID Label . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .257

Figure 111: Craft Interface Serial Number ID Label . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .258

Figure 112: DC Power Supply Serial Number ID Label. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .258

Figure 113: FPC Serial Number ID Label . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .259

Figure 114: MCS Serial Number ID Label . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .260

Figure 115: PCG Serial Number ID Label . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .260

Figure 116: PIC Serial Number ID Label . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261

Figure 117: Routing Engine 333 Serial Number ID Label . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261

Figure 118: Routing Engine 600 Serial Number ID Label . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .262

Figure 119: SFM Serial Number ID Label . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .262

Figure 120: EIA-530 PIC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .273

Figure 121: Fast Ethernet 48-port PIC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .275

Figure 122: VHDCI to RJ-21 Cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .275

List of Figures xv

M160 Internet Router Hardware Guide xvi List of Figures

List of Tables

Table 1: Notice Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xx

Table 2: Text and Syntax Conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xx

Table 3: Juniper Networks Technical Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xxi

Table 4: Field-Replaceable Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Table 5: Chassis Physical Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Table 6: States for PCG LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Table 7: States for SFM LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Table 8: States for MCS LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Table 9: Alarm LEDs and Alarm Cutoff/Lamp Test Button . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Table 10: States for Host Module LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Table 11: States for FPC LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Table 12: States for Power Supply LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Table 13: Electrical Specifications for Power Supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Table 14: Spacing of Holes on Front Support Post and Center-Mounting Bracket . . . . . . . . . . . . 61

Table 15: Routing Node Environmental Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Table 16: Component Power Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Table 17: DC Power and Grounding Cable Specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Table 18: Estimated Values for Factors Causing Link Loss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Table 19: Cable and Wire Specifications for Routing Engine Management and Alarm

Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Table 20: Site Preparation Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Table 21: Generic Inventory of Router Components Installed in Chassis . . . . . . . . . . . . . . . . . . . . . 79

Table 22: Router Component Weights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Table 23: FPC Removal Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

Table 24: Tools and Parts Required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .140

Table 25: Fuse Specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .206

Table 26: Chassis Alarm Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .209

Table 27: SONET/SDH Interface Alarm Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210

Table 28: RJ-45 Connector Pinout. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .269

Table 29: DB-9 Connector Pinout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .270

Table 30: RJ-48 Connector to RJ-48 Connector (Straight) Pinout . . . . . . . . . . . . . . . . . . . . . . . . . . . . .270

Table 31: RJ-48 Connector to RJ-48 Connector (Crossover) Pinout . . . . . . . . . . . . . . . . . . . . . . . . . . . 271

Table 32: RJ-48 Connector to DB-15 Connector (Straight) Pinout . . . . . . . . . . . . . . . . . . . . . . . . . . . .272

Table 33: RJ-48 Connector to DB-15 Connector (Crossover) Pinout . . . . . . . . . . . . . . . . . . . . . . . . . .272

Table 34: DB-25 Connector to V.35 Connector Pinout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .273

Table 35: DB-25 Connector to DB-15 (X.21) Connector Pinout. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .274

Table 36: RJ-21 Pin Assignments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .275

List of Tables xvii

M160 Internet Router Hardware Guide xviii List of Tables

About This Guide

Objectives on page xix

Audience on page xix

Documentation Conventions on page xix

List of Technical Publications on page xxi

Documentation Feedback on page xxiii

Requesting Support on page xxiii

Objectives

This manual describes hardware installation and basic troubleshooting procedures for the Juniper Networks M160 Internet router. It explains how to prepare your site for router installation, unpack and install the hardware, power on the router, perform initial software configuration, and perform routine maintenance. After completing the installation and basic configuration procedures covered in this manual, refer to the JUNOS Internet software configuration guides for information about further JUNOS software configuration.

NOTE: For additional information about Juniper Networks Internet routers and the

Physical Interface Cards (PICs) they support—either corrections to or information that might have been omitted from this guide—see the hardware release notes at http://www.juniper.net/ .

Audience

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

Documentation Conventions

Table 1 defines the notice icons used in this guide.

Documentation Conventions xix

M160 Internet Router Hardware Guide

Table 1: Notice Icons

Icon Meaning

Informational note

Caution

Warning

Description

Indicates important features or instructions.

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

Alerts you to the risk of personal injury or death.

Table 2 defines the text and syntax conventions used in this guide.

Table 2: Text and Syntax Conventions

Convention

Bold sans serif typeface

Fixed-width typeface

Italic typeface

Italic sans serif typeface

Sans serif typeface

< > (angle brackets)

| (pipe symbol)

Description

Represents text that you type.

Examples

To enter configuration mode, type the configure command:

Represents output that appears on the terminal screen.

Introduces important new terms.

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.

Identifies book names.

Identifies RFC and Internet draft titles.

JUNOS System Basics

Configuration Guide

RFC 1997, BGP Communities

Attribute

Configure the machine’s domain name: Represents variables (options for which you substitute a value) in commands or configuration statements.

[edit] root@# set system domain-name domain-name

Represents names of configuration statements, commands, files, and directories; IP addresses; configuration hierarchy levels; or labels on routing platform components.

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 .

Enclose optional keywords or variables.

stub <default-metric metric >;

Indicates a choice between the mutually exclusive keywords or variables on either side of the symbol. The set of choices is often enclosed in parentheses for clarity.

( broadcast | multicast string1 | string2 | string3 ) xx Documentation Conventions

About This Guide

Convention

# (pound sign)

[ ] (square brackets)

Indention and braces ( { } )

; (semicolon)

J-Web GUI Conventions

Bold typeface

> (bold right angle bracket)

Description

Indicates a comment specified on the same line as the configuration statement to which it applies.

Enclose a variable for which you can substitute one or more values.

Identify a level in the configuration hierarchy.

Identifies a leaf statement at a configuration hierarchy level.

Examples rsvp { # Required for dynamic MPLS only community name members [ community-ids ]

}

[edit] routing-options { static { route default { nexthop address ; retain;

}

Represents J-Web graphical user interface (GUI) items you click or select.

Separates levels in a hierarchy of J-Web selections.

In the Logical Interfaces box, select All Interfaces .

To cancel the configuration, click Cancel .

In the configuration editor hierarchy, select Protocols>Ospf .

List of Technical Publications

Table 3 lists the software and hardware guides and release notes for Juniper

Networks routing platforms that use the JUNOS Internet software and describes the contents of each book.

Table 3: Juniper Networks Technical Documentation

Book Description

JUNOS for J-series, M-series, and T-series Routing Platforms Configuration Guides

Feature Guide

System Basics

Network Interfaces and Class of Service

MPLS Applications

Provides a detailed explanation and configuration examples for several of the most complex features in the JUNOS software.

Provides an overview of the JUNOS software and describes how to install and upgrade the software. This manual also describes how to configure system management functions and how to configure the chassis, including user accounts, passwords, and redundancy.

Provides an overview of the network interface and class-of-service functions of the JUNOS software and describes how to configure the network interfaces on the router.

Provides an overview of traffic engineering concepts and describes how to configure traffic engineering protocols.

List of Technical Publications xxi

M160 Internet Router Hardware Guide

Book

Multicast Protocols

Network Management

Policy Framework

Routing Protocols

Services Interfaces

VPNs

Description

Provides an overview of multicast concepts and describes how to configure multicast routing protocols.

Provides an overview of network management concepts and describes how to configure various network management features, such as SNMP, accounting options, and cflowd.

Provides an overview of policy concepts and describes how to configure routing policy, firewall filters, and forwarding options.

Provides an overview of routing concepts and describes how to configure routing, routing instances, and unicast routing protocols.

Provides an overview of the services interfaces functions of the

JUNOS software and describes how to configure the services interfaces on the router.

Provides an overview and describes how to configure Layer 2 and

Layer 3 virtual private networks (VPNs), virtual private LAN service

(VPLS), and Layer 2 circuits. Provides configuration examples.

JUNOS References

Network and Services Interfaces Command

Reference

Protocols, Class of Service, and System Basics

Command Reference

System Log Messages Reference

JUNOScope Documentation

JUNOScope Software User Guide

Describes the JUNOS Internet software operational mode commands you use to monitor and troubleshoot network and services interfaces on Juniper Networks routing platforms.

Describes the JUNOS Internet software operational mode commands you use to monitor and troubleshoot most aspects of

Juniper Networks routing platforms.

Describes how to access and interpret system log messages generated by JUNOS software modules and provides a reference page for each message.

JUNOScript API Documentation

JUNOScript API Guide

JUNOScript API Configuration Reference

JUNOScript API Operational Reference

Hardware Documentation

Hardware Guide

PIC Guide

Describes how to use the JUNOScript application programming interface (API) to monitor and configure Juniper Networks routers.

Provides reference pages for the configuration tags in the

JUNOScript API.

Provides reference pages for the operational tags in the JUNOScript

API.

JUNOS Comprehensive Index and Glossary

Comprehensive Index and Glossary Provides a complete index of all JUNOS Internet software books and the JUNOScript API Guide . Also provides a comprehensive glossary.

Describes how to install, maintain, and troubleshoot routers and router components. Each platform has its own hardware guide.

Describes the router Physical Interface Cards (PICs). Each router platform has its own PIC guide.

Describes the JUNOScope software graphical user interface (GUI), how to install and administer the software, and how to use the software to manage router configuration files and monitor router operations.

xxii List of Technical Publications

About This Guide

Book

J-series Services Router Documentation

J-series Services Router User Guide

Description

Release Notes

JUNOS Internet Software Release Notes

Hardware Release Notes

JUNOScope Software Release Notes

J-series Services Router Release Notes

Contains instructions for installing, configuring, and managing a

J-series Services Router. The guide explains how to prepare your site for installation, unpack and install the hardware, power on the router, configure secure routing, monitor network operations, and perform routine maintenance.

Provide a summary of new features for a particular software release. Software release notes also contain corrections and updates to published JUNOS and JUNOScript manuals, provide information that might have been omitted from the manuals, and describe upgrade and downgrade procedures.

Describe the available documentation for the router platform and summarize known problems with the hardware and accompanying software. Each platform has its own release notes.

Contain corrections and updates to the published JUNOScope manual, provide information that might have been omitted from the manual, and describe upgrade and downgrade procedures.

Briefly describe Services Router features, identify known hardware problems, and provide upgrade and downgrade instructions

Documentation Feedback

We encourage you to provide feedback, comments, and suggestions so that we can improve the documentation. You can send your comments to [email protected]

, or fill out the documentation feedback form at http://www.juniper.net/techpubs/docbug/docbugreport.html

. If you are using e-mail, be sure to include the following information with your comments:

Document name

Document part number

Page number

Software release version

Requesting Support

For technical support, open a support case using the Case Manager link at http://www.juniper.net/support/ or call 1-888-314-JTAC (within the United States) or

1-408-745-9500 (outside the United States).

Requesting Support xxiii

M160 Internet Router Hardware Guide xxiv Requesting Support

Part 1 Product Overview

System Overview on page 3

Hardware Component Overview on page 7

JUNOS Internet Software Overview on page 43

System Architecture Overview on page 51

Product Overview 1

2 Product Overview

Chapter 1 System Overview

This chapter provides an overview of the Juniper Networks M160 Internet router, discussing the following topics:

System Description on page 3

Field-Replaceable Units (FRUs) on page 4

System Redundancy on page 4

Safety Requirements, Warnings, and Guidelines on page 5

System Description

The M160 Internet router is a complete routing system that provides

SONET/SDH, ATM, Ethernet, and channelized interfaces for large networks and network applications, such as those supported by Internet service providers (ISPs). Application-specific integrated circuits (ASICs), a definitive part of the router design, enable the router to forward data at the high speeds demanded by current network media.

The 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

32 OC-12/STM-4, 32 OC-48/STM-16, or eight OC-192/STM-64 ports per system. The router height of 35 in. (89 cm) enables stacked installation of two M160 systems in a single floor-to-ceiling rack, for increased port density per unit of floor space.

The router’s maximum aggregate throughput is 160 gigabits per second (Gbps) simplex or 80 Gbps full duplex. The router provides very high throughput for any combination of Physical Interface Cards (PICs) that does not exceed 3

Gbps on an FPC1 or 10 Gbps on an FPC2. A combination that exceeds these numbers is supported, but constitutes oversubscription.

The router architecture cleanly separates control operations from packet forwarding operations, which helps to eliminate processing and traffic bottlenecks. Control operations in the router are performed by the Routing Engine, which runs

JUNOS Internet software to handle routing protocols, traffic engineering, policy, policing, monitoring, and configuration management. Forwarding operations in the router are performed by the Packet Forwarding Engine, which consists of hardware, including ASICs, designed by Juniper Networks.

System Description 3

M160 Internet Router Hardware Guide

Field-Replaceable Units (FRUs)

Field-replaceable units (FRUs) are router components that can be replaced at the customer site. Replacing most FRUs requires minimal router downtime.

The router uses the following types of FRUs:

Hot-removable and hot-insertable FRUs—You can remove and replace these components without powering down the router or disrupting the routing functions.

Hot-pluggable FRUs—You can remove and replace these components without powering down the router, but the routing functions of the system are interrupted when the component is removed.

Table 4 lists the FRUs for the M160 router.

Table 4: Field-Replaceable Units

Hot-Removable and

Hot-Insertable FRUs

Air filter

Fan tray (located behind the cable management system)

Flexible PIC Concentrator

(FPC)

Physical Interface Card

(PIC)

Power supply

Small form factor pluggable (SFP)

Hot-Pluggable FRUs

Miscellaneous Control

Subsystem (MCS)

Packet Forwarding Engine

Clock Generator (PCG)

Routing Engine

Switching and Forwarding

Module (SFM)

FRUs That Require Powering

Down the Router

Circuit breaker box

Connector Interface Panel (CIP)

For FRU replacement instructions, see “Replacing Hardware

Components” on page 139.

System Redundancy

The router is designed so that no single point of failure can cause the entire system to fail. The following hardware components contribute to system redundancy:

Cooling system—When the temperature inside the router is below the acceptable maximum, the cooling system’s components function at less than full speed. If the temperature becomes excessive—for example, because a cooling system component is removed—the MCS automatically increases the speed of the remaining components to reduce the temperature. The cooling

4 System Redundancy

System Overview system can function at the higher speed indefinitely. For more information, see Cooling System on page 39.

Host module (Routing Engine and MCS functioning together)—The router can have one or two host modules. If two host modules are installed, one

(the master) is active and the other is in standby mode. If the master host module (or either of its components) is removed from the chassis, the standby host module becomes active. The Routing Engine and MCS must reside in adjacent slots and be fully operational for the host module to function. For more information, see Host Module on page 22.

PCG—The router has two PCGs. Both PCGs send their clock signals to the other Packet Forwarding Engine components, along with a signal that indicates which clock is the master. If one PCG fails, the other PCG becomes the master system clock. For more information, see “Packet Forwarding Engine Clock

Generators (PCGs)” on page 18.

Power supply—The router has two load-sharing, fully redundant power supplies to distribute DC power to the other components. If one power supply fails, the second power supply can provide full power to the router’s components indefinitely. For more information, see Power System on page 35.

SFM—The router can have up to four interconnected SFMs. If one SFM fails, the switching and forwarding functions of the failed module are distributed among the remaining SFMs. Total bandwidth is reduced by 1/ n , where n is the total number of SFMs installed in the router. For example, in a system with four SFMs, each SFM provides one-fourth of the forwarding capacity. For more information, see “Switching and Forwarding Module (SFM)” on page 19.

In the base configuration, the router has one host module and multiple SFMs,

PCGs, power supplies, and cooling system components.

Safety Requirements, Warnings, and Guidelines

To avoid harm to yourself or the router as you install and maintain it, you need to follow the guidelines for working with and near electrical equipment, as well as the safety procedures for working with Internet routers. For a discussion of how to make the installation site a safe environment, see “Preparing for Router

Installation” on page 59. For a list of safety warnings, see “Safety and Regulatory

Compliance Information” on page 221 and particularly “Electrical Safety Guidelines and Warnings” on page 227. However, providing an exhaustive set of guidelines for working with electrical equipment is beyond the scope of this manual.

Safety Requirements, Warnings, and Guidelines 5

M160 Internet Router Hardware Guide

6 Safety Requirements, Warnings, and Guidelines

Chapter 2 Hardware Component Overview

This chapter provides an overview of the hardware components on the M160

Internet router:

Chassis on page 7

Packet Forwarding Engine on page 11

Host Module on page 22

Craft Interface on page 27

Connector Interface Panel (CIP) on page 32

Power System on page 35

Cooling System on page 39

Cable Management System on page 41

Chassis

The router chassis is a rigid sheet metal structure that houses the other hardware components. The chassis is 17.5 in. (44.5 cm) wide and 29 in.

(73.6 cm) deep. The chassis height of 35 in. (89 cm) enables stacked installation of two M160 routers in a single floor-to-ceiling rack. For more information, see Rack Requirements on page 59.

The two front support posts and center-mounting brackets (one on each side) extend the chassis width to 19 in. (48.3 cm) and enable installation into either a front-mount or a center-mount rack.

Figure 1, Figure 2, and Figure 3 show three views of the router chassis.

Chassis 7

M160 Internet Router Hardware Guide

Figure 1: Front of Chassis

Craft interface

FPCs

CIP

ESD point

Cable management system

Air filter

8 Chassis

Figure 2: Rear of Chassis with Component Cover in Place

Component cover

ESD point

Lower impeller

Power supplies

Upper impeller

PCG 0

PCG 1

Grounding points

Circuit breaker box

Hardware Component Overview

Chassis 9

M160 Internet Router Hardware Guide

Figure 3: Rear of Chassis with Component Cover Removed

SFMs

MCS 0

Routing Engines

MCS 1

SFMs

SFM 0

SFM 1

MCS 0

RE 0

RE 1

MCS 1

SFM 2

SFM 3

PCG 0

PCG 1

PCGs

10 Chassis

The chassis includes the following electrical safety components:

Two electrostatic discharge (ESD) points (banana plug receptacles), one front and one rear, as shown in Figure 1 and Figure 2

Two internally threaded grounding points, as shown in Figure 2

WARNING: Before removing or installing components of a functioning router, attach an ESD strap to an ESD point and place the other end of the strap around your bare wrist. Failure to use an ESD strap could result in damage to the router.

The router must be connected to earth ground during normal operation.

Hardware Component Overview

For further safety information, see “Safety and Regulatory Compliance Information” on page 221.

Table 5 summarizes physical specifications for the router chassis.

Table 5: Chassis Physical Specifications

Description

Chassis height

Chassis width

Value

35 in. (89 cm)

17.5 in. (44.5 cm) for sides of chassis

19 in. (48.3 cm) with front support posts and center-mounting brackets

29 in. (73.6 cm)

370.5 lb (168 kg)

Chassis depth

Weight, maximum configuration

Weight, minimum configuration

Thermal output

190 lb (86 kg)

9400 BTU/hour

Packet Forwarding Engine

The Packet Forwarding Engine is a multicomponent system that uses application-specific integrated circuits (ASICs) to perform Layer 2 and Layer 3 packet switching, route lookups, and packet forwarding. The ASICs include the

Distributed Buffer Manager ASIC, Internet Processor II ASIC, I/O Manager ASIC,

Packet Director ASIC, and media-specific controller ASICs.

The Packet Forwarding Engine has the following components:

Midplane—Physically separates front and rear cavities inside the chassis, distributes power from the power supplies, and transfers packets and signals between router components, which plug into it.

Physical Interface Card (PIC)—Physically connects the router to network media such as OC-12/STM-4, OC-48/STM-16, Ethernet, and channelized interfaces.

PICs are housed in Flexible PIC Concentrators (FPCs). (Quad-wide PICs, such as the OC-192/STM-64 SONET/SDH PIC, are exceptions. Such PICs occupy

Packet Forwarding Engine 11

M160 Internet Router Hardware Guide

Midplane

an entire FPC slot in the chassis and insert directly into the slot rather than into an FPC card carrier.)

Flexible PIC Concentrator (FPC)—Processes incoming and outgoing packets.

Up to eight FPCs plug into the midplane from the front of the chassis. Each

FPC accommodates up to four PICs.

Packet Forwarding Engine Clock Generator (PCG)—Sends clock signals to the other Packet Forwarding Engine components. Two PCGs plug into the midplane from the rear of the chassis.

Switching and Forwarding Module (SFM)—Performs route lookup, filtering, and switching. Up to four SFMs plug into the midplane from the rear of the chassis.

For information about Packet Forwarding Engine components, see the following sections:

Midplane on page 12

Physical Interface Cards (PICs) on page 13

Flexible PIC Concentrators (FPCs) on page 14

Packet Forwarding Engine Clock Generators (PCGs) on page 18

Switching and Forwarding Module (SFM) on page 19

The midplane is a panel located in the center of the chassis, running from side to side and forming the rear of the FPC card cage (see Figure 4). All router components other than PICs plug directly into the midplane. The midplane contains an EEPROM that stores the serial number and revision level of the midplane.

The midplane performs the following functions:

Transfer of packets—The midplane accepts an incoming packet after it is processed by an FPC, and transmits it to an SFM. The SFM performs switching and forwarding functions and transfers outgoing packets back across the midplane to the FPCs for transmission to the network.

Power distribution—The midplane distributes power to all router components from the power supplies attached to it.

Signal connectivity—The midplane transports the signals exchanged by system components for monitoring and control purposes.

12 Packet Forwarding Engine

Hardware Component Overview

Figure 4: Midplane

Midplane

FPC card cage

Physical Interface Cards (PICs)

Physical Interface Cards (PICs) physically connect the router to network media. They are housed in Flexible PIC Concentrators (FPCs); for more information about FPCs, see “Flexible PIC Concentrators (FPCs)” on page

14. (Quad-wide PICs, such as the OC-192/STM-64 SONET/SDH PIC, are exceptions. Such PICs occupy an entire FPC slot in the chassis and insert directly into the slot rather than into an FPC card carrier.)

PICs receive incoming packets from the network and transmit outgoing packets to the network, performing framing and line-speed signaling for their media type as required. PICs also encapsulate outgoing packets received from the

FPCs before transmitting them. The controller ASIC on each PIC performs additional control functions specific to the PIC media type.

The router supports various PICs, including ATM, Channelized, Gigabit

Ethernet, IP Services, and SONET/SDH interfaces. For complete PIC specifications, see the M160 Internet Router PIC Guide .

Packet Forwarding Engine 13

M160 Internet Router Hardware Guide

Some PICs, such as selected Gigabit Ethernet PICs, accept small form factor pluggables (SFPs), which are fiber-optic transceivers that can be removed from the PIC. Various SFPs have different reach characteristics. You can mix them in a single PIC and change the combination dynamically. SFPs are hot-removable and hot-insertable, as described in Field-Replaceable Units (FRUs) on page 4. For

SFP replacement instructions, see “Replace an SFP” on page 190. For information about PICs that use SFPs, see the M160 Internet Router PIC Guide .

You can install up to four PICs in an FPC. The number of ports on a PIC depends on the type of PIC. PICs are hot-removable and hot-insertable, as described in Field-Replaceable Units (FRUs) on page 4. For PIC replacement instructions, see “Replacing a PIC” on page 179.

PIC Components

Most PICs supported on the M160 router have the following components. For complete specifications, see the M160 Internet Router PIC Guide . For information about pinouts for PIC cable connectors, see “Cable Connector Pinouts” on page 269.

One or more cable connector ports—Accept a network media connector.

LEDs—Indicate PIC and port status. Most PICs have an LED labeled STATUS on the PIC faceplate. Some PICs have additional LEDs, often one per port. The meaning of the LED states differs for various PICs. For more information, see the M160 Internet Router PIC Guide .

Offline button—Prepares the PIC for removal from the FPC when pressed. For the PICs that install on an FPC1, the offline button for each PIC is next to it on the FPC card carrier. For the PICs that install on an FPC2, the offline button is on the PIC faceplate. See Figure 6.

Flexible PIC Concentrators (FPCs)

Flexible PIC Concentrators (FPCs) house the PICs that connect the router to network media (for information about PICs, see “Physical Interface Cards (PICs)” on page

13). The main function of an FPC is to connect the PICs installed in it to the other router components. An I/O Manager ASIC on the FPC divides each incoming data packet into 64-byte cells and passes the cells through the midplane to the SFM, where another ASIC decides how to distribute them among the memory buffers located on and shared by all installed FPCs. After the SFM decides how to forward a packet, an I/O Manager ASIC on the FPC reassembles the corresponding data cells back into network-packet form and passes the packet to the appropriate PIC for transmission to the network. For more information, see “Data Flow through the

Packet Forwarding Engine” on page 52.

Up to eight FPCs install vertically into the midplane from the front of the chassis. The FPC slots are numbered from FPC0 to FPC7 , left to right. Each FPC accommodates up to four PICs. The PIC slots in each FPC are numbered from

0 (zero) through 3 , top to bottom. An FPC can be installed into any FPC slot, regardless of the PICs it contains, and any combination of slots can be used. If a

14 Packet Forwarding Engine

Hardware Component Overview slot is empty, you must install a blank FPC panel to shield it, so that cooling air can circulate properly throughout the card cage.

Figure 5, which shows a chassis with an FPC in slot FPC0 , omits the blank FPC panels to show the position of the FPC in the card cage.

Figure 5: Front of Chassis with Four-PIC FPC Installed in Slot FPC0

For information about FPC components and types, see the following sections:

FPC Components on page 16

FPC Types on page 17

Packet Forwarding Engine 15

M160 Internet Router Hardware Guide

FPC Components

An FPC has the following components:

FPC card carrier—Houses the ASICs, connectors, and processor subsystem.

Four I/O Manager ASICs—Parse Layer 2 and Layer 3 data and perform encapsulation and segmentation. The I/O Manager ASICs divide incoming packets into 64-byte data cells for easier processing, and reassemble the cells for each packet after the forwarding decision is made for it. Enhanced FPCs have I/O Manager ASICs capable of enhanced quality of service.

Two Packet Director ASICs—Transfer packets between the PICs and the I/O

Manager ASICs: one directs incoming packets from the PICs to the I/O

Manager ASICs, while the second directs outgoing packets from the I/O

Manager ASICs to the PICs.

Eight identical synchronous DRAM (SDRAM) dual inline memory modules

(DIMMs)—Form the memory pool shared with the other FPCs installed in the router.

Parity-protected synchronous SRAM (SSRAM)—Stores data structures used by the I/O Manager ASICs.

Processor subsystem—Manages packet handling in the FPC and communication with the SFM. It is a PowerPC 603e-based CPU with parity-protected DRAM.

EEPROM—Stores the serial number and revision level of the FPC.

Two LEDs—Indicate FPC status. The LED labeled OK is green and the one labeled FAIL is red. The LEDs for each FPC are located on the router craft interface. For more information, see “FPC LEDs and Offline Button” on page 31.

Offline button—Prepares the FPC for removal from the router when pressed.

Like the LEDs, an offline button is located on the craft interface. For more information, see “FPC LEDs and Offline Button” on page 31.

Four PIC offline buttons (on FPC1 only)—Prepare each corresponding PIC for removal from the FPC.

Ejector levers—Control the locking system that secures the FPC in the card cage.

NOTE: For specific information about FPC components (for example, the amount of memory available), issue the show chassis fpc command.

16 Packet Forwarding Engine

Hardware Component Overview

FPC Types

The router supports two types of FPC, shown in Figure 6:

FPC1 (standard or enhanced)—Supports PICs including single-port

OC-12/STM-4 and Gigabit Ethernet.

FPC2 (standard or enhanced)—Supports higher-speed PICs including

OC-48/STM-16 and Tunnel services.

You can install any combination of FPC types together on the router.

FPCs are hot-removable and hot-insertable, as described in Field-Replaceable Units

(FRUs) on page 4. When you remove or install an FPC, packet forwarding halts for about 200 ms while the Packet Forwarding Engine adjusts to the change in the amount of memory available in the pool located on and shared by all FPCs.

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. For FPC replacement instructions, see “Replacing an FPC” on page 169.

Enhanced FPCs have I/O Manager ASICs capable of enhanced quality of service, and 2 MB of SSRAM. Enhanced FPCs can be identified through the CLI, or by a sticker on the faceplate.

The PICs that install on both types of FPC are also hot-removable and hot-insertable.

For more information, see “Physical Interface Cards (PICs)” on page 13.

Packet Forwarding Engine 17

M160 Internet Router Hardware Guide

Figure 6: FPC1 and FPC2

Ejector lever

FPC 1

Ejector lever

FPC 2

Offline buttons

(on FPC)

Offline buttons

(on PICs)

Ejector lever Ejector lever

Packet Forwarding Engine Clock Generators (PCGs)

The router has two Packet Forwarding Engine Clock Generators (PCGs) installed in the slots at the rear of the chassis that are labeled PCG 0 and PCG 1 , as shown in Figure 3. The PCGs generate a 125-MHz clock signal used to gate packet processing. During startup, the active Routing Engine determines which PCG is master and which is backup, and the MCS relays the decision to the PCGs and to the modules and ASICs in the Packet Forwarding Engine that use the clock signal.

The modules and ASICs then use only the signal from the master source.

PCGs are hot-pluggable, as described in Field-Replaceable Units (FRUs) on page 4.

Removal or failure of the backup PCG does not affect router function. When the master PCG fails or is removed from the chassis, however, the Packet Forwarding

Engine resets so that the components start using the signal from the other PCG

(which becomes the master). Packet forwarding halts while there is no clock signal, because the Packet Forwarding Engine does not accept incoming packets. For

PCG replacement instructions, see “Replacing a PCG” on page 176.

18 Packet Forwarding Engine

Hardware Component Overview

PCG Components

Each PCG (shown in Figure 7) has the following components:

Signal generator—Provides a 125-MHz system clock signal.

EEPROM—Stores the serial number and revision level of the PCG.

Three LEDs—Indicate PCG status. There is a blue one labeled MASTER , a green one labeled OK , and an amber one labeled FAIL . Table 6 describes the LED states.

Offline button—Prepares the PCG for removal from the router when pressed.

Figure 7: Packet Forwarding Engine Clock Generator

Offline button

LEDs

Table 6: States for PCG LEDs

Label

MASTER

Color

Blue

Green

FAIL Amber

State Description

On steadily PCG is master.

On steadily PCG is functioning normally.

Blinking PCG is starting up.

On steadily PCG has failed.

Switching and Forwarding Module (SFM)

The Switching and Forwarding Module (SFM) performs route lookup, filtering, and switching on incoming data packets, then directs outbound packets to the appropriate FPC for transmission to the network. It can process 40 million packets per second (Mpps).

Up to four SFMs can be installed in the router, processing a total of 160 Mpps.

The SFMs are hot-pluggable, as described in Field-Replaceable Units (FRUs) on page 4. Removing or inserting an SFM causes a brief interruption in forwarding performance (about 500 ms) as the Packet Forwarding Engine reconfigures the distribution of packets across the remaining SFMs.

For SFM replacement instructions, see “Replacing an SFM” on page 188.

Packet Forwarding Engine 19

M160 Internet Router Hardware Guide

The SFM communicates with the Routing Engine using a dedicated 100-Mbps Fast

Ethernet link that transfers routing table data from the Routing Engine to the forwarding table in the Internet Processor II ASIC. The link is also used to transfer from the SFM to the Routing Engine routing link-state updates and other packets destined for the router that have been received through the router interfaces.

The ASICs and other components on the SFM provide the following functions:

Route lookups—The Internet Processor II ASIC on each SFM performs route lookups using the forwarding table stored in SSRAM.

Management of shared memory on the FPCs—One Distributed Buffer Manager

ASIC receives the 64-byte data cells into which the I/O Manager ASICs on each

FPC divide incoming packets, and uniformly allocates them throughout the shared memory buffers located on the FPCs.

Transfer of outgoing data packets—The second Distributed Buffer Manager

ASIC passes notification of the forwarding decision for each packet to an I/O

Manager ASIC so that data cells for the outgoing packet can be reassembled for transmission to the network.

Transfer of exception and control packets—The Internet Processor II ASIC passes exception packets to the microprocessor on the SFM, which processes almost all of them. The SFM sends any remaining exception packets to the Routing Engine for further processing. When the SFM detects an error originating in the Packet Forwarding Engine, it sends it to the Routing Engine using system logging (syslog) messages.

SFM Components

Each SFM is a two-board system, as shown in Figure 8. It has the following components:

Two Distributed Buffer Manager ASICs—Process incoming and outgoing packets: one distributes data cells (which the I/O Manager ASIC on each

FPC derives from incoming packets) to the shared memory buffers on the

20 Packet Forwarding Engine

Hardware Component Overview

FPCs, while the second forwards notification of routing decisions to the

I/O Manager ASICs.

One Internet Processor II ASIC—Performs route lookups and makes routing decisions.

Parity-protected SSRAM—Stores the forwarding table.

Processor subsystem—Manages SFM functions and handles exception packets.

The processor has the following components:

One PowerPC 603e processor

Parity-protected Level 2 cache

Parity-protected DRAM

EEPROM—Stores the serial number and revision level.

Offline button—Prepares the SFM for removal from the router when pressed.

Two LEDs—Indicate SFM status. There is a green one labeled OK and an amber one labeled FAIL . Table 7 describes the LED states.

Ejector handles and locking tabs—Control the locking system that secures the

SFM in the chassis.

NOTE: For specific information about SFM components (for example, the amount of

SSRAM and DRAM), issue the show chassis sfm detail command.

Figure 8: Switching and Forwarding Module

Ejector handle

Ejector locking tab

Offline button LEDs

Packet Forwarding Engine 21

M160 Internet Router Hardware Guide

Table 7: States for SFM LEDs

Label

Color

Green

FAIL Amber

State Description

On steadily SFM is functioning normally.

Blinking SFM is starting up.

On steadily SFM has failed.

Host Module

The host module constructs routing tables, performs system management functions, and generates the SONET/SDH clock signal for SONET/SDH interfaces. It consists of a paired Routing Engine and Miscellaneous Control Subsystem (MCS).

For a host module to function, both of its components—Routing Engine and

MCS—must be installed and operational. One or two host modules can be installed into the midplane from the rear of the chassis, as shown in Figure 3: the Routing

Engine slot labeled RE 0 is below the MCS slot labeled MCS 0 and the RE 1 slot is above the MCS 1 slot.

If two host modules are installed, both are powered on, but only one is active (the master); the second host module is in standby mode and performs no functions.

By default, the master host module is the one with components installed in the

RE 0 and MCS 0 slots. To change the default master Routing Engine, include the appropriate [edit chassis redundancy routing-engine] statement in the configuration, as described in the section about Routing Engine redundancy in the JUNOS Internet

Software Configuration Guide: Getting Started .

The host module components are hot-pluggable, as described in Field-Replaceable

Units (FRUs) on page 4. Removal or failure of one or both components in the standby host module does not affect router function. If one or both components in the master host module is removed from the chassis, the effect depends on whether two host modules are installed:

If there is only one host module, packet forwarding halts until both the Routing

Engine and MCS are reinstalled and functioning normally.

If there are two host modules, the effect depends on the software configuration:

If the Routing Engines are running JUNOS Release 6.0 or later and are configured for graceful switchover, the standby Routing Engine automatically assumes mastership without interruption of forwarding performance. For information about configuring graceful switchover, see the section about Routing Engine redundancy in JUNOS Internet Software

Configuration Guide: Getting Started .

Otherwise, forwarding halts while standby host module becomes the master and the new master Routing Engine resets the Packet Forwarding

Engine.

22 Host Module

Hardware Component Overview

For host module replacement instructions, see “Replacing an MCS” on page 159 and “Replacing a Routing Engine” on page 165.

Note that the effect of a hardware or software failure on one or both components in the master host module differs from the effect of removing a component that belongs to the master host module:

With the default router configuration, in case of failure you must correct the problem manually. You can issue the appropriate request chassis routing-engine master command to switch mastership to the other

Routing Engine, for example. For information about the command, see the

JUNOS Internet Software Operational Mode Command Reference: Protocols, Class of Service, Chassis, and Management .

On routers with two installed Routing Engines running JUNOS Release

6.0 or later, you can configure graceful switchover of Routing Engines, as previously described for the case of Routing Engine removal. When the standby Routing Engine stops receiving keepalive signals from the master

Routing Engine, it automatically assumes mastership without interruption of forwarding performance.

On routers with two installed Routing Engines running any JUNOS release, you can configure automatic Routing Engine mastership failover. When the standby Routing Engine stops receiving keepalive signals from the master

Routing Engine, it automatically assumes mastership. Packet forwarding halts while the Packet Forwarding Engine components reset and connect to the new master Routing Engine.

For information about configuring graceful switchover or automatic mastership failover, see the section about Routing Engine redundancy in the JUNOS Internet

Software Configuration Guide: Getting Started .

For more information about host module components, see the following sections:

Routing Engine on page 23

Miscellaneous Control Subsystem (MCS) on page 25

Routing Engine

The Routing Engine is an Intel-based PCI platform that runs JUNOS Internet software. Software processes that run on the Routing Engine maintain the routing tables, manage the routing protocols used on the router, control the router’s interfaces, control some chassis components, and provide the interface for system management and user access to the router.

For a description of the Routing Engine’s role in router architecture, see Routing Engine Architecture on page 53.

One or two host modules (paired Routing Engine and MCS) can be installed into the midplane from the rear of the chassis, as shown in Figure 3. If two host modules are installed, the Routing Engines together determine which is

Host Module 23

M160 Internet Router Hardware Guide the master and which is in standby mode (and so performs no functions). By default, the Routing Engine in the slot labeled RE0 is the master. The master

Routing Engine also determines which of the two PCGs is the master.

The Routing Engine is hot-pluggable, as described in Field-Replaceable

Units (FRUs) on page 4. For information about the effect of removing a

Routing Engine, see Host Module on page 22. For replacement instructions, see “Replacing a Routing Engine” on page 165.

Routing Engine Components

The Routing Engine (shown in Figure 9) is a two-board system with the following components:

CPU—Runs JUNOS Internet software to maintain the router’s routing tables and routing protocols. It has a Pentium-class processor.

SDRAM—Provides storage for the routing and forwarding tables and for other

Routing Engine processes.

Compact flash drive—Provides primary storage for software images, configuration files, and microcode. The drive is fixed and inaccessible from outside the router.

Hard disk—Provides secondary storage for log files, memory dumps, and rebooting the system if the flash drive fails.

PC card slots—Accept removable PC cards, which store software images for system upgrades.

LED—Indicates disk activity for the internal IDE interface. It does not necessarily indicate 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).

EEPROM—Stores the serial number of the Routing Engine.

Reset button—Reboots the Routing Engine when pressed.

NOTE: The LEDs that report host module status (and by implication Routing Engine status) are on the craft interface rather than the Routing Engine faceplate. For more information, see “Host Module LEDs” on page 31.

NOTE: The appearance and position of electronic components or the PC card slot on your Routing Engine might differ from Figure 9 and other figures in this

24 Host Module

Hardware Component Overview

Figure 9: Routing Engine

Routing Engine 333

Extractor clip document that depict the Routing Engine. These differences do not affect Routing

Engine installation and removal or functionality.

For specific information about Routing Engine components (for example, the amount of SDRAM), issue the show chassis routing-engine command.

NOTE: If two Routing Engines are installed, they must both be the same version.

Routing Engine 600

Extractor clip

JUNIP

ER NE

TWOR

KS LAB

EL THIS

SIDE

LED

PC card slot

LED

Extractor clip

Miscellaneous Control Subsystem (MCS)

The Miscellaneous Control Subsystem (MCS) works with its companion Routing

Engine to provide control and monitoring functions for router components. It also generates a clock signal for the SONET/SDH interfaces on the router.

One or two host modules (paired MCS and Routing Engine) can be installed into the midplane from the rear of the chassis, as shown in Figure 3. Only one host module is active at a time, with the optional second host module in standby mode. For more information about host module interdependence and redundancy, see Host Module on page 22.

The MCS performs the following functions:

Monitoring and control of router components—The MCS collects statistics from all sensors in the system. When it detects a failure or alarm condition, it sends a signal to the Routing Engine, which generates control messages

Host Module 25

M160 Internet Router Hardware Guide or sets an alarm. The MCS also relays control messages from the Routing

Engine to the router components.

Controlling component power-up and power-down—The MCS controls the power-up sequence of router components as they start, and powers down components when their offline buttons are pressed.

Signaling of mastership—In a router with more than one host module, the

MCS signals to all router components which host module is the master and which is the standby. It relays the mastership signal for the two PCGs as well.

Providing SONET/SDH clock source—The MCS generates a 19.44-MHz

SONET/SDH clock signal, along with a signal that indicates which MCS is the master SONET/SDH clock generator (if two MCSs are installed).

Clock monitoring—The MCS monitors the PCG system clock and its

SONET/SDH clock to verify that they are providing the expected signal. It generates an alarm if a clock signal is incorrect.

Control of FPC resets—If the MCS detects errors in an FPC, it attempts to reset the FPC. After three unsuccessful reset attempts, the MCS takes the

FPC offline and informs the Routing Engine. Other FPCs are unaffected, and system operation continues.

MCS Components

Each MCS (shown in Figure 10) has the following components:

PCI interface—Connects the MCS to the Routing Engine.

100-Mbps Ethernet switch—Carries signals and monitoring data between router components.

19.44-MHz stratum 3 reference clock—Generates clock signal for SONET/SDH

PICs.

I2C controller—Monitors the status of router components.

Three LEDs—Indicate MCS status. There is a blue one labeled MASTER , a green one labeled OK , and an amber one labeled FAIL . Table 8 describes the LED states.

Offline button—Prepares the MCS for removal from the router when pressed.

Extractor clips—Control the locking system that secures the MCS in the chassis.

26 Host Module

Hardware Component Overview

Figure 10: Miscellaneous Control Subsystem

Extractor clip

Offline button

LEDs

Extractor clip

Table 8: States for MCS LEDs

Label

MASTER

Color

Blue

Green

FAIL Amber

State Description

On steadily MCS is master.

On steadily MCS is functioning normally.

Blinking MCS is starting up.

On steadily MCS has failed.

Craft Interface

The craft interface provides status and troubleshooting information at a glance and has buttons for deactivating alarms and preparing FPCs for removal. The craft interface is located on the front of the chassis above the FPC card cage, as shown in

Figure 1. It includes the elements shown in Figure 11.

Craft Interface 27

M160 Internet Router Hardware Guide

Figure 11: Craft Interface

Yellow alarm

LED

Red alarm

LED

Alarm cutoff button

ACO/LT

Navigation buttons

ENTER

LCD Navigation buttons

Host module

LEDs

OFFLINE ONLINE MASTER

HOST0

OFFLINE ONLINE MASTER

HOST1

FAIL

FPC 0

OK FAIL

FPC 1

OK FAIL

FPC 2

OK FAIL

FPC 3

OK FAIL

FPC 4

OK FAIL

FPC 5

OK FAIL

FPC 6

OK FAIL

FPC 7

FPC LEDs and offline buttons (for FPC 0-7)

NOTE: The LEDs for some router components are located on the component faceplate, rather than on the craft interface. For information about those LEDs, see the following sections:

“PCG Components” on page 19

“SFM Components” on page 20

“MCS Components” on page 26

Power System on page 35

For information about the elements on the craft interface, see the following sections:

Alarm LEDs and Alarm Cutoff/Lamp Test Button on page 28

LCD and Navigation Buttons on page 29

Host Module LEDs on page 31

FPC LEDs and Offline Button on page 31

Alarm LEDs and Alarm Cutoff/Lamp Test Button

Two large alarm LEDs are located at the upper left of the craft interface

(see Figure 11). 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 “Alarm

28 Craft Interface

Hardware Component Overview

Relay Contacts” on page 34. The LCD on the craft interface reports the cause of the alarm, as described in “LCD Alarm Mode” on page 30.

To deactivate red and yellow alarms, press the button labeled ACO/LT (for “alarm cutoff/lamp test”), which is located to the left of the alarm LEDs. Deactivating an alarm 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 9 describes the alarm LEDs and alarm cutoff button in more detail.

Table 9: Alarm LEDs and Alarm Cutoff/Lamp Test Button

Shape Color

Red

Yellow

—

State Description

On steadily Critical alarm LED—Indicates a critical condition that can cause the router to stop functioning.

Possible causes include component removal, failure, or overheating.

On steadily Warning alarm LED—Indicates a serious but nonfatal error condition, such as a maintenance alert or a significant increase in component temperature.

— Alarm cutoff/lamp test button—Deactivates red and yellow alarms. Causes all LEDs on the craft interface to light (for testing purposes), when pressed and held.

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, as described in the following sections:

LCD Idle Mode on page 29

LCD Alarm Mode on page 30

LCD Idle Mode

During normal operation, the LCD operates in idle mode and reports current status information, as shown in Figure 12.

Craft Interface 29

M160 Internet Router Hardware Guide

Figure 12: LCD in Idle Mode

ENTER

Router1

Up 2 + 11:59

Power OK

The lines in the display report the following information:

First line—Routing node 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 two-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 Internet Software Operational Mode Command Reference:

Protocols, Class of Service, Chassis, and Management .

LCD Alarm Mode

When a red or yellow alarm occurs, the LCD switches to alarm mode and reports about the alarm condition, as shown in Figure 13.

Figure 13: LCD in Alarm Mode

ENTER

Router1

R: PEM 1 Input Failure

Y: Change air filter

30 Craft Interface

Hardware Component Overview

The lines in the display report the following information:

First line—Routing node name.

Second line—Number of active alarms.

Third and fourth lines—Individual alarm messages, with the most severe condition shown first. The prefix on each line indicates whether the alarm is a red ( R ) or yellow ( Y ) alarm.

For a list of alarm messages that can appear on the LCD, see “Chassis and Interface Alarm Messages” on page 209.

Host Module LEDs

At the upper right corner of the craft interface (see Figure 11) are two sets of LEDs that indicate host module status: the set labeled HOST0 reports the status of the

Routing Engine in slot RE 0 and MCS in slot MCS 0 , and the set labeled HOST1 reports the status of the Routing Engine in slot RE 1 and the MCS in slot MCS 1 . Each set includes three LEDs—a green one labeled MASTER , another green one labeled

ONLINE , and a red one labeled OFFLINE . Table 10 describes the LED states.

Table 10: States for Host Module LEDs

Label

MASTER

ONLINE

OFFLINE

Color

Green

Red

State Description

On steadily Host module is functioning as master.

On steadily Host module components (Routing Engine and

MCS) are installed and functioning normally.

Blinking Host module is starting up.

On steadily One or both host module components are not installed or have failed.

FPC LEDs and Offline Button

The LEDS and offline button for each FPC are located directly above it on the craft interface, as shown in Figure 11. The red LED labeled FAIL and the green

LED labeled OK indicate FPC status, as described in Table 11.

The offline button, labeled with the FPC slot number (for example, FPC2 ), prepares the FPC for removal from the router when pressed.

Craft Interface 31

M160 Internet Router Hardware Guide

Table 11: States for FPC LEDs

Label

Color

Green

FAIL Red

State Description

On steadily FPC is functioning normally.

Blinking FPC is starting up or going offline.

Off FPC is offline or not installed.

On steadily FPC has failed.

Connector Interface Panel (CIP)

The Connector Interface Panel (CIP) is located at the left side of the FPC card cage, as shown in Figure 1. It houses Routing Engine management ports and alarm relay contacts, as shown in Figure 14 and described in the following sections:

Routing Engine Management Ports on page 33

BITS Input Ports on page 34

Alarm Relay Contacts on page 34

32 Connector Interface Panel (CIP)

Hardware Component Overview

Figure 14: Connector Interface Panel

HOST

ETHERNET

ACT

YEL=10Mb

GRN=100Mb

CONSOLE

AUXILIARY

BITS A

LINK

BITS B

LINK

RED ALARM

YELLOW

ALARM

CONSOLE

AUXILIARY

HOST

ETHERNET

ACT

YEL=10Mb

GRN=100Mb

Routing

Engine ports

BITS input ports

Alarm relay contacts

Routing Engine Management Ports

On the upper half of the CIP are two sets of ports for connecting the Routing

Engines to one or more external devices on which system administrators can issue

JUNOS command-line interface (CLI) commands to manage the router. The set of ports labeled HOST0 connects to the Routing Engine in the slot labeled RE 0 , and the set labeled HOST1 connects to the Routing Engine in the slot labeled RE 1 .

Connector Interface Panel (CIP) 33

M160 Internet Router Hardware Guide

The ports with the indicated label in each set function as follows:

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 LED labeled ETHERNET lights yellow or green for a 10-Mbps or 100-Mbps connection, and the LED labeled

ACT lights green when traffic is passing through the port.

CONSOLE —Connects the Routing Engine to a system console through an

RS-232 (EIA-232) serial cable.

AUXILIARY — Connects the Routing Engine to a laptop, modem, or other auxiliary device through an RS-232 (EIA-232) serial cable.

For information about the pinouts for the connectors, see “Cable

Connector Pinouts” on page 269.

Figure 15 shows the ports that connect to the Routing Engine installed in slot RE 0.

The arrangement of ports for the Routing Engine installed in slot RE 1 is the same.

Figure 15: Routing Engine Interface Ports for Host Module 0

Ethernet

LEDs

HOST

ETHERNET

ACT

YEL=10Mb

GRN=100Mb

Ethernet port

Console port

CONSOLE

Auxiliary port

AUXILIARY

BITS Input Ports

In the center of the CIP are two ports labeled BITS A and BITS B (see Figure 16). The router does not support BITS input, so these ports do not function.

Alarm Relay Contacts

At the bottom of the CIP are two relay contacts for connecting the router to external alarm-reporting devices, the upper labeled RED ALARM and the lower

34 Connector Interface Panel (CIP)

Hardware Component Overview

YELLOW ALARM (see Figure 16). A system condition that causes the red or yellow alarm LED to light on the craft interface also activates the corresponding alarm relay contact. For instructions for attaching a device to the alarm relay contacts, see “Connecting to an External Alarm-Reporting Device” on page 115.

Figure 16: Alarm Relay Contacts and BITS Input Ports

BITS A

LINK

BITS B

BITS input ports

LINK

RED ALARM

YELLOW

ALARM

Alarm relay contacts

Power System

The router uses DC power. There are two load-sharing, pass-through power supplies located at the bottom rear of the chassis, as shown in Figure 2. The power supplies connect to the midplane, which distributes power to router components according to their individual voltage requirements. When the power supplies are installed and operational, they automatically share the electrical load. If a power supply stops functioning for any reason, the remaining power supplies instantly begin providing all the power the router needs for normal functioning and can provide full power indefinitely.

Power supplies are hot-removable and hot-insertable, as described in

Field-Replaceable Units (FRUs) on page 4. To avoid electrical injury, carefully follow the instructions in “Replacing a Power Supply” on page 197.

NOTE: After powering off a power supply, wait at least 60 seconds before turning it back on. After powering on a power supply, wait at least 60 seconds before turning it off.

If the router is completely powered down when you power on the power supply, the Routing Engine boots as the power supply completes its startup sequence. If

Power System 35

M160 Internet Router Hardware Guide

Power Supply

the Routing Engine finishes booting and you need to power down the router again, first issue the CLI request system halt command. For more information, see

“Disconnecting Power from the Router” on page 200.

After a power supply is powered on, it can take up to 60 seconds for status indicators—such as LEDs on the power supply, show chassis commands, and messages on the craft interface LCD—to indicate that the power supply is functioning normally. Ignore error indicators that appear during the first 60 seconds.

See the following sections for further information:

Power Supply on page 36

Circuit Breaker Box on page 38

Fuses on page 39

The router has two load-sharing, pass-through power supplies, located at the bottom rear of the chassis, as shown in Figure 2. For information about power supply redundancy and replaceability, see Power System on page 35.

Each power supply has the following components (see Figure 17 and Figure 18):

LEDs—Indicate power supply status. There is a green one labeled CB ON , a blue one labeled OUTPUT OK , and an amber one labeled CB OFF . The original power supply also has an amber LED labeled NO AIRFLOW . Table 12 describes the LED states.

In addition, power supply failure triggers the red alarm LED on the craft interface and the RED ALARM relay contact on the CIP. See “Alarm LEDs and

Alarm Cutoff/Lamp Test Button” on page 28.

Self-test button—Tests the power supply. Do not press this button; it is for use by qualified service personnel only.

36 Power System

Hardware Component Overview

Figure 17: Original Power Supply

Figure 18: Enhanced Power Supply

CB ON

OUTPUT O

NO A IRFLO

CB OFF

PEM

SELF TEST

ENHANCED PEM

CAUTION

TURN OFF CIRCUIT

BREAKER BEFORE REMOVING

OR INSERTING PEM.

INSERT PEM THEN

TURN ON CIRCUIT

BREAKER AFTER 1 MINUTE.

CB ON

OUTPUT OK

CB OFF

TIGHTEN THESE SCREWS FIRST

Table 12: States for Power Supply LEDs

Label

CB ON

Color

Green

OUTPUT OK Blue

State Description

On steadily Power supply is inserted correctly and is receiving power. Circuit breaker is on.

On steadily Power supply is inserted and is functioning normally.

Blinking Power supply is not functioning, is starting up, or is not properly inserted, or airflow is not sufficient.

Power System 37

M160 Internet Router Hardware Guide

Label

AIRFLOW

(original power supply only)

CB OFF

Color

Amber

State Description

On steadily Power supply is inserted, but airflow around the power supply is not sufficient.

On steadily Power supply is functioning, but the circuit breaker is off.

Table 13 lists electrical specifications for the power supply.

Table 13: Electrical Specifications for Power Supply

Description

Maximum power output

DC input voltage

DC input current rating

Output voltages

Specification

Original power supply: 2400 W; nonisolated

Enhanced power supply: 3000 W; nonisolated

Nominal: –48 VDC, –60 VDC

Operating range: –42 to –72 VDC

80 A @ –48 V

+48 V @ 8.3 A (cooling system), +8.3 V @ 6 A (bias), –48 V to

–60 V@ 75 A

Circuit Breaker Box

The circuit breaker box is located on the rear of the chassis, above the right power supply, as shown in Figure 2.

The circuit breaker box houses two circuit breakers and sets of terminal studs, corresponding positionally to the two power supplies, as shown in Figure 19.

For proper router operation and power load sharing, connect a different external DC power source to each set of terminal studs.

In addition, a grounding cable attaches to separate grounding points located above the circuit breaker box, as shown in Figure 2. For more information, see

“Power, Connection, and Cable Specifications” on page 67.

38 Power System

Hardware Component Overview

Figure 19: Circuit Breaker Box

Fuses

The router uses fuses from the Cooper Bussman brand GMT series for the FPCs,

MCSs, PCGs, and SFMs. The fuses are located in a fuse box on the rear of the midplane. When the fuse for a component blows, the component stops functioning even though it is installed correctly and the power supplies are providing power to the router. For more information, see “Blown Fuse Indicators” on page 211. For fuse replacement instructions, see “Replacing a Fuse” on page 204.

Cooling System

The cooling system includes a fan tray and several impellers that draw room air into the chassis to keep its internal temperature below a maximum acceptable level.

When the temperature is below the maximum, the fans and impellers function at less than full speed. If the MCS detects that the temperature of a component has exceeded the acceptable maximum—for example, because an impeller is removed—it automatically increases the speed of the remaining impellers and fans to reduce the temperature. The fans and impellers can function at the higher speed indefinitely.

For more information about the cooling system, see the following sections:

Cooling System Components on page 40

Airflow through the Chassis on page 40

Cooling System 39

M160 Internet Router Hardware Guide

Cooling System Components

The cooling system has the following components. All are hot-removable and hot-insertable, as described in Field-Replaceable Units (FRUs) on page 4.

Air intake vent, air filter, and intake cover—Provide an opening for room air to enter the router. They are located at the bottom of the chassis front, below the cable management system, as shown in Figure 1. The air filter is removable and covers the air intake vent, preventing dust and other particles from entering the cooling system. For maintenance and replacement instructions, see “Maintaining the Air Filter” on page 128. The nonremovable air intake cover is located behind the air filter and provides EMC shielding.

CAUTION: Do not remove the air filter for more than a few minutes while the router is operating. The fans and impellers are powerful enough to draw in foreign material, such as bits of wire, through the unfiltered air intake, which could damage router components.

Front cooling subsystem—Cools the FPCs, PICs, and midplane. It includes a fan tray located behind the cable management system and a large, central impeller behind the craft interface. For replacement instructions, see “Replacing the Fan

Tray” on page 148 and “Replacing the Front Impeller Assembly” on page 150.

Rear cooling subsystem—Cools the SFMs, host module, PCGs, and power supplies. It includes one impeller located at the upper right of the chassis rear and another at the lower left, as shown in Figure 2. The upper and lower impellers are not interchangeable. For replacement instructions, see

“Replacing the Rear Lower Impeller Assembly” on page 154 and “Replacing the Rear Upper Impeller Assembly” on page 156.

Airflow through the Chassis

Figure 20 shows airflow through the chassis and the location of the impellers and fan tray.

40 Cooling System

Hardware Component Overview

Figure 20: Airflow through the Chassis

Front view

Impeller

Side view

Impeller

Top view

Card cage

Front Rear Rear

Impeller

(upper rear)

Impeller

(upper front)

Fan tray

Air intake cover

Front

Cable Management System

The cable management system (see Figure 21) consists of a row of nine semicircular plastic bobbins mounted on the front of the router 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.

Figure 21: Cable Management System

Cable management system

Cable Management System 41

M160 Internet Router Hardware Guide

42 Cable Management System

Chapter 3 JUNOS Internet Software Overview

The JUNOS Internet software is especially designed for the large production networks typically supported by Internet Service Providers (ISPs). It incorporates

Internet Protocol (IP) routing software and software for management of interfaces, networks, and the router chassis.

The JUNOS Internet software runs on the Routing Engine. The software consists of processes that support Internet routing protocols, control the router’s interfaces and the router chassis itself, and provide an interface for system management.

The processes run on top of a kernel that coordinates the communication among processes and has a direct link to the Packet Forwarding Engine software.

Use the JUNOS Internet software to configure the routing protocols that run on the router and the properties of router interfaces. After you have activated a software configuration, use the JUNOS Internet software to monitor the protocol traffic passing through the router and to troubleshoot protocol and network connectivity problems.

For additional information about the JUNOS Internet software, including its security features and a list of the industry standards it supports, see the JUNOS System Basics

Configuration Guide . For complete information about configuring the software, including examples, see the JUNOS Internet software configuration guides.

This chapter discusses the following topics:

Routing Engine Software Components on page 43

Tools for Accessing and Configuring the Software on page 50

Tools for Monitoring the Software on page 50

Software Upgrades on page 50

Routing Engine Software Components

The Routing Engine software consists of several software processes that control router functions and a kernel that coordinates communication among the processes, as described in the following sections:

Routing Protocol Process on page 44

Routing Engine Software Components 43

M160 Internet Router Hardware Guide

VPNs on page 48

Interface Process on page 49

Chassis Process on page 49

SNMP and MIB II Processes on page 49

Management Process on page 49

Routing Engine Kernel on page 49

Routing Protocol Process

The JUNOS software routing protocol process controls the routing protocols that run on the router. The routing protocol process starts all configured routing protocols and handles all routing messages. It consolidates the routing information learned from all routing protocols into common routing tables. From this routing information, the routing protocol process determines the active routes to network destinations and installs these routes into the Routing Engine’s forwarding table.

Finally, the routing protocol process implements the routing policies you specify, which determine how routing information is transferred between the routing protocols and the routing table.

This section discusses the following topics:

IPv4 Routing Protocols on page 44

IPv6 Routing Protocols on page 46

Routing and Forwarding Tables on page 47

Routing Policy on page 47

For complete information about routing concepts, see the JUNOS

Internet software configuration guides.

IPv4 Routing Protocols

The JUNOS Internet software implements full IP routing functionality, providing support for IP version 4 (IPv4). The routing protocols are fully interoperable with existing IP routing protocols and provide the scale and control necessary for the Internet core. The software provides support for the following routing and traffic engineering protocols:

Unicast routing protocols

BGP—Border Gateway Protocol, version 4, is an Exterior Gateway Protocol

(EGP) that guarantees loop-free exchange of routing information between routing domains (also called autonomous systems). BGP, in conjunction

44 Routing Engine Software Components

JUNOS Internet Software Overview with JUNOS routing policy, provides a system of administrative checks and balances that can be used to implement peering and transit agreements.

ICMP—Internet Control Message Protocol router discovery is a method that hosts can use to discover the addresses of operational routers on a subnet.

IS-IS—Intermediate System-to-Intermediate System is a link-state interior gateway protocol (IGP) for IP networks that uses the shortest-path-first algorithm (SPF algorithm, also called the Dijkstra algorithm) to determine routes.

OSPF—Open Shortest Path First, version 2, is an IGP developed for

IP networks by the Internet Engineering Task Force (IETF). OSPF is a link-state protocol that makes routing decisions based on the SPF algorithm.

RIP—Routing Information Protocol, version 2, is an IGP for IP networks based on the Bellman-Ford algorithm. RIP is a distance-vector protocol.

RIP dynamically routes packets between a subscriber and a service provider without the subscriber having to configure BGP or to participate in the service provider’s IGP discovery process.

Multicast routing protocols

DVMRP—Distance Vector Multicast Routing Protocol is a dense-mode

(flood-and-prune) multicast routing protocol.

IGMP—Internet Group Management Protocol, versions 1 and 2, is used to manage membership in multicast groups.

MSDP—Multicast Source Discovery Protocol enables multiple PIM sparse mode domains to be joined. A rendezvous point (RP) in a PIM sparse mode domain has a peering relationship with an RP in another domain, thereby discovering multicast sources from other domains.

PIM sparse mode and dense mode—Protocol-Independent Multicast is a multicast routing protocol used to route traffic to multicast groups that might span wide-area and interdomain internetworks. In PIM sparse mode, routers explicitly join and leave multicast groups. PIM dense mode is a flood-and-prune protocol.

SAP/SDP—Session Announcement Protocol and Session Description

Protocol handle conference session announcements.

MPLS application protocols

LDP—Label Distribution Protocol provides a mechanism for distributing labels in nontraffic-engineered applications. LDP allows routers to establish label-switched paths (LSPs) through a network by mapping network-layer routing information directly to data-link layer switched

Routing Engine Software Components 45

M160 Internet Router Hardware Guide paths. LSPs created by LDP can also traverse LSPs created by Resource

Reservation Protocol (RSVP).

MPLS—Multiprotocol Label Switching enables you to configure LSPs through a network either manually or dynamically. You can control how traffic traverses the network by directing it through particular paths, rather than relying on an IGP’s least-cost algorithm to choose a path.

RSVP—Resource Reservation Protocol, version 1, provides a mechanism for engineering network traffic patterns that is independent of the shortest path determined by a routing protocol. RSVP itself is not a routing protocol, but is designed to operate with current and future unicast and multicast routing protocols. JUNOS RSVP software supports dynamic signaling for MPLS LSPs.

IPv6 Routing Protocols

The JUNOS Internet software implements full IP routing functionality, providing support for IP version 6 (IPv6). The routing protocols are fully interoperable with existing IP routing protocols and provide the scale and control necessary for the Internet core. The software provides support for the following unicast routing protocols:

BGP—Border Gateway Protocol, version 4, is an EGP that guarantees loop-free exchange of routing information between routing domains (also called autonomous systems). BGP, in conjunction with JUNOS routing policy, provides a system of administrative checks and balances that can be used to implement peering and transit agreements.

ICMP—Internet Control Message Protocol router discovery is a method that hosts can use to discover the addresses of operational routers on a subnet.

OSPF—Open Shortest Path First, version 3 (OSPFv3), supports version 6 of the Internet Protocol (IPv6). The fundamental mechanisms of OSPF such as flooding, Designated Router (DR) election, area based topologies and the

Shortest Path First (SPF) calculations remain unchanged. Some differences exist either due to changes in protocol semantics between IPv4 and IPv6, or to handle the increased address size of IPv6.

RIP—Routing Information Protocol, version 2, is an IGP for IP networks based on the Bellman-Ford algorithm. RIP is a distance-vector protocol. RIP dynamically routes packets between a subscriber and a service provider without the subscriber having to configure BGP or to participate in the service provider’s IGP discovery process.

46 Routing Engine Software Components

JUNOS Internet Software Overview

Routing and Forwarding Tables

The primary function of the JUNOS routing protocol process is maintaining routing tables and using the information in them to determine active routes to network destinations. It copies information about the active routes into the Routing Engine’s forwarding table, which the JUNOS kernel copies to the Packet Forwarding Engine.

By default, the routing protocol process maintains the following routing tables and uses the information in each table to determine active routes to network destinations:

Unicast routing table—Stores routing information for all unicast protocols running on the router, including BGP, IS-IS, OSPF, and RIP. You can also configure additional routes, such as static routes, for inclusion in the routing table. The unicast routing protocols use the routes in this table when advertising routing information to their neighbors.

In the unicast routing table, the routing protocol process designates routes with the lowest preference values as active. By default, a route’s preference value is simply a function of how the routing protocol process learned about the route.

You can modify the default preference value by setting routing policies and configuring other software parameters. See “Routing Policy” on page 47.

Multicast routing table (cache)—Stores routing information for all multicast protocols running on the router, including DVMRP and PIM. You can configure additional routes for inclusion in the routing table.

In the multicast routing table, the routing protocol process uses traffic flow and other parameters specified by the multicast routing protocol algorithms to select active routes.

MPLS routing table—Stores MPLS label information.

For unicast routes, the routing protocol process determines active routes by choosing the most preferred route, which is the route with the lowest preference value. By default, the route’s preference value is simply a function of how the routing protocol process learned about the route. You can modify the default preference value using routing policy and with software configuration parameters.

For multicast traffic, the routing protocol process determines active routes based on traffic flow and other parameters specified by the multicast routing protocol algorithms. The routing protocol process then installs one or more active routes to each network destination into the Routing Engine’s forwarding table.

You can configure additional routing tables to meet your requirements, as described in the JUNOS Routing Protocols Configuration Guide .

Routing Policy

By default, all routing protocols place their routes into the routing table.

When advertising routes, the routing protocols, by default, advertise only a limited set of routes from the routing table. Specifically, each routing protocol exports only the active routes that were learned by that protocol.

Routing Engine Software Components 47

M160 Internet Router Hardware Guide

VPNs

In addition, IGPs (IS-IS, OSPF, and RIP) export the direct (interface) routes for the interfaces on which the protocol is explicitly configured.

For each routing table, you can affect the routes that a protocol places into the table and the routes from the table that the protocol advertises by defining one or more routing policies and then applying them to the specific routing protocol.

Routing policies applied when the routing protocol places routes into the routing table are called import policies because the routes are being imported into the routing table. Policies applied when the routing protocol is advertising routes that are in the routing table are called export policies because the routes are being exported from the routing table. In other words, the terms import and export are used with respect to the routing table.

Routing policy enables you to control (filter) which routes are imported into the routing table and which routes are exported from the routing table. Routing policy also allows you to set the information associated with a route as it is being imported into or exported from the routing table. Routing policies applied to imported routes control the routes used to determine active routes, whereas policies applied to exported routes control which routes a protocol advertises to its neighbors.

You implement routing policy by defining policies. A policy specifies the conditions to use to match a route and the action to perform on the route when a match occurs. For example, when a routing table imports routing information from a routing protocol, a routing policy might modify the route’s preference, mark the route with a color to identify it for later manipulation, or prevent the route from even being installed in a routing table. When a routing table exports routes to a routing protocol, a policy might assign metric values, modify the BGP community information, tag the route with additional information, or prevent the route from being exported altogether. You also can define policies for redistributing the routes learned from one protocol into another protocol.

The JUNOS software supports several types of VPNs:

Layer 2 VPNs—A Layer 2 VPN links a set of sites sharing common routing information, and whose connectivity is controlled by a collection of policies. A

Layer 2 VPN is not aware of routes within a customer’s network. It simply provides private links between a customer’s sites over the service provider’s existing public Internet backbone.

Layer 3 VPNs—A Layer 3 VPN links a set of sites that share common routing information, and whose connectivity is controlled by a collection of policies.

A Layer 3 VPN is aware of routes within a customer’s network, requiring more configuration on the part of the service provider than a Layer 2 VPN.

The sites that make up a Layer 3 VPN are connected over a service provider’s existing public Internet backbone.

Interprovider VPNs—An interprovider VPN supplies connectivity between two

VPNs in separate autonomous systems (ASs). This functionality could be used

48 Routing Engine Software Components

JUNOS Internet Software Overview by a VPN customer with connections to several various ISPs, or different connections to the same ISP in various geographic regions.

Carrier-of-Carrier VPNs—Carrier-of-carrier VPNs allow a VPN service provider to supply VPN service to a customer who is also a service provider. The latter service provider supplies Internet or VPN service to an end customer.

Interface Process

The JUNOS interface process manages the physical interface devices and logical interfaces on the router. It implements the JUNOS command-line interface

(CLI) commands and configuration statements that you use to specify interface properties such as location (FPC location in the FPC card cage and PIC location on an FPC), the interface type (such as SONET/SDH or ATM), encapsulation, and interface-specific properties. You can configure both interfaces that are currently active and interfaces that might be installed later.

The JUNOS interface process communicates with the interface process in the

Packet Forwarding Engine through the JUNOS kernel, enabling the JUNOS Internet software to track the status and condition of router interfaces.

Chassis Process

The JUNOS chassis process allows you to configure and control the properties of the router, including conditions that trigger alarms and clock sources. The chassis process communicates directly with a chassis process in the JUNOS kernel.

SNMP and MIB II Processes

The JUNOS Internet software supports the Simple Network Management

Protocol (SNMP), versions 1, 2, and 3, which provides a mechanism for monitoring the state of the router. This software is controlled by the JUNOS

SNMP and Management Information Base (MIB) II processes, which consist of an SNMP master agent and a MIB II agent.

Management Process

The management process starts all the other JUNOS software processes and the

CLI when the router boots. It monitors the running JUNOS processes and makes all reasonable attempts to restart any process that terminates.

Routing Engine Kernel

The Routing Engine kernel provides the underlying infrastructure for all JUNOS software processes. It also provides the link between the routing tables maintained by the routing protocol process and the forwarding table maintained by the Routing

Engine. Additionally, it coordinates communication with the Packet Forwarding

Engine, which primarily involves synchronizing the Packet Forwarding Engine’s forwarding table with the master forwarding table maintained by the Routing Engine.

Routing Engine Software Components 49

M160 Internet Router Hardware Guide

Tools for Accessing and Configuring the Software

The JUNOS CLI is the primary tool for accessing and controlling the JUNOS Internet software. You use it when accessing the router through the console or a connection to an out-of-band management network. The CLI includes commands for configuring router hardware, the JUNOS Internet software, and network connectivity.

The JUNOS CLI is a straightforward command interface. You type commands on a single line and enter the commands by pressing the Enter key. The CLI provides command help and command completion, as well as Emacs-style keyboard sequences for moving around on a command line and scrolling through a buffer that contains recently executed commands. For more information about the CLI, see the JUNOS System Basics Configuration Guide .

Tools for Monitoring the Software

In addition to commands for configuring router hardware and software, the CLI includes commands for monitoring and troubleshooting hardware, software, routing protocols, and network connectivity. CLI commands display information from routing tables, information specific to routing protocols, and information about network connectivity derived from the ping and traceroute utilities.

You can also use the JUNOS Internet software implementation of SNMP to monitor routers. The SNMP software consists of an SNMP master agent and a MIB II agent.

It provides full support for MIB II SNMP version 1 traps and version 2 notifications,

SNMP version 1 Get and GetNext requests, and version 2 GetBulk requests. For more information about SNMP, see the JUNOS Network Management Configuration Guide .

The software also supports tracing and logging operations, which you can use to track normal router operations, error conditions, and the packets that the router generates or forwards. Logging operations use a syslog-like mechanism to record systemwide, high-level events such as interfaces going up or down and user logins on the router. Tracing operations record more detailed information about the operation of routing protocols, such as the various types of routing protocol packets sent and received, and routing policy actions.

Software Upgrades

The router is delivered with the JUNOS Internet software preinstalled. To upgrade the software, you use CLI commands to copy a set of software images over the network to memory storage on the Routing Engine. The JUNOS Internet software set consists of several images provided in individual packages or as a bundle. You normally upgrade all packages simultaneously. For information about installing and upgrading JUNOS software, see the JUNOS System Basics Configuration Guide .

50 Software Upgrades

Chapter 4 System Architecture Overview

The router architecture consists of two major components:

Packet Forwarding Engine—Performs Layer 2 and Layer 3 packet switching, route lookups, and packet forwarding.

Routing Engine—Provides Layer 3 routing services and network management.

The Packet Forwarding Engine and the Routing Engine perform independently but communicate constantly through a 100-Mbps internal link. This arrangement provides streamlined forwarding and routing control and the ability to run

Internet-scale networks at high speeds. Figure 22 illustrates the relationship between the Packet Forwarding Engine and the Routing Engine.

Figure 22: System Architecture

Packets in

Routing Engine

100-Mbps link

Packet Forwarding

Engine

Packets out

For a discussion of the architectural components, see the following sections:

Packet Forwarding Engine Architecture on page 51

Routing Engine Architecture on page 53

Packet Forwarding Engine Architecture

The Packet Forwarding Engine performs Layer 2 and Layer 3 packet switching.

It can forward up to 160 for all packet sizes. The aggregate throughput for the router is 160 gigabits per second (Gbps) simplex or 80 Gbps full duplex. The

Packet Forwarding Engine is implemented in application-specific integrated circuits

(ASICs). It uses a centralized route lookup engine and shared memory.

Packet Forwarding Engine Architecture 51

M160 Internet Router Hardware Guide

The Packet Forwarding Engine architecture includes the following components:

Midplane—Transports packets, notifications, and other signals between the

FPCs and the Packet Forwarding Engine (as well as other system components).

Physical Interface Card (PIC)—Physically connects the router to fiber-optic or digital network media. A controller ASIC in each PIC performs control functions specific to the PIC media type.

Flexible PIC Concentrator (FPC)—Houses PICs and provides shared memory for processing incoming and outgoing packets. Each FPC hosts four I/O

Manager ASICs, which divide incoming data packets into memory blocks (cells) before passing them to the SFMs, and reassembles cells into data packets when the packets are ready for transmission. The FPC also hosts two Packet Director

ASICs—one distributes incoming packets among the I/O Manager ASICs, and the other distributes outgoing packets to the appropriate PICs on the FPC.

Switching and Forwarding Module (SFM)—Hosts an Internet Processor II ASIC, which makes forwarding decisions, and two Distributed Buffer Manager ASICs: one distributes data cells to the shared memory buffers on the FPCs and the other notifies the FPCs of forwarding decisions for outgoing packets.

Data Flow through the Packet Forwarding Engine

Use of ASICs promotes efficient movement of data packets through the system. Packets flow through the Packet Forwarding Engine in the following sequence (see Figure 23):

Packets arrive at an incoming PIC interface.

The PIC passes the packets to the FPC, where the Packet Director ASIC distributes them among the I/O Manager ASICs.

The I/O Manager ASICs process the packet headers, divide the packets into

64-byte data cells, and pass the cells through the midplane to the SFMs.

The Distributed Buffer Manager ASICs on the SFMs distribute the data cells throughout memory buffers located on and shared by all the FPCs.

For each packet, an Internet Processor II ASIC on an SFM performs a route lookup and decides how to forward the packet.

The Internet Processor II ASIC notifies a Distributed Buffer Manager ASIC of the forwarding decision, and the Distributed Buffer Manager ASIC forwards the notification to the FPC that hosts the appropriate outbound interface.

The I/O Manager ASIC on the FPC reassembles data cells in shared memory into data packets as they are ready for transmission and passes them through the Packet Director ASIC to the outbound PIC.

The outbound PIC transmits the data packets.

52 Packet Forwarding Engine Architecture

System Architecture Overview

Figure 23: Packet Forwarding Engine Components and Data Flow

Midplane

FPC

I/O

Manager

Packet in

Packet out

Controller

PIC

Packet

Director

Distributed

Buffer

Manager

SFM

Internet

Processor II

Routing

Engine

= ASIC

Routing Engine Architecture

The Routing Engine is an Intel-based PCI platform running the JUNOS Internet software, which Juniper Networks has developed and optimized to handle large numbers of network interfaces and routes. The software consists of a set of system processes running in protected memory modules on top of an independent operating system. The JUNOS kernel supports JUNOS system processes, which handle system management processes, routing protocols, and control functions (see Figure 24).

The Routing Engine has a dedicated 100-Mbps internal connection to the Packet Forwarding Engine.

Routing Engine Architecture 53

M160 Internet Router Hardware Guide

Figure 24: Routing Engine Architecture

JUNOS software

System management processes

Routing protocols

Kernel

Intel-based PCI platform

Control functions

System processes

Operating system

Routing Engine Functions

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. These routing and software processes run on top of a kernel that interacts with the

Packet Forwarding Engine. For more information about the processes, see

Routing Engine Software Components on page 43.

The Routing Engine includes the following functions and features:

Processing of routing protocol packets—The Routing Engine handles all packets that concern routing protocols, freeing the Packet Forwarding Engine to handle only packets that represent Internet traffic.

Software modularity—Because each 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 routing protocol is implemented with a complete set of Internet features and provides full flexibility 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 routing tables have been designed to hold all the routes in current networks with ample capacity for expansion. Additionally, the

54 Routing Engine Architecture

System Architecture Overview

JUNOS Internet software can efficiently support large numbers of interfaces and virtual circuits.

Management interface—Different levels of system management tools are provided, including the JUNOS command-line interface (CLI), the JUNOScript application programming interface, the craft interface, and SNMP.

Storage and change management—Configuration files, system images, and microcode 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.

The Routing Engine constructs and maintains one or more routing tables (see

Figure 25). 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 25: Control Packet Handling for Routing and Forwarding Table Updates

Routing protocol process

Routing Engine

Forwarding table updates

Routing protocol packets from network

Packets in

Forwarding table

Packet Forwarding

Engines

Packets out

Routing Engine Architecture 55

M160 Internet Router Hardware Guide

56 Routing Engine Architecture

Part 2 Initial Installation

Preparing for Router Installation on page 59

Unpacking the Router on page 77

Installing the Router Using a Mechanical Lift on page 81

Installing the Router without a Mechanical Lift on page 83

Connecting the Router and Performing Initial Configuration on page 111

Initial Installation 57

58 Initial Installation

Chapter 5 Preparing for Router Installation

This chapter describes how to prepare your site for installation of the M160 Internet router. It discusses the following topics:

Rack Requirements on page 59

Clearance Requirements for Airflow and Hardware Maintenance on page 62

Routing Node Environmental Specifications on page 62

Fire Safety Requirements on page 63

Power Guidelines, Requirements, and Specifications on page 64

Network Cable Specifications and Guidelines on page 70

Routing Engine Interface Cable and Wire Specifications on page 74

Site Preparation Checklist on page 75

Rack Requirements

The router must be installed in a rack. Many types of racks are acceptable, including front-mount racks, 4-post (telco) racks, and center-mount racks. An example of a center-mount rack appears in Figure 26.

The following sections describe rack requirements:

Rack Size and Strength on page 60

Spacing of Mounting Holes on page 61

Connection to Building Structure on page 62

Rack Requirements 59

M160 Internet Router Hardware Guide

Rack Size and Strength

The router is designed for installation in a rack that complies with either of the following standards:

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

A 600-mm 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 the European

Telecommunications Standards Institute ( http://www.etsi.org

The horizontal spacing between the rails in a rack that complies with this standard is usually wider than the router’s front support posts and center-mounting brackets, which measure 19 in. (48.3 cm) from outer edge to outer edge. Use approved wing devices to narrow the opening between the rails as required.

The rack rails must be spaced widely enough to accommodate the router chassis’s external dimensions: 35 in. (89 cm) high, 29 in. (73.6 cm) deep, and 17.5 in.

(44.5 cm) wide. The outer edges of the front support posts 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 Clearance Requirements for Airflow and Hardware Maintenance on page 62.

NOTE: The router might not fit into an 800-mm-deep cabinet, even if you adjust the front-to-back position of the front mounting rails inside the cabinet.

If you mount the router in a cabinet, be sure that ventilation is sufficient to prevent overheating.

In general, a center-mount rack is preferable to a front-mount rack because the more even distribution of weight in the center-mount rack provides greater stability. If a front-mount rack is used, we recommend supporting the back of the router with a shelf or other structure.

The chassis height of 35 in. (89 cm) is approximately 20 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 Industry

Association. You can stack eight M160 routers in a rack that has at least

40 U (70 in. or 1.78 m) of usable vertical space.

The rack must be strong enough to support the weight of the fully configured router, up to about 370.5 lb (168 kg). If you stack eight routers in one rack, it must be capable of supporting about 740 lb (336 kg).

60 Rack Requirements

Figure 26: Typical Center-Mount Rack

19 in. (48.3 cm)

Mounting rails

Preparing for Router Installation

7 ft

(2.13 m)

Floor bolts

Spacing of Mounting Holes

Table 14 specifies the spacing between mounting holes in the chassis’s front support posts and center-mounting brackets. The mounting holes in a front-mount rack’s rails must align with the holes in the front support posts, and the mounting holes in a center-mount rack’s rails must align with the holes in the center-mounting brackets.

Table 14: Spacing of Holes on Front Support Post and Center-Mounting Bracket

Router Mounting Rail

Front support post

Center-mounting bracket

Hole Spacing

4 U (7 in. or 17.78 cm)

3 U (5.25 in. or 13.33 cm)

Rack Requirements 61

M160 Internet Router Hardware Guide

Connection to Building Structure

Always secure the rack to the structure of the building. If your geographical area is subject to earthquakes, bolt the rack to the floor. For maximum stability, also secure the rack to ceiling brackets. For more information, see

“Rack-Mounting Requirements and Warnings” on page 240.

Clearance Requirements for Airflow and Hardware Maintenance

When planning the installation site, you need to allow sufficient clearance around the rack (see Figure 27):

For the cooling system to function properly, the airflow around the chassis must be unrestricted. Figure 20 depicts the airflow in the router.

For service personnel to remove and install hardware components, there must be adequate space at the front and back of the router. Allow at least 24 in.

(61 cm) both in front of the router and behind it.

Figure 27: Chassis Dimensions and Clearance Requirements

Top down view

24 in. (61 cm) clearance for maintenance

29 in.

(73.6 cm)

24 in. (61 cm) clearance for maintenance

6 in. (15.2 cm) clearance for airflow

Front of chassis

19 in.

(48.3 cm)

19 in.

(48.3 cm)

17.5 in.

(44.5 cm)

Rear of chassis

6 in. (15.2 cm) clearance for airflow

Center rack-mount ears

Routing Node Environmental Specifications

Table 15 specifies the environmental specifications required for normal router operation. In addition, the site should be as dust-free as possible.

Dust can clog air intake vents, reducing cooling system efficiency. Check the vents frequently, cleaning them as necessary. For more information, see

“Maintaining Hardware Components” on page 127.

62 Routing Node Environmental Specifications

Preparing for Router Installation

Table 15: Routing Node Environmental Specifications

Description

Altitude

Relative humidity

Temperature

Value

No performance degradation to 10,000 ft (3048 m)

Normal operation ensured in relative humidity range of 5% to

90%, noncondensing

Normal operation ensured in temperature range of 32°F (0°C) to

104°F (40°C)

Non-operating storage temperature in shipping crate:

–40°F (–40°C) to 158°F (70°C)

Seismic Tested to meet Telcordia Technologies Zone 4 earthquake requirements

Maximum thermal output 9400 BTU/hour

NOTE: Install the router only in restricted areas, such as dedicated equipment rooms and equipment closets, in accordance with Articles 110-16, 110-17, and

110-18 of the National Electrical Code, ANSI/NFPA 70.

For additional safety guidelines and requirements, see “Safety and Regulatory

Compliance Information” on page 221.

Fire Safety Requirements

In the event of a fire emergency involving routers and other network equipment, the safety of people is the primary concern. You should establish procedures for protecting people in the event of a fire emergency, provide safety training, and properly provision fire-control equipment and fire extinguishers.

In addition, you should establish procedures to protect your equipment in the event of a fire emergency. Juniper Networks products should be installed in an environment suitable for electronic equipment. We recommend that fire suppression equipment be available in the event of a fire in the vicinity of the equipment, and that all local fire, safety, and electrical codes and ordinances be observed when installing and operating your equipment.

Fire Suppression

In the event of an electrical hazard or an electrical fire, you should first turn power off to the equipment at the source. Then use a Type C fire extinguisher, which uses noncorrosive fire retardants, to extinguish the fire. For more information about fire extinguishers, see “Fire Suppression Equipment” on page 64.

Fire Safety Requirements 63

M160 Internet Router Hardware Guide

Fire Suppression Equipment

Type C fire extinguishers, which use noncorrosive fire retardants such as carbon dioxide (CO2) and Halotron™, are most effective for suppressing electrical fires.

Type C fire extinguishers displace the oxygen from the point of combustion to eliminate the fire. For extinguishing fire on or around equipment that draws air from the environment for cooling, you should use this type of inert oxygen displacement extinguisher instead of an extinguisher that leave residues on equipment.

Do not use multipurpose Type ABC chemical fire extinguishers (dry chemical fire extinguishers) near Juniper Networks equipment. The primary ingredient in these fire extinguishers is monoammonium phosphate, which is very sticky and difficult to clean. In addition, in minute amounts of moisture, monoammonium phosphate can become highly corrosive and corrodes most metals.

Any equipment in a room in which a chemical fire extinguisher has been discharged is subject to premature failure and unreliable operation. The equipment is considered to be irreparably damaged.

NOTE: To keep warranties effective, do not use a dry chemical fire extinguisher to control a fire at or near a Juniper Networks router. If a dry chemical fire extinguisher is used, the unit is no longer eligible for coverage under a service agreement.

We recommend that you dispose of any irreparably damaged equipment in an environmentally responsible manner.

Power Guidelines, Requirements, and Specifications

For site wiring and power system guidelines, requirements, and specifications, see the following sections:

Site Electrical Wiring Guidelines on page 65

Router Power Requirements on page 65

Chassis Grounding on page 67

Power, Connection, and Cable Specifications on page 67

64 Power Guidelines, Requirements, and Specifications

Preparing for Router Installation

Site Electrical Wiring Guidelines

When planning the electrical wiring at your site, consider the factors discussed in the following sections.

Distance Limitations for Signaling

Improperly installed wires can emit radio interference. In addition, the potential for damage from lightning strikes increases if wires exceed recommended distances, or if wires pass between buildings. The electromagnetic pulse (EMP) caused by lightning can damage unshielded conductors and destroy electronic devices. If your site has previously experienced such problems, you might want to consult experts in electrical surge suppression and shielding.

Radio Frequency Interference

You can reduce or eliminate the emission of radio frequency interference (RFI) from your site wiring by using twisted-pair cable with a good distribution of grounding conductors. If you must exceed the recommended distances, use a high-quality twisted-pair cable with one ground conductor for each data signal when applicable.

Electromagnetic Compatibility

If your site is susceptible to problems with electromagnetic compatibility

(EMC), particularly from lightning or radio transmitters, you might want to seek expert advice. Strong sources of electromagnetic interference (EMI) can destroy the signal drivers and receivers in the router and conduct power surges over the lines into the equipment, resulting in an electrical hazard.

It is particularly important to provide a properly grounded and shielded environment and to use electrical surge-suppression devices.

CAUTION: To comply with intrabuilding lightning/surge requirements, intrabuilding wiring must be shielded, and the shield for the wiring must be grounded at both ends.

Router Power Requirements

Table 16 lists the power requirements for various hardware components when the router is operating under typical voltage conditions. For PIC power requirements, see the M160 Internet Router PIC Guide .

Power Guidelines, Requirements, and Specifications 65

M160 Internet Router Hardware Guide

Table 16: Component Power Requirements

Component

Base system (cooling system, power supplies, and craft interface)

Host module (Routing Engine and MCS)

FPC

PCG

SFM

Power Requirement (Amps)

7-10 A/48 V

1.3 A/48 V

2.4 A/48 V

0.2 A/48 V

1.3 A/48 V

You can use the information in Table 16 and the M160 Internet Router PIC

Guide to calculate power consumption for various hardware configurations, input current from a different source voltage, and thermal output, as shown in the following examples. (For an added safety margin, the examples use a generalized value for PICs of 0.625 A/48 V each.)

Power consumption for minimum configuration:

Base system + 1 FPC + 1 SFM + 1 host module + 2 PCGs + 4 PICs =

7 A + 2.4 A + 1.3 A + 1.3 A + 2(0.2 A) + 4(0.625 A) =

7 A + 2.4 A + 1.3 A + 1.3 A + 0.4 A + 2.5 A = 14.9 A @ 48 V = 715 W DC

Power consumption for maximum configuration:

Base system + 8 FPCs + 4 SFMs + 2 host modules + 2 PCGs + 32 PICs =

10 A + 8(2.4 A) + 4(1.3 A) + 2(1.3 A) + 2(0.2 A) + 32(0.625 A) =

10 A + 19.2 A + 5.2 A + 2.6 A + 0.4 A + 20 A = 57.4 A @ 48 V = 2755 W DC

Input current from a DC source other than 48 V (based on maximum configuration):

(54 VDC input) x (input current X) = (48 VDC input) x (input current Y)

54 x X = 48 x 57.4 A

X = 48 x 57.4 A/54 = 51.0 A

System thermal output for maximally configured router:

105% of Watts DC/0.293 = BTU/hr

1.05 x 2755/0.293 = 9873 BTU/hr

NOTE: If you plan to operate a maximally configured router, we recommend that you provision at least 70 A @ 48 VDC and use a facility circuit breaker rated for

70 A minimum. Doing so enables you to operate the router in any configuration without upgrading the power infrastructure, and allows the router to function at full capacity using one power supply.

If you plan to operate the router at less than the maximum configuration and do not provision a 70 A circuit breaker, we recommend that you provision a circuit breaker rated for at least 125% of the continuous current that the system draws at 48 V.

66 Power Guidelines, Requirements, and Specifications

Preparing for Router Installation

Chassis Grounding

To meet safety and electromagnetic interference (EMI) requirements and to ensure proper operation, the router must be adequately grounded before power is connected. A pair of threaded inserts (PEM nuts) are provided on the right rear of the chassis for connecting the router to earth ground.

CAUTION: Before router installation begins, a licensed electrician must attach a cable lug to the grounding and power cables that you supply. A cable with an incorrectly attached lug can damage the router (for example, by causing a short circuit).

To ground the router, connect a grounding cable to earth ground and then attach it to the chassis grounding points. The grounding points are spaced at

0.625-in. (15.86-mm) centers. The accessory box shipped with the router includes the cable lug that attaches to the grounding cable (see Figure 28) and the UNC 1/4–20 screws (American) used to secure the grounding cable to the grounding points. (The cable lug shown in Figure 28 is also used for the DC power cables.) The grounding cable must be able to handle up to 82 A.

Figure 28: Power and Grounding Cable Lug

2.25

End view

0.55

0.28

2 holes

0.08

0.25

0.63

0.37

Crimp area

All measurements in inches

The grounding cable must be 8-AWG (8.4 m2) wire, minimum, or as permitted by the local code.

Power, Connection, and Cable Specifications

To supply power to the router, connect power cables to a separate, dedicated power source for each power supply and attach the cables to the terminal studs on the circuit breaker box. Most sites distribute power through a main conduit that leads to frame-mounted power distribution panels, one of which might be located at the top of the rack that houses the router. A pair of cables (one input and one return) connects each set of terminal studs to the power distribution panel.

CAUTION: There is no standard color coding for DC power cables. The color coding used by the external DC power source at your site determines the color coding for the leads on the power cables that attach to the terminal studs on the circuit

Power Guidelines, Requirements, and Specifications 67

M160 Internet Router Hardware Guide breaker box. You must ensure that power connections maintain the proper polarity.

The power source cables might be labeled (+) and (–) to indicate their polarity.

Figure 29 shows a typical source cabling arrangement.

Figure 29: Typical Source Cabling to the Router

Chassis grounding points

Central office ground

Central office primary & secondary

DC power distribution

Rectifiers

Ground window

Central office ground

Batteries

Battery plant

Plant controls

WARNING: Power plant ground and chassis ground must be connected to the same building ground.

Table 17 summarizes the specifications for the grounding and power cables, which you supply. The accessory box shipped with the router includes the cable lugs that attach to the terminal studs of the circuit breaker box (see Figure 28). (The cable lug shown in Figure 28 is also used for the grounding the chassis.)

68 Power Guidelines, Requirements, and Specifications

Preparing for Router Installation

Table 17: DC Power and Grounding Cable Specifications

Cable Type

Power

Grounding

Quantity and Specification

Eight 4-AWG (16 mm2) wires, minimum, or as permitted by the local code

One 8-AWG (8.4 mm2) wire, minimum, or as permitted by the local code

Maximum

Equal Length

None

WARNING: For field-wiring connections, use copper conductors only.

For other electrical safety information, see “Electrical Safety Guidelines and

Warnings” on page 227.

CAUTION: Power cords and cables must not block access to router components or drape where people could trip on them.

Figure 30 shows how to attach the power cables. The power cables attach to the 1/4–20 UNC terminal studs located on the circuit breaker box— the input set of studs is labeled –48V and the return set is labeled RTN(+) .

The nuts and locking washers used to secure the power cable lugs on the terminal studs are preinstalled on the studs.

The tool for loosening or tightening the nuts on the terminal studs is a

7/16-in. hexagonal-head external drive socket wrench, or nut driver, with a minimum of 30 lb-in. (3.5 Nm) tightening torque.

CAUTION: Do not substitute a metric nut driver or wrench. A tool that does not fit the nuts exactly can damage them. If a 7/16-in. tool is not available, use pliers or an adjustable wrench.

Power Guidelines, Requirements, and Specifications 69

M160 Internet Router Hardware Guide

Figure 30: Power and Grounding Cable Connections

Grounding points

To ground

Nut

Flat washer

Nut

Flat washer

Cable lug

Terminal studs

For information about the DC power supply, including electrical specifications and a description of components, see “Power Supply” on page 36. For instructions on connecting the DC power and grounding cables during initial installation, see

“Connecting Power to the Router” on page 117. For instructions on replacing a

DC power cable, see “Disconnecting and Connecting Power” on page 200.

Network Cable Specifications and Guidelines

The various PICs supported on the router accept different kinds of network cable, including multimode and single-mode fiber-optic cable. For more information, see the following sections:

Fiber Optic and Network Cable Specifications on page 71

Signal Loss in Multimode and Single-Mode Fiber-Optic Cable on page 71

Attenuation and Dispersion in Fiber-Optic Cable on page 71

Calculating Power Budget for Fiber-Optic Cable on page 72

Calculating Power Margin for Fiber-Optic Cable on page 73

Attenuating to Prevent Saturation at SONET/SDH PICs on page 74

70 Network Cable Specifications and Guidelines

Preparing for Router Installation

Fiber Optic and Network Cable Specifications

The router supports PICs that use various kinds of network cable, including multimode and single-mode fiber-optic cable. For information about the type of cable used by each PIC, see the M160 Internet Router PIC Guide .

Signal Loss in Multimode and Single-Mode Fiber-Optic Cable

Multimode fiber is large enough in diameter to allow rays of light to reflect internally

(bounce off the walls of the fiber). Interfaces with multimode optics typically use LEDs as light sources. LEDs are not coherent sources, however. They spray varying wavelengths of light into the multimode fiber, which reflects the light at different angles. Light rays travel in jagged lines through a multimode fiber, causing signal dispersion. When light traveling in the fiber core radiates into the fiber cladding, higher-order mode loss (HOL) results. Together these factors limit the transmission distance of multimode fiber compared to single-mode fiber.

Single-mode fiber is so small in diameter that rays of light can reflect internally through one layer only. Interfaces with single-mode optics use lasers as light sources. Lasers generate a single wavelength of light, which travels in a straight line through the single-mode fiber. Compared with multimode fiber, single-mode fiber has higher bandwidth and can carry signals for longer distances. It is consequently more expensive.

For information about the maximum transmission distance and supported wavelength range for the types of single-mode and multimode fiber-optic cable used by PICs on the M160 router, see the M160 Internet Router PIC Guide .

Exceeding the maximum transmission distances can result in significant signal loss, which causes unreliable transmission.

The router uses optical lasers for SONET/SDH PIC single-mode interfaces.

These optics comply with IR-1 of Bellcore GR-253-CORE Issue 2,

December 1995 and ANSI TI.105.06.

Attenuation and Dispersion in Fiber-Optic Cable

Correct functioning of an optical data link depends on modulated light reaching the receiver with enough power to be demodulated correctly.

Attenuation is the reduction in power of the light signal as it is transmitted. Attenuation is caused by passive media components, such as cables, cable splices, and connectors.

While attenuation is significantly lower for optical fiber than for other media, it still occurs in both multimode and single-mode transmission. An efficient optical data link must have enough light available to overcome attenuation.

Network Cable Specifications and Guidelines 71

M160 Internet Router Hardware Guide

Dispersion is the spreading of the signal in time. The following two types of dispersion can affect an optical data link:

Chromatic dispersion—The spreading of the signal in time resulting from the different speeds of light rays.

Modal dispersion—The spreading of the signal in time resulting from the different propagation modes in the fiber.

For multimode transmission, modal dispersion, rather than chromatic dispersion or attenuation, usually limits the maximum bit rate and link length.

For single-mode transmission, modal dispersion is not a factor. However, at higher bit rates and over longer distances, chromatic dispersion rather than modal dispersion limits maximum link length.

An efficient optical data link must have enough light to exceed the minimum power that the receiver requires to operate within its specifications. In addition, the total dispersion must be less than the limits specified for the type of link in

Telcordia Technologies document GR-253-CORE (Section 4.3) and International

Telecommunications Union (ITU) document G.957.

When chromatic dispersion is at the maximum allowed, its effect can be considered as a power penalty in the power budget. The optical power budget must allow for the sum of component attenuation, power penalties (including those from dispersion), and a safety margin for unexpected losses. For more information about power budget, see “Calculating Power Budget for Fiber-Optic Cable” on page 72.

Calculating Power Budget for Fiber-Optic Cable

To ensure that fiber-optic connections have sufficient power for correct operation, you need to calculate the link’s power budget, which is the maximum amount of power it can transmit. When you calculate the power budget, you use a worst-case analysis to provide a margin of error, even though all the parts of an actual system do not operate at the worst-case levels. To calculate the worst-case estimate of power budget ( PB ), you assume minimum transmitter power ( PT ) and minimum receiver sensitivity ( PR ):

PB = PT – PR

The following hypothetical power budget equation uses values measured in decibels (dB) and decibels referred to one milliwatt (dBm):

PB = PT – PR

PB = –15 dBm – (–28 dBm)

PB = 13 dB

72 Network Cable Specifications and Guidelines

Preparing for Router Installation

Calculating Power Margin for Fiber-Optic Cable

After calculating a link’s power budget (using the equation described in

“Calculating Power Budget for Fiber-Optic Cable” on page 72), you can calculate the power margin ( PM ), which represents the amount of power available after subtracting attenuation or link loss ( LL ) from the power budget

( PB ). A worst-case estimate of PM assumes maximum LL :

PM = PB – LL

A PM greater than zero indicates that the power budget is sufficient to operate the receiver.

Factors that can cause link loss include higher-order mode losses, modal and chromatic dispersion, connectors, splices, and fiber attenuation. Table 18 lists an estimated amount of loss for the factors used in the following sample calculations. For information about the actual amount of signal loss caused by equipment and other factors, refer to vendor documentation.

Table 18: Estimated Values for Factors Causing Link Loss

Link-Loss Factor

Higher-order mode losses

Modal and chromatic dispersion

Connector

Splice

Fiber attenuation

Estimated Link-Loss Value

Single-mode—None

Multimode—0.5 dB

Single-mode—None

Multimode—None, if product of bandwidth and distance is less than 500 MHz–km

0.5 dB

Single-mode—0.5 dB/km

Multimode—1 dB/km

The following example uses the estimated values in Table 18 to calculate link loss

( LL ) for a 2 km-long multimode link with a power budget ( PB ) of 13 dB:

Fiber attenuation for 2 km @ 1.0 dB/km= 2 dB

Loss for five connectors @ 0.5 dB per connector = 5(0.5 dB) = 2.5 dB

Loss for two splices @ 0.5 dB per splice =2(0.5 dB) = 1 dB

Higher-order loss = 0.5 dB

Clock recovery module = 1 dB

The power margin ( PM ) is calculated as follows:

Network Cable Specifications and Guidelines 73

M160 Internet Router Hardware Guide

PM = PB – LL

PM = 13 dB – 2 km (1.0 dB/km) – 5 (0.5 dB) – 2 (0.5 dB) – 0.5 dB [HOL] – 1 dB [CRM]

PM = 13 dB – 2 dB – 2.5 dB – 1 dB – 0.5 dB – 1 dB

PM = 6 dB

The following sample calculation for an 8 km-long single-mode link with a power budget ( PB ) of 13 dB uses the estimated values from Table 18 to calculate link loss ( LL ) as the sum of fiber attenuation (8 km @ 0.5 dB/km, or 4 dB) and loss for seven connectors (0.5 dB per connector, or 3.5 dB).

The power margin ( PM ) is calculated as follows:

PM = PB – LL

PM = 13 dB – 8 km (0.5 dB/km) – 7 (0.5 dB)

PM = 13 dB – 4 dB – 3.5 dB

PM = 5.5 dB

In both examples, the calculated power margin is greater than zero, indicating that the link has sufficient power for transmission and does not exceed the maximum receiver input power.

Attenuating to Prevent Saturation at SONET/SDH PICs

SONET/SDH interfaces in the different reach classes—short reach (SR), intermediate reach (IR), and long reach (LR)—generate different output power levels and tolerate different input power levels. Interfaces that have a longer reach can transmit enough power to saturate the receivers on PICs that have a shorter reach.

Specifically, LR interfaces can saturate IR PICs, and both IR and LR interfaces can saturate SR PICs. Interfaces in the same reach class can also saturate one another.

To prevent saturation, you might need to attenuate power at the PIC receiver, particularly if you know that it has a shorter reach than the interface that is sending the signal. Determine the amount of attenuation needed by measuring the power level at each receiver. Attenuate the power to bring it within the allowable range; for short lengths of fiber, with fiber and connector loss close to zero, an attenuator of 5 to 10 dB should be sufficient.

For specifications of minimum and maximum input level (receiver sensitivity and receiver saturation) and minimum and maximum output level (average launch power) for the SONET/SDH PICs supported on the

M160 router, see the M160 Internet Router PIC Guide .

Routing Engine Interface Cable and Wire Specifications

For management and service operations, you connect the Routing Engine to an external console or management network through ports on the Connector

74 Routing Engine Interface Cable and Wire Specifications

Preparing for Router Installation

Interface Panel (CIP). You can also connect the router to external alarm-reporting devices through the alarm relay contacts on the CIP. (For more information, see Connector Interface Panel (CIP) on page 32.)

Table 19 lists the specifications for the cables that connect to management ports and the wires that connect to the alarm relay contacts.

Table 19: Cable and Wire Specifications for Routing Engine Management and Alarm Interfaces

Port

Routing Engine console or auxiliary interface

Routing Engine

Ethernet interface

Alarm relay contacts

Cable

Specification

RS-232 (EIA-232) serial cable

Category 5 cable or equivalent suitable for 100BaseT operation

Wire with gauge between 24-AWG and 12-AWG (0.20

and 3.33 mm2)

Cable/Wire

Supplied

One 6-ft (1.83-m) length with

DB-9/DB-9 connectors

One 15-ft (4.57-m) length with

RJ-45/RJ-45 connectors

Maximum

Length

6 ft (1.83 m)

328 ft (100 m)

None

Router

Receptacle

DB-9 male

RJ-45 autosensing

—

Site Preparation Checklist

The checklist in Table 20 summarizes the tasks you need to perform when preparing a site for router installation.

Table 20: Site Preparation Checklist

Item or Task

Verify that environmental factors such as temperature and humidity do not exceed router tolerances (see Routing Node

Environmental Specifications on page 62).

Measure distance between external power sources and router installation site.

Select the type of rack or cabinet.

Plan rack or cabinet location, including required space clearances.

If a rack is used, secure rack to floor and building structure.

Acquire cables and connectors.

Performed By Date Notes

Site Preparation Checklist 75

M160 Internet Router Hardware Guide

Item or Task

Locate sites for connection of system grounding.

Calculate power budget and power margin.

Performed By Date Notes

76 Site Preparation Checklist

Chapter 6 Unpacking the Router

This chapter explains how to unpack the router and verify the parts received.

Before beginning, prepare the installation site as described in “Preparing for

Router Installation” on page 59 and review the safety information in “Safety and

Regulatory Compliance Information” on page 221, especially “General Safety

Guidelines and Warnings” on page 224 and “Installation Safety Guidelines and

Warnings” on page 239. This chapter discusses the following topics:

Tools and Parts Required on page 77

Unpacking the Router on page 77

Tools and Parts Required

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 or socket wrench to remove bracket bolts from the shipping pallet

Blank panels to cover any slots not occupied by a component

Unpacking the Router

The router is shipped in a wooden crate and bolted to the pallet that forms the bottom of the crate. The crate also contains an accessory box, the handle used during manual router installation, and the M160

Internet Router Installation Quick Start poster.

NOTE: The router is maximally protected inside the shipping crate. Do not unpack it until you are ready to begin installation.

To unpack the router, perform these steps:

Move the shipping crate to a staging area as close to the installation site as possible, but where you have enough room to remove the system components.

Unpacking the Router 77

M160 Internet Router Hardware Guide

While the chassis is bolted to the pallet, you can use a forklift or pallet jack to move it.

Position the crate so that the arrows are pointing up.

Twist open the locking tabs that secure the crate to the pallet and the front panel to the side panels.

Remove the front panel from the crate, then lift the top and sides off the pallet as a unit. See Figure 31.

Remove the plastic cover, then the foam and Quick Start that are sitting on top of the chassis. The installation handle and accessory box are embedded in cutouts in the foam.

Open the accessory box and verify the contents against the parts inventory on the label attached to the box.

Verify the chassis components received against the packing list included with the router. A generic parts inventory appears in Table 21.

Use a 1/2-in. open-end or socket wrench to loosen and remove the bolts on the brackets that attach the chassis to the pallet. If a 1/2-in. tool is not available, use pliers or an adjustable wrench rather than a fixed-size metric wrench.

Use a Phillips screwdriver to loosen the screws that secure the brackets to the sides of the chassis, and remove the brackets. Store the brackets, screws, and bolts inside the accessory box.

10.

Save the shipping crate, packing materials, and pallet in case you later need to move or ship the router.

78 Unpacking the Router

Unpacking the Router

Figure 31: Unpacking the Router

Shipping crate cover

M160 chassis

Shipping crate base

Table 21: Generic Inventory of Router Components Installed in Chassis

Component

Front impeller assembly with craft interface

FPC with one or more PICs installed

PIC

CIP

Front fan tray with 4 fans and cable management system

Midplane

Rear upper impeller assembly

SFM

MCS

Routing Engine

PCG

Rear lower impeller assembly

Circuit breaker box

Power supply

Center-mounting brackets

Blank panels for slots without components

Quantity

Up to 8

Up to 4 per FPC

1 or 2

Varies depending on router configuration

Unpacking the Router 79

M160 Internet Router Hardware Guide

80 Unpacking the Router

Chapter 7 Installing the Router Using a Mechanical

Lift

Because the router weighs between 190 lb (86 kg) and about 370.5 lb (168 kg) depending on configuration, using a mechanical lift to install it is recommended.

This chapter provides instructions. If you do not use a lift, see “Installing the Router without a Mechanical Lift” on page 83. This chapter has the following sections:

Tools and Parts Required on page 81

Installing the Chassis Using a Mechanical Lift on page 81

Tools and Parts Required

To install the chassis into a rack using a mechanical lift, you need the following tools and parts:

Mechanical lift

5/32-in. Allen (hexagonal) wrench for tightening the mounting screws provided in the accessory box; do not substitute a metric-size wrench

Phillips (+) screwdrivers, numbers 1 and 2, if removing center-mounting brackets or installing rear support shelf

Installing the Chassis Using a Mechanical Lift

Using a mechanical lift to maneuver the router into the rack is recommended because of the router’s size and weight. The lift must be able to accommodate the router’s weight—between 190 lb (86 kg) and about 370.5 lb (168 kg) depending on configuration—and must fit between the support posts of the rack.

NOTE: If you are installing multiple routers in a rack, install the lowest one first and proceed upward.

Installing the Chassis Using a Mechanical Lift 81

M160 Internet Router Hardware Guide

First, perform the following prerequisite procedures:

Verify that the router site meets the requirements described in “Preparing for Router Installation” on page 59.

Place the rack in its permanent location, allowing adequate clearance for airflow and maintenance, and secure it to the building structure. For details, see Rack Requirements on page 59.

Read the information in “Installation Safety Guidelines and Warnings” on page

239, with particular attention to “Chassis Lifting Guidelines” on page 239.

Remove the router from the shipping carton, as described in “Unpacking the

Router” on page 77.

Then, perform the following procedures to install the router:

If you are front-mounting the router, remove the center-mounting ear from each side of the chassis. (Also, we recommend installing a shelf or other support for the rear of the chassis.)

Load the router onto the lift, making sure it rests securely on the lift platform.

Use the lift to position the router at the correct height in the rack.

Align the bottom hole in both front support posts or center-mounting brackets with a hole in each rack rail, making sure the chassis is level.

Install one of the mounting screws provided into each of the two aligned holes.

Use a 5/32-in. Allen wrench to tighten the screws.

Moving up each post or ear, install a screw in every mounting hole.

Verify that all the mounting screws on one side of the rack are aligned with the mounting screws on the opposite side and that the router is level.

Move the lift away from the rack.

To continue the installation, proceed to “Connecting the Router and Performing

Initial Configuration” on page 111.

82 Installing the Chassis Using a Mechanical Lift

Chapter 8 Installing the Router without a

Mechanical Lift

You can install the router into a rack either with or without the help of a mechanical lift. Because the router weighs between 190 lb (86 kg) and about 370.5 lb

(168 kg) depending on configuration, using a mechanical lift is recommended; for instructions, see “Installing the Router Using a Mechanical Lift” on page 81.

If you do not use a mechanical lift, you must remove components from the chassis to reduce its weight before lifting it into the rack. The reduced chassis weight is approximately 115 lb (52 kg), so installing it safely still requires three people to lift and another person to insert the mounting screws.

Table 22 lists the weight of the chassis and major components.

Table 22: Router Component Weights

Component

Air filter

Cable management system

Chassis (with midplane, CIP, and circuit breaker box or panel)

DC power supply

Fan tray

FPC with 4 installed PICs

Front impeller assembly with craft interface

MCS

PCG

Rear lower impeller assembly

Rear upper impeller assembly

Routing Engine

SFM

1.5

14.5

2.5

0.75

Approximate

Weight (lb)

113.5

2.3

1.8

0.7

2.3

5.9

6.8

6.6

1.1

0.34

Approximate

Weight (kg)

0.9

0.5

51.5

Installing the Chassis Using a Mechanical Lift 83

M160 Internet Router Hardware Guide

Before installing the chassis, perform the following prerequisite procedures:

Verify that the router site meets the requirements described in “Preparing for Router Installation” on page 59.

Place the rack in its permanent location, allowing adequate clearance for airflow and maintenance, and secure it to the building structure. For details, see Rack Requirements on page 59.

Read the information in “Installation Safety Guidelines and Warnings” on page

239, with particular attention to “Chassis Lifting Guidelines” on page 239.

Remove the router from the shipping carton, as described in “Unpacking the

Router” on page 77.

Then install the router by performing the procedures in the following sections:

Tools and Parts Required on page 84

Removing Components from the Chassis on page 84

Installing the Chassis into the Rack on page 97

Reinstalling Components into the Chassis on page 99

Tools and Parts Required

To install the chassis without using a mechanical lift, you need the following tools and parts:

Phillips (+) screwdrivers, numbers 1 and 2

Flat-blade screwdriver, approximately 1/4 in. (6 mm), for removing craft interface

5/32-in. Allen (hexagonal) wrench for tightening the mounting screws provided in the accessory box; do not substitute a metric-size wrench

Electrostatic bags or antistatic mats, one for each electronic component removed

Electrostatic discharge (ESD) grounding wrist strap

Removing Components from the Chassis

To make the router light enough to install without a mechanical lift, you must remove most of the components.

84 Removing Components from the Chassis

Installing the Router without a Mechanical Lift

WARNING: The procedures in this section apply only to initial installation and assume that you have not yet connected power to the router. If power is connected, completely disconnect it before continuing. See “Disconnecting Power from the

Router” on page 200.

If you are installing or replacing components in an operational router, see

“Replacing Hardware Components” on page 139.

Do not stack components on top of one another after removing them from the chassis. Place each one individually on a flat, stable surface, either on an antistatic mat or in an electrostatic bag.

Set the removed components far enough away from the installation site that they will not be in the way as you lift the chassis into the rack.

Perform the procedures described in the following sections to remove components from the chassis, first from the rear and then from the front:

Removing the Power Supplies on page 86

Removing the Rear Component Cover on page 86

Removing the SFMs on page 87

Removing the MCSs on page 88

Removing the PCGs on page 89

Removing the Routing Engines on page 90

Removing the Rear Upper Impeller Assembly on page 91

Removing the Rear Lower Impeller Assembly on page 92

Removing the Fan Tray on page 93

Removing the FPCs on page 94

Removing the Front Impeller Assembly on page 96

NOTE: Do not remove the circuit breaker box or the Connector Interface Panel (CIP).

This chapter does not include instructions for removing these components.

Removing Components from the Chassis 85

M160 Internet Router Hardware Guide

Removing the Power Supplies

The router has two power supplies located at the bottom rear of the chassis, as shown in Figure 2. A power supply weighs approximately 13 lb (5.9 kg).

To remove the power supplies, follow this procedure (see Figure 32):

Attach an electrostatic discharge (ESD) grounding strap to your bare wrist and connect the strap to one of the ESD points on the chassis. Make sure the router is attached to a proper earth ground. For more information about ESD, see

“Preventing Electrostatic Discharge Damage” on page 226.

Verify that the power switch for each power supply is in the OFF ( O ) position.

The switches are on the circuit breaker box.

Loosen the thumbscrew at each corner of the power supply faceplate, using a Phillips screwdriver if necessary.

Grasp the handle or handles on the power supply faceplate and pull firmly to slide the unit about halfway out of the chassis.

Place one hand under the power supply to support it, then slide it completely out of the chassis.

Repeat the procedure to remove the second power supply.

Figure 32: Removing a Power Supply

Removing the Rear Component Cover

The rear component cover protects the SFMs, Routing Engines, MCSs, and

PCGs, as shown in Figure 2. To remove it, follow this procedure:

“Preventing Electrostatic Discharge Damage” on page 226.

86 Removing Components from the Chassis

Installing the Router without a Mechanical Lift

Loosen the thumbscrew at each corner of the component cover, using a

Phillips screwdriver if necessary.

Pull the cover straight off the chassis.

CAUTION: To maintain proper airflow and provide electromagnetic shielding, do not operate the router without the rear component cover in place.

Removing the SFMs

The router can have an SFM in each of the slots labeled SFM 0 through

SFM 3 at the rear of the chassis, as shown in Figure 3. Each SFM weighs approximately 5 lb (2.3 kg).

To remove an SFM, follow this procedure (see Figure 33):

Place an electrostatic bag or antistatic mat on a flat, stable surface.

“Preventing Electrostatic Discharge Damage” on page 226.

Loosen the thumbscrew on each ejector locking tab (shown in Figure 8), using a Phillips screwdriver if necessary.

Pull the end of each ejector handle outward until it is nearly perpendicular to the SFM faceplate.

Grasp the ejector handles and pull firmly to slide the SFM about halfway out of the chassis.

Place one hand under the SFM to support it, slide it completely out of the chassis, and place it on the antistatic mat or in the electrostatic bag.

CAUTION: When an SFM is out of the chassis, do not hold it by the ejector handles.

They cannot support its weight.

Do not stack SFMs on top of or under other components. Place each one individually in an electrostatic bag or on its own antistatic mat on a flat, stable surface.

If additional SFMs are installed, repeat the procedure to remove them.

Removing Components from the Chassis 87

M160 Internet Router Hardware Guide

Figure 33: Removing an SFM

Locking tab

Ejector handle

Removing the MCSs

The router can have an MCS in each of the slots labeled MCS 0 and MCS 1 at the rear of the chassis, as shown in Figure 3. Each MCS weighs approximately 2.5 lb (1 kg).

To remove the MCSs, follow this procedure (see Figure 34):

Place an electrostatic bag or antistatic mat on a flat, stable surface.

“Preventing Electrostatic Discharge Damage” on page 226.

Push the end of each extractor clip (located at each end of the MCS) outward.

Grasp the extractor clips and slide the MCS about halfway out of the chassis.

Place one hand under the MCS to support it, slide it completely out of the chassis, and place it on the antistatic mat or in the electrostatic bag.

If a second MCS is installed, repeat the procedure to remove it.

88 Removing Components from the Chassis

Installing the Router without a Mechanical Lift

Figure 34: Removing an MCS

SFM 0

SFM 1

MCS 0

RE 0

PCG 0

Extractor clip

Removing the PCGs

The router has two PCGs installed in the slots labeled PCG 0 and PCG 1 at the rear of the chassis, as shown in Figure 3. Each PCG weighs approximately 1 lb (0.5 kg).

To remove the PCGs, follow this procedure (see Figure 35):

Place an electrostatic bag or antistatic mat on a flat, stable surface.

“Preventing Electrostatic Discharge Damage” on page 226.

Loosen the thumbscrew at the lower right corner of the PCG faceplate, using a Phillips screwdriver if necessary.

Grasp the thumbscrew and slide the PCG about halfway out of the chassis.

CAUTION: Be careful to slide the PCG straight out of the chassis to avoid bending any of the pins on the underside of the board.

Place one hand under the PCG to support it, slide it completely out of the chassis, and place it on the antistatic mat or in the electrostatic bag.

Repeat the procedure to remove the second PCG.

Removing Components from the Chassis 89

M160 Internet Router Hardware Guide

Figure 35: Removing a PCG

SFM 0

SFM 1

MCS 0

RE 0

RE 1

MCS 1

PCG 0

PCG 1

Removing the Routing Engines

The router can have a Routing Engine in each of the slots labeled RE 0 and RE 1 at the rear of the chassis, as shown in Figure 3. Each Routing

Engine weighs approximately 1.5 lb (0.7 kg).

To remove a Routing Engine, follow this procedure (see Figure 36):

Place an electrostatic bag or antistatic mat on a flat, stable surface.

“Preventing Electrostatic Discharge Damage” on page 226.

Using your thumbs, push and hold the red tab on each extractor clip toward the outer edge of the unit. Push the ends of the extractor clips outward to unseat the Routing Engine from the chassis.

Grasp the extractor clips and slide the unit about halfway out of the chassis.

CAUTION: Slide the Routing Engine straight out of the chassis. Damage can result if it gets lodged because of uneven movement.

Place one hand under the Routing Engine to support it, slide it completely out of the chassis, and place it on the antistatic mat or in the electrostatic bag.

90 Removing Components from the Chassis

Installing the Router without a Mechanical Lift

If a second Routing Engine is installed, repeat the procedure to remove it.

Figure 36: Removing a Routing Engine

SFM 0

SFM 1

MCS 0

RE 0

RE 1

PCG 0

PCG 1

Extractor clip

Removing the Rear Upper Impeller Assembly

The rear upper impeller assembly is located at the top of the chassis rear, as shown in Figure 2. The assembly weighs approximately 4 lb (1.8 kg).

To remove the rear upper impeller assembly, follow this procedure (see Figure 37 and Figure 38, which show the two types of impeller that can be installed):

“Preventing Electrostatic Discharge Damage” on page 226.

Loosen the thumbscrew at each corner of the impeller cover, using a Phillips screwdriver if necessary.

Grasp the screws at opposite corners of the impeller cover and slide the assembly out of the chassis.

Removing Components from the Chassis 91

M160 Internet Router Hardware Guide

Figure 37: Removing the Rear Upper Impeller Assembly

Figure 38: Removing the Rear Upper Impeller Assembly

Removing the Rear Lower Impeller Assembly

The rear lower impeller assembly is located to the left of the circuit breaker box on the rear of the chassis, as shown in Figure 2. The assembly weighs approximately 5 lb (2.3 kg).

To remove the rear lower impeller assembly, follow this procedure (see Figure 39):

“Preventing Electrostatic Discharge Damage” on page 226.

Loosen the thumbscrew at each corner of the impeller cover, using a Phillips screwdriver if necessary.

92 Removing Components from the Chassis

Installing the Router without a Mechanical Lift

Grasp the screws at opposite corners of the impeller cover and slide the assembly out of the chassis.

Figure 39: Removing the Rear Lower Impeller Assembly

Removing the Fan Tray

The fan tray is located behind the cable management system on the front of the chassis, just above the air filter, as shown in Figure 1. The fan tray contains four fans and weighs approximately 13 lb (5.9 kg).

To remove the fan tray, follow this procedure (see Figure 40):

“Preventing Electrostatic Discharge Damage” on page 226.

Loosen the thumbscrew at each end of the fan tray, using a Phillips screwdriver if necessary.

Grasp the sides of the fan tray and pull firmly to slide it out of the chassis.

Removing Components from the Chassis 93

M160 Internet Router Hardware Guide

Figure 40: Removing the Fan Tray

Removing the FPCs

The router can have up to eight FPCs mounted vertically in the FPC card cage on the front of the chassis, as shown in Figure 1. An FPC that houses four PICs weighs about 15 lb (6.8 kg).

NOTE: To help you work systematically, the following procedure directs you to remove FPCs starting at the left side of the card cage and working toward the right.

You can remove FPCs in any order, however. As you remove each FPC, label it with its slot number and record the relevant information in the checklist in Table 23.

Table 23: FPC Removal Checklist

Media Types Slot

Date Removed Date Reinstalled

To remove the FPCs, follow this procedure (see Figure 41):

94 Removing Components from the Chassis

Installing the Router without a Mechanical Lift

Place an electrostatic bag or antistatic mat on a flat, stable surface.

“Preventing Electrostatic Discharge Damage” on page 226.

Locate the FPC or blank panel located in the leftmost slot of the card cage on the front of the chassis. It is directly below the offline button on the craft interface that is labeled FPC0 .

If the slot is covered by a blank panel, you can leave it in place. If the slot contains an FPC, perform the following steps: a.

Loosen the thumbscrew at each end of the FPC, using a Phillips screwdriver if necessary.

Pull the ends of the ejector levers, which are adjacent to the thumbscrews, away from the face of the FPC until they are nearly perpendicular to it.

Grasp the top and bottom flanges of the card carrier and slide the FPC about halfway out of the card cage.

Place one hand around the front of the FPC (the PIC housing) and the other hand under it to support it. Slide the FPC completely out of the chassis, and place it on the antistatic mat or in the electrostatic bag.

CAUTION: The weight of the FPC is concentrated in the back end. Be prepared to accept the full weight—up to 29 lb (13.2 kg)—as you slide the FPC out of the chassis.

When the FPC is out of the chassis, do not hold it by the ejector levers, bus bars, or edge connectors. They cannot support its weight.

Do not stack FPCs on top of one another after removal. Place each one individually in an electrostatic bag or on its own antistatic mat on a flat, stable surface.

Repeat Step 4 for each FPC card carrier or blank cover, proceeding from left to right.

Removing Components from the Chassis 95

M160 Internet Router Hardware Guide

Figure 41: Removing an FPC

Offline button

Ejector levers

Removing the Front Impeller Assembly

The front impeller assembly, which includes the craft interface, is located at the front of the chassis above the FPC card cage, as shown in Figure 1.

The assembly weighs approximately 14.5 lb (6.6 kg).

To remove the front impeller assembly, follow this procedure (see Figure 42):

Place an electrostatic bag or antistatic mat on a flat, stable surface.

“Preventing Electrostatic Discharge Damage” on page 226.

Using a Phillips screwdriver, loosen the captive screw at each corner of the craft interface.

96 Removing Components from the Chassis

Installing the Router without a Mechanical Lift

Insert a flat-blade screwdriver into the gap around the craft interface and gently pry the impeller assembly forward until you can grasp the sides of the assembly and slide it halfway out of the chassis.

Place one hand under the assembly to support it, slide it completely out of the chassis, and place it on the antistatic mat or in the electrostatic bag.

Figure 42: Removing the Front Impeller Assembly

Captive screw

Installing the Chassis into the Rack

After you have removed components as described in Removing

Components from the Chassis on page 84, the chassis is light enough for a team of installers to lift into the rack.

CAUTION: The reduced weight of the chassis is approximately 115 lb (52 kg).

Installing it into the rack still requires three people to lift and an additional person to secure the mounting screws.

If you are installing multiple routers in a rack, install the lowest one first and proceed upward.

Perform the following procedures (see Figure 44):

If you are front-mounting the router, remove the center-mounting ear from each side of the chassis. (Also, we recommend installing a shelf or other support for the rear of the chassis.)

Attach the lifting handle to the rear of the chassis, screwing the thumbscrews at its corners into the holes located next to the SFM slots on the chassis (see

Figure 43). If you are installing the chassis in a lower rack space, use the set of holes adjacent to the slots labeled SFM 0 and SFM 1 . If you are installing

Installing the Chassis into the Rack 97

M160 Internet Router Hardware Guide the chassis in an upper rack space, use the set of holes adjacent to the slots labeled SFM 2 and SFM 3 .

Figure 43: Attaching the Lifting Handle

SFM 1

MCS 0

Prepare to lift the router:

One person stands behind the chassis and grasps the lifting handle.

Two people stand on either side of the chassis. Each grasps the bar at the bottom of the FPC card cage with one hand and places the other hand under the chassis near the rear.

Lift the chassis and position it in the rack.

WARNING: To prevent injury, keep your back straight and lift with your legs, not your back. Avoid twisting your body as you lift. Balance the load evenly and be sure that your footing is solid.

Align the bottom hole in both front support posts or center-mounting brackets with a hole in each rack rail, making sure the chassis is level.

Install one of the mounting screws provided into each of the two aligned holes.

Use a 5/32-in. Allen wrench to tighten the screws.

Moving up each post or ear, install a screw in every mounting hole.

Verify that all the mounting screws on one side of the rack are aligned with the mounting screws on the opposite side and that the router is level.

Loosen the thumbscrews on the lifting handle and remove it from the chassis.

98 Installing the Chassis into the Rack

Installing the Router without a Mechanical Lift

10.

Proceed to the instructions in Reinstalling Components into the Chassis on page 99.

Figure 44: Installing the Chassis in a Rack

Center-mounting rack

Chassis rack-mounting ear

Reinstalling Components into the Chassis

After you have mounted the chassis in the rack as described in Installing the Chassis into the Rack on page 97, reinstall the router components into the chassis.

Router” on page 200.

Reinstalling Components into the Chassis 99

M160 Internet Router Hardware Guide

If you are installing or replacing components in an operational router, see

“Replacing Hardware Components” on page 139.

Perform the procedures described in the following sections to reinstall components into the chassis, first into the front and then into the rear:

Reinstalling the Front Impeller Assembly on page 100

Reinstalling the FPCs on page 101

Reinstalling the Fan Tray on page 102

Reinstalling the Rear Lower Impeller Assembly on page 103

Reinstalling the Rear Upper Impeller Assembly on page 104

Reinstalling the Routing Engines on page 105

Reinstalling the PCGs on page 106

Reinstalling the MCSs on page 107

Reinstalling the SFMs on page 108

Reinstalling the Rear Component Cover on page 109

Reinstalling the Power Supplies on page 109

Reinstalling the Front Impeller Assembly

The front impeller assembly, which includes the craft interface, is located at the top of the chassis front, as shown in Figure 1. To reinstall it, follow this procedure (see Figure 45):

“Preventing Electrostatic Discharge Damage” on page 226.

Grasp the sides of the impeller assembly and align the rear of the assembly with the guides inside the chassis.

Slide the impeller assembly all the way into the chassis.

Using a Phillips screwdriver, tighten the captive screw at each corner of the craft interface.

100 Reinstalling Components into the Chassis

Installing the Router without a Mechanical Lift

Figure 45: Reinstalling the Front Impeller Assembly

Captive screw

Reinstalling the FPCs

The FPCs install into the card cage at the front of the chassis, as shown in Figure 1.

NOTE: To help you work systematically, the following procedure directs you to reinstall FPCs starting at the left side of the card cage and working toward the right.

You can install FPCs in any order, however.

Be sure there is a blank panel over every empty slot. The blank panels must be in place during router operation to guarantee adequate circulation of cooling air.

To reinstall the FPCs, follow this procedure (see Figure 46):

“Preventing Electrostatic Discharge Damage” on page 226.

Locate the leftmost slot in the FPC card cage on the front of the chassis. It is directly below the offline button on the craft interface that is labeled FPC0 .

Locate the FPC that you labeled FPC0 during removal.

Verify that the ends of the ejector levers, which are located at each end of the

FPC, are pushed outward, nearly perpendicular to the face of the FPC.

Grasp the front of the FPC with one hand and place the other hand under the FPC to support it.

CAUTION: When the FPC is out of the chassis, do not hold it by the ejector levers, bus bars, or edge connectors. They cannot support its weight.

Reinstalling Components into the Chassis 101

M160 Internet Router Hardware Guide

Align the rear bottom corners of the FPC with the guides at the bottom of the

FPC slot. Slide the FPC into the card cage until it contacts the midplane.

Push the ends of the ejector levers inward until they are nearly flush with the face of the FPC.

Tighten the thumbscrew at each end of the FPC to seat the FPC securely in the chassis.

Repeat the procedure for each FPC, proceeding from left to right through the slots with offline buttons labeled FPC1 through FPC7 on the craft interface.

Figure 46: Reinstalling an FPC

Ejector levers

Reinstalling the Fan Tray

The fan tray, which includes the cable management system, is located on the front of the chassis, just above the air filter, as shown in Figure 1. To reinstall it, follow this procedure (see Figure 47):

102 Reinstalling Components into the Chassis

Installing the Router without a Mechanical Lift

“Preventing Electrostatic Discharge Damage” on page 226.

Grasp the sides of the fan tray and align the rear of the tray with the guides inside the chassis.

Slide the fan tray all the way into the chassis.

Tighten the thumbscrew at each end of the cable management system.

Figure 47: Reinstalling the Fan Tray

Reinstalling the Rear Lower Impeller Assembly

The rear lower impeller assembly is located to the left of the circuit breaker box on the rear of the chassis, as shown in Figure 2. To reinstall it, follow this procedure (see Figure 48):

“Preventing Electrostatic Discharge Damage” on page 226.

Orient the impeller so that the label is on the top. Align the rails on the upper edges of the impeller assembly with the guides inside the chassis.

Push the impeller assembly up and to the right to start it into the chassis, then slide it all the way in.

Tighten the thumbscrew at each corner of the impeller cover.

Reinstalling Components into the Chassis 103

M160 Internet Router Hardware Guide

Figure 48: Reinstalling the Rear Lower Impeller Assembly

Label

Guides

Rails

Reinstalling the Rear Upper Impeller Assembly

The rear upper impeller assembly is installed at the top of the chassis rear, as shown in Figure 2. To reinstall the assembly, follow this procedure (see Figure 49 and Figure 50, which show the two types of impeller that can be installed):

“Preventing Electrostatic Discharge Damage” on page 226.

Slide the assembly all the way into the chassis.

Tighten the thumbscrew at each corner of the impeller cover.

104 Reinstalling Components into the Chassis

Figure 49: Reinstalling the Rear Upper Impeller Assembly

Installing the Router without a Mechanical Lift

Figure 50: Reinstalling the Rear Upper Impeller Assembly

Reinstalling the Routing Engines

The router can have a Routing Engine in each of the slots labeled RE 0 and

RE 1 at the rear of the chassis, as shown in Figure 3.

NOTE: If two Routing Engines are installed, they must both be the same version.

To reinstall a Routing Engine, follow this procedure (see Figure 51):

“Preventing Electrostatic Discharge Damage” on page 226.

Reinstalling Components into the Chassis 105

M160 Internet Router Hardware Guide

Verify that the extractor clip at each end of the Routing Engine is flipped toward the outer edge of the unit. If necessary, use your thumbs to push and hold the red tab on each extractor clip toward the outer edge, then push the ends of the extractor clips outward.

Place one hand under the Routing Engine to support it and grasp one of the extractor clips on the faceplate with the other hand.

Align the rear of the Routing Engine with the guide rails inside the chassis and slide it in completely.

CAUTION: Align the Routing Engine carefully with the guide rails and push it in evenly. Damage can result if it gets lodged in the rails because of uneven movement.

Press the extractor clip at each end of the Routing Engine inward to seat the unit firmly in the chassis.

If there is a second Routing Engine, repeat the procedure to reinstall it.

Figure 51: Reinstalling a Routing Engine

SFM 0

SFM 1

MCS 0

RE 0

RE 1

PCG 0

PCG 1

Extractor clip

Reinstalling the PCGs

The router has two PCGs installed in the slots labeled PCG 0 and PCG 1 at the rear of the chassis, as shown in Figure 3. To reinstall the PCGs, follow this procedure (see Figure 52):

106 Reinstalling Components into the Chassis

Installing the Router without a Mechanical Lift

“Preventing Electrostatic Discharge Damage” on page 226.

Place one hand under the PCG to support it and grasp the thumbscrew on the faceplate with the other hand.

Align the rear of the PCG with the guides inside the chassis and slide it in completely.

Tighten the thumbscrew on the faceplate to seat the PCG firmly in the chassis.

Repeat the procedure to reinstall the second PCG.

Figure 52: Reinstalling a PCG

SFM 0

SFM 1

MCS 0

RE 0

RE 1

MCS 1

PCG 0

PCG 1

Reinstalling the MCSs

The router can have an MCS in each of the slots labeled MCS 0 and

MCS 1 at the rear of the chassis, as shown in Figure 3. To reinstall an

MCS, follow this procedure (see Figure 53):

“Preventing Electrostatic Discharge Damage” on page 226.

Place one hand under the MCS to support it and grasp one of the extractor clips on the faceplate with the other hand.

Reinstalling Components into the Chassis 107

M160 Internet Router Hardware Guide

Align the rear of the MCS with the guides inside the chassis and slide it in completely.

Press the extractor clip at each end of the MCS inward.

If there is a second MCS, repeat the procedure to reinstall it.

Figure 53: Reinstalling an MCS

SFM 0

SFM 1

MSC 0

RE 0

PCG 0

Extractor clip

Reinstalling the SFMs

The router can have an SFM in each of the slots labeled SFM 0 through

SFM 3 at the rear of the chassis, as shown in Figure 3. To reinstall an

SFM, follow this procedure (see Figure 54):

“Preventing Electrostatic Discharge Damage” on page 226.

Verify that the ends of the ejector handles are pulled outward to a position nearly perpendicular to the faceplate of the SFM.

Place one hand under the SFM to support it and grasp one of the ejector handles at the front with the other hand.

Align the rear of the SFM with the guides inside the chassis and slide it in completely.

Press the ejector handle at each end of the SFM inward.

Tighten the thumbscrew on each ejector locking tab (shown in Figure 8) to seat the SFM firmly in the chassis.

108 Reinstalling Components into the Chassis

Installing the Router without a Mechanical Lift

If there are additional SFMs, repeat the procedure to reinstall them.

Figure 54: Reinstalling an SFM

SFM 0

SFM 1

MCS 0

Locking tab

Ejector handle

Reinstalling the Rear Component Cover

The rear component cover protects the Routing Engines, PCGs, MCSs, and SFMs, as shown in Figure 2. To reinstall the rear component cover, follow this procedure:

“Preventing Electrostatic Discharge Damage” on page 226.

Hold the component cover up to the rear of the chassis and align the flanges at the top and bottom with the top and bottom of the opening in the chassis.

Push the cover into place.

Tighten the thumbscrew at each corner of the cover.

CAUTION: To maintain proper airflow and provide electromagnetic shielding, do not operate the router without the rear component cover in place.

Reinstalling the Power Supplies

The two power supplies are located at the bottom rear of the chassis, as shown in

Figure 2. To reinstall the power supplies, follow this procedure (see Figure 55):

Reinstalling Components into the Chassis 109

M160 Internet Router Hardware Guide

“Preventing Electrostatic Discharge Damage” on page 226.

Verify that the power switch for each power supply is in the OFF ( O ) position.

The switches are on the circuit breaker box.

Place one hand under the power supply and grasp a handle on the faceplate with the other hand. Slide the power supply into the chassis until it contacts the midplane.

Starting with the bottom screws, tighten (but do not overtighten) the thumbscrew at each corner of the power supply faceplate.

Repeat the procedure to reinstall the second power supply.

To continue the installation, proceed to “Connecting the Router and Performing

Initial Configuration” on page 111.

Figure 55: Reinstalling a Power Supply

110 Reinstalling Components into the Chassis

Chapter 9 Connecting the Router and Performing

Initial Configuration

After installing the router into the rack as described in “Installing the Router Using a

Mechanical Lift” on page 81 or “Installing the Router without a Mechanical Lift” on page 83, complete the installation by connecting management and alarm devices,

PICs, and power cables. This chapter has the following sections:

Tools and Parts Required on page 111

Connecting the Router to Management and Alarm Devices on page 112

Connecting PIC Cables on page 115

Providing Power to the Router on page 117

Configuring the JUNOS Internet Software on page 121

Tools and Parts Required

To connect the router to management devices and PICs and to power on the router, you need the following tools and parts:

Phillips (+) screwdrivers, numbers 1 and 2

2.5 mm flat-blade (-) screwdriver

7/16-in. hexagonal-head external drive socket wrench, or nut driver, with a minimum of 30 lb-in. (3.5 Nm) tightening torque, for tightening nuts to terminal studs on the circuit breaker box

Tools and Parts Required 111

M160 Internet Router Hardware Guide

CAUTION: Do not substitute a metric nut driver or wrench. A tool that does not fit the nuts exactly can damage them. If a 7/16-in. tool is not available, use pliers or an adjustable wrench.

Wire cutters

Pliers

Electrostatic discharge (ESD) grounding wrist strap

Connecting the Router to Management and Alarm Devices

After you have installed the router into the rack, attach one or more external devices to the ports on the CIP that connect to the Routing Engines for management and service operations (see Figure 56). For specifications for the cable accepted by the Routing Engine management ports, see Routing Engine Interface Cable and Wire Specifications on page 74.

112 Connecting the Router to Management and Alarm Devices

Connecting the Router and Performing Initial Configuration

Figure 56: Routing Engine Management Ports and Alarm Relay Contacts

HOST

ETHERNET

ACT

YEL=10Mb

GRN=100Mb

CONSOLE

AUXILIARY

BITS A

LINK

BITS B

LINK

RED ALARM

YELLOW

ALARM

CONSOLE

AUXILIARY

HOST

ETHERNET

ACT

YEL=10Mb

GRN=100Mb

Routing

Engine ports

BITS input ports

Alarm relay contacts

To connect external devices to the Routing Engine management ports, perform the procedures described in the following sections:

Connecting to a Network for Out-of-Band Management on page 114

Connecting to a Management Console or Auxiliary Device on page 114

Connecting to an External Alarm-Reporting Device on page 115

Connecting the Router to Management and Alarm Devices 113

M160 Internet Router Hardware Guide

Connecting to a Network for Out-of-Band Management

To connect the Routing Engine to a network for out-of-band management, connect an Ethernet cable with RJ-45/RJ-45 connectors to the ETHERNET port on the CIP. One such cable is provided with the router. For cable specifications, see Routing Engine

Interface Cable and Wire Specifications on page 74. Follow this procedure:

Turn off the power to the management device.

Plug one end of the Ethernet cable (Figure 57 shows the connector) into the appropriate ETHERNET port on the CIP. Figure 56 shows the external device ports on the CIP. The ports labeled HOST 0 connect to the Routing Engine in the upper Routing Engine slot ( RE 0 ), and the ports labeled HOST 1 connect to the

Routing Engine in the lower Routing Engine slot ( RE 1 ).

Plug the other end of the cable into the network device.

Figure 57: Routing Engine Ethernet Cable Connector

Connecting to a Management Console or Auxiliary Device

To use a system console to configure and manage the Routing Engine, connect it to the appropriate CONSOLE port on the CIP. To use a laptop, modem, or other auxiliary device, connect it to the appropriate AUXILIARY port on the CIP. Both ports accept an RS-232 (EIA-232) serial cable with DB-9/DB-9 connectors. One such cable is provided with the router. If you want to connect a device to both ports, you must supply another cable. For cable specifications, see Routing

Engine Interface Cable and Wire Specifications on page 74.

To connect a management console or auxiliary device, follow this procedure:

Turn off the power to the console or auxiliary device.

Plug the female end (shown in Figure 58) of the provided serial cable into the appropriate CONSOLE or AUXILIARY port. Figure 56 shows the external device ports on the CIP. The ports labeled HOST 0 connect to the Routing Engine in the upper Routing Engine slot ( RE 0 ), and the ports labeled HOST 1 connect to the

Routing Engine in the lower Routing Engine slot ( RE 1 ).

Using a 2.5 mm flat-blade screwdriver, tighten the screws on the connector.

Attach the other end of the cable to the console or auxiliary device.

114 Connecting the Router to Management and Alarm Devices

Connecting the Router and Performing Initial Configuration

Figure 58: Console and Auxiliary Serial Port Connector

Connecting to an External Alarm-Reporting Device

To connect the router to external alarm-reporting devices, attach wires to the RED ALARM and YELLOW ALARM relay contacts on the CIP. A system condition that triggers the red or yellow alarm LED on the craft interface also activates the corresponding alarm relay contact.

The terminal blocks that plug into the alarm relay contacts are supplied with the router. They accept wire of any gauge between 24-AWG and

12-AWG (0.20 and 3.33 mm2), which is not provided. Use the gauge of wire appropriate for the external device you are connecting.

To connect an external device to an alarm relay contact, follow this procedure (see Figure 56):

Prepare the required length of wire with gauge between 24-AWG and 12-AWG

(0.20 and 3.33 mm2).

While the terminal block is not plugged into the relay contact, use a 2.5 mm flat-blade screwdriver to loosen the small screws on its side. Insert wires into the slots in the front of the block. Tighten the screws to secure the wire.

Orient the terminal block according to the labels to the left of the appropriate relay contact ( NC means “normally closed,” C means “common,” and NO means “normally open”).

Plug the terminal block into the relay contact and use a 2.5 mm flat-blade screwdriver to tighten the screws on the face of the block.

Attach the other end of the wires to the external device.

If attaching a reporting device for the other kind of alarm, repeat the procedure.

Connecting PIC Cables

Now connect PICs to the network by plugging in network cable. To connect cable to the PICs, follow this procedure (see Figure 59, which shows a fiber-optic PIC):

Have ready a length of the type of cable used by the PIC. For cable specifications, see the M160 Internet Router PIC Guide .

If the PIC cable connector port is covered by a rubber safety plug, remove the plug.

Connecting PIC Cables 115

M160 Internet Router Hardware Guide

WARNING: Do not look directly into the ends of fiber-optic cables or into the transceivers on the interface faceplate. Single-mode fiber-optic cable and the interfaces that use it (such as ATM and SONET/SDH interfaces) emit laser light that can damage your eyes.

CAUTION: Do not leave a fiber-optic transceiver uncovered except when inserting or removing cable. The safety cap keeps the port clean and prevents accidental exposure to laser light.

Insert the cable connector into the cable connector port on the PIC faceplate.

Arrange the cable in the cable management system to prevent it from dislodging or developing stress points. Secure the cable so that it is not supporting its own weight as it hangs to the floor. Place excess cable out of the way in a neatly coiled loop in the cable management system. Placing fasteners on the loop helps to maintain its shape.

CAUTION: Avoid bending fiber-optic cable beyond its minimum bend radius. An arc smaller than a few inches in diameter can damage the cable and cause problems that are difficult to diagnose.

CAUTION: Do not let fiber-optic cable hang free from the connector. Do not allow fastened loops of cable to dangle, which stresses the cable at the fastening point.

116 Connecting PIC Cables

Figure 59: Attaching Cable to a PIC

Connecting the Router and Performing Initial Configuration

Providing Power to the Router

Connect the router to external power sources and power it on by performing the following procedures:

Connecting Power to the Router on page 117

Powering On the Router on page 119

Connecting Power to the Router

Connect power to the router by attaching a grounding cable to the chassis grounding points and attaching power cables from external power sources to the terminal studs on the circuit breaker box. Power and grounding cables are not supplied with the router. For cable specifications, see “Power,

Connection, and Cable Specifications” on page 67.

NOTE: The router must be connected to at least two separate external power sources.

The power source cables might be labeled (+) and (–) to indicate their polarity.

To connect power to the router, follow this procedure (see Figure 60):

Providing Power to the Router 117

M160 Internet Router Hardware Guide

Verify that there is no power flowing from either external power source, so that the voltage across the leads of the power cables is 0 V. Ensure that there is no chance that the cable leads might become active during the procedure.

For each power supply, verify that the power switch on the circuit breaker box is in the OFF ( O ) position.

Connect the grounding cable to a proper earth ground.

Verify that a licensed electrician has attached the cable lug provided with the router to the grounding cable.

Place the grounding cable lug over the grounding points on the bottom rear of the chassis. The grounding points are sized for 1/4-20 UNC screws.

Secure the grounding cable lug to the grounding points, first with the washers, then with the screws.

CAUTION: Do not substitute metric screws such as M6 for the 1/4-20 UNC screws that screw into the grounding points; screws other than 1/4-20 UNC screws can strip the threading in the grounding points.

Using a Phillips screwdriver, loosen and remove the screws securing the protective shield over the terminal studs on the circuit breaker box. Remove the cover.

Install one flat washer and one nut (in that order) on each power terminal stud:

If no washers and nuts are already installed, they should be in the accessory box.

If two pairs of nuts and washers are installed on the studs, use a 7/16-in.

nut driver or wrench to loosen the outer nut on each stud. Remove the outer nuts and washers, leaving the inner nut and washer on each stud.

CAUTION: Do not substitute a metric nut driver or wrench. A tool that does not fit the nuts exactly can damage them. If a 7/16-in. tool is not available, use pliers or an adjustable wrench.

CAUTION: The inner washer and nut prevent direct contact between the power cable lug and the circuit breaker box, which can cause a short circuit.

Slide the power cable lugs onto the terminal studs:

118 Providing Power to the Router

Connecting the Router and Performing Initial Configuration

Connect the positive (+) source cable lugs to the return terminals, which are labeled RTN(+) .

Connect the negative (–) source cable lugs to the input terminals, which are labeled –48V .

10.

Install another washer and nut (in that order) on each terminal stud to secure the power cable lug. Using a 7/16-in. nut driver or wrench, tighten the nuts.

11.

Verify that the source power cabling and the grounding cabling are correct, that they are not touching or blocking access to router components, and that they do not drape where people could trip on them.

12.

Replace the protective shield over the terminal studs and use a Phillips screwdriver to tighten the screws.

Figure 60: Connecting Power and Grounding Cables

Grounding points

To ground

Nut

Flat washer

Nut

Flat washer

Cable lug

Terminal studs

Powering On the Router

To power on the router, follow this procedure:

Verify that the power supplies are fully inserted in the chassis and the thumbscrews on their faceplates are tightened.

Providing Power to the Router 119

M160 Internet Router Hardware Guide

For each power supply, verify that the source power cables are connected to the appropriate terminal on the circuit breaker box: the positive (+) source cable to the return terminal (labeled RTN(+) ) and the negative (–) source cable to the input terminal (labeled –48V ).

Verify that an external management device is connected to one of the

Routing Engine ports on the CIP ( AUXILIARY , CONSOLE , or ETHERNET ). For more information on connecting management devices, see Connecting the Router to Management and Alarm Devices on page 112.

Turn on the power to the external management device.

Press one power switch on the circuit box to the ON ( | ) position.

Observe the LEDs on the power supply faceplate:

As an enhanced power supply powers on, the green CB ON LED lights steadily, the blue OUTPUT OK LED blinks for a short time, then lights steadily, and the amber CB OFF LED does not light.

As an original power supply powers on, the green CB ON LED lights steadily, the blue OUTPUT OK LED blinks for a short time, then lights steadily, and the amber CB OFF and NO AIRFLOW LEDs do not light.

NOTE: After powering off a power supply, wait at least 60 seconds before turning it back on. After powering on a power supply, wait at least 60 seconds before turning it off.

If the router is completely powered down when you power on the power supply, the Routing Engine boots as the power supply completes its startup sequence. If the Routing Engine finishes booting and you need to power down the router again, first issue the CLI request system halt command. For more information, see

“Disconnecting Power from the Router” on page 200.

Press the other power switch on the circuit breaker box to the ON ( | ) position and observe the LEDs on the second power supply faceplate. They should light as described in the previous step.

If the LEDs are not lit in the appropriate pattern after 60 seconds, repeat the power supply and cable installation procedures described in “Reinstalling the Power Supplies” on page 109 and “Connecting Power to the Router” on page 117.

On the external management device connected to the Routing Engine, monitor the startup process to verify that the system has booted properly.

120 Providing Power to the Router

Connecting the Router and Performing Initial Configuration

Configuring the JUNOS Internet Software

The router is shipped with the JUNOS Internet software preinstalled and ready to be configured when the router is powered on. There are three copies of the software: one on a nonrotating flash drive in the Routing Engine, one on a rotating hard drive in the Routing Engine, and one on a PC card that can be inserted into the slot in the Routing Engine faceplate.

When the router boots, it first attempts to start the image on the PC card. If a PC card is not inserted into the Routing Engine or the attempt otherwise fails, the router next tries the flash drive, and finally the hard drive.

You configure the router by issuing JUNOS command-line interface (CLI) commands, either on a console device attached to the CONSOLE port on the CIP, or over a telnet connection to a network connected to the ETHERNET port on the CIP.

Gather the following information before configuring the router:

Name the router will use on the network

Domain name the router will use

IP address and prefix length information for the Ethernet interface

IP address of a default router

IP address of a DNS server

Password for the root user

To configure the software, follow this procedure:

If the router is not already turned on, power it on as described in “Powering On the Router” on page 119.

Start the CLI.

root# cli root@>

Enter configuration mode.

cli> configure

[edit] root@#

Configure the name of the router. If the name includes spaces, enclose the name in quotation marks (“ ”).

[edit] root@# set system host-name host-name

Configuring the JUNOS Internet Software 121

M160 Internet Router Hardware Guide

Configure the router’s domain name.

[edit] root@# set system domain-name domain-name

Configure the IP address and prefix length for the router’s Ethernet interface.

[edit] root@# set interfaces fxp0 unit 0 family inet address address/prefix-length

Configure the IP address of a backup router, which is used only while the routing protocol is not running.

[edit] root@# set system backup-router address

Configure the IP address of a DNS server.

[edit] root@# set system name-server address

10.

Set the root authentication password by entering either a clear-text password, an encrypted password, or an ssh public key string (DSA or RSA).

[edit] root@# set system root-authentication plain-text-password

New password: password

Retype new password: password or

[edit] root@# set system root-authentication encrypted-password encrypted-password or

[edit] root@# set system root-authentication ssh-dsa public-key or

[edit] root@# set system root-authentication ssh-rsa public-key

11.

Optionally, display the configuration to verify that it is correct.

[edit] root@# show system { host-name host-name ; domain-name domain-name ; backup-router address ; root-authentication { authentication-method ( password | public-key );

} name-server { address ;

122 Configuring the JUNOS Internet Software

Connecting the Router and Performing Initial Configuration

}

} interfaces { fxp0 { unit 0 { family inet { address address/prefix-length ;

}

12.

Commit the configuration to activate it on the router.

[edit] root@# commit

13.

Optionally, configure additional properties by adding the necessary configuration statements. Then commit the changes to activate them on the router.

[edit] root@host# commit

14.

When you have finished configuring the router, exit configuration mode.

[edit] root@host# exit root@host>

Configuring the JUNOS Internet Software 123

M160 Internet Router Hardware Guide

124 Configuring the JUNOS Internet Software

Part 3 Hardware Maintenance, Replacement, and Troubleshooting Procedures

Maintaining Hardware Components on page 127

Replacing Hardware Components on page 139

Troubleshooting Hardware Components on page 207

Hardware Maintenance, Replacement, and Troubleshooting Procedures 125

126 Hardware Maintenance, Replacement, and Troubleshooting Procedures

Chapter 10 Maintaining Hardware Components

This chapter describes how to maintain hardware components installed in the router. Some components, such as the Connector Interface Panel (CIP), require no maintenance.

For information about returning a part to Juniper Networks for repair or replacement, see “Contacting Customer Support and Returning Hardware” on page 255.

Routine Maintenance Procedures on page 127

Maintaining Cooling System Components on page 127

Maintaining Host Module Components on page 131

Maintaining Packet Forwarding Engine Components on page 132

Maintaining Power Supplies on page 137

Routine Maintenance Procedures

For optimum router performance, perform the following preventive maintenance procedures regularly:

Inspect the installation site for moisture, loose wires or cables, and excessive dust. Make sure that airflow is unobstructed around the router and into the air intake vents.

Check the status-reporting devices on the craft interface: system alarms, LEDs, and LCD. See Craft Interface on page 27.

Inspect the air filters at the bottom front and left rear of the router, cleaning or replacing it as needed for optimum cooling system performance. Do not run the router for more than a few minutes without the air filters in place. For maintenance instructions, see “Maintaining the Air Filter” on page 128.

Maintaining Cooling System Components

For instructions on maintaining cooling system components, see the following sections:

Maintaining Cooling System Components 127

M160 Internet Router Hardware Guide

Maintaining the Air Filter on page 128

Maintaining the Fan Tray and Impellers on page 130

Maintaining the Air Filter

Check the air filter regularly for dust and debris. Clean or replace it as needed.

The air filter is hot-removable and hot-insertable, as described in Field-Replaceable

Units (FRUs) on page 4. Take note of the following caution, however.

CAUTION: Do not operate the router for more than a few minutes when the air filter has been removed. The fans and impellers are powerful enough to draw in foreign material, such as bits of wire, through the unfiltered air intake, which could damage router components.

To maintain the air filter, perform the following procedures:

Removing the Air Filter on page 128

Cleaning the Air Filter on page 129

Installing the Air Filter on page 129

Removing the Air Filter

The air filter is located at the front of the chassis, below the FPC card cage and cable management system (see Figure 61).

To remove the air filter, follow this procedure:

“Preventing Electrostatic Discharge Damage” on page 226.

Loosen the thumbscrew at each corner of the air filter cover.

Grasp the edges of the air filter and pull it away from the front of the chassis.

Inspect the filter for dust, dirt, and holes. If needed, clean it as described in

“Cleaning the Air Filter” on page 129 or replace it.

128 Maintaining Cooling System Components

Maintaining Hardware Components

Figure 61: Removing the Air Filter

Air filter cover

Air filter Air intake cover

Thumbscrew

Cleaning the Air Filter

To clean the air filter, follow this procedure:

Pull the filter free of the air filter cover (see Figure 62).

Rinse the filter with water, running the water from the back side to the front side to help remove dust and particles accumulated in the filter.

Allow the filter to dry completely.

Press the filter back into the air filter cover.

Figure 62: Removing the Filter from the Air Filter Cover

Air filter

Air filter cover

Installing the Air Filter

To install the air filter, follow this procedure (see Figure 63):

Attach an electrostatic discharge (ESD) grounding strap to your bare wrist and connect the strap to one of the ESD points on the chassis. Make sure the router

Maintaining Cooling System Components 129

M160 Internet Router Hardware Guide

is attached to a proper earth ground. For more information about ESD, see

“Preventing Electrostatic Discharge Damage” on page 226.

Grasp the sides of the air filter and push it firmly into place over the air intake vent.

Tighten the thumbscrew at each corner of the air filter cover.

Figure 63: Installing the Air Filter

Air filter cover

Air filter

Maintaining the Fan Tray and Impellers

The fan tray is attached to the back of the cable management system and installs into the front of the chassis, as shown in Figure 1. There are also three separate, non-interchangeable impeller assemblies. The front impeller is located behind the craft interface (shown in Figure 1) and works together with the fan tray to cool the FPCs and midplane. The upper and lower impellers on the rear of the chassis (shown in Figure 2) work together to cool the components that install into the rear of the chassis.

To check the status of the impellers and the fans in the fan tray, issue the show chassis environment command. The output includes an entry for each impeller

(which it refers to as a Blower ) and for each fan in the fan tray: user@host> show chassis environment

Class Item Status Measurement

...

Fans Rear Bottom Blower

Rear Top Blower

Front Top Blower

Fan Tray Rear Left

Fan Tray Rear Right

Fan Tray Front Left

Fan Tray Front Right

Spinning at normal speed

...

130 Maintaining Cooling System Components

Maintaining Hardware Components

For further description of the output from the command, see the JUNOS

Internet Software Operational Mode Command Reference: Protocols, Class of Service, Chassis, and Management .

Maintaining Host Module Components

The router can have a Routing Engine in each of the slots labeled RE 0 and RE

1 and a Miscellaneous Control Subsystem (MCS) in each of the slots labeled

MCS 0 and MCS 1 at the rear of the chassis, as shown in Figure 3. Each paired

Routing Engine and MCS function together as a host module. To maintain the host module, perform the following procedures regularly:

Check the LCD and the host module LEDs on the craft interface. The LCD reports host module status during normal operation and describes the cause of failures when they occur. The green LEDs labeled ONLINE and MASTER light steadily for the master host module when it is functioning normally. The

ONLINE LED also lights for the standby host module if it is installed. For more information about the LEDs and LCD, see Craft Interface on page 27.

Issue the CLI show chassis routing-engine command to check the status of the

Routing Engines. As shown in the sample output, the master Routing Engine is designated Master in the Current state field: user@host> show chassis routing-engine

Routing Engine status:

Slot 0:

Current state

Election priority

Temperature

DRAM

Memory utilization

CPU utilization:

User

Background

Kernel

Interrupt

Idle

Model

Serial ID

Start time

Uptime

Load averages:

Routing Engine status:

Slot 1:

Current state

Election priority

Temperature

DRAM

Memory utilization

CPU utilization:

User

Master

Master (default)

37 degrees C / 98 degrees F

768 MB

18 percent

0 percent

2 percent

0 percent

98 percent

RE-2.0

8b00000792898b01

2003-04-29 16:09:49 PDT

16 days, 3 hours, 6 minutes, 34 seconds

1 minute 5 minute 15 minute

0.00

Backup

Backup (default)

36 degrees C / 96 degrees F

768 MB

16 percent

0 percent

Maintaining Host Module Components 131

M160 Internet Router Hardware Guide

Background

Kernel

Interrupt

Idle

Model

Serial ID

Start time

Uptime

0 percent

100 percent

RE-2.0

6d000007c8150801

2003-04-22 10:01:29 PDT

16 days, 3 hours, 6 minutes, 34 seconds

Issue the CLI show chassis environment mcs command to check the status of the

MCSs. As shown in the sample output, the MCS that belongs to the master host module is designated Master in the State field: user@host> show chassis environment mcs

MCS 0 status:

State

Temperature

Power:

3.3 V

5.0 V

12.0 V

5.0 V bias

8.0 V bias

BUS Revision

FPGA Revision

MCS 1 status:

State

Temperature

Power:

3.3V

5.0 V

12.0 V

5.0 V bias

8.0 V bias

BUS Revision

FPGA Revision

Online Master

48 degrees C / 118 degrees F

3299 mV

4971 mV

11770 mV

4989 mV

8246 mV

Online Standby

51 degrees C / 123 degrees F

3316 mV

5001 mV

11775 mV

5001 mV

8249 mV

For further description of the output from the commands, see the JUNOS

Internet Software Operational Mode Command Reference: Protocols, Class of Service, Chassis, and Management .

Maintaining Packet Forwarding Engine Components

For instructions on maintaining Packet Forwarding Engine components, see the following sections:

Maintaining FPCs on page 133

Maintaining PICs and PIC Cables on page 134

Maintaining the PCGs on page 135

132 Maintaining Packet Forwarding Engine Components

Maintaining Hardware Components

Maintaining SFMs on page 136

Maintaining FPCs

The router can have up to eight Flexible PIC Concentrators (FPCs) mounted vertically in the FPC card cage at the front of the chassis, as shown in Figure 1.

To maintain FPCs, perform the following procedures regularly:

Check the LCD on the craft interface and the LEDs on the craft interface directly above each FPC slot. The green LED labeled OK lights steadily when an FPC is functioning normally. For more information, see “FPC LEDs and

Offline Button” on page 31.

Issue the CLI show chassis fpc command to check the status of installed FPCs.

As shown in the sample output, the value Online in the column labeled State indicates that the FPC is functioning normally: user@host> show chassis fpc

Slot State

0 Online

1 Online

2 Empty

3 Online

4 Empty

5 Online

6 Online

7 Empty

Temp CPU Utilization (%)

Memory Utilization (%)

DRAM (MB) Heap Buffer

For more detailed output, add the detail option. The following example also specifies a slot number ( 0 ), which is optional: user@host> show chassis fpc detail 0

Slot 0 information:

State

Temperature

Total CPU DRAM

Total SRAM

Total SDRAM

Online

37 degrees C / 98 degrees F

32 MB

4 MB

256 MB

I/O Manager ASIC information Version 2.0, Foundry IBM, Part number 0

I/O Manager ASIC information

Version 2.0, Foundry IBM, Part number 0

I/O Manager ASIC information

Start time:

Uptime:

Version 2.0, Foundry IBM, Part number 0

2003-04-29 16:11:55 PDT

5 days, 21 hours, 32 minutes, 41 seconds

For further description of the output from the commands, see the JUNOS

Internet Software Operational Mode Command Reference: Protocols, Class of

Service, Chassis, and Management .

Maintaining Packet Forwarding Engine Components 133

M160 Internet Router Hardware Guide

Maintaining PICs and PIC Cables

To maintain PICs and PIC cables, follow these guidelines:

Check the LEDs on PIC faceplates. Most PIC faceplates have an LED labeled

STATUS . Some PICs have additional LEDs, often one per port. The meaning of the LED states differs for various PICs. For more information, see the M160

Internet Router PIC Guide . If the FPC that houses the PIC detects a PIC failure, the FPC generates an alarm message to be sent to the Routing Engine.

Issue the CLI show chassis fpc pic-status command. The PIC slots in an FPC are numbered from 0 through 3 , top to bottom: user@host> show chassis fpc pic-status

Slot 0 Online

PIC 0 4x OC-3 SONET, MM

PIC 1

PIC 3

1x CSTM1, SMIR

2x OC-3 ATM, MM

Slot 1 Online

PIC 0 1x OC-12 SONET, MM

PIC 1

PIC 2

PIC 3

1x OC-12 ATM, MM

2x OC-3 ATM, MM

For further description of the output from the command, see the JUNOS

Protocols, Class of Service, and System Basics Command Reference .

Use the cable management system (shown in Figure 21) to support cables and prevent cables from dislodging or developing stress points.

Place excess cable out of the way in the cable management system. Do not allow fastened loops of cable to dangle from the connector or cable management system, because this stresses the cable at the fastening point.

Putting fasteners on the loops helps to maintain their shape.

Keep the cable connections clean and free of dust and other particles, which can cause drops in the received power level. Always inspect cables and clean them if necessary before connecting an interface.

Label both ends of PIC cables to identify them.

134 Maintaining Packet Forwarding Engine Components

Maintaining Hardware Components

The following guidelines apply specifically to fiber-optic cable:

When you unplug a fiber-optic cable from a PIC, always place a rubber safety plug over the transceiver on the PIC faceplate and on the end of the cable.

Anchor fiber-optic cable to avoid stress on the connectors. When attaching fiber to a PIC, be sure to secure the fiber so it is not supporting its own weight as it hangs to the floor. Never let fiber-optic cable hang free from the connector.

Avoid bending fiber-optic cable beyond its bend radius. An arc smaller than a few inches can damage the cable and cause problems that are difficult to diagnose.

Frequent plugging and unplugging of fiber-optic cable into and out of optical instruments, such as ATM or SONET/SDH analyzers, can cause damage to the instruments that is expensive to repair. Instead, attach a short fiber extension to the optical equipment. Any wear and tear due to frequent plugging and unplugging is then absorbed by the short fiber extension, which is easy and inexpensive to replace.

Keep fiber-optic cable connections clean. Small micro-deposits of oil and dust in the canal of the transceiver or cable connector could cause loss of light, reducing signal power and possibly causing intermittent problems with the optical connection.

To clean the transceivers, use an appropriate fiber-cleaning device, such as

RIFOCS Fiber Optic Adaptor Cleaning Wands (part number 946). Follow the directions for the cleaning kit you use.

After you have cleaned the transceiver on the fiber-optic PIC, make sure that the connector tip of the fiber-optic cable is clean. Use only an approved alcohol-free fiber-optic cable cleaning kit, such as the Opptex Cletop-S® Fiber

Cleaner. Follow the directions for the cleaning kit you use.

Maintaining the PCGs

The router has two Packet Forwarding Engine Clock Generators (PCGs) installed in the slots labeled PCG 0 and PCG 1 on the rear of the chassis, as shown in Figure 3.

To maintain the PCGs, perform the following procedures regularly:

Check the LEDs on the PCG faceplates. The green LED labeled OK lights steadily when the PCG is functioning normally. The blue LED labeled

MASTER lights steadily on the master PCG. For more information, see “PCG

Components” on page 19.

Issue the CLI show chassis environment pcg command to check the status of the PCGs. As shown in the sample output, the master PCG is designated

Online - Master clock and the standby PCG Online - Standby : user@host> show chassis environment pcg

PCG 0 status:

Maintaining Packet Forwarding Engine Components 135

M160 Internet Router Hardware Guide

State

Temperature

Frequency:

Setting

Measurement

Power:

3.3 V

5.0 V bias

8.0 V bias

BUS Revision

PCG 1 status:

State

Temperature

Frequency:

Setting

Measurement

Power:

3.3 V

5.0 V bias

8.0 V bias

BUS Revision

Online Master clock

40 degrees C / 104 degrees F

125.00 MHz

125.01 MHz

3274 mV

4974 mV

8183 mV

Online - Standby

40 degrees C / 104 degrees F

125.00 MHz

125.03 MHz

3267 mV

4993 mV

8190 mV

For further description of the output from the command, see the JUNOS

Internet Software Operational Mode Command Reference: Protocols, Class of

Service, Chassis, and Management .

Maintaining SFMs

The router can have a Switching and Forwarding Module (SFM) in each of the slots labeled SFM 0 through SFM 3 at the rear of the chassis, as shown in Figure 3.

To maintain the SFMs, perform the following procedures regularly:

Check the LEDs on the SFM faceplates. The green LED labeled OK lights steadily when an SFM is functioning normally. For more information, see

“SFM Components” on page 20.

Issue the CLI show chassis sfm command to check the status of the SFMs. The following sample output is for a router with four SFMs installed: user@host> show chassis sfm

Slot State

0 Online

1 Online

2 Online

3 Online

Temp CPU Utilization (%)

Memory Utilization (%)

DRAM (MB) Heap Buffer

For more detailed output, add the detail option. The following example also specifies a slot number ( 1 ), which is optional: user@host> show chassis sfm detail 1

136 Maintaining Packet Forwarding Engine Components

Maintaining Hardware Components

Slot 1 information:

State

SPP Temperature

SPR Temperature

Total CPU DRAM

Total SSRAM

Internet Processor II

Start time:

Uptime:

Online

43 degrees C / 109 degrees F

64 MB

8 MB

Version 1, Foundry IBM, Part number 9

2003-04-29 16:12:26 PDT

5 days, 22 hours, 28 minutes, 26 seconds

Packet scheduling mode : Disabled

For further description of the output from the commands, see the JUNOS

Internet Software Operational Mode Command Reference: Protocols, Class of

Service, Chassis, and Management .

Maintaining Power Supplies

To verify that the power system is functioning normally, perform the following procedures regularly:

Check the LEDs on the faceplate of both power supplies. A power supply is functioning correctly when the green LED labeled CB ON is lit steadily

(indicating that the circuit breaker is switched on) and the blue LED labeled

OUTPUT OK is lit steadily (indicating that the supply is receiving power from the DC source).

If these LEDs are blinking or other LEDs are lit, there could be an error condition. For a summary of LED states, see “Power Supply” on page 36.

Issue the following CLI command to check the status of the power supplies.

The following example specifies a slot number ( 0 ), which is optional. As shown in the sample output, the value Online in the State column indicates that the power supply is operating normally: user@host> show chassis environment pem 0

PEM 0 status:

State

Temperature

DC input

DC Output

Load

Voltage:

48.0 V input

48.0 V fan supply

5.0 V bias

8.0 V bias

55059 mV

50181 mV

5032 mV

8224 mV

Online

Less than 40 percent

Maintaining Power Supplies 137

M160 Internet Router Hardware Guide

NOTE: The messages in the craft interface LCD and the output from CLI show commands refer to the power supply on the right as PEM 0 and the power supply on the left as PEM 1 .

For further description of the output from the command, see the JUNOS

Internet Software Operational Mode Command Reference: Protocols, Class of

Service, Chassis, and Management .

Check the red and yellow alarm LEDs and the LCD on the craft interface.

Power supply failure or removal triggers an alarm that causes one or both of the LEDs to light and an error message to appear on the LCD. You can display the associated error messages by issuing the following CLI command: user@host> show chassis alarms

For a list of possible alarm messages, see “Chassis and Interface Alarm

Messages” on page 209.

Verify that the power source has the proper current rating and that each power supply is connected to a separate power source.

Verify that the cable or cord connecting the power supply to the external power source is securely in place and that there is no moisture accumulating near the router.

Verify that the cable or cord from the power source to the router is not damaged. If the insulation is cracked or broken, replace the cable or cord immediately.

Verify that the power cables or cord do not touch or obstruct access to other router components, and that they do not drape where people could trip on them.

Verify that the air flow in and out of cooling system components is not obstructed.

138 Maintaining Power Supplies

Chapter 11 Replacing Hardware Components

Most of the router’s hardware components are field-replaceable units (FRUs), which means that you can remove and replace them yourself. When you need to replace a router component, contact your customer support or sales representative to order the field-replaceable unit (FRU) that contains the component. For instructions, see

“Contacting Customer Support and Returning Hardware” on page 255. For a list of the FRUs on the M160 router, see Field-Replaceable Units (FRUs) on page 4.

Tools and Parts Required on page 139

Replacing the CIP and Routing Engine Interface Port Cables on page 141

Replacing Cooling System Components on page 148

Replacing Host Module Components on page 159

Replacing Packet Forwarding Engine Components on page 169

Replacing Power System Components on page 193

Tools and Parts Required

To replace hardware components, you need the tools and parts listed in Table 24.

Tools and Parts Required 139

M160 Internet Router Hardware Guide

Table 24: Tools and Parts Required

Tool or part

Electrostatic bag or antistatic mat

Components

CIP

Craft interface

FPC

Front impeller assembly

MCS

PIC

PCG

Routing Engine

SFM

All Electrostatic discharge (ESD) grounding wrist strap

Flat-blade (–) screwdriver, 2.5 mm

Flat-blade screwdriver, approximately 1/4 in. (6 mm)

Phillips (+) screwdrivers, numbers

1 and 2

7/16-in. hexagonal-head external drive socket wrench, or nut driver, with a minimum of 30 lb-in.

(3.5 Nm) tightening torque

(See following note.)

Alarm relay contacts on CIP

Craft interface

Front impeller assembly

Air filter

CIP

Circuit breaker box

Craft interface

DC power cables (to remove protective shield over circuit breaker box)

Fan tray

Fuse (to remove rear lower impeller assembly)

Impeller assembly

PCG

PIC

Power supply

Routing Engine

SFM

Circuit breaker box (to remove or install power cables)

DC power cables

140 Tools and Parts Required

Replacing Hardware Components

Tool or part

Wire cutters

Rubber safety cap

Components

Alarm relay contacts on CIP

Fiber-optic PIC or PIC cable

CAUTION: Do not substitute a metric nut driver or wrench. A tool that does not fit the nuts exactly can damage them. If a 7/16-in. tool is not available, use pliers or an adjustable wrench.

Replacing the CIP and Routing Engine Interface Port Cables

The CIP is located to the left side of the FPC card cage, as shown in Figure 1. It houses the Routing Engine interface ports, which accept connections to external management and alarm-reporting devices.

The CIP is field-replaceable, but you must power off the router before removing or installing it. It weighs about 6.5 lb (3 kg). The cables and wire that connect to the

Routing Engine interface ports are hot-removable and hot-insertable.

To replace the CIP and cables connecting to the Routing Engine interface ports, perform the following procedures:

Removing the CIP on page 141

Installing the CIP on page 143

Replacing Connections to Routing Engine Interface Ports on page 145

Removing the CIP

To remove the CIP, follow this procedure (see Figure 64):

Place an electrostatic bag or antistatic mat on a flat, stable surface.

On the console or other management device connected to the master Routing

Engine, enter CLI operational mode and issue the following command to shut down the router software. (If two Routing Engines are installed, also issue the command on the backup Routing Engine.) user@host> request system halt

NOTE: Wait until a message appears on the console confirming that the operating system has halted.

Replacing the CIP and Routing Engine Interface Port Cables 141

M160 Internet Router Hardware Guide

For more information about the command, see the JUNOS Protocols, Class of

Service, and System Basics Command Reference .

Press the power switch for both power supplies to the OFF ( 0 ) position. The switches are on the circuit breaker box.

“Preventing Electrostatic Discharge Damage” on page 226.

Disconnect any external devices connected to the CIP. For instructions, see

“Replacing the Management Ethernet Cable” on page 146, “Replacing the

Console or Auxiliary Cable” on page 146, and “Replace Alarm Relay Wires” on page 147.

Using a Phillips screwdriver, loosen and remove the screw at each end of the

CIP faceplate.

Grasp the CIP and slide it out of the chassis. Place it in the electrostatic bag or on the antistatic mat.

CAUTION: Be sure to slide the CIP straight within the slot to avoid damaging the connector pins on the front of the midplane.

142 Replacing the CIP and Routing Engine Interface Port Cables

Figure 64: Removing the CIP

Replacing Hardware Components

Installing the CIP

To install the CIP, follow this procedure (see Figure 65):

Verify that the router is powered down.

Carefully insert the rear of the CIP into the guides at the top and bottom of the

CIP slot, which is located to the left of the FPC card cage.

NOTE: The components on the CIP are on the left side of the board, unlike the components of an FPC, which are on the right side. Verify that the components are on the left before inserting the CIP.

Slide the CIP into the chassis until it contacts the midplane.

Replacing the CIP and Routing Engine Interface Port Cables 143

M160 Internet Router Hardware Guide

CAUTION: Be sure to slide the CIP straight within the slot to avoid damaging the connector pins on the front of the midplane.

Using a Phillips screwdriver, tighten the screw at each end of the CIP faceplate.

Reattach an external management device to one of the Routing Engine ports on the CIP ( AUXILIARY , CONSOLE , or ETHERNET ). Also reattach alarm relay contacts if desired. For instructions, see “Replacing the Management Ethernet Cable” on page 146, “Replacing the Console or Auxiliary Cable” on page 146, and

“Replace Alarm Relay Wires” on page 147.

Power on the router and verify correct startup by performing the procedures in

“Powering On the Router” on page 119.

Figure 65: Installing the CIP

144 Replacing the CIP and Routing Engine Interface Port Cables

Replacing Hardware Components

Replacing Connections to Routing Engine Interface Ports

The ports on the CIP connect the Routing Engine to external management devices

(see Figure 66).

Figure 66: Routing Engine Interface Ports and Alarm Relay Contacts

HOST

ETHERNET

ACT

YEL=10Mb

GRN=100Mb

CONSOLE

AUXILIARY

BITS A

LINK

BITS B

LINK

RED ALARM

YELLOW

ALARM

CONSOLE

AUXILIARY

HOST

ETHERNET

ACT

YEL=10Mb

GRN=100Mb

Routing

Engine ports

BITS input ports

Alarm relay contacts

To replace the cables that connect to the ports, perform the procedures described in the following sections:

Replacing the Management Ethernet Cable on page 146

Replacing the CIP and Routing Engine Interface Port Cables 145

M160 Internet Router Hardware Guide

Replacing the Console or Auxiliary Cable on page 146

Replace Alarm Relay Wires on page 147

Replacing the Management Ethernet Cable

Interface Cable and Wire Specifications on page 74. Follow this procedure:

If a cable is already installed in the ETHERNET port for the relevant Routing

Engine, perform the following steps: a.

Press the tab on the connector and pull the connector straight out of the port. Figure 67 shows the connector.

Disconnect the cable from the network device.

Plug one end of the replacement Ethernet cable into the appropriate ETHERNET port. Figure 66 shows the external device ports on the CIP. The ports labeled

HOST 0 connect to the Routing Engine in the upper Routing Engine slot ( RE

0 ), and the ports labeled HOST 1 connect to the Routing Engine in the lower

Routing Engine slot ( RE 1 ).

Plug the other end of the cable into the network device.

Figure 67: Ethernet Cable Connector

Replacing the Console or Auxiliary Cable

Engine Interface Cable and Wire Specifications on page 74.

To connect a management console or auxiliary device, follow this procedure:

If a cable is already installed in the CONSOLE or AUXILIARY port, perform the following steps: a.

Turn off the power to the console or auxiliary device.

146 Replacing the CIP and Routing Engine Interface Port Cables

Replacing Hardware Components

Unscrew the screws that secure the cable connector to the port, using a

2.5-mm flat-blade screwdriver if necessary.

Pull the cable connector straight out of the port.

Disconnect the cable from the console or auxiliary device.

Plug the female end of the replacement serial cable into the appropriate

CONSOLE or AUXILIARY port. Figure 66 shows the external device ports on the

CIP. The ports labeled HOST 0 connect to the Routing Engine in the upper

Routing Engine slot ( RE 0 ), and the ports labeled HOST 1 connect to the Routing

Engine in the lower Routing Engine slot ( RE 1 ).

Tighten the screws on the connector, using a 2.5-mm flat-blade screwdriver if necessary.

Power on the auxiliary or console device.

Figure 68: Serial Port Connector

Replace Alarm Relay Wires

The terminal blocks that plug into the alarm relay contacts are supplied with the router. They accept wire of any gauge between 24-AWG and

12-AWG (0.20 and 3.33 mm2), which is not provided. Use the gauge of wire appropriate for the external device you are connecting.

To replace the wires connecting to an alarm-reporting device, follow this procedure (see Figure 66:

Disconnect the existing wire at the external device.

Prepare the required length of replacement wire with gauge between 24-AWG and 12-AWG (0.20 and 3.33 mm2).

Using a 2.5 mm flat-blade screwdriver, loosen the small screws on the face of the terminal block and remove the block from the relay contact.

Using the 2.5 mm flat-blade screwdriver, loosen the small screws on the side of the terminal block. Remove existing wires from the slots in the front of the block and insert replacement wires. Tighten the screws to secure the wire.

Replacing the CIP and Routing Engine Interface Port Cables 147

M160 Internet Router Hardware Guide

Orient the terminal block according to the labels to the left of the appropriate relay contact ( NC means “normally closed,” C means “common,” and NO means “normally open”).

Plug the terminal block into the relay contact and use a 2.5 mm flat-blade screwdriver to tighten the screws on the face of the block.

Attach the other end of the wires to the external device.

Replacing Cooling System Components

For instructions on replacing cooling system components, see the following sections:

Replacing the Fan Tray on page 148

Replacing the Front Impeller Assembly on page 150

Replacing the Rear Lower Impeller Assembly on page 154

Replacing the Rear Upper Impeller Assembly on page 156

Replacing the Fan Tray

To replace the fan tray, perform the following procedures:

Removing the Fan Tray on page 148

Installing the Fan Tray on page 149

Removing the Fan Tray

The fan tray is located behind the cable management system on the front of the chassis, as shown in Figure 1. It weighs approximately 13 lb (5.9 kg).

To remove the fan tray, follow this procedure (see Figure 69):

Unwrap any PIC cables from the spools on the cable management system and remove the cables from the tray. Arrange the cables so that they do not block the front of the cable management system and tray, and secure them with temporary fasteners so that they are not supporting their own weight as they hang from the connector.

CAUTION: Do not let fiber-optic cable hang free from the connector. Do not allow fastened loops of cable to dangle, which stresses the cable at the fastening point.

148 Replacing Cooling System Components

Replacing Hardware Components

“Preventing Electrostatic Discharge Damage” on page 226.

Loosen the thumbscrew at each end of the fan tray, using a Phillips screwdriver if necessary.

Grasp the sides of the fan tray and pull firmly to slide it halfway out of the chassis.

CAUTION: To avoid injury, keep tools and your fingers away from the fans as you slide the fan tray out of the chassis. The fans might still be spinning.

Place one hand under the fan tray to support it and slide the tray completely out of the chassis after the fans stop spinning.

Figure 69: Removing the Fan Tray

Installing the Fan Tray

To install the fan tray, follow this procedure (see Figure 70):

CAUTION: When sliding the fan tray into the chassis, take care not to catch and pinch any dangling PIC cables with the edges of the tray. Also make sure your fingers are not near the fans, which start spinning as soon as the fan tray contacts the midplane.

Replacing Cooling System Components 149

M160 Internet Router Hardware Guide

“Preventing Electrostatic Discharge Damage” on page 226.

Grasp the sides of the fan tray and align the rear of the tray with the guides inside the chassis.

Slide the fan tray all the way into the chassis.

Tighten the thumbscrew at each end of the cable management system.

Rearrange the PIC cables in the cable management system. For more information about proper cable arrangement, see “Maintaining PICs and

PIC Cables” on page 134.

Figure 70: Installing the Fan Tray

Replacing the Front Impeller Assembly

The front impeller assembly, which includes the craft interface, is located at the front of the chassis above the FPC card cage, as shown in Figure 1. The assembly weighs approximately 14.5 lb (6.6 kg). The assembly is hot-removable and hot-insertable, as described in Field-Replaceable Units (FRUs) on page 4.

The craft interface is attached to the front of the front impeller assembly. If you are removing the front impeller assembly to replace it and the replacement assembly does not have a craft interface already installed on it, you must transfer the craft interface from the removed assembly to the replacement assembly. Perform the procedures described in the following sections:

Removing the Front Impeller Assembly on page 151

Removing the Craft Interface from the Front Impeller Assembly on page 152

150 Replacing Cooling System Components

Replacing Hardware Components

Installing the Craft Interface on the Front Impeller Assembly on page 153

Installing the Front Impeller Assembly on page 154

If the replacement front impeller assembly already has a craft interface on it, perform only the procedures in “Removing the Front Impeller Assembly” on page 151 and “Installing the Front Impeller Assembly” on page 154.

Removing the Front Impeller Assembly

To remove the front impeller assembly, follow this procedure (see Figure 71):

Place an electrostatic bag or antistatic mat on a flat, stable surface.

“Preventing Electrostatic Discharge Damage” on page 226.

Using a Phillips screwdriver, loosen the captive screw at each corner of the craft interface.

CAUTION: To avoid injury, as you slide the assembly out of the chassis do not touch any part of the impeller behind the front panel—the impeller might still be spinning.

Place one hand under the assembly to support it. When the impeller is no longer spinning, slide the assembly completely out of the chassis and place it on the antistatic mat or in the electrostatic bag.

If you are replacing the front impeller assembly and the replacement assembly has a craft interface panel installed on it, proceed to “Installing the Front

Impeller Assembly” on page 154. Otherwise, proceed to “Removing the Craft

Interface from the Front Impeller Assembly” on page 152.

Replacing Cooling System Components 151

M160 Internet Router Hardware Guide

Figure 71: Removing the Front Impeller Assembly

Captive screw

Removing the Craft Interface from the Front Impeller Assembly

If you are replacing the front impeller assembly and the replacement assembly does not have a craft interface panel on the front, you must transfer the craft interface from the removed assembly to the replacement assembly. To remove the craft interface from the removed impeller assembly, follow this procedure:

“Preventing Electrostatic Discharge Damage” on page 226.

Place the removed and replacement impeller assemblies top side up on antistatic mats.

If not immediately transferring the craft interface panel to the replacement assembly, place an antistatic mat or electrostatic bag on a flat, stable surface to receive it.

Using a Phillips screwdriver, remove the screws from the three semicircular metal tabs on the back of the craft interface that secure it to the impeller assembly (see Figure 72). Save the screws.

Grasp the ends of the craft interface, pull upward to release the hooks on the back of it from the windows on the front of the impeller assembly, then pull it toward you to free the craft interface completely (see Figure 73). If not immediately transferring it to a replacement impeller assembly, place it in the electrostatic bag or on the antistatic mat.

152 Replacing Cooling System Components

Replacing Hardware Components

Figure 72: Removing the Screws along the Top Front Edge of the Front Impeller Assembly

Top Down View

Upper impeller

Screws

Craft interface

Figure 73: Removing the Craft Interface

Hook Window

Installing the Craft Interface on the Front Impeller Assembly

To attach the craft interface to the front impeller assembly, follow this procedure:

“Preventing Electrostatic Discharge Damage” on page 226.

Place the replacement impeller assembly top side up on an antistatic mat on a flat, stable surface.

Replacing Cooling System Components 153

M160 Internet Router Hardware Guide

Attach the craft interface to the front of the impeller assembly, making sure that the hooks on the back of the craft interface clip securely into the windows on the front of the impeller assembly (see Figure 73).

Align the holes in the three semicircular metal tabs on the back of the craft interface with the corresponding holes in the top of the impeller assembly.

Insert the screws you saved when removing the craft interface into the three holes and tighten using a Phillips screwdriver (see Figure 72).

Installing the Front Impeller Assembly

To install the front impeller assembly, follow this procedure (see Figure 74):

“Preventing Electrostatic Discharge Damage” on page 226.

Grasp the sides of the impeller assembly and align the rear of the assembly with the guides inside the chassis.

Slide the impeller assembly all the way into the chassis.

Using a Phillips screwdriver, tighten the captive screw at each corner of the craft interface.

Figure 74: Installing the Front Impeller Assembly

Captive screw

Replacing the Rear Lower Impeller Assembly

The rear lower impeller assembly is located at the lower left of the rear of the chassis, above the left power supply, as shown in Figure 2. It weighs about 4 lb

(1.8 kg).

154 Replacing Cooling System Components

Replacing Hardware Components

The assembly is hot-removable and hot-insertable, as described in Field-Replaceable

Units (FRUs) on page 4. To replace it, perform the following procedures:

Removing the Rear Lower Impeller Assembly on page 155

Installing the Rear Lower Impeller Assembly on page 155

Removing the Rear Lower Impeller Assembly

To remove the rear lower impeller assembly, follow this procedure (see Figure 75):

“Preventing Electrostatic Discharge Damage” on page 226.

Loosen the thumbscrew at each corner of the impeller cover, using a Phillips screwdriver if necessary.

Grasp the thumbscrews at opposite corners of the impeller cover and slide the assembly halfway out of the chassis.

CAUTION: To avoid injury, as you slide the assembly out of the chassis do not touch any part of the impeller behind the front panel—the impeller might still be spinning.

When the impeller is no longer spinning, slide the assembly completely out of the chassis.

Figure 75: Removing the Rear Lower Impeller Assembly

Installing the Rear Lower Impeller Assembly

To install the rear lower impeller assembly, follow this procedure (see Figure 76:

Replacing Cooling System Components 155

M160 Internet Router Hardware Guide

“Preventing Electrostatic Discharge Damage” on page 226.

Orient the impeller so that the label is on the top. Align the rails on the upper edges of the impeller assembly with the guides inside the chassis.

Push the impeller assembly up and to the right to start it into the chassis, then slide it all the way in.

Tighten the thumbscrew at each corner of the impeller cover.

Figure 76: Installing the Rear Lower Impeller Assembly

Label

Guides

Rails

Replacing the Rear Upper Impeller Assembly

The rear upper impeller assembly is located at the upper left of the rear of the chassis, as shown in Figure 2. It weighs about 4 lb (1.8 kg).

The assembly is hot-removable and hot-insertable, as described in Field-Replaceable

Units (FRUs) on page 4. To replace it, perform the following procedures:

Removing the Rear Upper Impeller Assembly on page 157

Installing the Rear Upper Impeller Assembly on page 158

156 Replacing Cooling System Components

Replacing Hardware Components

Removing the Rear Upper Impeller Assembly

To remove the rear upper impeller assembly, follow this procedure (see Figure 77 and Figure 78, which show the two types of impeller that can be installed):

“Preventing Electrostatic Discharge Damage” on page 226.

Loosen the thumbscrew at each corner of the impeller cover, using a Phillips screwdriver if necessary.

Grasp the thumbscrews at opposite corners of the impeller cover and slide the assembly halfway out of the chassis.

CAUTION: To avoid injury, as you slide the assembly out of the chassis do not touch any part of the impeller behind the front panel—the impeller might still be spinning.

When the impeller is no longer spinning, slide the assembly completely out of the chassis.

Figure 77: Removing the Rear Upper Impeller Assembly

Replacing Cooling System Components 157

M160 Internet Router Hardware Guide

Figure 78: Removing the Rear Upper Impeller Assembly

Installing the Rear Upper Impeller Assembly

To install the rear upper impeller assembly, follow this procedure (see Figure 79 and Figure 80, which show the two types of impeller that can be installed):

“Preventing Electrostatic Discharge Damage” on page 226.

Slide the assembly all the way into the chassis.

Tighten the thumbscrew at each corner of the impeller cover.

Figure 79: Installing the Rear Upper Impeller Assembly

158 Replacing Cooling System Components

Figure 80: Installing the Rear Upper Impeller Assembly

Replacing Hardware Components

Replacing Host Module Components

For instructions on replacing host module components, see the following sections:

Replacing an MCS on page 159

Removing and Insert the PC Card on page 163

Replacing a Routing Engine on page 165

Replacing an MCS

The MCSs are hot-pluggable, as described in Field-Replaceable Units (FRUs) on page

4. For a description of the effect of removing an MCS, see Host Module on page 22.

To replace an MCS, perform the following procedures:

Removing an MCS on page 159

Installing an MCS on page 161

Removing an MCS

To remove an MCS, follow this procedure (see Figure 81):

Place an electrostatic bag or antistatic mat on a flat, stable surface.

“Preventing Electrostatic Discharge Damage” on page 226.

Replacing Host Module Components 159

M160 Internet Router Hardware Guide

Remove the rear component cover by loosening the thumbscrew at each corner of the cover and pulling it straight off the chassis. For complete instructions, see “Removing the Rear Component Cover” on page 86.

If two host modules are installed, use one of the following two methods to determine which is functioning as master:

Note which of the green host module MASTER LEDs is lit on the craft interface.

Issue the following CLI command. The master Routing Engine is designated Master in the Current state field: user@host> show chassis routing-engine

Routing Engine status:

Slot 0:

Current state

...

Master

If the component you are removing belongs to the master host module and a second host module is installed, issue the following CLI command to switch mastership to the standby host module: user@host> request chassis routing-engine master switch

If the Routing Engines are running JUNOS Release 6.0 or later and are configured for graceful switchover, the standby Routing Engine immediately assumes Routing Engine functions and there is no interruption to packet forwarding. Otherwise, packet forwarding halts while the standby Routing

Engine becomes the master and the Packet Forwarding Engine components reset and connect to the new master Routing Engine. For information about configuring graceful switchover, see the section about Routing Engine redundancy in the JUNOS System Basics Configuration Guide .

NOTE: Router performance might change if the standby Routing Engine’s configuration differs from the former master’s configuration. For the most predictable performance, configure the two Routing Engines identically, except for parameters unique to a Routing Engine, such as the hostname defined at the

[edit system] hierarchy level and the management interface ( fxp0 or equivalent) defined at the [edit interfaces] hierarchy level.

To configure Routing Engine-specific parameters and still use the same configuration on both Routing Engines, include the appropriate configuration statements under the re0 and re1 statements at the [edit groups] hierarchy level and use the apply-groups statement. For instructions, see the JUNOS System Basics Configuration Guide .

160 Replacing Host Module Components

Replacing Hardware Components

On the console or other management device connected to the Routing Engine that is paired with the CB you are removing, enter CLI operational mode and issue the following command. The command shuts down the Routing Engine cleanly, so its state information is preserved: user@host> request system halt

NOTE: Wait until a message appears on the console confirming that the operating system has halted.

For more information about the command, see the JUNOS Protocols, Class of

Service, and System Basics Command Reference .

Push the end of each extractor clip (located at each end of the MCS) outward.

Grasp the extractor clips and slide the MCS about halfway out of the chassis.

Place one hand under the MCS to support it, slide it completely out of the chassis, and place it on the antistatic mat or in the electrostatic bag.

Figure 81: Removing an MCS

SFM 0

SFM 1

MCS 0

RE 0

PCG 0

Extractor clip

Installing an MCS

To install an MCS, follow this procedure (see Figure 82):

“Preventing Electrostatic Discharge Damage” on page 226.

Replacing Host Module Components 161

M160 Internet Router Hardware Guide

Place one hand under the MCS to support it and grasp one of the extractor clips on the faceplate with the other hand.

Align the rear of the MCS with the guides inside the chassis and slide it in completely.

Press the extractor clip at each end of the MCS inward.

Verify that the green LED labeled OK on the MCS faceplate is lit. Also check the host module LEDs on the craft interface to verify that the green LED labeled ONLINE is lit for the host module to which the MCS belongs (Figure 11 shows the LEDs).

You can also verify correct MCS functioning by issuing the show chassis environment mcs command described in Maintaining Host Module

Components on page 131.

Reinstall the rear component cover and tighten the thumbscrew at each corner to secure it to the chassis. For complete instructions, see “Reinstalling the Rear

Component Cover” on page 109.

CAUTION: To maintain proper airflow and provide electromagnetic shielding, do not operate the router without the rear component cover in place.

Figure 82: Installing an MCS

SFM 0

SFM 1

MSC 0

RE 0

PCG 0

Extractor clip

162 Replacing Host Module Components

Replacing Hardware Components

Removing and Insert the PC Card

The slot labeled PC CARD on the Routing Engine faceplate 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 Internet software. The PC card can be used to copy JUNOS software from the PC card onto the Routing Engine. You can also copy JUNOS software 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 Internet software.

NOTE: The appearance and position of electronic components or the PC card slot on your Routing Engine might differ from the figures in this section. These differences do not affect Routing Engine installation and removal or functionality.

NOTE: The software on a PCMCIA card is loaded only onto the Routing Engine into which the PCMCIA card is inserted. It is not automatically copied to the other Routing Engine.

To remove and insert a PC card, perform the following procedures:

Removing the PC Card on page 163

Insert the PC Card on page 164

Removing the PC Card

The PC card is inserted in the slot labeled PC CARD in the Routing Engine faceplate.

To remove the PC card, follow this procedure (see Figure 83):

Press the eject button located next to the PC card slot in the Routing Engine faceplate. Note that the PC card slot might be located in a different position from that shown in Figure 83.

When the PC card pops partially out of the slot, grasp the card and pull it straight out of the slot.

Replacing Host Module Components 163

M160 Internet Router Hardware Guide

Figure 83: Removing the PC Card

SFM 0

SFM 1

MCS 0

RE 0

PCG 0

Eject button

Insert the PC Card

To insert the PC card, follow this procedure (see Figure 84):

Orient the PC card with the Juniper Networks logo facing in the direction specified on the Routing Engine faceplate. Insert the card into the slot.

Press the card firmly all the way into the slot. Note that the PC card slot might be located in a different position from that shown in Figure 84.

Reinstall the rear component cover and tighten the thumbscrew at each corner to secure it to the chassis. For complete instructions, see “Reinstalling the Rear

Component Cover” on page 109.

CAUTION: To maintain proper airflow and provide electromagnetic shielding, do not operate the router without the rear component cover in place.

164 Replacing Host Module Components

Replacing Hardware Components

Figure 84: Insert the PC Card

SFM 0

SFM 1

MCS 0

RE 0

PCG 0

Replacing a Routing Engine

The Routing Engines are hot-pluggable, as described in Field-Replaceable Units

(FRUs) on page 4. For a description of the effect of removing a Routing Engine, see Host Module on page 22. To replace a Routing Engine, perform the following procedures:

Removing a Routing Engine on page 165

Installing a Routing Engine on page 168

Removing a Routing Engine

To remove a Routing Engine, follow this procedure (see Figure 85):

Place an electrostatic bag or antistatic mat on a flat, stable surface.

“Preventing Electrostatic Discharge Damage” on page 226.

If two host modules are installed, use one of the following two methods to determine which is functioning as master:

Note which of the green host module MASTER LEDs is lit on the craft interface.

Replacing Host Module Components 165

M160 Internet Router Hardware Guide

Issue the following CLI command. The master Routing Engine is designated Master in the Current state field: user@host> show chassis routing-engine

Routing Engine status:

Slot 0:

Current state

...

Master

[edit system] hierarchy level and the management interface ( fxp0 or equivalent) defined at the [edit interfaces] hierarchy level.

On the console or other management device connected to the Routing

Engine you are removing, enter CLI operational mode and issue the following command. The command shuts down the Routing Engine cleanly, so its state information is preserved: user@host> request system halt

166 Replacing Host Module Components

Replacing Hardware Components

NOTE: Wait until a message appears on the console confirming that the operating system has halted.

For more information about the command, see the JUNOS Protocols, Class of

Service, and System Basics Command Reference .

Using your thumbs, push and hold the red tab on each extractor clip toward the outer edge of the unit. Push the ends of the extractor clips outward to unseat the Routing Engine from the chassis.

Grasp the extractor clips and slide the unit about halfway out of the chassis.

CAUTION: Slide the Routing Engine straight out of the chassis. Damage can result if it gets lodged because of uneven movement.

Place one hand under the Routing Engine to support it, slide it completely out of the chassis, and place it on the antistatic mat or in the electrostatic bag.

Figure 85: Removing a Routing Engine

SFM 0

SFM 1

MCS 0

RE 0

RE 1

PCG 0

PCG 1

Extractor clip

Replacing Host Module Components 167

M160 Internet Router Hardware Guide

Installing a Routing Engine

NOTE: If two Routing Engines are installed, they must both be the same version.

To install a Routing Engine, follow this procedure (see Figure 86):

“Preventing Electrostatic Discharge Damage” on page 226.

Place one hand under the Routing Engine to support it and grasp one of the extractor clips on the faceplate with the other hand.

Align the rear of the Routing Engine with the guide rails inside the chassis and slide it in completely.

CAUTION: Align the Routing Engine carefully with the guide rails and push it in evenly. Damage can result if it gets lodged in the rails because of uneven movement.

Press the extractor clip at each end of the Routing Engine inward to seat the unit firmly in the chassis.

Check the host module LEDs on the craft interface to verify that the green

LED labeled ONLINE is lit for the host module to which the Routing Engine belongs (Figure 11 shows the LEDs).

You can also verify correct Routing Engine functioning by issuing the show chassis routing-engine command described in Maintaining Host Module

Components on page 131.

Reinstall the rear component cover and tighten the thumbscrew at each corner to secure it to the chassis. For complete instructions, see “Reinstalling the Rear

Component Cover” on page 109.

CAUTION: To maintain proper airflow and provide electromagnetic shielding, do not operate the router without the rear component cover in place.

168 Replacing Host Module Components

Replacing Hardware Components

Figure 86: Installing a Routing Engine

SFM 0

SFM 1

MCS 0

RE 0

RE 1

PCG 0

PCG 1

Extractor clip

Replacing Packet Forwarding Engine Components

For instructions on replacing Packet Forwarding Engine components, see the following sections:

Replacing an FPC on page 169

Replacing a PCG on page 176

Replacing a PIC on page 179

Replace PIC Cables on page 185

Replacing an SFM on page 188

Replace an SFP on page 190

Replacing an FPC

FPCs are hot-removable and hot-insertable, as described in Field-Replaceable

Units (FRUs) on page 4. When you remove an FPC, forwarding operations halt for about 200 ms while the Packet Forwarding Engine flushes the shared memory buffers on the remaining FPCs.

To replace an FPC, perform the following procedures:

Removing an FPC on page 170

Replacing Packet Forwarding Engine Components 169

M160 Internet Router Hardware Guide

Installing an FPC on page 172

Removing an FPC

To remove an FPC, follow this procedure (see Figure 87):

Place an antistatic mat on a flat, stable surface to receive the FPC. If you are removing PICs from the FPC, prepare an antistatic mat or electrostatic bag for each one. If any of the PICs on the FPC use fiber-optic cable, have ready a rubber safety cap for each transceiver and cable.

“Preventing Electrostatic Discharge Damage” on page 226.

Label the cables connected to each PIC on the FPC so that you can later reconnect the cables to the correct PICs.

Use one of the following methods to take the FPC offline:

Press and hold the FPC offline button. The green OK LED next to the button begins to blink. Hold the button down until the LED goes out.

The LEDS and offline button for each FPC are located directly above it on the craft interface.

Issue the following CLI command: user@host>request chassis fpc slot slot-number offline

For more information about the command, see the JUNOS Internet Software

Operational Mode Command Reference: Protocols, Class of Service, Chassis, and Management .

Disconnect the cables from the PICs installed in the FPC. If a PIC uses fiber-optic cable, immediately cover each transceiver and the end of each cable with a rubber safety cap. Arrange the disconnected cables in the cable management system, to prevent the cables from developing stress points.

170 Replacing Packet Forwarding Engine Components

Replacing Hardware Components

CAUTION: Do not leave a fiber-optic transceiver uncovered except when inserting or removing cable. The safety cap keeps the port clean and prevents accidental exposure to laser light.

CAUTION: Avoid bending fiber-optic cable beyond its minimum bend radius. An arc smaller than a few inches in diameter can damage the cable and cause problems that are difficult to diagnose.

If you are transferring any PICs to a different FPC, follow this procedure to remove them while the FPC is still installed:

Unscrew the thumbscrews at the top and bottom of the PIC faceplate simultaneously and at about the same rate (unscrewing the two screws alternately or at very different rates can cause the PIC to become lodged in the FPC slot, making it difficult to turn the screws).

Slide the PIC out of the slot and immediately place it on an antistatic mat or in an electrostatic bag.

Loosen the thumbscrew at each end of the FPC, using a Phillips screwdriver if necessary.

Pull the ends of the ejector levers, which are adjacent to the thumbscrews, away from the face of the FPC until they are nearly perpendicular to it.

Grasp the top and bottom flanges of the card carrier and slide the FPC about halfway out of the card cage.

10.

CAUTION: The weight of the FPC is concentrated in the back end. Be prepared to accept the full weight—up to 29 lb (13.2 kg)—as you slide the FPC out of the chassis.

When the FPC is out of the chassis, do not hold it by the ejector levers, bus bars, or edge connectors. They cannot support its weight.

Do not stack FPCs on top of one another after removal. Place each one individually in an electrostatic bag or on its own antistatic mat on a flat, stable surface.

Replacing Packet Forwarding Engine Components 171

M160 Internet Router Hardware Guide

11.

If you are not reinstalling an FPC into the emptied FPC slot within a short time, install a blank FPC panel over the slot to maintain proper airflow in the FPC card cage.

CAUTION: After removing an FPC from the chassis, wait at least 30 seconds before reinserting it, removing an FPC from a different slot, or inserting an FPC into a different slot.

Figure 87: Removing an FPC

Offline button

Ejector levers

Installing an FPC

To install an FPC, follow this procedure (see Figure 88 and Figure 89):

Attach an electrostatic discharge (ESD) grounding strap to your bare wrist and connect the strap to one of the ESD points on the chassis. Make sure the router

172 Replacing Packet Forwarding Engine Components