Alcatel-Lucent MPLS Lab Guide v1-1

Alcatel Multi-Protocol Label Switching (MPLS)

Lab Guide

Version 1.1

December 19, 2007

Software Version: 7750 SR OS 4.0 R5

August 2006

Alcatel-Lucent

Confidential

for

internal

use

only

--

Do

Not

Distribute

Alcatel-Lucent

Confidential

for

internal

use

only

--

Do

Not

Distribute

Table of contents

Lab 1

Lab Infrastructure and IGP Configuration ...6

Section 1.1 – Remote Lab Connection...7

Section 1.2 – Lab Infrastructure Verification and IGP Configuration...7

Lab 1 Review Questions ...8

Lab 2

Static LSP Configuration ...9

Lab 2 Review Questions ...12

Lab 3

Implementing Provider Core LDP...13

Section 3.1 – LDP Session Establishment ...15

Section 3.2 – Configuring and Verifying the Provider Core for LDP ...17

Section 3.3 – Enabling ECMP LDP...20

Section 3.4 – Applying Export Policy for Label Distribution ...23

Section 3.5 – Configuring Targeted LDP ...25

Lab 3 Review Questions ...27

Lab 4

Enabling Provider Core OSPF-TE and MPLS...28

Lab 4 Review Questions ...33

Lab 5

CSPF Based LSPs and LSP Establishment ...34

Section 5.1– RSVP-TE LSP Establishment ...35

Section 5.2– Configuring CSPF Based LSPs...37

Lab 5 Review Questions ...44

Lab 6

Enabling Primary and Secondary LSP Tunnels...45

Lab 6 Review Questions ...50

Lab 7

FRR One-to-One Protection ...51

Lab 7 Review Questions ...56

Lab 8

FRR Facility Backup Protection ...57

Lab 8 Review Questions ...64

Lab Solutions and Answers...65

Lab 1 Solution – Lab Infrastructure and IGP Configuration ...65

Lab 1 - Review Question Answers...65

Lab 2 Solution – Configuring a Static LSP...65

Lab 2 - Review Question Answers...66

Lab 3 Solution – LDP Implementation ...66

Lab 3 Section 3.1 Solution – LDP Session Establishment ...66

Lab 3 Section 3.1 - Answers to Exercise Questions ...68

Lab 3 Section 3.2 – Configuring and Verifying the Provider Core for LDP ...68

Lab 3 Section 3.2 - Answers to Exercise Questions ...69

Alcatel-Lucent

Confidential

for

internal

use

only

--

Do

Not

Distribute

Lab 4 Solution – Configuring the Provider Core for MPLS...73

Lab 4 - Answers to Exercise Questions ...73

Lab 4 - Answers to Review Questions...74

Lab 5 Solution – CSPF Based LSPs and LSP Establishment ...75

Lab 5 Section 5.1 - Answers to Exercise Questions ...76

Lab 5 Section 5.2 - Answers to Exercise Questions ...77

Lab 5 - Answers to Review Questions...77

Lab 6 Solution – Enabling Primary and Secondary LSP Tunnels ...78

Lab 6 - Answers to Exercise Questions ...78

Lab 6 - Answers to Review Questions...79

Lab 7 Solution – FRR One-to-One Link Protection ...80

Lab 7 - Answers to Exercise Questions ...80

Lab 7 - Answers to Review Questions...81

Lab 8 Solution – FRR Facility Bypass...81

Lab 8 - Answers to Exercise Questions ...82

Lab 8 - Answers to Review Questions...82

Alcatel-Lucent

Confidential

for

internal

use

only

--

Do

Not

Distribute

List of Figures

Figure 1-1 Lab Topology Overview... 6

Figure 2-1 Static LSP Configuration... 9

Figure 3-1 Implementing Provider Core LDP... 13

Figure 4-1: Enabling Provider Core MPLS ... 28

Figure 5-1: CSPF Based LSPs ... 34

Figure 6-1: Enabling Primary and Secondary LSP Tunnels... 45

Figure 7-1: Enabling FRR One-to-One Protection ... 51

Figure 8-1: Enabling FRR Facility Bypass ... 57

List of Tables

Table 1-1 Lab 1 Configuration and Verification Commands ... 7

Table 1-2 Remote Lab Addressing... 7

Table 1-3 Interface IP Addressing... 8

Table 2-1 Lab 2 Configuration and Verification Commands ... 10

Table 2-2 Labels for Static LSPs ... 10

Table 3-1 Lab 3 Configuration and Verification Commands ... 14

Table 4-1 Lab 4 Configuration and Verification Commands ... 29

Table 5-1: Lab 5 Configuration and Verification Commands... 35

Table 6-1: Lab 6 Configuration and Verification Commands... 46

Table 7-1: Lab 7 Configuration and Verification Commands... 52

Table 8-1: Lab 8 Configuration and Verification Commands... 58

Alcatel-Lucent

Confidential

for

internal

use

only

--

Do

Not

Distribute

Lab 1

Lab Infrastructure and IGP Configuration

Objective:

The purpose of this lab is to verify the operation and physical connectivity of the routers and to configure and verify

the IGP routing protocol. The lab topology is shown in Figure 1-1. Additional connection details will be provided

by the instructor if required.

Figure 1-1 Lab Topology Overview

The Alcatel Multi-protocol Label Switching (MPLS) course labs use 7750 Service Routers for the core

infrastructure as shown in Figure 1-1. The 7750 SR Edge (PE) routers and the 7750 SR ‘Core’ (P) routers form the

Service Provider Core backbone.

Syntax:

The configuration and verification commands required for this Lab are provided in Table 1-1. Each command may

have additional parameters possible. Use the ‘?’ character for help and to explore all command line options. Other

commands may also be used, including those found in previous courses.

Pod 1

Pod 2

Pod 3

Pod 4

Service Provider Core

IGP Routing

Alcatel-Lucent

Confidential

for

internal

use

only

--

Do

Not

Distribute

Lab 1 Command list

#telnet <management ip address> #configure router ospf area <area #>

#configure router ospf area <area #> interface #show port

#show router interface #show router ospf status #show router ospf interface #show router ospf neighbor #show router route-table #ping <ip-address> #traceroute <ip-route>

Table 1-1 Lab 1 Configuration and Verification Commands

Section 1.1 – Remote Lab Connection

Exercise:

1. Establish a remote connection to the routers, using the addresses from Table 1-2. The username and

password for all routers is ‘admin’. If you are unable to connect or login to any of the routers, notify your

instructor. Please do not change the admin password unless instructed to do so.

2. Change the bof to use a new configuration file and then save the configuration to this file. The default is set

up as read-only, so you will be unable to save to this file. If you have not worked on the 7750 before and

need assistance in this step, ask your instructor for help.

Pod Number

Management Address

Pod 1 - Core1 (P1) Edge1 (PE1) Pod 2 - Core2 (P2) Edge2 (PE2) Pod 3 - Core3 (P3) Edge3 (PE3) Pod 4 - Core4 (P4)

Alcatel-Lucent

Confidential

for

internal

use

only

--

Do

Not

Distribute

2. Configure the cards, MDAs and physical ports, using the appropriate show and config commands. If you

