[Contents] [Prev] [Next] [Index] [Report an Error]

Example: Routing Matrix Configuration

Figure 15: Routing Matrix Topology Diagram

Image g015014.gif

Figure 15 shows Routing Matrix A, a basic routing matrix consisting of a TX Matrix platform and two T640 routing nodes. The TX Matrix platform is named SCC and the nodes are named LCC0 and LCC2. The routing matrix is acting as a provider edge (PE) router in a Layer 2 circuit network. SONET interface so-1/1/0 in node LCC0 connects to an IP/MPLS core network, and Asynchronous Transfer Mode 2 (ATM2) intelligent queuing (IQ) interface at-17/1/0 in node LCC2 runs Layer 2 circuit trunk mode to connect to an ATM switch. (For more information about Layer 2 circuit trunk mode, see Option: Configuring Layer 2 Circuit Trunk Mode on ATM2 IQ Interfaces or the JUNOS VPNs Configuration Guide.)

Some key considerations for this configuration are as follows:

TX Matrix Platform—SCC

[edit]
groups { # You can create special configuration groups in a routing matrix.
re0 { # This group corresponds to the master Routing Engine
system { # on the TX Matrix platform.
host-name scc;
backup-router 192.168.17.254;
}
interfaces {
fxp0 {
unit 0 {
family inet {
address 192.168.77.158/21;
}
}
}
}
}
re1 { # This group corresponds to the backup Routing Engine
system { # on the TX Matrix platform.
host-name scc1;
backup-router 192.168.17.254;
}
interfaces {
fxp0 {
unit 0 {
family inet {
address 192.168.77.168/21;
}
}
}
}
}
lcc0-re0 { # This group corresponds to the master Routing Engine
system { # on the T640 routing node LCC0.
host-name lcc0;
backup-router 192.168.17.254 destination [10.0.0.0/8 192.168.0.0/16];
}
interfaces {
fxp0 {
unit 0 {
family inet {
address 192.168.77.157/21;
}
}
}
}
}
lcc2-re0 { # This group corresponds to the master Routing Engine
system { # on the T640 routing node LCC2.
host-name lcc2;
backup-router 192.168.17.254 destination [10.0.0.0/8 192.168.0.0/16];
}
interfaces {
fxp0 {
unit 0 {
family inet {
address 192.168.77.159/21;
}
}
}
}
}
lcc0-re1 { # This group corresponds to the backup Routing Engine
system { # on the T640 routing node LCC0.
host-name lcc0-1;
backup-router 192.168.17.254 destination [10.0.0.0/8 192.168.0.0/16];
}
interfaces {
fxp0 {
unit 0 {
family inet {
address 192.168.77.169/21;
}
}
}
}
}
lcc2-re1 { # This group corresponds to the backup Routing Engine
system { # on the T640 routing node LCC2.
host-name lcc2-1;
backup-router 192.168.17.254 destination [10.0.0.0/8 192.168.0.0/16];
}
interfaces {
fxp0 {
unit 0 {
family inet {
address 192.168.77.192/21;
}
}
}
}
}
}
apply-groups [ re0 re1 lcc0-re1 lcc2-re1 lcc0-re0 lcc2-re0 ];
system {
syslog {
file messages {
any any;
}
}
}
chassis { # You must apply chassis commands to a specific T640 routing node.
lcc 2 { # Specify the T640 routing node and the FPC hardware slot of the node.
fpc 1 { # This FPC is equivalent to slot 17 in the routing matrix.
pic 1 {
atm-l2circuit-mode {
trunk nni;
}
}
}
}
}
interfaces {
so-1/1/0 { # This is a SONET interface at FPC 1, PIC 1, port 0
mtu 9192; # on the T640 routing node LCC0.
unit 0 {
family inet {
address 10.15.1.1/30 {
destination 10.15.1.2;
}
}
family iso;
family mpls {
filter {
input filter_1;
}
}
}
}
at-17/1/0 { # This is an ATM2 IQ interface at FPC 1, PIC 1, port 0
encapsulation atm-ccc-cell-relay; # on the T640 routing node LCC2.
atm-options {
pic-type atm2;
scheduler-maps { # CoS on an ATM2 IQ PIC works the same in a routing matrix
cos1 { # as it does in a standalone T640 routing node.
forwarding-class ubr {
priority low;
transmit-weight percent 25;
}
forwarding-class nrtvbr {
priority low;
transmit-weight percent 25;
}
forwarding-class rtvbr {
priority low;
transmit-weight percent 25;
}
forwarding-class cbr {
priority high;
transmit-weight percent 25;
}
}
cos2 {
forwarding-class ubr {
priority low;
transmit-weight percent 10;
}
forwarding-class nrtvbr {
priority low;
transmit-weight percent 20;
}
forwarding-class rtvbr {
priority low;
transmit-weight percent 30;
}
forwarding-class cbr {
priority high;
transmit-weight percent 40;
}
}
cos3 {
forwarding-class ubr {
priority low;
transmit-weight percent 40;
}
forwarding-class nrtvbr {
priority low;
transmit-weight percent 30;
}
forwarding-class rtvbr {
priority low;
transmit-weight percent 20;
}
forwarding-class cbr {
priority high;
transmit-weight percent 10;
}
}
}
}
unit 0 {
trunk-id 0;
trunk-bandwidth 10m;
cell-bundle-size 2;
}
unit 1 {
trunk-id 1;
trunk-bandwidth 10m;
cell-bundle-size 1;
atm-scheduler-map cos1;
}
unit 2 {
trunk-id 2;
trunk-bandwidth 10m;
cell-bundle-size 2;
atm-scheduler-map cos2;
}
unit 3 {
trunk-id 3;
trunk-bandwidth 10m;
cell-bundle-size 3;
atm-scheduler-map cos3;
}
}
lo0 {
unit 0 {
family inet {
address 127.0.0.1/32;
address 10.255.77.158/32 {
primary;
}
}
family iso {
address 47.0005.80ff.f800.0000.0108.0001.0102.5507.0158.00;
}
family inet6 {
address 2001:db8::10:255:77:158/32 {
primary;
}
}
}
}
}
protocols { # You can configure protocols in the routing matrix as usual.
mpls {
interface so-1/1/0.0;
}
isis {
interface so-1/1/0.0;
interface lo0.0;
}
ldp {
interface so-1/1/0.0;
interface lo0.0;
}
l2circuit {
neighbor 10.255.71.97 {
interface at-17/1/0.0 {
virtual-circuit-id 100;
}
interface at-17/1/0.1 {
virtual-circuit-id 101;
}
interface at-17/1/0.2 {
virtual-circuit-id 102;
}
interface at-17/1/0.3 {
virtual-circuit-id 103;
}
}
}
}
class-of-service { # You can configure CoS in the routing matrix as usual.
forwarding-classes {
queue 0 ubr;
queue 1 nrtvbr;
queue 2 rtvbr;
queue 3 cbr;
}
traceoptions {
flag all;
}
}
firewall { # You can configure firewalls in the routing matrix as usual.
family mpls {
filter filter_1 {
term plp0 {
from {
exp [ 0 2 4 6 ];
}
then {
count LOW;
loss-priority low;
}
}
term plp1 {
from {
exp [ 1 3 5 7 ];
}
then {
count HIGH;
loss-priority high;
}
}
}
}
}
[Contents] [Prev] [Next] [Index] [Report an Error]

Copyright © 2008, Juniper Networks, Inc. All rights reserved. Trademark Notice.