Image requirements:

VIRL: IOSv 15.7

EVE-NG: Cisco vIOS Router vios-15.6

GNS3: vios-adventerprisek9-m.vmdk.SPA.156-2.T

 

Description:

Welcome to my MPLS series labs, this is the first lab, the network infrastructure has been installed and IPv4 has been configured, topological diagrams have drawn, now is the time for the team of the network engineers to begin their work to bring MPLS backbone to life, you have been hired as senior network expert to lead this project. In this lab, the main tasks are to verify IPv4 connectivity between the provider routers inside the MPLS cloud, configure the IS-IS routing protocol as IGP for MPLS functionality, and finally implement and verify MPLS.

 

Topology:

img0 clipped rev 1

img1 clipped rev 1

 

Download Lab:

button virl  button eve ng  button gns

 

Scenario:

An enthusiastic group of tech-savvy entrepreneurs starts the startup company "NISP", which will provide MPLS based services to the large corporations, as a matter of fact, the very first customer nationwide wholesale company has signed the contract and expecting service installation within 2 months. Now that you have been working for about 2 weeks and understand the current needs, proceed to the tasks to complete your assigned job. 

 

Tasks:

1. Access the routers in the topology, get familiar with the configurations, verify that routers able to ping peers on their directly connected networks.

2. Implement the IS-IS routing protocol, the Area-ID is 49.E000, assign router-id by using the value of the last octet of the loopback0 interface, for example, router PE1 will have NET 49.E000.0000.0000.0011.00 and so on. All routers in the domain should be configured as L2 type of the router, adjacency type should be L2 as well, wide metric-type have to be configured to allow the use of MPLS traffic engineering in the future implementation. Links between nodes should be configured as network type point-to-point, enable MD5 authentication for security reason and IS-IS process id will be MPLS.

3. Verify IGP configurations, make sure that each of the routers in the MPLS cloud able to ping IPv4 address of the loopback0 interface of every other router in the topology. Source your ping from the loopback0 interface.

4. Configure MPLS, specify the range of the labels for each router, make the range size of 100 labels on each node, enable MPLS on the appropriate interfaces, then enable MPLS globally, additionally force loopback0 to be LDP router-id permanently. 

5. Verify MPLS implementation, use the traceroute command to display the label in the output. Make sure that each router has local and outgoing labels for each loopback0 interface in the topology.

6. Save configurations and proceed to the next lab.

 

Note: this lab could be the challenge if you complete all the tasks on your own, otherwise proceed to step-by-step instructions.

 

Procedure:

Task1: Determine the proper functionality of the devices in the topology.

 

Step1: Access all nodes' CLI and verify the brief configuration of the interfaces, ping peer devices.

Example for P1 router:

P1#show ip interface brief
Interface IP-Address OK? Method Status Protocol
GigabitEthernet0/0 10.255.2.167 YES TFTP up up
GigabitEthernet0/1 10.0.0.1 YES TFTP up up
GigabitEthernet0/2 10.0.0.5 YES TFTP up up
GigabitEthernet0/3 10.0.0.9 YES TFTP up up
GigabitEthernet0/4 10.0.1.1 YES TFTP up up
GigabitEthernet0/5 10.0.1.5 YES TFTP up up
Loopback0 10.100.0.1 YES TFTP up up
P1#

Learn what are Loopback0 interfaces' IPv4 addresses.

Ping devices on the opposite sides:

P1#ping 10.0.0.2
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.0.0.2, timeout is 2 seconds:
.!!!!
Success rate is 80 percent (4/5), round-trip min/avg/max = 3/3/3 ms

P1#ping 10.0.0.6
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.0.0.6, timeout is 2 seconds:
.!!!!
Success rate is 80 percent (4/5), round-trip min/avg/max = 2/2/3 ms

P1#ping 10.0.0.10
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.0.0.10, timeout is 2 seconds:
.!!!!
Success rate is 80 percent (4/5), round-trip min/avg/max = 2/2/3 ms

P1#ping 10.0.1.6
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.0.1.6, timeout is 2 seconds:
.!!!!
Success rate is 80 percent (4/5), round-trip min/avg/max = 2/2/4 ms

P1#ping 10.0.1.2
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.0.1.2, timeout is 2 seconds:
.!!!!
Success rate is 80 percent (4/5), round-trip min/avg/max = 2/2/3 ms