are not familiar with this process, ask your instructor for assistance.

3. Configure the IP addresses of all interfaces as shown in Table 1-3 using the appropriate commands. In

order to make addressing consistent, the last octet of a router’s IP address will always be the same, using

the last octet of the management address from Table 1-2.

4. Enable OSPF routing on your PE and P routers. Use one area (area 0).

5. Enable OSPF on all interfaces.

6. Verify the configuration and operation of the IGP. The routing table of your routers should have all the

domain networks listed. Refer to Table 1-3 for a list of subnet addresses. If 4 pods are in use, the networks

should include the following:

a. 10 Ethernet segments

b. 8 system addresses

7. Check with your instructor if you are not sure of the number of networks that should be visible.

8. Make note of the configured addresses or other parameters on the diagram if required.

9. All destinations should be reachable. Verify the routing topology using available tools such as ping or

traceroute.

Parameter

Value

Pod Number x = 1, 2, 3, or 4 (circle your Pod number) 7750 SR router you are configuring P___ or PE___

y = ______ (Use as the last octet of all addresses) Last octet of management address from Table 1-2

System IP address 10.10.10.y/32 For the last octet of the interface address use the

last octet of the router’s management address from Table 1-2

Core 1 to Edge 1 subnet 10.16.1.y/24 Core 2 to Edge 2 subnet 10.32.1.y/24 Core 3 to Edge 3 subnet 10.48.1.y/24 Core 4 to Edge 4 subnet 10.64.1.y/24 Core 1 to Core 2 subnet 10.1.2.y/24 Core 1 to Core 3 subnet 10.1.3.y/24 Core 1 to Core 4 subnet 10.1.4.y/24 Core 2 to Core 3 subnet 10.2.3.y/24 Core 2 to Core 4 subnet 10.2.4.y/24 Core 3 to Core 4 subnet 10.3.4.y/24

Table 1-3 Interface IP Addressing

Lab 1 Review Questions

1. What is the routed path between your PE router and all other PE routers under normal circumstances?

Verify with a traceroute between PE devices. Are other paths possible?

2. What is the next-hop to reach PE1 from your P router?

3. What is the value of the OSPF metric of each link?

Alcatel-Lucent

Confidential

for

internal

use

only

--

Do

Not

Distribute

Lab 2

Static LSP Configuration

Objective:

The purpose of this lab is to configure a static LSP from your PE router across the provider core to another PE router

as shown in Figure 2-1, and to understand the label operations performed on packets that would be routed along this

LSP.

Figure 2-1 Static LSP Configuration

Syntax:

The configuration and verification commands required for this Lab are provided in Table 2-1. Refer to the student

guide for additional command details. Each command may have additional parameters possible. Use the ‘?’

character for help and to explore all command line options. Other commands may also be used, including those

Pod 1

Pod 2

Pod 3

Pod 4

Service Provider Network

Static LSP

Alcatel-Lucent

Confidential

for

internal

use

only

--

Do

Not

Distribute

Lab 2 Command List

#configure router mpls

#configure router mpls interface <interface-name>

#configure router mpls static-lsp <lsp-name> to <destination-ip-address> #configure router mpls static-lsp <lsp-name> push <label> nexthop <ip-address>

#configure router mpls interface <interface-name> label-map <in-label > swap <out-label> nexthop <ip-address> #configure router mpls interface <interface-name> label-map <in-label > pop

#info (from all contexts) #exit [all] (from all contexts) #admin save

#show router mpls label <label range> in-use

#show router mpls static-lsp <lsp-name> [transit | terminate] #show router mpls status

Table 2-1 Lab 2 Configuration and Verification Commands

Exercise:

Configure a Static LSP as shown in Figure 2-1across the provider core by completing the following steps. Use the

labels provided in Table 2-2.

NOTE: Recall that an LSP is unidirectional, thus you will configure an LSP from your PE router to your neighbor’s

PE router while your neighbor will configure an LSP from their PE router to your PE. You will have to work with

your neighboring Pod as they will be responsible for configuring the portion of your LSP that traverses their P and

PE routers, while you will be responsible for configuring the portion of their LSP that traverses your P and PE

routers.

1. Configure a static LSP originating on your PE router and going to your adjacent P router.

2. Configure the cross-connection for the static LSP on your P router going to your neighbor’s P router. The

outgoing interface must be added to MPLS even though no configuration is required.

3. Your neighbor will configure the remainder of your LSP on their P and PE routers.

4. Configure the remainder of your neighbor’s LSP. On your P router configure the cross-connection for the static

LSP coming from your neighbor’s P router and going to your PE router.

5. On your PE router configure the termination of your neighbor’s LSP coming from your P router.

Pods

Edge to Core Label

Core to Core Label

Core to Edge Label

Pod 1 and Pod 3 999 998 997 Pod 2 and Pod 4 597 598 599

Table 2-2 Labels for Static LSPs

6. On your PE router verify that the static LSP originating on the router is configured and active. Also verify that

the LSP (from your neighbor’s PE router) terminating on your PE router is configured and active. Examples of

the output you should see are shown below.

Alcatel-Lucent

Confidential

for

internal

use

only

--

Do

Not

Distribute

7. On your P router verify that the transit LSPs going to your neighbor’s PE and coming from your neighbor’s PE

are configured and active. An example is shown below.

8. On your PE router verify the labels in use by the configured static LSPs. An example is shown below.

A:P1# show router mpls static-lsp transit

=============================================================================== MPLS Static LSPs (Transit)

=============================================================================== In Label In I/F Out Label Out I/F Next Hop Adm Opr ---999 1/1/1 998 1/1/2 10.1.2.2 Up Up 598 1/1/2 597 1/1/1 10.16.1.2 Up Up ---LSPs : 2 ===============================================================================

A:PE1# show router mpls label 32 131071 in-use

================================================================ MPLS Labels from 32 to 131071 (In-use)

================================================================ A:PE1# show router mpls static-lsp terminate

=============================================================================== MPLS Static LSPs (Terminate)

=============================================================================== In Label In I/F Out Label Out I/F Next Hop Adm Opr ---599 1/2/1 n/a n/a n/a Up Up ---LSPs : 1

=============================================================================== A:PE1# show router mpls static-lsp

=============================================================================== MPLS Static LSPs (Originating)

=============================================================================== LSP Name To Next Hop Out Label Out I/F Adm Opr ---PE1 to PE2 10.10.10.242 10.16.1.221 999 1/2/1 Up Up ---LSPs : 1 =============================================================================== A:PE1#

Alcatel-Lucent

Confidential

for

internal

use

only

--

Do

Not

Distribute

10. On your PE and P routers shutdown and disable MPLS support. Use the ‘show router status’ command to verify

that MPLS is not supported on your P and PE routers.

Lab 2 Review Questions

1. How many static LSPs are required between 2 routers to create an end to end path?

2. Which range of label values is reserved for static LSP configurations?

3. How many originating, transiting and terminating LSPs should you see on your PE router? What about on

the P router?

4. What is the value of the label that appears on the packet coming in on your P router from your neighbor’s P

router?

5. What is the value of the label that is POPed by your PE router?

A:P1# show router mpls status

=============================================================================== MPLS Status

