Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation
Guide That Contains This Content
[+] Expand All
[-] Collapse All

    TX Matrix Plus CLI Overview

    TX Matrix Plus Junos OS Configuration Overview

    The TX Matrix Plus router is shipped with the Junos OS preinstalled and ready to be configured when the TX Matrix Plus router is powered on.

    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 Junos OS CLI User Guide PDF Document.

    Familiarity with the Junos OS and its CLI allows you to quickly and easily configure the routing matrix. The TX Matrix Plus router runs the same Junos OS that runs on all Juniper Networks J Series, M Series, MX Series, and T Series routers, including the TX Matrix router. You can configure routing protocols, Multiprotocol Label Switching (MPLS) applications, virtual private networks (VPNs), routing and forwarding options, and other software features as usual. You use the Junos OS to configure the properties of routing matrix interfaces.

    From the perspective of 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 routers with the following exceptions:

    • You configure and manage the TX Matrix Plus router and all T1600 routers 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 T1600 routers. If you issue the commit synchronize command, you commit the configuration to all master and backup Routing Engines in the routing matrix.
    • Creating groups for the T1600 routers

      Parameters that are not configured at the groups hierarchy level apply to all Routing Engines in the routing matrix. Providing special group names for all Routing Engines in the routing matrix allows you to configure the individual Routing Engines in each T1600 router differently.

    • Configuration statements included at the [edit chassis] hierarchy level are applied to the TX Matrix Plus router and all T1600 routers 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 T1600 router 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 T1600 router chassis. Do not use the expanded range of routing matrix-based FPC number shown in T1600 FPC Slot Number Correspondence.

    For more information about configuring the TX Matrix Plus router, see the Junos OS Feature Guides. 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 System Basics Configuration Guide PDF Document.

    Configuration Groups

    Configuration groups allow you to create a group containing configuration statements (by including the groups statement) and to direct the inheritance of that group's statements in the rest of the configuration. The configuration groups offer a simple way to establish hostnames, management interfaces, and default routes.

    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 T1600 router in the following formats:

    lcc lcc-number -re0lcc lcc-number-re1

    lcc-number identifies the T1600 router and can be from 0 through 3.

    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.

    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, a routing matrix with a TX Matrix Plus router and T1600 routers supports most of the same Junos operational mode commands that run on all Juniper Networks J Series, M Series, MX Series, and T Series routers, including TX Matrix routers. The operation of a routing matrix is the same as for all other Juniper Networks routers, with the following exceptions:

    • A new management Ethernet interface em0
    • The new sfc interface for the TX Matrix Plus router. When you specifiy the sfc option, you must use the expanded range of FPC numbers for interfaces.
    • The lcc interface is now supported for T1600 routers in a routing matrix.

      Note: The lcc interface is also supported for T640 routers connected to a TX Matrix router.

    • Additional commands and options have been added to support enhanced diagnostics features for the fiber-optic links and other new hardware in the TX Matrix Plus router

    For more information about operational mode commands, see the Junos OS command references.

    You can also use the Junos OS implementation of SNMP to monitor routers. The SNMP software consists of an SNMP master agent and a MIB II agent. It provides full support for MIB II SNMP version 1 traps and version 2 notifications, SNMP version 1 Get and GetNext requests, and version 2 GetBulk requests. For more information about SNMP, see the Junos OS Network Management Configuration Guide PDF Document.

    The software also supports tracing and logging operations, which you can use to track normal router operations, error conditions, and the packets that the router generates or forwards.

    • Logging operations use a syslog-like mechanism to record systemwide, high-level events such as interfaces going up or down and user logins on the router.
    • Tracing operations record more detailed information about the operation of routing protocols, such as the various types of routing protocol packets sent and received, and routing policy actions.

    Published: 2011-12-19