Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Example: Configuring a Routing Matrix with a TX Matrix Plus Router in Mixed Mode

 

The mixed-mode (TXP-Mixed-LCC-3D) configuration supports the following combinations of T1600 and T4000 routers:

  • Six T1600 routers and one T4000 router

  • Four T1600 routers and two T4000 routers

  • Two T1600 routers and three T4000 routers

This example provides a step-by-step procedure and commands for configuring and verifying a routing matrix with a TX Matrix Plus router and 3D SIBs in a mixed-mode configuration of two T1600 routers and three T4000 routers.

Requirements

This example uses the following software and hardware components:

  • Junos OS Release 13.1 or later.

  • One TX Matrix Plus router SFC (also referred to as the switch-fabric chassis (SFC) in a routing matrix).

  • Three T4000 routers (also referred to as line-card chassis (LCC) in a routing matrix).

  • Two T1600 routers (also referred to as line-card chassis (LCC) in a routing matrix).

  • Interchassis UTP Category 5 Ethernet cables that connect the SFC and LCC control planes.

  • Equipment racks for the SFC and the LCCs.

Note

This configuration example has been tested using the software release listed and is assumed to work on all later releases.

Before you configure a routing matrix with a TX Matrix Plus router and 3D SIBs, make sure that you understand how to connect the hardware components, and upgrade to a TX Matrix Plus router with 3D SIBs including setting the SFC configuration size. For more information, see the TX Matrix Plus Hardware Guide.

Overview

TX Matrix Plus routers with 3D SIBs double the T Series multichassis bandwidth when compared with TX Matrix Plus routers without 3D SIBs. Each T1600 LCC adds up to 1.6 terabits per second (Tbps) full-duplex (3.2 Tbps of any-to-any, nonblocking, half-duplex) switching. Each T4000 LCC adds up to 2.0 Tbps, full-duplex (4.0 Tbps of any-to-any, nonblocking, half-duplex) switching.

In this example, you configure a routing matrix in mixed mode that includes a TX Matrix Plus router with 3D SIBs, and two T1600 and three T4000 LCCs with 3D SIBs.

Note the following key considerations for this routing matrix configuration:

  • The TX Matrix Plus router with 3D SIBs, or the SFC, manages the routing matrix as a single router. All the operational commands and configurations required for the connected LCCs are executed on the TX Matrix Plus router with 3D SIBs which is designated as sfc0.

  • Create configuration groups for each Routing Engine in the routing matrix by using the special configuration groups for a routing matrix consisting of routers with dual Routing Engines: re0, re1, lcc0-re0, lcc2-re0, lcc4-re0, lcc6-re0, lcc7-re0, lcc0-re1, lcc2-re1, lcc4-re1, lcc6-re1, and lcc7-re1. Configure hostnames, default routes, and management Ethernet interfaces in these Routing Engine configuration groups.

  • To configure interfaces, use the routing matrix FPC numbering convention of slots 0 through 63. For details, see the FPC Numbering for Interfaces in TXP-Mixed-LCC-3D Configuration.

Topology

In this example, Routing Matrix A comprises a TX Matrix Plus router (sfc0) with 3D SIBs, three T4000 routers with 3D SIBs, and two T1600 routers with 3D SIBs.

In this example, the following hostnames are used for the TX Matrix Plus router and the LCCs:

  • sfc0—Primary Routing Engine on the TX Matrix Plus router

  • sfc0_alt_re—Backup Routing Engine on the TX Matrix Plus router

  • lcc0—Primary Routing Engine on T4000 LCC 0

  • lcc0_alt_re—Backup Routing Engine on T4000 LCC 0

  • lcc2—Primary Routing Engine on T4000 LCC 2

  • lcc2_alt_re—Backup Routing Engine on T4000 LCC 2

  • lcc4—Primary Routing Engine on T4000 LCC 4

  • lcc4_alt_re—Backup Routing Engine on T4000 LCC 4

  • lcc6—Primary Routing Engine on T1600 LCC 6

  • lcc6_alt_re—Backup Routing Engine on T1600 LCC 6

  • lcc7—Primary Routing Engine on T1600 LCC 7

  • lcc7_alt_re—Backup Routing Engine on T1600 LCC 7

Figure 1 shows that Routing Matrix A is a provider edge (PE) router in a Layer 2 circuit network. Ethernet interfaces xe-1/0/0 on LCC 0, xe-16/0/0 on LCC 2, xe-32/0/0 on LCC 4, xe-48/0/0 on LCC 6, and xe-56/0/0 on LCC 7 connect to an IP/MPLS core network.

Figure 1: Topology of a Routing Matrix with a TX Matrix Plus Router in a Mixed Mode
Topology of a Routing Matrix with
a TX Matrix Plus Router in a Mixed Mode

Configuration