=============================================================================== Admin Status : Up Oper Status : Up FR Object : Enabled Resignal Timer : Disabled

LSP Counts Originate Transit Terminate

---Static LSPs 0 2 0

Dynamic LSPs 0 0 0 Detour LSPs 0 0 0 =============================================================================== A:PE1# show router mpls status

=============================================================================== MPLS Status

=============================================================================== Admin Status : Up Oper Status : Up FR Object : Enabled Resignal Timer : Disabled

LSP Counts Originate Transit Terminate ---Static LSPs 1 0 1 Dynamic LSPs 0 0 0 Detour LSPs 0 0 0 =============================================================================== A:PE1#

Alcatel-Lucent

Confidential

for

internal

use

only

--

Do

Not

Distribute

Lab 3

Implementing Provider Core LDP

Objective:

This lab has the following objectives:

1. To view the packet exchanged between two routers during the establishment of the LDP session.

2. To enable the provider core for LDP support, enabling and verifying LDP on all required interfaces.

3. To identify the labels generated and distributed for each FEC by default and hence to map out the labels

used for an LSP associated with a given FEC. To generate labels for other prefixes using Export Policies.

4. To enable LDP ECMP and view the impact on the LFIB.

5. To configure targeted LDP session between remote routers.

Figure 3-1 Implementing Provider Core LDP

Pod 1

Pod 2

Pod 3

Pod 4

Service Provider Network

LDP Enabled Core

Alcatel-Lucent

Confidential

for

internal

use

only

--

Do

Not

Distribute

Lab 3 Command list

#configure router ldp interface-parameters interface <interface-name> #configure router ldp targeted-session [no] disable-targeted-session #configure router ldp targeted-session peer <peer-ip-address>

#configure router ldp peer-parameters peer <peer-address> authentication-key <key> #configure router ldp export <export-policy-name>

#configure>router>policy-options# begin

#configure>router>policy-options# policy-statement <policy-name> #configure>router>policy-options>policy-statement# entry <entry index> #configure>router>policy-options>policy-statement>entry# action accept #configure>router>policy-options# commit

#clear router ldp session <neighbor-ip-address> #show router status

#show router route-table #show router ldp status #show router ldp parameters #show router ldp discovery [detail] #show router ldp interface #show router ldp session #show router ldp bindings #show router ldp bindings active #show router ldp tunnel-table #oam lsp-ping prefix <ip-address> #oam lsp-trace prefix <ip-address>

#debug router ldp interface <interface name> packet hello detail

#debug router ldp peer <peer address> packet [hello | init | keepalive | label] detail #debug router ldp peer <peer address> event [bindings | message] detail

info (from all contexts) exit [all] (from all contexts) #admin save <file-name>

Table 3-1 Lab 3 Configuration and Verification Commands

Alcatel-Lucent

Confidential

for

internal

use

only

--

Do

Not

Distribute

Section 3.1 – LDP Session Establishment

1. On your PE and P routers configure a log to capture the LDP packets exchanged during session

establishment using debug-trace, as follows (this log-id configuration will send the results of the packet

capture to the session):

2. Enable event debug on your PE router’s LDP session to your peer P router, as well as the interface, and

vice-versa, to capture event messages and bindings exchanged between the routers during LDP session

establishment.

3. On your P router enable LDP on the interface to your PE router and on your PE router enable LDP on the

interface to your P router. Observe the LDP messages exchanged between the routers to establish the LDP

session. The output is shown in the solutions section at the end of the lab guide.

a. After the hello adjacency is established what must happen before the LDP session can be

established?

b. What state occurs after the Active router sends the Initialization message?

c. When can label advertisement start occurring?

4. Disable debug on your PE and P routers.

5. Enable packet debug on your PE router’s LDP session to your peer P router, and vice-versa, to capture

Hello, Initialization, Keep Alive and Label Advertisement packets.

Note: Enabling debug on the interface only captures the interface Hellos while enabling debug on peer captures the

targeted Hello, Initialization, Keep Alive and Label Advertisement messages. Use the ‘detail’ keyword to obtain

more details for each packet.

6. On your P router shutdown the LDP interface to your PE router.

a. What LDP message is sent to the PE router?

7. On your P router re-enable the LDP interface to your PE router. Observe the LDP messages exchanged

between the routers to establish the LDP session. An example is shown below.

a. Which router plays the active role?

8. Disable debug on your PE and P routers.

#--- echo "Log Configuration"

#--- log-id 74 from debug-trace to session exit ---

Alcatel-Lucent

Confidential

for

internal

use

only

--

Do

Not

Distribute

A:P3>debug router ldp peer 10.10.10.243 packet init detail 56 2006/09/19 23:42:53.36 UTC MINOR: DEBUG #2001 - LDP

"LDP: LDP

Recv Initialization packet (msgId = 2) from 10.10.10.243:0

Recv 10.10.10.223:0

Protocol version = 1 Keepalive Timeout = 30 Label Advertisement = downStreamUnsolicited

Loop Detection = Off PathVector Limit = 0 Max Pdu = 4096 "

57 2006/09/19 23:42:53.36 UTC MINOR: DEBUG #2001 - LDP

"LDP: LDP

Send Initialization packet (msgId 2) to 10.10.10.243:0

Send 10.10.10.243:0

Protocol version = 1 Keepalive Timeout = 30 Label Advertisement = downStreamUnsolicited

Loop Detection = Off PathVector Limit = 0 Max Pdu = 4096 "

58 2006/09/19 23:42:53.36 UTC MINOR: DEBUG #2001 - LDP

"LDP: LDP

Send Keepalive packet (msgId 3) to 10.10.10.243:0

"

59 2006/09/19 23:42:53.37 UTC MINOR: DEBUG #2001 - LDP

"LDP: LDP

Send Address packet (msgId 4) to 10.10.10.243:0

Address Family = 1 Number of addresses = 5 Address 1 = 10.3.4.3 Address 2 = 10.2.3.3 Address 3 = 10.1.3.3 Address 4 = 10.48.1.1 Address 5 = 10.10.10.223 "

60 2006/09/19 23:42:53.37 UTC MINOR: DEBUG #2001 - LDP

"LDP: LDP

Send Label Mapping packet (msgId 5) to 10.10.10.243:0

Label 131071 advertised for the following FECs

Address Prefix Address Family = 1 Prefix = 10.10.10.223/32 "

61 2006/09/19 23:42:53.38 UTC MINOR: DEBUG #2001 - LDP

"LDP: LDP

Recv Address packet (msgId = 4) from 10.10.10.243:0

Address Family = 1 Number of addresses = 2 Address 1 = 10.48.1.2

Address 2 = 10.10.10.243 "

62 2006/09/19 23:42:53.38 UTC MINOR: DEBUG #2001 - LDP

"LDP: LDP

Recv Label Mapping packet (msgId = 5) from 10.10.10.243:0

Label 131071 advertised for the following FECs

Address Prefix Address Family = 1 Prefix = 10.10.10.243/32 "

Alcatel-Lucent

Confidential

for

internal

use

only

--

Do

Not

Distribute

Section 3.2 – Configuring and Verifying the Provider Core for LDP

Exercise:

