 |
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 T640 routing node chassis. Do not use the routing matrix-based FPC number shown in Table 16. |
When you configure a routing matrix, you need to be aware of several differences and similarities between a routing matrix and a standalone T640 routing node. To implement a routing matrix in your network, perform the configuration procedures in this section:
A routing matrix can contain up to four T640 routing nodes, and each T640 routing node can contain up to eight FPCs (numbered 0 through 7). Therefore, the routing matrix as a whole can consist of up to 32 FPCs (numbered 0 through 31).
Each T640 routing node is assigned a number (LCCs 0 through 3) that depends upon the hardware setup and connectivity to the TX Matrix platform. Table 15 shows the basic correspondence between the FPC hardware slot numbers in T640 routing nodes and the FPC assignments recognized by a routing matrix.
Table 15: FPC Correspondence Between T640 Routing Nodes and the Routing Matrix
T640 Routing Node |
T640 FPC Range |
Routing Matrix FPC Range |
|---|---|---|
LCC 0 |
0–7 |
0–7 |
LCC 1 |
0–7 |
8–15 |
LCC 2 |
0–7 |
16–23 |
LCC 3 |
0–7 |
24–31 |
To easily convert FPC numbers in the T640 routing nodes to the correct FPC number in a routing matrix, use the conversion chart shown in Table 16. You can use the converted FPC number to configure the interfaces on the TX Matrix platform in your routing matrix.
Table 16: T640 to Routing Matrix FPC Conversion Chart
For example, if you have a Gigabit Ethernet interface installed in FPC slot 7, PIC slot 0, port 0 of T640 routing node LCC 3, you can configure this interface on the TX Matrix platform by including the ge-31/0/0 statement at the [edit interfaces] hierarchy level.
For more information about physically connecting T640 routing nodes and a TX Matrix platform together in a routing matrix, see the TX Matrix Platform Hardware Guide. For more information about the interface-naming conventions for a routing matrix, see the JUNOS Network Interfaces Configuration Guide.
For easy maintenance of chassis in a routing matrix, you can add a configuration group for each Routing Engine in the T640 routing nodes and TX Matrix platform. The configuration groups added to the TX Matrix platform configuration offer a simple way to establish hostnames, management interfaces, and default routes. In the example below, groups re0 and re1 refer to the TX Matrix platform Routing Engines, while groups lcc0-re0 and lcc0-re1 refer to the Routing Engines on T640 routing node LCC0. To configure groups for the TX Matrix platform, include the re0 and re1 statements at the [edit groups] hierarchy level. To configure groups for the T640 routing nodes, include the lccnumber-re0 and lccnumber-re1 statements at the [edit groups] hierarchy level.
- [edit]
- groups {
-
- re0 {
-
- system {
- host-name hostname-scc-re0;
- backup-router ip-address;
- }
-
- interfaces {
-
- fxp0 {
-
- unit 0 {
-
- family inet {
- address ip-address;
- }
- }
- }
- }
- }
-
- re1 {
-
- system {
- host-name hostname-scc-re1;
- backup-router ip-address;
- }
-
- interfaces {
-
- fxp0 {
-
- unit 0 {
-
- family inet {
- address ip-address;
- }
- }
- }
- }
- }
-
- lcc0-re0 {
-
- system {
- host-name hostname-lcc0-re0;
- backup-router ip-address;
- }
-
- interfaces {
-
- fxp0 {
-
- unit 0 {
-
- family inet {
- address ip-address;
- }
- }
- }
- }
- }
-
- lcc0-re1 {
-
- system {
- host-name hostname-lcc0-re1;
- backup-router ip-address;
- }
-
- interfaces {
-
- fxp0 {
-
- unit 0 {
-
- family inet {
- address ip-address;
- }
- }
- }
- }
- }
- }
- apply-groups [ re0 re1 lcc0-re0 lcc0-re1 ];
Note that apply groups can be nested. For example, any configuration statements that are common to lcc0-re0 and lcc0-re1 can be put into a separate group and then added as an apply group to the lcc0-re0 and lcc0-re1 groups, which in turn are applied to the main configuration.
For more information about configuration groups, see the JUNOS CLI User Guide.
Other than the expanded range of FPC numbers for interfaces and the requirement to create groups for the T640 routing nodes, the configuration of a routing matrix is exactly the same as for all other Juniper Networks routing platforms. As such, you can configure routing protocols, Multiprotocol Label Switching (MPLS) applications, virtual private networks (VPNs), routing and forwarding options, and other software features as usual.
For more information on configuring JUNOS-based routing platforms, see the JUNOS configuration guides.
You can configure PIC-specific features, such as SONET/SDH framing, on specific T640 routing nodes within the routing matrix. To do so, include the lcc lcc-number statement at the [edit chassis] hierarchy level and specify the chassis-specific feature to configure.
- [edit]
- chassis {
-
- lcc lcc-number {
-
- fpc slot-number { # Use the T640 routing
node FPC hardware slot number.
-
- pic pic-number {
- ...
- }
- }
- }
- }
|
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 T640 routing node chassis. Do not use the routing matrix-based FPC number shown in Table 16. |
By default, the JUNOS software allows all T640 routing nodes in the routing matrix to come online. Optionally, you can configure the TX Matrix platform to generate an alarm if the T640 routing nodes in the routing matrix do not come online. To configure, include the online-expected statement at the [edit chassis lcc number] hierarchy level on the TX Matrix platform.
If you do not want a T640 routing node to be part of the routing matrix, you can configure it to be offline. This is useful when you are performing maintenance on a T640 routing node. To configure a T640 routing node so that it is offline, include the offline statement at the [edit chassis lcc number] hierarchy level.
When you are ready to bring the T640 routing node back online, delete the offline configuration statement at the [edit chassis lcc number] hierarchy level.
|
Note: If you do not configure the online-expected or offline statement, any T640 routing node that is part of the routing matrix is allowed to come online. However, if a T640 routing node does not come online, the TX Matrix platform does not generate an alarm. |
For more information about chassis-specific statements, see the JUNOS System Basics Configuration Guide.
