Example: GMPLS Configuration
Figure 1: GMPLS Topology Diagram
In Figure 1, 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 traffic engineering links and peers to create a data channel and a control channel to connect with OXC1. To differentiate the logical traffic engineering link from the physical network, the local and remote addresses in the traffic engineering 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
On OXC1, complete your configuration of the control channel and the traffic engineering link data channel to Router A. Refer to your OXC vendor’s instructions to configure a traffic engineering 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 traffic engineering 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 1, you can assume a traffic engineering 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 traffic engineering link to Router A. Refer to your OXC vendor’s instructions to configure this traffic engineering 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 traffic engineering link, LMP peer, and control channel statements to connect to OXC2. As with Router A, the local and remote addresses in the traffic engineering 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
Verifying Your Work
To verify proper operation of GMPLS, you can use the following commands:
- show link-management (te-link | peer)
- show link-management routing (te-link | peer)
- show mpls lsp (bidirectional | unidirectional)
- show mpls lsp (detail | extensive)
- show ospf interface
- show ospf neighbor
- show rsvp interface link-management
- show rsvp session (bidirectional | unidirectional)
- show rsvp session te-link
- show rsvp session detail
- show rsvp neighbor detail
- show ted database extensive
- traceroute (using the lsp flag with RSVP protocol–level trace options)
The following sections show the output of these commands used with the configuration example:
Router A Status
After you enter the local-address, remote-address, and interface parameters in traffic engineering link te-oxc1 and commit the changes, the router automatically creates a local ID at the te-link and interface levels of the [edit protocols link-management] hierarchy. To view these IDs, issue the show link-management te-link command.
user@RouterA> show link-management te-link TE link name: te-oxc1 , State: Up Local identifier: 8255, Remote identifier: 0 , Local address: 10.35.100.2, Remote address: 10.35.100.1, Encoding: SDH/SONET, Minimum bandwidth: 155.52Mbps, Maximum bandwidth: 155.52Mbps, Total bandwidth: 155.52Mbps, Available bandwidth: 0bps Name Local ID Remote ID Bandwidth In use LSP so-0/0/0 65535 0 155.52Mbps No
Once you find these values on Router A, configure them as remote IDs at the same hierarchy levels on OXC1. In this example, 8255 is Router A’s local traffic engineering link ID (configure this as the traffic engineering link remote-ID on OXC1) and 65535 is Router A’s local interface ID (configure this as the interface remote-ID on OXC1).
After you configure both remote IDs on both peers, the GMPLS traffic engineering links should work. Using the same command as before, you can verify whether the link is functional, with both remote and local IDs in place:
user@RouterA> show link-management te-linkTE link name: te-oxc1, State: Up Local identifier: 8255, Remote identifier: 8256, Local address: 10.35.100.2, Remote address: 10.35.100.1, Encoding: SDH/SONET, Minimum bandwidth: 155.52Mbps, Maximum bandwidth: 155.52Mbps, Total bandwidth: 155.52Mbps, Available bandwidth: 0bps Name Local ID Remote ID Bandwidth In use LSP so-0/0/0 65535 65536 155.52Mbps Yes gmpls-lsp1
To further verify proper operation, use the following commands:
user@RouterA> show link-management routing
peerPeer name: oxc1, System identifier: 13892
State: Up, Control address: 10.255.255.69
Control-channel State
so-0/3/0.0 Active
user@RouterA> show link-management routing te-link
TE link name: te-oxc1, State: Up
Local identifier: 8255, Remote identifier: 8256, Local address: 10.35.100.2, Remote address: 10.35.100.1, Encoding: SDH/SONET,
Minimum bandwidth: 155.52Mbps, Maximum bandwidth: 155.52Mbps, Total bandwidth: 155.52Mbps, Available bandwidth: 0bps
user@RouterA> show link-management peer
Peer name: oxc1, System identifier: 13892
State: Up, Control address: 10.255.255.69
Control-channel State
so-0/3/0.0 Active
TE links:
te-oxc1
user@RouterA> show mpls lsp bidirectional
Ingress LSP: 1 sessions
To From State Rt ActivePath P LSPname
10.255.255.40 10.255.255.35 Up 0 path-lsp1 * gmpls-lsp1 Bidir
Total 1 displayed, Up 1, Down 0
Egress LSP: 0 sessions
Total 0 displayed, Up 0, Down 0
Transit LSP: 0 sessions
Total 0 displayed, Up 0, Down 0
user@RouterA> show mpls lsp bidirectional extensive
Ingress LSP: 1 sessions
10.255.255.40
From: 10.255.255.35, State: Up, ActiveRoute: 0, LSPname: gmpls-lsp1
Bidirectional
ActivePath: path-lsp1 (primary)
LoadBalance: Random
Signal type: STM-1
Encoding type: SDH/SONET, Switching type: Fiber, GPID: PPP
*Primary path-lsp1 State: Up
Bandwidth: 155.52Mbps
Computed ERO (S [L] denotes strict [loose] hops): (CSPF metric: 2)
10.35.100.1 S 10.35.150.1 S 10.35.200.1 S
Received RRO:
10.35.100.1 10.35.150.1 10.35.200.1
7 Nov 7 15:47:11 Selected as active path
6 Nov 7 15:47:11 Record Route: 10.35.100.1 10.35.150.1 10.35.200.1
5 Nov 7 15:47:11 Up
4 Nov 7 15:47:11 Update LSP Encoding Type
3 Nov 7 15:47:11 Originate Call
2 Nov 7 15:47:11 CSPF: computation result accepted
1 Nov 7 15:46:41 CSPF failed: no route toward 10.255.255.40
Created: Thu Nov 7 15:46:38 2002
Total 1 displayed, Up 1, Down 0
Egress LSP: 0 sessions
Total 0 displayed, Up 0, Down 0
Transit LSP: 0 sessions
Total 0 displayed, Up 0, Down 0
If you configure an LMP peer interface in OSPF, you can see that this virtual interface is treated as a point-to-point link. To view this, use the show ospf interface command.
user@RouterA> show ospf interface Interface State Area DR ID BDR ID Nbrs lo0.0 DR 0.0.0.0 10.255.255.35 0.0.0.0 0 oxc1 PtToPt 0.0.0.0 0.0.0.0 0.0.0.0 1
The next command is useful because it indicates whether RSVP is disabled on the control channel. It also shows the state of the reservations on the traffic engineering links.
user@RouterA> show rsvp interface link-management RSVP interface: 1 active
oxc1 State Up
Active control channel: so-0/3/0.0 RSVP disabled
TElink: te-oxc1, Local identifier: 8255
ActiveResv 1, PreemptionCnt 0
StaticBW: 155.52Mbps, ReservedBW: 155.52Mbps, AvailableBW: 0bps
user@RouterA> show rsvp session detail
Ingress RSVP: 1 sessions
10.255.255.40
From: 10.255.255.35, LSPstate: Up, ActiveRoute: 0
LSPname: gmpls-lsp1, LSPpath: Primary
Bidirectional, Upstream label in: 27676, Upstream label out: -
Suggested label received: -, Suggested label sent: 27676
Recovery label received: -, Recovery label sent: 60444
Resv style: 1 FF, Label in: -, Label out: 60444
Time left: -, Since: Thu Nov 7 15:47:11 2002
Tspec: rate 0bps size 0bps peak 1.544Mbps m 20 M 1500
Port number: sender 1 receiver 17 protocol 0
PATH rcvfrom: localclient
PATH sentto: 10.255.255.40 (oxc1) 157 pkts
RESV rcvfrom: 10.255.255.40 (oxc1) 71 pkts
Explct route: 10.35.100.1 10.35.150.1 10.35.200.1
Record route: <self> 10.35.100.1 10.35.150.1 10.35.200.1
Total 1 displayed, Up 1, Down 0
Egress RSVP: 0 sessions
Total 0 displayed, Up 0, Down 0
Transit RSVP: 0 sessions
Total 0 displayed, Up 0, Down 0
user@RouterA> show rsvp session bidirectional
Ingress RSVP: 1 sessions
To From State Rt Style Labelin Labelout LSPname
10.255.255.40 10.255.255.35 Up 0 1 FF - 60444 gmpls-lsp1 Bidir
Total 1 displayed, Up 1, Down 0
Egress RSVP: 0 sessions
Total 0 displayed, Up 0, Down 0
Transit RSVP: 0 sessions
Total 0 displayed, Up 0, Down 0
user@RouterA> show rsvp session te-link te-oxc1
Ingress RSVP: 1 sessions
To From State Rt Style Labelin Labelout LSPname
10.255.255.40 10.255.255.35 Up 0 1 FF - 60444 gmpls-lsp1 Bidir
Total 1 displayed, Up 1, Down 0
Egress RSVP: 0 sessions
Total 0 displayed, Up 0, Down 0
Transit RSVP: 0 sessions
Total 0 displayed, Up 0, Down 0
user@RouterA> show ted database extensive
TED database: 0 ISIS nodes 4 INET nodes
NodeID: 10.255.255.35
Type: Rtr, Age: 2178 secs, LinkIn: 4, LinkOut: 5
Protocol: OSPF(0.0.0.0)
To: 10.255.255.69, Local: 10.35.100.2, Remote: 10.35.100.1
Metric: 1
Static BW: 155.52Mbps
Reservable BW: 155.52Mbps
Available BW [priority] bps:
[0] 0bps [1] 0bps [2] 0bps [3] 0bps
[4] 0bps [5] 0bps [6] 0bps [7] 0bps
Interface Switching Capability Descriptor(1):
Switching type: Fiber
Encoding type: SDH/SONET
Maximum LSP BW [priority] bps:
[0] 155.52Mbps [1] 155.52Mbps [2] 155.52Mbps [3] 155.52Mbps
[4] 155.52Mbps [5] 155.52Mbps [6] 155.52Mbps [7] 155.52Mbps
Minimum LSP BW: 155.52Mbps
Interface MTU: 2595
NodeID: 10.255.255.37
Type: Rtr, Age: 2852 secs, LinkIn: 5, LinkOut: 5
Protocol: OSPF(0.0.0.0)
To: 10.255.255.69, Local: 10.35.150.1, Remote: 10.35.150.2
Metric: 1
Static BW: 622.08Mbps
Reservable BW: 622.08Mbps
Available BW [priority] bps:
[0] 622.08Mbps [1] 622.08Mbps [2] 622.08Mbps [3] 622.08Mbps
[4] 622.08Mbps [5] 622.08Mbps [6] 622.08Mbps [7] 622.08Mbps
Interface Switching Capability Descriptor(1):
Switching type: Fiber
Encoding type: SDH/SONET
Maximum LSP BW [priority] bps:
[0] 622.08Mbps [1] 622.08Mbps [2] 622.08Mbps [3] 622.08Mbps
[4] 622.08Mbps [5] 622.08Mbps [6] 622.08Mbps [7] 622.08Mbps
Minimum LSP BW: 622.08Mbps
Interface MTU: 2597
To: 10.255.255.40, Local: 10.35.200.2, Remote: 10.35.200.1
Metric: 1
Static BW: 155.52Mbps
Reservable BW: 155.52Mbps
Available BW [priority] bps:
[0] 0bps [1] 0bps [2] 0bps [3] 0bps
[4] 0bps [5] 0bps [6] 0bps [7] 0bps
Interface Switching Capability Descriptor(1):
Switching type: Fiber
Encoding type: SDH/SONET
Maximum LSP BW [priority] bps:
[0] 155.52Mbps [1] 155.52Mbps [2] 155.52Mbps [3] 155.52Mbps
[4] 155.52Mbps [5] 155.52Mbps [6] 155.52Mbps [7] 155.52Mbps
Minimum LSP BW: 155.52Mbps
Interface MTU: 2600
NodeID: 10.255.255.40
Type: Rtr, Age: 2854 secs, LinkIn: 2, LinkOut: 2
Protocol: OSPF(0.0.0.0)
To: 10.255.255.37, Local: 10.35.200.1, Remote: 10.35.200.2
Metric: 1
Static BW: 155.52Mbps
Reservable BW: 155.52Mbps
Available BW [priority] bps:
[0] 0bps [1] 0bps [2] 0bps [3] 0bps
[4] 0bps [5] 0bps [6] 0bps [7] 0bps
Interface Switching Capability Descriptor(1):
Switching type: Fiber
Encoding type: SDH/SONET
Maximum LSP BW [priority] bps:
[0] 155.52Mbps [1] 155.52Mbps [2] 155.52Mbps [3] 155.52Mbps
[4] 155.52Mbps [5] 155.52Mbps [6] 155.52Mbps [7] 155.52Mbps
Minimum LSP BW: 155.52Mbps
Interface MTU: 2600
NodeID: 10.255.255.69
Type: Rtr, Age: 2832 secs, LinkIn: 8, LinkOut: 7
Protocol: OSPF(0.0.0.0)
To: 10.255.255.35, Local: 10.35.100.1, Remote: 10.35.100.2
Metric: 1
Static BW: 155.52Mbps
Reservable BW: 155.52Mbps
Available BW [priority] bps:
[0] 0bps [1] 0bps [2] 0bps [3] 0bps
[4] 0bps [5] 0bps [6] 0bps [7] 0bps
Interface Switching Capability Descriptor(1):
Switching type: Fiber
Encoding type: SDH/SONET
Maximum LSP BW [priority] bps:
[0] 155.52Mbps [1] 155.52Mbps [2] 155.52Mbps [3] 155.52Mbps
[4] 155.52Mbps [5] 155.52Mbps [6] 155.52Mbps [7] 155.52Mbps
Minimum LSP BW: 155.52Mbps
Interface MTU: 2595
To: 10.255.255.37, Local: 10.35.150.2, Remote: 10.35.150.1
Metric: 1
Static BW: 622.08Mbps
Reservable BW: 622.08Mbps
Available BW [priority] bps:
[0] 622.08Mbps [1] 622.08Mbps [2] 622.08Mbps [3] 622.08Mbps
[4] 622.08Mbps [5] 622.08Mbps [6] 622.08Mbps [7] 622.08Mbps
Interface Switching Capability Descriptor(1):
Switching type: Fiber
Encoding type: SDH/SONET
Maximum LSP BW [priority] bps:
[0] 622.08Mbps [1] 622.08Mbps [2] 622.08Mbps [3] 622.08Mbps
[4] 622.08Mbps [5] 622.08Mbps [6] 622.08Mbps [7] 622.08Mbps
Minimum LSP BW: 622.08Mbps
Interface MTU: 2597
user@RouterA> show rsvp neighbor detail
RSVP neighbor: 1 learned
Address: 10.255.255.40 via: oxc1 status: Up
Last changed time: 50:52, Idle: 0 sec, Up cnt: 1, Down cnt: 0
Message received: 145
Hello: sent 338, received: 338, interval: 9 sec
Remote instance: 0x643087c7, Local instance: 0x3271e0a4
Refresh reduction: not operational
Link protection: disabled
Bypass LSP: does not exist, Backup routes: 0, Backup LSPs: 0
Router C Status
After you enter the local-address, remote-address, and interface parameters in traffic engineering link te-oxc2 and commit the changes, the router automatically creates a local ID at the te-link and interface levels of the [edit protocols link-management] hierarchy. To view these IDs, issue the show link-management te-link command.
user@RouterC> show link-management te-link TE link name: te-oxc2, State: Up Local identifier: 41059, Remote identifier: 0, Local address: 10.35.200.1, Remote address: 10.35.200.2, Encoding: SDH/SONET, Minimum bandwidth: 155.52Mbps, Maximum bandwidth: 155.52Mbps, Total bandwidth: 155.52Mbps, Available bandwidth: 0bps Name Local ID Remote ID Bandwidth In use LSP so-0/1/0 22277 0 155.52Mbps No
Once you see what these values are, configure them as remote IDs at the same hierarchy levels on OXC2 where you found them on Router C. In this example, 41059 is Router C’s local traffic engineering link ID (configure this as the traffic engineering link remote-ID on OXC2) and 22277 is Router C’s local interface ID (configure this as the interface remote-ID on OXC2).
After you configure both remote IDs on both peers, the GMPLS traffic engineering links should work. Using the same command as before, you can determine whether the link is functional, with both remote and local IDs in place:
user@RouterC> show link-management te-linkTE link name: te-oxc2, State: Up Local identifier: 41059, Remote identifier: 41060, Local address: 10.35.200.1, Remote address: 10.35.200.2, Encoding: SDH/SONET, Minimum bandwidth: 155.52Mbps, Maximum bandwidth: 155.52Mbps, Total bandwidth: 155.52Mbps, Available bandwidth: 0bps Name Local ID Remote ID Bandwidth In use LSP so-0/1/0 22277 22278 155.52Mbps Yes gmpls-lsp1
The other show commands operate like those in Router A Status.