1. Enable LDP on all the interfaces of your P router to the other P routers. (LDP should have already been

enabled between your P and PE routers from lab 3.1).

2. Verify that the core IGP and LDP processes are up on your PE & P routers and that LDP has been enabled

on all provider core network interfaces. An example of the output is shown below.

a. How many LDP neighbors should each P router have?

b. How many should each PE router have?

3. Verify that the LDP sessions with peer routers are UP. An example of the output is shown below.

a. How many LDP sessions does your P router have?

b. How many sessions does your PE router have?

c. What types of adjacencies are formed? Why?

A:P1# show router ldp session

=============================================================================== LDP Sessions

=============================================================================== Peer LDP Id Adj Type State Mesg Sent Mesg Recv Up Time ---10.10.10.224:0 Link Established 254 255 0d 00:11:24 10.10.10.223:0 Link Established 250 251 0d 00:11:11 10.10.10.222:0 Link Established 257 256 0d 00:11:35 10.10.10.241:0 Link Established 261 260 0d 00:11:01 ---No. of Sessions: 4 =============================================================================== A:P1# show router ldp interface

=============================================================================== LDP Interfaces

=============================================================================== Interface Adm Opr Hello Hold KA KA Transport Factor Time Factor Timeout Address ---P1-P2 Up Up 3 15 3 30 System P1-P3 Up Up 3 15 3 30 System P1-P4 Up Up 3 15 3 30 System P1-PE1 Up Up 3 15 3 30 System ---No. of Interfaces: 4 ===============================================================================

Alcatel-Lucent

Confidential

for

internal

use

only

--

Do

Not

Distribute

5. Verify that the Label Forwarding Information Base (LFIB) of your P and PE routers contains the active

labels used by the router for MPLS forwarding. An example is shown below.

A:P1# show router ldp bindings

=============================================================================== LDP LSR ID: 10.10.10.221

=============================================================================== Legend: U - Label In Use, N - Label Not In Use, W - Label Withdrawn

S - Status Signaled Up, D - Status Signaled Down E - Epipe Service, V - VPLS Service, M - Mirror Service

A - Apipe Service, F - Fpipe Service, I - IES Service, R - VPRN service P - Ipipe Service

=============================================================================== LDP Prefix Bindings

=============================================================================== Prefix Peer IngLbl EgrLbl EgrIntf EgrNextHop ---10.10.10.221/32 10.10.10.222 131071U -- -- -- 10.10.10.221/32 10.10.10.223 131071U -- -- -- 10.10.10.221/32 10.10.10.224 131071U -- -- -- 10.10.10.221/32 10.10.10.241 131071U -- -- -- 10.10.10.222/32 10.10.10.222 -- 131071 1/1/2 10.1.2.2 10.10.10.222/32 10.10.10.223 131070U 131067 -- -- 10.10.10.222/32 10.10.10.224 131070U 131068 -- -- 10.10.10.222/32 10.10.10.241 131070U 131069 -- -- 10.10.10.223/32 10.10.10.222 131067U 131067 -- -- 10.10.10.223/32 10.10.10.223 -- 131071 1/1/4 10.1.3.3 10.10.10.223/32 10.10.10.224 131067U 131067 -- -- 10.10.10.223/32 10.10.10.241 131067U 131068 -- -- 10.10.10.224/32 10.10.10.222 131065U 131065 -- -- 10.10.10.224/32 10.10.10.223 131065U 131065 -- -- 10.10.10.224/32 10.10.10.224 -- 131071 1/1/3 10.1.4.4 10.10.10.224/32 10.10.10.241 131065U 131067 -- -- 10.10.10.241/32 10.10.10.222 131063U 131063 -- -- 10.10.10.241/32 10.10.10.223 131063U 131063 -- -- 10.10.10.241/32 10.10.10.224 131063U 131064 -- -- 10.10.10.241/32 10.10.10.241 -- 131071 1/1/1 10.16.1.2 10.10.10.242/32 10.10.10.222 131068N 131069 1/1/2 10.1.2.2 10.10.10.242/32 10.10.10.223 131068U 131066 -- -- 10.10.10.242/32 10.10.10.224 131068U 131066 -- -- 10.10.10.242/32 10.10.10.241 131068U 131066 -- -- 10.10.10.243/32 10.10.10.222 131066U 131066 -- -- 10.10.10.243/32 10.10.10.223 131066N 131070 1/1/4 10.1.3.3 10.10.10.243/32 10.10.10.224 131066U 131065 -- -- 10.10.10.243/32 10.10.10.241 131066U 131065 -- -- 10.10.10.244/32 10.10.10.222 131064U 131064 -- -- 10.10.10.244/32 10.10.10.223 131064U 131064 -- -- 10.10.10.244/32 10.10.10.224 131064N 131070 1/1/3 10.1.4.4 10.10.10.244/32 10.10.10.241 131064U 131064 -- -- ---No. of Prefix Bindings: 32

=============================================================================== LDP Service Bindings

=============================================================================== Type VCId SvcId SDPId Peer IngLbl EgrLbl LMTU RMTU ---No Matching Entries Found

===============================================================================

Alcatel-Lucent

Confidential

for

internal

use

only

--

Do

Not

Distribute

a. What is the difference in the ‘show router ldp bindings’ when the ‘active’ keyword is used?

Why are there fewer prefix bindings in the LFIB than the FIB?

b. Why does your P router have both a PUSH and SWAP operation for the prefix corresponding to

your PE router?

c. Based on the output of the ‘show router ldp bindings active’ command can you tell the system

address of the router on which the command is executed?

d. Identify all the label mappings corresponding to the LSP extending from your PE router to the PE

router of the diagonally connected Pod. At each router along the path identify the label that is

PUSHed, SWAPed or POPed.

6. Verify the LSPs that are present. An example is shown below.

a. What are the FECs for which the LSPs have been created?

b. What does the metric value represent?

A:PE1# show router tunnel-table protocol ldp

=============================================================================== Tunnel Table (Router: Base)

=============================================================================== Destination Owner Encap TunnelId Pref Nexthop Metric ---A:P1# show router ldp bindings active

=============================================================================== Legend: (S) - Static

=============================================================================== LDP Prefix Bindings (Active)

=============================================================================== Prefix Op IngLbl EgrLbl EgrIntf EgrNextHop ---10.10.10.221/32 Pop 131071 -- -- -- 10.10.10.222/32 Push -- 131071 1/1/2 10.1.2.2 10.10.10.222/32 Swap 131070 131071 1/1/2 10.1.2.2 10.10.10.223/32 Push -- 131071 1/1/4 10.1.3.3 10.10.10.223/32 Swap 131067 131071 1/1/4 10.1.3.3 10.10.10.224/32 Push -- 131071 1/1/3 10.1.4.4 10.10.10.224/32 Swap 131065 131071 1/1/3 10.1.4.4 10.10.10.241/32 Push -- 131071 1/1/1 10.16.1.2 10.10.10.241/32 Swap 131063 131071 1/1/1 10.16.1.2 10.10.10.242/32 Push -- 131069 1/1/2 10.1.2.2 10.10.10.242/32 Swap 131068 131069 1/1/2 10.1.2.2 10.10.10.243/32 Push -- 131070 1/1/4 10.1.3.3 10.10.10.243/32 Swap 131066 131070 1/1/4 10.1.3.3 10.10.10.244/32 Push -- 131070 1/1/3 10.1.4.4 10.10.10.244/32 Swap 131064 131070 1/1/3 10.1.4.4 ---No. of Prefix Bindings: 15

