Juniper Networks, Junos, Steel-Belted Radius, NetScreen, and ScreenOS are registered trademarks of Juniper Networks, Inc. in the United
States and other countries. The Juniper Networks Logo, the Junos logo, and JunosE are trademarks of Juniper Networks, Inc. All other
trademarks, service marks, registered trademarks, or registered service marks are the property of their respective owners.
Juniper Networks assumes no responsibility for any inaccuracies in this document. Juniper Networks reserves the right to change, modify,
transfer, or otherwise revise this publication without notice.
Products made or sold by Juniper Networks or components thereof might be covered by one or more of the following patents that are
owned by or licensed to Juniper Networks: U.S. Patent Nos. 5,473,599, 5,905,725, 5,909,440, 6,192,051, 6,333,650, 6,359,479, 6,406,312,
6,429,706, 6,459,579, 6,493,347, 6,538,518, 6,538,899, 6,552,918, 6,567,902, 6,578,186, and 6,590,785.
Revision History
October 2010—Corporate rebranding. Minor edits.
August 2010—Corporate rebranding. Minor edits.
May 2010—ForJunos OS Release 10.2, added supportof theclock interfaceports onthe SONETclock generator(SCG). Addedthe three-phase
delta and wye AC power supplies. Updated the European Community EMC Declaration of Conformity. Updated the DC power supply
specifications.
November 2009—Updated the amber LED to yellow.
September 2009—Completed topic conversion.
10 April 2009— 530-021112-01 Revision 5. Added the Enhanced Scaling FPC2 (T640-FPC2-ES) and Enhanced Scaling FPC4-1P
(T640-FPC4-1P-ES).
6 February 2009— 530-021112-01 Revision 4. Added the Enhanced Scaling FPC1 (T640-FPC1-ES).
31 December2008— 530-021112-01 Revision 3.Added the 3-input240-A power supply in2–INPUTmode. Updated thepowerrequirements.
28 October 2008— 530-021112-01 Revision 2. Updated the failover description for power supplies, high availability information, compliance
statement for acoustic noise, procedure for replacing serial cables, the replacement schedule for air filters, the number of fans, and the
weight of the rear fan tray. Added the T640 Enhanced Scaling FPC3 (T640-FPC3-ES).
22 June 2007— 530-021112-01 Revision 1. Updated DC input voltage range. Updated clearance requirements. Updated procedures for
mounting hardware. Add first Junos OS Release for each FPC. Removed end-of-life control board.
20 October 2006— 530-017398-01 Revision 1. Added European Community EMC Declaration of Conformity.
28 June 2006—530-015180-01 Revision 3. Added Lithium battery compliance statement. Updated Product Reclamation and Recycling
statement. Updated power information for FPCs. Added the power requirements for FPC4. Updated how much torque to apply when
securing the cable to a DC power supply. Corrected thermal output specification.
13 April 2006—530-015180-01 Revision 2. Changed replacement procedures to reflect the fact that some Routing Engines might or might
not have retaining screws. Updated Junos OS Release recommendation for graceful switchover.
9 January 2006—530-015180-01 Revision 1. Added note about SIB version B. Added graphic of T640-SIB. Added Enhanced Scaling FPC4
and its SIB version B requirement. Corrected power supply input DC current rating.
26 September 2005—530-014306-01 Revision 1. Corrected figures and added power supply input description.
14 September 2005—530-011256-01 Revision 3. Corrected chassis figures and updated SIB content.
25 April 2005—530-011256-01 Revision 2. Updated DC power supply illustration.
01 April 2004—530-011256-01 Revision 1. General updates and cleanup.
30 June 2003—530-007306-01 Revision 3. Updated information and minor edits.
02 April 2002—530-007306-01 Revision 2.
03 December 2001—530-007306-01 Revision 1. First edition.
The information in this document is current as of the date listed in the revision history.
YEAR 2000 NOTICE
Juniper Networks hardware and software products are Year 2000 compliant. The Junos OS has no known time-related limitations through
the year 2038. However, the NTP application is known to have some difficulty in the year 2036.
READ THIS END USER LICENSE AGREEMENT (“AGREEMENT”) BEFORE DOWNLOADING, INSTALLING, OR USING THE SOFTWARE.
BY DOWNLOADING, INSTALLING, OR USING THE SOFTWARE OR OTHERWISE EXPRESSING YOUR AGREEMENT TO THE TERMS
CONTAINED HEREIN, YOU (AS CUSTOMER OR IF YOU ARE NOT THE CUSTOMER, AS A REPRESENTATIVE/AGENT AUTHORIZED TO
BIND THE CUSTOMER) CONSENT TO BE BOUND BY THISAGREEMENT. IF YOU DO NOT ORCANNOT AGREE TO THE TERMS CONTAINED
HEREIN, THEN (A) DO NOT DOWNLOAD, INSTALL, OR USE THE SOFTWARE, AND (B) YOU MAY CONTACT JUNIPER NETWORKS
REGARDING LICENSE TERMS.
1. The Parties. The parties to this Agreement are (i) Juniper Networks, Inc. (if the Customer’s principal office is located in the Americas) or
Juniper Networks (Cayman) Limited (ifthe Customer’sprincipal officeis located outsidethe Americas) (such applicable entitybeing referred
to herein as“Juniper”),and (ii) the person or organization thatoriginally purchased from Juniperor an authorized Juniperreseller the applicable
license(s) for use of the Software (“Customer”) (collectively, the “Parties”).
2. The Software. In this Agreement, “Software” means the program modules and features of the Juniper or Juniper-supplied software, for
which Customer has paid the applicable license or support fees to Juniper or an authorized Juniper reseller, or which was embedded by
Juniper in equipment which Customer purchased from Juniper or an authorized Juniper reseller. “Software” also includes updates, upgrades
and new releases of such software. “Embedded Software” means Software which Juniper has embedded in or loaded onto the Juniper
equipment and any updates, upgrades, additions or replacements which are subsequently embedded in or loaded onto the equipment.
3. License Grant. Subject to paymentof the applicable fees and thelimitations andrestrictions set forth herein, Juniper grants toCustomer
a non-exclusive and non-transferable license, without right to sublicense, to use the Software, in executable form only, subject to the
following use restrictions:
a. Customer shall use Embedded Software solely as embedded in, and for execution on, Juniper equipment originally purchased by
Customer from Juniper or an authorized Juniper reseller.
b. Customer shall use the Software on a single hardware chassis having a single processing unit, or as many chassis or processing units
for which Customer has paid the applicable license fees; provided, however, with respect to the Steel-Belted Radius or Odyssey Access
Client software only, Customer shall use such Software on a single computer containing a single physical random access memory space
and containing any number of processors. Use of the Steel-Belted Radius or IMS AAA software on multiple computers or virtual machines
(e.g., Solaris zones) requires multiple licenses, regardless of whether such computers or virtualizations are physically contained on a single
chassis.
c. Product purchase documents, paper or electronic user documentation, and/or the particular licenses purchased by Customer may
specify limitsto Customer’s useof the Software. Suchlimits may restrictuse to amaximum numberof seats, registered endpoints, concurrent
users, sessions, calls, connections, subscribers, clusters, nodes, realms, devices, links, ports or transactions, or require the purchase of
separate licenses to use particular features, functionalities, services, applications, operations, or capabilities, or provide throughput,
performance, configuration, bandwidth, interface, processing, temporal, or geographical limits. In addition, such limits may restrict the use
of the Software to managing certain kinds of networks or require the Software to be used only in conjunction with other specific Software.
Customer’s use of the Software shall be subject to all such limitations and purchase of all applicable licenses.
d. For any trial copy of the Software, Customer’s right to use the Software expires 30 days after download, installation or use of the
Software. Customer may operate the Software after the 30-day trial period only if Customer pays for a license to do so. Customer may not
extend or create an additional trial period by re-installing the Software after the 30-day trial period.
e. The Global Enterprise Edition of the Steel-Belted Radius software may be used by Customer only to manage access to Customer’s
enterprise network. Specifically, service provider customers are expressly prohibited from using the Global Enterprise Edition of the
Steel-Belted Radius software to support any commercial network access services.
The foregoing license is not transferable or assignable by Customer. No license is granted herein to any user who did not originally purchase
the applicable license(s) for the Software from Juniper or an authorized Juniper reseller.
4. Use Prohibitions. Notwithstanding the foregoing, the license provided herein does not permit the Customer to, and Customer agrees
not to and shall not: (a) modify, unbundle, reverse engineer, or create derivative works based on the Software; (b) make unauthorized
copies of the Software (except as necessary for backup purposes); (c) rent, sell, transfer, or grant any rights in and to any copy of the
Software,in any form, to any third party; (d) remove any proprietary notices,labels, or marks on or inany copyof the Software orany product
in which the Software is embedded; (e) distribute any copy of the Software to any third party, including as may be embedded in Juniper
equipment sold inthe secondhand market; (f)use any ‘locked’ orkey-restricted feature,function, service, application, operation, orcapability
without first purchasing the applicable license(s) and obtaining a valid key from Juniper, even if such feature, function, service, application,
operation, or capability is enabled without a key; (g) distribute any key for the Software provided by Juniper to any third party; (h) use the
Software in any manner that extends or is broader than the uses purchased by Customer from Juniper or an authorized Juniper reseller; (i)
use Embedded Software on non-Juniper equipment; (j) use Embedded Software (or make it available for use) on Juniper equipment that
the Customer did not originally purchase from Juniper or an authorized Juniper reseller; (k) disclose the results of testing or benchmarking
of the Software to any third party without the prior written consent of Juniper; or (l) use the Software in any manner other than as expressly
provided herein.
5. Audit. Customer shall maintain accurate records as necessary to verify compliance with this Agreement. Upon request by Juniper,
Customer shall furnish such records to Juniper and certify its compliance with this Agreement.
6. Confidentiality. The Parties agree that aspects of the Software and associated documentation are the confidential property of Juniper.
As such, Customer shall exercise all reasonable commercial efforts to maintain the Software and associated documentation in confidence,
which at a minimum includes restricting access to the Software to Customer employees and contractors having a need to use the Software
for Customer’s internal business purposes.
7. Ownership. Juniper and Juniper’s licensors, respectively, retain ownership of all right, title, and interest (including copyright) in and to
the Software, associated documentation, and all copies of the Software. Nothing in this Agreement constitutes a transfer or conveyance
of any right, title, or interest in the Software or associated documentation, or a sale of the Software, associated documentation, or copies
of the Software.
8. Warranty, Limitation of Liability, Disclaimer of Warranty. The warranty applicable to the Software shall be as set forth in the warranty
statementthat accompaniesthe Software (the“Warranty Statement”).Nothing inthis Agreement shallgive riseto any obligation to support
the Software. Support services may be purchased separately. Any such support shall be governed by a separate, written support services
agreement. TO THE MAXIMUM EXTENT PERMITTED BY LAW, JUNIPER SHALL NOT BE LIABLE FOR ANY LOST PROFITS, LOSS OF DATA,
OR COSTS ORPROCUREMENT OFSUBSTITUTE GOODSOR SERVICES,OR FORANY SPECIAL, INDIRECT, ORCONSEQUENTIAL DAMAGES
ARISING OUTOF THIS AGREEMENT,THE SOFTWARE,OR ANY JUNIPEROR JUNIPER-SUPPLIEDSOFTWARE. INNO EVENT SHALLJUNIPER
BE LIABLE FOR DAMAGES ARISING FROM UNAUTHORIZED OR IMPROPER USE OF ANY JUNIPER OR JUNIPER-SUPPLIED SOFTWARE.
EXCEPT AS EXPRESSLY PROVIDED IN THE WARRANTY STATEMENT TO THE EXTENT PERMITTED BY LAW, JUNIPER DISCLAIMS ANY
AND ALL WARRANTIES IN AND TO THE SOFTWARE (WHETHER EXPRESS, IMPLIED, STATUTORY, OR OTHERWISE), INCLUDING ANY
IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NONINFRINGEMENT. IN NO EVENT DOES
JUNIPER WARRANT THAT THE SOFTWARE, OR ANY EQUIPMENT OR NETWORK RUNNING THE SOFTWARE, WILL OPERATE WITHOUT
ERROR OR INTERRUPTION, OR WILL BE FREE OF VULNERABILITY TO INTRUSION OR ATTACK. In no event shall Juniper’s or its suppliers’
or licensors’ liability to Customer, whether in contract, tort (including negligence), breach of warranty, or otherwise, exceed the price paid
by Customer for the Software that gave rise to the claim, or if the Software is embedded in another Juniper product, the price paid by
Customer for such other product. Customer acknowledges and agrees that Juniper has set its prices and entered into this Agreement in
reliance upon the disclaimers of warranty and the limitations of liability set forth herein, that the same reflect an allocation of risk between
the Parties (including the risk that a contract remedy may fail of its essential purpose and cause consequential loss), and that the same
form an essential basis of the bargain between the Parties.
9. Termination. Any breach of this Agreement or failure by Customer to pay any applicable fees due shall result in automatic termination
of the license granted herein. Upon such termination, Customer shall destroy or return to Juniper all copies of the Software and related
documentation in Customer’s possession or control.
10. Taxes. All license fees payable under this agreement are exclusive of tax. Customer shall be responsible for paying Taxes arising from
the purchase of the license, or importation or use of the Software. If applicable, valid exemption documentation for each taxing jurisdiction
shall be provided to Juniper prior to invoicing, and Customer shall promptly notify Juniper if their exemption is revoked or modified. All
payments made by Customer shall be net of any applicable withholding tax. Customer will provide reasonable assistance to Juniper in
connection with such withholding taxes by promptly: providing Juniper with valid tax receipts and other required documentation showing
Customer’s payment of any withholding taxes; completing appropriate applications that would reduce the amount of withholding tax to
be paid; and notifying and assisting Juniper in any audit or tax proceeding related to transactions hereunder. Customer shall comply with
all applicable tax laws and regulations, and Customer will promptly pay or reimburse Juniper for all costs and damages related to any
liability incurred by Juniper as a result of Customer’s non-compliance or delay with its responsibilities herein. Customer’s obligations under
this Section shall survive termination or expiration of this Agreement.
11. Export. Customer agrees to comply with all applicable export laws and restrictions and regulations of any United States and any
applicable foreign agency or authority, and not to export or re-export the Software or any direct product thereof in violation of any such
restrictions, laws or regulations, or without all necessary approvals. Customer shall be liable for any such violations. The version of the
Software supplied to Customer may contain encryption or other capabilities restricting Customer’s ability to export the Software without
an export license.
12. Commercial Computer Software. The Software is “commercial computer software” and is provided with restricted rights. Use,
duplication, or disclosure by the United States government is subject to restrictions set forth in this Agreement and as provided in DFARS
227.7201 through 227.7202-4, FAR 12.212, FAR 27.405(b)(2), FAR 52.227-19, or FAR 52.227-14(ALT III) as applicable.
13. Interface Information. To the extent required by applicable law, and at Customer's written request, Juniper shall provide Customer
with the interface information needed to achieve interoperability between the Software and another independently created program, on
payment of applicable fee, if any. Customer shall observe strict obligations of confidentiality with respect to such information and shall use
such information in compliance with any applicable terms and conditions upon which Juniper makes such information available.
14. Third Party Software. Any licensor of Juniper whose software is embedded in the Software and any supplier of Juniperwhose products
or technology are embedded in (or services are accessed by) the Software shall be a third party beneficiary with respect to this Agreement,
and such licensor or vendor shall have the right to enforcethis Agreement inits own name as if it were Juniper. In addition, certain third party
software may be provided with the Software and is subject to the accompanying license(s), if any, of its respective owner(s). To the extent
portions of the Software are distributed under and subject to open source licenses obligating Juniper to make the source code for such
portions publicly available (such as the GNU General Public License (“GPL”) or the GNU Library General Public License (“LGPL”)), Juniper
will make such source code portions (including Juniper modifications, as appropriate) available upon request for a period of up to three
years from the date of distribution. Such request can be made in writing to Juniper Networks, Inc., 1194 N. Mathilda Ave., Sunnyvale, CA
94089, ATTN: General Counsel. You may obtain a copy of the GPL at http://www.gnu.org/licenses/gpl.html, and a copy of the LGPL
at http://www.gnu.org/licenses/lgpl.html .
15. Miscellaneous. This Agreement shall be governed by the laws of the State of California without reference to its conflicts of laws
principles. The provisions of the U.N. Convention for the International Sale of Goods shall not apply to this Agreement. For any disputes
arising under this Agreement, the Parties hereby consent to the personal and exclusive jurisdiction of, and venue in, the state and federal
courts within Santa Clara County, California. This Agreement constitutes the entire and sole agreement between Juniper and the Customer
with respect to the Software, and supersedes all prior and contemporaneous agreements relating to the Software, whether oral or written
(including any inconsistent terms contained in a purchase order), except that the terms of a separate written agreement executed by an
authorized Juniper representative and Customer shall govern to the extent such terms are inconsistent or conflict with terms contained
herein. No modification to this Agreement nor any waiver of any rights hereunder shall be effective unless expressly assented to in writing
by the party to be charged. If any portion of this Agreement is held invalid, the Parties agree that such invalidity shall not affect the validity
of the remainder of this Agreement. This Agreement and associated documentation has been written in the English language, and the
Parties agree that the English version will govern. (For Canada: Les parties aux présentés confirment leur volonté que cette convention de
même que tous les documents y compris tout avis qui s'y rattaché, soient redigés en langue anglaise. (Translation: The parties confirm that
this Agreement and all related documentation is and will be in the English language)).
General Safety Guidelines for M Series, MX Series, and T Series Routers . . 303
General Safety Warnings for M Series, MX Series, and T Series Routers . . . 304
Junos OS Documentation and Release Notes on page xxv
•
Objectives on page xxv
•
Audience on page xxvi
•
Documentation Conventions on page xxvi
•
Documentation Feedback on page xxvii
•
Requesting Technical Support on page xxviii
Junos OS Documentation and Release Notes
For a list of related Junos OS documentation, see
http://www.juniper.net/techpubs/software/junos/ .
If the information in the latest release notes differs from the information in the
documentation, follow the Junos OS Release Notes.
To obtain the most current version of all Juniper Networks®technical documentation,
see the product documentation page on the Juniper Networks website at
http://www.juniper.net/techpubs/.
Objectives
This documentation describes hardware components, installation, basic configuration,
and basic troubleshooting procedures for the Juniper Networks T640 Router. It explains
how to prepare your site for router installation, unpack and install the hardware, power
on the router, perform initial software configuration, and perform routine maintenance.
After completing the installation and basic configuration procedures covered in this
documentation, see the Junos OS configuration guides for information about further
Junos OS configuration.
NOTE: For additional information about Juniper Networks routers and the
Physical Interface Cards (PICs) they support—either corrections to or
informationthat mighthave been omitted from this guide—see the hardware
release notes at http://www.juniper.net/.
This documentation is designed for network administrators who are installing and
maintaining a Juniper Networks router or preparing a site for router installation. To use
the documentation, you need a broad understanding of networks in general, the Internet
in particular, networking principles, and network configuration. Any detailed discussion
of these concepts is beyond the scope of this hardware documentation.
Documentation Conventions
Table 1 on page xxvi defines the notice icons used in this guide.
Table 1: Notice Icons
DescriptionMeaningIcon
Indicates important features or instructions.Informational note
Table 2 on page xxvi defines the text and syntax conventions used in this guide.
Table 2: Text and Syntax Conventions
Represents text that you type.Bold text like this
Fixed-width text like this
Italic text like this
Represents output that appears on the
terminal screen.
•
Introduces important new terms.
•
Identifies book names.
•
Identifies RFC and Internet draft titles.
Indicates a situation that might result in loss of data or hardware damage.Caution
Alerts you to the risk of personal injury or death.Warning
Alerts you to the risk of personal injury from a laser.Laser warning
ExamplesDescriptionConvention
To enter configuration mode, type the
configure command:
user@host> configure
user@host> show chassis alarms
No alarms currently active
•
A policy term is a named structure
that defines match conditions and
actions.
Represents variables (options for which
you substitute a value) in commands or
configuration statements.
Represents names of configuration
statements, commands, files, and
directories; IP addresses; configuration
hierarchy levels; or labels on routing
platform components.
Indicates a choice betweenthe mutually
exclusivekeywords or variables on either
side of the symbol. The set of choices is
often enclosed in parentheses for clarity.
same lineas theconfiguration statement
to which it applies.
Enclose a variable for which you can
substitute one or more values.
Identify a level in the configuration
hierarchy.
Identifies a leaf statement at a
configuration hierarchy level.
Configure the machine’s domain name:
[edit]
root@# set system domain-name
domain-name
•
To configure a stub area, include the
stub statement at the [edit protocols
ospf area area-id] hierarchy level.
•
The console port is labeled CONSOLE.
stub <default-metric metric>;Enclose optional keywords or variables.< > (angle brackets)
broadcast | multicast
(string1 | string2 | string3)
rsvp { # Required for dynamic MPLS onlyIndicates a comment specified on the
community name members [
community-ids ]
[edit]
routing-options {
static {
route default{
nexthop address;
retain;
}
}
}
J-Web GUI Conventions
Bold text like this
> (bold right angle bracket)
Documentation Feedback
We encourage you to provide feedback, comments, and suggestions so that we can
improve the documentation. You can send your comments to
techpubs-comments@juniper.net, or fill out the documentation feedback form at
Represents J-Web graphical user
interface (GUI) items you click or select.
Separates levels in a hierarchy of J-Web
selections.
•
In the Logical Interfaces box, select
All Interfaces.
•
To cancel the configuration, click
Cancel.
In the configuration editor hierarchy,
select Protocols>Ospf.
https://www.juniper.net/cgi-bin/docbugreport/. If you are using e-mail, be sure to include
the following information with your comments:
•
Document or topic name
•
URL or page number
•
Software release version (if applicable)
Requesting Technical Support
Technical productsupport is available through the Juniper Networks Technical Assistance
Center (JTAC). If you are a customer with an active J-Care or JNASC support contract,
or are covered under warranty, and need post-sales technical support, you can access
our tools and resources online or open a case with JTAC.
•
JTAC policies—For a complete understanding of our JTAC procedures and policies,
review the JTAC User Guide located at
JTAC hours of operation—The JTAC centers have resources available 24 hours a day,
7 days a week, 365 days a year.
Self-Help Online Tools and Resources
For quick and easy problem resolution, Juniper Networks has designed an online
self-service portal called the Customer Support Center (CSC) that provides you with the
following features:
The T640 Core Router is a complete routing system that provides Gigabit Ethernet,
SONET/SDH, and other high-speed interfacesfor large networksand networkapplications,
such as those supported by Internet service providers (ISPs).
Application-specific integrated circuits (ASICs) are a definitive part of the router design;
these ASICs enable the router to achieve data forwarding rates that match current
fiber-optic capacity.
The router accommodates up to eight Flexible PIC Concentrators (FPCs), which can
each be configured with a variety of network media types—altogether providing up to
128 SONET/SDH OC48/STM16, 32 SONET/SDH OC192/STM64, or 128 Gigabit Ethernet
ports for the router. In a standalone configuration, the router's maximum aggregate
throughput is 320 Gbps, full duplex.
Related
Documentation
The router architecture cleanly separates control operations from packet forwarding
operations. This design eliminates processing and traffic bottlenecks, permitting the
router to achieve high performance. Control operations in the router are performed by
the host subsystem, whichruns Junos OS tohandle routingprotocols, traffic engineering,
policy, policing, monitoring, and configuration management. Forwarding operations in
the router are performed by the Packet Forwarding Engines, which consist of hardware,
including ASICs, designed by Juniper Networks.
The router is a modular, rack-mountable system. Two routers can be installed in one
standard, 78-in. telco rack.
T640 Chassis Description on page 13•
• T640 Physical Specifications on page 341
• T640 Environmental Specifications on page 343
• T640 DC Power System Electrical Specifications on page 347
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 off the router or disrupting the routing functions.
•
Hot-pluggableFRUs—You can removeand replace these componentswithout powering
down the router, but the routing functions of the system are interrupted when the
component is removed.
If the router contains a redundant host subsystem, the Control Board (T-CB), and the
Routing Engine are hot-removable and hot-insertable. Before you replace a T-CB or a
Routing Engine, you must take the host subsystem offline.
Related
Documentation
T640 FRU List
T640 Router Description on page 3•
• T640 FRU List on page 4
• Taking the T640 Host Subsystem Offline on page 198
Table 3 on page 4 lists the FRUs for the router.
Table 3: Field-Replaceable Units
Hot-Pluggable FRUsHot-Removable and Hot-Insertable FRUs
Air filters
Flexible PIC Concentrators (FPCs)
Front and rear fan trays
Physical Interface Cards (PICs)
Power supplies
Backup SONET Clock Generators (SCGs)
Switch Interface Boards (SIBs)
Master T-CB (if nonstop active routing is
configured)
Connector Interface Panel (CIP)
Nonredundant T-CB
Master T-CB (if nonstop active routing is not
configured)
Nonredundant Routing Engine
MasterRouting Engine(if nonstop active routing
is not configured)
• Taking the T640 Host Subsystem Offline on page 198
T640 Component Redundancy
The T640 Core Router is designed so that no single point of failure can cause the entire
system to fail. The following major hardware components are redundant:
•
Switch Interface Boards (SIBs)—The router has five SIBs. A T640 router that is
connected to a TX Matrix platform requires T640-SIBs ; see “T640 Switch Interface
Boards (SIBs) Description” on page 30) Each Type 1 FPC and Type 2 FPC has a
dedicated ASIC with five high-speed links that connect to the SIBs (one link per SIB).
Each Type 3 FPC has two dedicated ASICs, and each ASIC has five high-speed links
that connect to the SIBs (a total of 10 links). Each Type 4 FPC has one dedicated ASIC
with ten high-speed links that connect to the SIBs (two links per SIB). One of the five
SIBs—usually SIB4—acts as a backup to the remaining four SIBs. If a SIB fails, the
backup SIB becomes active and traffic forwarding continues without any degradation.
When the failed SIB is replaced, it becomes the new backup.
•
Host subsystem—The host subsystem consists ofa Routing Enginefunctioning together
with a T-CB. The router can have one or two host subsystems. If two host subsystems
are installed, one functions as the master and the other functions as the backup. If the
master host subsystem (or either of its components) fails, the backup can take over
as the master. To operate, each host subsystem requires a Routing Engine installed in
an adjacent slot to a T-CB.
Related
Documentation
If theRouting Enginesare configured for graceful switchover, thebackup Routing Engine
automatically synchronizes its configurationand state with the master Routing Engine.
Any update to the master Routing Engine state is replicated on the backup Routing
Engine. Ifthe backupRouting Engine assumes mastership, packet forwarding continues
through the router without interruption. For more information aboutgraceful switchover,
see the Junos OS System Basics Configuration Guide.
•
SONET Clock Generators (SCGs)—The router has a standard configuration of one
SCG. A second can be purchased to function as backup. If one SCG fails, the other
becomes the masterSCG.Mastershipof the SCGs isindependent of the host subsystem,
so routing functions are not affected.
•
Power supplies—The router has two power supplies, which share the load evenly. If
one power supply fails, the other power supply can provide full power to the router
indefinitely.
•
Cooling system—Thecooling system has redundantcomponents, whichare controlled
by the host subsystem. If one of the fans fails, the host subsystem increases the speed
of the remaining fans to provide sufficient cooling for the router indefinitely.
• T640 Router Description on page 3
• Reinstalling Components in the T640 Chassis on page 108
PacketForwardingEngines—Thesehigh-performance,ASIC-basedcomponents provide
Layer 2 and Layer 3 packet switching, route lookups, and packet forwarding.
Related
Documentation
The Routing Engine and the Packet Forwarding Engines perform their primary tasks
independently, although theyconstantly communicate through multiple 100-Mbps links.
This arrangement streamlines forwarding and routing control and runs Internet-scale
backbone networks at high speeds. Figure 1 on page 7 shows the relationship between
the Routing Engine and the Packet Forwarding Engines.
Figure 1: Router Architecture
T640 Chassis Description on page 13•
• Safety Requirements, Warnings, and Guidelines for Installing the T640 Router on
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 topof a kernel that interacts withthe Packet Forwarding Engine. For more information
about the processes, see the Junos OS System Basics and Services Command Reference.
The Routing Engine includes the functions and features:
•
Processing of routing protocol packets—The Routing Engine handles all packets that
concern routing protocols, freeing thePacketForwarding Engineto handle only packets
that represent Internet traffic.
•
Softwaremodularity—Becauseeach software process is devoted to a different function
and uses a separate process space, the failure of one process has little or no effect on
the others.
•
In-depth Internet functionality—Each routingprotocolis implemented with a complete
set ofInternet featuresand provides fullflexibility for advertising, filtering, and modifying
routes. Routing policies are set according to route parameters (for example, prefix,
prefix lengths, and 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 Junos OS can
efficiently support large numbers of interfaces and virtual circuits.
•
Management interface—Different levels of system management tools are provided,
including the Junos OS command-line interface (CLI), the Junos XML management
protocol, the craft interface, and SNMP.
•
Storage and change management—Configuration files,system images, andmicrocode
can be held and maintained in primary and secondary storage systems, permitting
local or remote upgrades.
•
Monitoring efficiency and flexibility—The router supports functions such as alarm
handling and packet counting on every port, without degrading packet-forwarding
performance.
The Routing Engine constructs and maintains one or more routing tables (see Figure 2
on page 9). 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.
Chapter 2: Overview of the T640 Router System Architecture
Figure 2: Control Packet Handling for Routing and Forwarding Table
Updates
Related
Documentation
Replacing a T640 Routing Engine on page 206•
• T640 Routing Engine Description on page 32
• Maintaining the T640 Routing Engines on page 148
T640 Packet Forwarding Engine Architecture
The Packet Forwarding Engines provide the Layer 2 and Layer 3 packet switching,
forwarding, and route lookup functions. In a maximum configuration with eight Type 3
FPCs installed, the Packet Forwarding Engines can forward up to 640 million packets
per second (Mpps) for all packet sizes. The maximum aggregate throughput rate for the
T640 router is 320 Gbps (full duplex). The Packet Forwarding Engines are implemented
in ASICs that are physically located on the FPCs and the PICs.
Each Packet Forwarding Engine consists of the following components (see Figure 3 on
page 10):
•
Layer 2/Layer 3 Packet Processing ASIC, which performs Layer 2 and Layer 3
encapsulation and de-encapsulation, and manages the division and reassembly of
packets within the T640 router.
•
Queuing and Memory Interface ASICs, which manage the buffering of data cells in
memory and the queueing of notifications.
•
T-series Internet Processor, which provides the route lookup function.
Related
Documentation
•
Switch Interface ASICs, which extract the route lookup key and manage the flow of
data cells across the switch fabric.
•
Media-specific ASICs on the PICs that perform control functions tailored to the PIC
media types.
• Replacing T640 Packet Forwarding Engine Components on page 219
Data Flow Through the T640 Router
To ensure the efficient movement of data through the T640 Core Router, the router is
designed so that ASICs on the hardware components handle the forwarding of data.
Data flows through the T640 router in the following sequence (see Figure 3 on page 10):
Figure 3: Data Flow Through the T640 Router
1. Packets arrive at an incoming PIC interface.
2. The PIC passes the packets to the FPC, where the Layer 2/Layer 3 Packet Processing
ASIC performs Layer 2 and Layer 3 parsing and divides the packets into 64-byte cells.
3. The Switch Interface ASIC extracts the route lookup key, places it in a notification and
passes the notification to the T-series Internet Processor. The Switch Interface ASIC
also passes the data cells to the Queuing and Memory Interface ASICs for buffering.
4. The Queuing and Memory InterfaceASICs pass the data cellsto memoryfor buffering.
5. The T-series Internet Processorperforms theroute lookup and forwards the notification
to the Queuing and Memory Interface ASIC.
6. TheQueuing andMemory Interface ASIC sends the notification to theSwitch Interface
ASIC facing the switch fabric, unless the destination is onthe samePacket Forwarding
Engine. In this case, the notification is sent back to the Switch Interface ASIC facing
Chapter 2: Overview of the T640 Router System Architecture
the outgoing ports, and the packets are sent to the outgoing port without passing
through the switch fabric (see Step 13).
7. The Switch Interface ASIC sends bandwidth requests through the switch fabric to the
destination port. The Switch Interface ASIC also issues read requests to the Queuing
and Memory Interface ASIC to begin reading data cells out of memory.
8. The destination Switch Interface ASIC sends bandwidth grants through the switch
fabric to the originating Switch Interface ASIC.
9. On receipt of each bandwidth grant, the originating Switch Interface ASIC sends a
cell through the switch fabric to the destination Packet Forwarding Engine.
10. The destination Switch Interface ASIC receives cells from the switch fabric. It extracts
the route lookup key from each cell, places it in a notification, and forwards the
notification to the T-series Internet Processor.
11. The T-series Internet Processor performs the route lookup, and forwards the
notification to the Queuing and Memory Interface ASIC.
12. The Queuing and Memory Interface ASIC forwardsthe notification, including next-hop
information, to the Switch Interface ASIC.
Related
Documentation
13. The Switch Interface ASIC sends read requests to the Queuing and Memory Interface
ASIC to read the data cells out of memory, and passes the cells to the Layer 2/Layer
3 Packet Processing ASIC.
14. The Layer 2/Layer 3 Packet Processing ASIC reassembles the data cells into packets,
adds Layer 2 encapsulation, and sends the packets to the outgoing PIC interface.
15. The outgoing PIC sends the packets out into the network.
• T640 Chassis Description on page 13
• T640 Physical Specifications on page 341
• Replacing T640 Packet Forwarding Engine Components on page 219
These topics provide an overview of the T640 router hardware components:
•
T640 Chassis Description on page 13
•
T640 Midplane Description on page 16
•
T640 Flexible PIC Concentrators (FPCs) Overview on page 18
•
T640 PIC Description on page 29
•
T640 Switch Interface Boards (SIBs) Description on page 30
•
T640 Host Subsystem Overview on page 32
•
T640 SONET Clock Generators (SCGs) Overview on page 40
•
T640 Craft Interface Overview on page 41
•
T640 Connector Interface Panel (CIP) Description on page 46
•
T640 Routing Engine Ports on page 47
•
T640 Alarm Relay Contacts on page 48
•
T640 Power System Overview on page 48
•
T640 Cooling System Description on page 61
•
T640 Cable Management System Description on page 62
T640 Chassis Description
The T640 Core Router chassis is a rigid sheet metal structure that houses all the other
router components (see Figure 4 on page 15 and Figure 5 on page 16). The chassis
measures 37.45 in. (95.1 cm) high, 31 in. (78.7 cm) deep, and 17.43 in. (44.3 cm) wide. For
physical specifications, see “T640 Physical Specifications” on page 341. The chassis can
be installed into many types of racks or cabinets. For more information. see “T640 Rack
Requirements” on page 66.
The chassis includes the following features (see Figure 4 on page 15 and Figure 5 on
page 16):
•
One pairof metal flanges for front-mounting ormounting ina four-post rack or cabinet.
Installation handles on each side to facilitate positioning the router in the rack. Do not
use the handles to lift the router.
Two electrostatic discharge (ESD) points (banana plug receptacles), one front and
one rear.
CAUTION: Before removing or installing components of a 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.
WARNING: The router must be connected to earth ground during normal
operation.
For chassis serial number information , see “Locating T640 Component Serial Numbers
Using the CLI” on page 369.
Related
Documentation
Safety Requirements, Warnings, and Guidelines for Installing the T640 Router on
•
page 85
• T640 Physical Specifications on page 341
• T640 Chassis Grounding Cable and Lug Specifications on page 345
• T640 Chassis Lifting Guidelines on page 310
T640 Midplane Description
The T640 Core Router midplane is located in the center of the chassis and forms the
rear of the FPC card cage (see Figure 6 on page 17). The FPCs install into the midplane
from the front of the chassis, and the SIBs, Routing Engines, control boards, and SCGs
install into the midplane from the rear of the chassis. The power supplies and cooling
system components also connect to the midplane.
The midplane performs the following major functions:
•
Data path—Data packets are transferred across the midplane from the Packet
Forwarding Engine on the originating FPC to the SIBs, and from the SIBs across the
midplane to the Packet Forwarding Engine on the destination FPC.
•
Power distribution—The router power supplies are connected to the midplane, which
distributes power to all the router components.
•
Signal path—The midplane providesthe signalpath to theFPCs, SIBs,Routing Engines,
and T-CBs, and other system components for monitoring and control of the system.
Figure 6: T640 Midplane
For chassis serial number information , see “Locating T640 Component Serial Numbers
Using the CLI” on page 369.
• Safety Requirements, Warnings, and Guidelines for Installing the T640 Router on
page 85
• T640 Physical Specifications on page 341
T640 Flexible PIC Concentrators (FPCs) Overview
•
T640 FPC Description on page 18
•
T640 FPCs Supported on page 28
T640 FPC Description
Up to eight Flexible PIC Concentrators (FPCs) install vertically in the front of the T640
Core Router (see Figure 7 on page 19). The FPC slots are numbered left to right from
FPC0 to FPC7. An FPC can be installed into any FPC slot on the router, regardless of which
PICs it contains.
If a slot is not occupied by an FPC, an FPC blank panel must be installed to shield the
empty slot and to allow cooling air to circulate properly through the router.
Each FPC contains oneor two Packet ForwardingEngines. ThePacketForwarding Engines
receive incoming packets from the PICs installed on the FPC and forward them through
the switch planes to the appropriate destination port. Each FPC contains data memory
that is managed by the Queuing and Memory Interface ASICs.
FPCs are hot-removable andhot-insertable, as describedin “T640 Router FRU Overview”
on page 4. 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 a T640 FPC” on page 219.
Each FPC consists of the following components:
•
FPC card carrier.
•
One ortwo Packet ForwardingEngines, consisting ofLayer2/Layer 3 Packet Processing
ASICs, Switch Interface ASICs, T-series Internet Processor ASICs, and a Memory
Mezzanine Board (MMB) which includes the Queuing and Memory Interface ASICs.
Each Type 1, Type 2, and Type 4 FPChas one Packet Forwarding Engine, and each Type
3 FPC has two Packet Forwarding Engines.
•
ProcessorMezzanine Board(PMB), which includes a 300-MHz CPU,system controller,
256 MB of SDRAM, and two Fast Ethernet interfaces.
•
Two LEDs, located on the craft interface above the FPC, that display the status of the
FPC. For more information about the FPC LEDs, see “T640 Craft Interface FPC LEDs
and Online/Offline Buttons” on page 45.
•
FPC online/offline button, located on the craft interface above the FPC.
Regardless of whether you are holding an FPC vertically or horizontally, this document
uses the same terms for all four edges of the FPC (see Figure 8 on page 20):
•
Faceplate—Edge of the FPC that has slots into which you insert the PICs
•
Connectoredge—Edge opposite the faceplate;this edgehas the connectorsthat attach
to the midplane
•
Top edge—Edge at the top of the FPC when it is vertical
•
Bottom edge—Edge at the bottom of the FPC when it is vertical
Check the label on the faceplate to identify the FPC. For FPCs without a label on the
faceplate, check the location of a PIC's offline button and how the PIC is secured to the
FPC. See Table 4 on page 20.
Table 4: Identifying the FPCs Supported by the T640 Router
Location of PIC Offline
ButtonLabelon theFPC FaceplateFPC
• T640 Craft Interface FPC LEDs and Online/Offline Buttons on page 45
• Troubleshooting the T640 FPCs on page 169
T640 PIC Description
PICs provide the physical connection to various network media types,receiving incoming
packets from the network and transmitting outgoing packets to the network. During this
process, each PIC performs framing and line-speed signaling for its media type. Before
transmitting outgoing data packets, the PICs encapsulate the packets received from the
FPCs. Each PIC is equipped with an ASIC that performs control functions specific to the
media type of that PIC.
PICs are hot-removable and hot-insertable. You can install up to four PICs in the slots
of each Type 1, 2, and 3 FPC, and one PIC in a Type 4 FPC. Type 1 and Type 2 PICs have
captive screws at theirupper and lower corners. Type 3 PICs have an upper ejector handle
and a lower captive screw. Type 4 PICs have an upper ejector handle and a lower ejector
handle.
The router supportsvarious PICs,including ATM, Channelized, GigabitEthernet, IPServices,
and SONET/SDH interfaces. Blank PICs resemble other PICs but do not provide any
physical connection or activity. When a slot is not occupied by a PIC, you must insert a
blank PIC to fill the empty slot and ensure proper cooling of the system.
Related
Documentation
T640 PICs Supported•
• T640 End-of-Life PICs Supported
T640 Switch Interface Boards (SIBs) Description
The Switch Interface Boards (SIBs) provide the switching function to the destination
FPC (see Figure 16 on page 31).
The SIBs create the switch fabric for the router, providing up to a total of 640 million
packets per second (Mpps) of forwarding. Five SIBs are installed in the router. The SIBs
are located at the center rear of the chassis in the slots labeled SIB0 through SIB4 (top
to bottom).
SIBs are hot-insertable and hot-removable.
Each Type 1 FPC and Type 2 FPC has a dedicated ASIC with five high-speed links that
connect to the SIBs (one link per SIB). Each Type 3 FPC has two dedicated ASICs, and
each ASIC has five high-speed links that connect to the SIBs (a total of 10 links). Each
Type 4 FPC has one dedicated ASIC with ten high-speed links that connect to the SIBs
(two links per SIB).One of the five SIBs—usually SIB4—acts as abackup tothe remaining
four SIBs. If a SIB fails, the backup SIB becomes active and traffic forwarding continues
without any degradation. When the failed SIB is replaced, it becomes the new backup.
The T640 router supports these types of SIBs:
•
Standard SIB
•
Standard SIB version B (supported in Junos OS Release 7.3 and later) is required to
support the Enhanced Scaling FPCs in a standalone T640 router. If you use one or
more Enhanced Scaling FPCs in a T640 router that is not part of a routing matrix, each
SIB in the router must be a SIB version B. All the SIBs in the T640 router can be either
standard SIB or SIB version B. You cannot use both on the same router at the same
time.
Figure 16: Standard SIB and Standard SIB Version B
•
The T640-SIB (supported in Junos OS Release 7.0 and later) is required to support
T640 routers connected to a TX Matrix platform); see Figure 17 on page 31. The T640
SIB supports the Enhanced Scaling FPC4 for T640 routers connected to a TX Matrix
platform.
Figure 17: T640 SIB
Each SIB consists of the following components:
•
Switch Fabric ASICs.
•
High-speed links (HSLs) to each FPC.
•
Three LEDs located on the SIB faceplate that display the status of the SIB. Table 6 on
page 31 describes the functions of the SIB LEDs. If all three LEDs are off, the SIB is not
receiving power. The OK and FAIL LEDs are replicated on the craft interface.
•
SIB online/offline button, located on the SIB faceplate.
• Upgrading to a T640 Standard SIB Version B on page 214
T640 Host Subsystem Overview
•
T640 Host Subsystem Description on page 32
•
T640 Routing Engine Overview on page 32
•
T640 T Series Control Boards (T-CBs) Description on page 38
•
T640 T Series Control Boards (T-CBs) LEDs on page 39
T640 Host Subsystem Description
The host subsystem provides the routing and system management functions of the
router. You can install one or two host subsystems on the router. To operate, each host
subsystem functions as a unit; the Routing Engine requires the corresponding T–CB, and
vice versa.
NOTE: We recommend that you install two host subsystems for redundant
protection. If you install only one host subsystem, we recommend that you
install it in slot RE0.
Each host subsystem has three LEDs that display its status. The host subsystem LEDs
are located on the upper right of the craft interface. For more information about the host
subsystem LEDs, see “T640 Craft Interface Host Subsystem LEDs” on page 44.
Related
Documentation
Replacing the T640 Host Subsystem Components on page 198•
• Taking the T640 Host Subsystem Offline on page 198
• Maintaining the T640 Host Subsystem on page 148
T640 Routing Engine Overview
•
T640 Routing Engine Description on page 32
•
T640 RE-600 Description on page 33
•
T640 RE-1600 Description on page 35
•
T640 RE-2000 Description on page 36
T640 Routing Engine Description
The Routing Engine is an Intel-based Peripheral Component Interconnect (PCI) platform
that runs Junos OS. Software processes that run on the Routing Engine maintain the
routing tables, manage the routing protocols used on the router, control the router
interfaces, control some chassis components, and provide the interface for system
management and user access to the router.
The T640 router is shipped with the Junos OS preinstalled and ready to be configured
when the T640 router is powered on. There are three copies of the software: one on a
CompactFlash card in the Routing Engine, one on a rotating hard disk in the Routing
Engine, and one on a PC Card that can be inserted into the slot in the Routing Engine
faceplate.
You can install one or two Routing Engines in the router. The Routing Engines install into
the upperrear ofthe chassisin the slots labeled RE0 and RE1.Each Routing Engine requires
a T-CB to be installed in the adjacent slot. RE0 installs below CB0, and RE1 installs above
CB1. A Routing Engine does not power up without a control board present in the adjacent
slot.
NOTE: If two Routing Engines are installed, they must both be the same
hardware model.
If two Routing Engines are installed, one functions as the master and the other acts as
the backup. If the masterRouting Engine fails or is removed, and the backup is configured
appropriately, the backup takes over as the master. If the host system is redundant, the
backup Routing Engine is hot-removable and hot-insertable, but the master Routing
Engine is hot-pluggable. A Routing Engine that is not redundant requires that you power
down the router before replacement.
Related
Documentation
NOTE: For specific information about Routing Engine components (for
example, the amount of DRAM), issue the show chassis routing-engine
command.
The ports forconnecting theRouting Engine toexternal management devices are located
on the Connector InterfacePanel (CIP).The CIP has three ports for each host subsystem:
•
10/100-Mbps Ethernet port for connecting to a management network
•
One asynchronous serial port for connecting to a console
•
One asynchronous serial port for connecting to a modem or other auxiliary device
Replacing a T640 Routing Engine on page 206•
• T640 Routing Engine Functions on page 8
• Maintaining the T640 Routing Engines on page 148
T640 RE-600 Description
The RE-600 Routing Engine boots from the storage media in this order: the PC Card (if
present), then the CompactFlash card (if present), then the hard disk.
Each Routing Engine 600 (shown in Figure 18 on page 34) consists of the following
components:
•
CPU—Runs Junos OS 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.
•
CompactFlash card—Providesprimary storagefor software images, configuration files,
and microcode. The fixed CompactFlash card is inaccessible from outside the router.
•
Hard disk—Provides secondary storage for log files, memory dumps, and rebooting the
system if the CompactFlash card fails.
•
EEPROM—Stores the serial number of the Routing Engine.
•
Interfaces for management access—Provide information about Routing Engine status
to devices (console, laptop, or terminal server) connected to ports located on the
Connector Interface Panel (CIP).
The faceplate of the Routing Engine 600 contains the following:
•
One PC Card slot—Accepts a removable PC Card, which stores software images for
system upgrades.
•
Reset button—Reboots the Routing Engine when pressed.
•
HD LED—Indicates activity on the hard drive. It does not necessarily indicate
routing-related activity.
NOTE: The LEDs that report host modulestatus (including RoutingEngine
status) are on the craft interface ratherthan the Routing Engine faceplate.
•
HD LED—Table 7 on page 35 describes the functions of the LED.
Indicates activity on the hard drive.On steadily or
NOTE: The LEDs on the Routing Engine do not necessarily indicate
routing-related activity.
Replacing a T640 Routing Engine on page 206•
• T640 Routing Engine Functions on page 8
• Maintaining the T640 Routing Engines on page 148
T640 RE-1600 Description
The RE-1600 Routing Engine boots from the storage media in this order: the PC Card in
SLOT 0 (if present), then the PC Card in SLOT 1 (if present), then the CompactFlash card
(if present), then the hard disk.
Figure 19: Routing Engine 1600 (RE-1600)
Each RE-1600 (shown in Figure 19 on page 35) consists of the following components:
•
CPU—Runs Junos OS 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.
•
CompactFlash card—Providesprimary storagefor software images, configuration files,
and microcode. The fixed CompactFlash card is inaccessible from outside the router.
•
Hard disk—Provides secondary storage for log files, memory dumps, and rebooting the
system if the CompactFlash card fails.
The faceplate of the RE-1600 contains the following:
•
•
•
Table 8: Routing Engine 1600 LEDs
EEPROM—Stores the serial number of the Routing Engine.
Interfaces for management—Provide information about Routing Engine status to
devices (console, laptop, or terminal server) connected to the Routing Engine ports
located on the CIP.
Two PC Card slots—Accept removable PC Cards, which store software images for
system upgrades.
Reset button—Reboots the Routing Engine when pressed.
LEDs—Table 8 on page 36 describes the functions of these LEDs.
DescriptionStateColorLabel
Related
Documentation
Slot LEDs 0
and 1
BlinkingRed and
green
alternately
On steadilyGreen
YellowHD
blinking
Indicates that the Routing Engine is booting
and the firmware is checking if a PC card is
installed.
Indicates that the RoutingEngine booted from
the PC Card.
Indicates activity on the hard drive.On steadily or
NOTE: The LEDs on the Routing Engine do not necessarily indicate
routing-related activity.
NOTE: The LEDs that report host modulestatus (including RoutingEngine
status) are on the craft interface ratherthan the Routing Engine faceplate.
Replacing a T640 Routing Engine on page 206•
• T640 Routing Engine Functions on page 8
• Maintaining the T640 Routing Engines on page 148
T640 RE-2000 Description
The RE-2000Routing Engine boots from thestorage media in this order: the USBdevice,
then the CompactFlash card (if present), then the hard disk, then the LAN.
Each RE-2000 (shown in Figure 20 on page 37) consists of the following components:
•
CPU—Runs Junos OS to maintain the router's routing tables and routing protocols. It
has a Pentium-class processor.
•
DRAM—Provides storage for the routing and forwarding tables and for other Routing
Engine processes.
•
CompactFlash card—Providesprimary storagefor software images, configuration files,
and microcode. The fixed CompactFlash card is inaccessible from outside the router.
•
Hard disk—Provides secondary storage for log files, memory dumps, and rebooting the
system if the CompactFlash card fails.
•
EEPROM—Stores the serial number of the Routing Engine.
•
Interfaces for management access—Provide information about Routing Engine status
to devices (console, laptop, or terminal server) connected to the Routing Engine ports
located on the CIP.
The faceplate of the RE-2000 contains the following:
•
USB port—Provides a removable media interface through which you can install the
Junos OS manually. Junos OS supports USB version 1.0.
•
Reset button—Reboots the Routing Engine when pressed.
•
Offline button—Takes the Routing Engine offline when pressed.
•
Extractor clips—Control the locking system that secures the Routing Engine.
•
LEDs—Table 9 on page 37 describes the functions of these LEDs.
Table 9: Routing Engine 2000 LEDs
DescriptionStateColorLabel
Indicates disk activity for the hard disk drive.On steadilyBlueHDD
Routing Engine is functioning normally.On steadilyGreenONLINE
NOTE: The LEDs on the Routing Engine do not necessarily indicate
routing-related activity.
Related
Documentation
Replacing a T640 Routing Engine on page 206•
• T640 Routing Engine Functions on page 8
• Maintaining the T640 Routing Engines on page 148
T640 T Series Control Boards (T-CBs) Description
This chassis supports up to two T-CBs. The Routing Engine requires an adjacent T-CB
to provide control and monitoring functions for the router (see Figure 21 on page 38).
These functions include determining Routing Engine mastership, controlling power and
reset for the other router components, monitoring and controlling fan speed, and
monitoring system status.
You can install up to two T-CBs in the router. Control boards install into the upper rear
of the chassis in the slots labeled CB0 and CB1 (referred to as CB-0 and CB-1, top to
bottom). If two T-CBs are installed, one functions as the master and the other as its
backup. If the master fails or is removed, the backup restarts and becomes the master.
Each T-CB requires a Routing Engine to be installed in the adjacent slot. CB0 installs
above RE0, and CB1 installs below RE1. T-CBs cannot function if a Routing Engine is not
present in the adjacent slot.
If the host system is redundant, the backup T-CB is hot-removable and hot-insertable,
but the master T-CB is hot-pluggable. A T-CB that is not redundant is hot-pluggable.
Figure 21: T-CB
NOTE: The T-CB requires Junos OS Release 7.0 or later.
100-MB Ethernet switch for intermodule communication.
•
PCI bus to the Routing Engines.
•
Processor subsystem (SPMB).
•
Three LEDs, located on the T-CB faceplate, indicate its status.
•
The T-CB online/offline button, located on the faceplate.
NOTE: When the adjacent Routing Engine is online, the online/offline
button on the T-CB faceplate is nonfunctional. For more information, see
“Taking the T640 Host Subsystem Offline” on page 198.
•
Two configuration switches, located on the faceplate:
•
For a standalone T640 router, the M/S and CHASSISID configuration switches must
always be set to S and 0.
•
For T640 routers connected to a TX Matrix platform, the M/S and CHASSIS ID
configuration switches must always be set to M and the chassis identifier (ID) of the
router. In this case, bothT-CBs must have the same chassis ID. For more information,
see the TX Matrix Router Hardware Guide.
•
Two RJ-45 ports labeled AUX and CIP on the T-CB faceplate.
•
For a standalone T640 router, these ports are not used.
•
For T640 routers connected to a TX Matrix platform, only the CIP port is used. For
more information, see the TX Matrix Router Hardware Guide.
Related
Documentation
T640 Chassis Description on page 13•
• Replacing a T640 T-CB on page 201
• Maintaining the T640 T-CBs on page 149
T640 T Series Control Boards (T-CBs) LEDs
Three LEDs, located on the T-CB faceplate, indicate its status. Table 10 on page 39
describes the functions of the T-CB LEDs.
Table 10: T-CB LEDs
DescriptionStateColorLabel
T-CB is functioning as the master.On steadilyBlueMASTER
T-CB is online and is functioning normally.On steadilyGreenOK
T-CB is powering up, but not online.Blinking
Related
Documentation
T640 Chassis Description on page 13•
• Replacing a T640 T-CB on page 201
• Maintaining the T640 T-CBs on page 149
T640 SONET Clock Generators (SCGs) Overview
•
T640 Standard SONET Clock Generators (SCGs) Description on page 40
•
T640 SONET Clock Generators (SCGs) LEDs on page 41
T640 Standard SONET Clock Generators (SCGs) Description
The SONET Clock Generators (SCGs) provide 19.44-MHz Stratum 3 clock signal for the
SONET/SDH interfaces on the router (see Figure 22 on page 40).
One SCG is shipped as part of the standard router configuration, but up to two SCGs can
be installed to provide redundancy. SCGs are installed into the upper rear of the chassis
in the slots labeled SCG0 and SCG1.
Backup SCGs are hot-removable and hot-insertable. Master and nonredundant SCGs
are hot-pluggable.
Figure 22: SCG
Each standard SCG consists of the following components:
•
19.44-MHz Stratum 3 clock.
•
Field-programmable gate array (FPGA) that performs multiplexing of clock sources.
•
Three LEDs, located on the SCG faceplate, that display the status of the SCG.
•
SCG online/offline button, located on the SCG faceplate.
NOTE: The external clock inputs are not supported on the standard SONET
Clock Generator (SCG) .
Related
Documentation
Replacing a T640 SCG on page 210•
• Maintaining the T640 SCGs on page 150
• Locating the T640 SCG Serial Number Label on page 375
T640 SONET Clock Generators (SCGs) LEDs
Three LEDs, located on the SCG faceplate, display the status of the SCG. Table 11 on
page 41 describes the functions of the SCG LEDs.
Table 11: SCG LEDs
Related
Documentation
Replacing a T640 SCG on page 210•
• Maintaining the T640 SCGs on page 150
DescriptionStateColorLabel
On steadilyGreenOK
SCG is online and is functioning
normally.
SCG has failed.On steadilyYellowFAIL
SCG is functioning as master.On steadilyBlueMASTER
• Locating the T640 SCG Serial Number Label on page 375
T640 Craft Interface Overview
•
T640 Craft Interface Description on page 41
•
T640 Craft Interface Alarm LEDs and ACO/LT Button on page 42
•
T640 Craft Interface LCD and Navigation Buttons on page 43
•
T640 Craft Interface Host Subsystem LEDs on page 44
•
T640 Craft Interface SIB LEDs on page 45
•
T640 Craft Interface FPC LEDs and Online/Offline Buttons on page 45
T640 Craft Interface Description
The craft interface allows you to view status and troubleshooting information at a glance
and to perform many system control functions. It is hot-insertable and hot-removable.
The craft interface is located on the front of the router above the FPCs and contains the
following:
Figure 23: Front Panel of the T640 Craft Interface
Related
Documentation
T640 Chassis Description on page 13•
• Troubleshooting Using the T640 Craft Interface LEDs
• Replacing a T640 Craft Interface on page 196
T640 Craft Interface Alarm LEDs and ACO/LT Button
Two large alarm LEDs are located at the upper left of the craft interface (see Figure 23
on page 42). 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 “T640 Alarm Relay
Contacts” on page 48. The LCD on the craft interface reports the cause of the alarm, as
described in “T640 Craft Interface LCD and Navigation Buttons” on page 43.
To deactivate red and yellow alarms, press the button labeled ACO/LT (for “alarm
cutoff/lamp test”), which is located to the right of the alarm LEDs. Deactivating analarm
turns off both LEDs and deactivates the device attached to the corresponding alarm
relay contact on the CIP. However, the LCD continues to report the alarm message until
you clear the condition that caused the alarm.
Table 12 on page 43 describes the alarm LEDs and alarm cutoff button in more detail.
Table 12: Alarm LEDs and Alarm Cutoff/Lamp Test Button
DescriptionStateColorShape
On steadilyRed
On steadilyYellow
——
Related
Documentation
T640 Chassis Description on page 13•
• Troubleshooting Using the T640 Craft Interface LEDs
• Replacing a T640 Craft Interface on page 196
T640 Craft Interface LCD and Navigation Buttons
A four-line LCD is located in the craft interface, along with six navigation buttons. The
LCD operates in two modes:
•
LED Idle Mode
Critical alarm LED—Indicates a criticalcondition that
can cause the router to stop functioning. Possible
causes include component removal, failure, or
overheating.
Warningalarm LED—Indicatesa seriousbut nonfatal
error condition, such as a maintenance alert or a
significant increase in component temperature.
Alarm cutoff/lamp test button—Deactivates red and
yellowalarms. Causesall LEDs on the craft interface
to light (for testing purposes), when pressed and
held.
•
LED Alarm Mode
During normal operation, the LCD operates in idle mode and reports current status
information, as shown in Figure 24 on page 43.
Figure 24: T640 LCD in Idle Mode
The lines in the display report the following information:
•
First line—Router name.
•
Second line—Length of time the router has been running, reported in the following
form:
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 OSSystem Basics and Services Command Reference.
When a red or yellow alarm occurs, the LCD switches to alarm mode and reports the
alarm condition, as shown in Figure 25 on page 44.
Figure 25: T640 LCD in Alarm Mode
The lines in the display report the following information:
Third and fourth lines—Status messages, which rotate at 2-second intervals. Some
conditions, such as removal or insertion of a system component, can interrupt the
messages.
•
First line—Router name.
•
Second line—Number of active alarms.
•
Third and fourth lines—Individual alarm messages, with the most severe condition
shown first. The prefix oneach line indicates whether the alarm isa red(R) or yellow (Y)
alarm.
For a list of alarm messages that can appear on the LCD, see “Troubleshooting Using the
T640 Chassis and Interface Alarm Messages” on page 165.
Related
Documentation
T640 Chassis Description on page 13•
• Troubleshooting Using the T640 Craft Interface LEDs
• Replacing a T640 Craft Interface on page 196
T640 Craft Interface Host Subsystem LEDs
Each host subsystem has three LEDs, located on the upper right of the craft interface,
that indicate its status. The LEDs labeled HOST0 show the status of the Routing Engine
in slot RE0 and the T-CB in slot CB0. The LEDs labeled HOST1 show the status of the
Routing Engine in slot RE1 and the T-CB in slot CB1. Table 13 on page 44 describes the
functions of the host subsystem LEDs.
Table 13: T640 Host Subsystem LEDs
DescriptionStateColorLabel
Host is offline.On steadilyRedFAIL
Host is online and is functioning normally.On steadilyGreenOK
• Troubleshooting Using the T640 Craft Interface LEDs
• Replacing a T640 Craft Interface on page 196
T640 Connector Interface Panel (CIP) Description
The Connector Interface Panel (CIP) consists of Ethernet, console, and auxiliary
connectors for the Routing Engines and alarm relay contacts (see Figure 26 on page 47).
The front electrostatic discharge point is located near the bottom of the CIP. The CIP is
located at the left side of the FPC card cage.
• Locating the T640 CIP Serial Number Label on page 371
T640 Routing Engine Ports
The CIP has two sets of ports that you use to connect the Routing Engines to external
management devices. Fromthese management devices, youcan use theCLI toconfigure
the router.
The upper set of ports, labeled HOST 0, connects to the Routing Engine in slot RE0; and
the lower set, labeled HOST 1, connectsto theRouting Enginein slotRE1. Eachset includes
the following ports:
•
•
•
ETHERNET—Connects the Routing Engine through an Ethernet connection to a
management LAN (or any other device that plugs into an Ethernet connection) for
out-of-band management. The port uses an autosensing RJ-45 connector to support
both 10- and 100-Mbps connections. Two small LEDs on the left edge of the port
indicate the connection in use: the yellow LED lights for a 10-Mbps connection and the
green LED lights for a 100-Mbps connection.
CONSOLE—Connects the Routing Engine to a system console through an RS-232
(EIA-232) serial cable.
AUXILIARY—Connects theRouting Engine to a laptop,modem, or other auxiliary device
through an RS-232 (EIA-232) serial cable.
Related
Documentation
T640 Connector Interface Panel (CIP) Description on page 46•
• T640 DB-9 Connector Pinouts for the Routing Engine AUXILIARY and CONSOLE Ports
on page 368
• T640 RJ-45 Connector Pinouts for the Routing Engine ETHERNET Port on page 367
• Replacing the T640 Connections to Routing Engine Interface Ports on page 180
T640 Alarm Relay Contacts
The CIPhas two alarm relay contacts for connecting the router to external alarmdevices.
Whenever a system condition triggers eitherthe red oryellowalarm onthe craft interface,
the alarm relay contacts are also activated. The alarm relay contacts are located below
the Routing Engine ports. The terminal blocks that plug into the alarm relay contacts are
supplied with the router. They accept wire of any gauge between 28-AWG and 14-AWG
(0.08 and 2.08 mm2), which is not provided. Use the gauge of wire appropriate for the
external device you are connecting.
Related
Documentation
T640 Connector Interface Panel (CIP) Description on page 46•
• Replacing the T640 Alarm Relay Wires on page 184
• T640 Routing Engine Interface Cable and Wire Specifications on page 365
• T640 Routing Engine Ports on page 47
T640 Power System Overview
•
T640 Power System Description on page 49
•
T640 Two-Input 160-A DC Power Supply Overview on page 49
•
T640 Two-Input 160-A DC Power Supply LEDs on page 51
•
T640 Three-Input 240-A DC Power Supply Overview on page 52
NOTE: Mixing power supplies with a different number of inputs in the same
router is supported only during upgrade. Mixing different types of power
supplies is not supported during normal operations.
Related
Documentation
Powering On a DC-Powered T640 Router on page 130•
• Maintaining the T640 Power Supplies on page 159
• T640 DC Power System Electrical Specifications on page 347
T640 Two-Input 160-A DC Power Supply Overview
•
Two-Input 160-A DC Power Supply Description on page 49
•
Two-Input 160-A DC Power Supply Inputs on page 50
•
Two-Input 160-A DC Power Supply Load Sharing and Fault Tolerance on page 50
Two-Input 160-A DC Power Supply Description
Each two-input 160-A DC power supply weighsapproximately 23lb (10.5kg) andconsists
of two inputs, two 80-A (@ –48 VDC) circuit breakers, a fan, and LEDs to monitor the
status of the power supply. Figure 27 on page 50 shows the two-input 160-A DC power
supply.
Each two-input 160-A DC power supply has two inputs—INPUT 1 and INPUT 0, from top
to bottom—each with its own 80-A (@ –48 VDC) circuit breaker.
NOTE: All inputs on the two-input 160-A DC powersupply in slotPEM0 must
be powered by dedicatedpower feeds derived from feed A, and all inputs on
the two-input 160-A DC power supply in slot PEM1 must be powered by
dedicated power feeds derived from feed B. This configuration provides the
commonly deployed A/B feed redundancy for the system.
Table 16 on page 50 describes which components are powered by each input.
Table 16: Components Powered by Each Input
Provides Power to These ComponentsInput
INPUT 0
Two-Input 160-A DC Power Supply Load Sharing and Fault Tolerance
When the router is operating normally and both power supplies in a redundant power
system are switched on, load sharing between them occurs automatically. When one
power supply fails or is turned off, the other power supply immediately assumes the
entire electrical load for the system. A single power supply with both inputs active can
provide full power for as long as the router is operational. Table 17 on page 51 describes
the behavior of the two-input160-A DC power supply and router if one of the inputs fails.
FPCs in slots FPC0 and FPC1, SIBs, T-CBs, Routing Engines, CIP, craft interface, and
fan trays
If either input on one power supply fails, the other power supply
assumes the electrical load for both inputs. If one of the inputs on
the other power supply is not functional, the router shuts down.
Related
Documentation
Redundantpowersupplies
T640 Power System Description on page 49•
• Powering On a DC-Powered T640 Router on page 130
• Maintaining the T640 Power Supplies on page 159
T640 Two-Input 160-A DC Power Supply LEDs
Four LEDs on each two-input 160-A DC power supply faceplate indicate the status of
the power supply. In addition, a power supply failure triggers the red alarm LED on the
craft interface. Table 18 on page 51 describes the functions of the power supply LEDs.
Table 18: Two-Input 160-A DC Power Supply LEDs
On steadilyYellowCB TRIP
DescriptionStateColorLED
Circuit breaker is on.On steadilyGreenCB OK
Circuit breaker is off.Off
Circuit breaker is not turned on, or host subsystem
has detected a failure and has turned the circuit
breaker off.
Off
On steadilyYellowOVER TEMP
Off
On steadilyBlueDC OK
Blinking
No problems have occured with circuit breaker, or
the power supply is off.
Power supply has exceeded recommended
temperature.
Power supply is within the recommended
temperature or is not turned on.
Power supply is installed correctly and is
functioning normally.
Power supply is starting up, is not properly
installed, or is not functioning correctly. One of the
inputs mighthave failed, or the power supplymight
not be receiving sufficient power.
• Powering On a DC-Powered T640 Router on page 130
• Maintaining the T640 Power Supplies on page 159
T640 Three-Input 240-A DC Power Supply Overview
•
Three-Input 240-A DC Power Supply Description on page 52
•
Three-Input 240-A DC Power Supply Inputs on page 52
•
Three-Input 240-A DC Power Supply Load Sharing and Fault Tolerance on page 53
Three-Input 240-A DC Power Supply Description
Each three-input 240-A DCpower supply weighsapproximately 25 lb(11.3 kg)and consists
of three inputs, three 80-A circuit breakers, a fan, and LEDs to monitor the status of the
power supply. Figure 28 on page 52 shows the three-input 240-A DC power supply in
2-INPUT mode.
Figure 28: Three-Input 240-A DC Power Supply
Three-Input 240-A DC Power Supply Inputs
The three-input 240-A DC powersupply inputsare labeled INPUT 0, INPUT 1, and INPUT2,
from top to bottom. Each input consists of –48 VDC and return, each with its own 80-A
circuit breaker. The input mode switch on the faceplate allows you to set the DC power
supply to either 2–INPUT or 3–INPUTmode. 2-INPUTmode isrequired for the T640router
and TX Matrix router.
Table 19 on page 53 describes which components are powered by each input.
Table 19: Components Powered by Each Three-Input 240-A DC Power
Supply Input
Three-Input ModeInput
INPUT 0
T640-SIBs, T-CBs, fan trays, Routing
Engines, and FPCs in slots FPC0 and
FPC1
FPCs in slots FPC2 through FPC7INPUT 1
Related
Documentation
INPUT 2
This input is not supported in 2–INPUT
mode.
Three-Input 240-A DC Power Supply Load Sharing and Fault Tolerance
When the router is operating normally and both power supplies are switched on, load
sharing between them occurs automatically. When one power supply fails or is turned
off, the other power supply immediately assumes theentire electrical loadfor the system.
A single power supply canprovide fullpower for aslong as the router is operational. Table
20 on page 53 describes the behavior of the power supply if one of the inputs fails.
Table 20: Fault Tolerance
Fault Tolerance When One Input Fails or is DisconnectedRedundancy
Nonredundant power supply
Redundant power supplies
T640 Power System Description on page 49•
• Powering On a DC-Powered T640 Router on page 130
If this input fails, the router shuts down.
NOTE: We recommend that you install redundant power
supplies.
If an input on one power supply fails, the other power supply
assumes theelectrical loadfor allinputs. Ifone input on the other
power supply is not functional, the router shuts down.
• Maintaining the T640 Power Supplies on page 159
T640 Three-Input 240-A DC Power Supply LEDs
LEDs on each power supply faceplate (see Figure 29 on page 54) indicate the status of
the power supply. In addition, a power supply failure triggers the red alarm LED on the
craft interface. Table 21 on page 54 describes the functions of the power supply LEDs.
Table 21 on page 54 describes the three-input 240-A DC power supply LEDs.
Table 21: Three-Input 240-A DC Power Supply LEDs
input
Off
DescriptionStateColorLED
Circuit breaker is on.On steadilyGreenCB ON—One per
Circuit breaker is not turned on, or
host subsystem has detected a
failure and has turned the circuit
breaker off.
Related
Documentation
On steadilyBlueDC OK—One per
power supply
Blinking
PRESENT—One
per input
On steadilyYellowOVER
TEMP—One per
power supply
Off
T640 Power System Description on page 49•
• Powering On a DC-Powered T640 Router on page 130
When the power supply is correctly
set to 2-INPUT mode and INPUT 0
and INPUT1 are properlyenergized,
the DC OK LED indicates that the
power supply is functioning
normally.
Power supply is starting up, is not
functioning, is not properly
installed, or is not operating
properly.
Input is receiving voltage.On steadilyGreenINPUT
Input voltage is not present.Off
Power supply has exceeded
recommended temperature.
Power supply is within the
recommended temperature or the
power supply is not on.
Four-Input 240-A DC Power Supply Description on page 55
•
Four-Input 240-A DC Power Supply Inputs on page 55
•
Four-Input 240-A DC Power Supply Load Sharing and Fault Tolerance on page 55
Four-Input 240-A DC Power Supply Description
Each four-input 240-A DC power supply weighs approximately 26.6 lb (12.0 kg) and
consists of four inputs, four 60-A circuit breakers, a fan, and LEDs to monitor the status
of the power supply. Figure 30 on page 55 shows the four-input 240-A DC power supply.
The four-input 240-ADC power supply inputs are labeled INPUT 0, INPUT1, and INPUT 2,
and INPUT 3 from top to bottom. Each input consists of –48 VDC and return, each with
its own 60-A circuit breaker.
Table 22 on page 55 describes which components are powered by each input.
Table 22: Components Powered by Each Four-Input 240-A DC Power
Supply Input
ComponentsInput
SIBs, control boards,Routing Engines, andhalf thesystem fanpowerINPUT 0
FPCs in slots FPC0 and FPC1 and half the system fan powerINPUT 1
FPCs in slots FPC2 through FPC4INPUT 2
FPCs in slots FPC5 through FPC7INPUT 3
Four-Input 240-A DC Power Supply Load Sharing and Fault Tolerance
When the router is operating normally and both power supplies are switched on, load
sharing between them occurs automatically. When one power supply fails or is turned
off, the other power supply immediately assumes theentire electrical loadfor the system.
CIRCUITBREAKERS FOR MIN. 60
SEC.TO DE-ENERGIZE THE UNIT
COMPLETELYBEFORE TURN ON.
g004660
Power supply LEDs
60A
60A
60A
60A
INPUT 3
T640 Core Router Hardware Guide
A single power supply can provide full power for as long as the router is operational. If
any of the four inputs fails, the router shuts down, and the other power supply assumes
the electrical load for all four inputs.
Related
Documentation
T640 Four-Input 240-A DC Power Supply LEDs on page 56•
• Troubleshooting the T640 Power System on page 171
• Replacing a T640 Four-Input 240-A DC Power Supply on page 254
• T640 DC Power Supply Electrical Specifications on page 348
T640 Four-Input 240-A DC Power Supply LEDs
LEDs on each four-input 240-A DC power supply faceplate (see Table 23 on page 56)
indicate the status of the power supply. In addition, a power supply failure triggers the
red alarm LED on the craft interface. Figure 31on page56 displays the powersupply LEDs.
Figure 31: Four-Input 240-A DC Power Supply LEDs
Table 23: Four-Input 240-A DC Power Supply LEDs
PRESENT—One
per input
input
power supply
Off
On steadilyBlueDC OK—One per
Blinking
DescriptionStateColorLED
Input is receiving voltage.On steadilyGreenINPUT
Input voltage is not present.Off
Circuit breaker is on.On steadilyGreenCB ON—One per
Circuit breaker is not turned on, or
host subsystem has detected a
failure and has turned the circuit
breaker off.
When all four inputs are properly
energized, the DC OK LED indicates
that thepower supplyis functioning
normally.
Either the power supply is starting
up, or it is not functioning, not
properly installed, or not operating
properly.
Table 23: Four-Input 240-A DC Power Supply LEDs (continued)
DescriptionStateColorLED
On steadilyYellowOVER
TEMP—One per
power supply
Off
Related
Documentation
T640 Four-Input 240-A DC Power Supply Overview on page 55•
• Maintaining the T640 Power Supplies on page 159
• Troubleshooting the T640 Power System on page 171
• Replacing a T640 Four-Input 240-A DC Power Supply on page 254
T640 Three-Phase Delta and Wye AC Power Supply Overview
•
Three-Phase Delta AC Power Supply Description on page 57
•
Three-Phase Wye AC Power Supply Description on page 58
•
AC Power Supply Load Sharing and Fault Tolerance on page 59
Three-Phase Delta AC Power Supply Description
Each three-phase delta AC power supply weighs approximately 31.0 lb (14.06 kg). A
metal wiring compartment contains the AC terminal block and ground labeled GND. The
AC terminal block consists of three input terminals labeled L1, L2, and L3, from left to
right. Thepower switch providespower to the router. Each power supply’s cooling system
consists of two fans, a front air filter, and a side air filter. LEDs provide the status of the
power supply. Figure 32 on page 57 shows the three-phase delta AC power supply.
Power supply has exceeded
recommended temperature.
Power supply is within the
recommended temperature or the
power supply is not on.
Figure 32: Three-Phase Delta AC Power Supply
Figure 33 on page 58 shows the three-phase delta AC power supply connections.
Figure 33: Three-Phase Delta AC Power Supply Connections
Figure 34 on page 58 shows the three-phase delta AC power cord.
Figure 34: Three-Phase Delta AC Power Cord
Three-Phase Wye AC Power Supply Description
Each three-phase wye AC power supply weighs approximately 31.0 lb (14.06 kg). A metal
wiring compartment contains the AC terminal block and ground labeled GND. The AC
terminal block consists of four input terminals labeled L1, L2, L3, and N, from left to right.
The power switch provides power to the router. Each power supply’s cooling system
consists of two fans, a front air filter, and a side air filter. LEDs provide the status of the
power supply. Figure 35 on page 59 shows the three-phase wye AC power supply.
Figure 36 on page 59 shows the three-phase wye AC power supply connections.
Figure 36: Three-Phase Wye AC Power Supply Connections
Figure 37 on page 59 shows the three-phase wye AC power cord.
Figure 37: Wye Three-Phase AC Power Cord
AC Power Supply Load Sharing and Fault Tolerance
When the router is operating normally and both power supplies are switched on, load
sharing between them occurs automatically. When one power supply fails or is turned
off, the other power supply immediately assumes theentire electrical loadfor the system.
A single power supply can provide full power for as long as the router is operational.
Related
Documentation
T640 Power System Description on page 49•
• T640 Three-Phase Delta and Wye AC Power Supply LEDs on page 60
• Troubleshooting the T640 Power System on page 171
• T640 AC Power Requirements on page 356
• T640 AC Power Cord Specifications on page 358
T640 Three-Phase Delta and Wye AC Power Supply LEDs
Figure 38 on page 60 shows the LEDs on each three-phase delta AC power supply
faceplate. The three-phase wye AC power supply has the same LEDs. The LEDs in Table
24 on page 60 indicate the status of the power supply. In addition, a power supply failure
triggers the red alarm LED on the craft interface.
Figure 38: Delta AC Power Supply LEDs
Table 24: Delta AC Power Supply LEDs
power supply
power supply
On steadilyGreenAC OK—One per
Off–
On steadilyBlueDC OK—One per
Blinking
Off–
DescriptionStateColorLED
The AC terminal block is receiving
voltage.
The AC terminal block is not
receiving voltage.
Power supply is functioning
normally.
Powersupply isstarting up, oris not
functioning or operating properly,
or is not properly installed.
The power supply fails or the AC
terminal block is not receiving
voltage.
T640 Three-Phase Delta and Wye AC Power Supply Overview on page 57•
• Troubleshooting the T640 Power System on page 171
• T640 AC Power Requirements on page 356
T640 Cooling System Description
The cooling system components work together to keep all router components within the
acceptable temperaturerange. Figure 39on page 61shows the airflowthrough therouter.
Figure 39: Airflow Through the Chassis
On steadilyYellowOVER
Off–
Power supply has exceeded
recommended temperature.
If the DC OK and AC OK are on
steadily, this LED indicates that
power supply is within the
recommended temperature.
The host subsystem monitors the temperature of the router components. When the
router is operating normally, the fans function at lower than full speed. If a fan fails or
the ambient temperature rises above a threshold, the speed of the remaining fans is
automatically adjusted to keep the temperature within the acceptable range. If the
ambient maximum temperature specification is exceeded and the system cannot be
adequately cooled, the Routing Engine shuts down some or all of the hardware
components.
The cooling system consists of the following components:
•
•
•
•
•
All fan trays and filters are hot-insertable and hot-removable.
Two front fan trays—The front fan trays each contain six fans and are interchangeable.
The front fan trays cool the components installed in the front card cage (the FPCs,
PICs, CIP, and midplane).
Front air filter.
Rear fan tray—The rear fan tray contains eight fans or five blowers, and cools the
components installed in the rear card cage (theRouting Engines, Control Boards, SCGs,
and the SIBs). The rear fan tray is not interchangeable with the front trays.
Rear air filter.
Each power supply contains one fan that cools that power supply.
Related
Documentation
Maintaining the T640 Air Filters on page 146•
• Maintaining the T640 Fan Trays on page 147
• Troubleshooting the T640 Cooling System on page 168
T640 Cable Management System Description
The cable management system (see Figure 40 on page 62) consists of a row of nine
semicircular plastic bobbins mounted on the front of therouter below the FPC card cage.
The PIC cables pass between the bobbins and into the tray, keeping the cables organized
and securely in place. The curvature of the bobbins also helps maintain the proper bend
radius for optical PIC cables.
You can pull the cable management system up and outward to lock it into the
maintenance position. This allows you to access the lower fan tray and the front air filter.
Figure 40: Cable Management System
Related
Documentation
• T640 Router Description on page 3
• T640 Chassis Description on page 13
• Removing the T640 Cable Management System on page 102
If arack isused, secure rack tofloor andbuilding
structure.
Cables
Acquire cables and connectors:
•
Determine the number of cables needed
based on your planned configuration.
•
Review the maximum distance allowed for
each cable. Choose the length ofcable based
on the distance between the hardware
components being connected.
Plan the cable routing and management.
Related
Documentation
T640 Router Installation Summary on page 69•
• Safety Requirements, Warnings, and Guidelines for Installing the T640 Router on
page 85
• T640 Chassis Lifting Guidelines on page 310
T640 Rack Requirements
“T640 Rack Requirements” on
page 66
“Calculating Power Budget for
Fiber-Optic Cable for M Series, MX
Series, and T Series Routers” on
page 363
“Calculating Power Margin for
Fiber-Optic Cable for M Series, MX
Series, and T Series Routers” on
page 363
“Maintaining T640 PICs and PIC
Cables” on page 156
The T640 Core Router can be installed in a rack or cabinet. Many types of racks are
acceptable, including four-post (telco) racks and open-frame racks. An example of an
open-frame rack is shown in Figure 41 on page 67.
The router isdesigned forinstallation in a 19-in. rack as defined in Cabinets, Racks, Panels,and Associated Equipment (document number EIA-310-D) published by the Electronics
Industry Association (http://www.eia.org).
With the use ofadapters, therouter is designed to fit intoa 600-mm-wide rack, asdefined
in the four-part Equipment Engineering (EE); European telecommunications standard forequipment practice (document numbers ETS 300 119-1 through 119-4) published by the
European Telecommunications Standards Institute (http://www.etsi.org). Use approved
wing devices to narrow the opening between the rails.
The rack rails must be spaced widely enough to accommodate the router chassis's
external dimensions: 37.45 in. (95.1 cm) high, 31 in.(78.7 cm)deep, and 17.43 in. (44.3 cm)
wide. The outer edges of the 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 “T640 Clearance Requirements for Airflow and Hardware
Maintenance” on page 68.
The chassis height of 37.45 in. (95.1 cm) is approximately 21.4 U. A U is the standard rack
unit defined in Cabinets, Racks, Panels, and Associated Equipment (document number
EIA-310-D) published by the Electronics Industry Association. You can stack two routers
in a rack that has at least 42.8 U (74.9 in. or 1.90 m) of usable vertical space.
The rack must be strong enough to support the weight of the fully configured router, up
to approximately 565 lb (256.3 kg). If you stack two fully configured routers in one rack,
it must be capable of supporting about 1130 lb (512.6 kg).
Figure 41: Typical Open-Frame Rack
Related
Documentation
Always secure therack to thestructure ofthe building. If your geographical area issubject
to earthquakes, bolt the rack to the floor. For maximum stability, also secure the rack to
ceiling brackets. For more information, see “Before You Install the T640 Rack-Mounting
Hardware” on page 77.
T640 Chassis Description on page 13•
• Installing the T640 Mounting Hardware for a Four-Post Rack or Cabinet on page 78
• Installing the T640 Mounting Hardware for an Open-Frame Rack on page 81
• Safety Requirements, Warnings, and Guidelines for Installing the T640 Router on
T640 Clearance Requirements for Airflow and Hardware Maintenance
When planning the installation site, you need to allow sufficient clearance around the
rack (see Figure 42 on page 68):
•
For the cooling system to function properly, the airflow around the chassis must be
unrestricted. Figure 39 on page 61 depicts the airflow in the router.
NOTE: If you mount the router in a cabinet, be sure that ventilation is
sufficient to prevent overheating.
•
For service personnel to remove and install hardware components, there must be
adequate space at the front and back of the router. At least 24 in. (61 cm) is required
both in front of and behind the router. NEBS GR-63 recommends that you allow at
least 30 in. (72.6 cm) in front of the rack and 24 in. (61.0 cm) behind the rack.
Figure 42: T640 Chassis Dimensions and Clearance Requirements
Related
Documentation
• T640 Chassis Description on page 13
• T640 Cooling System Description on page 61
• Safety Requirements, Warnings, and Guidelines for Installing the T640 Router on
It is important to proceed through the installation process in the following order:
1. Prepare your installation site.
See “T640 Site Preparation Checklist” on page 65.
2. Review the safety guidelines.
See “General Safety Guidelines for M Series, MX Series, and T Series Routers” on
page 303.
3. Unpack the router and verify the parts received.
“Unpacking the T640 Router” on page 71.
4. Install the mounting hardware.
See “Installing the T640 Mounting Hardware for a Four-Post Rack or Cabinet” on
page 78 or “Installing the T640 Mounting Hardware for an Open-Frame Rack” on
page 81.
5. Install the router.
See “Mounting the T640 Chassis Using a Mechanical Lift” on page 89 or “Installing
the T640 Chassis in the Rack Manually” on page 104.
6. Ground the router.
See “Connecting the T640 Grounding Cable” on page 115.
7. Connect the router to a management device.
See “Connecting the T640 Router to a Management Console or Auxiliary Device” on
page 119.
8. Power on the router.
See “Powering On a DC-Powered T640 Router” on page 130.
9. Perform the initial system configuration.
See “Initially Configuring the T640 Router” on page 139.