Step2: Repeat step1 for the rest of the routers, never skip verification it is important for documentation and troubleshooting reason always payoffs in the future. If in the real environment the output of executed commands could serve as baseline documentation.

 

 

Task 2&3: Implement and verify IGP to facilitate MPLS. In this task, the IS-IS routing protocol will be used to propagate the Loopback0 Ipv4 addresses. 

List of Actions:

1. Configure IS-IS with MPLS process-id

2. Configure NET with area-id of 49.E000 and router-id as described in the Task2 overview.

3. Set IS-IS Router Type to L2 only.

4. Set Wide Metric.

5. Enable IS-IS on all interfaces connected to the neighbors.

6. Change IS-IS adjacency type to L2 only on all interfaces connected to the neighbors. 

7. Switch network type to point-to-point on all interfaces connected to the neighbors. 

8. Enable MD5 authentication

9. Verify IS-IS implementation.

10. Verify that all routers in the topology, able to reach IPv4 addresses of loopbacks0 interfaces of all nodes.

 

Steps 1-4:

P1(config)#router isis MPLS

P1(config-router)#net 49.E000.0000.0000.0001.00
P1(config-router)#is-type level-2-only
P1(config-router)#metric-style wide
P1(config-router)#exit

 

Step 5:

P1(config)#interface range g0/1-5,lo0
P1(config-if-range)#ip router isis MPLS
P1(config-if-range)#exit

 

Steps 6-7:

P1(config)#interface range g0/1-5
P1(config-if-range)# isis circuit-type level-2-only
P1(config-if-range)# isis network point-to-point
P1(config-if-range)#exit

 

Step8:

P1(config)#key chain ISIS
P1(config-keychain)#key 1
P1(config-keychain-key)#key-string isis
P1(config-keychain-key)#exit
P1(config-keychain)#exit
P1(config)#

P1(config)#interface range g0/1-5
P1(config-if-range)#isis authentication mode md5 level-2
P1(config-if-range)#isis authentication key-chain ISIS
P1(config-if-range)#exit
P1(config)#

Repeat steps 1 to 8 on every other router in the MPLS cloud then proceed to the last two steps.

 

Step9: Now that IS-IS configurations have been completed you need to verify the proper operation of the IGP.

There are 4 commands that can be used to see if the routing protocol operates as intended.

1. The first is "show isis neighbors" command which shows what IS-IS peers have been installed.

2. Next command verifies the IS-IS configurations, the "show isis protocol".

3. This command displays the detailed output of the IS-IS topology information, useful to see which routes in the topology made into the database." show isis database detail"

4. Lastly, the verification of the IS-IS routing table will prove that all routes have been populated properly."show ip route isis"

 

Example:

P4#show isis neighbors

Tag MPLS:
System Id Type Interface IP Address State Holdtime Circuit Id
P1 L2 Gi0/3 10.0.0.9 UP 23 03
P2 L2 Gi0/2 10.0.0.13 UP 23 02
P3 L2 Gi0/1 10.0.0.21 UP 26 01
PE3 L2 Gi0/4 10.0.4.2 UP 25 02
PE4 L2 Gi0/5 10.0.4.6 UP 29 02
P4#

P4#show isis protocol

Tag MPLS:
IS-IS Router: MPLS
System Id: 0000.0000.0004.00 IS-Type: level-2
Manual area address(es):
49.e000
Routing for area address(es):
49.e000
Interfaces supported by IS-IS:
Loopback0 - IP
GigabitEthernet0/5 - IP
GigabitEthernet0/4 - IP
GigabitEthernet0/3 - IP
GigabitEthernet0/2 - IP
GigabitEthernet0/1 - IP
Redistribute:
static (on by default)
Distance for L2 CLNS routes: 110
RRR level: none
Generate narrow metrics: none
Accept narrow metrics: none
Generate wide metrics: level-1-2
Accept wide metrics: level-1-2
P4#
P4#

P4#show isis database detail