===============================================================================

Alcatel-Lucent

Confidential

for

internal

use

only

--

Do

Not

Distribute

7. On your P router shutdown the interface to your diagonally connected neighbor P router.

8. Verify the Label Information Base (LIB) of your P and PE routers.

a. How has the LIB changed on the P and PE router compared to before the interface shutdown?

9. Verify the Label Forwarding Information Base (LFIB) of your P and PE routers.

a. How has the LFIB changed on the P and PE router compared to before the interface shutdown?

b. What is the LSP path for packets originating on your PE router and destined for your diagonally

connected neighbor Pod’s PE router now?

c. What label does your P router SWAP in for a packet coming in from your PE router destined for

your diagonally connected neighbor Pod’s PE router?

10. Use the oam lsp-trace command to verify the path taken to your diagonal PE router.

Note: Keep the interface from your P router to the diagonally connected P router in the shutdown mode.

Section 3.3 – Enabling ECMP LDP

Exercise:

1. Enable ECMP for 4 equal cost paths.

2. Verify the routing table on your P router. What is the next-hop to reach the PE router in the diagonally

connected neighbor Pod?

3. Verify the Label Information Base (LIB) of your P and PE routers. An example is shown below.

a. Is there any difference on your P and PE with the output of the LIB without ECMP LDP enabled?

b. How many Prefixes bindings should be present in your P and PE router’s LIB? Explain.

Alcatel-Lucent

Confidential

for

internal

use

only

--

Do

Not

Distribute

4. Verify the Label Forwarding Information Base (LFIB) of your P and PE routers. An example is shown

below.

a. Is there any difference on your P and PE routers with the output of the LFIB without ECMP LDP

enabled?

b. How many equal cost LSPs are there from your P router to the PE router in the diagonally

connected neighbor Pod?

A:P1> # show router ldp bindings

=============================================================================== LDP LSR ID: 10.10.10.221

=============================================================================== Legend: U - Label In Use, N - Label Not In Use, W - Label Withdrawn

S - Status Signaled Up, D - Status Signaled Down E - Epipe Service, V - VPLS Service, M - Mirror Service

A - Apipe Service, F - Fpipe Service, I - IES Service, R - VPRN service P - Ipipe Service

=============================================================================== LDP Prefix Bindings

=============================================================================== Prefix Peer IngLbl EgrLbl EgrIntf EgrNextHop ---10.10.10.221/32 10.10.10.222 131071U -- -- -- 10.10.10.221/32 10.10.10.223 131071U -- -- -- 10.10.10.221/32 10.10.10.241 131071U -- -- -- 10.10.10.222/32 10.10.10.222 -- 131071 1/1/2 10.1.2.2 10.10.10.222/32 10.10.10.223 131070U 131067 -- -- 10.10.10.222/32 10.10.10.241 131070U 131069 -- -- 10.10.10.223/32 10.10.10.222 131067U 131067 -- -- 10.10.10.223/32 10.10.10.223 -- 131071 1/1/4 10.1.3.3 10.10.10.223/32 10.10.10.241 131067U 131068 -- -- 10.10.10.224/32 10.10.10.222 131065N 131065 1/1/2 10.1.2.2 10.10.10.224/32 10.10.10.223 131065N 131065 1/1/4 10.1.3.3 10.10.10.224/32 10.10.10.241 131065U 131061 -- -- 10.10.10.241/32 10.10.10.222 131063U 131063 -- -- 10.10.10.241/32 10.10.10.223 131063U 131063 -- -- 10.10.10.241/32 10.10.10.241 -- 131071 1/1/1 10.16.1.2 10.10.10.242/32 10.10.10.222 131068N 131069 1/1/2 10.1.2.2 10.10.10.242/32 10.10.10.223 131068U 131066 -- -- 10.10.10.242/32 10.10.10.241 131068U 131066 -- -- 10.10.10.243/32 10.10.10.222 131066U 131066 -- -- 10.10.10.243/32 10.10.10.223 131066N 131070 1/1/4 10.1.3.3 10.10.10.243/32 10.10.10.241 131066U 131065 -- -- 10.10.10.244/32 10.10.10.222 131064N 131064 1/1/2 10.1.2.2 10.10.10.244/32 10.10.10.223 131064N 131064 1/1/4 10.1.3.3 10.10.10.244/32 10.10.10.241 131064U 131060 -- -- ---No. of Prefix Bindings: 24

==========================================================================

Alcatel-Lucent

Confidential

for

internal

use

only

--

Do

Not

Distribute

5. Verify the number of LSPs present on your P and PE routers. An example is shown below.

a. How many LSPs are there to reach the diagonally connected neighbor Pod’s P and PE routers?

b. How many LSPs are there to reach the other routers?

6. From your P router do a LSP trace to the diagonally connected neighbor P router’s system address. Which

LSP is used?

7. From your P router do a LSP trace to the diagonally connected neighbor PE router system address. Which

LSP is used?

A:P1# show router tunnel-table protocol ldp

=============================================================================== Tunnel Table (Router: Base)

=============================================================================== Destination Owner Encap TunnelId Pref Nexthop Metric ---10.10.10.222/32 ldp MPLS - 9 10.1.2.2 100 10.10.10.223/32 ldp MPLS - 9 10.1.3.3 100 10.10.10.224/32 ldp MPLS - 9 10.1.2.2 200 10.10.10.224/32 ldp MPLS - 9 10.1.3.3 200 10.10.10.241/32 ldp MPLS - 9 10.16.1.2 100 10.10.10.242/32 ldp MPLS - 9 10.1.2.2 200 10.10.10.243/32 ldp MPLS - 9 10.1.3.3 200 10.10.10.244/32 ldp MPLS - 9 10.1.2.2 300 10.10.10.244/32 ldp MPLS - 9 10.1.3.3 300 =============================================================================== A:P1># show router ldp bindings active

=============================================================================== Legend: (S) - Static

=============================================================================== LDP Prefix Bindings (Active)

=============================================================================== Prefix Op IngLbl EgrLbl EgrIntf EgrNextHop ---10.10.10.221/32 Pop 131071 -- -- -- 10.10.10.222/32 Push -- 131071 1/1/2 10.1.2.2 10.10.10.222/32 Swap 131070 131071 1/1/2 10.1.2.2 10.10.10.223/32 Push -- 131071 1/1/4 10.1.3.3 10.10.10.223/32 Swap 131067 131071 1/1/4 10.1.3.3 10.10.10.224/32 Push -- 131065 1/1/2 10.1.2.2 10.10.10.224/32 Swap 131065 131065 1/1/2 10.1.2.2 10.10.10.224/32 Push -- 131065 1/1/4 10.1.3.3 10.10.10.224/32 Swap 131065 131065 1/1/4 10.1.3.3 10.10.10.241/32 Push -- 131071 1/1/1 10.16.1.2 10.10.10.241/32 Swap 131063 131071 1/1/1 10.16.1.2 10.10.10.242/32 Push -- 131069 1/1/2 10.1.2.2 10.10.10.242/32 Swap 131068 131069 1/1/2 10.1.2.2 10.10.10.243/32 Push -- 131070 1/1/4 10.1.3.3 10.10.10.243/32 Swap 131066 131070 1/1/4 10.1.3.3 10.10.10.244/32 Push -- 131064 1/1/2 10.1.2.2 10.10.10.244/32 Swap 131064 131064 1/1/2 10.1.2.2 10.10.10.244/32 Push -- 131064 1/1/4 10.1.3.3 10.10.10.244/32 Swap 131064 131064 1/1/4 10.1.3.3 ---No. of Prefix Bindings: 19

