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

Example: LMP Control Channel Configuration

Figure 22: LMP Control Channel Topology Diagram

Image g017251.gif

Figure 22 shows a series of four routers that are used to establish an LMP control channel and TE link between Routers R1 and R4. The control channel originates on the so-1/1/0 interface of Router 1 and ends at the so-6/0/0 interface of Router 4. The TE link data channel is a point-to-point link from the so-0/1/2 interface of Router R1 to the so-3/0/2 interface of Router R4.

On Router 1, configure IS-IS, MPLS, and RSVP to support the LMP control channel. For the control channel, use the so-1/1/0 interface as the origin and specify 10.35.100.22 (the so-6/0/0 interface on Router 4) as the remote address. For the TE link, use the so-0/1/2 interface as the origin, include a local address and remote address pair of your choice, and configure the remote IDs to match the local IDs generated by the remote peer.

Configure a bidirectional GMPLS LSP to reach Router 4. Use the loopback address of 10.255.71.244 as the destination for the LSP, disable CSPF, and configure a strict path to the remote address of the TE link.

Router 1

[edit]
interfaces {
so-0/1/2 {
description “Data channel to Router 4”;
unit 0 {
family inet {
address 10.35.100.9/30;
}
family iso;
family mpls;
}
}
so-1/1/0 {
description “Control channel to Router 4”;
unit 0 {
family inet {
address 10.35.100.1/30;
}
family iso;
family mpls;
}
}
lo0 {
unit 0 {
family inet {
address 10.255.71.241/32;
}
family iso {
address 47.0005.0000.0000.0000.0000.0000.0102.5507.1241.00;
}
}
}
}
routing-options {
router-id 10.255.71.241;
}
protocols {
rsvp {
interface all;
}
mpls {
label-switched-path gmpls-router1-router4 {
to 10.255.71.244;
lsp-attributes {
switching-type fiber;
}
no-cspf;
primary path1;
}
path path1 {
10.35.1.2 strict;
}
interface so-1/1/0.0;
}
isis {
interface so-1/1/0.0;
interface fxp0.0 {
disable;
}
interface lo0.0 {
passive;
}
}
link-management {
te-link sonet {
local-address 10.35.1.1;
remote-address 10.35.1.2;
remote-id 8070;
interface so-0/1/2 {
remote-id 21303;
}
}
peer router4 {
address 10.255.71.244;
lmp-control-channel so-1/1/0.0 {
remote-address 10.35.100.22;
}
te-link sonet;
}
traceoptions {
file lmp.logs size 5m files 10 world-readable;
flag hello-packets;
flag packets;
flag state;
}
}
}

On Router 2, configure IS-IS, MPLS, and RSVP to provide backbone connectivity for GMPLS and LMP between Routers 1 and 3.

Router 2

[edit]
interfaces {
so-1/1/0 {
description “Connection to Router 3”;
unit 0 {
family inet {
address 10.35.100.5/30;
}
family iso;
family mpls;
}
}
so-5/0/0 {
description “Connection to Router 1”;
unit 0 {
family inet {
address 10.35.100.2/30;
}
family iso;
family mpls;
}
}
lo0 {
unit 0 {
family inet {
address 10.255.71.242/32;
}
family iso {
address 47.0005.0000.0000.0000.0000.0000.0102.5507.1242.00;
}
}
}
}
routing-options {
router-id 10.255.71.242;
}
protocols {
rsvp {
interface all;
}
mpls {
interface all;
}
isis {
interface so-1/1/0.0;
interface so-5/0/0.0;
interface fxp0.0 {
disable;
}
interface lo0.0 {
passive;
}
}
link-management {
traceoptions {
file lmp.logs size 5m files 10 world-readable;
flag hello-packets;
flag packets;
flag state;
}
}
}

The configuration of Router 3 is very similar to the configuration on Router 2. Configure IS-IS, MPLS, and RSVP to provide backbone connectivity for GMPLS and LMP between Routers 2 and 4.

Router 3

[edit]
interfaces {
so-0/1/1 {
description “Connection to Router 2”;
unit 0 {
family inet {
address 10.35.100.6/30;
}
family iso;
family mpls;
}
}
so-1/1/0 {
description “Connection to Router 4”;
unit 0 {
family inet {
address 10.35.100.21/30;
}
family iso;
family mpls;
}
}
lo0 {
unit 0 {
family inet {
address 10.255.71.243/32;
}
family iso {
address 47.0005.0000.0000.0000.0000.0000.0102.5507.1243.00;
}
}
}
}
routing-options {
router-id 10.255.71.243;
}
protocols {
rsvp {
interface all;
}
mpls {
interface all;
}
isis {
interface so-0/1/1.0;
interface so-1/1/0.0;
interface fxp0.0 {
disable;
}
interface lo0.0 {
passive;
}
}
link-management {
traceoptions {
file lmp.logs size 5m files 10 world-readable;
flag hello-packets;
flag packets;
flag state;
}
}
}

On Router 4, complete the example by configuring IS-IS, MPLS, and RSVP to support the LMP control channel. For the control channel, use the so-6/0/0 interface as the origin and specify 10.35.100.1 (the so-1/1/0 interface on Router 1) as the remote address. For the TE link, use the so-3/0/2 interface as the origin, swap the local address and remote address pair configured on Router 1 and add them here, and configure the remote IDs to match the local IDs generated by the remote peer.

Because GMPLS LSPs are bidirectional by default, you do not need to configure a return path to Router 1.

Router 4

[edit]
interfaces {
so-3/0/2 {
description “Data channel to Router 1”;
unit 0 {
family inet {
address 10.35.100.10/30;
}
family iso;
family mpls;
}
}
so-6/0/0 {
description “Control channel to Router 1”;
unit 0 {
family inet {
address 10.35.100.22/30;
}
family iso;
family mpls;
}
}
lo0 {
unit 0 {
family inet {
address 10.255.71.244/32;
}
family iso {
address 47.0005.0000.0000.0000.0000.0000.0102.5507.1244.00;
}
}
}
}
routing-options {
router-id 10.255.71.244;
}
protocols {
rsvp {
interface all;
}
mpls {
interface all;
}
isis {
interface so-6/0/0.0;
interface fxp0.0 {
disable;
}
interface lo0.0 {
passive;
}
}
link-management {
te-link sonet {
local-address 10.35.1.2;
remote-address 10.35.1.1;
remote-id 8070;
interface so-3/0/2 {
remote-id 22279;
}
}
peer router1 {
address 10.255.71.241;
lmp-control-channel so-6/0/0.0 {
remote-address 10.35.100.1;
}
te-link sonet;
}
traceoptions {
file lmp.logs size 5m files 10 world-readable;
flag hello-packets;
flag packets;
flag state;
}
}
}
[Contents] [Prev] [Next] [Index] [Report an Error]

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