Tag MPLS:
IS-IS Level-2 Link State Database:
LSPID LSP Seq Num LSP Checksum LSP Holdtime/Rcvd ATT/P/OL
P1.00-00 0x0000000A 0x5F12 1078/1199 0/0/0
Area Address: 49.e000
NLPID: 0xCC
Hostname: P1
Metric: 10 IS-Extended P2.00
Metric: 10 IS-Extended P3.00
Metric: 10 IS-Extended P4.00
Metric: 10 IS-Extended PE1.00
Metric: 10 IS-Extended PE2.00
IP Address: 10.100.0.1
Metric: 10 IP 10.0.0.0/30
Metric: 10 IP 10.0.0.4/30
Metric: 10 IP 10.0.0.8/30
Metric: 10 IP 10.0.1.0/30
Metric: 10 IP 10.0.1.4/30
Metric: 10 IP 10.100.0.1/32
P2.00-00 0x00000008 0x87D4 850/1199 0/0/0
Area Address: 49.e000
NLPID: 0xCC
Hostname: P2
Metric: 10 IS-Extended P1.00
Metric: 10 IS-Extended P3.00
Metric: 10 IS-Extended P4.00
Metric: 10 IS-Extended PE1.00
Metric: 10 IS-Extended PE4.00
IP Address: 10.100.0.2
Metric: 10 IP 10.0.0.0/30
Metric: 10 IP 10.0.0.12/30
Metric: 10 IP 10.0.0.16/30
Metric: 10 IP 10.0.2.0/30
Metric: 10 IP 10.0.2.4/30
Metric: 10 IP 10.100.0.2/32

