Juniper Networks, the Juniper Networks logo, Junos, NetScreen, ScreenOS, and Steel-Belted Radius are registered trademarks of Juniper
Networks, Inc. in the United States and other countries. JunosE is a trademark 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
Editing: Fran Mues
Illustration: Faith Bradford Brown
Cover Design: Edmonds Design
Revision History
August 2010—Corporate rebranding.
January 2010—For Junos OS Release 10.1, added procedures for upgrading and integrating an operational T1600 router into the routing
matrix.
October 2009—Added that Junos OS Release 9.6R2 is the first supported release for the TX Matrix Plus and T1600 routers in a routing
matrix. For Junos OS Release 10.0, added support for nonstop activing routing.
August 2009—Initial release.
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)).
Junos OS Documentation and Release Notes on page xxix
•
Objectives on page xxix
•
Audience on page xxx
•
Documentation Conventions on page xxx
•
Documentation Feedback on page xxxi
•
Requesting Technical Support on page xxxii
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 Plus Router. It
explains how to prepare your site for router installation, unpack and install the hardware,
power on the router, perform initial software configuration, and perform routine
maintenance. After completing the installation and basic configuration procedures
covered in this documentation, see the Junos OS configuration guides for information
about further Junos OS configuration.
NOTE: For additional information about Juniper Networks routers and the
Physical Interface Cards (PICs) they support—either corrections to or
informationthat 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 xxx defines the notice icons used in this guide.
Table 1: Notice Icons
DescriptionMeaningIcon
Indicates important features or instructions.Informational note
Table 2 on page xxx 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 TX Matrix Plus router is the centralized switch fabric of the routing matrix, which is
a multiterabit routing system for interconnecting T1600 routers. Each T1600 router
connectedto theTX MatrixPlus router adds1.6 terabits per second (Tbps)of nonblocking
subscriber switching capacity to the routing matrix. Currently, the TX Matrix Plus router
supports connections to up to four T1600 routers.
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, GigabitEthernet, 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.
The router architecture cleanly separates control operations from packet-forwarding
operations. This design eliminates processing and traffic bottlenecks, permitting the
routing matrix to achieve terabit performance levels. Control operations in the routing
matrix are performed by the host subsystem, which runs Junos OS to handle traffic
engineering andconfigurationmanagement. High availability, interchassis communications
are provided by an Ethernet LAN that interconnects the host subsystems in the TX Matrix
Plus router and the T1600 routers.
The TX Matrix Plus router is a modular, rack-mountable system that can be installed in
one standard 23-in. wide, 78-in. high, EIA telco rack.
The routing matrix consists of the following components:
Interchassis fiber-optic array cables that connect the TX Matrix Plus router and T1600
router
•
Interchassis UTP Category 5 Ethernet cables that connect the TX Matrix Plus router
and T1600 router control planes
•
Cable management system for the fiber-optic array cables
•
Equipment racks for the TX Matrix Plus router and T1600 routers
Switch Interface Boards (TXP-F13 SIBs) in the TX Matrix Plus router connect with the
SIBs in the T1600 routers (TXP-T1600 SIBs) to create a high-speed switch fabric. You
manage the routing matrix by connecting the TXP-CB in the TX Matrix Plus router to
external management devices.
Figure 1 on page 4 shows a routing matrix that connects to four T1600 routers.
Figure 1: Routing Matrix
Documentation
Related
NOTE: A TX Matrix Plus router is also referred to as a switch-fabric chassis
(SFC). The command-line interface (CLI) uses sfc to refer to the TX Matrix
Plus router. A T1600 router in a routing matrix is also referredto as a line-cardchassis (LCC). The CLI and some labels on TX Matrix Plus router hardware
• Connecting the TX Matrix PlusRouter to External Alarm-Reporting Devices on page 162
• Routing Matrix with a TX Matrix Plus Router System Architecture on page 55
• Routing Matrix with a TX Matrix Plus Router System Control Plane Architecture on
components use LCC or lcc to refer to a specific T1600 router.
This chapter provides an overview of the TX Matrix Plus router hardware components:
•
TX Matrix Plus Component Redundancy on page 7
•
TX Matrix Plus Switch-Fabric Chassis Description on page 8
•
TX Matrix Plus Midplane Description on page 11
•
TX Matrix Plus Switch Interface Boards Overview on page 13
•
TX Matrix Plus Host Subsystem Overview on page 20
•
TX Matrix Plus Craft Interface Overview on page 30
•
TX Matrix Plus Craft Interface LED Overview on page 32
•
TX Matrix Plus Connector Interface Panel Overview on page 36
•
TX Matrix Plus Power System Overview on page 41
•
TX Matrix Plus Cooling System Overview on page 45
•
TX Matrix Plus Cables Overview on page 48
•
TX Matrix Plus Rear Cable Management System on page 49
•
TX Matrix Plus Front Cable Manager on page 53
TX Matrix Plus Component Redundancy
The TX Matrix Plus router is designed so that no single point of failure can cause the
entire system to fail. The following major hardware components are redundant:
•
Data Switching Planes—In the TXMatrix Plus router, one data switching plane consists
of oneor two TXP-F13SIBs connected internally through the midplane to fourTXP-F2S
SIBs. For the TXP-4 configuration, there are a total of five data switching planes in the
routing matrix. One of the five data switching planes acts as a backup spare to the
remaining data switching planes. If faults are detected in an active data switching
plane, the plane is taken offline, and the backup spare plane is brought online. When
a failed component is replaced and brought online, the data switching plane in which
it resides becomes the new backup spare plane.
•
Host subsystem—The hostsubsystem consists of a RoutingEngine functioningtogether
with a TXP-CB. The TX Matrix Plus router can have one or two host subsystems. To
operate, each host subsystem requires a Routing Engine installed directly into the
TXP-CB. If two host subsystems are installed, one functions as the master and the
other functions as the backup.
If the master host subsystem (or either of its components) fails, the backup can take
over as the master. For information about the effect of taking the host subsystem
offline, see “Taking the Host Subsystem Offline” on page 354. For more information
about high availability features, see the Junos OS High Availability Configuration Guide.
•
TXP-CIPs—The TX Matrix Plus router has two TXP-CIPs. Each TXP-CIP provides the
ports for the control plane connections to the Control Boards (LCC-CBs) in up to four
T1600 routers.
If the master TXP-CIP fails, the backup TXP-CIP provides redundant connections to
the active host subsystem in the TX Matrix Plus router and the active LCC-CBs in the
T1600 routers. In this case, the Routing Engines in the TX Matrix Plus router and T1600
routers do not perform a switchover to their backups.
NOTE: The remaining ports are reserved for future use.
•
Power supplies—The TX Matrix Plus 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 Plus 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 Plus router
indefinitely.
Related
Documentation
Routing Matrix with a TX Matrix Plus Router System Architecture on page 55•
• Routing Matrix with a TX Matrix Plus Router System Control Plane Architecture on
page 56
• Routing Matrix with a TX Matrix Plus Router Switch Fabric and Switching Plane
Architecture on page 60
TX Matrix Plus Switch-Fabric Chassis Description
The TX Matrix Plus switch-fabric chassis is a rigid sheet metal structure that houses all
the other system components (see Figure 2 on page 10 and Figure 3 on page 11). The
chassis measures 52 in. (132.1 cm or approximately 29.7 U) high, 21.4 in. (54.4 cm) wide,
and 36.2 in. (91.9 cm) deep. The cable management systemcomb assembly that installs
on top of the chassis adds 17 in. (43.2 cm or approximately 9.7 U) to the height. You can
install a TX Matrix Plus router in a rack that has at least 39.4 U of usable vertical space.
The cable management system on the rear of the chassis adds 9 in. (22.86 cm) to the
depth. The chassis installs into 23-in. equipment racks or telco racks. One TX Matrix Plus
router can be installed into a (44-U) rack, if the rack can handle the maximum
configuration weight of 925 lb (420 kg).
Chapter 2: TX Matrix Plus Hardware Component Overview
The chassis includes the following features (see Figure 2 on page 10 and Figure 3 on
page 11):
•
A pair of metal front-mounting flanges used to mount the chassis in a four-post rack.
•
A pair of metal center-mounting brackets used to mount the chassis in an open-frame
rack.
•
Upper andlower handles on each side to facilitate positioningthe TXMatrix Plusrouter
in the rack. Do not use the handles to lift the TX Matrix Plus router.
•
Four electrostatic discharge points (banana plug receptacles), two in the front above
and below the left front air filters and two in the rear near the right rear fan trays.
WARNING: Before removing or installing components of a TX Matrix Plus
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 Plus router.
TheTX Matrix Plusrouter must be connectedto earthground during normal
operation.
Chapter 2: TX Matrix Plus Hardware Component Overview
Figure 3: Rear View of the TX Matrix Plus Router
Related
Documentation
Rack Requirements for a TX Matrix Plus Router on page 106•
• TX Matrix Plus Router Physical Specifications on page 431
• TX Matrix Plus Chassis Grounding Specifications on page 440
TX Matrix Plus Midplane Description
The midplane is located in the center of the chassis and forms the rear of the TXP-F2
SIB card cage (see Figure 4 on page 12). The TXP-F2S SIBs, TXP-CIPS, TXP-CBs, and
Routing Engines install into the midplane from the front of the chassis, and the TXP-F13
SIBs installinto themidplane fromthe rear of the chassis. The power supplies and cooling
system components also connect to the midplane.
TX Matrix Plus Switch Interface Boards Description on page 13
•
TX Matrix Plus TXP-F13 SIB Overview on page 13
•
TX Matrix Plus TXP-F13 SIB LEDs on page 15
•
TX Matrix Plus TXP-F2S SIB Overview on page 17
•
TX Matrix Plus TXP-F2S SIB LEDs on page 19
TX Matrix Plus Switch Interface Boards Description
The TX Matrix Plus Router containsTXP-F13 SIBsand TXP-F2SSIBs thatconnect together
through the midplane to create the switch fabric for the TX Matrix Plus router.
Chapter 2: TX Matrix Plus Hardware Component Overview
Related
Documentation
TX Matrix Plus TXP-F13 SIB Overview on page 13•
• TX Matrix Plus TXP-F2S SIB Overview on page 17
• Routing Matrix with a TX Matrix Plus Router Switch Fabric and Switching Plane
Architecture on page 60
TX Matrix Plus TXP-F13 SIB Overview
•
TXP-F13 SIB Description on page 13
•
TXP-F13 SIB Slots on page 14
TXP-F13 SIB Description
TXP-F13 SIBs are hot-removable and hot-insertable (see Figure 5 on page 13).
Figure 5: TXP-F13 SIB
Each TXP-F13 SIB consists of the following components:
•
Switch Fabric ASICs.
•
High-speed electrical links through the midplane to the TXP-F2S SIBs on the same
switching plane.
These components are located on the TXP-F13 faceplate:
•
Eight high-speed fiber-optic links connect to two T1600 routers in the routing matrix.
The left four ports are labeled EVEN and provide connections to one even-numbered
LCC—LCC0 or LCC2.The right four ports are labeled ODD and provide connections to
one odd-numbered LCC—LCC1 or LCC3. The four ports on each side are labeled CBL
A, CBL B, CBL C and CBL D.
•
Three ONLINE/OFFLINE buttons are located in the middle of the TXP-F13 SIB.
•
•
•
•
Three status LEDs, labeled ACTIVE, OK and FAIL, located below the ONLINE/OFFLINE
buttons.
The ONLINE/OFFLINE button labled LCC EVEN brings the corresponding interface
and TXP-T1600 SIB on the even T1600 router online and offline.
The ONLINE/OFFLINE button labled LCC ODD brings the corresponding interface
and TXP-T1600 SIB on the odd T1600 router online and offline.
The ONLINE/OFFLINE button in the center labeled SIB brings the TXP-F13 SIB online
and offline.
•
Two port LEDs, labeled LINK and RxPWR, located to the right of each fiber-optic array
port.
Three LEDs, labeled OK , FAIL, and ACTIVE are located on the craft interface; they show
the status of the link to the T1600 router.
TXP-F13 SIB Slots
Sixteen horizontal TXP-F13 SIB slots numbered 0 through 15 (top to bottom) are located
in the rear of the TX Matrix Plus router. A TXP-4 configuration contains ten TXP-F13 SIBs,
two for each data switching plane. The remaining slots are unused.
The port LEDs are located next to the ports. Table 5 on page 16 describes the functions
of these LEDs.
DescriptionStateColorLabel
TXP-F13 SIB is in active mode and actively passing traffic.On steadilyGreenACTIVE
TXP-F13 SIB is either offline or not actively passing traffic.Off–
TXP-F13 SIB is functioning normally.On steadilyGreenOK
TXP-F13 SIB is offline or not seated properly.Off–
TXP-F13 SIB has failed.On steadilyYellowFAIL
No faults have been detected for the TXP-F13 SIB.Off–
Table 5: F13-SIB Port LEDs
On steadilyGreenLINK
Blinking
Blinking
On steadilyRed
Off–
On steadilyYellow
DescriptionStateColorLabel
The link between the TXP-F13 SIB port and the TXP-T1600 SIB
port has been established successfully.
The link between the TXP-F13 SIB port and the loopback
connector has been established successfully.
The link is being established.On steadilyYellow
The fiber-optic array cable might be connected to either the
wrong TXP-T1600 SIB port or wrong TXP-FI3 port.
The link between the TXP-F13 SIB port and the TXP-T1600 SIB
port failed. There might bea hardware problem, orthe fiber-optic
port or cable might need to be cleaned.
The cable is not connected on both sides, or either the TXP-F13
SIB or TXP-T1600 SIB is powered off.
Full optical power is being received.On steadilyGreenRxPWR
Diminished opticalpower isbeing received. The fiber-optic array
cable or the fiber-optic array port might need cleaning, or the
cable might be damaged.
Off–
No optical power has been received. The fiber-optic array cable
is not connected to the TXP-FI3 SIB port, or not connected to
the TXP-T1600 SIB port. If the cable is connected on both sides,
the cable might be cut.
Chapter 2: TX Matrix Plus Hardware Component Overview
Related
Documentation
Routing Matrix with a TX Matrix Plus Router Switch Fabric and Switching Plane
•
Architecture on page 60
• Maintaining the TX Matrix Plus SIBs on page 269
• Troubleshooting the TX Matrix Plus SIBs on page 294
• Troubleshooting the Switching Planes in the Routing Matrix on page 305
TX Matrix Plus TXP-F2S SIB Overview
•
TXP-F2S SIB Components on page 17
•
TXP-F2S SIB Slots on page 17
TXP-F2S SIB Components
TXP-F2S SIBs are hot-removable and hot-insertable (see Figure 7 on page 17).
Figure 7: TXP-F2S SIB
Each TXP-F2S SIB consists of the following components:
•
Switch Fabric ASICs.
•
High-speed links through the midplane to the TXP-FI3 SIBs.
These components are located on the TXP-F2S faceplate:
•
Three status LEDs—FAIL, OK, and ACTIVE .
•
One ONLINE/OFFLINE button located below the status LEDs.
TXP-F2S SIB Slots
Twenty vertical TXP-F2S SIB slots are located in the front of the TX Matrix Plus router.
A TXP-4 configuration contains four TXP-F2 SIBs for each data switching plane (see
Table 6 on page 18).
TX Matrix Plus Host Subsystem Description on page 20
•
TX Matrix Plus Control Board Description on page 20
•
TX Matrix Plus TXP-CB Overview on page 21
•
TX Matrix Plus TXP-CB LEDs on page 23
•
TX Matrix Plus Routing Engine Description on page 25
•
TX Matrix Plus RE-C2600 Routing Engine Overview on page 26
•
TX Matrix Plus RE-C2600 LEDs on page 28
TX Matrix Plus Host Subsystem Description
The host subsystem provides the routing and system management functions of the TX
Matrix Plus router. You can install one or two host subsystems on the TX Matrix Plus
router. A host subsystem consists of a Routing Engine installed directly into a slot in a
control board. To operate, each host subsystem functions as a unit; the Routing Engine
requires the corresponding control board, 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 CB0.
Related
Documentation
TX Matrix Plus Control Board Description on page 20•
• TX Matrix Plus TXP-CB Overview on page 21
• TX Matrix Plus Routing Engine Description on page 25
• TX Matrix Plus RE-C2600 Routing Engine Overview on page 26
TX Matrix Plus Control Board Description
You can install up to two control boards in the TX Matrix Plus Router. Control boards
install into the upper front of the chassis in the slots labeled CB0 and CB1 (referred to as
CB-0 and CB-1). A Routing Engine installs directly into a slot on each control board. The
control boards can not function if a Routing Engine is not present.
Each control board works with the Routing Engine to provide the following control and
monitoring functions for the TX Matrix Plus router:
•
Determining Routing Engine mastership
•
Controlling power and reset for the other TX Matrix Plus components
Chapter 2: TX Matrix Plus Hardware Component Overview
If the TX Matrix Plus router contains a redundant host subsystem, one TXP-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.
The TX Matrix Plus router supports the TXP-CB.
Related
Documentation
TX Matrix Plus Host Subsystem Description on page 20•
• TX Matrix Plus TXP-CB Overview on page 21
• TX Matrix Plus Routing Engine Description on page 25
TX Matrix Plus TXP-CB Overview
•
TXP-CB Description on page 21
•
Routing Engine Ports on the TXP-CB on page 23
TXP-CB Description
Each TXP-CB (see Figure 9 on page 22) works with the Routing Engine to provide the
following control and monitoring functions for the TX Matrix Plus router.
1-GB Ethernet switch used for intermodule communication.
•
PCI bus to the Routing Engines.
•
Switch Processor Mezzanine Board (SPMB).
These components are located on the TXP-CB faceplate:
•
Three Routing Engine ports—ETHERNET, CONSOLE, and AUXILIARY—located below
the Routing Engine,for connecting the Routing Engineto external managementdevices.
•
Two port LEDs—ETHERNET and ACT—located next to the ETHERNET port indicate the
port status and speed.
•
Three status LEDs—MASTER, FAIL, and OK— indicate the status of the TXP-CB.
•
Online/offline button, located below the status LEDs..
Chapter 2: TX Matrix Plus Hardware Component Overview
Routing Engine Ports on the TXP-CB
Each TXP-CB has a set of ports that you use to connect the Routing Engines to external
management devices (see Figure 19 on page 37). From these management devices, you
can use the CLI to configure and manage the TX Matrix Plus router.
The management ports on each TXP-CB connect to the Routing Engine iinstalled into
that TXP-CB. Each TXP-CB includes the following ports:
•
ETHERNET—10/100-Mbps/1-Gbps Ethernet port for connecting to a 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
management of the routing matrix. The port uses an autosensing RJ-45 connector to
support 10-Mbps, 100-Mbps, or 1-Gbps connections. Two small LEDs on the left edge
of the port indicate the connection in use.
•
CONSOLE—One asynchronous serial port for connecting to a console. Connects the
Routing Engine to a system console through an RS-232 (EIA-232) serial cable.
•
AUXILIARY—One asynchronous serial port for connecting toa modemor other auxiliary
device. Connects the Routing Engine to a laptop, modem, or other auxiliary device
through an RS-232 (EIA-232) serial cable.
Related
Documentation
TX Matrix Plus Host Subsystem Description on page 20•
• TX Matrix Plus TXP-CB LEDs on page 23
• TX Matrix Plus Routing Engine Description on page 25
• TX Matrix Plus Routing Engine Interface Cable Specifications on page 443
• RJ-45 Connector Pinouts for the TX Matrix Plus Routing Engine ETHERNET Port on
page 445
• RJ-45 Connector Pinouts for the TX Matrix Plus Routing Engine AUXILIARY and
CONSOLE Ports on page 446
TX Matrix Plus TXP-CB LEDs
The LEDs located on the bottom of the TXP-CB indicate its status. Table 8 on page 24
describes the functions of the TXP-CB LEDs.
NOTE: If a TX Matrix Plus routercontains twohost subsystems,connectboth
Chapter 2: TX Matrix Plus Hardware Component Overview
Table 8: TXP-CB LEDs (continued)
DescriptionStateColorLabel
1-Gbps connectionOn steadilyGreenETHERNET
10/100-Mbps connectionOn steadilyYellow
TXP-CB is offline.Off–
Traffic is passing through the port.On steadilyGreenACT
No traffic is passing through the port.Off–
Related
Documentation
TX Matrix Plus TXP-CB Overview on page 21•
• Maintaining the TX Matrix Plus TXP-CBs on page 268
• Troubleshooting the TX Matrix Plus Host Subsystem on page 311
• Troubleshooting the TX Matrix Plus TXP-CBs on page 311
TX Matrix Plus Routing Engine Description
You can install one or two Routing Engines in the TX Matrix Plus router. The Routing
Engines install into the control boards labeled CB0 and CB1. If two Routing Engines are
installed, one functions as the master and the other acts as the backup. If the master
Routing Engine failsor is removed andthe backupis configured appropriately, the backup
restarts and becomes the master.
NOTE: Nonstop active routing is supported for the TX Matrix Plus router in
Junos OS Release 10.0 and later.
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 T1600 routers. TheJunos kernel running on each T1600
Routing Engine copies its forwarding table to all Packet Forwarding Engines in the router.
The design of the ASICs allows the forwarding table in the Packet Forwarding Engine to
be updated without interrupting forwarding performance.
The TX Matrix Plus Routing Engines handle all routing protocols, as well as the software
processes that control the interfaces in the TX Matrix Plus router and user access to the
TX Matrix Plus router. All Routing Engines in the routing matrix run software processes
that control chassis components and system management.
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 Plusrouter supports functions such
as alarm handling and packet counting on every port, without degrading
packet-forwarding performance.
Related
Documentation
TX Matrix Plus Host Subsystem Description on page 20•
• TX Matrix Plus RE-C2600 Routing Engine Overview on page 26
• Routing Matrix with a TX Matrix Plus Router System Architecture on page 55
TX Matrix Plus RE-C2600 Routing Engine Overview
•
RE-C2600 Description on page 26
•
RE-C2600 Boot Sequence on page 28
RE-C2600 Description
Each RE-C2600 (shown in Figure 11 on page 27) consists of the following components:
•
CPU—Runs Junos OS to maintain the TX Matrix Plus routing tables and routing
protocols.
•
DRAM—Provides storage for the routing and forwarding tables and for other Routing
Engine processes.
•
EEPROM—Stores the serial number of the Routing Engine.
•
Interfaces for management access—Provide information about Routing Engine status
to the external management devices (console, laptop, or terminal server) connected
to the TXP Routing Engine ports located below the Routing Engine on the TXP-CB.
Chapter 2: TX Matrix Plus Hardware Component Overview
The faceplate of the RE-C2600 contains the following:
•
USB port USB—Provides a removable media interface through which you can install
the Junos OS manually. Junos supports USB versions 2.0 and 1.1.
•
CompactFlash card slot CF (shown in Figure 12 on page 28)—Provides primary storage
for software images, configuration files, and microcode.
•
Two solid-state disk slots SSD1 and SSD2 (shown in Figure 12 on page 28)—Provides
secondary storage for log files, memory dumps, and rebooting the system if the
CompactFlash card fails.
NOTE: SSD2 is not currently supported.
•
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—“TX Matrix Plus RE-C2600 LEDs” on page 28 describes the functions of these
LEDs.
NOTE: For specific information about Routing Engine components (for
example, the amount of DRAM), issue the show chassis routing-engine
command.
Figure 12: RE-C2600 CompactFlash Card and Solid-State Disk Slots
RE-C2600 Boot Sequence
The RE-C2600 boots from the storage media in this order: the USB device (if present),
the CompactFlash card CF (if present), the disk (if present) in slot 1 SSD1, the disk (if
present) in slot 2 SSD2, then the LAN.
Related
Documentation
Providing Power to a Seven-Input 420-A Power Supply on page 167•
• Maintaining the TX Matrix Plus Routing Engines on page 268
• Troubleshooting the TX Matrix Plus Host Subsystem on page 311
• Troubleshooting the TX Matrix Plus Routing Engines on page 312
TX Matrix Plus RE-C2600 LEDs
Four LEDs—ONLINE, CF, SSD1, and SSD2—indicate the status of the RE-C2600 (see
Figure 13 on page 29 and Table 15 on page 39).
TX Matrix Plus RE-C2600 Routing Engine Overview on page 26•
• Troubleshooting the TX Matrix Plus Host Subsystem on page 311
• Troubleshooting the TX Matrix Plus Routing Engines on page 312
TX Matrix Plus Craft Interface Overview
•
Craft Interface Front Panel on page 30
•
LCD Modes on page 31
•
LCD Navigation Buttons on page 32
•
Alarm Cutoff/Lamp Test Button on page 32
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 is hot-insertable and hot-removable.
The craft interface is located at the upper front of the TX Matrix Plus router.
Figure 14: Front Panel of the TX Matrix Plus Craft Interface
The front panel of the craft interface contains:
•
SFC chassis number.
•
Configuration (config) size.
•
A four-line LCD display, along with six navigation buttons. The LCD display operates
in Idle mode or alarm mode.
•
Yellow Minor Alarm LED, red Major Critical Alarm LED.
•
Alarm cutoff/lamp test ACO/LT button.
•
Chassis Status Master and Standby LEDs.
•
OK, FAIL, and ACT LEDs for each TXP-F13 SIB.
•
OK and FAIL LEDs for the front and rear fan trays.
Chapter 2: TX Matrix Plus Hardware Component Overview
•
LCD Display Idle Mode on page 31
•
LCD Display Alarm Mode on page 31
LCD Display Idle Mode
During normaloperation, the LCD display operates in idle mode and reports current status
information, as shown in Figure 15 on page 31.
Figure 15: LCD Display in Idle Mode
The lines in the display report the following information:
•
First line—TX Matrix Plus router name.
•
Second line—Length of time the TX Matrix Plus 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 Configuration Guide.
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 16 on page 31.
Figure 16: LCD Display in Alarm Mode
The lines in the display report the following information:
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.
LCD Navigation Buttons
The LCD Display has the following navigation buttons:
•
Menu button
•
Enter button
•
Four arrow buttons for scrolling up or down, and left or right
Alarm Cutoff/Lamp Test Button
The alarm cutoff/lamp test button labeled ACO/LT is located below the alarm LEDs.
Figure 17 on page 32 shows the alarm cutoff button.
Figure 17: Alarm Cutoff/Lamp Test Button
Use the ACO/LT button to deactivate the red and yellow alarms. Pressing the button
turns off both LEDs and deactivates the device attached to the corresponding alarm
relay contact on the TXP-CIP. However, the LCD display continues to report the alarm
message until the condition that caused the alarm is cleared.
To test the LEDs on the craft interface, press and hold the ACO/LT button. All the LEDs
on the craft interface should light.
Related
Documentation
Deactivating Alarms on the TX Matrix Plus Craft Interface on page 279•
• Displaying TX Matrix Plus SFC and LCC Alarm Messages Information on page 280
• Alarm LEDs on the TX Matrix Plus Craft Interface on page 33
• Chassis Status LEDs on the TX Matrix Plus Craft Interface on page 34
• TXP-F13 SIB LEDs on the TX Matrix Plus Craft Interface on page 34
• Fan Tray LEDs on the TX Matrix Plus Craft Interface on page 35
• Power Supply LEDs on the TX Matrix Plus Craft Interface on page 35
TX Matrix Plus Craft Interface LED Overview
•
Alarm LEDs on the TX Matrix Plus Craft Interface on page 33
•
Chassis Status LEDs on the TX Matrix Plus Craft Interface on page 34
•
TXP-F13 SIB LEDs on the TX Matrix Plus Craft Interface on page 34
Fan Tray LEDs on the TX Matrix Plus Craft Interface on page 35
•
Power Supply LEDs on the TX Matrix Plus Craft Interface on page 35
Alarm LEDs on the TX Matrix Plus Craft Interface
Two large alarm LEDs are located on the craft interface (see Figure 18 on page 33) Both
LEDs can be lit simultaneously.
Figure 18: Alarm LEDs on the TX Matrix Plus Craft Interface
Chapter 2: TX Matrix Plus Hardware Component Overview
Related
Documentation
•
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.
The LCD display on the craft interface reports the cause of the alarm. A condition that
causes an alarm LED to light also activates the corresponding alarm relay contact on
the connector interface panel (TXP-CIP).
Table 10 on page 33 describes the alarm LEDs.
Table 10: Alarm LEDs on the TX Matrix Plus Craft Interface
DescriptionStateColorShape
On steadilyRed
On steadilyYellow
TX Matrix Plus TXP-CIP Overview on page 36•
• TX Matrix Plus Craft Interface Overview on page 30
• Deactivating Alarms on the TX Matrix Plus Craft Interface on page 279
Critical alarm LED—Indicates a critical condition that
can cause the TX Matrix Plus router to stop
functioning. Possible causes include component
removal, failure, or overheating.
Warningalarm LED—Indicates aserious but nonfatal
error condition, such as a maintenance alert or a
significant increase in component temperature.
• Displaying TX Matrix Plus SFC and LCC Alarm Messages Information on page 280
Chassis Status LEDs on the TX Matrix Plus Craft Interface
Two LEDs located in the middle of craft interface below the Alarm LEDs indicate whether
the TX Matrix Plus router is functioning as the master for the routing matrix. Table 11 on
page 34 describes the functions of the Chassis Status LEDs.
Table 11: Chassis Status LEDs on the TX Matrix Plus Craft Interface
DescriptionStateColorLabel
On steadilyGreenMASTER
Off–
STANDBY
NOTE: This LED is reserved for future use.
Related
Documentation
TX Matrix Plus Switch-Fabric Chassis Description on page 8•
• TX Matrix Plus Craft Interface Overview on page 30
TXP-F13 SIB LEDs on the TX Matrix Plus Craft Interface
The right side of the craft interface has three LEDs for each TXP-F13 SIB that indicate
the status of that SIB. The corresponding TXP-F13 SIB slots are labeled 0 through 15.
Table 12 on page 34 describes the functions of the TXP-F13 SIB LEDs.
Table 12: TXP-F13 SIB LEDs on the TX Matrix Plus Craft Interface
The TX Matrix Plus routeris functioning asthe master
SFC for the routing matrix. For the A4 configuration,
this LED should always be lit when the router is
receiving power.
For the A4 configuration, the TX Matrix Plus router
might not be receiving power.
DescriptionStateColorLabel
TXP-F13 SIB is functioning normally.On steadilyGreenOK
TXP-F13 SIB is coming online.Blinking
TXP-F13 SIB is not functioning normally.Off–
TXP-F13 SIB has failed.On steadilyRedFAIL
No faults have been detected for the TXP-F13 SIB.Off–
On steadilyGreenACTIVE
Off–
TXP-F13 SIB is in active mode and actively passing
traffic.
TXP-F13 SIB is either offline or not actively passing
traffic.
• TX Matrix Plus Seven-Input 420-A Power Supply LEDs on page 43
• Troubleshooting the TX Matrix Plus Power System on page 290
TX Matrix Plus Connector Interface Panel Overview
•
TX Matrix Plus Connector Interface Panel Description on page 36
•
TX Matrix Plus TXP-CIP Overview on page 36
•
TX Matrix Plus TXP-CIP LEDs on page 39
TX Matrix Plus Connector Interface Panel Description
The TX Matrix Plus routercontains two connector interface panels—onefor eachRouting
Engine—that install vertically belowthe host subsystem intothe front right of the chassis
in the slots labeled CIP0 and CIP1.
The TX Matrix Plus router supports the TXP-CIP.
Related
Documentation
TX Matrix Plus Router Description on page 3•
• TX Matrix Plus TXP-CIP Overview on page 36
• TX Matrix Plus TXP-CIP LEDs on page 39
TX Matrix Plus TXP-CIP Overview
•
TXP-CIP Components on page 36
•
TXP-CIP Ports on page 37
•
TXP-CIP Alarm Relay Contacts on page 38
TXP-CIP Components
The TXP-CIPs (see Figure 19 on page 37) are referred to as TXP-CIP-0 and TXP-CIP-1.
Chapter 2: TX Matrix Plus Hardware Component Overview
Each TXP-CIP houses:
•
Ports for connections to the LCC control plane, SFC control plane, and other devices.
NOTE: The SFC control plane ports are reserved for future use.
•
Alarm relay contacts
•
Three LEDs—ACTIVE, OK, FAIL— that indicate the status of the TXP-CIP.
•
ACT and SPEED port LEDs for the LCC CTRL PLANE ports 0 through 15
•
Port LEDs for the reserved ports 16 and 17
•
ACT and LINK port LEDs for the SFC CTRL PLANE ports XGE0 through XGE4
The TXP-CIPs are hot-removable and hot-insertable.
TXP-CIP Ports
LCC Control Plane Ports
Control plane connections to the T1600 routers in the routing matrix are provided by
sixteen 10/100/1000 Base-T copper RJ-45 LCC control plane ports labeled LCC CTRL
PLANE 0 through 15 on the TXP-CIP. UTP Category 5E Ethernet cables connect the LCC
CTRL PLANE ports in TXP-CIP-0 and TXP-CIP-1 to the LCC-CBs LCC-CB-0 and LCC-CB-1
in each T1600 router. For more information about connecting TXP-CIPs to LCC-CBs, see
“Control Plane Connections from the TX Matrix Plus Router to the T1600 Routers” on
page 58.
Reserved Ports
Each TXP-CIP contains two copper RJ-45 ports, labeled 16 and 17,that are reserved for
future use.
SFC Control Plane Ports
Each TXP-CIP contains five 10-Gigabit Ethernet SFP+ ports labeled SFC CTRL PLANE
XGE0 through XGE4.
NOTE: The ports labeled 4 through 15 on a TXP-CIP are reserved for future
use.
NOTE: These ports are reserved for future use.
Related
Documentation
TXP-CIP Alarm Relay Contacts
Each TXP-CIP has two alarm relay contacts—labeled RED ALARM and YELLOW ALARM
(see Figure 19 on page 37), located on the bottom of the TXP-CIP. You can connect the
TX Matrix Plus router to external alarm-reporting devices by attaching wires to the alarm
relay contacts.
NOTE: If your TX Matrix Plus router contains two host subsystems, we
recommend that you connect each relay contact on each TXP-CIP to a
separate reporting device.
The terminal blocks that plug into the alarm relay contacts are supplied with the TX
Matrix Plus router. They accept wire of any gauge between 28-AWG and 14-AWG (0.08
and 2.08 mm2), which is not provided. Use the wire gauge appropriate for the external
device you are connecting.
Whenever a system condition triggers eitherthe redor yellow alarm on the craftinterface,
the corresponding alarm relay contacts are also activated. The alarms on TXP-CIP-0and
TXP-CIP-1 correspond to the Routing Engines installed into the TXP-CBs in slots CB0
and CB1.
TX Matrix Plus TXP-CIP LEDs on page 39•
• Troubleshooting the TX Matrix Plus TXP-CIPs on page 309
• Replacing a TX Matrix Plus TXP-CIP on page 327
• TX Matrix Plus Alarm Relay Contact Wire Specifications on page 444
TX Matrix Plus Power System Description on page 41
•
TX Matrix Plus Seven-Input 420-A Power Supplies Overview on page 41
•
TX Matrix Plus Seven-Input 420-A Power Supply LEDs on page 43
TX Matrix Plus Power System Description
The TX Matrix Plus router supports DC power only. The router has two load-sharing DC
power supplies located at the lower rear of the chassis in slots PEM0 and PEM1 (left to
right). The powersupplies connectto themidplane, which distributes the different output
voltages produced by the power supplies to the TX Matrix Plus components, depending
on their voltage requirements.
There are no passive fuses in the TX Matrix Plus router that must be replaced.
The TX Matrix Plus router supports the seven-input 420-A power supply.
Chapter 2: TX Matrix Plus Hardware Component Overview
Related
Documentation
TX Matrix Plus Switch-Fabric Chassis Description on page 8•
• TX Matrix Plus Seven-Input 420-A Power Supplies Overview on page 41
• TX Matrix Plus Power Specifications on page 435
• TX Matrix Plus Router Power Requirements on page 436
• TX Matrix Plus DC Power Cable and Cable Lug Specifications on page 438
• TX Matrix Plus Power Distribution on page 439
TX Matrix Plus Seven-Input 420-A Power Supplies Overview
•
Seven-Input 420-A Power Supplies Description on page 41
•
Seven-Input 420-A Power Supply Load Sharing and Fault Tolerance on page 42
Seven-Input 420-A Power Supplies Description
Each seven-input 420-A power supply consists of a removable input power tray with
seven inputs (Figure 21 on page 42),seven 60-Acircuit breakers, afan (each power supply
is cooled by its own internalcooling system), andLEDs tomonitor thestatus ofthe power
supply.
Each seven-input 420-A power supply weighs approximately 35.5 lb (16.1 kg). The input
power tray weighs 3.7 lb (1.7 kg).
Figure 20 on page 42 shows the seven-input 420-A power supply.
Figure 20: TX Matrix Plus Seven-Input 420-A Power Supply with Input
Power Tray Removed
Figure 21: TX Matrix Plus Input Power Tray
Related
Documentation
Seven-Input 420-A Power Supply Load Sharing and Fault Tolerance
When the TX Matrix Plus router is operating normally and both power supplies are
switched on, load sharing between them occurs automatically. When one power supply
fails or is turned off, the other power supply immediately assumes the entire electrical
load for the system. A single power supply can provide full power for as long as the TX
Matrix Plus router is operational. Table 17 on page 42 describes the behaviorof the power
supply if an input fails.
Fault Tolerance When One Input Fails or Is DisconnectedRedundancy
Nonredundant power
supply
Redundantpowersupplies
TX Matrix Plus Power System Description on page 41•
• TX Matrix Plus Seven-Input 420-A Power Supply LEDs on page 43
• Maintaining the TX Matrix Plus Power Supplies on page 268
NOTE: Redundant power supplies are required for the TX Matrix
Plus router. A nonredundant power supply is not supported.
If inputs 0 through 4 fail, the TX Matrix Plus router shuts down.
If aninput onone powersupply fails, theother power supply assumes
the electrical loadfor allinputs. If one inputon the other power supply
is not functional, the TX Matrix Plus router shuts down.
• Troubleshooting the TX Matrix Plus Power System on page 290
g004516
DC power supply LEDs
• TX Matrix Plus Power Specifications on page 435
• TX Matrix Plus DC Power Cable and Cable Lug Specifications on page 438
TX Matrix Plus Seven-Input 420-A Power Supply LEDs
The LEDs on the faceplate of each power supply (see Figure 22 on page 43) indicate the
status of the power supply. The PEM OK, FAULT, INPUT PRESENT, and PWR ON LEDs are
located on the faceplate of the power supply. Additionally, the input power tray contains
seven INPUT PRESENT LEDs, which are visible when the input power tray is removed
from the power supply. A power supply failure also triggers the red alarm LED on the
craft interface.
Figure 22: TX Matrix Plus Seven-Input 420-A Power Supply LEDs
Chapter 2: TX Matrix Plus Hardware Component Overview
Table 18 on page 43describes theseven-input 420-Apower supply LEDs on the faceplate.
Table 18: TX Matrix Plus Seven-Input 420-A Power Supply LEDs
Table 18: TX Matrix Plus Seven-Input 420-A Power Supply LEDs (continued)
DescriptionStateColorLED
Circuit breaker is powered on.On steadilyGreenPWR ON—One
per input
Circuit breaker is not powered on. The circuit breaker might have
been turned off, the host subsystem detected a failure and turned
off thecircuit breaker, or the power supplyis not receiving anyinput
voltage.
Power supply is functioning normally.On steadilyBluePEM OK—One
Power supply might be starting up or not receiving any input
voltage. The circuit breakers might be off, or a fault has occurred.
per power
supply
Off–
Off–
power supply
On steadilyYellowFAULT—One per
Power supply might be starting up, not properly installed, not
receiving sufficient power, or not functioning properly. Inputs 0
through 4 might have failed.
Off–
No faults have been detected for the power supply, or the power
supply is not receiving any input voltage.
Table 18 on page 43 describes the seven-input 420-A power supply LEDs (shown in
Figure 23 on page 44) that are visible on the input power tray after it has been removed
from the power supply.
Figure 23: Seven-Input 420-A Power Supply LEDs
Table 19: TX Matrix Plus Seven-Input 420-A Power Supply LEDs on the Input Power Tray
Chapter 2: TX Matrix Plus Hardware Component Overview
Related
Documentation
TX Matrix Plus Power System Description on page 41•
• TX Matrix Plus Seven-Input 420-A Power Supplies Overview on page 41
• Power Supply LEDs on the TX Matrix Plus Craft Interface on page 35
• Troubleshooting the TX Matrix Plus Power System on page 290
TX Matrix Plus Cooling System Overview
•
Cooling System Description on page 45
•
Fan Trays on page 46
•
Air Filters on page 47
Cooling System Description
The cooling system components work together to keep all TX Matrix Plus components
within the acceptable temperature range (see Figure 24 on page 45).
To function properly, the entire cooling system requires an unobstructed airflow and
proper clearance around the site. Figure 24 on page 45 shows the airflow through the
router.
Figure 24: Airflow Through the TX Matrix Plus Chassis
The cooling system consists of the following components:
The TX Matrix Plus router contains two front fan trays and four rear fan trays. The fan
trays are hot-insertable and hot-removable. In addition, each power supply has two fans
that cools that power supply.
Each fan tray contains multiple fans that work in unison to cool the TX Matrix Plus
components. When the router is operating normally, the fans function at lower than full
speed. If a fan fails or the ambient temperature rises above a threshold, the speed of the
remaining fans is automatically adjusted to keep the temperature within the acceptable
range and to maintain proper cooling. If the ambient maximum temperature specification
is exceededand thesystem cannot beadequatelycooled,the Routing Engineshuts down
some or all of the hardware components. A red alarm is triggered when a fan fails, and
a yellow alarm is triggered when a fan tray is removed.
The front fan trays, installed horizontally in the front of the chassis, cool the components
installed in the front card cage (the TXP-F2 SIBs, TXP-CIPs, TXP-CBs, and Routing
Engines). Each front fan traycontains six fans. The twofront fan trays are interchangeable
with each other, but are not interchangeable with the front fan trays.
CAUTION: The two front fan trays work as a pair. To avoid damage to the
router, do not remove more than one of the two front fan trays at a time. If
you remove both front fan trays, the router might shut down.
The rear fan trays install vertically in the rear of the chassis, and cool the components
installed in the rear card cage (TXP-F13 SIBs). Each rear fan tray contains nine fans
(shown in Figure 25 on page 47). The four rear fan trays are interchangeable with each
other.
Chapter 2: TX Matrix Plus Hardware Component Overview
Figure 25: TX Matrix Plus Rear Fan Tray
Air Filters
Documentation
Related
CAUTION: The upper rear fan trays 2 and 4 work as a pair, and the lower rear
fan trays 3 and 5 work as a pair. For each fan tray pair, only one fan tray can
be removed at a time. The router might shut down if you remove both fan
trays in a pair.
Air filters help keep dust and other particles from entering the cooling system. The TX
Matrix Plus router has three air filters located in the front of the chassis. Two air filters
are located to the left of the TXP-F2S SIBs. The third air filter is located below the lower
front fan tray. The left air filters are interchangeable with each other; the lower air filter
is not interchangeable with the left air filters. The air filters are hot-insertable and
hot-removable.
TX Matrix Plus Clearance Requirements for Airflow and Hardware Maintenance on
• Troubleshooting the TX Matrix Plus Cooling System on page 283
• TX Matrix Plus Router Environmental Specifications on page 433
TX Matrix Plus Cables Overview
•
Fiber-Optic Array Cables on page 48
•
Ethernet Management Cables on page 48
•
Serial Cables on page 48
Fiber-Optic Array Cables
The fiber-optic arraycables connect theswitching planes of the the TX MatrixPlus router.
The TXP-F13 SIBs connect to the TXP-T1600 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 45 on page 110.
You can order cable lengths of 4 m, 6 m, 8 m, 10 m, 12 m, 15 m, 20 m, 25 m, 30 m, 35 m,
40 m, 45 m, 50 m, 55 m, 60 m, 65 m, 70 m, 75 m, 80 m, 85 m, 90 m, 95 m, and 100 m
from Juniper Networks.
Ethernet Management Cables
The UTP Category 5 cables, which use “straight through” wiring and RJ-45 connectors
on each end, are used for controlling the T1600 routers and for management of the
routing matrix. Controlling the T1600 routersrequires connections fromthe twoTXP-CIPs
in the TX Matrix Plus router to the LCC-CBs in the T1600 routers. Managing the routing
matrix requires connections from the TXP-CIPs to external management devices.
These cables can be up to 100 m long.
Serial Cables
For configuration and management of therouting matrix, RS-232 (EIA-232) serial cables
with RJ-45 connectors connect to the CONSOLE port and AUXILIARY port on a TXP-CB.
The CONSOLE port connects to a system console. The AUXILIARY port connectsto a
laptop computer modem, or other auxiliary device.
One cable is provided with the TX Matrix Plus router. To connect one device to the
CONSOLE port andanother device tothe AUXILIARY port, you must supplyanother cable.
NOTE: You must use the same length for every fiber-optic array cable from
a particular T1600 router to the TX Matrix Plus router. However, you do not
need to use the same length for all fiber-optic array cables within a routing
matrix.
NOTE: If your TX Matrix Plus router contains two host subsystems, we
recommend that you connect each TXP-CB to a system console.
Chapter 2: TX Matrix Plus Hardware Component Overview
Related
Documentation
Fiber-Optic Array Cable Connections and Considerations on page 109•
• Routing Matrix with a TX Matrix Plus Router Hardware Configuration Overview on
page 104
• TX Matrix Plus Routing Engine Interface Cable Specifications on page 443
• RJ-45 Connector Pinouts for the TX Matrix Plus Routing Engine ETHERNET Port on
page 445
• RJ-45 Connector Pinouts for the TX Matrix Plus Routing Engine AUXILIARY and
CONSOLE Ports on page 446
TX Matrix Plus Rear Cable Management System
The TX Matrix plus rear cable management system installs in the rear and top of the
TX Matrix Plus chassis. It organizes, supports, and provides strain relief for the fiber-optic
array cables connected to the TXP-F13 SIBs. The fiber-optic array cables (see Figure 28
on page 52) are routed to the sides of the TX Matrix Plus router, and then toward the top
of the chassis, where you can route the cables to the T1600 routers. The cable
management system adds 9 in. (22.86 cm) to the depth of the chassis.
NOTE: We recommend that you use the TX Matrix plus rear cable
management system to maintain the fiber-optic array cable bend radius.
The cable management system consists of three shelves connected to four cable
management arms. Cables connected to the odd side of theTXP-F13 SIBs in slots 0
through 7 areroutedto theupper right cablemanagement arm, and the cables connected
to the even side are routed to the upper left cable management arm. cables connected
to the odd side of the TXP-F13 SIBs in slots 8 through 15 are routed to the lower right
cable management arm, and the cables connected to the even side are routed to the
lower left cable management arm.
Figure 26 on page 50 shows the TX Matrix Plus cable management system.
Figure 26: TX Matrix Plus Rear Cable Management System
Each cable management arm has eight cable clamps (Figure 27 on page 51). Each cable
clamp contains four cable dividers labeled A, B, C, D, one divider for each cable (Figure
28 on page 52).
The front cable manager organizes, supports, and provides strain relief for the cables
that connect to the components in front of the TX Matrix Plus router. The front cable
manager adds 2.7 in. (6.9 cm) to the depth of the chassis. The cables are routed to the
sides of the TX Matrix Plus router.
The cable management system consists of a tray to manage the cables.
Figure 29 on page 53 shows the TX Matrix Plus front cable management system.
Figure 29: TX Matrix Plus Front Cable Manager
Chapter 2: TX Matrix Plus Hardware Component Overview
Related
Documentation
• Installing the TX Matrix Plus Front Cable Manager on page 155
• TX Matrix Plus Clearance Requirements for Airflow and Hardware Maintenance on
Routing Matrix with a TX Matrix Plus
Router System Architecture Overview
•
Routing Matrix with a TX Matrix Plus Router System Architecture on page 55
•
Routing Matrix with a TX Matrix Plus Router System Control Plane
Architecture on page 56
•
Control Plane Connections from the TX Matrix Plus Router to the T1600
Routers on page 58
•
Routing Matrix with a TX Matrix Plus Router Switch Fabric and Switching Plane
Architecture on page 60
•
Switching Plane Connections from the TX Matrix Plus Router to the T1600
Routers on page 63
Routing Matrix with a TX Matrix Plus Router System Architecture
A routing matrix with a TX Matrix Plus router and up to four T1600 routers 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 TXP-CIPs in
the TX Matrix Plus router and LCC-CBs in the T1600 routers, and the Routing Engines.
•
The forwarding plane in the routing matrix is formed by the switch fabric—TXP-F13
SIBs and TXP-F2S SIBs in the TX Matrix Plus router and the TXP-T1600 SIBs and
Packet Forwarding Engines in the T1600 Router.
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 30 on page 56 shows the
relationship between the Routing Engines and the Packet Forwarding Engines.
• Routing Matrix with a TX Matrix Plus Router System Control Plane Architecture on
page 56
• Routing Matrix with a TX Matrix Plus Router Switch Fabric and Switching Plane
Architecture on page 60
Routing Matrix with a TX Matrix Plus Router System Control Plane Architecture
The routing matrix contains two control planes. All master Routing Engines in the TX
Matrix Plus router andT1600 routers are onone control plane; allbackup Routing Engines
are on another control plane (see Figure 31 on page 57). To manage the Routing Engines
on a control plane, you must be logged into the Routing Engine in the TX Matrix Plus
router on that control plane. For example, you must be logged into the backup Routing
Engine inthe TX Matrix Plusrouter to upgradethe softwareof all backup RoutingEngines
in the routing matrix.
The TX Matrix Plus Routing Engine connects to a high-speed switch through a 10-Gbps
link within the host subsystem. The switch provides a 1-Gbps link to each T1600 Routing
Engine. The 1-Gbps links are provided through the UTP Category 5 Ethernet cable
connections between the TXP-CBs and the LCC-CBs in the T1600 routers. (For more
information about connecting TXP-CBs to LCC-CBs, see “Control Plane Connections
from the TX Matrix Plus Router to the T1600 Routers” on page 58.)
The kernel synchronization process running on each T1600 Routing Engine synchronizes
the forwarding table on the TX Matrix Plus Routing Engine with the forwarding table on
the T1600 router. The Junos kernel running on each T1600 Routing Engine copies its
forwarding table to all Packet Forwarding Engines in the T1600 router.
Figure 32 on page 58 illustrates the control plane architecture.
Chapter 3: Routing Matrix with a TX Matrix Plus Router System Architecture Overview
Figure 33: TX Matrix Plus Control Plane Connections
UTP Category 5 Ethernet cables provide the control plane connections between the
RJ-45 LCC CTRL PLANE ports 0 through 3 on the TXP-CIPs in the TX Matrix Plus router
and theSFC 0 port on theLCC-CBs in the T1600 routers. The maximumlength 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 20 on page 60 shows these connections.
The cable connections provided in Table 20 on page 60 apply to routing matrix
configurations using from one through four T1600 routers.
Table 20: Cable Connections Between TXP-CIPs and LCC-CBs
T1600 routerTX Matrix Plus
LCC CTRL
PLANEPortTXP-CIP
LCC-CBLCC
SFC Port
SFC0LCC-CB-000TXP-CIP-0
SFC0LCC-CB-011
SFC0LCC-CB-022
SFC0LCC-CB-033
SFC0LCC-CB-100TXP-CIP-1
SFC0LCC-CB-111
SFC0LCC-CB-122
SFC0LCC-CB-133
Related
Documentation
TX Matrix Plus Router Description on page 3•
• Routing Matrix with a TX Matrix Plus Router System Architecture on page 55
• Routing Matrix with a TX Matrix Plus Router Switch Fabric and Switching Plane
Architecture on page 60
Routing Matrix with a TX Matrix Plus Router Switch Fabric and Switching Plane
Architecture
The TX Matrix Plus router TXP-4 configuration consists of one routing matrix switch
fabric with five data switching planes. One of the five data switching planes acts as a
backup spare to the remaining data switching planes. If faults are detected in an active
data switching plane, the plane is taken offline, and the backup spare plane is brought
online. When a failed component is replaced andbrought online, the data switchingplane
in which it resides becomes the new backup spare plane.
Each data switching planeconsists ofone ortwo TXP-F13SIBs connected to fourTXP-F2S
SIBs thorough the midplane. Table 21 on page 62 shows these connections.
The TXP-F13 SIBs on the TX Matrix Plus router and the TXP-T1600 SIBs on the T1600
router are connected by high-speed optical links within fiber-optic array cables. The
switch fabric uses ASICs to perform high-speed packet forwarding between the T1600
routers.
A packet that enters an interface on a PIC in a T1600 router and is destined for another
T1600 router in the routing matrix is first forwarded to a Packet Forwarding Engine on
the source router. The packet is then forwarded through the Packet Forwarding Engine
Chapter 3: Routing Matrix with a TX Matrix Plus Router System Architecture Overview
from the source T1600 router, through the switch fabric on the TX Matrix Plus router, to
the target T1600 router. The switch fabric allows high-priority traffic from any Packet
Forwarding Engine to an egress Packet Forwarding Engine to be given preferential
treatment over low-priority traffic from any other Packet Forwarding Engine. The Packet
Forwarding Engine on the target T1600 router forwards the packet to the destination
PIC and interface.
Figure 34 on page 61 illustrates the switch fabric architecture.
Chapter 3: Routing Matrix with a TX Matrix Plus Router System Architecture Overview
Switching Plane Connections from the TX Matrix Plus Router to the T1600 Routers
•
Switching Plane Description on page 63
•
Fiber-Optic Array Cable Connections Between TX Matrix Plus Routers and T1600
Routers on page 63
Switching Plane Description
Fiber-optic array cables connect the TXP-F13 SIBs to the TXP-T1600 SIBs on the T1600
router.Figure 35 on page 63 shows the switching plane connections between the TX
Matrix Plus router and four T1600 routers.
Figure 35: Switching Plane Connections
Fiber-Optic Array Cable Connections Between TX Matrix Plus Routers and T1600 Routers
The cable connections provided in Table 22 on page 64 apply to routing matrix
configurations with up to four T1600 routers. For example, a four-router configuration
contains TXP-F13 SIBs in slots 1, 3, 4, 6, 7, 8, 9, 11, and 12. Slots 2, 5, 10, 13, 14, and 15 are
not used and must contain blanks. For a two-router configuration, the TXP-F13 SIB slots
1, 2, 4, 5, 7, 9,10, 12, 13, 14, and 15 are not used and must contain blanks.
Table 22: Fiber-Optic Array Cable Connections to Four T1600 Routers