To configure a routing matrix with a TX Matrix Plus router in mixed mode, perform the following tasks:

CLI Quick Configuration

To quickly configure this example, copy the following commands, paste them in a text file, remove any line breaks, change any details necessary to match your network configuration, and paste the commands into the CLI at the [edit] hierarchy level.

Configuring LCC Mode

Step-by-Step Procedure

A routing matrix with a TX Matrix Plus router and 3D SIBs supports a combination of T1600 and T4000 LCCs, which is also known as the TXP-Mixed-LCC-3D configuration. To enable the TXP-Mixed-LCC-3D configuration, you must configure the LCC mode on the TX Matrix Plus router. In this example, LCC 0, LCC 2, and LCC 4 are configured as T4000 LCCs and LCC 6 and LCC 7 are configured as T1600 LCCs.

Note
  • By default, the LCC mode is configured to t1600.

  • The LCC mode t4000 is supported only on the even-numbered LCCs LCC 0, LCC 2, LCC 4, and LCC 6.

  • When you set the LCC mode as t4000, you must set the LCC mode for the next (odd-numbered) LCC as empty. For example, if you set the LCC mode t4000 on LCC 2, then you must set the mode for LCC 3 as empty. Otherwise, the commit operation fails. Setting the LCC mode for an LCC as empty disables the control plane and data plane connections between that LCC and the SFC, so the LCC does not come online.

To configure LCC mode:

  1. Configure the LCC mode t4000 for LCC 0, LCC 2, and LCC 4 and the LCC mode empty for the odd-numbered LCCs ( LCC 1, LCC 3, and LCC 5) next to the T4000 LCCs.
  2. (Optional) Configure the LCC mode as t1600 on LCC 6 and LCC 7.
    Note

    By default, the LCC mode is set to t1600. However, if the LCC mode is set to t4000 or empty due to a previous configuration, then you need to configure the LCC mode as t1600. You can verify the LCC mode by using the show chassis lcc-mode operational mode command.

Creating Special Configuration Groups

Step-by-Step Procedure

The configuration groups featured in Junos OS enable you to create a group containing configuration statements and to direct the inheritance of that group’s statements in the rest of the configuration.

Using special configuration group names for all Routing Engines in the routing matrix allows you to configure the individual Routing Engines in each router differently. Because the configuration statements in the special configuration groups for Routing Engines apply to specific Routing Engines in the routing matrix, you can create a single configuration for all of the routers, with each Routing Engine using only the configuration statements that apply to it. For example, the configuration specified in group re0 is applied only if the current Routing Engine is in slot 0; likewise, the configuration specified in group re1 is applied only if the current Routing Engine is in slot 1. Therefore, both Routing Engines can use the same configuration file, each using only the configuration statements that apply to it.

To create and apply special configuration groups:

  1. Create special groups for the primary and the backup Routing Engines on the SFC.

    In this example, re0 and re1 are the special group names for the primary and backup Routing Engines of the SFC.

  2. Create special groups for the primary and the backup Routing Engines on the LCCs.

    In this example, lcc0-re0, lcc2-re0, lcc4-re0, lcc6-re0, and lcc7-re0 are the special group names for the primary Routing Engines in the LCCs and lcc0-re1, lcc2-re1, lcc4-re1, lcc6-re1, and lcc7-re1 are the special group names for the backup Routing Engines in the LCCs.

  3. Set a default router for the primary and backup Routing Engines in the SFC and the LCCs.
  4. Configure an IP address for the management interface logical port for the SFC and for each LCC.
  5. Enable inheritance to ensure that the group's statements are inherited in the rest of the configuration.

Configuring Interfaces

Step-by-Step Procedure

Ethernet interfaces xe-1/0/0 on LCC 0, xe-16/0/0 on LCC 2, xe-32/0/0 on LCC 4, xe-48/0/0 on LCC 6, and xe-56/0/0 on LCC 7 connect to an IP/MPLS core network.

To configure the interfaces:

  1. Configure the Ethernet interfaces and interface properties.
  2. Configure the loopback interface properties.

    You can configure the loopback interface on the routing matrix as usual. In this example, IP and IPv6 addresses are configured on the loopback interface with subnetwork routes.

Configuring Protocols

Step-by-Step Procedure

You can configure the protocols as usual. In this example, MPLS, IS-IS, and LDP protocols are configured on the SFC.

To configure the protocols:

  • Configure protocols on the configured interfaces in the routing matrix.

Configuring Firewall Filters

Step-by-Step Procedure

Firewall filters are configured to protect your router and network from excessive incoming traffic or hostile attacks that can disrupt network service, and to control which packets are forwarded from which router interfaces.

In this example, MPLS firewall filters filter_1, filter_2, filter_3, filter_4, and filter_5 are configured to count packets based on the EXP bits for the MPLS label in a packet.