P3.00-00 0x00000008 0x0843 477/1199 0/0/0
Area Address: 49.e000
NLPID: 0xCC
Hostname: P3
Metric: 10 IS-Extended P2.00
Metric: 10 IS-Extended P1.00
Metric: 10 IS-Extended P4.00
Metric: 10 IS-Extended PE2.00
Metric: 10 IS-Extended PE3.00
IP Address: 10.100.0.3
Metric: 10 IP 10.0.0.4/30
Metric: 10 IP 10.0.0.16/30
Metric: 10 IP 10.0.0.20/30
Metric: 10 IP 10.0.3.0/30
Metric: 10 IP 10.0.3.4/30
Metric: 10 IP 10.100.0.3/32
P4.00-00 * 0x00000007 0x1A2B 852/* 0/0/0
Area Address: 49.e000
NLPID: 0xCC
Hostname: P4
Metric: 10 IS-Extended P2.00
Metric: 10 IS-Extended P1.00
Metric: 10 IS-Extended P3.00
Metric: 10 IS-Extended PE3.00
Metric: 10 IS-Extended PE4.00
IP Address: 10.100.0.4
Metric: 10 IP 10.0.0.8/30
Metric: 10 IP 10.0.0.12/30
Metric: 10 IP 10.0.0.20/30
Metric: 10 IP 10.0.4.0/30
Metric: 10 IP 10.0.4.4/30
Metric: 10 IP 10.100.0.4/32
PE1.00-00 0x00000005 0x1307 736/1198 0/0/0
Area Address: 49.e000
NLPID: 0xCC
Hostname: PE1
Metric: 10 IS-Extended P2.00
Metric: 10 IS-Extended P1.00
IP Address: 10.100.0.11
Metric: 10 IP 10.0.1.0/30
Metric: 10 IP 10.0.2.0/30
Metric: 10 IP 10.100.0.11/32

PE2.00-00 0x00000005 0xEA21 884/1198 0/0/0
Area Address: 49.e000
NLPID: 0xCC
Hostname: PE2
Metric: 10 IS-Extended P3.00
Metric: 10 IS-Extended P1.00
IP Address: 10.100.0.12
Metric: 10 IP 10.0.1.4/30
Metric: 10 IP 10.0.3.4/30
Metric: 10 IP 10.100.0.12/32
PE3.00-00 0x00000004 0x9674 482/1199 0/0/0
Area Address: 49.e000
NLPID: 0xCC
Hostname: PE3
Metric: 10 IS-Extended P3.00
Metric: 10 IS-Extended P4.00
IP Address: 10.100.0.13
Metric: 10 IP 10.0.3.0/30
Metric: 10 IP 10.0.4.0/30
Metric: 10 IP 10.100.0.13/32
PE4.00-00 0x00000004 0xC43C 855/1199 0/0/0
Area Address: 49.e000
NLPID: 0xCC
Hostname: PE4
Metric: 10 IS-Extended P2.00
Metric: 10 IS-Extended P4.00
IP Address: 10.100.0.14
Metric: 10 IP 10.0.2.4/30
Metric: 10 IP 10.0.4.4/30
Metric: 10 IP 10.100.0.14/32

P4#show ip route isis
Codes: L - local, C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2
i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
ia - IS-IS inter area, * - candidate default, U - per-user static route
o - ODR, P - periodic downloaded static route, H - NHRP, l - LISP
a - application route
+ - replicated route, % - next hop override, p - overrides from PfR

Gateway of last resort is not set

10.0.0.0/8 is variably subnetted, 27 subnets, 2 masks
i L2 10.0.0.0/30 [115/20] via 10.0.0.13, 00:31:30, GigabitEthernet0/2
[115/20] via 10.0.0.9, 00:31:30, GigabitEthernet0/3
i L2 10.0.0.4/30 [115/20] via 10.0.0.21, 00:31:30, GigabitEthernet0/1
[115/20] via 10.0.0.9, 00:31:30, GigabitEthernet0/3
i L2 10.0.0.16/30 [115/20] via 10.0.0.21, 00:31:30, GigabitEthernet0/1
[115/20] via 10.0.0.13, 00:31:30, GigabitEthernet0/2
i L2 10.0.1.0/30 [115/20] via 10.0.0.9, 00:31:30, GigabitEthernet0/3
i L2 10.0.1.4/30 [115/20] via 10.0.0.9, 00:31:30, GigabitEthernet0/3
i L2 10.0.2.0/30 [115/20] via 10.0.0.13, 00:31:30, GigabitEthernet0/2
i L2 10.0.2.4/30 [115/20] via 10.0.4.6, 00:07:08, GigabitEthernet0/5
[115/20] via 10.0.0.13, 00:07:08, GigabitEthernet0/2
i L2 10.0.3.0/30 [115/20] via 10.0.4.2, 00:13:21, GigabitEthernet0/4
[115/20] via 10.0.0.21, 00:13:21, GigabitEthernet0/1
i L2 10.0.3.4/30 [115/20] via 10.0.0.21, 00:31:30, GigabitEthernet0/1
i L2 10.100.0.1/32 [115/20] via 10.0.0.9, 00:31:30, GigabitEthernet0/3
i L2 10.100.0.2/32 [115/20] via 10.0.0.13, 00:31:30, GigabitEthernet0/2
i L2 10.100.0.3/32 [115/20] via 10.0.0.21, 00:31:30, GigabitEthernet0/1
i L2 10.100.0.11/32 [115/30] via 10.0.0.13, 00:24:07, GigabitEthernet0/2
[115/30] via 10.0.0.9, 00:24:07, GigabitEthernet0/3
i L2 10.100.0.12/32 [115/30] via 10.0.0.21, 00:18:09, GigabitEthernet0/1
[115/30] via 10.0.0.9, 00:18:09, GigabitEthernet0/3
i L2 10.100.0.13/32 [115/20] via 10.0.4.2, 00:13:21, GigabitEthernet0/4
i L2 10.100.0.14/32 [115/20] via 10.0.4.6, 00:07:08, GigabitEthernet0/5
P4#

Step10: Finally to make sure that all routers in the topology, able to communicate with every loopback0 interface on every other router use the ping command to see the proper operation.

PE1#ping 10.100.0.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.100.0.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 2/2/3 ms

PE1#ping 10.100.0.2
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.100.0.2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 2/2/3 ms

PE1#ping 10.100.0.3
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.100.0.3, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 4/4/5 ms

PE1#ping 10.100.0.4
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.100.0.4, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 3/3/5 ms

PE1#ping 10.100.0.11
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.100.0.11, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/1 ms

PE1#ping 10.100.0.12
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.100.0.12, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 2/4/6 ms

PE1#ping 10.100.0.13
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.100.0.13, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 4/6/12 ms

PE1#ping 10.100.0.14
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.100.0.14, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 3/4/5 ms

 

Task 4: Configuring MPLS.

 

Step1: Specify the label range. Make sure to use different ranges for every other router.

P1(config)#mpls label range 100 199

Suggested MPLS Label ranges:

Node  Range
 P1 100-199
 P2  200-299
 P3  300-399
 P4  400-499
 PE1  1100-1199
 PE2  1200-1299
PE3 1300-1399
 PE4  1400-1499

 

 

Step2: Enable MPLS on the interfaces connected to the peers.

P1(config)#interface range g0/1-5
P1(config-if-range)#mpls ip

 

Step3: Enable MPLS globally.

P1(config)#mpls ip

 

Step4: Make the loopback0 interface permanently LDP Router-id.

P1(config)#mpls ldp router-id loopback 0 force

 

Step5: Repeat steps 1 to 4 on every other router in the topology.

 

Step6: Verify LDP neighborship. Check this on every other node in the topology.

P1#show mpls ldp neighbor
Peer LDP Ident: 10.100.0.2:0; Local LDP Ident 10.100.0.1:0
TCP connection: 10.100.0.2.59343 - 10.100.0.1.646
State: Oper; Msgs sent/rcvd: 45/46; Downstream
Up time: 00:17:53
LDP discovery sources:
GigabitEthernet0/1, Src IP addr: 10.0.0.2
Addresses bound to peer LDP Ident:
10.0.0.2 10.0.0.13 10.0.0.17 10.0.2.1
10.0.2.5 10.100.0.2

Peer LDP Ident: 10.100.0.3:0; Local LDP Ident 10.100.0.1:0
TCP connection: 10.100.0.3.41940 - 10.100.0.1.646
State: Oper; Msgs sent/rcvd: 42/42; Downstream
Up time: 00:15:35
LDP discovery sources:
GigabitEthernet0/2, Src IP addr: 10.0.0.6
Addresses bound to peer LDP Ident:
10.0.0.21 10.0.0.6 10.0.0.18 10.0.3.1
10.0.3.5 10.100.0.3

Peer LDP Ident: 10.100.0.4:0; Local LDP Ident 10.100.0.1:0
TCP connection: 10.100.0.4.33652 - 10.100.0.1.646
State: Oper; Msgs sent/rcvd: 41/42; Downstream
Up time: 00:14:33
LDP discovery sources:
GigabitEthernet0/3, Src IP addr: 10.0.0.10
Addresses bound to peer LDP Ident:
10.0.0.22 10.0.0.14 10.0.0.10 10.0.4.1
10.0.4.5 10.100.0.4

Peer LDP Ident: 10.100.0.11:0; Local LDP Ident 10.100.0.1:0
TCP connection: 10.100.0.11.22825 - 10.100.0.1.646
State: Oper; Msgs sent/rcvd: 40/39; Downstream
Up time: 00:13:24
LDP discovery sources:
GigabitEthernet0/4, Src IP addr: 10.0.1.2
Addresses bound to peer LDP Ident:
10.0.1.2 10.0.2.2 10.100.0.11

Peer LDP Ident: 10.100.0.12:0; Local LDP Ident 10.100.0.1:0
TCP connection: 10.100.0.12.60111 - 10.100.0.1.646
State: Oper; Msgs sent/rcvd: 38/38; Downstream
Up time: 00:11:24
LDP discovery sources:
GigabitEthernet0/5, Src IP addr: 10.0.1.6
Addresses bound to peer LDP Ident:
10.0.1.6 10.0.3.6 10.100.0.12

For every P router there should be 5 peers, and for PE routers should be 2 peers.

 

 

Task 5: Verify MPLS implementation, use the traceroute command to display the label in the output. Make sure that each router has local and outgoing labels for each loopback0 interface in the topology.

Step1: Verify MPLS forwarding table:

PE1#show mpls forwarding-table
Local Outgoing Prefix Bytes Label Outgoing Next Hop
Label Label or Tunnel Id Switched interface
1119 129 10.100.0.12/32 0 Gi0/1 10.0.1.1
1120 Pop Label 10.0.1.4/30 0 Gi0/1 10.0.1.1
1121 Pop Label 10.0.0.8/30 0 Gi0/1 10.0.1.1
1122 Pop Label 10.0.0.4/30 0 Gi0/1 10.0.1.1
1123 Pop Label 10.100.0.1/32 0 Gi0/1 10.0.1.1
1124 231 10.100.0.14/32 0 Gi0/2 10.0.2.1
1125 Pop Label 10.0.2.4/30 0 Gi0/2 10.0.2.1
1126 Pop Label 10.0.0.16/30 0 Gi0/2 10.0.2.1
1127 Pop Label 10.0.0.12/30 0 Gi0/2 10.0.2.1
1128 Pop Label 10.100.0.2/32 0 Gi0/2 10.0.2.1
1129 130 10.100.0.13/32 0 Gi0/1 10.0.1.1
230 10.100.0.13/32 0 Gi0/2 10.0.2.1
1130 122 10.0.3.4/30 0 Gi0/1 10.0.1.1
222 10.0.3.4/30 0 Gi0/2 10.0.2.1
1131 121 10.0.3.0/30 0 Gi0/1 10.0.1.1
221 10.0.3.0/30 0 Gi0/2 10.0.2.1
1132 124 10.0.4.4/30 0 Gi0/1 10.0.1.1
224 10.0.4.4/30 0 Gi0/2 10.0.2.1
1133 123 10.0.4.0/30 0 Gi0/1 10.0.1.1
223 10.0.4.0/30 0 Gi0/2 10.0.2.1
Local Outgoing Prefix Bytes Label Outgoing Next Hop
Label Label or Tunnel Id Switched interface
1134 118 10.0.0.20/30 0 Gi0/1 10.0.1.1
218 10.0.0.20/30 0 Gi0/2 10.0.2.1
1135 Pop Label 10.0.0.0/30 0 Gi0/1 10.0.1.1
Pop Label 10.0.0.0/30 0 Gi0/2 10.0.2.1
1136 126 10.100.0.3/32 0 Gi0/1 10.0.1.1
226 10.100.0.3/32 0 Gi0/2 10.0.2.1
1137 127 10.100.0.4/32 0 Gi0/1 10.0.1.1
227 10.100.0.4/32 0 Gi0/2 10.0.2.1
PE1#
PE1#

This table shows you the local and ougoing labels for all prefixes IS-IS advertises within the domain, additionally you can see what is the outgoing interface and the next-hop address to each the given prefix. 

 

Step2: From PE1 router traceroute the IP addresses of loopback0 interfaces for the routers PE2, PE3, and PE4.

You can use regular traceroute command with a probe set to 1 it will show you the path and outgoing labels at each hop:

PE1#traceroute 10.100.0.13 probe 1
Type escape sequence to abort.
Tracing the route to 10.100.0.13
VRF info: (vrf in name/id, vrf out name/id)
1 10.0.2.1 [MPLS: Label 230 Exp 0] 7 msec
2 10.0.0.6 [MPLS: Label 330 Exp 0] 7 msec
3 10.0.3.2 5 msec
PE1#

At this example traceroute is used to reach PE3, the first hop is P2 then P3 then it is PE3 but the label is missing due to the PHP operation.

 

Also, MPLS specific traceroute command useful when you need to know more information about the path to the destination:

PE1#traceroute mpls ipv4 10.100.0.13/32 source 10.100.0.11
Tracing MPLS Label Switched Path to 10.100.0.13/32, timeout is 2 seconds

Codes: '!' - success, 'Q' - request not sent, '.' - timeout,
'L' - labeled output interface, 'B' - unlabeled output interface,
'D' - DS Map mismatch, 'F' - no FEC mapping, 'f' - FEC mismatch,
'M' - malformed request, 'm' - unsupported tlvs, 'N' - no label entry,
'P' - no rx intf label prot, 'p' - premature termination of LSP,
'R' - transit router, 'I' - unknown upstream index,
'X' - unknown return code, 'x' - return code 0

Type escape sequence to abort.
0 10.0.1.2 MRU 1500 [Labels: 130 Exp: 0]
L 1 10.0.1.1 MRU 1500 [Labels: 330 Exp: 0] 6 ms
L 2 10.0.0.6 MRU 1504 [Labels: implicit-null Exp: 0] 9 ms
! 3 10.0.3.2 6 ms
PE1#

 

Task 6: Save configurations and proceed to the next lab.

 

Summary:

Alright, this lab comes to the end, now that the backbone MPLS network is configured, the team of network engineers is ready to move for the next stage of the MPLS deployment. In the next lab, MP-BGP VPNv4 address-family will be configured then for the first time the engineers will test the L3 MPLS VPN service.