Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Junos OS Overview in a TX Matrix Plus Routing Matrix

 

Junos OS Releases Required

To determine the Junos OS required for your hardware configuration, see the following documentation:

The TX Matrix Plus router, T1600 router, and T4000 router are delivered with the Junos OS preinstalled.

Note

There are up to three copies of the software: one on a CompactFlash card (if installed) in the Routing Engine, one on the Disk1 in the Routing Engine (if installed), and one on a USB device that can be inserted into the slot in the Routing Engine faceplate.

To upgrade the software:

  1. Upgrade the JUNOS OS running on the router.
  2. After you are satisfied that the new packages are successfully installed and running, issue the request system snapshot command to back up the new software.

Running Different Junos OS Releases on the Routing Engines

We recommend that you run the same Junos OS Release on the master and backup Routing Engines. If you run the same Junos OS Release on all master and backup Routing Engines in the routing matrix, a change in mastership to any backup Routing Engine in the routing matrix does not cause a change in mastership in any other chassis in the routing matrix.

However, if you choose to run different Junos OS Releases on the Routing Engines, all Routing Engines on the same control plane must run the same Junos OS Release. All master Routing Engines in the TX Matrix Plus router and line-card chassis (LCC)are on one control plane; all backup Routing Engines are on another control plane.

Note

If you run different Junos OS Releases on the Routing Engines, a change in Routing Engine mastership might cause one or all LCCs to be logically disconnected from the TX Matrix Plus router.

Junos OS Software Overview

The Junos OS processes support Internet routing protocols, control the routing matrix's interfaces and chassis, and provide an interface for system management. The Junos OS runs on all Routing Engines in the routing matrix. The Routing Engine kernel provides the underlying infrastructure for all Junos OS processes. The Junos OS processes run on top of a kernel that coordinates the communication among processes and has a direct link to the Packet Forwarding Engine software.

The Routing Engine in the TX Matrix Plus router:

  • Maintains the routing tables used by the routing matrix. The kernel running on the TX Matrix Plus Routing Engine maintains the master forwarding table for the routing matrix, and provides all routing tables, along with updates about active routes, to each line-card chassis (LCC) in the routing matrix.

  • Controls the routing protocols that run on the routing matrix. The Junos routing protocol process uses the routing tables to determine active routes to network destinations and installs these routes into the TX Matrix Plus Routing Engine's forwarding table. The routing protocol process starts all configured routing protocols and handles all routing messages. It consolidates the routing information learned from all routing protocols into common routing tables. Finally, the routing protocol process implements the routing policies you specify, which determine how routing information is transferred between the routing protocols and the routing table.

Each Routing Engine in an LCC runs its own kernel, which is synchronized with the kernel running in each Routing Engine in the TX Matrix Plus router. The kernel running on each Routing Engine in an LCC copies its local forwarding table—which is synchronized with the master forwarding table by the kernel synchronization process—to all Packet Forwarding Engines in the LCC (see Figure 1).

Figure 1: Control Packet Handling for Routing and Forwarding Table Updates
Control Packet Handling for
Routing and Forwarding Table Updates

The Junos OS chassis process, which runs on all Routing Engines in the routing matrix, allows you to configure and control the properties of the routing matrix, including conditions that trigger alarms and clock sources. The chassis process running on the TX Matrix Plus Routing Engine manages the components in the TX Matrix Plus chassis, and the chassis process running on each LCC Routing Engine manages the components in that router's chassis. All chassis processes running in the routing matrix collectively coordinate the control of the routing matrix switch fabric.

TX Matrix Plus Junos OS Configuration Overview

The Junos OS CLI is the primary tool for accessing and controlling the Junos OS. You use it when accessing the router through the console or a connection to a management network. The CLI includes commands for configuring router hardware, the Junos OS, and network connectivity. For more information about the CLI, see the CLI User Guide.

The TX Matrix Plus router runs the same Junos OS that runs on other Juniper Networks devices. From the user interface, the routing matrix appears as a single router. The configuration of a routing matrix is the same as for all other Juniper Networks devices with the following exceptions:

  • You configure and manage the TX Matrix Plus router and all line-card chassis (LCC) in the routing matrix through the CLI on the TX Matrix Plus router.

  • The configuration file on the TX Matrix Plus router is used for the entire routing matrix.

  • When you commit the configuration on the TX Matrix Plus master Routing Engine, the changes are automatically propagated to all master Routing Engines in all LCCs. If you issue the commit synchronize command, you commit the configuration to all master and backup Routing Engines in the routing matrix.

  • Configuration statements included at the [edit chassis] hierarchy level are applied to the TX Matrix Plus router and all LCCs in the routing matrix.

    Use the expanded range of Flexible PIC Concentrator (FPC) numbers for interfaces when you include configuration statements at the [edit chassis] hierarchy level.

  • Configuration statements included at the [edit chassis lcc lcc-number] hierarchy level are applied only to the LCC specified.

    Note

    When you include statements at the [edit chassis lcc lcc-number] hierarchy level, specify the actual FPC hardware slot number as labeled on the LCC chassis. Do not use the expanded range of routing matrix-based FPC number shown in Line-Card Chassis Interface Names.

  • Creating groups for the LCC—Configuration groups offer a simple way to establish host names, management interfaces, and default routes. Providing special group names for all Routing Engines in the routing matrix allows you to configure the individual Routing Engines in each LCC. Configuration groups contain configuration statements, and direct the inheritance of that group's statements in the rest of the configuration.

    Note

    Parameters that are not configured at the groups hierarchy level apply to all Routing Engines in the routing matrix.

    You can also specify two special group names—re0 and re1. These two special group names apply to the Routing Engines in slots 0 and 1 of the TX Matrix Plus router. In addition, the TX Matrix Plus router supports group names for the Routing Engines in each LCC in the following formats:

    lcc-number identifies the LCC and can be from 0 through 7, depending on the routing matrix configuration.

    For example, to configure Routing Engine 1 properties for lcc3, you include statements at the [edit groups lcc3-re1] hierarchy level.

    You must include the apply-groups statement in the configuration for all special groups, including re0 and re1.

For more information about configuring the TX Matrix Plus router, see the Routing Matrix with a TX Matrix Plus Router Deployment Guide. For complete information about configuring the software, including examples, see the Junos OS configuration guides.

For more information about chassis-specific statements, the Junos OS, including its security features and a list of the industry standards it supports, and software installation, see the Junos OS Administration Library.

TX Matrix Plus Junos Operational Overview

The CLI includes commands for monitoring and troubleshooting hardware, software, routing protocols, and network connectivity. CLI commands display information from routing tables, information specific to routing protocols, and information about network connectivity derived from the ping and traceroute utilities.

In general, the same Junos operational mode commands that run on other Juniper Networks devices are supported in with a TX Matrix Plus router and LCCs in a routing matrix. The operation of a routing matrix is the same as for other Juniper Networks devices, with the following exceptions:

  • Additional commands and options support enhanced diagnostics features for the fiber-optic links and other new hardware in the TX Matrix Plus router and LCCs.

  • The management Ethernet interface is em0.

  • The sfc option for the TX Matrix Plus router. When you specify the sfc option, you must use the expanded range of FPC numbers for interfaces.

  • The lcc option for LCCs in a routing matrix.

    Note

    The lcc option is also supported for T640 routers connected to a TX Matrix router.