===============================================================================

Alcatel-Lucent

Confidential

for

internal

use

only

--

Do

Not

Distribute

8. From your PE router do a LSP trace to the diagonally connected neighbor P router system address. Which

LSP is used?

9. From your PE router do a LSP trace to the diagonally connected neighbor PE router system address.

Which LSP is used?

10. Re-enable the interface from your P router to your diagonally connected neighbor P router by executing a

‘no shutdown’ command.

Section 3.4 – Applying Export Policy for Label Distribution

Exercise:

1. Configure an Export policy with a single entry set to “action accept”. An example is shown below.

2. Apply the Export policy to LDP on your PE and P router.

3. Verify the Label Information Base (LIB) of your P and PE routers. An example is shown below.

a. For what additional FEC are labels now generated?

b. How many Prefix bindings should be present? Explain.

--- echo "Policy Configuration"

#--- policy-options begin policy-statement "ldp-export" entry 10 action accept exit exit exit commit exit exit

Alcatel-Lucent

Confidential

for

internal

use

only

--

Do

Not

Distribute

4. Verify that the Label Forwarding Information Base (LFIB) of your P and PE routers contains the active

labels used by the router for MPLS forwarding. An example is shown below.

A:PE1# show router ldp bindings

=============================================================================== LDP LSR ID: 10.10.10.241

=============================================================================== Legend: U - Label In Use, N - Label Not In Use, W - Label Withdrawn

S - Status Signaled Up, D - Status Signaled Down E - Epipe Service, V - VPLS Service, M - Mirror Service

A - Apipe Service, F - Fpipe Service, I - IES Service, R - VPRN service P - Ipipe Service

=============================================================================== LDP Prefix Bindings

=============================================================================== Prefix Peer IngLbl EgrLbl EgrIntf EgrNextHop ---10.1.2.0/24 10.10.10.221 131067N 131069 1/2/1 10.16.1.1 10.1.3.0/24 10.10.10.221 131064N 131061 1/2/1 10.16.1.1 10.1.4.0/24 10.10.10.221 131053N 131051 1/2/1 10.16.1.1 10.2.3.0/24 10.10.10.221 131059N 131058 1/2/1 10.16.1.1 10.2.4.0/24 10.10.10.221 131058N 131057 1/2/1 10.16.1.1 10.3.4.0/24 10.10.10.221 131057N 131055 1/2/1 10.16.1.1 10.10.10.221/32 10.10.10.221 -- 131071 1/2/1 10.16.1.1 10.10.10.222/32 10.10.10.221 131069N 131070 1/2/1 10.16.1.1 10.10.10.223/32 10.10.10.221 131068N 131067 1/2/1 10.16.1.1 10.10.10.224/32 10.10.10.221 131061N 131065 1/2/1 10.16.1.1 10.10.10.241/32 10.10.10.221 131071U -- -- -- 10.10.10.242/32 10.10.10.221 131066N 131068 1/2/1 10.16.1.1 10.10.10.243/32 10.10.10.221 131065N 131066 1/2/1 10.16.1.1 10.10.10.244/32 10.10.10.221 131060N 131064 1/2/1 10.16.1.1 10.16.1.0/24 10.10.10.221 131063U 131060 -- -- 10.32.1.0/24 10.10.10.221 131062N 131059 1/2/1 10.16.1.1 10.48.1.0/24 10.10.10.221 131056N 131054 1/2/1 10.16.1.1 10.64.1.0/24 10.10.10.221 131052N 131050 1/2/1 10.16.1.1 ---No. of Prefix Bindings: 18

=============================================================================== LDP Service Bindings

=============================================================================== Type VCId SvcId SDPId Peer IngLbl EgrLbl LMTU RMTU ---No Matching Entries Found

============================================================================

Alcatel-Lucent

Confidential

for

internal

use

only

--

Do

Not

Distribute

A:P1# show router ldp bindings active

=============================================================================== Legend: (S) - Static

=============================================================================== LDP Prefix Bindings (Active)

=============================================================================== Prefix Op IngLbl EgrLbl EgrIntf EgrNextHop ---10.1.2.0/24 Pop 131069 -- -- -- 10.1.3.0/24 Pop 131061 -- -- -- 10.2.4.0/24 Swap 131057 131057 1/1/2 10.1.2.2 10.3.4.0/24 Swap 131055 131053 1/1/4 10.1.3.3 10.10.10.221/32 Pop 131071 -- -- -- 10.10.10.222/32 Push -- 131071 1/1/2 10.1.2.2 10.10.10.222/32 Swap 131070 131071 1/1/2 10.1.2.2 10.10.10.223/32 Push -- 131071 1/1/4 10.1.3.3 10.10.10.223/32 Swap 131067 131071 1/1/4 10.1.3.3 10.10.10.224/32 Push -- 131065 1/1/4 10.1.3.3 10.10.10.224/32 Swap 131065 131065 1/1/4 10.1.3.3 10.10.10.241/32 Push -- 131071 1/1/1 10.16.1.2 10.10.10.241/32 Swap 131063 131071 1/1/1 10.16.1.2 10.10.10.242/32 Push -- 131069 1/1/2 10.1.2.2 10.10.10.242/32 Swap 131068 131069 1/1/2 10.1.2.2 10.10.10.243/32 Push -- 131070 1/1/4 10.1.3.3 10.10.10.243/32 Swap 131066 131070 1/1/4 10.1.3.3 10.10.10.244/32 Push -- 131064 1/1/4 10.1.3.3 10.10.10.244/32 Swap 131064 131064 1/1/4 10.1.3.3 10.16.1.0/24 Pop 131060 -- -- -- 10.32.1.0/24 Swap 131059 131059 1/1/2 10.1.2.2 10.48.1.0/24 Swap 131054 131054 1/1/4 10.1.3.3 10.64.1.0/24 Swap 131050 131049 1/1/4 10.1.3.3 ---No. of Prefix Bindings: 23

===============================================================================

Section 3.5 – Configuring Targeted LDP

Exercise:

1. On your PE router configure Targeted LDP sessions with every other PE router and with your P router.

2. On your P router configure a Targeted LDP session with your PE router.

3. Verify that the LDP Targeted sessions are operational. An example is shown below.

a. What adjacency types are established between the PE routers? Why?

b. What adjacency type is established between your PE and P routers? Why?

Alcatel-Lucent

Confidential

for

internal

use

only

--

Do

Not

