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

Example: LMP Control Channel Configuration

Figure 4: LMP Control Channel Topology Diagram

Image g017251.gif

Figure 4 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;
}
}
}

Verifying Your Work

To verify proper operation of LMP control channels, use the following commands:

The following sections show the output of these commands used with the configuration example:

Router 1 Status

On Router 1, issue the show link-management commands to verify if the control channel, TE links, and LMP negotiations are working as expected. The show link-management peer command indicates peer addresses, names, and identifiers, as well as control channel identifiers. The show link-management statistics command shows the number of LMP hellos and messages that have been exchanged. The show link-management te-link command displays names and identifiers configured for the TE link.


user@router1> show link-management peer
Peer name: router4, System identifier: 37495
 State: Up, Control address: 10.255.70.103
   CC local ID CC remote ID State       TxSeqNum  RcvSeqNum Flags
         22515        38882 Up              1692       1691 
  TE links:
   sonet

user@router1> show link-management statistics
Statistics for peer router4
    Received packets
        ConfigAck: 1
        Hello: 748
        LinkSummary: 13
        LinkSummaryAck: 1
    Small packets: 0
    Wrong protocol version: 0
    Messages for unknown peer: 0
    Messages for bad state: 0
    Stale acknowledgements: 0
    Stale negative acknowledgements: 0
    Sent packets
        Config: 24
        Hello: 748  
        LinkSummary: 13
        LinkSummaryAck: 13
    Retransmitted packets
        Config: 18
        LinkSummary: 9
    Dropped packets
        Config: 5
        LinkSummary: 3

user@router1> show link-management te-link
 TE link name: sonet, State: Up
  Local identifier: 8070, Remote identifier: 8070, Local address: 10.35.1.1,
  Remote address: 10.35.1.2, Encoding: SDH/SONET, Switching: PSC-1,
  Minimum bandwidth: 622.08Mbps, Maximum bandwidth: 622.08Mbps,
  Total bandwidth: 622.08Mbps, Available bandwidth: 622.08Mbps
    Name        State Local ID  Remote ID      Bandwidth Used  LSP-name
    so-0/1/2    Up       22279      21303     622.08Mbps   No

Router 4 Status

On Router 4, issue the show link-management commands to verify if the control channel, TE links, and LMP negotiations are being reciprocated by Router 1.


user@router4> show link-management peer 
Peer name: router1, System identifier: 56483
 State: Up, Control address: 10.255.71.242
   CC local ID CC remote ID State       TxSeqNum  RcvSeqNum Flags
         38882        22515 Up              1451       1450 
  TE links:
   sonet

user@router4> show link-management statistics
Statistics for peer router1
    Received packets
        Config: 1
        Hello: 255
        LinkSummary: 1
        LinkSummaryAck: 1
    Small packets: 0
    Wrong protocol version: 0
    Messages for unknown peer: 0
    Messages for bad state: 0
    Stale acknowledgements: 0
    Stale negative acknowledgements: 0
    Sent packets
        Config: 31
        ConfigAck: 1
        Hello: 255
        LinkSummary: 13
        LinkSummaryAck: 1
    Retransmitted packets
        Config: 23
        LinkSummary: 9
    Dropped packets
        Config: 7
        LinkSummary: 3

user@router4> show link-management te-link
TE link name: sonet, State: Up
  Local identifier: 8070, Remote identifier: 8070, Local address: 10.35.1.2,
  Remote address: 10.35.1.1, Encoding: SDH/SONET, Switching: PSC-1,
  Minimum bandwidth: 622.08Mbps, Maximum bandwidth: 622.08Mbps,
  Total bandwidth: 622.08Mbps, Available bandwidth: 622.08Mbps
    Name        State Local ID  Remote ID      Bandwidth Used  LSP-name
    so-3/0/2    Up       21303      22279     622.08Mbps   No
[ Contents] [ Prev] [ Next] [ Index] [ Report an Error]