Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 

Routing Matrix with TXP-T1600 Configuration

 

A routing matrix with the TXP-T1600 configuration consists of two types of chassis: a Juniper Networks TX Matrix Plus Router and Juniper Networks T1600 Core Routers.

  • TX Matrix Plus router—A routing matrix can contain only one Juniper Networks TX Matrix Plus router. A TX Matrix Plus router is also referred to as the switch-fabric chassis (SFC). In the Junos OS command-line interface (CLI), sfc 0 is used to refer to the TX Matrix Plus router. For information about installing and connecting to a TX Matrix Plus router, see the TX Matrix Plus Router Hardware Guide  .

  • T1600 routers—A routing matrix can contain from one to four T1600 routers, numbered from 0 through 3. A T1600 router in a routing matrix is also referred to as a line-card chassis (LCC). In the Junos OS CLI, lcc 0 through lcc 3 are used to refer to T1600 routers in a TXP-T1600 configuration. For information about connecting to a T1600 routers in a routing matrix, see the TX Matrix Plus Router Hardware Guide  .

In a routing matrix, the TX Matrix Plus router controls all the connected T1600 routers, as shown in Figure 1.

Figure 1: TXP-T1600 Configuration
TXP-T1600 Configuration

A key element of the routing matrix design is the ability to migrate existing standalone T1600 routers and connect them with a TX Matrix Plus router through fiber-optic cables and Switch Interface Boards (SIBs).

The TX Matrix Plus router connection between the T1600 routers uses a scalable, three-stage switch fabric. This system architecture provides terabit bandwidth expansion capacity and eliminates the use of subscriber line cards to connect devices within points of presence (POPs). As a result, the primary application for the routing matrix is to collapse aggregation and core layers in large POPs and central offices.

Similarly, you can limit which portions of the routing matrix are modified during configuration or maintenance procedures (for example, performing software upgrades or halting Routing Engines).