Distribute

A:PE1# show router ldp session

=============================================================================== LDP Sessions

=============================================================================== Peer LDP Id Adj Type State Mesg Sent Mesg Recv Up Time ---10.10.10.221:0 Both Established 258 257 0d 00:10:48 10.10.10.242:0 Targeted Established 434 431 0d 01:42:14 10.10.10.243:0 Targeted Established 273 275 0d 00:24:44 10.10.10.244:0 Targeted Established 12777 12778 0d 19:26:17 ---No. of Sessions: 4 ===============================================================================

4. On your PE and P router verify that both interface based LDP and targeted LDP are enabled. An example is

shown below.

a. How many direct and targeted LDP peers do your PE and P routers have?

b. What are the FECs sent by your PE and P routers?

c. What are the FECs received by your PE and P routers?

A:P1# show router ldp status

=============================================================================== LDP Status for LSR ID 10.10.10.221

=============================================================================== Admin State : Up Oper State : Up Created at : 09/13/2006 15:49:31 Up Time : 0d 20:10:10 Oper Down Reason : n/a Oper Down Events : 0 Last Change : 09/13/2006 19:19:10 Tunn Down Damp Time : 3 sec Import Policies : None Export Policies : None

Active Adjacencies : 5 Active Sessions : 4 Active Interfaces : 4 Inactive Interfaces : 0 Active Peers : 1 Inactive Peers : 0 Addr FECs Sent : 24 Addr FECs Recv : 24

Serv FECs Sent : 0 Serv FECs Recv : 0 Attempted Sessions : 0 No Hello Err : 0 Param Adv Err : 0 Max PDU Err : 0 Label Range Err : 0 Bad LDP Id Err : 0 Bad PDU Len Err : 0 Bad Mesg Len Err : 0 Bad TLV Len Err : 0 Malformed TLV Err : 0 Keepalive Expired Err: 0 Shutdown Notif Sent: 0 Shutdown Notif Recv : 1 ===============================================================================

5. Verify that the MPLS label exchange has not been impacted by the change in LDP by using the ‘show

router ldp bindings [active] command. Compare the output to that shown in Section 3-2 to ensure they are

the same.

Note: After having configured Targeted LDP in this lab you will notice that no additional labels appear in the output

of the ‘show router ldp bindings’ command. In other words, the T-LDP peers have not exchanged any label bindings

over their Targeted LDP session. This is normal behavior. The T-LDP peers will only generate and exchange labels

after VLL or VPLS services are configured between them.

Alcatel-Lucent

Confidential

for

internal

use

only

--

Do

Not

Distribute

Lab 3 Review Questions

1. Which command may be used to view the details of each LDP peer?

2. Is it possible for two routers to form both a link and targeted LDP adjacency?

3. For which FECs are labels advertised by default? How can additional FECs be advertised?

4. How does a router determine which LSP to use when ECMP LDP is enabled?

Alcatel-Lucent

Confidential

for

internal

use

only

--

Do

Not

Distribute

Lab 4

Enabling Provider Core OSPF-TE and MPLS

Objective:

The purpose of this lab is to enable MPLS and Traffic Engineering extensions on the OSPF routing protocol in the

service provider network and verify the Traffic Engineering Database.

Figure 4-1: Enabling Provider Core MPLS

Syntax:

The configuration and verification commands required for this Lab are provided in Table 4-1. Refer to the student

guide for additional command details. Each command may have additional parameters possible. Use the ‘?’

character for help and to explore all command line options. Other commands may also be used, including those

found in previous exercises and courses.

Pod 1

Pod 2

Pod 3

Pod 4

Service Provider Network

LDP Enabled Core

Alcatel-Lucent

Confidential

for

internal

use

only

--

Do

Not

Distribute

Lab 4 Command List

#configure router ospf traffic-engineering

#configure router mpls interface <interface-name> #show router ospf status

#show router ospf opaque-database

#show router ospf opaque-database adv-router <router-id> detail #show router ospf area detail

info (from all contexts) exit [all] (from all contexts) #admin save

Table 4-1 Lab 4 Configuration and Verification Commands

Exercise:

1. On your P and PE routers use the “show router status” command to verify that MPLS has not been

configured (i.e. the administrative and operational status of MPLS is “Not configured”).

2. On your P and PE routers, use the “show router ospf status” command to verify that currently Traffic

Engineering is disabled.

a. Are Opaque LSAs supported on your P/PE router?

b. What does it mean if a router supports Opaque LSAs but TE support is disabled?

3. On your P router view the opaque database to verify that currently the router does not see any opaque

LSAs. An example of the output is shown below.

Note: If others in the class have already enabled TE, your router may see some Opaque LSAs but they are not

being generated by your router since you have not yet enabled TE.

A:P1# show router ospf opaque-database

=============================================================================== OSPF Opaque Link State Database (Type : All)

=============================================================================== Type Id Link State Id Adv Rtr Id Age Sequence Cksum ---No. of Opaque LSAs: 0

=============================================================================== A:P1#

Alcatel-Lucent

Confidential

for

internal

use

only

--

Do

Not

Distribute

A

=============================================================================== OSPF Areas (Detailed)

=============================================================================== ---Area Id: 0.0.0.0

---Area Id : 0.0.0.0 Type : Standard Virtual Links : 0 Total Nbrs : 4 Active IFs : 5 Total IFs : 5 Area Bdr Rtrs : 0 AS Bdr Rtrs : 0 SPF Runs : 73 Last SPF Run : 09/14/2006 11:15:27

Router LSAs : 8 Network LSAs : 9 Summary LSAs : 0 Asbr-summ LSAs : 0 Nssa ext LSAs : 0 Area opaque LSAs : 0 Total LSAs : 17 LSA Cksum Sum : 0x138e83

Blackhole Range : True Unknown LSAs : 0 ===============================================================================

5. For now enable Traffic Engineering only on your PE router.

6. Now on your P router again view the number of Type 10 Area Opaque LSAs. An example output is shown

below.

a. How many Type 10 LSAs do you see?

b. Why has this value increased even though you have not enabled TE on this router?

A:P1# show router ospf area detail

=============================================================================== OSPF Areas (Detailed)

=============================================================================== ---Area Id: 0.0.0.0

---Area Id : 0.0.0.0 Type : Standard

Virtual Links : 0 Active IFs : 5 Area Bdr Rtrs : 0 AS Bdr Rtrs : 0

SPF Runs : 14 Last SPF Run : 02/02/2002 18:05:05 Router LSAs : 8 Network LSAs : 9

Summary LSAs : 0 Asbr-summ LSAs : 0 Nssa ext LSAs : 0 Area opaque LSAs : 1 Total LSAs : 25 LSA Cksum Sum : 0xc531b Blackhole Range : True

=============================================================================== A:P1#

7. Now enable Traffic Engineering on your P router.

8. Confirm that now Traffic Engineering is now enabled

9. On your P router verify that the router now has opaque routes in the database. An example output is shown

below.

Alcatel-Lucent

Confidential

for

internal

use

only

--

Do

Not

Distribute

A:P1# show router ospf opaque-database

=============================================================================== OSPF Opaque Link State Database (Type : All)