To configure firewall filters:

  1. Configure firewall filters in the routing matrix.
  2. Apply the MPLS firewall filters to interfaces.

Verification

Confirm that the configuration is working properly.

Verifying LCC Mode

Purpose

Confirm that the LCC mode is working properly.

Action

In operational mode, enter the show chassis lcc-mode command.

[edit]

user@sfc0# show chassis lcc-mode

Meaning

The LCC mode is displayed as T4000 for LCC 0, LCC 2, and LCC 4. The LCC mode is shown as T1600 for LCC 6 and LCC 7. The LCC mode for the odd-numbered LCCs (LCC 1, LCC 3, and LCC 5) is shown as empty.

This means the LCC mode is configured correctly for the TXP-Mixed-LCC-3D configuration.

Verifying LCC Information

Purpose

Verify that the TX Matrix Plus router and the connected LCCs are communicating properly within the routing matrix.

Action

In operational mode, enter the show chassis lccs command.

[edit]

user@sfc0# show chassis lccs

Meaning

The display output includes the following information about the LCCs:

  • The Slot field displays the LCC slot number in the SFC.

  • The State field displays the LCC state information.

    • Online—The LCC connected to a TX Matrix Plus router with 3D SIBs is online and communicating properly.

    • Offline—The LCC is powered down.

    • Uptime—The duration since the LCC is online.

Verifying Junos OS Versions for All Routers

Purpose

Verify that the correct version of Junos OS is running for all routing matrix components.

Action

In operational mode, enter the show version command.

Meaning

In this example, all the routers have the same software revision [13.1R1.0]. It indicates that all the routers are running the same 64-bit Junos OS.

Verifying the Configured Interfaces

Purpose

Verify that all available interfaces in the routing matrix are up.

Action

In operational mode, enter the show interfaces terse command.

Meaning

The Admin and the Link status are shown as up, which means that the interfaces are configured and working properly.

Verifying the Route Information

Purpose

Verify the route information for the routing matrix.

Action

In operational mode, enter the show route summary command.

Meaning

The summary statistics about the entries in the routing table are shown based on the configuration.

Verifying System Uptime

Purpose

Verify the amount of time the routing matrix components have been in operation.

Action

In operational mode, enter the show system uptime command.

Meaning

The output shows the following information:

  • Current time—Current system time in UTC.

  • System booted—Date and time when the Routing Engine on the router was last booted and how long it has been running.

  • Protocols started—Date and time when the routing protocols were last started and how long they have been running.

  • Last configured—Date and time when a configuration was last committed. Also shows the name of the user who issued the last commit command.

  • time and up—Current time, in the local time zone, and how long the router has been operational.

  • users—Number of users logged in to the router.

  • load averages—Load averages for the last 1 minute, 5 minutes, and 15 minutes.

Verifying the Craft Interface Messages

Purpose

Verify the information on the craft interface. The craft interface allows you to view status and troubleshooting information at a glance and to perform many system control functions.

Action

In operational mode, enter the show chassis craft-interface command.

Meaning

The output shows the information of the craft interface.

  • The FPM Display Contents field displays the following contents of the Front Panel Module:

    • 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:

      Note

      During an alarm condition, the second line displays the number of active alarms in the following form:

    • Third and fourth lines—Information about the router traffic load, the power supply status, the fan status, and the temperature status.

      Note

      During an alarm condition, the third and fourth lines display individual alarm messages, with the most severe condition shown first. The prefix on each line indicates whether the alarm is a red or yellow alarm. R indicates a major alarm and Y indicates a minor alarm. You can view more information about the error messages associated with the alarm LEDs and the craft interface LCD by issuing the show chassis alarms operational mode command.

  • The SFC Chassis Number field displays 00 and the Config Size field displays 3.

  • Status of the Front Panel System LEDs, Front Panel F13 SIB LEDs, PS LEDs, Fan Tray LEDs, CB LEDs, SIB LEDs, and SCG LEDs. A dot (.) indicates that the LED is not lit. An asterisk (*) indicates that the LED is lit. For more details on the LEDs and troubleshooting information, see TX Matrix Plus LED Overview.

  • Status of the Front Panel Alarm Indicators. A dot (.) indicates that the relay is off. An asterisk (*) indicates that the relay is active.

Verifying the Chassis Alarms

Purpose

Verify the information about chassis alarms.

Action

In operational mode, enter the show chassis alarms command.

Meaning

The output shows information about the chassis alarms that are active. Verify the following information:

  • Date and time the alarm was first recorded.

  • Severity class for this alarm: Minor or Major.

  • The Description field displays information about chassis components such as the cooling system or power supplies. For example, Temperature Warm indicates that the chassis temperature exceeded the warm-temperature threshold, and you must ensure to provide sufficient cooling for the component. For more details on alarm information and actions to be taken, see the Troubleshooting the TX Matrix Plus Cooling System.