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.
Writing: Elizabeth Gardner, Jerry Isaac
Editing: Fran Mues
Illustration: Faith Bradford Brown
Cover Design: Edmonds Design
Revision History
October 2010—Corporate rebranding. Updated fiber-optic cleaning procedures. Minor edits.
December 2009—Converted to topics.
October 2009—Updated the description of the 12 m fiber-optic array cable.
31 December 2008—530-021926-01. Revision 2. Added support of the three-input 240-A power supply in two-input mode for Junos OS
Release 9.2 and later.
5 October 2007— 530-021926-01. Revision 1. Updated Junos OS release recommendation for graceful switchover, fiber-optic cleaning and
cabling instructions, DC input voltage specification, torque specification for securing the cable to a DC power supply, description of the
routing engines, taking the host subsystem offline procedure, replacing a DC power cable procedure, and maintaining the power supplies
section. Added information about nonstop active routing.
28 August2005—530-011711-01. Revision 5. Corrected “Routing Matrix Architecture” and“Routing Matrix Control Plane Architecture” figures,
revised the description of the system architecture, and added a paragraph to “Running Different Junos OS releases on the Routing Engines.”
5 January 2005— 530-011711-01. Revision 4.
9 December 2004—530-011711-01. Revision 3. Corrected “Chassis Dimensions and Clearance Requirements” figure, changed TX-CIP power
requirements, and made general updates.
3 December 2004—530-011711-01. Revision 2.
12 November 2004—530-011711-01. Revision 1.
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 BEBOUND BY THISAGREEMENT. IF YOUDO NOTOR CANNOT AGREE TO THE TERMS CONTAINED
HEREIN, THEN (A) DO NOT DOWNLOAD, INSTALL, OR USE THE SOFTWARE, AND (B) YOU MAY CONTACT JUNIPER NETWORKS
REGARDING LICENSE TERMS.
1. The Parties. The parties to this Agreement are (i) Juniper Networks, Inc. (if the Customer’s principal office is located in the Americas) or
Juniper Networks (Cayman) Limited(if the Customer’s principaloffice islocated outside theAmericas)(such applicable entitybeing referred
to herein as “Juniper”), and(ii) the person or organization that originallypurchased from Juniper or anauthorized Juniper reseller the applicable
license(s) for use of the Software (“Customer”) (collectively, the “Parties”).
2. The Software. In this Agreement, “Software” means the program modules and features of the Juniper or Juniper-supplied software, for
which Customer has paid the applicable license or support fees to Juniper or an authorized Juniper reseller, or which was embedded by
Juniper in equipment which Customer purchased from Juniper 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 payment ofthe applicablefees andthe limitations and restrictions set forth herein, Juniper grants to Customer
a non-exclusive and non-transferable license, without right to sublicense, to use the Software, in executable form only, subject to the
following use restrictions:
a. Customer shall use 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. Such limitsmay restrict use to a maximumnumber of 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 in anycopy ofthe Software or anyproduct
in which the Software is embedded; (e) distribute any copy of the Software to any third party, including as may be embedded in Juniper
equipment sold inthe secondhandmarket; (f) use any‘locked’or key-restricted feature, function, service, application,operation, or capability
without first purchasing the applicable license(s) and obtaining a valid key from Juniper, even if such feature, function, service, application,
operation, or capability is enabled without a key; (g) distribute any key for the Software provided by Juniper to any third party; (h) use the
Software in any manner that extends or is broader than the uses purchased by Customer from Juniper or an authorized Juniper reseller; (i)
use Embedded Software on non-Juniper equipment; (j) use Embedded Software (or make it available for use) on Juniper equipment that
the Customer did not originally purchase from Juniper or an authorized Juniper reseller; (k) disclose the results of testing or benchmarking
of the Software to any third party without the prior written consent of Juniper; or (l)use the Softwarein 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 Softwareand 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 accompanies theSoftware (the “WarrantyStatement”). Nothingin thisAgreement shall giverise toany 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 COSTSOR PROCUREMENTOF SUBSTITUTE GOODS ORSERVICES, ORFOR ANY SPECIAL, INDIRECT,OR CONSEQUENTIAL DAMAGES
ARISING OUTOF THIS AGREEMENT,THE SOFTWARE, ORANY JUNIPEROR JUNIPER-SUPPLIED SOFTWARE. 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 Juniper whose 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 toenforce this Agreement in its 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)).
Connecting to a Management Console or Auxiliary Device . . . . . . . . . . . . . . . . . . 119
Connecting the TX Matrix Router to External Alarm-Reporting Devices . . . . . . . 122
Overview of Providing Power to the TX Matrix Router . . . . . . . . . . . . . . . . . . . . . . 125
Tools and Parts Required for Connecting the TX Matrix Router to Power . . . . . . 126
Connecting Power to a Two-Input 160-A Power Supply in a TX Matrix Router . . 126
Connecting Power to a Three-Input 240-A Power Supply In 2-INPUT Mode in a
General Safety Guidelines for M Series, MX Series, and T Series Routers . . 295
General Safety Warnings for M Series, MX Series, and T Series Routers . . . 296
Figure 70: Connecting DC Power to the Two-Input 160-A DC Power Supplies . . . 127
Figure 71: Connecting DC Power to a Three-Input 240-A Power Supply in
Figure 129: Connecting Power Cables to the Power Supply . . . . . . . . . . . . . . . . . 282
Figure 130: Standard Cable Restraint on a Three-Input 240-A Power Supply . . 284
Figure 131: Optional Cable Restraint on a Three-Input 240-A Power Supply . . . 284
Figure 132: Disconnecting a DC Power Cable from a Two-Input 160-A DC Power
Junos OS Documentation and Release Notes on page xxvii
•
Objectives on page xxvii
•
Audience on page xxviii
•
Documentation Conventions on page xxviii
•
Documentation Feedback on page xxix
•
Requesting Technical Support on page xxx
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 TX Matrix Internet
Router(s). 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 theinstallation 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 might have been omittedfrom 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 xxviii defines the notice icons used in this guide.
Table 1: Notice Icons
DescriptionMeaningIcon
Indicates important features or instructions.Informational note
Table 2 on page xxviii 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 portis 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 product support is available throughthe 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:
Find solutions and answer questions using our Knowledge Base: http://kb.juniper.net/
•
Download the latest versions of software and review release notes:
http://www.juniper.net/customers/csc/software/
•
Search technical bulletins for relevant hardware and software notifications:
https://www.juniper.net/alerts/
•
Join and participate in the Juniper Networks Community Forum:
http://www.juniper.net/company/communities/
•
Open a case online in the CSC Case Management tool: http://www.juniper.net/cm/
To verify service entitlementby product serialnumber, use ourSerial NumberEntitlement
(SNE) Tool: https://tools.juniper.net/SerialNumberEntitlementSearch/
The Juniper Networks TX Matrix router is the centralized switch fabric of the routing
matrix, which is a terabit routing system interconnecting up to four T640 Core Routers
to deliver up to 2.56 terabits per second (Tbps) of subscriber switching capacity. The
routing matrix multichassis architecture provides scalable growth for aggregation and
core services for voice, video, and data networks. It provides a flexible and cost-effective
means to simplify large point-of-presence (POP) and central office environments. The
routing matrix delivers high-availability services from tunnel services, ATM, DS3,
OC3/STM1, OC12/STM4, Gigabit Ethernet, 10-Gigabit Ethernet, OC48/STM16,
OC192/STM64, and other high-speed interfaces.
The routing matrixleverages the intelligent virtual services capabilitiesof Junos OS, which
enable you to create multiple application-specific logical networks over a single physical
topology. This gives you the ability to virtually separate traffic types that require unique
network attributes—such as ATM or high-priorityvoice over IP (VoIP) and third-generation
(3G) mobile traffic—from bulk transit IP traffic.
Related
Documentation
The TX Matrix router architecture cleanly separates control operations from packet
forwarding operations. This design eliminates processing and traffic bottlenecks,
permitting the TX Matrix router to achieve terabit performance levels. Control operations
in the TX Matrix router are performed by the host subsystem, which runs Junos OS to
handle traffic engineering and configuration management. High-availability, interchassis
communicationsare provided byan EthernetLAN thatinterconnectsthe hostsubsystems
in the TX Matrix router and the T640 routers.
The TX Matrix router is a modular, rack-mountable system. One TX Matrix router can be
installed in one standard 19-in. wide, 78-in. high, EIA telco rack.
• TX Matrix System Architecture Description on page 5
• TX Matrix Routing Matrix Control Plane Architecture on page 8
TX Matrix System Architecture Description on page 5
•
TX Matrix Routing Engine Functions on page 6
•
TX Matrix Routing Matrix Control Plane Architecture on page 8
•
Control Plane Connections Between the TX Matrix Router and T640 Routeron page 10
•
TX Matrix Routing Matrix Switch Fabric Architecture on page 12
•
Switching Plane Connections Between the TX Matrix Router and T640
Routers on page 14
TX Matrix System Architecture Description
The routing matrix has two main architectural components, the control plane and the
forwarding plane:
•
The control plane in the routing matrix is formed by the connection of the host
subsystems—TX-CBs in the TX Matrix router and T-CBs in the T640 routers —and the
Routing Engines.
•
The forwarding plane in the routing matrix is formed by the switch fabric—TX-SIBs in
the TX Matrix router and T640-SIBs in the T640 routers—and the Packet Forwarding
Engines.
The Routing Engines and the Packet Forwarding Engines perform their primary tasks
independently. This arrangement streamlines routing control and forwarding and runs
Internet-scale backbone networks at high speeds. Figure 1 on page 6 shows the
relationship between the Routing Engines and the Packet Forwarding Engines.
The TX Matrix Routing Engine handles all routing protocols, as well as the software
processes that control the TX Matrix interfaces and user access to the TX Matrix router.
All Routing Engines in the routing matrix run software processes that control chassis
components and system management. For more information about the processes, see
“Routing Engine Software Components” on page 149.
The Routing Engines include the following functions and features:
•
Processing of routing protocol packets—The Routing Engine handles all packets that
concern routing protocols, freeingthe Packet Forwarding Engine to handleonly 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 witha complete
set ofInternet features and provides full flexibilityfor advertising, filtering,and modifying
routes. Routing policies are set according to route parameters (for example, prefix,
prefix lengths, and Border Gateway Protocol [BGP] attributes).
•
Scalability—The Junos routing tables have been designed to hold all the routes in
current networks with ample capacity for expansion. Additionally, the 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 andchange management—Configurationfiles, system images, andmicrocode
can be held and maintained in primary and secondary storage systems, permitting
local or remote upgrades.
•
Monitoring efficiency and flexibility—The TX Matrix router supports functions such as
alarm handling and packet countingon every port, without degradingpacket-forwarding
performance.
The TX Matrix Routing Engine constructs and maintains one ormore routingtables. From
the routingtables, the Routing Engine derives a tableof activeroutes, called theforwarding
table, which is then copied to the T640 routers (see Figure 2 on page 8). The Junos
kernel running on each T640 router's Routing Engine copies its forwarding table to all
Packet Forwarding Engines in the router. The design of the ASICs allow the forwarding
table in the Packet Forwarding Engine to be updated without interrupting forwarding
performance.
Figure 2: Control Packet Handling for Routing and Forwarding Table
Updates
Related
Documentation
TX Matrix Router Description on page 3•
• TX Matrix System Architecture Description on page 5
• TX Matrix Routing Engine Description on page 26
TX Matrix Routing Matrix Control Plane Architecture
The routing matrix contains two controlplanes. Allmaster Routing Enginesin the TX Matrix
router and T640 routers are on one control plane; all backup Routing Engines are on
another control plane (see Figure 3 on page 9). To manage the Routing Engines on a
control plane, you must be logged into the Routing Engine in the TX Matrix router on that
control plane. For example, you must be logged into the backup Routing Engine in the
TX Matrix router to upgrade the software of all backup Routing Engines in the routing
matrix.
The TX Matrix Routing Engine connects to a high-speed switch through a 1-Gbps link
within the host subsystem. The switch provides a 100-Mbps link to each T640 Routing
Engine. The 100-Mbps links are provided through the UTP Category 5 Ethernet cable
connections between the TX-CIPs and the T-CBs in the T640 routers.
The kernel synchronization process running on each T640 router Routing Engine
synchronizes the TX Matrix Routing Engine's forwarding table with the forwarding table
on a T640 router. The Junos kernel running on each T640 router Routing Engine copies
its forwarding table to all Packet Forwarding Engines in each T640 router.
Figure 4 on page 10 illustrates the control plane architecture.
Figure 4: Routing Matrix Control Plane Architecture
Related
Documentation
TX Matrix Router Description on page 3•
• TX Matrix System Architecture Description on page 5
• Control Plane Connections Between the TX Matrix Router and T640 Routeron page 10
Control Plane Connections Between the TX Matrix Router and T640 Router
The control plane connections between the T640 routers and the TX Matrix router are
provided by UTP Category 5 Ethernet cables between the RJ-45 ports on the TX-CIPs in
the TX Matrix router and the T-CBs in the T640 routers. The maximum length supported
is 100 m. The UTP Category 5 cables do not have to be the same length. The cable wiring
is straight-through (not crossover).
Table 3 on page 11shows these connections.Each column represents aTX-CIP (TX-CIP-0
and TX-CIP-1), and each cell within a column represents a port on that TX-CIP. Each cell
specifies the TX-CIP port (LCC0 through LCC3) and its connection to the port labeled
CIP on a T-CB in one of the T640 routers. For example, port LCC0 on TX-CIP-0 is
connected to T-CB-0 in chassis LCC0, port LCC1 on TX-CIP-0 is connected to T-CB-0 in
chassis LCC1, and so on.
NOTE: The RJ-45 port labeled AUX on a T-CB is reserved for future use.
The cable connections provided in Table 3 on page 11 apply to routing matrix
configurations using from one through four T640 routers. For example, if you have a
single T640 router in your configuration, the connections from each TX-CIP to chassis
LCC0 are presented in the first row of the table. If you have two T640 routers in your
configuration,the connections fromeach TX-CIP to chassis LCC0 and LCC1 are presented
in the first two rows of the table, and so on.
NOTE: The RJ-45 ports labeled LCC4 through LCC7 on a TX-CIP are reserved
for future use.
Table 3: Cable Connections between TX-CIPs and T-CBs
TX-CIP-1 Port and DestinationTX-CIP-0 Port and Destination
LCC0—T-CB-1 in LCC0LCC0—T-CB-0 in LCC0
LCC1—T-CB-1 in LCC1LCC1—T-CB-0 in LCC1
LCC2—T-CB-1 in LCC2LCC2—T-CB-0 in LCC2
LCC3—T-CB-1 in LCC3LCC3—T-CB-0 in LCC3
Figure 5 on page 12 shows the control and switching planes connections between the
TX Matrix router and a T640 router. The control plane connections are in the center.
The routing matrix switch fabric consists of five data switching planes. The switch fabric
uses ASICs to perform high-speed packet forwarding between the T640 routers. Each
TX-SIB and the T640-SIBs connected to it represent a data switching plane that spans
the TX Matrix router and all T640 routers in the routing matrix. The switching planes are
connected by high-speed optical links within fiber-optic array cables.
Consider a packet that enters a T640 router and is destined for another T640 router in
the routing matrix. When the packet enters an interface on a PIC in a T640 router, it is
forwarded to the switch fabric by a Packet Forwarding Engine on that router (see T640Core Router Hardware Guide for moredetails). The packet is forwarded through the switch
fabric from the source T640 router, through the TX Matrix router, to the target T640
router. The switch fabric allows high-priority traffic from any Packet Forwarding Engine
to an egress Packet Forwarding Engine to be given preferential treatment overlow-priority
traffic from any other Packet Forwarding Engine. The Packet Forwarding Engine on the
target T640 router forwards the packet to the destination PIC and interface.
The switch fabric can forward up to 3 Gpps. The maximum aggregate throughput rate
for the TX Matrix router is 2.56 Tbps (full duplex). Figure 6 on page 13 illustrates the
switch fabric architecture.
Switching Plane Connections Between the TX Matrix Router and T640 Routers
The switching plane connections between the T640 routers and the TX Matrix router are
provided by the fiber-optic array cables that connect the T640-SIBs to the TX-SIBs.
Table 4 on page 14shows theseconnections. Each columnrepresents a TX-SIB (TX-SIB-0
through TX-SIB-4), and each cell within a column represents an adapter on that TX-SIB.
Each cell specifies the TX-SIB adapter (LCC0 through LCC3) and its connection to a
T640-SIB in one of the T640 routers. For example, adapter LCC0 on TX-SIB-0 is
connected to T640-SIB-0 in chassis LCC0, adapter LCC1 on TX-SIB-0 is connected to
T640-SIB-0 in chassis LCC1, and so on.
The cable connections provided in Table 4 on page 14 apply to routing matrix
configurations using from one through four T640 routers. For example, if you have a
single T640 router in your configuration, the connections from each TX-SIB to chassis
LCC0 are presented in the first row of the table. If you have two T640 routers in your
configuration,the connections fromeach TX-SIB tochassis LCC0 and LCC1are presented
in the first two rows of the table, and so on.
Table 4: Fiber-Optic Array Cable Connections Between TX-SIBs and T640-SIBs
TX-SIB-0 Adapter
and Destination
LCC0—T640-SIB-0 in
LCC0
LCC1—T640-SIB-0 in
LCC1
LCC2—T640-SIB-0 in
LCC2
LCC3—T640-SIB-0 in
LCC3
TX-SIB-1 Adapter
and Destination
LCC0—T640-SIB-1 in
LCC0
LCC1—T640-SIB-1 in
LCC1
LCC2—T640-SIB-1 in
LCC2
LCC3—T640-SIB-1 in
LCC3
TX-SIB-2 Adapter
and Destination
LCC0—T640-SIB-2 in
LCC0
LCC1—T640-SIB-2 in
LCC1
LCC2—T640-SIB-2 in
LCC2
LCC3—T640-SIB-2 in
LCC3
TX-SIB-3 Adapter
and Destination
LCC0—T640-SIB-3 in
LCC0
LCC1—T640-SIB-3 in
LCC1
LCC2—T640-SIB-3 in
LCC2
LCC3—T640-SIB-3 in
LCC3
Figure 7 on page 15 shows the control and switching planes connections between the
TX Matrix router and a T640 router. Five switching planes are shown.
NOTE: Because theT640-SIB adaptersand fiber-optic arraycableconnectors
extend beyond the rear of the chassis, you need a minimum of 4 inches of
clearance in the rear of a T640 router installed in a cabinet.
The TX Matrix router is designed so that no single point of failure can cause the entire
system to fail. The following major hardware components are redundant:
•
TX-SIBs—The TX Matrix router has five TX-SIBs. Each TX-SIB and the T640-SIBs
connected to it represent a data switching plane that spans the TX Matrix router and
all T640 routers in the routing matrix. One ofthe five TX-SIBs—usually TX-SIB-0—acts
as a backup to the remaining four TX-SIBs. If a TX-SIB or T640-SIB fails, the backup
data switching plane becomes active and traffic forwarding continues without any
degradation.When thefailedcomponent isreplaced, the data switching plane in which
it resides becomes the new backup. If the failed component is not replaced, and a
TX-SIB or T640-SIB in an active data switching plane fails, only that component is
taken offline.
•
Host subsystem—The hostsubsystem consists of a RoutingEngine functioningtogether
with a TX-CB. The TX Matrix 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 asthe master. To operate, each hostsubsystem requires aRouting Engine
installed in an adjacent slot to a TX-CB.
If theRouting Enginesare configured for graceful switchover, the backup Routing Engine
automatically synchronizes its configuration andstate with the master RoutingEngine.
Any update to the master Routing Engine state is replicated on the backup Routing
Engine. Ifthe backupRouting Engine assumes mastership, packet forwarding continues
through theTX Matrix router without interruption. For more informationabout graceful
switchover, see the Junos OS High Availability Configuration Guide.
NOTE: We recommend that you run Junos OS Release 7.3 or later on the
TX Matrix router to support graceful switchover.
•
TX-CIPs—The TX Matrix router has two TX-CIPs. Each TX-CIP provides the ports for
its corresponding host subsystem (Routing Engine and TX-CB) in the TX Matrix router
and the control plane connections to the Control Boards (T-CBs) in up to four T640
routers.
If the master TX-CIP fails, the backup TX-CIP provides redundant connections to the
active host subsystemin the TX Matrix router andthe activeT-CBs in the T640 routers.
In thiscase, the Routing Engines in the TX Matrix routerand T640 routers donot perform
a switchover to their backups.
•
Power supplies—The TX Matrix 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
TX Matrix 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 TX Matrix router indefinitely.
The TX Matrix SCC is a rigid sheet metal structure that houses all the other system
components (see Figure 8 on page 20 and Figure 9 on page 21). The chassis measures
44.5 in. (113.0 cm) high, 17.4 in. (44.2 cm) wide, and 31.4 in. (79.8 cm) deep. The chassis
installs into standard 19-in. equipment racks or telco center-mount racks. One TX Matrix
router can be installed into a standard (44-U) rack, if the rack can handle the maximum
configuration weight of 495 lb (225 kg).
The chassis includes the following features (see Figure 8 on page 20 and Figure 9 on
page 21):
•
A pair of metal flanges and a pair of metal brackets used for mounting the chassis in
a four-post rack or cabinet or open-frame rack.
•
Upper and lower handles on each side to facilitate positioning the TX Matrix router in
the rack. Do not use the handles to lift the TX Matrix router.
•
Two electrostatic discharge points (banana plug receptacles), one on each TX-CIP
and one in the rear.
WARNING: Before removing or installingcomponents of aTX Matrix 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 TX Matrix router.
The TX Matrix router must be connected to earth ground during normal
operation.
Rack Requirements for TX Matrix Routers on page 61•
• TX Matrix Preventing Electrostatic Discharge Damage on page 298
• TX Matrix Physical Specifications on page 333
• TX Matrix Chassis Grounding Specifications on page 337
TX Matrix Midplane Description
The midplane is located in the center of the chassis and forms the rear of the TX-SIB
card cage (see Figure 10 on page 22). The TX-SIBs install into the midplane from the
front of the chassis, and the Routing Engines and TX-CBs install into the midplane from
the rear of the chassis.The power supplies and cooling system components also connect
to the midplane.
The TX-SIBs create the switch fabric for the TX Matrix router, providing up to a total of
3 billionpacketsper second(Gpps) of forwarding(see Figure 11on page24). Five TX-SIBs
are installed vertically in the front of the TX Matrix router. The TX-SIBs are referred to as
TX-SIB-0 through TX-SIB-4 (left to right).
One of the five TX-SIBs—usually TX-SIB-0—acts as a backup to the remaining four
TX-SIBs. If a TX-SIB or T640-SIB fails, the backup data switching plane becomes active
and traffic forwarding continues without any degradation. When the failed component
is replaced, the data switching plane in which it resides becomes the new backup. If the
failed component is not replaced, and a TX-SIB or T640-SIB in an active data switching
plane fails, only that component is taken offline.
TX-SIBs are hot-removable and hot-insertable.
Each TX-SIB consists of the following components:
•
Switch fabric ASICs.
•
A high-speed fiber-optic link to each T640 router in the routing matrix (a total of four
links labeled LCC0 through LCC3). The four links represent one data switching plane
across four T640 routers.
•
Two status LEDs located to the right of each fiber-optic array adapter on the TX-SIB
faceplate. Table 5 on page 24 describes the functions of these LEDs.
•
An ONLINE/OFFLINE button next to each fiber-optic array adapter that brings the
corresponding interface and T640-SIB online and offline.
TX Matrix Routing Matrix Switch Fabric Architecture on page 12•
• TX Matrix TX-SIB LEDs on page 24
• TX Matrix TX-SIB LEDs on the Craft Interface on page 38
• Maintaining the TX Matrix TX-SIBs on page 198
• Troubleshooting the TX Matrix TX-SIBs and the Switching Planes on page 216
Two LEDs—RX and TX—indicate the status of the TX-SIB (see Table 5 on page 24). Each
TX-SIB has three additional LEDs on the craft interface that show its status.
DescriptionStateColorLabel
Receive link is offline.Off—RX
Receive link is powering on.BlinkingGreen
On steadilyGreen
On steadilyYellow
Receive link is online and functioning
normally.
Fiber-optic array cable might be
connected to the wrong T640-SIB.
On steadilyRed
Errors have been detected, or the
receivelink is not functioning normally.
TX Matrix Switch Interface Boards (TX-SIBs) Description on page 23•
• TX Matrix TX-SIB LEDs on the Craft Interface on page 38
• Troubleshooting the TX Matrix TX-SIBs and the Switching Planes on page 216
TX Matrix Host Subsystem Description
The host subsystem provides the routing and system management functions of the
TX Matrix router. You can install one or two host subsystems on the TX Matrix router. To
operate, each host subsystem functions as a unit; the Routing Engine requires the
corresponding TX-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.
On steadilyGreen
On steadilyRed
Transmit link is online and functioning
normally.
Transmit link is not functioning
normally.
Related
Documentation
TX Matrix Control Board (TX-CB) Description on page 32•
• TX Matrix Routing Engine Description on page 26
• TX Matrix Host Subsystem LEDs on the Craft Interface on page 37
The Routing Engine in the TX Matrix router maintains the routing tables used by the
routing matrix and controls the routing protocols that run on the routing matrix. The
TX Matrix router provides all routing tables, along with updates, to each T640 router in
the routing matrix.
You can install one or two Routing Engines in the TX Matrix router. The Routing Engines
install into the upper rear of the chassis in the slots labeled RE0 and RE1. If two Routing
Engines are installed, one functions as the master and the other acts as the backup. If
the master Routing Enginefails oris removed, and the backup is configured appropriately,
the backup restarts and becomes the master.
NOTE: Werecommendthat yourun thesame JunosOS releaseon the master
and backup Routing Engines. If you elect to run different Junos OS releases
on the Routing Engines, a change in Routing Engine mastership can cause
one or all T640 routers tobe logicallydisconnectedfromthe TX Matrixrouter.
Related
Documentation
Each Routing Engine requires a TX-CB to be installed in the adjacent slot. RE0 installs
below CB0, and RE1 installs above CB1. A Routing Engine does not power on if no TX-CB
is present in the adjacent slot.
The ports forconnecting theRouting Engine toexternal management devices arelocated
on the corresponding TX-CIP. The ports on TX-CIP-0 connect to the Routing Engine in
slot RE0, and the ports on TX-CIP-1 connect to the Routing Engine in slot RE1.
The TX Matrix router supports the following Routing Engines:
•
RE-600-2048 (EOL)
•
RE-1600-2048 (EOL)
•
RE-A-2000-4096
NOTE: For specific information about Routing Engine components (for
example, the amount of DRAM), issue the show chassis routing-engine
command.
The RE-600 boots from the storage media in this order: the PC Card (if present), then
the CompactFlash card (if present), then the hard disk.
Figure 12: Routing Engine 600
Each Routing Engine 600 (shown in Figure 12 on page 27) consists of the following
components:
Chapter 3: TX Matrix Hardware Components Overview
•
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—Provides primarystoragefor software images, configuration files,
and microcode. The fixed CompactFlash card is inaccessible from outside the router.
•
Hard disk—Provides secondary storage for log files, memorydumps, and rebooting the
system if the CompactFlash card fails.
•
EEPROM—Stores the serial number of the Routing Engine.
•
Interfaces for out-of-band 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.
A slot labeled PC CARD on the Routing Engine faceplate accepts a Type I PC Card, as
defined in the PC Card Standard published by the Personal Computer Memory Card
International Association (PCMCIA). The TX Matrix router is shipped with a PC Card
that contains Junos OS. The PC Card can be used to copy Junos OS from the PC Card
onto the Routing Engine. You can also copy Junos OS from the Routing Engine onto a
PC Card, for example, to create a backup copy of upgrade software that you have
obtained from Juniper Networks. Instructions for copying software to a PC Card are
available at the Juniper Networks Support Web site (http://www.juniper.net/support/);
after logging in, navigate to the Customer Support Center, then to the download page
for Junos OS.
NOTE: The software on a PC Card is loaded only onto the Routing Engine
into which the PC Card is inserted. It is not automatically copied to the
other Routing Engine.
•
Reset button—Reboots the Routing Engine when pressed.
•
HD LED.
Related
Documentation
TX Matrix Host Subsystem Description on page 25•
• TX Matrix Routing Engine Description on page 26
• TX Matrix Host Subsystem LEDs on the Craft Interface on page 37
• TX Matrix RE-600 LEDs on page 28
TX Matrix RE-600 LEDs
The HD LED indicates activity on the hard drive. It does not necessarily indicate
routing-related activity.
Related
Documentation
TX Matrix Host Subsystem Description on page 25•
• TX Matrix RE-600 Description on page 27
• TX Matrix Host Subsystem LEDs on the Craft Interface on page 37
TX Matrix RE-1600 Description
The RE-1600 boots from the storage media in this order: the PC Card in SLOT 0 (if
present), then the PCCard inSLOT1 (if present), then the CompactFlash card(if present),
then the hard disk.
NOTE: The LEDs that report host module status (including Routing Engine
status) are on the craft interface rather than the Routing Engine faceplate.
Each RE-1600 (shown in Figure 13 on page 29) 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—Provides primarystoragefor software images, configuration files,
and microcode. The CompactFlash card is inaccessible from outside the router.
•
Hard disk—Provides secondary storage for log files, memorydumps, and rebooting the
system if the CompactFlash card fails.
•
EEPROM—Stores the serial number of the Routing Engine.
•
Interfaces for out-of-band management—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-1600 contains the following:
•
Two PC Card slots—Accept removable PC Cards, which store software images for
system upgrades.
Each PC card slot accepts a Type I PC Card, as defined in the PC Card Standard
published by the Personal Computer MemoryCard International Association (PCMCIA).
The TX Matrix router is shipped with a PC Card that contains Junos OS. The PC Card
can be used to copy Junos OS from the PC Card onto the Routing Engine. You can also
copy Junos OSfrom theRouting Engine onto a PC Card, for example, tocreatea backup
copy of upgrade software that you have obtained from Juniper Networks. Instructions
for copying software to a PC Card are available at the Juniper Networks Support Web
site (http://www.juniper.net/support/); after logging in, navigate to the Customer
Support Center, then to the download page for Junos OS.
NOTE: The software on a PC Card is loaded only onto the Routing Engine
into which the PC Card is inserted. It is not automatically copied to the
other Routing Engine.
Each RE-2000 (shown in Figure 14 on page 31) consists of the following components:
•
CPU—Runs Junos OS to maintain the 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.
Related
Documentation
•
CompactFlash card—Provides primarystoragefor software images, configuration files,
and microcode. The CompactFlash card is inaccessible from outside the router.
•
Hard disk—Provides secondary storage for log files, memorydumps, and rebooting the
system if the CompactFlash card fails.
•
EEPROM—Stores the serial number of the Routing Engine.
•
Interfaces for out-of-band 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. The 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—HDD and ONLINE indicate activity on the hard disk drive and the status of the
Routing Engine.
TX Matrix Host Subsystem Description on page 25•
• TX Matrix Host Subsystem LEDs on the Craft Interface on page 37
Table 7 on page 32 describes the functions of the LEDs on the faceplate of the Routing
Engine.
Table 7: Routing Engine 2000 LEDs
NOTE: The LEDs on the Routing Engine do not necessarily indicate
routing-related activity.
DescriptionStateColorLabel
Indicates disk activity for the hard disk drive.On steadilyBlueHDD
Routing Engine is functioning normally.On steadilyGreenONLINE
Routing Engine is transitioning online.Blinking
Related
Documentation
TX Matrix Host Subsystem Description on page 25•
• TX Matrix Host Subsystem LEDs on the Craft Interface on page 37
• TX Matrix Routing Engine Description on page 26
• TX Matrix RE-2000 Description on page 30
TX Matrix Control Board (TX-CB) Overview
•
TX Matrix Control Board (TX-CB) Description on page 32
•
TX Matrix Control Board (TX-CB) LEDs on page 34
TX Matrix Control Board (TX-CB) Description
Each TX-CB works with an adjacent Routing Engine to provide control and monitoring
functions for the TX Matrix router (see Figure 15 on page 33). These functions include
determining Routing Enginemastership,controlling power andreset for the other TX Matrix
router components, monitoring and controlling fan speed, and monitoring system status.
You can install up to two TX-CBs in the TX Matrix router. TX-CBs install into the upper
rear of the chassisin the slots labeled CB0 and CB1 (referred to as TX-CB-0 and TX-CB-1).
Each TX-CB requiresa Routing Engine to be installed inthe adjacentslot. TX-CB-0 installs
above RE0, and TX-CB-1 installs below RE1. TX-CBs cannot function if a Routing Engine
is not present in the adjacent slot.
Routing Engine has failed.On steadilyRed
The TX-CB is hot-pluggable if the TX Matrix router contains only one host subsystem. If
the TX Matrixrouter contains aredundant host subsystem, theTX-CBs are hot-insertable
and hot-removable. One TX-CB functions as the master and the other as its backup. If
the master fails or is removed, the backup restarts and becomes the master.
NOTE: A TX-CB and a T-CB are not interchangeable.
Figure 15: TX-CB
Related
Documentation
Each TX-CB consists of the following components:
•
100-MB Ethernet switch. This switch is used for intermodule communication.
•
PCI bus to the Routing Engines.
•
Switch processor mezzanine board (SPMB).
•
Three LEDs, located on the TX-CB faceplate. These indicate the status of the TX-CB.
Table 8 on page 34 describes the functions of the TX-CB LEDs.
•
Online/offline button, located on the TX-CB faceplate. This button is nonfunctional.
•
Two configuration switches, located on the TX-CB faceplate.
NOTE: The M/S and CHASSIS ID switches on the TX-CB faceplate must
always be set to S and 0.
•
Two RJ-45 ports labeled AUX and CIP on the TX-CB faceplate. These ports are not
used.
TX Matrix Host Subsystem Description on page 25•
• TX Matrix Host Subsystem LEDs on the Craft Interface on page 37
Table 8 on page 34 describes the functions of the LEDs on the faceplate of the TX-CB.
Table 8: TX-CB LEDs
DescriptionStateColorLabel
Control board is functioning as the master.On steadilyBlueMASTER
Control board has failed.On steadilyYellowFAIL
Control board is online and is functioning normally.On steadilyGreenOK
Control board is powering up, but not online.Blinking
Related
Documentation
TX Matrix Host Subsystem Description on page 25•
• TX Matrix Host Subsystem LEDs on the Craft Interface on page 37
• TX Matrix Control Board (TX-CB) Description on page 32
TX Matrix Craft Interface Overview
•
TX Matrix Craft Interface Overview on page 34
TX Matrix Craft Interface Overview
•
Craft Interface Front Panel on page 34
•
TX-SIB Online/Offline Buttons on page 35
•
LCD display and Navigation Buttons on page 35
Craft Interface Front Panel
The craft interface allows you to view status and troubleshooting information at a glance
and to perform many system control functions. It contains LEDs, buttons, and an LCD
display showing status messages for the TX Matrix router. The craft interface is located
on the lower front of the TX Matrix router below the air filter. It is hot-insertable and
hot-removable.
Each TX-SIB also has a button that you use to take the TX-SIB offline and bring it online.
The button is located next to the TX-SIB LEDs on the top of the craft interface.
LCD display and Navigation Buttons
A four-line LCD display is located in the craft interface, along with six navigation buttons.
The LCD display operates in two modes, as described in the following sections:
•
LCD Display Idle Mode on page 35
•
LCD Display Alarm Mode on page 35
LCD Display Idle Mode
During normaloperation, the LCD display operates in idle mode and reports current status
information, as shown in Figure 17 on page 35.
Figure 17: LCD display in Idle Mode
The lines in the display report the following information:
•
First line—TX Matrix router name.
•
Second line—Length of time the TX Matrix router has been running, reported in the
following form:
Up days + hours:minutes
•
Third and fourth lines—Status messages, which rotate at 2-second intervals. Some
conditions, such as removal or insertion of a system component, can interrupt the
messages.
To add a message that alternates every 2 seconds with the default status messages,
use the set chassis display message command. For more information, see the Junos OSSystem Basics and Services Command Reference.
LCD Display Alarm Mode
When a red or yellow alarm occurs, the LCD display switches to alarm mode and reports
about the alarm condition, as shown in Figure 18 on page 35.
The lines in the display report the following information:
•
First line—TX Matrix router name.
•
Second line—Number of active alarms.
•
Third and fourth lines—Individual alarm messages, with the most severe condition
shown first. Theprefix on each line indicates whether the alarm is ared (R)or yellow (Y)
alarm.
Related
Documentation
TX Matrix Chassis and Interface Alarm Messages Overview on page 209.•
• TX Matrix Alarm LEDs on the Craft Interface on page 36
• TX Matrix Host Subsystem LEDs on the Craft Interface on page 37
• TX Matrix TX-SIB LEDs on the Craft Interface on page 38
TX Matrix Craft Interface LED Overview
•
TX Matrix Alarm LEDs on the Craft Interface on page 36
•
Alarm Cutoff/Lamp Test Button on the Craft Interface on page 37
•
TX Matrix Host Subsystem LEDs on the Craft Interface on page 37
•
TX Matrix TX-SIB LEDs on the Craft Interface on page 38
TX Matrix Alarm LEDs on the Craft Interface
Two large alarm LEDs are located at the left of the craft interface (see Figure 19 on
page 36). Both LEDs can be lit simultaneously.
•
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.
Figure 19: Alarm LEDs on the Craft Interface
A condition that causes an LED to light also activates the corresponding alarm relay
contacton the connector interface panel (TX-CIP). The LCDdisplay on the craft interface
reports the cause of the alarm.
Table 9 on page 37 describes the alarm LEDs and alarm cutoff button in more detail.
Table 9: Alarm LEDs and Alarm Cutoff/Lamp Test Button
DescriptionStateColorShape
On steadilyRed
On steadilyYellow
Related
Documentation
Alarm Relay Contacts on page 40•
• TX Matrix Craft Interface Overview on page 34
• TX Matrix Chassis and Interface Alarm Messages Overview on page 209.
Alarm Cutoff/Lamp Test Button on the Craft Interface
The alarm cutoff/lamp test button (Figure 20 on page 37), which is located to the right
of the alarm LEDs, deactivates red and yellow alarms. It also causes all LEDs on the craft
interface to light (for testing) when pressed and held. Deactivating an alarm turns off
both LEDs and deactivates the device attached to the corresponding alarm relay contact
on the TX-CIP. However, the LCD display continues to report the alarm message until
you clear the condition that caused the alarm.
Figure 20: TX Matrix Alarm Cutoff/Lamp Test Button
Critical alarm LED—Indicates a critical condition that
can cause the TX Matrix router to stop functioning.
Possiblecauses include componentremoval, failure,
or overheating.
Warningalarm LED—Indicates aserious but nonfatal
error condition, such as a maintenance alert or a
significant increase in component temperature.
To deactivate red and yellow alarms, press the button labeled ACO/LT (for “alarm
cutoff/lamp test”).
Related
Documentation
TX Matrix Craft Interface Overview on page 34•
• TX Matrix Alarm LEDs on the Craft Interface on page 36
• TX Matrix Chassis and Interface Alarm Messages Overview on page 209.
TX Matrix Host Subsystem LEDs on the Craft Interface
Each host subsystem has three LEDs, located on the right of the craft interface, that
indicate its status. The LEDs labeled HOST 0 show the status of the Routing Engine in
slot RE0 and the TX-CB in slot CB0. The LEDs labeled HOST 1 show the status of the
Routing Engine in slot RE1 and the TX-CB in slot CB1. Table 10 on page 37 describes the
functions of the host subsystem LEDs.
Table 10: Host Subsystem LEDs
DescriptionStateColorLabel
Host is functioning as the master.On steadilyGreenMASTER
Host is online and is functioning normally.On steadilyGreenONLINE
Host is offline.On steadilyGreenOFFLINE
Related
Documentation
TX Matrix Host Subsystem Description on page 25•
• TX Matrix Control Board (TX-CB) LEDs on page 34
• TX Matrix RE-600 LEDs on page 28
• TX Matrix RE-1600 LEDs on page 30
• TX Matrix RE-2000 LEDs on page 32
TX Matrix TX-SIB LEDs on the Craft Interface
Each TX-SIB has three LEDs located along the top of the craft interface that indicate its
status. The corresponding TX-SIB slots are identified by the labels on the TX-SIB
online/offline buttons (SIB0 through SIB4). Table 11 on page 38 describes the functions
of the TX-SIB LEDs.
Table 11: TX-SIB LEDs on the Craft Interface
DescriptionStateColorLabel
TX-SIB is passing traffic.On steadilyGreenACTIVE
TX-SIB is not passing traffic.Off
TX-SIB is functioning normally.On steadilyGreenOK
TX-SIB is coming online.Blinking
TX-SIB has failed.On steadilyRedFAIL
Related
Documentation
TX Matrix Switch Interface Boards (TX-SIBs) Description on page 23•
The TX Matrix router contains one or two TX-CIPs—one for each Routing Engine—that
install vertically into the front left of the chassis in the slots labeled CIP0 and CIP1 (see
Figure 21 on page 39). The TX-CIPs are referred to as TX-CIP-0 and TX-CIP-1. The front
electrostatic discharge point is located near the bottom of the TX-CIP.
Each TX-CIP contains four RJ-45 ports labeled LCC0 through LCC3. These ports provide
T640 router control by connecting to T-CBs in up to four T640 routers through UTP
Category 5 Ethernet cables. TX-CIP-0 and TX-CIP-1 are used to connect to T-CB-0 and
T-CB-1 in each T640 router.
NOTE: The RJ-45 ports labeled LCC4 through LCC7 on a TX-CIP are reserved
for future use.
Each TX-CIP hasthree portsfor connecting the corresponding hostsubsystem to external
management devices (see Figure 21 on page 39). From these management devices, you
can use the CLI to configure the TX Matrix router. The ports on TX-CIP-0 connect to the
Routing Engine in slot RE0, and the ports on TX-CIP-1 connect to the Routing Engine in
slot RE1.
Alarm Relay Contacts
•
One 10/100-Mbps ETHERNETport for connecting toa management network—Connects
the Routing Engine through an Ethernet connection to a management LAN (or any
other device that plugs into an Ethernet connection) for out-of-band management.
The port uses an autosensing RJ-45 connector to support both 10- and 100-Mbps
connections. Two small LEDs on the left edge of the port indicate the connection in
use: the LED labeled ETHERNET lights yellow or green for a 10-Mbps or 100-Mbps
connection, and the LED labeled ACT lights green when traffic is passing through the
port.
NOTE: If a TX Matrix router contains two host subsystems, connect both
TX-CIPs to your external management network.
•
CONSOLE—One asynchronous serialport for connectingthe Routing Engine to a system
console through an RS-232 (EIA-232) serial cable.
•
AUXILIARY—One asynchronous serial port for connecting the Routing Engine to a
laptop, modem, or other auxiliary device through an RS-232 (EIA-232) serial cable.
Each TX-CIP hastwo alarm relay contacts—labeledRED ALARM and YELLOWALARM—for
connecting the TX Matrix router to external alarm devices (see Figure 21 on page 39).
Whenever a system condition triggers eitherthe redor yellow alarm on the craftinterface,
the alarm relay contacts are also activated. The alarm relay contacts are located below
the Routing Engine ports.
Related
Documentation
Control Plane Connections Between the TX Matrix Router and T640 Routeron page 10•
TX Matrix Two-Input 160-A Power Supply Overview on page 41
•
TX Matrix Two-Input 160-A DC Power Supply LEDs on page 43
•
TX Matrix Three-Input 240-A Power Supply Overview on page 44
•
TX Matrix Three-Input 240-A Power Supply LEDs on page 46
TX Matrix Power System Description
The TX Matrix router supports DC power only. The TX Matrix router has two load-sharing
DC power supplies, located at the lower rear of the chassis in slots PEM0 and PEM1 (top
to bottom). The power supplies connect to the midplane, which distributes the different
output voltages produced by the power supplies to the TX Matrix router components,
depending on their voltage requirements.
Each power supply has either an active circuitbreaker or an active current limiter for each
output voltage it provides. There are no passive fuses in the TX Matrix router that must
be replaced.
Chapter 3: TX Matrix Hardware Components Overview
Each power supply is cooled by its own internal cooling system.
The TX Matrix router supports these DC power supplies:
•
The two-input 160-A DC power supply is supported by Junos OS Release 5.3 and later.
•
The three-input 240-A DC power supply in 2-INPUT mode is supported by Junos OS
Release 9.2 and later.
NOTE: Mixing a two-input160-A powersupplyand a three-input240-A power
supply in the same chassis is not supported during normal operations.
Related
Documentation
TX Matrix Two-Input 160-A Power Supply Overview on page 41•
• TX Matrix Three-Input 240-A Power Supply Overview on page 44
• TX Matrix DC Power Supply Specifications on page 338
TX Matrix Two-Input 160-A Power Supply Overview
•
Two-Input 160-A DC Power Supply Description on page 41
•
Two-Input 160-A DC Power Supply Inputs on page 42
•
Two-Input 160-A DC Power Supply Load Sharing and Fault Tolerance on page 42
Two-Input 160-A DC Power Supply Description
Each two-input 160-ADC powersupply weighs approximately 23 lb (10.5 kg) and consists
of two inputs, two 80-A (@ –48 VDC) circuit breakers, a fan, and LEDs to monitor the
status of the power supply. Figure 22 on page 42 shows the two-input 160-A DC power
supply.
Figure 22: Two-Input 160-A DC Power Supply
Two-Input 160-A DC Power Supply Inputs
Each two-input 160-A 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 power supply in slot PEM0 must
be powered by dedicated power 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 12 on page 42 describes which components are powered by each input.
Table 12: TX Matrix Components Powered by Each Input
Provides Power to These ComponentsInput
SIBs in slot 2, 3, and 4INPUT 0
SIB in slots 0 and 1, control boards, Routing Engines,CIP, craft interface, and fan traysINPUT 1
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 13 on page 43 describes
the behavior of the two-input160-A DC power supply and router if one of the inputs fails.
Fault Tolerance When One Input Fails or Is DisconnectedRedundancy
Nonredundant power
supplies
If either input fails, the router shuts down.
NOTE: We recommend that you install redundant power supplies.
Chapter 3: TX Matrix Hardware Components Overview
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
TX Matrix Power System Description on page 41•
• TX Matrix Two-Input 160-A DC Power Supply LEDs on page 43
• Installing a TX Matrix Two-Input 160-A Power Supply on page 272
• Maintaining the Power Supplies on page 203
• TX Matrix DC Power Supply Specifications on page 338
TX Matrix 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 14 on page 43 describes the functions of the power supply LEDs.
Table 14: Two-Input 160-A DC Power Supply LEDs
DescriptionStateColorLED
Circuit breaker is on.On steadilyGreenCB OK
On steadilyYellowCB TRIP
Off
On steadilyYellowOVER TEMP
Off
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.
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.
Table 14: Two-Input 160-A DC Power Supply LEDs (continued)
DescriptionStateColorLED
On steadilyBlueDC OK
Blinking
Related
Documentation
TX Matrix Power System Description on page 41•
• Installing a TX Matrix Two-Input 160-A Power Supply on page 272
• Maintaining the Power Supplies on page 203
• Troubleshooting the TX Matrix Power System on page 213
• TX Matrix DC Power Supply Specifications on page 338
TX Matrix Three-Input 240-A Power Supply Overview
•
Three-Input 240-A DC Power Supply Description on page 44
•
Three-Input 240-A DC Power Supply Inputs on page 45
•
Three-Input 240-A DC Power Supply Load Sharing and Fault Tolerance on page 45
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.
Power supply is not powered on.Off
Three-Input 240-A DC Power Supply Description
Each three-input 240-ADC power supplyweighs approximately25 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 23 on page 45 shows the three-input 240-A DC power supply in
The three-input 240-A DC powersupply inputsare labeled INPUT0, 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 is required for the T640 router
and TX Matrix router.
Table 15 on page 45 describes which components are powered by each input.
Table 15: Components Powered by Each Three-Input 240-A DC Power
Supply Input
Three-Input ModeInput
INPUT 0
INPUT 2
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 load for thesystem.
A single power supply can provide full power foras long as the router is operational. Table
16 on page 46 describes the behavior of the power supply if one of the inputs fails.
T640-SIBs, T-CBs, fan trays, Routing
Engines, and FPCs in slots FPC0 and
Fault Tolerance When One Input Fails or is DisconnectedRedundancy
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.
Related
Documentation
Redundant power supplies
TX Matrix Power System Description on page 41•
• TX Matrix Three-Input 240-A Power Supply LEDs on page 46
• Installing a TX Matrix Three-Input 240-A DC Power Supply on page 279
• Maintaining the Power Supplies on page 203
• Troubleshooting the TX Matrix Power System on page 213
• TX Matrix DC Power Supply Specifications on page 338
TX Matrix Three-Input 240-A Power Supply LEDs
LEDs on each power supply faceplate (see Figure 24 on page 46) indicate the status of
the power supply. In addition, a power supply failure triggers the red alarm LED on the
craft interface. Table 17 on page 46 describes the functions of the power supply LEDs.
Figure 24: Three-Input 240-A DC Power Supply LEDs
Table 17 on page 46 describes the three-input 240-A DC power supply LEDs.
Table 17: Three-Input 240-A DC Power Supply LEDs
DescriptionStateColorLED
Circuit breaker is on.On steadilyGreenCB ON—One per
input
Off
Circuit breaker is not turned on, or
host subsystem has detected a
failure and has turned the circuit
breaker off.
Table 17: Three-Input 240-A DC Power Supply LEDs (continued)
DescriptionStateColorLED
Related
Documentation
power supply
PRESENT—One
per input
TEMP—One per
power supply
•
•
•
On steadilyBlueDC OK—One per
Blinking
On steadilyYellowOVER
Off
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.
TX Matrix Cooling System Overview
•
Cooling System Description on page 47
•
Fan Tray Description on page 48
•
Air Filter Description on page 49
Cooling System Description
The cooling system components work together to keep all TX Matrix router components
within the acceptable temperature range (see Figure 25 on page 48). 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.
To function properly, the entire cooling system requires an unobstructed airflow and
proper clearance around the site, as described in “TX Matrix Clearance Requirements for
Airflow and Hardware Maintenance” on page 63.
The cooling system consists of the following components:
•
Two front fan trays
•
Rear fan tray
•
Front air filter
•
Rear air filter
The TX Matrix router cooling system contains two front and one rear fan tray (see Figure
8 on page 20 and Figure 9 on page 21). The fan trays each contain multiple fans that
work in unison to cool the TX Matrix router components. The fan trays are hot-insertable
and hot-removable. Figure 25 onpage 48 shows the airflow through the TX Matrix router.
•
The front fan trays each contain six fans and are interchangeable with each other. The
front fan trays cool the components installed in the front card cage (the TX-SIBs,
TX-CIPs, and midplane).
•
The rear fan tray contains eight fans and is not interchangeable with the front trays.
The rear fan tray cools the components installed in the rear card cage (the Routing
Engines and TX-CBs).
•
Each power supply has one fan that cools that power supply.
When the TX Matrix router is operating normally, the fans function at lower than full
speed. The host subsystem constantly monitors the temperature detected by sensors
on the midplane and TX Matrix router components. If a fan fails or the ambient
temperature rises above a threshold, the host subsystem adjusts the speed of the
remaining fans tomaintain proper cooling and keepthe temperature withinthe acceptable
range. If the TX Matrix router temperature exceeds the acceptable maximum, the TX-CB
turns off the power supplies. A red alarm is triggered when a fan fails, and a yellow alarm
is triggered when a fan tray is removed.
CAUTION: To maintain proper cooling, do not operate the TX Matrix router
with the rear fan tray removed for more than 1 minute.
Air filters for both the front and rear fan trays help keep dust and other particles from
entering the cooling system. The TX Matrix router has one front air filter and one rear air
filter. The air filter is hot-insertable and hot-removable.
Related
Documentation
•
•
•
TX Matrix Cables Overview
•
Fiber-optic Array Cables on page 49
•
Ethernet cables on page 50
•
DB-9 Serial Cables on page 50
Fiber-optic Array Cables
The fiber-optic array cables connect the switching planes of the T640 routers to the
TX Matrix router by connecting the T640-SIBs to the TX-SIBs. Cable lengths from 3 m
to 100 m are supported to accommodate both centralized and distributed TX Matrix
configurations. The fiber-optic array connector is shown in Figure 26 on page 50.
You can order cable lengths of 4 m, 5 m, 6 m, and 12 m from Juniper Networks. If you
require cables longer than 12 m, you must order them directly from the manufacturer.
Contact your Juniper Networks representative for more information.
Ethernet cables
DB-9 Serial Cables
Related
Documentation
NOTE: A fiber-optic array connector is attached to each end of a fiber-optic
array cable and plugs into a fiber-optic array adapter on a TX-SIB and a
T640-SIB.
The UTP Category 5 Ethernet cables, which use straight-through wiring and RJ-45
connectors on each end, are used for controlling the T640 routers and for out-of-band
management of the routing matrix. Controlling the T640 routers requires connections
from the two TX-CIPs in the TX Matrix router to the T-CBs in the T640 routers.
Out-of-band management requires connections from the TX-CIPs to external
management devices.
These cables can be up to 100 m long.
The DB-9 serial cables are used to connect a system console or laptop computer to the
TX-CIPs for local management of the routing matrix.
Switching Plane Connections Between the TX Matrix Router and T640 Routers on
•
page 14
• TX Matrix Control Plane Cable Considerations on page 65
• TX Matrix Routing Matrix Hardware Configurations on page 58
• TX Matrix Fiber-Optic Array Cable Considerations on page 65
• Routing the TX Matrix Fiber-Optic Array Cables on page 111
The cable managementsystem consists ofthe comb panel assembly and the cableshelf
assembly.
Figure 27 on page 51 shows the TX Matrix cable management system.
Figure 27: Cable Management System
Chapter 3: TX Matrix Hardware Components Overview
The comb panel assembly, which installs immediately above the TX-SIBs, consists of
five combs—one comb above each TX-SIB. Each comb contains four teeth to organize
and provide strain relief to the four fiber-optic array cables connected to the TX-SIB
immediately below it. The fiber-optic array cables extend through the top of the cable
comb so that you can route the cables to the T640 routers.
The cable shelf assembly routes and supports the fiber-optic array cables over the top
of the TX Matrix router (see Figure 28 on page 52). The cable shelf assembly consists of
four parallel shelves. Each shelf is used to route five fiber-optic array cables—and
potentially a sixth spare cable—destined for a T640 router.
It is important to proceed through the installation process in the following order:
1. Review all the safety guidelines and warnings for the TX Matrix router.
2. Prepare your installation site.
See “Overview of Preparing the Site for the TX Matrix Router” on page 57.
3. Unpack the TX Matrix router and verify the parts received.
See “Overview of Unpacking the TX Matrix Router” on page 69.
4. Install the mounting hardware. The TX Matrix router can be installed in a four-post
rack or cabinet or an open-frame rack.
See “Installing the TX Matrix Mounting Hardware for a Four-Post Rack or Cabinet” on
page 75 or “Installing the TX Matrix Mounting Hardware for an Open-Frame Rack” on
page 79.
5. Install the TX Matrix chassis. See “Overview of Installing the TX Matrix Chassis” on
page 83
Because of the TX Matrix router's size and weight—up to 495 lb (225 kg) depending
on configuration—we strongly recommend thatyou installthe TX Matrix chassis using
a lift.
6. Install the TX Matrix cable management system.
See “Installing the TX Matrix Cable Shelf Assembly” on page 108 and “Installing the
TX Matrix Comb Panel Assembly” on page 107.
7. Connect the TX Matrix grounding cable.
See “Connecting the Grounding Cable to the TX Matrix Router” on page 109.
8. Route the TX Matrix fiber-optic array cables.
See “Routing the TX Matrix Fiber-Optic Array Cables” on page 111.
9. Connect the TX Matrix router to a management console so that you can monitor
powering on the router. Optionally, you can also connect to other external devices.
“TX Matrix Clearance Requirements for Airflowand Hardware Maintenance” onpage 63
See “Rack Requirements for TX Matrix Routers” on page 61.
8. If a rack is used, secure it to the floor and building structure.
See “Rack Requirements for TX Matrix Routers” on page 61.
9. 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 of cable
based on the distance between the hardware components being connected.
See “TX MatrixCablesOverview” onpage49 and“TX Matrix Fiber-OpticArray Cable
Considerations” on page 65.
10. Plan the cable routing and management.
“TX Matrix Fiber-Optic Array Cable Considerations” on page 65
TX Matrix Routing Matrix Hardware Configurations
•
Routing Matrix Configurations on page 58
•
Centralized Configuration on page 58
•
Distributed Configuration on page 59
Routing Matrix Configurations
A fully loaded routing matrix configuration consists of one TX Matrix router, four T640
routers, three to five 44-U, seismic-rated racks, 20 fiber-optic array cables, 10 Ethernet
cables, and a cable management system. There are two types of configurations to
consider when you plan and prepare forthe installation ofthe routingmatrix—centralized
and distributed.
Centralized Configuration
In the centralized configuration, three racks are placed next to each other in a row. Figure
29 on page 59 and Figure 30 on page 59 show a rack view and a top view of a centralized
configuration in which the left and center racks each hold two T640 routers, and the
right rack holds the TX Matrix router. In Figure 30 on page 59, each connection to a T640
router represents five fiber-optic array cables.
NOTE: In the configuration shown in Figure 29 on page 59, if the raceway is
less than 1 m above the racks, 5-m fiber-optic array cables are usually long
enough to connect the system.
In the centralized configuration, the total weight of the routing matrix and the heat it
generates are concentrated in a relatively small area. You must ensure that your site can
support the weight and your site cooling can adequately dissipate the heat. For physical
and environmental specifications, see Table 31 on page 333 and Table 32 on page 335.
Chapter 5: Preparing the Site for TX Matrix Router Installation
You can order the centralized configuration as a turnkey solution, or you can configure it
from existing T640 routers.
Figure 29: Centralized Configuration—Rack View
Figure 30: Centralized Configuration
Distributed Configuration
In the distributed configuration, the placement of the racks is more flexible. Ensure that
the rack placement allows you to connect the T640 routers to the TX Matrix router using
the fiber-optic array cables. The maximum cable length is 100 m. The total weight and
heat dissipation of the routing matrix are important in the distributed configuration, but
not as critical as in the centralized configuration. For physical and environmental
specifications, see Table 31 on page 333 and “TX Matrix Router Environmental
Specifications” on page 335.
Spacing of Mounting Bracket and Flange Holes on page 63
•
Connection to Building Structure on page 63
Rack Mounting Considerations
If you are installing a TX Matrix router, or a T640 router that you intend to integrate into
a routing matrix, consider these guidelines to facilitate the integration:
•
If you will be installing a fully configured centralized configuration, as described in
“Centralized Configuration” on page 58 (one TX Matrix router and four T640 routers),
plan to use a minimum of three racks side by side.
•
If you will be installing a fully configured distributed configuration, as described in
“Distributed Configuration” on page 59 (one TX Matrix router and four T640 routers),
plan to use one rack for the TX Matrix router, and two through four racks for the T640
routers (depending on whether you plan to install one or two T640 routers in a single
rack).
Chapter 5: Preparing the Site for TX Matrix Router Installation
•
•
•
Rack Size and Strength
The TX Matrix router is designed for installation in a rack that complies with either of the
following standards:
•
•
Account for the total weight of the routing matrix. One TX Matrix router and four
maximally configured T640 routers weigh approximately 2755 lb (1250 kg).
If you are installing the T640 router in the bottom of an empty rack, reserve the top of
the rack for the future installation of another T640 router.
We recommend that you install the TX Matrix router in its own dedicated rack. If you
must install another device in the rack, consider the height and weight of the TX Matrix
router and the fiber-optic array cable management above the chassis, including the
optional cable shelf assembly.
A 19-in.rack as definedin Cabinets,Racks, Panels, and Associated Equipment (document
number EIA-310-D) published by the Electronics Industry Association
(http://www.eia.org).
A 600-mm rack as defined in the four-part Equipment Engineering (EE); Europeantelecommunications standard for equipment practice (document numbers ETS 300
119-1 through 119-4) published bythe EuropeanTelecommunications Standards Institute
(http://www.etsi.org). The horizontal spacing between the rails in a rack that complies
with thisstandard isusually widerthan the TX Matrix router's mountingbrackets, which
measure 19 in. (48.3 cm) from outer edge to outer edge. Use approved wing devices
to narrow the opening between the rails as required.
The rack rails must be spaced widely enough to accommodate the TX Matrix chassis's
externaldimensions: 44.5in. (113.0 cm)high, 31.4 in.(79.8 cm) deep,and 17.4 in.(44.2cm)
wide. The outer edges of the mounting brackets extend the width to 19 in. (48.3 cm). The
spacing ofrails and adjacent racks mustalso allow forthe clearances around the TX Matrix
router and rack that are specified in “TX Matrix Clearance Requirements for Airflow and
Hardware Maintenance” on page 63.
In an open-frame rack, center-mounting is preferable to front-mounting because the
more even distribution of weight provides greater stability. If center-mounting is used,
you use the mounting brackets attached to the center of the chassis for rack mounting;
if front-mounting is used, you use the front-mounting flanges.
Before you mount the TX Matrix router in a four-post rack or cabinet, you must install the
spacer bars on the rack. For instructions aboutinstalling the mounting hardware, see
“Installing theTX Matrix Mounting Hardware for a Four-Post Rackor Cabinet”on page 75.
The chassis height of 44.5 in. (113.0 cm) is approximately 25.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 ElectronicsIndustry Association. You can stack one TX Matrix
router in a rack that has at least 25.4 U (44.5 in. or 113 cm) of usable vertical space.
The rack must be strong enough to support the weight of the fully configured TX Matrix
router, up to about 495 lb (225 kg).
Chapter 5: Preparing the Site for TX Matrix Router Installation
Figure 32: Typical Open-Frame Rack
Spacing of Mounting Bracket and Flange Holes
There are two sets of holes in the mounting brackets and front-mount flanges used to
attach the chassis to a rack. The holes within each set are spaced at 3 U (5.25 in. or
13.3 cm). The TX Matrix router can be mounted in any rack that provides holes spaced
at those distances.
Connection to Building Structure
Always securethe rackto the structure of the building. If your geographical area is subject
to earthquakes, bolt the rack to the floor. For maximum stability, also secure the rack to
ceiling brackets. For moreinformation, see “Rack-MountingRequirementsand Warnings”
on page 305.
Related
Documentation
TX Matrix Routing Matrix Hardware Configurations on page 58•
• Installation Safety Warnings for M Series, MX Series, and T Series Routers on page 304
TX Matrix Clearance Requirements for Airflow and Hardware Maintenance
When planning the installation site, allow sufficient clearance around the rack:
For the cooling system to function properly, the airflow around the chassis must be
unrestricted. Figure 33 on page 64 depicts the airflow in the TX Matrix router.
Figure 33: Airflow Through the Chassis
Related
Documentation
•
For service personnel to remove and install hardware components, there must be
adequate space at the front and back of the rack. Allow at least 30 in. (72.6 cm) in
front of the rack and 24 in. (61.0 cm) behind the rack (see Figure 34 on page 64).
Figure 34: Chassis Dimensions and Clearance Requirements
TX Matrix Cooling System Overview on page 47•
• Maintaining the TX Matrix Air Filters on page 194
The control plane connections between the T640 routers and the TX Matrix router are
provided by UTP Category 5 Ethernet cables between the RJ-45 ports on the TX-CIPs in
the TX Matrix router and the T-CBs in the T640 routers. The maximum length supported
is 100 m. The UTP Category 5 cables do not have to be the same length. The cable wiring
is straight-through (not crossover).
Chapter 5: Preparing the Site for TX Matrix Router Installation
Related
Documentation
TX Matrix Cables Overview on page 49•
• Control Plane Connections Between the TX Matrix Router and T640 Routeron page 10
TX Matrix Fiber-Optic Array Cable Considerations
The fiber-optic array cables connect the switching planes of the T640 routers to the
TX Matrix router by connecting the T640-SIBs to the TX-SIBs. When planning your
installation site, consider the following fiber-optic array cable requirements:
•
You must use the same length for every fiber-optic array cable from a particular T640
router to the TX Matrix router. However, you do not need to use the same length for all
fiber-optic array cables within a routing matrix. For example, if your routing matrix
contains two T640 routers, you can use 6-meter fiber-optic array cables to one router
and 100-meter fiber-optic array cables to the other router.
•
You must maintain a minimum bend radius of 2 in. (5.1 cm). We recommend that you
maintain a bend radius of 10 in. (25.4 cm). If you must bend a fiber-optic array cable
to a 2-inch radius, we recommend that you do not use more than two such bends.
•
Plastic wrap-ties can damage or crimp the fiber-optic array cables (see Figure 35 on
page 65). We recommend that you use soft band straps to secure fiber-optic array
cable.
Figure 35: Using Soft Band Straps to Secure Fiber-Optic Array Cables
•
The fiber-optic array cable connectors must fit through your site's cable conduits. For
the connector dimensions, see Figure 37 on page 67.
In addition, consider the following when planning your installation site:
Make sure any existing T640 routers are close enough to the location of the TX Matrix
router, particularly in a distributed configuration. Consider the length of the longest
fiber-optic array cables (100 meters), along with their routing through overhead
raceways and mounting racks.
•
When you plug a fiber-optic array cable into a T640-SIB, the cable extends toward
the left side of the T640 router (as viewed from the rear of the chassis) due to the
horizontal orientation of the connectors (see Figure 36 on page 66). To facilitate the
fiber-optic array cable routing, particularly in a centralized configuration, we recommend
that you install the TX Matrix router to the right of the T640 routers (as viewed from
the front of the chassis). This chassis placement might allow you to use shorter
fiber-optic array cables—such as 4 m or 5 m—and helps you manage the bend radius
of the cable. See “TX Matrix Routing Matrix Hardware Configurations” on page 58 for
an illustration of the recommended centralized configuration.
Figure 36: T640-SIB
•
Plan the management of the fiber-optic array cables between the T640 routers and
the TX Matrix router, keeping in mind the following considerations:
•
With four T640 routers, you can have atotal of 20 fiber-optic arraycables in a routing
matrix.
NOTE: We recommend that you purchase one additional fiber-optic
array cable for each T640 router in the TX Matrix router in case one of
the cables becomes damaged. Werecommend that you route the spare
cables when you route the main cables, particularly in a distributed
configuration.
•
The fiber-optic array cables must not interfere withTX Matrix routerand T640router
airflow and maintenance access. For an illustration of the TX Matrix router airflow,
see “TX Matrix Clearance Requirements for Airflow and Hardware Maintenance” on
page 63.
•
The fiber-optic array cable weighs 0.22 lb (0.10 kg) per meter and each cable
connector weighs 0.5 lb (0.23 kg).
•
With four T640 routers, you can have a total of 128 PICs in a routing matrix, and each
PIC can contain up to 10 cables (for example, the 10-port Gigabit Ethernet PIC), for
a total of 1,280 cables.Consider PICcabling aspart ofyour overall cable management