=============================================================================== Type Id Link State Id Adv Rtr Id Age Sequence Cksum ---Area 0.0.0.0 1.0.0.1 10.10.10.75 60 0x80000001 0x3b41 Area 0.0.0.0 1.0.0.1 10.10.10.76 65 0x80000001 0x3f3b Area 0.0.0.0 1.0.0.1 10.10.10.77 36 0x80000001 0x4335 Area 0.0.0.0 1.0.0.1 10.10.10.78 41 0x80000001 0x472f Area 0.0.0.0 1.0.0.1 10.10.10.79 49 0x80000001 0x4b29 Area 0.0.0.0 1.0.0.1 10.10.10.80 46 0x80000001 0x4f23 Area 0.0.0.0 1.0.0.1 10.10.10.81 25 0x80000001 0x531d Area 0.0.0.0 1.0.0.1 10.10.10.82 19 0x80000001 0x5717 ---No. of Opaque LSAs: 8

=============================================================================== A:P1#

10. On your P router use the “show router ospf opaque-database adv-router <router-id> detail” command,

where <router-id> is the router ID of your P router, to view a more detailed description of the opaque LSA

for your router. An example output is shown below.

a. What is the LSA type number for “Area Opaque”?

b. Why does the Area ID show up as 0.0.0.0?

c. Which top-level TLV sub-type does the LSA contain, and what does it specify?

A:P1# show router ospf opaque-database adv-router 10.10.10.221 detail

=============================================================================== OSPF Opaque Link State Database (Type : All) (Detailed)

=============================================================================== ---Opaque LSA

---Area Id : 0.0.0.0 Adv Router Id : 10.10.10.221 Link State Id : 1.0.0.1 LSA Type : Area Opaque Sequence No : 0x80000001 Checksum : 0x3b41 Age : 221 Length : 28 Options : E Advertisement : ROUTER-ID TLV (0001) Len 4 : 10.10.10.221 ===============================================================================

11. Again verify the number of Type 10 Area Opaque LSAs now discovered. An example output is shown

below.

a. Write down the number of Type 10 LSAs now being reported.

Alcatel-Lucent

Confidential

for

internal

use

only

--

Do

Not

Distribute

A:P1# show router ospf area detail

=============================================================================== OSPF Areas (Detailed)

=============================================================================== ---Area Id: 0.0.0.0

---Area Id : 0.0.0.0 Type : Standard

Virtual Links : 0 Active IFs : 5 Area Bdr Rtrs : 0 AS Bdr Rtrs : 0

SPF Runs : 14 Last SPF Run : 02/02/2002 18:05:05 Type 1 LSAs : 8 Type 2 LSAs : 9

Type 3 LSAs : 0 Type 4 LSAs : 0 Type 7 LSAs : 0 Type 10 LSAs : 8 Total LSAs : 25 LSA Cksum Sum : 0xc531b Blackhole Range : True

=============================================================================== A:P1#

12. Enable MPLS for all interfaces on your P and PE routers, including your system interfaces.

13. Verify that MPLS has been enabled for your interfaces and that the relevant interfaces are administratively

and operationally “up”. An example output is shown below.

A:P1# show router mpls interface

=============================================================================== MPLS Interfaces

=============================================================================== Interface Port-id Adm Opr

---system ---system Up Up

Admin Groups None

P1-PE1 1/1/1 Up Up Admin Groups None

P1-P2 1/1/2 Up Up Admin Groups None

P1-P3 1/1/3 Up Up Admin Groups None

P1-P4 1/1/4 Up Up Admin Groups None

---Interfaces : 5

=============================================================================== A:P1#

14. On your P router again use the “show router ospf opaque-database adv-router <router-id> detail” command,

where <router-id> is the router ID of your P router, to view a more detailed description of the opaque LSA

for your router. An example output is shown below.

a. How many opaque LSAs does your P router have in its opaque-database?

b. The LSAs contain which additional top-level TLV sub-type? What does this LSA specify?

Alcatel-Lucent

Confidential

for

internal

use

only

--

Do

Not

Distribute

A:PE1# show router ospf opaque-database adv-router 10.10.10.241 detail

=============================================================================== OSPF Opaque Link State Database (Type : All) (Detailed)

=============================================================================== ---Opaque LSA

---Area Id : 0.0.0.0 Adv Router Id : 10.10.10.241 Link State Id : 1.0.0.1 LSA Type : Area Opaque Sequence No : 0x80000001 Checksum : 0xd559 Age : 10 Length : 28 Options : E Advertisement : ROUTER-ID TLV (0001) Len 4 : 10.10.10.241 ---Opaque LSA ---Area Id : 0.0.0.0 Adv Router Id : 10.10.10.241 Link State Id : 1.0.0.2 LSA Type : Area Opaque Sequence No : 0x80000001 Checksum : 0x2e2f Age : 10 Length : 124 Options : E Advertisement : LINK INFO TLV (0002) Len 100 :

Sub-TLV: 1 Len: 1 LINK_TYPE : 2

Sub-TLV: 2 Len: 4 LINK_ID : 10.16.1.2 Sub-TLV: 3 Len: 4 LOC_IP_ADDR : 10.16.1.2 Sub-TLV: 4 Len: 4 REM_IP_ADDR : 0.0.0.0 Sub-TLV: 5 Len: 4 TE_METRIC : 100

Sub-TLV: 6 Len: 4 MAX_BDWTH : 1000000 Kbps Sub-TLV: 7 Len: 4 RSRVBL_BDWTH : 1000000 Kbps Sub-TLV: 8 Len: 32 UNRSRVD_CLS0 :

P0: 1000000 Kbps P1: 1000000 Kbps P2: 1000000 Kbps P3: 1000000 Kbps P4: 1000000 Kbps P5: 1000000 Kbps P6: 1000000 Kbps P7: 1000000 Kbps Sub-TLV: 9 Len: 4 ADMIN_GROUP : 0 None

===========================================================================

Lab 4 Review Questions

1. Why must Traffic Engineering extensions be enabled on OSPF?

2. What additional information is advertised by the routers when Traffic Engineering is enabled on OSPF?

3. What type of LSA is used to carry this additional information and where is it stored?

4. What happens to the LSA type used for TE extensions in a multi-area OSPF network?

5. What is missing in the opaque database if MPLS has not been enabled on the routers’ interfaces?

Alcatel-Lucent

Confidential

for

internal

use

only

--

Do

Not

Distribute

Lab 5

CSPF Based LSPs and LSP Establishment

Objective:

The purpose of this lab is to:

• Establish LSPs using RSVP-TE signaling, with and without constraints, and to observe the path determined

for the LSPs.

• View the RSVP messages exchanged during LSP establishment.

Figure 5-1: CSPF Based LSPs

Syntax:

The configuration and verification commands required for this Lab are provided in Table 5-1. Refer to the student

guide for additional command details. Each command may have additional parameters possible. Use the ‘?’

character for help and to explore all command line options. Other commands may also be used, including those

found in previous exercises and courses.

Pod 1

Pod 2

Pod 3

Pod 4

Service Provider Network

RSVP-TE Enabled Core

Alcatel-Lucent

Confidential

for

internal

use

only

--

Do

Not

Distribute