Basic MPLS Configuration
Basic MPLS Configuration
Table of Contents
Basic MPLS Configuration .......................................................................... 1
Frame-Mode MPLS Configuration and Verification ..................................................................................................................... 1
Cell-Mode MPLS over ATM Overview, Configuration, and Verification .................................................................................... 15
Command Reference .................................................................................................................................................................... 45
Page 1
Licensed by
Alex Hannah
- Frame-mode MPLS over RFC 2684 (obsoletes RFC 1483) routed PVC
Cell-mode MPLS over ATM configuration and verification
- Basic cell-mode MPLS configuration and verification
- Configuring cell-mode MPLS with and without virtual circuit merge (VC-merge)
- MPLS over VP tunnels configuration and verification
- Configuring MPLS over ATM using BPX ATM switch and 7200 as label switch
controller (LSC)
Page 2
Figure 2-2 illustrates the configuration flowchart to implement frame-mode MPLS on the
provider network shown in Figure 2-1. The configuration flowchart assumes that IP
addresses are preconfigured where required.
Figure 2-2. Frame-Mode MPLS Configuration Flowchart
Page 3
Page 4
Step 3. Assign LDP router IDLDP uses the highest IP address on a loopback
interface as the LDP router ID. If there is no loopback address defined, the
highest IP address on the router becomes the LDP router ID. To force an
interface to be an LDP router ID, mpls ldp router-idinterface-type
number command can be used. The loopback interface address is
recommended because it always remains up. Configure the loopback 0
interface on the R2 router to be the LDP router ID as shown in Example 2-3.
Repeat the configuration on R1, R3, and R4, assigning the local loopback
interface as LDP router-id.
Example 2-3. Assign LDP Router ID
R2#show ip cef
%CEF not running
Prefix
Next Hop
Interface
_____________________________________________________________________
R2#show cef interface serial 0/0
Serial0/0 is up (if_number 5)
Page 5
(Output truncated)
IP CEF switching enabled
IP CEF Fast switching turbo vector
(Output Truncated)
_____________________________________________________________________
R2#show cef interface serial 0/1
Serial0/1 is up (if_number 6)
(Output Truncated)
IP CEF switching enabled
IP CEF Fast switching turbo vector
Step 2. Verify MPLS forwarding is enabled on the interfaces by issuing the show
mpls interfaces command. Example 2-6 shows that MPLS is enabled on the
serial interfaces. The IP column depicts Yes if IP label switching is enabled on
the interface. The Tunnel column is Yes if LSP tunnel labeling (discussed later
in Chapter 9, "MPLS Traffic Engineering") is enabled on the interface, and the
Operational column is Yes if packets are labeled on the interface.
Example 2-6. MPLS Forwarding Verification
Tunnel
No
No
Operational
Yes
Yes
Step 3. Verify the status of the Label Distribution Protocol (LDP) discovery process
by issuing show mpls ldp discovery. This command displays neighbor
discovery information for LDP and shows the interfaces over which the LDP
discovery process is running. Example 2-7 shows that R2 has discovered two
LDP neighbors, 10.10.10.101 (R1) and 10.10.10.103 (R3). The xmit/recv field
indicates that the interface is transmitting and receiving LDP discovery Hello
packets.
Example 2-7. LDP Discovery Verification
Page 6
Step 4. Issue show mpls ldp neighbor to verify the status of the LDP neighbor
sessions. Example 2-8 shows that the LDP session between R2 and R1
(10.10.10.101), as well as between R2 and R3 (10.10.10.103), is operational.
Downstream indicates that the downstream method of label distribution is
being used for this LDP session in which the LSR advertises all of its locally
assigned (incoming) labels to its LDP peer (subject to any configured access
list restrictions).
Example 2-8. LDP Neighbor Verification
Page 7
Page 8
Bytes tag
switched
0
0
0
0
Outgoing
interface
Se0/0
Se1/0
Se1/0
Se1/0
Next Hop
point2point
point2point
point2point
point2point
Step 3. Example 2-11 shows that on R3, prefix 10.10.10.101/32 has been assigned a
local label of 17 and an outgoing label of 16. The outgoing label is received from
the Router R2. The local label of 17 has been propagated during label
distribution to Router R4. Label 17 is used by R4 in the data forwarding path
for data destined to prefix 10.10.10.101/32 located on R1 from R4.
Example 2-11. Label Allocation and Distribution Verification on R3
R3#show
Local
tag
16
17
18
19
mpls forwarding-table
Outgoing
Prefix
tag or VC
or Tunnel Id
Pop tag
10.10.10.0/30
16
10.10.10.101/32
Pop tag
10.10.10.102/32
Pop tag
10.10.10.104/32
Bytes tag
switched
0
0
0
0
Outgoing
interface
Se0/0
Se0/0
Se0/0
Se1/0
Next Hop
point2point
point2point
point2point
point2point
Page 9
Page 10
Figure 2-4 shows the network topology for RFC 2684 routed.
Page 11
Figure 2-4. Topology: Frame-Mode MPLS Over RFC 2684 Routed PVCs
Figure 2-5 illustrates the flowchart to configure frame-mode MPLS on the provider
network devices shown in Figure 2-4. The configuration flowchart assumes that IP
addresses are pre-configured where needed.
Figure 2-5. Frame-Mode MPLS Configuration Flowchart
Page 12
Figure 2-6 shows the flowchart for configuring the ATM PVC route on the LS1010 ATM
switch.
Figure 2-6. Configuration Flowchart for LS1010 ATM Switch
Configuration Steps for Frame-Mode MPLS Over RFC 2684 Routed PVC
The steps to configure RFC 2684 bridged encapsulation over MPLS on R1 and R2 are as
follows. Ensure that IP addresses are preconfigured on R1 and R2, as illustrated in Figure
2-4:
Step 1. Follow the steps shown in the "Basic Frame-Mode MPLS Configuration
Steps" section. These steps are the same for frame-mode MPLS over RFC 2684
routed PVC. Follow those steps to configure frame-mode MPLS on R1 and R2:
Step 1. Enable CEF
Step 2. Enable IGP routing protocol
Step 3. Assign LDP router ID
Step 2. Enable IPv4 MPLS or label forwarding on the interfaceConfigure
the ATM PVCs 2/200 on each of the appropriate subinterfaces on R1 and R2.
The encapsulation used on the PVC is ATM aal5snap. Example 2-16 highlights
the steps to configure ATM PVC.
Example 2-16. Configure PVCs on R1 and R2
Page 13
Verification Steps for Frame-Mode MPLS Over RFC 2684 Routed PVC
The steps to verify frame-mode MPLS over RFC 2684 (previously RFC 1483) routed PVC
are as follows:
Step 1. Verify the operation of MPLS over RFC 2684 by performing a view of the MPLS
forwarding information base (LFIB), as shown in Example 2-18.
Example 2-18. Verification of LFIB
Page 14
R1#ping 10.10.10.104
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.10.10.101, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/4 ms
R4#
R2#ping 10.10.10.101
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.10.10.101, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/4 ms
R4#
Final Device Configuration for Frame-Mode MPLS Over RFC 2684 Routed PVC
The final device configuration for R1, A1, A2, and R2 is shown in Example 2-20 through
Example 2-23.
Example 2-20. Configuration of R1
hostname R1
!
ip cef
!
interface Loopback0
ip address 10.10.10.101 255.255.255.255
!
interface Ethernet0
ip address 10.10.20.193 255.255.255.252
!
interface ATM2/0
no ip address
!
interface ATM2/0.2 point-to-point
description connection to A1
ip address 10.10.20.1 255.255.255.252
mpls ip
pvc 2/200
encapsulation aal5snap
!
router ospf 100
network 10.10.0.0 0.0.0.255 area 0
Page 15
Page 16
the number of virtual channels into a single pipe (virtual path) between sites that need a
large number of VCs.
The ATM switch is responsible for switching ATM cells on both the VC and VP. When the
ATM switch is configured to switch cells on a VC, it has to look at both VPI and VCI fields
of the cell in order to make a switching decision. Switching is done based on a table
containing (port, VPI, VCI) tuplets for the input and output side of the VC. On Cisco IOS
ATM switches, you can see this table with the show atm vc command. You can also
configure the ATM switch to switch cells based only on the port and VPI number; this is
called VP switching. For VP switching, the ATM switch uses a table consisting of (port,
VPI) pairs for input and output. You can see this table on Cisco IOS ATM switches with
the show atm vp command. When VP switching, the ATM switch uses only the VPI field
of each ATM cell to make a switching decision, which reduces processing time. The same
holds true for cell header rewrites. In VC switching, both VPI and VCI fields of the cell
header are rewritten and possibly changed. However, in VP switching, only VPI fields can
be changed, and the VCI field remains the same end-to-end.
Page 17
Figure 2-8. Basic Cell-Mode MPLS Configuration Flowchart for Edge ATM LSR
Page 18
Figure 2-9. Basic Cell-Mode MPLS Configuration Flowchart for ATM LSR
R1(config)#ip cef
Page 19
Page 20
A1(config)#interface atm1/0/0
A1(config-if)#mpls ip
A1(config)#interface atm 1/0/1
A1(config-if)#mpls ip
Note that no configuration has been made on the MPLS ATM subinterfaces on the Edge
ATM LSRs or LSRs with regards to the control-vc using the mpls atm control-vc
command. This implies that all the control plane information is propagated and exchanged
using the default control VC VPI/VCI values of 0/32. However, the user can change the
control-vc associated on an interface in a cell-mode MPLS network. Changes made to the
VPI/VCI values associated to the control-vc on an LSR interface must also be made on the
connected LSR's interface to enable proper exchange of control plane information.
Step 2. As shown in Example 2-30, verify that MPLS forwarding is enabled on the
appropriate interfaces on R1 and A1.
Example 2-30. Verify MPLS Forwarding
Page 21
Step 3. Verify the status of the LDP discovery process by issuing show mpls ldp
discovery. This command displays neighbor discovery information for LDP
and shows the interfaces over which the LDP discovery process is running.
Example 2-31 shows neighbor discovery information and interfaces where
LDP is running on R1 and A1. The xmit/recv field indicates that the interface
is transmitting and receiving LDP discovery Hello packets.
Example 2-31. Verify MPLS LDP Discovery
Step 4. Issue show mpls ldp neighbor to verify the status of LDP neighbor
sessions. Example 2-32 shows that the LDP session between R1 and A1 is
operational. Downstream on demand on R1 indicates the downstream on
demand method of label distribution is used for the LDP session between R1
and A1 in which the LSR (R1) advertises its locally assigned (incoming) labels
to its LDP peer, A1, only when A1 requests them.
Example 2-32. LDP Distribution Protocol Neighbor Verification
Page 22
R1#ping 10.10.10.104
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.10.10.104, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/4 ms
Page 23
Bytes tag
switched
0
0
0
0
Outgoing
interface
AT2/0.1
AT2/0.1
AT2/0.1
AT2/0.1
Next Hop
point2point
point2point
point2point
point2point
Page 24
28
1/39
10.10.20.102/32
0
AT2/0.1
point2point
_____________________________________________________________________
R1#show mpls atm-ldp bindings
Destination: 10.10.10.104/32
Headend Router ATM2/0.1 (3 hops) 1/35 Active, VCD=19
Destination: 10.10.20.4/30
Headend Router ATM2/0.1 (1 hop) 1/36 Active, VCD=13
Destination: 10.10.20.8/30
Headend Router ATM2/0.1 (2 hops) 1/37 Active, VCD=15
Destination: 10.10.20.101/32
Headend Router ATM2/0.1 (1 hop) 1/38 Active, VCD=14
Destination: 10.10.20.102/32
Headend Router ATM2/0.1 (2 hops) 1/39 Active, VCD=16
Destination: 10.10.10.101/32
Tailend Router ATM2/0.1 1/34 Active, VCD=18
Step 2. A1 uses the VPI/VCI 1/34 received from R1 as its outbound VPI/VCI value,
allocates a free VC that is mapped to the local inbound VPI/VCI 1/45, and
modifies the LFIB entry for 10.10.10.101/32. A1 then sends VPI/VCI value
1/45 to A2 via an LDP reply. Example 2-36 shows the output of show mpls
atm-ldp bindings. ATM LSR A1 prefix 10.10.10.104/32 has been assigned
a local tag of 1/35 and an outgoing tag of 1/43. The outgoing tag is received
from the downstream ATM LSR A2. During label distribution, the local tag of
1/35 has been propagated upstream to Router R1, which functions as the
outgoing tag for the specific prefix 10.10.10.104/32 on R1.
Example 2-36. Label Allocation and Distribution Verification on A1
Step 3. A2 uses the VPI/VCI 1/45 received from A1 as its outbound VPI/VCI value,
allocates a free VC that is mapped to the local inbound VPI/VCI 1/44, and
modifies the LFIB entry for 10.10.10.101/32. A2 then sends VPI/VCI value
1/44 to R2 via an LDP reply. Example 2-37 shows the output of show mpls
Page 25
Step 4. Edge ATM LSR R2 uses VPI/VCI value 1/44 received from A2 as its outbound
VPI/VCI value and modifies the entry in the LFIB. Example 2-38 shows the
output of show mpls atm-ldp bindings. As shown in Example 2-38 on
Edge ATM LSR R2, the mpls atm-ldp bindings show the local tag of 1/35
assigned to prefix 10.10.10.104/32. This local tag is propagated upstream to
ATM LSR A2 and functions as the next-hop tag or outgoing tag for prefix
10.10.10.104/32 on A2.
Example 2-38. Label Allocation and Distribution Verification on R2
Page 26
Destination: 10.10.20.101/32
Headend Router ATM2/0.1 (2 hops) 1/34 Active, VCD=15
Destination: 10.10.20.102/32
Headend Router ATM2/0.1 (1 hop) 1/35 Active, VCD=14
Destination: 10.10.10.101/32
Headend Router ATM2/0.1 (3 hops) 1/44 Active, VCD=18
Destination: 10.10.10.104/32
Tailend Router ATM2/0.1 1/35 Active, VCD=14
Page 27
Page 28
when two Edge LSRs are sending packets to the same destination, the ingress label
mapping to the two Edge LSRs are mapped to a single outgoing label. The number of VCs
required for label switching is greatly reduced as the ATM switch maintains just one
outgoing VC label for each destination prefix. VC-merge reduces the label space that needs
to be maintained by sharing labels for flows toward the same FEC or prefix.
Figure 2-11 shows a cell-mode MPLS network. This is the same as the network shown in
Figure 2-10 except the new Router R3 is added, which is connected to A1. Edge LSRs R1
and R3 share the same label space for the same destination prefixes on Edge ATM LSR
R2.
Figure 2-11. Cell-Mode MPLS Topology for VC-Merge
Depending upon the hardware, the ATM VC-merge capability is enabled by default;
otherwise, this feature is disabled. Please check Cisco Documentation at cisco.com.
Page 29
Configuration Steps for Cell-Mode MPLS with VC-Merge on Edge ATM LSR
The configuration steps for cell-mode MPLS with VC-merge on Edge ATM LSR are the
same as what was shown earlier in section "Configuration Steps for Edge ATM LSR."
Page 30
!
router ospf 100
network 10.10.0.0 0.0.255.255 area 0
VPI
Range
[1 - 1]
[1 - 1]
[1 - 1]
VCI
Range
[33 - 16383]
[33 - 16383]
[33 - 65530]
Alloc
Scheme
UNIDIR
UNIDIR
UNIDIR
Odd/Even
Scheme
VC-Merge
IN
OUT
EN
EN
-
ATM1/0/1
Negotiated
Local
Peer
VPI
Range
[1 - 1]
[1 - 1]
[1 - 1]
VCI
Range
[33 - 16383]
[33 - 16383]
[33 - 16383]
Alloc
Scheme
UNIDIR
UNIDIR
UNIDIR
Odd/Even
Scheme
VC-Merge
IN
OUT
EN
EN
Page 31
Page 32
Page 33
A1(config)#interface ATM1/0/1
A1(config-if)# description Connection to A2
A1(config-if)# no ip address
A1(config-if)# atm pvp 2 interface ATM1/0/0 2
_____________________________________________________________________
A2(config)#interface ATM1/0/1
A2(config-if)# description connection to A1
A2(config-if)# no ip address
A2(config-if)# atm pvp 2 interface ATM1/0/0 2
Step 2. Configure the VP tunnel using mpls atm vp-tunnelvpivc-range {start-ofvci-range-end-of-vci-range} under the MPLS ATM subinterface. Enable
MPLS on the created subinterface, as shown in Example 2-51.
Example 2-51. Configure VP Tunnel on ATM MPLS Subinterface
Step 3. Configure IGP for IP connectivity across the VP tunnel on R1 and R2, as shown
in Example 2-52.
Example 2-52. Configure IGP
Page 34
A1#show atm vp
Interface
VPI
Type X-Interface
X-VPI
Status
ATM1/0/0
2
PVP
ATM1/0/1
2
UP
ATM1/0/1
2
PVP
ATM1/0/0
2
UP
_____________________________________________________________________
A2#show atm vp
Interface
VPI
Type X-Interface
X-VPI
Status
ATM1/0/0
2
PVP
ATM1/0/1
2
UP
ATM1/0/1
2
PVP
ATM1/0/0
2
UP
Step 2. Verify OSPF routes on R1 by issuing show ip route ospf. Example 2-54
shows the networks received on R1 from R2.
Example 2-54. Verify OSPF Routes
Step 3. Verify connectivity across the VP tunnel using the ping command, as shown
in Example 2-55.
Example 2-55. Verify Connectivity Using Ping
Page 35
interface Ethernet0
ip address 10.10.20.193 255.255.255.252
!
interface ATM2/0
!
interface ATM2/0.1 mpls
description Connection to A1
ip address 10.10.20.1 255.255.255.252
mpls ip
mpls atm vp-tunnel 2 vci-range 33-65535
!
router ospf 100
network 10.10.0.0 0.0.255.255 area 0
Page 36
Implementing Cell-Mode MPLS with BPX8600 and 7200 as Label Switch Controller
Cell-mode MPLS can also be implemented by separating the control and data plane
functions of an ATM LSR. The control plane function is performed by a device called the
LSC or label switch controller, and the data plane function can be performed by an ATM
switch such as the BPX8600 Series ATM switches. In the BPX with LSC design, the LSC
is connected to the BPX ATM switch by trunks that can carry PVCs, SVCs, or MPLS Label
VCs (LVCs). The control software is physically located in the LSC that is connected to the
ATM switch by a physical connection also called the virtual switch interface (VSI) control
link. The VSI control link could be an STM-1 link connected to a single port of a broadband
switching module (BXM) linecard on the BPX8600. This is shown in Figure 2-14.
Figure 2-14. BPX with LSC as LSR
In Figure 2-14, the functions control plane is implemented using a BPX+LSC. The figure
outlines a connection from each of the Edge ATM LSRs to the LSC connected to the BPX
switch using LVCs. These signaling LVCs are maintained per LSR that the BPX+LSC is
connected to. In addition, VSI control links are maintained per card on the BPX.
Page 37
From a data plane perspective, data label VCs bypass the LSC and are switched using the
BPX ports. Therefore, in the data plane, the traffic via the ATM label switch router traverses
only the BPX ATM switch and not the LSC.
The signaling label VCs are on VPI/VCI values of 0/32 by default and will be crossconnected to a different VCI on the switch control link between the BPX and LSC. One key
thing to note is that the LSC functions as the VSI master and the BPX functions as the VSI
slave.
Figure 2-15 shows the physical connections for this section in which two Edge ATM LSRs
are connected to a BPX 8600 switch. The LSC (7200 router) is also connected on the same
switch. The numbers 2.1, 2.2, and 2.3 in Figure 2-15 pertain to slot.port on the BPX 8600
switch. The only IP addresses shown in this figure are those of the loopbacks on the LSR
and ELSRs. Figure 2-16 shows the Edge ATM LSRs connected to the LSC in the control
plane using the VSI control VCs as well as the signaling LVCs that originate from an
mpls subinterface on the Edge ATM LSR and terminate on an XtagATM interface on the
LSC. The XtagATM interface controls the trunks on the BPX that are connected to other
LSRs.
Page 38
bpxa
1
2
3
4
5
6
7
8
TRM
cisco:1
FrontCard
BackCard
Type
Rev Type Rev
BME-622 KMB SM-2 BD
BXM-155 FJL MM-8 BB
BXM-T3 FJL TE3-12BA
BXM-622 FML SM-2 BD
BXM-155 FAL SM-4 BB
BXM-622 FPH SM-2 BE
BCC-4
HDM LM-2 AC
Empty reserved for Card
BPX 8620
Status
Standby
Active
Active
Standby
Standby
Standby
Active
9
10
11
12
13
14
15
9.2.30
FrontCard
Type
Rev
Empty
Empty
Empty
Empty
Empty
Empty
ASM
ACC
Oct. 8 2004
15:18 MST
BackCard
Type Rev
Status
LMASM AC
Active
Step 2. Enable the trunks on the ports 2.1, 2.2, and 2.3. This is as shown in Example
2-60. Example 2-61 shows only the command to be used in the "next command"
section to enable the three trunks connecting to the two Edge ATM LSRs as well as
the LSC.
Page 39
When the trunks are configured, view the trunk configuration using the dsptrks
command, as shown in Example 2-62.
Example 2-62. Viewing Trunk Configuration
bpxa
TRK
2.1
2.2
2.3
TRM
Type
OC3
OC3
OC3
cisco:1
Current
Clear Clear Clear -
BPX 8620
9.2.30
Oct. 8 2004
15:26 MST
Other End
-
bpxa
TRM
Port/Trunk : 2.1
Maximum PVC LCNS:
Partition 1
Partition State :
Minimum VSI LCNS:
Maximum VSI LCNS:
Start VSI VPI:
End VSI VPI :
Minimum VSI Bandwidth :
VSI ILMI Config
:
VSI Topo Dsc
:
cisco:1
BPX 8620
256
Enabled
600
1500
240
255
105000
0
0
9.2.30
Oct. 8 2004
15:29 MST
105000
255
Last Command: cnfrsrc 2.1 256 247207 y 1 e 600 1500 240 255 105000 105000
The command in Example 2-63 can be explained as "configure resources for trunk
2.1 where the maximum PVC LCNs are 256, the maximum PVC bandwidth is
247207; editing of VSI information is enabled, Partition ID is 1 and is enabled; the
maximum VSI LCNs are 600 and the maximum VSI LCNs are 1500; the VSI VPIrange is configured to be between 240255 and the minimum and maximum VSI
bandwidths is 105000."
Page 40
Repeat this command to configure resources for trunks 2.2 and 2.3. However, all
trunks need to be part of the same partition (1). When completed, a dsprsrc issued
for the appropriate trunk and partition IDs, as shown in Example 2-64, shows the
resources allocated to the trunk.
Example 2-64. Display Configured Resources
bpxa
TRM
Port/Trunk : 2.2
Maximum PVC LCNS:
cisco:1
BPX 8620
256
Partition 1
Partition State :
Minimum VSI LCNS:
Maximum VSI LCNS:
Start VSI VPI:
End VSI VPI :
Minimum VSI Bandwidth :
VSI ILMI Config
:
VSI Topo Dsc
:
Enabled
512
1500
240
255
105000
0
0
9.2.30
Oct. 8 2004
15:37 MST
105000
255
Step 4. MPLS labeled packets use the queues 1014 on each port (one queue per class). To
enable MPLS packet forwarding, configure the queues using the cnfqbin
command. Example 2-65 shows the command to configure the qbin 10 on BPX
trunk 2.2 as well as the output of the configuration.
Example 2-65. Configuring Qbin's on BPX Ports for MPLS
bpxa
TRM
cisco:1
BPX 8620
9.2.30
Oct. 8 2004
15:43 MST
(Configured by User)
(EPD Enabled on this qbin)
Qbin State:
Enabled
Discard Threshold:
65536 cells
EPD Threshold:
95%
High CLP Threshold:
100%
EFCI Threshold:
40%
Last Command: cnfqbin 2.2 10 e n 65536 95 100 40
Step 5. Finally, add an LSC shelf as a VSI master using the addshelf command. In
Example 2-66, the first "1" after "VSI" is the VSI controller ID, which must be set
the same on both the BPX 8650 and the LSC. The default controller ID on the LSC
is "1." The second "1" after "VSI" is the partition ID that indicates this is a controller
for partition 1. The "v" stands for a VSI controller.
Page 41
bpxa
TRM
Trunk
Name
2.2
VSI
cisco:1
BPX 8620 9.2.30
Oct. 8 2004 15:48 MST
BPX 8620 Interface Shelf Information
Type
Part Id
Ctrl Id
Control_VC
Alarm
VPI
VCIRange
VSI
1
1
0
40-54
OK
To verify, perform a dsptrks, and the trunk 2.2 appears with VSI on the other end
column to show that a VSI master systems or device is connected on trunk 2.2, as
shown in Example 2-67.
Example 2-67. Verification of VSI
a
TRK
2.1
2.2
2.3
TRM
Type
OC3
OC3
OC3
cisco:1
Current
Clear Clear Clear -
BPX 8620
Line Alarm Status
OK
OK
OK
9.2.30
Oct. 8 2004
15:51 MST
Other End
VSI(VSI)
-
LSC(config)#interface ATM1/0
LSC(config-if)# no ip address
LSC(config-if)# tag-control-protocol vsi
Step 2. Configure the XTagATM interfaces as control links for the trunks 2.1 and 2.3
on the BPX using the extended port command on the LSC, as displayed in
Example 2-69. Note that the numbering of the XTagATM interfaces maps to
the actual trunk ports that they control on the BPX shelf. Therefore, XTagATM
interface 21 controls BPX trunk 2.1, and XTagATM interface 23 controls BPX
trunk 2.3.
Page 42
LSC(config)#interface ATM1/0
LSC(config-if)# no ip address
LSC(config-if)# tag-control-protocol vsi
LSC(config-if)#interface XTagATM21
LSC(config-if)# ip address 10.10.10.2 255.255.255.252
LSC(config-if)# extended-port ATM1/0 bpx 2.1
LSC(config-if)# mpls ip
LSC(config-if)#interface XTagATM23
LSC(config-if)# ip address 10.10.10.6 255.255.255.252
LSC(config-if)# extended-port ATM1/0 bpx 2.3
LSC(config-if)# mpls ip
Step 3. Configure OSPF as the IGP on the LSC, and include all interfaces for OSPF
routing. See Example 2-70.
Example 2-70. Configure IGP (OSPF) on LSC
Step 4. Verify the operation of the VSI control interfaces using the show controllers
vsi status command on the LSC. See Example 2-71.
Example 2-71. Verify VSI Controller Status
IF Status
up
n/a
up
IFC State
ACTIVE
ACTIVE
ACTIVE
Physical Descriptor
0.2.1.0
0.2.2.0
0.2.3.0
Page 43
ELSR1(config-subif)# mpls ip
ELSR1(config)#router ospf 100
ELSR1(config-router)# router-id 10.10.10.101
ELSR1(config-router)# network 10.10.10.0 0.0.0.255 area 0
_____________________________________________________________________
ELSR2(config)#interface ATM1/0
ELSR2(config-if)# no ip address
ELSR2(config-if)#interface ATM1/0.1 mpls
ELSR2(config-subif)# ip address 10.10.10.5 255.255.255.252
ELSR2(config-subif)# mpls atm vpi 240-255
ELSR2(config-subif)# mpls ip
ELSR2(config-subif)#router ospf 100
ELSR2(config-router)# network 10.10.10.0 0.0.0.255 area 0
The key command to be added in Example 2-72 is mpls atm vpi, which defines the VPI
range to be used for the LVCs. This needs to match the configuration of the BPX, as shown
in Example 2-64.
Page 44
Step 2. Verify MPLS label exchange on the Edge LSRs, as shown in Example 2-74.
Example 2-74. MPLS Label Mapping/Exchange Verification
Page 45
Step 4. Confirm connectivity using ping between ELSRs, as shown in Example 2-76.
Example 2-76. Verification of Reachability
LSR1#ping 10.10.10.102
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.10.10.102, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/4
Command Reference
Command
Router(config)#ip cef [distributed]
Description
Enables CEF operation. Use the
distributed keyword for distributed
switching platforms in which line cards
maintain an identical copy of the FIB and
adjacency tables. The line cards perform
the forwarding function between port
adapters, relieving the route processor of
involvement in the switching operation.
Enables CEF on the interface.
Page 46
Command
Router(config-if)#mpls ip
Router(config)#router ospfprocess-id
Router(config-router)#networkip-address wild-card maskareaarea-id
Router(config-router)#no auto-summary
Router(config)#router isisprocess-id
Router(config-router)#netnetwork-entity-title
Router(config)#interfacetype number
Router(config-if)#ip router isisprocess-id
Router(config)#mpls label protocol {ldp | tdp}
Router(config-if)#mpls label protocol {ldp | tdp}
Description
Enables MPLS forwarding on the
interface.
OSPF IGP configuration.