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

Example: GMPLS Configuration

Figure 3: GMPLS Topology Diagram

Image g017148.gif

In Figure 3, a control channel is established between Router A and OXC1, OXC1 and OXC2, and OXC2 and Router C. A data channel is enabled on a second connection between each pair of devices. The optical network cloud can contain OXCs, ADMs, or other lower-layer devices. In this example, OXC1 and OXC2 are in the direct data path between Routers A and C and the two OXCs have point-to-point connectivity with each other and the directly connected peer routers.

Starting with Router A, configure LMP TE links and peers to create a data channel and a control channel to connect with OXC1. To differentiate the logical TE link from the physical network, the local and remote addresses in the TE link are not related to the IP addresses assigned to the physical interfaces.

When you enable LMP peering on both Router A and OXC1, include the control channel interface as one of the peer statements. Use the name of the peer (in this case, oxc1) as the peer interface name when you add the peer-interface statement to RSVP at the [edit protocols rsvp] hierarchy level and OSPF at the [edit protocols ospf area area-number] hierarchy level.

The peer-interface statement adds the remote address and local address from your LMP configuration into the routing and signaling processes activated between Router A and OXC1. Make sure the physical control channel is a point-to-point link and has some form of IP reachability through static routes, an interior gateway protocol (IGP), or BGP (this example uses OSPF). Another way to achieve point-to-point links, especially if there are multiple hops between peers, is to use a generic routing encapsulation (GRE) tunnel for the control channel.

Next, configure an MPLS LSP on Router A to reach Router C. For this example, assume your data plane connection uses STM1 and Point-to-Point Protocol (PPP) over a fiber-switched network. Configure these LSP attributes in the LSP. Because this LSP does not use packet switching, a bidirectional LSP is enabled by default. As a result, you do not need to configure a return path LSP on Router C.

Finally, remember to discover the local IDs and configure them on OXC1 with the remote-id statement at the [edit protocols link-management te-link te-link-name] and [edit protocols link-management te-link te-link-name interface] hierarchy levels. For Router A, use the command show link-management te-link to find Router A’s two local IDs (te-link and interface); then configure these IDs as remote IDs on OXC1 at the equivalent hierarchy levels.

Router A



[edit]
interfaces {


so-0/0/0 {
description “Data channel to OXC1”;
encapsulation ppp;


unit 0 {


family inet {


address 10.255.3.2/30 {
destination 10.255.3.1;
}


}


family mpls;
}


}




so-0/3/0 {
description “Control channel to OXC1”;
encapsulation ppp;


unit 0 {


family inet {


address 10.255.6.1/30 {
destination 10.255.6.2;
}


}


family mpls;
}


}




lo0 {


unit 0 {


family inet {
address 10.255.255.35/32;
}


}


}


}
protocols 

rsvp {


interface all;




interface so-0/3/0.0 {


disable;


}




peer-interface oxc1;

}

mpls {




label-switched-path gmpls-lsp1 {


to 10.255.255.40;




lsp-attributes {


signal-bandwidth stm-1;


switching-type fiber;


gpid ppp;

}



primary path-lsp1;


}






path path-lsp1 {

10.35.100.1 strict; # This example does not disable CSPF,
10.35.150.1 strict; # so this step is optional.
10.35.200.1 strict;
}


interface all;
}

ospf {



area 0.0.0.0 {
interface lo0.0;


interface fxp0.0 {
disable;
}



peer-interface oxc1;

}


}

link-management {




te-link te-oxc1 {


local-address 10.35.100.2;


remote-address 10.35.100.1;


remote-id 8256;




interface t3-3/3/0:0 {


local-address 10.35.100.2;


remote-address 10.35.100.1;


remote-id 65536;

}


}





peer oxc1 {


address 10.255.255.69;


control-channel so-0/3/0.0;


te-link te-oxc1;

}


}

On OXC1, complete your configuration of the control channel and the TE link data channel to Router A. Refer to your OXC vendor’s instructions to configure a TE link on your specific device. Enable LMP peering, configure Router A’s local IDs as remote IDs on OXC1, and discover OXC1’s local IDs. Finally, configure OXC1’s local IDs as remote IDs on Router A.

In the optical network between your OXCs, configure a TE link and a control channel between OXC1 and OXC2. Refer to the OXC vendor’s instructions to configure this link. For the example shown in Figure 3, you can assume a TE link with an address space of 10.255.150.x/30 has been enabled over a physical network with IP addresses 10.255.2.x/30. Also, a control channel has been created over the 10.255.4.x/30 link.

On OXC2, configure a TE link to Router A. Refer to your OXC vendor’s instructions to configure this TE link on your device. Enable LMP peering, configure Router C’s local IDs as remote-IDs on OXC2, and discover OXC2’s local IDs. Finally, configure OXC2’s local IDs as remote IDs on Router C.

Now you are ready to complete this GMPLS example. On Router C, set up your TE link, LMP peer, and control channel statements to connect to OXC2. As with Router A, the local and remote addresses in the TE link on Router C are not related to the IP addresses assigned to the physical interface.

Next, configure RSVP, MPLS, and OSPF to match the control channel protocols you configured on Router A. You do not need to set up an LSP on Router C because Router A’s nonpacket LSP is bidirectional by default. Also, because RSVP is enabled for all interfaces and you are using a peer interface, you must disable RSVP on the physical control channel interface so-0/3/2.

After you enable LMP on both Router C and OXC2, discover the local IDs and configure them as remote IDs on OXC2. For Router C, use the command show link-management te-link to discover Router C’s two local IDs (te-link and interface); then configure these IDs as remote IDs on OXC2 at the equivalent hierarchy levels.

Router C



[edit]
interfaces {


so-0/3/2 {
description “Control channel to OXC2”;


unit 0 {


family inet {


address 10.255.4.2/30 {
destination 10.255.4.1;
}


}


family mpls;
}


}




so-0/1/0 {
description “Data channel to OXC2”;
encapsulation ppp;


unit 0 {


family inet {


address 10.255.1.1/30 {
destination 10.255.1.2;
}


}


family mpls;
}


}




lo0 {


unit 0 {


family inet {
address 10.255.255.40/32;
}


}


}


}
protocols 

rsvp {


interface all;




interface so-0/3/2.0 {


disabled;

}



peer-interface oxc2;

}

mpls {

interface all;
}

ospf {



area 0.0.0.0 {


interface fxp0.0 {
disable;
}


interface lo0.0;

peer-interface oxc2;

}


}

link-management {




te-link te-oxc2 {


local-address 10.35.200.1;


remote-address 10.35.200.2;


remote id 41060;




interface so-0/1/0 {


local-address 10.35.200.1;


remote-address 10.35.200.2;


remote-id 22278;

}


}





peer oxc2 {


address 10.255.255.37;


control-channel so-0/3/2.0;


te-link te-oxc2;

}


}

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