2015-09-04.MPLS LabGuide Ver2.2

May, 2015
Version 2.2.0
Lab Guide
Alcatel-Lucent Multiprotocol Label Switching (MPLS)
This ALU-IPD-SRC Alcatel-Lucent Multiprotocol Label Switching Guide is for exclusive use of Jeremias Nhaduco - MCEL
TABLE OF CONTENTS
LAB 3 MPLS INFRASTRUCTURE AND LDP CONFIGURATION .........................................................4
3.1. MPLS Infrastructure Verification and IGP Configuration .................................................................7
3.2. Configuring and Verifying the Provider Core for LDP .................................................................... 10
3.3. Enabling LDP ECMP ....................................................................................................................... 19
3.4. Applying Export Policy for Label Distribution ................................................................................. 24
LAB 3 REVIEW QUESTIONS .......................................................................................................................... 27
LAB 4 IGP-BASED RSVP LSP ESTABLISHMENT ................................................................................. 29
LAB 5 ENABLING RSVP-TE LSP TUNNELS ........................................................................................... 35
5.1. Configure Link Coloring for Constraint-Based LSP Tunnels ........................................................... 37
5.2. LSP Soft Preemption ......................................................................................................................... 56
5.3. Configure LDP over RSVP across OSPF Areas ............................................................................... 66
5.4. Configure RSVP for IP Routing ........................................................................................................ 74
LAB 6 RSVP-TE RESILIENCY FEATURES ............................................................................................. 81
6.1. Enabling Primary and Secondary LSP Tunnels ............................................................................... 83
6.2. Using SRLG for Path Resiliency ....................................................................................................... 97
6.3. FRR Facility Backup Protection ..................................................................................................... 106
6.4. FRR One-to-One Protection ........................................................................................................... 114
LAB 6 REVIEW QUESTIONS ........................................................................................................................ 125
Alcatel-Lucent Multiprotocol Label Switching Lab Guide v2.2 | All rights reserved 2015 Alcatel-Lucent 2/127
LIST OF FIGURES
FIGURE 3-1: LAB TOPOLOGY OVERVIEW ................................................................................................................4
FIGURE 3-2: IMPLEMENTING PROVIDER CORE LDP .............................................................................................. 10
FIGURE 3-3: ENABLING LDP ECMP ..................................................................................................................... 19
FIGURE 3-4: APPLYING EXPORT POLICY FOR LABEL DISTRIBUTION ..................................................................... 24
FIGURE 4-1: IGP BASED LSPS ............................................................................................................................... 29
FIGURE 5-1: ENABLING LINK COLORING CONSTRAINT-BASED LSP TUNNELS...................................................... 37
FIGURE 5-4: ENABLING LDP TUNNELS OVER RSVP ............................................................................................. 66
FIGURE 5-5: ENABLING LDP TUNNELS OVER RSVP ............................................................................................. 74
FIGURE 6-1: ENABLING PRIMARY AND SECONDARY LSP TUNNELS ...................................................................... 83
FIGURE 6-2: ENABLING SRLG STANDBY LSPS ..................................................................................................... 97
FIGURE 6-3: ENABLING FRR FACILITY BYPASS PROTECTION ............................................................................. 106
FIGURE 6-4: ENABLING FRR ONE-TO-ONE PROTECTION .................................................................................... 114
LIST OF TABLES
TABLE 3-1: LAB 3 CONFIGURATION AND VERIFICATION COMMANDS .....................................................................5
TABLE 3-2: REMOTE LAB ADDRESSING ..................................................................................................................7
TABLE 3-3: INTERFACE IP ADDRESSING..................................................................................................................9
TABLE 4-1: LAB 4 CONFIGURATION AND VERIFICATION COMMANDS ................................................................... 30
Lab 3 MPLS Infrastructure and LDP Configuration
Objective
This lab prepares the routed domain to support the MPLS infrastructure that we will build as we
progress through the course. Here, we will verify the operation and physical connectivity between
the pods and the routers in the pods. We will verify and, if necessary, configure the interfaces and
IGP.
Once we have the routed core in place, we will begin exploring LDP operations. First, we will enable
and verify LDP operation on the CORE (R1 to R4) and EDGE (R5 to R8) routers. We will identify the
labels that the routers exchange and use to populate their LFIBs, mapping out the labels that an LSP
uses for a given FEC. We will configure export policies to allow the routers to generate labels for
prefixes other than /32 prefixes and, finally, enable ECMP and view the impact that it has on the
LFIBs.
Figure 3-1 shows the lab topology. Additional connection details will be provided by the instructor, if
required.
Figure 3-1: Lab Topology Overview
The Alcatel-Lucent Multiprotocol Label Switching (MPLS) course labs use 7750 Service Routers for the
core infrastructure, as shown in Figure 3-1. The 7750 SR Edge (EDGE) routers and the 7750 SR Core
(CORE) routers form the service provider core backbone.
Syntax
Table 3-1 provides the configuration and verification commands required for this lab. Each command
may require additional parameters other than those shown in the table. Use the ? character for
help and to explore all command line options. In addition to the commands shown, you may need to
use commands learned in previous courses.
Lab 3 Command list
A:MPLS_R1# telnet <management ip address>

A:MPLS_R1# configure router interface <interface name> address
<address/mask>
A:MPLS_R1# configure router interface <interface name> port <iom/mda/port>
A:MPLS_R1# configure router ospf area <area #>
A:MPLS_R1# configure router ospf area <area #> interface <interface name>
interface-type <point-to-point>
A:MPLS_R1# show port
A:MPLS_R1# show router interface
A:MPLS_R1# show router ospf status
A:MPLS_R1# show router ospf interface
A:MPLS_R1# show router ospf neighbor
A:MPLS_R1# show router route-table
A:MPLS_R1# ping <ip-address>
A:MPLS_R1# traceroute <ip-route>
A:MPLS_R1# configure router ldp interface-parameters interface <interface-
name>
A:MPLS_R1# configure router ldp export <export-policy-name>
A:MPLS_R1# configure>router>policy-options# begin
A:MPLS_R1# configure>router>policy-options# policy-statement <policy-name>
A:MPLS_R1# configure>router>policy-options>policy-statement# entry <entry
index>
A:MPLS_R1# configure>router>policy-options>policy-statement>entry# action
accept
A:MPLS_R1# configure>router>policy-options# commit
A:MPLS_R1# clear router ldp session <neighbor-ip-address>
A:MPLS_R1# show router status
A:MPLS_R1# show router route-table
A:MPLS_R1# show router ldp status
A:MPLS_R1# show router ldp parameters
Table 3-1: Lab 3 Configuration and Verification Commands
Lab 3 Command list (contd)
A:MPLS_R1# show router ldp discovery [detail]
A:MPLS_R1# show router ldp interface
A:MPLS_R1# show router ldp session
A:MPLS_R1# show router ldp bindings
A:MPLS_R1# show router ldp bindings active
A:MPLS_R1# show router ldp tunnel-table
A:MPLS_R1# oam lsp-ping prefix <ip-address>
A:MPLS_R1# oam lsp-trace prefix <ip-address>
A:MPLS_R1>..# info (from all contexts)
A:MPLS_R1>..# exit [all] (from all contexts)
A:MPLS_R1# admin save <file-name>
Table 3-1: Lab 3 Configuration and Verification Commands (contd)
3.1. MPLS Infrastructure Verification and IGP Configuration
Exercise
1. Record your pods router management interface addresses in Table 3-2 below. Use these
addresses to establish a telnet connection to your CORE, EDGE, and CE routers.
All routers use the default SR OS username and password, admin. If you cannot connect or log in to
any of the routers, notify your instructor. Please do not change the admin password unless instructed
to do so.
Pod Number Management Address
Pod 1 CORE (R1)

EDGE (R5)
CUSTOMER EDGE (R9)
Pod 2 CORE (R2)
EDGE (R6)
CUSTOMER EDGE (R10)
Pod 3 CORE (R3)
EDGE (R7)
CUSTOMER EDGE (R11)
Pod 4 CORE (R4)
EDGE (R8)
CUSTOMER EDGE (R12)
Table 3-2: Remote Lab Addressing
2. Familiarize yourself with lab topology, shown in Figure 3-1.

3. Verify the cards, MDAs, and physical ports using the appropriate show commands. The
configuration should match the topology shown in Figure 3-1.
4. Use the appropriate show commands to verify each interfaces IP address, as defined in Table
3-3. For consistency, the last octet of a routers IP address equals the router number shown
in both Figure 3-1 and Table 3-2. All interfaces should be operationally up.
5. Verify that OSPF area 0 is defined on all CORE and EDGE routers and includes all interfaces
EXCEPT the CE system interfaces and CE-EDGE link interfaces. (CE interfaces will be
configured in Lab 5).
6. Verify the routing tables. The CORE and EDGE routers need routes to all subnetworks,
including the system IDs, EXCEPT to the CE networks. Refer to Table 3-3 for a list of subnet
addresses. With all 4 pods in use, the route tables contain:
a. On the CORE routers:
i. 10 Ethernet segments
ii. 8 system addresses
iii. 13 OSPF routes
b. On the EDGE routers:
i. 11 Ethernet segments
ii. 8 system addresses
iii. 16 OSPF routes
c. On the CE routers:
i. 1 Ethernet segment
ii. 1 system address
iii. 0 OSPF routes
Use available tools such as ping or traceroute. If all is working as designed, you should be
able to successfully ping each OSPF area 0 interface from any CORE or EDGE router.
7. If you do not see all that you expect, ask your instructor for help or clarification.
8. You may want to annotate the diagram with the configured addresses or other parameters.
Parameter Value
Interface name toRy = where y is the opposite routers router

number
Addressing Format 10.x.y.z/27
1st router number x = 1 (R1), 2 (R2), 3 (R3), 4 (R4), etc.
2nd router number y = opposite router number
For the last octet of the interface address z= the number of the router on which the interface is
use the router number from Figure 3-1 defined (either x or y)
System IP address 10.10.10.z/32
R1 to R2 subnet 10.1.2.z/27 (10.1.2.1/27 on R1, 10.1.2.2/27 on R2)
R1 to R3 subnet 10.1.3.z/27
R6 to R10 subnet 10.6.10.z/27
R7 to R11 subnet 10.7.11.z/27
R8 to R12 subnet 10.8.12.z/27
Table 3-3: Interface IP Addressing
3.2. Configuring and Verifying the Provider Core for LDP
Figure 3-2: Implementing Provider Core LDP
Exercise
1. On your CORE and EDGE routers, enable LDP on all but the EDGE-CE interfaces.
On your CORE router, the LDP configuration should look like:
*A:MPLSv2_R1>config>router>ldp# info
----------------------------------------------
interface-parameters
interface "toR2"
exit
interface "toR3"
exit
interface "toR4"
exit
interface "toR5"
exit
exit
targeted-session
exit
no shutdown
----------------------------------------------
On your EDGE router, the LDP configuration should look like:
----------------------------------------------
interface "toR1"
exit
exit
targeted-session
exit
no shutdown
----------------------------------------------
2. Verify that the base IGP and LDP processes are up on your EDGE and CORE routers, and that
LDP has been enabled on all the appropriate network interfaces. The example below shows
the LDP adjacencies between neighbors.
a. How many LDP neighbors should each CORE router (R1, R2, R3, and R4) have?
Four, as per the following output:
*A:MPLSv2_R1# show router ldp discovery
===============================================================================
LDP Hello Adjacencies
===============================================================================
Interface Name Local Addr Peer Addr AdjType State
-------------------------------------------------------------------------------
toR2 10.10.10.1 10.10.10.2 Link Estab
toR3 10.10.10.1 10.10.10.3 Link Estab
toR4 10.10.10.1 10.10.10.4 Link Estab
toR5 10.10.10.1 10.10.10.5 Link Estab
-------------------------------------------------------------------------------
No. of Hello Adjacencies: 4
===============================================================================
b. How many LDP neighbors should each EDGE router (R5, R6, R7, and R8) have?
One, as per the following output:
*A:MPLSv2_R5# show router ldp discovery
===============================================================================
LDP Hello Adjacencies
===============================================================================
Interface Name Local Addr Peer Addr AdjType State
-------------------------------------------------------------------------------
toR1 10.10.10.5 10.10.10.1 Link Estab
-------------------------------------------------------------------------------
No. of Hello Adjacencies: 1
===============================================================================
3. Verify that your routers LDP sessions show Established.

An example of the output is shown below.
a. How many LDP sessions does your CORE router have?
Four, as per the following output:
*A:MPLSv2_R1# show router ldp session
==============================================================================
LDP Sessions
==============================================================================
Peer LDP Id Adj Type State Msg Sent Msg Recv Up Time
------------------------------------------------------------------------------
10.10.10.2:0 Link Established 253 254 0d 00:11:22
------------------------------------------------------------------------------
No. of Sessions: 4
==============================================================================
b. How many LDP sessions does your EDGE router have?

One, as per the following output:
==============================================================================
LDP Sessions
==============================================================================
------------------------------------------------------------------------------
------------------------------------------------------------------------------
No. of Sessions: 1
==============================================================================
c. What types of adjacencies do your routers form? Why?
Link adjacencies are formed because the LDP peers are directly connected to each other.
4. Verify the Label Information Base (LIB) of your CORE and EDGE routers.
An example is shown in step c.
a. How many prefixes should be present? Explain.
There should be 32 prefix bindings; there are 8 prefixes (FECs)- one for each system
interface address. Each CORE router receives labels for these FECs from each of its 4
peers.
b. Should the CORE and EDGE routers have the same number of prefix bindings?
No. The EDGE router should have 8 prefix bindings since it receives a label for each
binding only from the directly connected peer (the connected CORE router).
c. What label does your CORE router generate for its system address FEC?
Your output might vary from the one below. In the example below, the label generated
by router R1 for its system interface address (10.10.10.1/32) is 131071.
*A:MPLSv2_R1# show router ldp bindings
===============================================================================
LDP LSR ID: 10.10.10.1
===============================================================================
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, WP - Label Withdraw Pending, C - Cpipe Service
BU - Alternate Next-hop for Fast Re-Route, TLV - (Type, Length: Value)
===============================================================================
LDP Prefix Bindings
===============================================================================
Prefix IngLbl EgrLbl EgrIntf/ EgrNextHop
Peer LspId
-------------------------------------------------------------------------------
10.10.10.1/32 131071U -- -- --
10.10.10.2
10.10.10.1/32 131071U -- -- --
10.10.10.3
10.10.10.1/32 131071U -- -- --
10.10.10.4
10.10.10.1/32 131071U -- -- --
10.10.10.5
10.10.10.2/32 -- 131071 1/1/2 10.1.2.2
10.10.10.2
10.10.10.2/32 131070U 131069 -- --
10.10.10.3
10.10.10.2/32 131070U 131069 -- --
10.10.10.4
10.10.10.2/32 131070U 131069 -- --
10.10.10.5
10.10.10.3/32 131069U 131069 -- --
10.10.10.2
10.10.10.3/32 -- 131071 1/1/3 10.1.3.3
10.10.10.3
10.10.10.3/32 131069U 131068 -- --
10.10.10.4
10.10.10.3/32 131069U 131068 -- --
10.10.10.5
10.10.10.4/32 131068U 131068 -- --
10.10.10.2
10.10.10.4/32 131068U 131068 -- --
10.10.10.3
10.10.10.4/32 -- 131071 1/1/4 10.1.4.4
10.10.10.4
10.10.10.4/32 131068U 131067 -- --
10.10.10.5
10.10.10.5/32 131067U 131067 -- --
10.10.10.2
10.10.10.5/32 131067U 131067 -- --
10.10.10.3
10.10.10.5/32 131067U 131067 -- --
10.10.10.4
10.10.10.5/32 -- 131071 1/1/1 10.1.5.5
10.10.10.5
10.10.10.6/32 131066N 131066 1/1/2 10.1.2.2
10.10.10.2
10.10.10.6/32 131066U 131066 -- --
10.10.10.3
10.10.10.6/32 131066U 131066 -- --
10.10.10.4
10.10.10.6/32 131066U 131066 -- --
10.10.10.5
10.10.10.7/32 131065U 131065 -- --
10.10.10.2
10.10.10.7/32 131065N 131065 1/1/3 10.1.3.3
10.10.10.3
10.10.10.7/32 131065U 131065 -- --
10.10.10.4
10.10.10.7/32 131065U 131065 -- --
10.10.10.5
10.10.10.8/32 131064U 131064 -- --
10.10.10.2
10.10.10.8/32 131064U 131064 -- --
10.10.10.3
10.10.10.8/32 131064N 131064 1/1/4 10.1.4.4
10.10.10.4
10.10.10.8/32 131064U 131064 -- --
10.10.10.5
-------------------------------------------------------------------------------
No. of Prefix Bindings: 32
===============================================================================
d. On your CORE router, find the label that the diagonally connects CORE router supplies for
its directly connected EDGE router.
Depends on output. A sample is shown in "c". Router R4 advertises label 131064 to R1 for
its connected EDGE router R8 (10.10.10.8/32).
e. Why does your CORE router show some labels as N (label not in use)?
The labels not in use indicate that the router has generated a label for a given FEC, and
that the next-hop to reach that FEC is that peer router itself. Therefore, the CORE
router will not advertise a label to one of its peers if that peer is the next-hop to reach
the FEC for which the label is generated.
For example, router R1 does not advertize a label for router R8's system address to
router R4 since R4 is the next hop router to reach R8. The label 131064 is marked with
"N", which stands for "label not in use" as defined in the output's legend.
5. Verify that your CORE and EDGE routers Label Forwarding Information Base (LFIB) contains
the active labels used by the router for MPLS forwarding.
An example is shown in step d.
a. What are the differences between the show router ldp bindings and the show
router ldp bindings active commands? Why does the LFIB contain fewer prefix
bindings than the FIB?
The former command gives the LIB and the latter gives the LFIB. The LIB contains all
labels received for a given FEC, while the LFIB only contains the label that is actually
used to forward packets. This active label corresponds to the label received from the
router that is the next-hop to reach that FEC.
b. Why does your CORE router both PUSH and SWAP labels for your EDGE routers prefix?
Why does it not POP labels for your EDGE routers prefix?
The PUSH operation applies when unlabeled packets destined for the FEC arrive at the
router, while the SWAP operation applies when labeled packets with the corresponding
ingress label arrive at the router. The CORE router applies the POP operation when
labeled packets are destined for its own FEC and only applies Push and SWAP operations
for the EDGE router's prefix.
c. Based on the show router ldp bindings active command output, can you identify
the system address of the router on which you executed the command?
Yes, by looking at the prefix for which the operation is POP.
d. Verify each label PUSHed, SWAPed, and POPed along the LSP path from your EDGE router
to the diagonally connected EDGE router.
Repeat the following for all 4 routers (2 EDGE and 2 CORE routers) along the LSP path
between the 2 diagonal EDGE routers:
*A:MPLSv2_R1# show router ldp bindings active
===============================================================================
Legend: (S) - Static (M) - Multi-homed Secondary Support
(B) - BGP Next Hop (BU) - Alternate Next-hop for Fast Re-Route
===============================================================================
LDP Prefix Bindings (Active)
===============================================================================
Prefix Op IngLbl EgrLbl EgrIntf/LspId EgrNextHop
-------------------------------------------------------------------------------
10.10.10.1/32 Pop 131071 -- -- --
10.10.10.2/32 Push -- 131071 1/1/2 10.1.2.2
10.10.10.2/32 Swap 131070 131071 1/1/2 10.1.2.2
10.10.10.3/32 Push -- 131071 1/1/3 10.1.3.3
10.10.10.3/32 Swap 131069 131071 1/1/3 10.1.3.3
10.10.10.4/32 Push -- 131071 1/1/4 10.1.4.4
10.10.10.4/32 Swap 131068 131071 1/1/4 10.1.4.4
10.10.10.5/32 Push -- 131071 1/1/1 10.1.5.5
10.10.10.5/32 Swap 131067 131071 1/1/1 10.1.5.5
10.10.10.6/32 Push -- 131066 1/1/2 10.1.2.2
10.10.10.6/32 Swap 131066 131066 1/1/2 10.1.2.2
10.10.10.7/32 Push -- 131065 1/1/3 10.1.3.3
10.10.10.7/32 Swap 131065 131065 1/1/3 10.1.3.3
10.10.10.8/32 Push -- 131064 1/1/4 10.1.4.4
10.10.10.8/32 Swap 131064 131064 1/1/4 10.1.4.4
-------------------------------------------------------------------------------
No. of Prefix Active Bindings: 15
===============================================================================
As can be seen in LIB output above, router R1 only performs the POP operation for its
own system address since it is the iLER for its system interface address. Router R1
performs PUSH and SWAP operations for all the other prefixes. The PUSH operation is
performed when R1 is the head-end (iLER) router for an LSP, while the SWAP operation
is performed when R1 is a LSR for an LSP.
6. Verify the LSPs that are present.

An example is shown below.
*A:MPLSv2_R1# show router tunnel-table
===============================================================================
Tunnel Table (Router: Base)
===============================================================================
Destination Owner Encap TunnelId Pref Nexthop Metric
-------------------------------------------------------------------------------
10.10.10.2/32 ldp MPLS - 9 10.1.2.2 100
10.10.10.3/32 ldp MPLS - 9 10.1.3.3 100
10.10.10.4/32 ldp MPLS - 9 10.1.4.4 100
10.10.10.5/32 ldp MPLS - 9 10.1.5.5 100
10.10.10.6/32 ldp MPLS - 9 10.1.2.2 200
10.10.10.7/32 ldp MPLS - 9 10.1.3.3 200
10.10.10.8/32 ldp MPLS - 9 10.1.4.4 200
===============================================================================
a. For which FECs has your router created LSPs?

Every routers system address.
b. What does the metric value represent for each FEC?
This corresponds to the path cost to reach the FEC based on the OSPF metrics of each
link.
7. On your CORE router, shut down the network interface leading to the diagonally connected
neighbor CORE router.
On router R1:
*A:MPLSv2_R1# configure router interface "toR4" shutdown
8. View your CORE and EDGE router LIBs. How did shutting down the interface change the LIB
contents?
===============================================================================
LDP LSR ID: 10.10.10.1
===============================================================================
===============================================================================
LDP Prefix Bindings
===============================================================================
Peer LspId
-------------------------------------------------------------------------------
10.10.10.1/32 131071U -- -- --
10.10.10.2
10.10.10.1/32 131071U -- -- --
10.10.10.3
10.10.10.1/32 131071U -- -- --
10.10.10.5
10.10.10.2/32 -- 131071 1/1/2 10.1.2.2
10.10.10.2
10.10.10.2/32 131070U 131069 -- --
10.10.10.3
10.10.10.2/32 131070U 131069 -- --
10.10.10.5
10.10.10.3/32 131069U 131069 -- --
10.10.10.2
10.10.10.3/32 -- 131071 1/1/3 10.1.3.3
10.10.10.3
10.10.10.3/32 131069U 131068 -- --
10.10.10.5
10.10.10.4/32 131068N 131068 1/1/2 10.1.2.2
10.10.10.2
10.10.10.4/32 131068U 131068 -- --
10.10.10.3
10.10.10.4/32 131068U 131062 -- --
10.10.10.5
10.10.10.5/32 131067U 131067 -- --
10.10.10.2
10.10.10.5/32 131067U 131067 -- --
10.10.10.3
10.10.10.5/32 -- 131071 1/1/1 10.1.5.5
10.10.10.5
10.10.10.6/32 131066N 131066 1/1/2 10.1.2.2
10.10.10.2
10.10.10.6/32 131066U 131066 -- --
10.10.10.3
10.10.10.6/32 131066U 131066 -- --
10.10.10.5
10.10.10.7/32 131065U 131065 -- --
10.10.10.2
10.10.10.7/32 131065N 131065 1/1/3 10.1.3.3
10.10.10.3
10.10.10.7/32 131065U 131065 -- --
10.10.10.5
10.10.10.8/32 131064N 131064 1/1/2 10.1.2.2
10.10.10.2
10.10.10.8/32 131064U 131064 -- --
10.10.10.3
10.10.10.8/32 131064U 131063 -- --
10.10.10.5
-------------------------------------------------------------------------------
===============================================================================
The LIB on the CORE router has 8 fewer prefix bindings because the router no longer
receives bindings from its diagonally connected neighbor. The LIB on the EDGE routers
does not change.
9. View your CORE and EDGE router LFIBs.
a. How did shutting down the interface change the LFIB contents?
===============================================================================
===============================================================================
===============================================================================
-------------------------------------------------------------------------------
10.10.10.1/32 Pop 131071 -- -- --
10.10.10.2/32 Push -- 131071 1/1/2 10.1.2.2
10.10.10.2/32 Swap 131070 131071 1/1/2 10.1.2.2
10.10.10.3/32 Push -- 131071 1/1/3 10.1.3.3
10.10.10.3/32 Swap 131069 131071 1/1/3 10.1.3.3
10.10.10.4/32 Push -- 131068 1/1/2 10.1.2.2
10.10.10.4/32 Swap 131068 131068 1/1/2 10.1.2.2
10.10.10.5/32 Push -- 131071 1/1/1 10.1.5.5
10.10.10.5/32 Swap 131067 131071 1/1/1 10.1.5.5
10.10.10.6/32 Push -- 131066 1/1/2 10.1.2.2
10.10.10.6/32 Swap 131066 131066 1/1/2 10.1.2.2
10.10.10.7/32 Push -- 131065 1/1/3 10.1.3.3
10.10.10.7/32 Swap 131065 131065 1/1/3 10.1.3.3
10.10.10.8/32 Push -- 131064 1/1/2 10.1.2.2
10.10.10.8/32 Swap 131064 131064 1/1/2 10.1.2.2
-------------------------------------------------------------------------------
===============================================================================
On the CORE router the active label binding used to reach the diagonally connected
neighbor pods CORE and EDGE routers have changed. The egress interface and egress
next hop for routers R4 and R8 are now 1/1/2 and 10.1.2.2, since router R2 is now the
next hop to reach routers R4 and R8.
===============================================================================
===============================================================================
===============================================================================
-------------------------------------------------------------------------------
10.10.10.1/32 Push -- 131071 1/1/1 10.1.5.1
10.10.10.2/32 Push -- 131070 1/1/1 10.1.5.1
10.10.10.2/32 Swap 131069 131070 1/1/1 10.1.5.1
10.10.10.3/32 Push -- 131069 1/1/1 10.1.5.1
10.10.10.3/32 Swap 131068 131069 1/1/1 10.1.5.1
10.10.10.4/32 Push -- 131068 1/1/1 10.1.5.1
10.10.10.4/32 Swap 131062 131068 1/1/1 10.1.5.1
10.10.10.5/32 Pop 131071 -- -- --
10.10.10.6/32 Push -- 131066 1/1/1 10.1.5.1
10.10.10.6/32 Swap 131066 131066 1/1/1 10.1.5.1
10.10.10.7/32 Push -- 131065 1/1/1 10.1.5.1
10.10.10.7/32 Swap 131065 131065 1/1/1 10.1.5.1
10.10.10.8/32 Push -- 131064 1/1/1 10.1.5.1
10.10.10.8/32 Swap 131063 131064 1/1/1 10.1.5.1
-------------------------------------------------------------------------------
===============================================================================
The LFIB on the EDGE router does not change since its next hop to reach routers R4 and
R8 is not affected by shutting down the diagonal CORE routers' link interfaces.
b. What path will packets follow when your EDGE router forwards them to the diagonally
connected EDGE router? Use the oam lsp-trace command to verify the path taken to
the diagonal EDGE router.
*A:MPLSv2_R5# oam lsp-trace prefix 10.10.10.8/32
lsp-trace to 10.10.10.8/32: 0 hops min, 0 hops max, 104 byte packets
1 10.10.10.1 rtt=0.886ms rc=8(DSRtrMatchLabel)
4 10.10.10.8 rtt=4.68ms rc=3(EgressRtr)
Packets flowing between diagonal EDGE routers will now bypass the link between the
diagonal CORE routers. For example, a packet sent from router R5 to router R8 will now
use the path R5 - R1 - R2 - R4 - R8.
c. With what label will your CORE router forward a packet sent from your EDGE router to
your diagonally connected EDGE router?
This depends on output. In the example above, router R1 uses label 131064 to forward
packets sent from router R5 to router R8.
NOTE: For the next exercise to succeed, keep the interface from your CORE router to
the diagonally connected CORE router shut down.
3.3. Enabling LDP ECMP
Figure 3-3: Enabling LDP ECMP
Exercise
1. Verify that the diagonal paths in the core are still shut down.
2. On your CORE router, enable ECMP for 4 equal cost paths.
A:MPLSv2_R1# configure router ecmp 4
3. View your CORE routers route table. What next hop does your CORE router use to reach the
diagonally connected EDGE router?
*A:MPLSv2_R1# show router route-table
===============================================================================
Route Table (Router: Base)
===============================================================================
Dest Prefix[Flags] Type Proto Age Pref
Next Hop[Interface Name] Metric
-------------------------------------------------------------------------------
10.1.2.0/27 Local Local 23h49m57s 0
toR2 0
10.1.3.0/27 Local Local 23h49m57s 0
toR3 0
10.1.5.0/27 Local Local 23h49m57s 0
toR5 0
10.2.4.0/27 Remote OSPF 23h49m40s 10
10.1.2.2 200
10.2.6.0/27 Remote OSPF 23h49m40s 10
10.1.2.2 200
10.3.4.0/27 Remote OSPF 23h49m40s 10
10.1.3.3 200
10.3.7.0/27 Remote OSPF 23h49m40s 10
10.1.3.3 200
10.4.8.0/27 Remote OSPF 00h00m52s 10
10.1.2.2 300
10.4.8.0/27 Remote OSPF 00h00m52s 10
10.1.3.3 300
10.10.10.1/32 Local Local 23h50m06s 0
system 0
10.10.10.2/32 Remote OSPF 23h46m42s 10
10.1.2.2 100
10.10.10.3/32 Remote OSPF 23h49m40s 10
10.1.3.3 100
10.10.10.4/32 Remote OSPF 00h00m52s 10
10.1.2.2 200
10.10.10.4/32 Remote OSPF 00h00m52s 10
10.1.3.3 200
10.10.10.5/32 Remote OSPF 23h46m24s 10
10.1.5.5 100
10.10.10.6/32 Remote OSPF 23h46m14s 10
10.1.2.2 200
10.10.10.7/32 Remote OSPF 23h49m32s 10
10.1.3.3 200
10.10.10.8/32 Remote OSPF 00h00m52s 10
10.1.2.2 300
10.10.10.8/32 Remote OSPF 00h00m52s 10
10.1.3.3 300
-------------------------------------------------------------------------------
No. of Routes: 19
Flags: L = LFA nexthop available B = BGP backup route available
n = Number of times nexthop is repeated
===============================================================================
The CORE router can now use either the clockwise or counter-clockwise CORE router to
reach the diagonal CORE router.
4. View your CORE and EDGE router LIBs.

===============================================================================
LDP LSR ID: 10.10.10.1
===============================================================================
===============================================================================
LDP Prefix Bindings
===============================================================================
Peer LspId
-------------------------------------------------------------------------------
10.10.10.1/32 131071U -- -- --
10.10.10.2
10.10.10.1/32 131071U -- -- --
10.10.10.3
10.10.10.1/32 131071U -- -- --
10.10.10.5
10.10.10.2/32 -- 131071 1/1/2 10.1.2.2
10.10.10.2
10.10.10.2/32 131070U 131069 -- --
10.10.10.3
10.10.10.2/32 131070U 131069 -- --
10.10.10.5
10.10.10.3/32 131069U 131069 -- --
10.10.10.2
10.10.10.3/32 -- 131071 1/1/3 10.1.3.3
10.10.10.3
10.10.10.3/32 131069U 131068 -- --
10.10.10.5
10.10.10.4/32 131068N 131068 1/1/2 10.1.2.2
10.10.10.2
10.10.10.4/32 131068N 131068 1/1/3 10.1.3.3
10.10.10.3
10.10.10.4/32 131068U 131062 -- --
10.10.10.5
10.10.10.5/32 131067U 131067 -- --
10.10.10.2
10.10.10.5/32 131067U 131067 -- --
10.10.10.3
10.10.10.5/32 -- 131071 1/1/1 10.1.5.5
10.10.10.5
10.10.10.6/32 131066N 131066 1/1/2 10.1.2.2
10.10.10.2
10.10.10.6/32 131066U 131066 -- --
10.10.10.3
10.10.10.6/32 131066U 131066 -- --
10.10.10.5
10.10.10.7/32 131065U 131065 -- --
10.10.10.2
10.10.10.7/32 131065N 131065 1/1/3 10.1.3.3
10.10.10.3
10.10.10.7/32 131065U 131065 -- --
10.10.10.5
10.10.10.8/32 131064N 131064 1/1/2 10.1.2.2
10.10.10.2
10.10.10.8/32 131064N 131064 1/1/3 10.1.3.3
10.10.10.3
10.10.10.8/32 131064U 131063 -- --
10.10.10.5
-------------------------------------------------------------------------------
===============================================================================
a. How does this differ from the LIB entries you saw before you enabled ECMP?
On the CORE router it can be seen in the LIB that the router does not use the labels it
has generated for the FEC corresponding to the diagonally connected pods CORE and
EDGE routers, and has advertised to the peer routers, which are the next hops to reach
that pod.
The LIB of the EDGE router does not change.
b. How many prefix bindings should you see in your CORE and EDGE router LIBs? Explain.
The LIB of the CORE and EDGE routers have the same number of prefix bindings as
before because the LIB contains labels received from all peers for a given FEC.
5. View the LFIBs.
===============================================================================
===============================================================================
===============================================================================
-------------------------------------------------------------------------------
10.10.10.1/32 Pop 131071 -- -- --
10.10.10.2/32 Push -- 131071 1/1/2 10.1.2.2
10.10.10.2/32 Swap 131070 131071 1/1/2 10.1.2.2
10.10.10.3/32 Push -- 131071 1/1/3 10.1.3.3
10.10.10.3/32 Swap 131069 131071 1/1/3 10.1.3.3
10.10.10.4/32 Push -- 131068 1/1/2 10.1.2.2
10.10.10.4/32 Push -- 131068 1/1/3 10.1.3.3
10.10.10.4/32 Swap 131068 131068 1/1/2 10.1.2.2
10.10.10.4/32 Swap 131068 131068 1/1/3 10.1.3.3
10.10.10.5/32 Push -- 131071 1/1/1 10.1.5.5
10.10.10.5/32 Swap 131067 131071 1/1/1 10.1.5.5
10.10.10.6/32 Push -- 131066 1/1/2 10.1.2.2
10.10.10.6/32 Swap 131066 131066 1/1/2 10.1.2.2
10.10.10.7/32 Push -- 131065 1/1/3 10.1.3.3
10.10.10.7/32 Swap 131065 131065 1/1/3 10.1.3.3
10.10.10.8/32 Push -- 131064 1/1/2 10.1.2.2
10.10.10.8/32 Push -- 131064 1/1/3 10.1.3.3
10.10.10.8/32 Swap 131064 131064 1/1/2 10.1.2.2
10.10.10.8/32 Swap 131064 131064 1/1/3 10.1.3.3
-------------------------------------------------------------------------------
===============================================================================
a. How does this differ from the LFIB entries you saw before you enabled ECMP?
The LFIB of the CORE router now has two additional entries for the FECs corresponding
to the diagonally connected pods CORE and EDGE routers.
The LFIB of the EDGE router does not change.
b. How many equal cost LSPs originate on your CORE router and terminate on the diagonally
connected EDGE router?
2
6. View all the LSPs present on your CORE and EDGE routers.
*A:MPLSv2_R1# show router tunnel-table
===============================================================================
Tunnel Table (Router: Base)
===============================================================================
Destination Owner Encap TunnelId Pref Nexthop Metric
-------------------------------------------------------------------------------
10.10.10.2/32 ldp MPLS - 9 10.1.2.2 100
10.10.10.3/32 ldp MPLS - 9 10.1.3.3 100
10.10.10.4/32 ldp MPLS - 9 10.1.2.2 200
10.10.10.4/32 ldp MPLS - 9 10.1.3.3 200
10.10.10.5/32 ldp MPLS - 9 10.1.5.5 100
10.10.10.6/32 ldp MPLS - 9 10.1.2.2 200
10.10.10.7/32 ldp MPLS - 9 10.1.3.3 200
10.10.10.8/32 ldp MPLS - 9 10.1.2.2 300
10.10.10.8/32 ldp MPLS - 9 10.1.3.3 300
===============================================================================
a. How many LSPs do you see connecting your routers to the diagonally connected pods
CORE and EDGE routers?
Two each.
b. How many LSPs do you see connecting your routers to all other routers?
One each.
7. NOTE: This step is beyond the scope of the course. The tool introduced becomes useful in the
scenario where multiple LDP paths are available to the destination. On the CORE router, run
an oam ldp-treetrace prefix to the diagonally connected neighbors CORE routers
system address and edge router's system address. You can see the multiple LDP paths to the
destination.
*A:MPLSv2_R1# oam ldp-treetrace prefix 10.10.10.4/32
ldp-treetrace for Prefix 10.10.10.4/32:
10.3.4.4, ttl = 2 dst = 127.2.0.255 rc = EgressRtr status = Done

Hops: 10.1.3.3

Hops: 10.1.2.2
ldp-treetrace discovery state: Done

ldp-treetrace discovery status: ' OK '
Total number of discovered paths: 2
Total number of failed traces: 0
*A:MPLSv2_R1# oam ldp-treetrace prefix 10.10.10.8/32
ldp-treetrace for Prefix 10.10.10.8/32:

Hops: 10.2.4.4 10.1.2.2

Hops: 10.3.4.4 10.1.3.3
ldp-treetrace discovery state: Done

ldp-treetrace discovery status: ' OK '
Total number of discovered paths: 2
Total number of failed traces: 0
3.4. Applying Export Policy for Label Distribution
Figure 3-4: Applying Export Policy for Label Distribution
Exercise
1. Turn up the core interfaces using the no shutdown command and disable ECMP using
configure router no ecmp.
2. Configure an Export policy with a single entry set to action accept.
*A:MPLSv2_R1# configure router policy-options

*A:MPLSv2_R1>config>router>policy-options# begin
*A:MPLSv2_R1>config>router>policy-options# policy-statement ldp-export
*A:MPLSv2_R1>config>router>policy-options>policy-statement$ entry 10
*A:MPLSv2_R1>config>router>policy-options>policy-statement>entry$ action accept
*A:MPLSv2_R1>config>router>policy-options>policy-statement>entry>action$ back
*A:MPLSv2_R1>config>router>policy-options>policy-statement>entry$ back
*A:MPLSv2_R1>config>router>policy-options>policy-statement$ back
*A:MPLSv2_R1>config>router>policy-options# commit
*A:MPLSv2_R1>config>router>policy-options# exit all
3. Apply the Export policy to your CORE and EDGE routers LDP instances.
*A:MPLSv2_R1# configure router ldp export "ldp-export"
4. View the LIBs.
An example is shown below, truncated for clarity.
===============================================================================
LDP LSR ID: 10.10.10.1
===============================================================================
===============================================================================
LDP Prefix Bindings
===============================================================================
Peer LspId
-------------------------------------------------------------------------------
10.1.2.0/27 131064U 131064 -- --
10.10.10.2
10.1.2.0/27 131064U 131064 -- --
10.10.10.3
10.1.2.0/27 131064U 131055 -- --
10.10.10.4
10.1.2.0/27 131064U 131063 -- --
10.10.10.5
10.1.3.0/27 131071U 131071 -- --
10.10.10.2
10.1.3.0/27 131071U 131071 -- --
10.10.10.3
10.1.3.0/27 131071U 131071 -- --
10.10.10.4
10.1.3.0/27 131071U 131062 -- --
10.10.10.5
10.1.4.0/27 131067U 131068 -- --
10.10.10.2
10.1.4.0/27 131067U 131067 -- --
10.10.10.3
10.1.4.0/27 131067U 131068 -- --
10.10.10.4
10.1.4.0/27 131067U 131055 -- --
10.10.10.5
10.1.5.0/27 131054U 131054 -- --
10.10.10.2
10.1.5.0/27 131054U 131054 -- --
10.10.10.3
10.1.5.0/27 131054U 131054 -- --
10.10.10.4
10.1.5.0/27 131054U 131054 -- --
10.10.10.5
10.2.3.0/27 131070N 131065 1/1/2 10.1.2.2
10.10.10.2
10.2.3.0/27 131070U 131070 -- --
10.10.10.3
10.2.3.0/27 131070U 131065 -- --
10.10.10.4
10.2.3.0/27 131070U 131068 -- --
10.10.10.5
10.2.4.0/27 131065N 131067 1/1/2 10.1.2.2
10.10.10.2
10.2.4.0/27 131065U 131066 -- --
10.10.10.3
10.2.4.0/27 131065U 131067 -- --
10.10.10.4
10.2.4.0/27 131065U 131066 -- --
10.10.10.5
10.2.6.0/27 131055N 131055 1/1/2 10.1.2.2
10.10.10.2
10.2.6.0/27 131055U 131055 -- --
10.10.10.3
10.2.6.0/27 131055U 131064 -- --
10.10.10.4
10.2.6.0/27 131055U 131065 -- --
10.10.10.5
10.3.4.0/27 131069U 131070 -- --
10.10.10.2
10.3.4.0/27 131069N 131069 1/1/3 10.1.3.3
10.10.10.3
10.3.4.0/27 131069U 131070 -- --
10.10.10.4
10.3.4.0/27 131069U 131071 -- --
10.10.10.5
10.3.7.0/27 131068U 131069 -- --
10.10.10.2
10.3.7.0/27 131068N 131068 1/1/3 10.1.3.3
10.10.10.3
10.3.7.0/27 131068U 131069 -- --
10.10.10.4
10.3.7.0/27 131068U 131070 -- --
10.10.10.5
10.4.8.0/27 131066U 131066 -- --
10.10.10.2
10.4.8.0/27 131066U 131065 -- --
10.10.10.3
10.4.8.0/27 131066N 131066 1/1/4 10.1.4.4
10.10.10.4
10.4.8.0/27 131066U 131069 -- --
10.10.10.5
10.5.9.0/27 -- 131053 -- --
10.10.10.5

-------------------------------------------------------------------------------
===============================================================================
a. What additional FECs do your routers now generate labels for?

With the export policy, all routers now generate labels for all their directly connected
interfaces.
b. How many prefix bindings do you expect to see? Explain.
There should be 10 additional prefix bindings one for each link between the routers.
c. On your CORE routers, why do you see a prefix binding for your pods EDGE to the CE
interface? Does this prefix appear in the other CORE router LIBs? Why?
According to the policy, the EDGE router generates a label for all local networks. The
CORE router accepts this label and places it in its LIB. However, since the CORE router
has no route to the interface between the EDGE and CE routers (since it is not
advertised into OSPF), it will not place this network in its LFIB, and will not send a label
to its peers (as you will see in the next step).
5. View the LFIBs.
===============================================================================
===============================================================================
===============================================================================
-------------------------------------------------------------------------------
10.1.2.0/27 Pop 131064 -- -- --
10.1.3.0/27 Pop 131071 -- -- --
10.1.4.0/27 Pop 131067 -- -- --
10.1.5.0/27 Pop 131054 -- -- --
10.2.3.0/27 Swap 131070 131065 1/1/2 10.1.2.2
10.2.4.0/27 Swap 131065 131067 1/1/2 10.1.2.2
10.2.6.0/27 Swap 131055 131055 1/1/2 10.1.2.2
10.3.4.0/27 Swap 131069 131069 1/1/3 10.1.3.3
10.3.7.0/27 Swap 131068 131068 1/1/3 10.1.3.3
10.4.8.0/27 Swap 131066 131066 1/1/4 10.1.4.4
10.10.10.1/32 Pop 131063 -- -- --
10.10.10.2/32 Push -- 131063 1/1/2 10.1.2.2
10.10.10.2/32 Swap 131060 131063 1/1/2 10.1.2.2
10.10.10.3/32 Push -- 131063 1/1/3 10.1.3.3
10.10.10.3/32 Swap 131062 131063 1/1/3 10.1.3.3
10.10.10.4/32 Push -- 131063 1/1/4 10.1.4.4
10.10.10.4/32 Swap 131059 131063 1/1/4 10.1.4.4
10.10.10.5/32 Push -- 131067 1/1/1 10.1.5.5
10.10.10.5/32 Swap 131061 131067 1/1/1 10.1.5.5
10.10.10.6/32 Push -- 131058 1/1/2 10.1.2.2
10.10.10.6/32 Swap 131058 131058 1/1/2 10.1.2.2
10.10.10.7/32 Push -- 131057 1/1/3 10.1.3.3
10.10.10.7/32 Swap 131056 131057 1/1/3 10.1.3.3
10.10.10.8/32 Push -- 131061 1/1/4 10.1.4.4
10.10.10.8/32 Swap 131057 131061 1/1/4 10.1.4.4
-------------------------------------------------------------------------------
===============================================================================
Lab 3 Review Questions

1. Under normal circumstances, over what paths do the EDGE routers route traffic between
each other? Issue a traceroute between EDGE routers to verify these paths. Do you have
alternate paths available?
Through their respective CORE routers and over the direct links between the pods.
2. What router serves as the next hop between your CORE router and router R5?
Router R1
3. What metric value does OSPF assign to each link?
100 by default since all ports in this lab topology are 1 Gb ports. The default bandwidth
reference in OSPF is 100 Gb, which translates to a metric of 100 Gb/1 Gb= 100
(reference bandwidth divided by the port bandwidth).
4. Which command may be used to view the details of each LDP peer?
The show router ldp session detail command may be used to view the details
of each LDP peer.
5. For which FECs are labels advertised by default? How can additional FECs be advertised?
By default, a 7750 SR only advertises labels for its own system interface. An export
policy is needed to advertise labels for other FECs in the routing table.
6. How does a router determine which LSP to use when ECMP LDP is enabled?
The LSP used to forward traffic is based on a hashing algorithm.
Lab 4 IGP-based RSVP LSP Establishment
Objective
In this lab we will build loose hop, IGP-based LSPs, using RSVP signaling. We will use the routers OAM
tools to verify the LSPs operation and path.
Figure 4-1: IGP based LSPs

Syntax
Table 4-1 provides the configuration and verification commands required for this lab. Each command
may require additional parameters other than those shown in the table. Use the ? character for
help and to explore all command line options. In addition to the commands shown, you may need to
use commands learned in previous courses.
Lab 4 Command List
A:MPLS_R1# configure router mpls no shutdown

A:MPLS_R1# configure router rsvp no shutdown
A:MPLS_R1# configure router mpls path <path-name>
A:MPLS_R1# configure router mpls lsp <lsp-name>
A:MPLS_R1# configure router mpls lsp <lsp-name> to <system-id>
A:MPLS_R1# show router mpls path
A:MPLS_R1# show router mpls lsp [detail]
A:MPLS_R1# show router mpls lsp <lsp-name> path detail
A:MPLS_R1# show router ospf area detail
A:MPLS_R1# show router rsvp session
A:MPLS_R1# show router rsvp interface detail
A:MPLS_R1# tools perform router mpls cspf to <ip-address> [from <ip-addr>]
[bandwidth <bandwidth>] [include-bitmap <bitmap>] [exclude-bitmap <bitmap>]
[hop-limit <limit>] [exclude-address <excl-addr> [<excl-addr>...(up to 8
max)]]
A:MPLS_R1# oam lsp-ping lsp <lsp-name>
A:MPLS_R1# oam lsp-trace lsp <lsp-name>
A:MPLS_R1>..# info (from all contexts)
A:MPLS_R1>..# exit [all] (from all contexts)
A:MPLS_R1# admin save <file-name>
Exercise
1. Enable MPLS for all interfaces on your CORE and EDGE routers (excluding the interfaces to
the CUSTOMER EDGE routers, R9 to R12). Remember to globally turn up both MPLS and RSVP,
as SR OS shuts both down by default.
The configuration on router R1 is shown below.
*A:MPLSv2_R1>config>router>mpls# info
----------------------------------------------
interface "system"
no shutdown
exit
interface "toR2"
no shutdown
exit
interface "toR3"
no shutdown
exit
interface "toR4"
no shutdown
exit
interface "toR5"
no shutdown
exit
no shutdown
*A:MPLSv2_R1>config>router>rsvp# info
----------------------------------------------
interface "system"
no shutdown
exit
interface "toR2"
no shutdown
exit
interface "toR3"
no shutdown
exit
interface "toR4"
no shutdown
exit
interface "toR5"
no shutdown
exit
no shutdown
----------------------------------------------
2. Verify that MPLS is enabled on your interfaces and that the relevant interfaces are
administratively and operationally up.
*A:MPLSv2_R1# show router mpls interface
===============================================================================
MPLS Interfaces
===============================================================================
Interface Port-id Adm Opr TE-metric
-------------------------------------------------------------------------------
system system Up Up None
Admin Groups None
Srlg Groups None
toR2 1/1/2 Up Up None
Admin Groups None
Srlg Groups None
Admin Groups None
Srlg Groups None
Admin Groups None
Srlg Groups None
Admin Groups None
Srlg Groups None
-------------------------------------------------------------------------------
Interfaces : 5
===============================================================================
3. Verify that RSVP is enabled on your interfaces.

*A:MPLSv2_R1# show router rsvp interface
===============================================================================
RSVP Interfaces
===============================================================================
Interface Total Active Total BW Resv BW Adm Opr
Sessions Sessions (Mbps) (Mbps)
-------------------------------------------------------------------------------
system - - - - Up Up
toR2 0 0 1000 0 Up Up
toR3 0 0 1000 0 Up Up
toR4 0 0 1000 0 Up Up
toR5 0 0 1000 0 Up Up
-------------------------------------------------------------------------------
Interfaces : 5
===============================================================================
4. On both your CORE and EDGE routers, configure a path named loose and do not specify any
hops (that is, make it totally loose).
The configuration below is for router R1.
----------------------------------------------
path "loose"
no shutdown
exit
----------------------------------------------
5. On your CORE router, configure an LSP "toRx-1" to your EDGE router, where "x" is the number
of your EDGE router. Use the loose path you created in step 4 as the primary path.
----------------------------------------------
lsp "toR5-1"
to 10.10.10.5
primary "loose"
exit
no shutdown
exit
----------------------------------------------
6. On your EDGE router, configure an LSP "toRx-1" to your CORE router, using the loose path as
the primary path.
----------------------------------------------
lsp "toR1-1"
to 10.10.10.1
primary "loose"
exit
no shutdown
exit
----------------------------------------------
7. Verify each routers LSPs operational state, using the show router mpls lsp command.
*A:MPLSv2_R1# show router mpls lsp
===============================================================================
MPLS LSPs (Originating)
===============================================================================
LSP Name To Tun Fastfail Adm Opr
Id Config
-------------------------------------------------------------------------------
toR5-1 10.10.10.5 1 No Up Up
-------------------------------------------------------------------------------
LSPs : 1
-------------------------------------------------------------------------------
8. Use the show router rsvp session command to obtain the LSPs full names. The full
LSP name takes the form lsp-name::path-name. Also note the LSPs tunnel and LSP IDs.
An example is shown on the following page.
*A:MPLSv2_R1# show router rsvp session
===============================================================================
RSVP Sessions
===============================================================================
From To Tunnel LSP Name State
ID ID
-------------------------------------------------------------------------------
10.10.10.1 10.10.10.5 1 37394 toR5-1::loose Up
10.10.10.5 10.10.10.1 1 14848 toR1-1::loose Up
-------------------------------------------------------------------------------
Sessions : 2
===============================================================================
9. Configure another LSP from your EDGE router to the clockwise pods EDGE router, again using
the loose path you created in step 4.
----------------------------------------------
lsp "toR6-1"
to 10.10.10.6
primary "loose"
exit
no shutdown
exit
----------------------------------------------
a. Can the new LSP use the same path as the first you configured?
Yes, the path does not terminate on any specific node or interface.
b. Over what path will your router signal this LSP?
Over an IGP-based path. An LSP with a fully loose path follows the IGP shortest path.
c. What determines the path that the head-end router uses to signal this LSP path?
FIB entry for target prefix.
10. Verify the LSPs operation and paths using the oam lsp-ping <lsp-name> and oam lsp-
trace <lsp-name> commands.
Examples are shown below.
*A:MPLSv2_R1# oam lsp-ping "toR5-1"
LSP-PING toR5-1: 92 bytes MPLS payload
Seq=1, send from intf toR5, reply from 10.10.10.5
udp-data-len=32 ttl=255 rtt=1.10ms rc=3 (EgressRtr)
---- LSP toR5-1 PING Statistics ----

1 packets sent, 1 packets received, 0.00% packet loss
round-trip min = 1.10ms, avg = 1.10ms, max = 1.10ms, stddev = 0.000ms
*A:MPLSv2_R1# oam lsp-trace "toR5-1"

lsp-trace to toR5-1: 0 hops min, 0 hops max, 116 byte packets
10.10.10.5 rtt=1.38ms rc=3(EgressRtr)
*A:MPLSv2_R5# oam lsp-ping "toR6-1"
LSP-PING toR6-1: 92 bytes MPLS payload
Seq=1, send from intf toR1, reply from 10.10.10.6
udp-data-len=32 ttl=255 rtt=2.62ms rc=3 (EgressRtr)
---- LSP toR6-1 PING Statistics ----
1 packets sent, 1 packets received, 0.00% packet loss
round-trip min = 2.62ms, avg = 2.62ms, max = 2.62ms, stddev = 0.000ms

1. Over what path does traffic travel when the head-end router forwards it toward the LSPs
tail-end?
The head-end router forwards packets over the FIBs best path toward the LSPs tail-
end.
2. Can the head-end router recover the LSP if a failure occurs on the primary path?
Yes, if the IGP can find a path to the tail-end network, then the head-end can resignal
the LSP on a new path.
3. What must be in place in the network before the head-end router can signal the LSP
requirements to the tail-end?
An IGP path must be in place to the target tail-end. This could be a static or dynamic
route, though dynamic routes allow the network to recover from outages without
operator intervention.
Lab 5 Enabling RSVP-TE LSP Tunnels
Objective
In this lab, we will use link coloring techniques to build constraint-based LSPs. Then, we will configure
RSVP-TE support over multiple OSPF areas, using LDP over RSVP for multi-area forwarding. Finally, we
will build RSVP-TE signaled LSPs for tunneling IGP routed traffic from edge-to-edge.
Lab 5 Command list
A:MPLS_R1# configure router interface shutdown

A:MPLS_R1# configure router interface no shutdown
A:MPLS_R1# configure router ldp targeted-session peer <peer-ip> tunneling
A:MPLS_R1# configure router mpls admin-group <group-name> <group-value>
A:MPLS_R1# configure router mpls interface <interface-name>
A:MPLS_R1# configure router mpls interface <interface-name> admin-group
<group-name>
A:MPLS_R1# configure router mpls interface <interface-name> srlg-group <group-
name>
A:MPLS_R1# configure router mpls lsp <lsp-name> cspf
A:MPLS_R1# configure router mpls lsp <lsp-name> no igp-shortcut
A:MPLS_R1# configure router mpls lsp <lsp-name> path <path-name> include
<group-name> exclude <group-name>
A:MPLS_R1# configure router mpls lsp <lsp-name> primary <path-name>
A:MPLS_R1# configure router mpls lsp <lsp-name> secondary <path-name>
A:MPLS_R1# configure router mpls lsp <lsp-name> secondary <path-name> srlg
A:MPLS_R1# configure router mpls lsp <lsp-name> secondary <path-name> standby
A:MPLS_R1# configure router mpls path <path-name> hop <index> [strict | loose]
A:MPLS_R1# configure router mpls srlg-group <group-name> value <group-value>
A:MPLS_R1# configure router ospf area <area-id> interface <interface-name>
interface-type point-to-point
A:MPLS_R1# configure router ospf ldp-over-rsvp
A:MPLS_R1# configure router ospf rsvp-shortcut

A:MPLS_R1# configure router ospf traffic-engineering
A:MPLS_R1# configure router rsvp no shutdown
A:MPLS_R1# show router mpls lsp terminate detail
A:MPLS_R1# show router mpls lsp transit detail
A:MPLS_R1# show router rsvp session
A:MPLS_R1# show router ospf opaque-database
A:MPLS_R1# show router ospf opaque-database adv-router <router-id> detail
A:MPLS_R1# tools dump router ospf route-table <prefix> detail
5.1. Configure Link Coloring for Constraint-Based LSP Tunnels
Figure 5-1: Enabling Link Coloring Constraint-Based LSP Tunnels
Exercise
In this exercise, you will enableTtraffic Engineering and CSPF on LSPs, connecting your CORE router to
the clockwise CORE router. You will create two admin groups, red and green, to assign each of your
core interfaces to the appropriate admin group. On your LSPs, you will include green and exclude red
links, and observe the LSPs behavior as you shut down the direct links between the core routers.
Phase I Enable and verify CSPF

1. On both of your routers, use the show router ospf status command to verify that Traffic
Engineering is currently disabled.
A:MPLSv2_R1# show router ospf status
===============================================================================
OSPF Status
===============================================================================
OSPF Cfg Router Id : 0.0.0.0
OSPF Oper Router Id : 10.10.10.1
OSPF Version : 2
OSPF Admin Status : Enabled
OSPF Oper Status : Enabled
Graceful Restart : Disabled
GR Helper Mode : Disabled
Preference : 10
External Preference : 150
Backbone Router : True
Area Border Router : False
AS Border Router : False
Opaque LSA Support : True
Traffic Engineering Support : False
RFC 1583 Compatible : True
Demand Exts Support : False
In Overload State : False
In External Overflow State : False
Exit Overflow Interval : 0
Last Overflow Entered : Never
Last Overflow Exit : Never
External LSA Limit : -1
Reference Bandwidth : 100,000,000 Kbps
Init SPF Delay : 1000 msec
Sec SPF Delay : 1000 msec
Max SPF Delay : 10000 msec
Min LS Arrival Interval : 1000 msec
Init LSA Gen Delay : 5000 msec
Sec LSA Gen Delay : 5000 msec
Max LSA Gen Delay : 5000 msec
Last Ext SPF Run : Never
Ext LSA Cksum Sum : 0x0
OSPF Last Enabled : 04/01/2015 10:39:50
Unicast Import : True
Multicast Import : False
Export Policies : None
Import Policies : None
OSPF Ldp Sync Admin Status : Enabled
LDP-over-RSVP : Disabled
RSVP-Shortcut : Disabled
Advertise-Tunnel-Link : Disabled
LFA : Disabled
Export Limit : 0
Export Limit Log Percent : 0
Total Exp Routes : 0
===============================================================================
a. Do your routers support opaque LSAs by default?
Yes
b. Why do your routers support opaque LSAs, though TE support is disabled?
RFCs require all TE-capable routers support opaque LSAs.
2. Verify that your routers opaque database is empty. View the opaque database on your CORE
router.
Note: If others have already enabled TE on their routers, you may see opaque LSAs in your routers
opaque databases.
A:MPLSv2_R1# 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
===============================================================================
3. View the number of Type 10 Area Opaque LSAs on your CORE router.
A:MPLSv2_R1# show router ospf area 0 detail
===============================================================================
OSPF Area (Detailed) : 0.0.0.0
===============================================================================
-------------------------------------------------------------------------------
Configuration
-------------------------------------------------------------------------------
Area Id : 0.0.0.0 Type : Standard
Key Rollover Int.: 10 LFA : Include
-------------------------------------------------------------------------------
Statistics
-------------------------------------------------------------------------------
Virtual Links : 0 Total Nbrs : 4
Active IFs : 5 Total IFs : 5
Area Bdr Rtrs : 0 AS Bdr Rtrs : 0
SPF Runs : 29 Last SPF Run : 04/02/2015 14:03:44
Router LSAs : 8 Network LSAs : 0
Summary LSAs : 0 Asbr-summ LSAs : 0
Nssa ext LSAs : 0 Area opaque LSAs : 0
Total LSAs : 8 LSA Cksum Sum : 0x28459
Blackhole Range : True Unknown LSAs : 0
===============================================================================
a. How many Type 10 LSAs do your routers report?

0
b. Why would your router report Type 10 LSAs if you have not yet enabled TE?
You would see Type 10 LSAs on your router if someone has already enabled TE on their
router. Once you enable TE on the router, it sends out the router address top-level TLV to
all adjacent routers within its area.
4. For now, enable Traffic Engineering only on your EDGE router.
A:MPLSv2_R5# configure router ospf traffic-engineering
5. Again, view the number of Type 10 Area opaque LSAs on your CORE router.
An example output is shown below.
A:MPLSv2_R1# show router ospf area 0 detail
===============================================================================
OSPF Area (Detailed) : 0.0.0.0
===============================================================================
-------------------------------------------------------------------------------
Configuration
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
Statistics
-------------------------------------------------------------------------------
Total LSAs : 16 LSA Cksum Sum : 0x4dce4
===============================================================================
a. How many Type 10 LSAs do you see?
Eight; each EDGE router sends two Type 10 LSAs: one for its system interface and one for
the interface connecting it to the CORE router.
b. Why has this value increased even though you have not enabled TE on this router?
Your CORE router still receives Type 10 LSAs from all EDGE routers in the OSPF area.
6. Enable Traffic Engineering on your CORE router. Confirm that Traffic Engineering is now
enabled.
A:MPLSv2_R1# configure router ospf traffic-engineering
*A:MPLSv2_R1# show router ospf status
===============================================================================
OSPF Status
===============================================================================
OSPF Version : 2
Preference : 10
Traffic Engineering Support : True
LFA : Disabled
Export Limit : 0
===============================================================================
7. Verify that your CORE router now has opaque LSAs in the database.
*A:MPLSv2_R1# 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.1 292 0x80000001 0x12fe
Area 0.0.0.0 1.0.0.2 10.10.10.1 292 0x80000001 0x81ca
Area 0.0.0.0 1.0.0.3 10.10.10.1 292 0x80000001 0xf551
Area 0.0.0.0 1.0.0.4 10.10.10.1 292 0x80000001 0x6ad7
Area 0.0.0.0 1.0.0.5 10.10.10.1 292 0x80000001 0xde5e
Area 0.0.0.0 1.0.0.1 10.10.10.2 293 0x80000001 0x16f8
Area 0.0.0.0 1.0.0.2 10.10.10.2 215 0x80000002 0x5bef
Area 0.0.0.0 1.0.0.3 10.10.10.2 215 0x80000002 0x4cf5
Area 0.0.0.0 1.0.0.4 10.10.10.2 215 0x80000002 0xc07c
Area 0.0.0.0 1.0.0.5 10.10.10.2 215 0x80000002 0xb380
Area 0.0.0.0 1.0.0.1 10.10.10.3 293 0x80000001 0x1af2
Area 0.0.0.0 1.0.0.2 10.10.10.3 293 0x80000001 0xb790
Area 0.0.0.0 1.0.0.3 10.10.10.3 293 0x80000001 0x2a19
Area 0.0.0.0 1.0.0.4 10.10.10.3 293 0x80000001 0x1b1f
Area 0.0.0.0 1.0.0.5 10.10.10.3 293 0x80000001 0x8ca0
Area 0.0.0.0 1.0.0.1 10.10.10.4 293 0x80000001 0x1eec
Area 0.0.0.0 1.0.0.2 10.10.10.4 201 0x80000002 0x1033
Area 0.0.0.0 1.0.0.3 10.10.10.4 201 0x80000002 0x82bb
Area 0.0.0.0 1.0.0.4 10.10.10.4 201 0x80000002 0xf444
Area 0.0.0.0 1.0.0.5 10.10.10.4 201 0x80000002 0x61c2
Area 0.0.0.0 1.0.0.1 10.10.10.5 1176 0x80000001 0x22e6
Area 0.0.0.0 1.0.0.2 10.10.10.5 1041 0x80000002 0x6ad4
Area 0.0.0.0 1.0.0.1 10.10.10.6 1161 0x80000001 0x26e0
Area 0.0.0.0 1.0.0.2 10.10.10.6 362 0x80000002 0x41f5
Area 0.0.0.0 1.0.0.1 10.10.10.7 1154 0x80000001 0x2ada
Area 0.0.0.0 1.0.0.2 10.10.10.7 207 0x80000002 0x1817
Area 0.0.0.0 1.0.0.1 10.10.10.8 1149 0x80000001 0x2ed4
Area 0.0.0.0 1.0.0.2 10.10.10.8 56 0x80000002 0xee38
-------------------------------------------------------------------------------
No. of Opaque LSAs: 28
===============================================================================
8. On your CORE router, use the show router ospf opaque-database adv-router
<router-id> detail command, where <router-id> belongs to your CORE router, for a more
detailed description of the opaque LSA for your router.
*A:MPLSv2_R1# show router ospf opaque-database adv-router 10.10.10.1 detail
===============================================================================
OSPF Opaque Link State Database (Type : All) (Detailed)
===============================================================================
-------------------------------------------------------------------------------
Opaque LSA
-------------------------------------------------------------------------------
Area Id : 0.0.0.0 Adv Router Id : 10.10.10.1
Link State Id : 1.0.0.1 LSA Type : Area Opaque
Sequence No : 0x80000001 Checksum : 0x12fe
Age : 392 Length : 28
Options : E
Advertisement :
ROUTER-ID TLV (0001) Len 4 : 10.10.10.1
-------------------------------------------------------------------------------
Opaque LSA
-------------------------------------------------------------------------------
Sequence No : 0x80000001 Checksum : 0x81ca
Options : E
Advertisement :
LINK INFO TLV (0002) Len 100 :
Sub-TLV: 1 Len: 1 LINK_TYPE : 1
Sub-TLV: 2 Len: 4 LINK_ID : 10.10.10.2
Sub-TLV: 3 Len: 4 LOC_IP_ADDR : 10.1.2.1
Sub-TLV: 4 Len: 4 REM_IP_ADDR : 10.1.2.2
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
Sub-TLV: 9 Len: 4 ADMIN_GROUP : 0 None
-------------------------------------------------------------------------------
Opaque LSA
-------------------------------------------------------------------------------
Sequence No : 0x80000001 Checksum : 0xf551
Options : E
Advertisement :
-------------------------------------------------------------------------------
Opaque LSA
-------------------------------------------------------------------------------
Sequence No : 0x80000001 Checksum : 0x6ad7
Options : E
Advertisement :
-------------------------------------------------------------------------------
Opaque LSA
-------------------------------------------------------------------------------
Sequence No : 0x80000001 Checksum : 0xde5e
Options : E
Advertisement :
===============================================================================
a. Why do you not see opaque LSAs generated by the other routers?
You chose to only view the opaque LSAs your router advertises.
b. Why is 0.0.0.0 the Area ID shown?
There is only one area configured in this network topology, which is a backbone area.
Opaque LSAs only flood within the area in which the routers have generated them.
c. Which top-level TLV sub-types do the LSAs contain, and what do they specify?
Router-ID TLV and Link Info TLV. Router ID TLV advertises the routers router ID, and Link
Info TLV advertises the link attributes, such as admin group membership and available
bandwidth.
9. Again, verify the number of Type 10 Area opaque LSAs now discovered.
*A:MPLSv2_R1# show router ospf area detail
===============================================================================
OSPF Areas (Detailed)
===============================================================================
-------------------------------------------------------------------------------
Area Id: 0.0.0.0
-------------------------------------------------------------------------------
Total LSAs : 36 LSA Cksum Sum : 0xd7751
===============================================================================
a. Write down the number of Type 10 LSAs now reported.
28
b. How many Type 10 LSAs should be discovered when everyone in the class has finished
enabling Traffic Engineering?
28 two from each EDGE router: one for the system interface (Router-ID TLV) and one for
the link with the CORE router (Link info TLV), and five from each CORE router: one for the
system interface (Router-ID TLV) and 4 for the links with the other 3 CORE routers and the
EDGE router (Link info TLV) .
Phase II Configure link coloring
1. On your CORE routers, configure two administrative groups: one called green with a group
value of 1, the other called red with a group value of 2. Assign group green to all CORE outer
ring MPLS interfaces, and assign groups green and red to the diagonally CORE interfaces.
For example: If you work with router R1, assign the interfaces toR2 and toR3 to the green
group, and the interface toR4 to both the green and the red group. See Figure 5-1 for
clarification.
----------------------------------------------
admin-group "green" 1
admin-group "red" 2
interface "system"
no shutdown
exit
interface "toR2"
admin-group "green"
no shutdown
exit
interface "toR3"
admin-group "green"
no shutdown
exit
interface "toR4"
admin-group "green"
admin-group "red"
no shutdown
exit
interface "toR5"
no shutdown
exit
no shutdown
----------------------------------------------
2. Verify that the admin groups are on your CORE router, and that you have applied them to the
correct interfaces.
*A:MPLSv2_R1# show router mpls admin-group
==================================================
MPLS Administrative Groups
==================================================
Group Name Group Value
--------------------------------------------------
green 1
red 2
--------------------------------------------------
No. of Groups: 2
==================================================
*A:MPLSv2_R1# show router mpls interface
===============================================================================
MPLS Interfaces
===============================================================================
Interface Port-id Adm Opr TE-metric
-------------------------------------------------------------------------------
system system Up Up None
Admin Groups None
Srlg Groups None
Admin Groups green
Srlg Groups None
Admin Groups green
Srlg Groups None
Admin Groups green
red
Srlg Groups None
Admin Groups None
Srlg Groups None
-------------------------------------------------------------------------------
Interfaces : 5
===============================================================================
3. On your CORE router, use the show router ospf opaque-database adv-router
<router-id> detail command, where <router-id> is the router ID of your CORE router, for
a more detailed description of the opaque LSAs for your router.
===============================================================================
===============================================================================
-------------------------------------------------------------------------------
Opaque LSA
-------------------------------------------------------------------------------
Sequence No : 0x80000002 Checksum : 0x10ff
Options : E
Advertisement :
ROUTER-ID TLV (0001) Len 4 : 10.10.10.1
-------------------------------------------------------------------------------
Opaque LSA
-------------------------------------------------------------------------------
Sequence No : 0x80000003 Checksum : 0x52f5
Options : E
Advertisement :
Sub-TLV: 9 Len: 4 ADMIN_GROUP : 00000002 (2)
-------------------------------------------------------------------------------
Opaque LSA
-------------------------------------------------------------------------------
Sequence No : 0x80000003 Checksum : 0xc67c
Options : E
Advertisement :
-------------------------------------------------------------------------------
Opaque LSA
-------------------------------------------------------------------------------
Sequence No : 0x80000003 Checksum : 0xe455
Options : E
Advertisement :
-------------------------------------------------------------------------------
Opaque LSA
-------------------------------------------------------------------------------
Sequence No : 0x80000003 Checksum : 0xda60
Options : E
Advertisement :
===============================================================================
a. Why are the ADMIN_GROUP values shown not equal to the admin group values you set in
the configure router mlps admin-group command?
The show command converts the Admin_Group sub-TLV bit position to a decimal value.
For example, admin group 1 becomes decimal 2 because the router sets the 1-bit position
in the sub-TLV, which, when converted to decimal, equals 2 (10 binary = 2 decimal).
b. Which ADMIN_GROUP value represents the green group? Which value represents the red and
green groups?
Value 2 represents the green group; value 6 represents the red andgreen groups.
c. Why do you see all bandwidth available on the links?
You have not reserved any bandwidth.
Admin-group mapping to bitmap table:
31 28 27 24 23 20 19 16 15 12 11 8 7 4 3 0
0 00 0 0 00 0 0 00 0 0 00 0 0 00 0 0 00 0 0 00 0 0 11 0
Admin Group Sub TLV: 00000006 (6)

Decimal (2^1 + 2^2)
Hexadecimal 0110
4. On your CORE router, configure a loose hop LSP "toRx-1" that terminates on the clockwise CORE
router (where x is the terminating router's number). Use the existing loose path for the primary
path. Enable CSPF on the LSP, and include admin group green and exclude admin group
red under the primary path context.
----------------------------------------------
lsp "toR2-1"
to 10.10.10.2
cspf
primary "loose"
include "green"
exclude "red"
exit
no shutdown
exit
----------------------------------------------
5. Use the show router mpls lsp <lsp-name> path detail command to verify the path
that the LSP takes.
*A:MPLSv2_R1# show router mpls lsp "toR2-1" path detail
===============================================================================
MPLS LSP toR2-1 Path (Detail)
===============================================================================
Legend :
@ - Detour Available # - Detour In Use
b - Bandwidth Protected n - Node Protected
s - Soft Preemption
S - Strict L - Loose
===============================================================================
-------------------------------------------------------------------------------
LSP toR2-1 Path loose
-------------------------------------------------------------------------------
LSP Name : toR2-1 Path LSP ID : 9728
From : 10.10.10.1 To : 10.10.10.2
Adm State : Up Oper State : Up
Path Name : loose Path Type : Primary
Path Admin : Up Path Oper : Up
OutInterface: 1/1/2 Out Label : 131049
Path Up Time: 0d 00:06:49 Path Dn Time: 0d 00:00:00
Retry Limit : 0 Retry Timer : 30 sec
RetryAttempt: 0 NextRetryIn : 0 sec
Adspec : Disabled Oper Adspec : Disabled

CSPF : Enabled Oper CSPF : Enabled
CSPF-FL : Disabled Oper CSPF-FL: Disabled
Least Fill : Disabled Oper LeastF*: Disabled
FRR : Disabled Oper FRR : Disabled
Prop Adm Grp: Disabled Oper PropAG : Disabled
Neg MTU : 1564 Oper MTU : 1564

Bandwidth : No Reservation Oper Bw : 0 Mbps
Hop Limit : 255 Oper HopLim*: 255
Record Route: Record Oper RecRou*: Record
Record Label: Record Oper RecLab*: Record
SetupPriori*: 7 Oper SetupP*: 7
Hold Priori*: 0 Oper HoldPr*: 0
Class Type : 0 Oper CT : 0
Backup CT : None
MainCT Retry: n/a
Rem :
MainCT Retry: 0
Limit :
Include Grps: Oper InclGr*:
green green
Exclude Grps: Oper ExclGr*:
red red
Adaptive : Enabled Oper Metric : 100

Preference : n/a
Path Trans : 1 CSPF Queries: 1
Failure Code: noError Failure Node: n/a
ExplicitHops:
No Hops Specified
Actual Hops :
10.1.2.1(10.10.10.1) Record Label : N/A
-> 10.1.2.2(10.10.10.2) Record Label : 131049
ComputedHops:
10.1.2.1(S) -> 10.1.2.2(S)
ResigEligib*: False
LastResignal: n/a CSPF Metric : 100
===============================================================================
* indicates that the corresponding row element may have been truncated.
a. Does the LSP follow the IGP-chosen best path? Why?

Yes. The IGP shortest path between routers R1 and R2 is the direct link (10.1.2.0). This
IGP path meets the administrative constraints of the LSP.
b. How does the head-end router inform the downstream routers of the path it chose for the
LSP?
Explicit Route Object (ERO). ERO is shown in the ComputedHops in the CLI output above.
NOTE: In the next steps, one pod at a time should work through steps 6 to 8 below. Work together to
ensure that each pod successfully completes the given procedures. Pod 2 users should wait for pod 1
users to enable any interfaces they have shut down before they can proceed (step 8). Similarly, pod 3
should wait for pod 2, and pod 4 should wait for pod 3.
6. On your CORE router, shut down the interface facing the clockwise CORE router. After a few
seconds, view the LSP path with the show router mpls lsp <lsp-name> path detail
command.
===============================================================================
===============================================================================
Legend :
s - Soft Preemption
===============================================================================
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
From : 10.10.10.1 To : 10.10.10.2


Backup CT : None
MainCT Retry: n/a
Rem :
MainCT Retry: 0
Limit :
green green
red red

Preference : n/a
ExplicitHops:
No Hops Specified
Actual Hops :
10.1.3.1(10.10.10.1) Record Label : N/A
-> 10.1.3.3(10.10.10.3) Record Label : 131048
-> 10.3.4.4(10.10.10.4) Record Label : 131048
-> 10.2.4.2(10.10.10.2) Record Label : 131048
ComputedHops:
10.1.3.1(S) -> 10.1.3.3(S) -> 10.3.4.4(S)
-> 10.2.4.2(S)
ResigEligib*: False
===============================================================================
a. Is the head-end router able to resignal the LSP over a new path? Why or why not?
Yes, the LSP goes around the ring in the other direction.
b. Does the new path follow the IGP path? Why or why not? HINT: Use the traceroute and
oam lsp-trace commands and compare the results.
*A:MPLSv2_R1# traceroute 10.10.10.2
traceroute to 10.10.10.2, 30 hops max, 40 byte packets
1 10.1.3.3 (10.1.3.3) 0.897 ms 0.657 ms 0.778 ms
2 10.10.10.2 (10.10.10.2) 1.69 ms 1.48 ms 1.23 ms

No; IGP still chooses the diagonal link, but CSPF prunes that link. The link is a member of
both the green and red administrative groups. The LSP's administrative constraints exclude
any link belonging to the red administrative group.
c. Did the CSPF metric change? Why or why not?
Yes; the cumulative metric changed from 100 (CSPF Metric shown in CLI output in step 5)
to 300 to reflect the total cost of the path, which now includes two additional links.
7. On the same CORE router, shut down the interface facing the counter-clockwise CORE router.
After a few seconds, view the LSP path with the show router mpls lsp <lsp-name>
path detail command.
===============================================================================
===============================================================================
Legend :
s - Soft Preemption
===============================================================================
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
From : 10.10.10.1 To : 10.10.10.2
Adm State : Up Oper State : Down
Path Admin : Up Path Oper : Down
OutInterface: n/a Out Label : n/a
Adspec : Disabled Oper Adspec : N/A

CSPF : Enabled Oper CSPF : N/A
CSPF-FL : Disabled Oper CSPF-FL: N/A
Least Fill : Disabled Oper LeastF*: N/A
FRR : Disabled Oper FRR : N/A
Prop Adm Grp: Disabled Oper PropAG : N/A
Neg MTU : 0 Oper MTU : N/A

Bandwidth : No Reservation Oper Bw : N/A
Hop Limit : 255 Oper HopLim*: N/A
Record Route: Record Oper RecRou*: N/A
Record Label: Record Oper RecLab*: N/A
SetupPriori*: 7 Oper SetupP*: N/A
Hold Priori*: 0 Oper HoldPr*: N/A
Class Type : 0 Oper CT : N/A
Backup CT : None
MainCT Retry: n/a
Rem :
MainCT Retry: 0
Limit :
green N/A
red N/A

Preference : n/a
Failure Code: noCspfRouteToDestination Failure Node: 10.10.10.1
ExplicitHops:
No Hops Specified
Actual Hops :
No Hops Specified
ComputedHops:
No Hops Specified
ResigEligib*: False
===============================================================================
a. Is the head-end router able to resignal the LSP over a new path? Why?
No; there are no more links that belong to the green admin group and not to the red
admin group.
b. Does the show command output provide any indication as to whether or not the LSP
recovered?
Failure code reads noCspfRouteToDestination.
c. Use the trace commands and compare the results. Is there still an IGP route to the tail-end
router?
1 10.1.4.4 (10.1.4.4) 0.688 ms 0.729 ms 0.702 ms
2 10.10.10.2 (10.10.10.2) 1.82 ms 1.18 ms 1.08 ms
Send failed. Unable to get LSP label info
Yes, but the IGP chooses the diagonal link, which is excluded from the LSP. The LSP trace
fails, as can be seen above.
8. Turn up the interfaces and verify that the routers move the LSP back to the original path. You
can use the tools perform router mpls resignal lsp <lsp-name> path <path-
name> command to make the head-end router resignal the LSP more quickly.
*A:MPLSv2_R1# configure router interface "toR3" no shutdown
*A:MPLSv2_R1# configure router interface "toR2" no shutdown
===============================================================================
===============================================================================
Legend :
s - Soft Preemption
===============================================================================
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
From : 10.10.10.1 To : 10.10.10.2


Backup CT : None
MainCT Retry: n/a
Rem :
MainCT Retry: 0
Limit :
green N/A
red N/A
Preference : n/a
ExplicitHops:
No Hops Specified
Actual Hops :
No Hops Specified
ComputedHops:
No Hops Specified
ResigEligib*: False
===============================================================================
*A:MPLSv2_R1# tools perform router mpls resignal lsp "toR2-1" path "loose"
===============================================================================
===============================================================================
Legend :
s - Soft Preemption
===============================================================================
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
From : 10.10.10.1 To : 10.10.10.2


Backup CT : None
MainCT Retry: n/a
Rem :
MainCT Retry: 0
Limit :
green green
red red
Preference : n/a
ExplicitHops:
No Hops Specified
Actual Hops :
10.1.2.1(10.10.10.1) Record Label : N/A
-> 10.1.2.2(10.10.10.2) Record Label : 131049
ComputedHops:
10.1.2.1(S) -> 10.1.2.2(S)
ResigEligib*: False
Last MBB :
MBB Type : ManualResignal MBB State : Success
Ended At : 04/03/2015 15:42:04 Old Metric : 100
Signaled BW: 0 Mbps
===============================================================================
5.2. LSP Soft Preemption
Objective
In this lab, we will create multiple LSPs with different setup and hold priority values and observe the
effect that modifying these values has on the states of the different LSPs.
Exercise
In this exercise, you will configure two LSPs to your diagonal neighbor: from your CORE router to your
diagonal neighbor's CORE router, and from your EDGE router to your diagonal neighbor's EDGE router.
1. On your CORE router, configure an LSP "toRx-1" to your diagonal neighbor's Core router with
600 Mb of bandwidth, and setup and hold priorities of 3. Use the loose path that you previously
created on your CORE router. Remember to enable CSPF on the LSP.
What path does the LSP take to destination? Does it follow the IGP path?

----------------------------------------------
lsp "toR4-1"
to 10.10.10.4
cspf
primary "loose"
bandwidth 600
priority 3 3
exit
no shutdown
exit
no shutdown
----------------------------------------------
===============================================================================
===============================================================================
Legend :
s - Soft Preemption
===============================================================================
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
From : 10.10.10.1 To : 10.10.10.4


Bandwidth : 600 Mbps Oper Bw : 600 Mbps
Backup CT : None
MainCT Retry: n/a
Rem :
MainCT Retry: 0
Limit :
None None
None None

Preference : n/a
ExplicitHops:
No Hops Specified
Actual Hops :
10.1.4.1(10.10.10.1) Record Label : N/A
-> 10.1.4.4(10.10.10.4) Record Label : 131047
ComputedHops:
10.1.4.1(S) -> 10.1.4.4(S)
ResigEligib*: False
===============================================================================
IGP takes the following route:

1 10.10.10.4 (10.10.10.4) 0.733 ms 0.700 ms 0.601 ms
2. On the CORE router, verify the remaining bandwidth on all RSVP interfaces.
===============================================================================
RSVP Interfaces
===============================================================================
-------------------------------------------------------------------------------
toR2 2 2 1000 0 Up Up
toR3 0 0 1000 0 Up Up
toR4 1 1 1000 600 Up Up
toR5 2 2 1000 0 Up Up
-------------------------------------------------------------------------------
Interfaces : 5
===============================================================================
3. On your EDGE router, configure an LSP "toRx-1" to your diagonal neighbor's EDGE router with
600 Mb of bandwidth, and setup and hold priorities of 4. Use the loose path that you have
previously created on your EDGE router.
What path does the LSP take to destination? Does it follow the IGP path?
----------------------------------------------
lsp "toR8-1"
to 10.10.10.8
cspf
primary "loose"
bandwidth 600
priority 4 4
exit
no shutdown
exit
----------------------------------------------
*A:MPLSv2_R5>config>router>mpls# show router mpls lsp "toR8-1" path detail
===============================================================================
===============================================================================
Legend :
s - Soft Preemption
===============================================================================
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
From : 10.10.10.5 To : 10.10.10.8


Backup CT : None
MainCT Retry: n/a
Rem :
MainCT Retry: 0
Limit :
None None
None None

Preference : n/a
ExplicitHops:
No Hops Specified
Actual Hops :
10.1.5.5(10.10.10.5) Record Label : N/A
-> 10.1.5.1(10.10.10.1) Record Label : 131047
-> 10.1.3.3(10.10.10.3) Record Label : 131049
-> 10.3.4.4(10.10.10.4) Record Label : 131048
-> 10.4.8.8(10.10.10.8) Record Label : 131069
ComputedHops:
10.1.5.5(S) -> 10.1.5.1(S) -> 10.1.3.3(S)
-> 10.3.4.4(S) -> 10.4.8.8(S)
ResigEligib*: False
===============================================================================
IGP takes the following route:
1 10.1.5.1 (10.1.5.1) 1.18 ms 1.19 ms 1.07 ms
2 10.1.4.4 (10.1.4.4) 1.92 ms 1.83 ms 1.68 ms
3 10.10.10.8 (10.10.10.8) 2.90 ms 2.29 ms 2.38 ms
The LSP does not follow the IGP best path since the LSP requires 600 Mb of bandwidth,
while the IGP best path only has 400 Mb of bandwidth available for an LSP with a setup
priority of 4. The following shows the reserved bandwidth on router R1's RSVP interfaces
after all LSPs between the EDGE routers on all the pods have been established.
===============================================================================
RSVP Interfaces
===============================================================================
-------------------------------------------------------------------------------
toR2 3 3 1000 600 Up Up
toR3 1 1 1000 600 Up Up
toR4 1 1 1000 600 Up Up
toR5 3 3 1000 600 Up Up
-------------------------------------------------------------------------------
Interfaces : 5
===============================================================================
4. Configure another LSP "toRx-2" on the EDGE router to your diagonal neighbor's EDGE router with
600 Mb of bandwidth, and setup and hold priorities of 2. What path does the LSP take? Were
the LSPs on your CORE router and the LSPs previously configured on the EDGE routers affected?
On which of the LSPs was MBB triggered? Why?
----------------------------------------------
lsp "toR8-2"
to 10.10.10.8
cspf
primary "loose"
bandwidth 600
priority 2 2
exit
no shutdown
exit
----------------------------------------------
As can be seen below, the new LSP "toRx-2" on the EDGE router now takes the same path
to its destination as the IGP:
*A:MPLSv2_R5>config>router>mpls# show router mpls lsp "toR8-2" path detail
===============================================================================
===============================================================================
Legend :
s - Soft Preemption
===============================================================================
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
From : 10.10.10.5 To : 10.10.10.8


Backup CT : None
MainCT Retry: n/a
Rem :
MainCT Retry: 0
Limit :
None None
None None

Preference : n/a
ExplicitHops:
No Hops Specified
Actual Hops :
10.1.5.5(10.10.10.5) Record Label : N/A
-> 10.1.5.1(10.10.10.1) Record Label : 131049
-> 10.1.4.4(10.10.10.4) Record Label : 131042
-> 10.4.8.8(10.10.10.8) Record Label : 131049
ComputedHops:
10.1.5.5(S) -> 10.1.5.1(S) -> 10.1.4.4(S)
-> 10.4.8.8(S)
ResigEligib*: False
===============================================================================
Since the link between the diagonal CORE routers cannot accommodate multiple 600 Mb
LSPs, the LSP with the higher setup and hold priority values is preempted by the LSP with
lower setup and hold priority values. MBB is triggered on the LSP that is being preempted.
In our case, the LSP on the CORE routers is the affected LSP, as can be seen below:
===============================================================================
===============================================================================
Legend :
s - Soft Preemption
===============================================================================
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
From : 10.10.10.1 To : 10.10.10.4


Backup CT : None
MainCT Retry: n/a
Rem :
MainCT Retry: 0
Limit :
None None
None None

Preference : n/a
ExplicitHops:
No Hops Specified
Actual Hops :
10.1.3.1(10.10.10.1) Record Label : N/A
-> 10.1.3.3(10.10.10.3) Record Label : 131048
-> 10.3.4.4(10.10.10.4) Record Label : 131041
ComputedHops:
10.1.3.1(S) -> 10.1.3.3(S) -> 10.3.4.4(S)
ResigEligib*: False
Last MBB :
MBB Type : SoftPreemption MBB State : Success
Ended At : 04/03/2015 17:51:19 Old Metric : 100
Signaled BW: 600 Mbps
===============================================================================
NOTE: If you trigger the show router mpls lsp command on the CORE router soon after
you bring the EDGE router's LSP up, you will notice that the LSP will not take the new path until
the MBB algorithm is complete. You will observe the following output:
===============================================================================
MPLS LSP toR4-lsp1 Path (Detail)
===============================================================================
Legend :
s - Soft Preemption
===============================================================================
-------------------------------------------------------------------------------
LSP toR4-lsp1 Path loose
-------------------------------------------------------------------------------
LSP Name : toR4-lsp1 Path LSP ID : 5122
From : 10.10.10.1 To : 10.10.10.4


Backup CT : None
MainCT Retry: n/a
Rem :
MainCT Retry: 0
Limit :
None None
None None

Preference : n/a
ExplicitHops:
No Hops Specified
Actual Hops :
10.1.4.1(10.10.10.1) s Record Label : N/A
-> 10.1.4.4(10.10.10.4) Record Label : 131045
ComputedHops:
10.1.4.1(S) -> 10.1.4.4(S)
ResigEligib*: False
In Prog MBB :
MBB Type : SoftPreemption NextRetryIn : 10 sec
Started At : 01/06/2015 22:42:24 RetryAttempt: 0
FailureCode: noError Failure Node: n/a
Signaled BW: 0 Mbps
===============================================================================
The LSPs between the EDGE routers configured in step 3 are now preempted by the LSPs
between the CORE routers. Since there is not enough bandwidth to accommodate these
LSPs, they are now operationally down:
===============================================================================
===============================================================================
Legend :
s - Soft Preemption
===============================================================================
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
From : 10.10.10.5 To : 10.10.10.8


Bandwidth : 600 Mbps Oper Bw : N/A
Backup CT : None
MainCT Retry: n/a
Rem :
MainCT Retry: 0
Limit :
None N/A
None N/A

Preference : n/a
ExplicitHops:
No Hops Specified
Actual Hops :
No Hops Specified
ComputedHops:
No Hops Specified
ResigEligib*: False
===============================================================================
5. Shut down the diagonal LSPs created in steps 1, 3 and 4 on your CORE and EDGE routers.
*A:MPLSv2_R1# configure router mpls lsp "toR4-1" shutdown

5.3. Configure LDP over RSVP across OSPF Areas
Objective
In this lab, we will create LDP over RSVP tunnels that will allow cross-area services to take advantage
of RSVP-TE resiliency features. Each pod will create a new CE-EDGE OSPF area, and build three RSVP
LSPs, one in each of three OSPF areas. Each team will then create LDP tunnels over the three RSVP
LSPs.
Figure 5-4: Enabling LDP Tunnels over RSVP
Exercise
In this exercise, you will configure LDP-over-RSVP tunnels and verify their operation to demonstrate
Inter-Area Traffic Engineering. We will incorporate the CE routers in this topology, using these routers
as our LDP tunnel head-ends. Use CE1 and CE3 for one set of tunnels, and CE2 and CE4 for the other
set.
1. On your EDGE and CE routers, create a new OSPF area, as shown in Figure 5-4. Put the CE
router system, CE-EDGE, and EDGE-CE interfaces in this new area.
The following is the configuration of the new OSPF area on router R5.
*A:MPLSv2_R5>config>router>ospf# info
----------------------------------------------
area 0.0.0.1
interface "toR9"
no shutdown
exit
exit
----------------------------------------------
The following is the configuration of the new OSPF area on CE router R9.
*A:MPLSv2_R9>config>router>ospf# info
----------------------------------------------
area 0.0.0.1
interface "system"
no shutdown
exit
interface "toR5"
no shutdown
exit
exit
----------------------------------------------
2. Verify that OSPF traffic-engineering is enabled on the CE and EDGE routers with the show
router ospf status command. If not, turn up traffic engineering.
OSPF is already enabled on the EDGE router.
===============================================================================
OSPF Status
===============================================================================
OSPF Version : 2
Preference : 10
Area Border Router : True
LFA : Disabled
Export Limit : 0
===============================================================================
Traffic Engineering is not yet enabled on the CE router.
===============================================================================
OSPF Status
===============================================================================
OSPF Version : 2
Preference : 10
Backbone Router : False
Traffic Engineering Support : False
LFA : Disabled
Export Limit : 0
===============================================================================
Enable Traffic Engineering using the following command:
*A:MPLSv2_R9# configure router ospf traffic-engineering
3. On your CE router, turn up MPLS and RSVP, put the CE-EDGE interface in MPLS, and configure a
totally loose path and LSP "toRx-1" to your pods EDGE router, where x is the EDGE router's
number. Enable CSPF on the LSP.
The following is the configuration on router R9.
----------------------------------------------
interface "system"
no shutdown
exit
interface "toR5"
no shutdown
exit
path "loose"
no shutdown
exit
lsp "toR5-1"
to 10.10.10.5
cspf
primary "loose"
exit
no shutdown
exit
no shutdown
----------------------------------------------
*A:MPLSv2_R9>config>router>rsvp# info
----------------------------------------------
interface "system"
no shutdown
exit
interface "toR5"
no shutdown
exit
no shutdown
----------------------------------------------
Note that the LSP to the EDGE router that you just created remains operationally down
until you place the EDGE-CE interface on your EDGE router in MPLS in the next step.
4. On your EDGE router, place the EDGE-CE interface in MPLS. Configure a CSPF-enabled LSP
"toRx-3" to your neighbors EDGE router as shown in Figure 5-4 (between pods 1 and 3, and
between pods 2 and 4).
----------------------------------------------
interface "toR9"
no shutdown
exit
lsp "toR7-3"
to 10.10.10.7
cspf
primary "loose"
exit
no shutdown
exit
----------------------------------------------
5. Verify that the RSVP LSPs on your EDGE and CE routers are operational.
An example is shown below. If the LSPs are not operational, verify that TE is enabled, that
the route-tables contain all routes including system IDs, and that you have enabled MPLS
on all necessary interfaces.
===============================================================================
===============================================================================
Id Config
-------------------------------------------------------------------------------
toR1-1 10.10.10.1 1 No Up Up
toR6-1 10.10.10.6 2 No Up Up
toR8-1 10.10.10.8 3 No Dwn Dwn
toR8-2 10.10.10.8 4 No Dwn Dwn
toR7-3 10.10.10.7 5 No Up Up
-------------------------------------------------------------------------------
LSPs : 5
===============================================================================
===============================================================================
===============================================================================
Id Config
-------------------------------------------------------------------------------
toR5-1 10.10.10.5 1 No Up Up
-------------------------------------------------------------------------------
LSPs : 1
===============================================================================
6. Shut down LDP on the EDGE-CORE router interfaces using the configure router ldp
interface-parameters interface <interface-name> shutdown command. This
limits the number of LDP-RSVP tunnel associations.
A:MPLSv2_R1# configure router ldp interface-parameters interface "toR5" shutdown
*A:MPLSv2_R5# configure router ldp interface-parameters interface "toR1" shutdown
7. Log into your neighbor pods EDGE router and configure a CSPF-enabled LSP "toRx-3", that
terminates on its connected CE router. Users of pod 1 and pod 3 should log into each others'
routers. Similarly, users of pod 2 and pod 4 should log into each others' routers. Verify that this
LSP is operational. Do not log out of your neighbors router.
The configurations on router R7 are shown below.
----------------------------------------------
lsp "toR11-3"
to 10.10.10.11
cspf
primary "loose"
exit
no shutdown
exit
----------------------------------------------
===============================================================================
===============================================================================
Id Config
-------------------------------------------------------------------------------
toR3-1 10.10.10.3 1 No Up Up
toR5-1 10.10.10.5 2 No Up Up
toR6-1 10.10.10.6 3 No Dwn Dwn
toR6-2 10.10.10.6 4 No Dwn Dwn
toR5-3 10.10.10.5 5 No Up Up
toR11-3 10.10.10.11 6 No Up Up
-------------------------------------------------------------------------------
LSPs : 6
===============================================================================
8. On your CE router, configure a manual T-LDP peering with your EDGE router and enable the
tunneling option. Configure targeted peers under the configure router ldp
targeted-session sub-context. Use the system IP address as the peer address.
The configuration on R9 is shown below.
*A:MPLSv2_R9>config>router>ldp$ info
----------------------------------------------
exit
targeted-session
peer 10.10.10.5
tunneling
exit
exit
exit
no shutdown
----------------------------------------------
9. On your EDGE router, configure a T-LDP peering to your neighbor pods EDGE router, with
tunneling enabled (between pods 1 and 3, and between pods 2 and 4).
----------------------------------------------
targeted-session
peer 10.10.10.7
tunneling
exit
exit
exit
no shutdown
----------------------------------------------
10. On your neighbor pods EDGE router, configure a T-LDP peering with its CE router, enabling
tunneling once more.
----------------------------------------------
targeted-session
peer 10.10.10.11
tunneling
exit
exit
exit
no shutdown
----------------------------------------------
11. After all users have configured T-LDP, use the show router ldp session command and
verify that the routers correctly establish their T-LDP sessions.
==============================================================================
LDP Sessions
==============================================================================
------------------------------------------------------------------------------
10.10.10.7:0 Targeted Established 133 134 0d 00:11:35
10.10.10.9:0 Targeted Established 115 114 0d 00:10:00
------------------------------------------------------------------------------
No. of Sessions: 2
==============================================================================
12. On your CE router, check the LFIB (show router ldp bindings active).
===============================================================================
===============================================================================
===============================================================================
-------------------------------------------------------------------------------
10.10.10.5/32 Push -- 131067 LspId 1 10.10.10.5
10.10.10.9/32 Pop 131070 -- -- --
-------------------------------------------------------------------------------
===============================================================================
a. Which prefixes are available?

Yours and the directly connected PE.
b. Do you see an entry for the other areas CE router system IP address?
No.
13. Enable LDP-over-RSVP in the CE and EDGE routers OSPF configuration with the configure
router ospf ldp-over-rsvp command.
14. On your CE router, check the LFIB now. Is the entry for the CE router in the other area there
now?
You can now tunnel over RSVP LSPs to your neighbor's CE router.
===============================================================================
===============================================================================
===============================================================================
-------------------------------------------------------------------------------
10.10.10.5/32 Push -- 131067 LspId 1 10.10.10.5
10.10.10.7/32 Push -- 131070 LspId 1 10.10.10.5
10.10.10.7/32 Swap 131066 131070 LspId 1 10.10.10.5
10.10.10.9/32 Pop 131070 -- -- --
10.10.10.11/32 Push -- 131065 LspId 1 10.10.10.5
10.10.10.11/32 Swap 131065 131065 LspId 1 10.10.10.5
-------------------------------------------------------------------------------
===============================================================================
15. What does the EgrIntf/LspId field indicate? Determine the LSP supporting the session by
viewing the tunnel ID shown in the show router rsvp session command output.
The EgrIntf/LSPId stands for the LSP tunnel ID of the LSP supporting the LDP binding.
*A:MPLSv2_R9# show router rsvp session
===============================================================================
RSVP Sessions
===============================================================================
ID ID
-------------------------------------------------------------------------------
10.10.10.9 10.10.10.5 1 15360 toR5-1::loose Up
10.10.10.5 10.10.10.9 6 41984 toR9-3::loose Up
-------------------------------------------------------------------------------
Sessions : 2
===============================================================================
16. On your CE router, verify the tunnel by targeting the far end CE router using the oam lsp-
trace prefix <system ID> command.
*A:MPLSv2_R9# oam lsp-trace prefix 10.10.10.11/32
lsp-trace to 10.10.10.11/32: 0 hops min, 0 hops max, 104 byte packets
5.4. Configure RSVP for IP Routing
Figure 5-5: Enabling LDP Tunnels over RSVP
Exercise
In this exercise, you will provision loose path LSPs between your EDGE router and the diagonally
opposite EDGE router. You will enable OSPF RSVP shortcut support, and you will enable CSPF in your
LSPs. Do not set any constraints on the LSP paths.
1. On your EDGE router, create a CSPF-enabled loose path LSP "toRx-3" that terminates on the
diagonally opposite EDGE router. Do not assign any constraints to the LSP.
----------------------------------------------
lsp "toR8-3"
to 10.10.10.8
cspf
primary "loose"
exit
no shutdown
exit
----------------------------------------------
2. Verify your LSPs operational state.
*A:MPLSv2_R5# show router mpls lsp "toR8-3"
===============================================================================
===============================================================================
Id Config
-------------------------------------------------------------------------------
toR8-3 10.10.10.8 7 No Up Up
-------------------------------------------------------------------------------
LSPs : 1
===============================================================================
3. View your route table with the show router route-table command.
a. What next-hop appears in your route table entry for the opposite EDGE routers system ID?
The directly connected CORE routers interface address facing the EDGE router.
===============================================================================
===============================================================================
-------------------------------------------------------------------------------
10.1.2.0/27 Remote OSPF 00h00m20s 10
10.1.5.1 200
10.1.3.0/27 Remote OSPF 00h00m20s 10
10.1.5.1 200
10.1.4.0/27 Remote OSPF 00h00m20s 10
10.1.5.1 200
10.1.5.0/27 Local Local 03d11h20m 0
toR1 0
10.2.3.0/27 Remote OSPF 00h00m20s 10
10.1.5.1 300
10.2.4.0/27 Remote OSPF 00h00m20s 10
10.1.5.1 300
10.2.6.0/27 Remote OSPF 00h00m20s 10
10.1.5.1 300
10.3.4.0/27 Remote OSPF 00h00m20s 10
10.1.5.1 300
10.3.7.0/27 Remote OSPF 00h00m20s 10
10.1.5.1 300
10.4.8.0/27 Remote OSPF 00h00m20s 10
10.1.5.1 300
10.5.9.0/27 Local Local 03d11h20m 0
toR9 0
10.6.10.0/27 Remote OSPF 00h00m20s 10
10.1.5.1 400
10.7.11.0/27 Remote OSPF 00h00m04s 10
10.1.5.1 400
10.8.12.0/27 Remote OSPF 00h00m04s 10
10.1.5.1 400
10.10.10.1/32 Remote OSPF 00h00m20s 10
10.1.5.1 100
10.10.10.2/32 Remote OSPF 00h00m20s 10
10.1.5.1 200
10.10.10.3/32 Remote OSPF 00h00m20s 10
10.1.5.1 200
10.10.10.4/32 Remote OSPF 00h00m20s 10
10.1.5.1 200
10.10.10.5/32 Local Local 03d11h20m 0
system 0
10.10.10.6/32 Remote OSPF 00h00m20s 10
10.1.5.1 300
10.10.10.7/32 Remote OSPF 00h00m04s 10
10.1.5.1 300
10.10.10.8/32 Remote OSPF 00h00m05s 10
10.1.5.1 300
10.10.10.9/32 Remote OSPF 00h00m05s 10
10.5.9.9 100
10.10.10.10/32 Remote OSPF 00h00m21s 10
10.1.5.1 400
10.10.10.11/32 Remote OSPF 00h00m05s 10
10.1.5.1 400
10.10.10.12/32 Remote OSPF 00h00m05s 10
10.1.5.1 400
-------------------------------------------------------------------------------
No. of Routes: 26
===============================================================================
b. What metric does the router assign to this route?

The same metric as the IGP.
4. In OSPF, enable RSVP-shortcuts on all your routers. Use the show router ospf status
command to verify that RSVP-shortcut is enabled.
NOTE: Enabling RSVP-shortcut can prompt the router to make existing, non-CSPF enabled LSPs
operationally down, as this command makes all LSPs shortcut eligible. To exempt certain LSPs from
shortcut consideration, use the configure router mpls lsp <lsp-nam>. no igp-shortcut
command.
*A:MPLSv2_R5# configure router ospf rsvp-shortcut
===============================================================================
OSPF Status
===============================================================================
OSPF Version : 2
Preference : 10
Area Border Router : True
LDP-over-RSVP : Enabled
RSVP-Shortcut : Enabled
LFA : Disabled
Export Limit : 0
===============================================================================
5. View your EDGE routers route table and list of LSPs.

NOTE: The route table will likely show other tunneled prefixes as well. Any CSPF-enabled LSPs are
shortcut eligible, and so the IGP will use those for forwarding traffic to its configured FECs.
===============================================================================
===============================================================================
-------------------------------------------------------------------------------
10.1.2.0/27 Remote OSPF 00h00m19s 10
10.1.5.1 200
10.1.3.0/27 Remote OSPF 00h00m19s 10
10.1.5.1 200
10.1.4.0/27 Remote OSPF 00h00m19s 10
10.1.5.1 200
10.1.5.0/27 Local Local 03d11h35m 0
toR1 0
10.2.3.0/27 Remote OSPF 00h00m19s 10
10.1.5.1 300
10.2.4.0/27 Remote OSPF 00h00m19s 10
10.1.5.1 300
10.2.6.0/27 Remote OSPF 00h00m19s 10
10.1.5.1 300
10.3.4.0/27 Remote OSPF 00h00m19s 10
10.1.5.1 300
10.3.7.0/27 Remote OSPF 00h00m19s 10
10.1.5.1 300
10.4.8.0/27 Remote OSPF 00h00m19s 10
10.1.5.1 300
10.5.9.0/27 Local Local 03d11h35m 0
toR9 0
10.6.10.0/27 Remote OSPF 00h00m19s 10
10.1.5.1 400
10.7.11.0/27 Remote OSPF 00h11m32s 10
10.10.10.7 (tunneled:RSVP:5) 400
10.8.12.0/27 Remote OSPF 00h11m32s 10
10.10.10.8 (tunneled:RSVP:7) 400
10.10.10.1/32 Remote OSPF 00h00m19s 10
10.1.5.1 100
10.10.10.2/32 Remote OSPF 00h00m19s 10
10.1.5.1 200
10.10.10.3/32 Remote OSPF 00h00m19s 10
10.1.5.1 200
10.10.10.4/32 Remote OSPF 00h00m19s 10
10.1.5.1 200
10.10.10.5/32 Local Local 03d11h35m 0
system 0
10.10.10.6/32 Remote OSPF 00h00m19s 10
10.1.5.1 300
10.10.10.7/32 Remote OSPF 00h11m32s 10
10.10.10.7 (tunneled:RSVP:5) 300
10.10.10.8/32 Remote OSPF 00h11m33s 10
10.10.10.8 (tunneled:RSVP:7) 300
10.10.10.9/32 Remote OSPF 00h11m33s 10
10.10.10.9 (tunneled:RSVP:6) 100
10.10.10.10/32 Remote OSPF 00h00m21s 10
10.1.5.1 400
10.10.10.11/32 Remote OSPF 00h11m33s 10
10.10.10.7 (tunneled:RSVP:5) 400
10.10.10.12/32 Remote OSPF 00h11m33s 10
10.10.10.8 (tunneled:RSVP:7) 400
-------------------------------------------------------------------------------
No. of Routes: 26
===============================================================================
A:MPLSv2_R5# show router mpls lsp
===============================================================================
===============================================================================
Id Config
-------------------------------------------------------------------------------
toR1-1 10.10.10.1 1 No Up Dwn
toR6-1 10.10.10.6 2 No Up Dwn
toR8-1 10.10.10.8 3 No Dwn Dwn
toR8-2 10.10.10.8 4 No Dwn Dwn
toR7-3 10.10.10.7 5 No Up Up
toR9-3 10.10.10.9 6 No Up Up
toR8-3 10.10.10.8 7 No Up Up
-------------------------------------------------------------------------------
LSPs : 7
===============================================================================
a. Do you see any routes listed as tunneled via RSVP?

Yes, all routes to FECs on which CSPF-enabled LSPs terminate, are reachable via tunnels
terminating on the tail-end router.
b. What does the route table list as these routes next-hop interface?
The LSP tail-end routers system ID and the tunnel ID of the LSP terminating on that tail-
end router.
c. Why does your router choose RSVP tunnels over IGP routes for this traffic?
Tunnel counts as one hop, versus several hops via IGP route.
6. Use the tools dump router ospf route-table <prefix> detail command to view
the IGP shortcut tunnel information to the diagonal EDGE router.
*A:MPLSv2_R5# tools dump router ospf route-table 10.10.10.8/32 detail
================================================================================
OSPFv2 Routing Table (detailed)
================================================================================
Destination Type(Dest) Stat
NHIP NHIF Cost[E2] Area Tunnel-Information
--------------------------------------------------------------------------------
10.10.10.8/32 IA (HOST) N (R)
10.10.10.8 RSVP:7 300 0.0.0.0 IGP-Shortcut tnl
10.10.10.8/0 IA (ABR) N (N)

10.10.10.8 RSVP:7 300 0.0.0.0 IGP-Shortcut tnl
--------------------------------------------------------------------------------
2 OSPFv2 routes found (2 paths)
Stat: D = direct N = not direct
(RTM stat):(R) = added (F) = add failed
(N) = not added (D) = policy discarded
================================================================================
7. Turn off RSVP-shortcuts with the configure router ospf no rsvp-shortcut command.

1. What type of LSA does OSPF use to advertise Traffic Engineering information?
Type 10 opaque
2. What top-level TLV does a router automatically send out, once you enable Traffic Engineering
support in the IGP?
Router ID
3. Once you enable Traffic Engineering support on a router located in OSPF area 0, that router
would see opaque LSAs from what other areas?
None, OSPF only floods type 10 LSAs in the area in which they are generated.
4. If you configure an LSP to include green but exclude red links, will it use a link assigned to the
red and green admin groups?
No, the head-end will prune the red links from consideration.
5. The opaque LSA represents a links admin group membership in what format(s)?
Hexadecimal and decimal
6. If the head-end router chooses a path other than the IGP best path for a loose path LSP, how
does it inform the downstream routers of this decision?
It sends the ERO in the RSVP path message.
7. If the primary path fails on a colored LSP, can the LSP recover on an alternate path?
Yes, if another path exists that meets the LSPs constraints.
8. If you configure admin groups on a router, and build an LSP without specifying link admin group
membership, can the LSP become operational?
Yes, the LSP will still operate; however, the path the head-end chooses for this LSP
depends on other constraints, not admin groups.
9. In what top-level TLV does the router advertise admin group membership?
Link TLV.
10. Why must you use LDP over RSVP tunnels when Traffic Engineering LSPs between OSPF areas?
Opaque LSAs carry TE constraint information and cannot cross OSPF area boundaries.
11. In addition to RSVP LSPs, what must you configure on each hop to support LDP over RSVP
tunneling?
Targeted sessions between the EDGE routers and the ABRs, and between the ABRs with
tunneling enabled.
12. What benefit does an LSP shortcut provide over a traditional IGP route?
IGP shortcuts allow you to label-switch traffic instead of routing it. Traffic targeting a
router that is not MPLS-capable is tunneled using the LSP shortcut over MPLS-capable
routers.
13. Once you have configured RSVP for IGP shortcuts between two edge routers, what networks will
your head-end router be able to reach via the tunnels tail-end?
Any routed network accessible through the tail-end router.
14. If a router has in its RIB both an IGP shortcut and a standard IGP route to a destination
network, which will it place in its FIB?
The IGP shortcut.
Lab 6 RSVP-TE Resiliency Features
Objective
These exercises introduce LSP resiliency features that RSVP-TE supports in an MPLS domain. You will
configure and observe the behavior of primary and secondary LSP paths using strict and loose hop
definitions, shared risk link groups (SRLG), fast reroute one-to-one, and facility bypass.
Lab 6 Command list
A:MPLS_R1# configure router mpls lsp <lsp-name> fast-reroute one-to-

one|facility
A:MPLS_R1# show router mpls status
A:MPLS_R1# show router mpls lsp path detail
A:MPLS_R1# show router mpls lsp transit
A:MPLS_R1# show router rsvp session detail
A:MPLS_R1# show router mpls bypass-tunnel detail
A:MPLS_R1# show router mpls bypass-tunnel protected-lsp detail
A:MPLS_R1# show router rsvp session bypass-tunnel
A:MPLS_R1# show router rsvp session bypass-tunnel detail
A:MPLS_R1# oam lsp-ping <lsp-name>
A:MPLS_R1# configure router ldp targeted-session peer <peer-ip> tunneling
A:MPLS_R1# configure router mpls interface <interface-name>
A:MPLS_R1# configure router mpls interface <interface-name> srlg-group <group-
name>
A:MPLS_R1# configure router mpls lsp <lsp-name> cspf
A:MPLS_R1# configure router mpls lsp <lsp-name> primary <path-name>
A:MPLS_R1# configure router mpls lsp <lsp-name> secondary <path-name>
A:MPLS_R1# configure router mpls lsp <lsp-name> secondary <path-name> srlg
A:MPLS_R1# configure router mpls lsp <lsp-name> secondary <path-name> standby
A:MPLS_R1# configure router mpls path <path-name> hop <index> [strict | loose]
A:MPLS_R1# configure router mpls srlg-group <group-name> value <group-value>
A:MPLS_R1# configure router ospf area <area-id> interface <interface-name>
A:MPLS_R1# configure router ospf rsvp-shortcut

A:MPLS_R1# show router mpls lsp terminate detail
A:MPLS_R1# oam lsp-trace <lsp-name>
6.1. Enabling Primary and Secondary LSP Tunnels
Figure 6-1: Enabling Primary and Secondary LSP Tunnels
Exercise
This lab consists of three phases. In phase I, you will configure an LSP with a primary and secondary
path and examine the results. In phase II, you will reconfigure the secondary path to standby mode
and again examine the results. In phase III, you will shut down an interface along the primary path and
watch the secondary path back up the downed primary path.
Phase I
1. Configure an LSP with your EDGE router as the tunnel head, and the diagonally connected CORE
router as the tail-end. For example, if you are in pod 1, router R5 would be your tunnel head,
and router R4 would be the tail-end. Follow these steps:
a. Configure a strict hop path "toRxstrict" from your EDGE router that goes through the
clockwise CORE router, and terminates on the diagonally opposite CORE router. For
example, if you are on router R5, use router R2 in the path to get to router R4.
----------------------------------------------
path "toR4strict"
hop 10 10.10.10.1 strict
hop 20 10.10.10.2 strict
hop 30 10.10.10.4 strict
no shutdown
exit
b. Configure an LSP "toRx-4", originating on your EDGE router and terminating on the
diagonally connected CORE router, using the strict path as the primary path, and a fully
loose path as the secondary path. Do not configure the standby option for the secondary
path, and do not allocate bandwidth, set hop-limits or admin-group inclusions/exclusions,
or enable CSPF.
----------------------------------------------
lsp "toR4-4"
to 10.10.10.4
primary "toR4strict"
exit
secondary "loose"
exit
no shutdown
exit
2. Use the show router mpls path command to confirm that the paths you have configured
are administratively up, and that the hops have been defined correctly.

*A:MPLSv2_R5# show router mpls path
===============================================================================
MPLS Path:
===============================================================================
Path Name Adm Hop Index IP Address Strict/Loose
-------------------------------------------------------------------------------
loose Up no hops n/a n/a
toR4strict Up 10 10.10.10.1 Strict

20 10.10.10.2 Strict
30 10.10.10.4 Strict
-------------------------------------------------------------------------------
Total Paths : 2
===============================================================================
a. What is the difference between strict and loose paths?
A strict path requires the next-hop address to be directly connected to the current router,
while a loose path hop makes use of the routing table to find the best path to the next-
hop address.
3. Use the show router mpls lsp <lsp name> path detail command to view the details
of the paths used by your newly created LSP.

===============================================================================
===============================================================================
Legend :
s - Soft Preemption
===============================================================================
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
From : 10.10.10.5 To : 10.10.10.4
Path Name : loose Path Type : Secondary

CSPF : Disabled Oper CSPF : N/A

None N/A
None N/A

Preference : n/a
ExplicitHops:
No Hops Specified
Actual Hops :
No Hops Specified
Srlg : Disabled
ResigEligib*: False
-------------------------------------------------------------------------------
LSP toR4-4 Path toR4strict
-------------------------------------------------------------------------------
From : 10.10.10.5 To : 10.10.10.4
Path Name : toR4strict Path Type : Primary

CSPF : Disabled Oper CSPF : Disabled

Backup CT : None
MainCT Retry: n/a
Rem :
MainCT Retry: 0
Limit :
None None
None None

Preference : n/a
ExplicitHops:
10.10.10.1(S) -> 10.10.10.2(S) -> 10.10.10.4(S)
Actual Hops :
10.1.5.5(10.10.10.5) Record Label : N/A
-> 10.1.5.1(10.10.10.1) Record Label : 131053
-> 10.1.2.2(10.10.10.2) Record Label : 131052
-> 10.2.4.4(10.10.10.4) Record Label : 131052
ResigEligib*: False
===============================================================================
a. What is the operational state of the primary path?

The operational state of the primary path should be UP.
b. What is the operational state of the secondary path? Explain.
The operational state of the secondary path is Down because this secondary path is not
in "standby" mode. The LSP head must signal the secondary state in order to enable it and
bring it into an up state. If the secondary path is configured in "standby" mode, it will
be operationally up even when the primary path is operationally up (Phase II).
4. On your CORE router, determine whether there are any transiting or terminating LSPs using the
show router mpls lsp transit and show router mpls lsp transit commands.

A:MPLSv2_R1# show router mpls lsp transit
===============================================================================
MPLS LSPs (Transit)
===============================================================================
Legend : @ - Active Detour
===============================================================================
From To In I/F Out I/F State LSP Name
-------------------------------------------------------------------------------
10.10.10.5 10.10.10.7 1/1/1 1/1/3 Up toR7-3::loose
10.10.10.7 10.10.10.5 1/1/3 1/1/1 Up toR5-3::loose
10.10.10.5 10.10.10.8 1/1/1 1/1/4 Up toR8-3::loose
10.10.10.8 10.10.10.5 1/1/4 1/1/1 Up toR5-3::loose
10.10.10.7 10.10.10.5 1/1/3 1/1/1 Up toR5-1::loose
10.10.10.5 10.10.10.6 1/1/1 1/1/2 Up toR6-1::loose
10.10.10.5 10.10.10.4 1/1/1 1/1/2 Up toR4-4::toR4strict
10.10.10.7 10.10.10.2 1/1/3 1/1/2 Up toR2-4::toR2strict
-------------------------------------------------------------------------------
LSPs : 8
-------------------------------------------------------------------------------
A:MPLSv2_R1# show router mpls lsp terminate

===============================================================================
MPLS LSPs (Terminate)
===============================================================================
===============================================================================
-------------------------------------------------------------------------------
10.10.10.3 10.10.10.1 1/1/3 n/a Up toR1-1::loose
10.10.10.5 10.10.10.1 1/1/1 n/a Up toR1-1::loose
10.10.10.8 10.10.10.1 1/1/3 n/a Up toR1-4::toR1strict
-------------------------------------------------------------------------------
LSPs : 3
-------------------------------------------------------------------------------
a. From where do the transiting LSPs with strict paths originate?

In addition to the LSPs configured in previous exercises, there are 2 new transiting LSPs:
one originating on the counter-clockwise neighbor pod and another originating on your
EDGE router. (Your output will defer if other pods have not yet completed the LSP
creation)
b. From where do the terminating LSPs with strict paths originate?

From the LSPs created on the diagonal pod. (Your output will defer if other pods have not
yet completed the LSP creation).
5. Connect to your clockwise neighbor's CORE router (the one on your strict primary path). Use
the show router mpls lsp transit detail command to verify that this router is in
your LSP's path and to view the labels assigned.
An example of the output is shown below (truncated for simplicity).

A:MPLSv2_R2# show router mpls lsp transit detail
===============================================================================
MPLS LSPs (Transit) (Detail)
===============================================================================
-------------------------------------------------------------------------------
LSP toR4-4::toR4strict
-------------------------------------------------------------------------------
From : 10.10.10.5 To : 10.10.10.4
State : Up
SetupPriority : 7 Hold Priority : 0
Class Type : 0
In Interface : 1/1/2 In Label : 131052
Out Interface : 1/1/3 Out Label : 131052
Previous Hop : 10.1.2.1 Next Hop : 10.2.4.4
Reserved BW : 0 Kbps
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
From : 10.10.10.6 To : 10.10.10.3
State : Up
Class Type : 0
===============================================================================
6. Connect to the diagonal neighbor's CORE router (the tail-end of your LSP). Use the show
router mpls lsp terminate detail command to verify that this router is in your LSP's
path and to view the labels assigned.
A:MPLSv2_R4# show router mpls lsp terminate detail
===============================================================================
MPLS LSPs (Terminate) (Detail)
===============================================================================
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
From : 10.10.10.5 To : 10.10.10.4
State : Up
Class Type : 0
Previous Hop : 10.2.4.2
===============================================================================
Phase II
1. On your EDGE router, configure the secondary path of the LSP you created in Phase I as a
standby path to enable hot standby mode.
*A:MPLSv2_R5# configure router mpls lsp "toR4-4" secondary "loose" standby
2. Use the show router mpls lsp <lsp name> path detail command to view the details
of the paths used by your LSP.

===============================================================================
===============================================================================
Legend :
s - Soft Preemption
===============================================================================
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
From : 10.10.10.5 To : 10.10.10.4
Path Name : loose Path Type : Standby


None None
None None

Preference : 255
ExplicitHops:
No Hops Specified
Actual Hops :
10.1.5.5(10.10.10.5) Record Label : N/A
-> 10.1.5.1(10.10.10.1) Record Label : 131049
-> 10.1.4.4(10.10.10.4) Record Label : 131048
Srlg : Disabled
SrlgDisjoint: False
ResigEligib*: False
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
From : 10.10.10.5 To : 10.10.10.4


Backup CT : None
MainCT Retry: n/a
Rem :
MainCT Retry: 0
Limit :
None None
None None
Preference : n/a
ExplicitHops:
10.10.10.1(S) -> 10.10.10.2(S) -> 10.10.10.4(S)
Actual Hops :
10.1.5.5(10.10.10.5) Record Label : N/A
-> 10.1.5.1(10.10.10.1) Record Label : 131053
-> 10.1.2.2(10.10.10.2) Record Label : 131052
-> 10.2.4.4(10.10.10.4) Record Label : 131052
ResigEligib*: False
===============================================================================

The operational state of the primary path should still be UP.
b. What is the operational state of the secondary path? Explain.
The operational state of the secondary path is now Up because it is now in "standby"
mode. Both primary and secondary paths are now operationally up.

A:MPLSv2_R1# show router mpls lsp transit
===============================================================================
MPLS LSPs (Transit)
===============================================================================
===============================================================================
-------------------------------------------------------------------------------
10.10.10.5 10.10.10.7 1/1/1 1/1/3 Up toR7-3::loose
10.10.10.7 10.10.10.5 1/1/3 1/1/1 Up toR5-3::loose
10.10.10.5 10.10.10.8 1/1/1 1/1/4 Up toR8-3::loose
10.10.10.8 10.10.10.5 1/1/4 1/1/1 Up toR5-3::loose
10.10.10.7 10.10.10.5 1/1/3 1/1/1 Up toR5-1::loose
10.10.10.5 10.10.10.6 1/1/1 1/1/2 Up toR6-1::loose
10.10.10.5 10.10.10.4 1/1/1 1/1/2 Up toR4-4::toR4strict
10.10.10.7 10.10.10.2 1/1/3 1/1/2 Up toR2-4::toR2strict
10.10.10.5 10.10.10.4 1/1/1 1/1/4 Up toR4-4::loose
-------------------------------------------------------------------------------
LSPs : 9
-------------------------------------------------------------------------------
A:MPLSv2_R1# show router mpls lsp terminate

===============================================================================
===============================================================================
===============================================================================
-------------------------------------------------------------------------------
10.10.10.3 10.10.10.1 1/1/3 n/a Up toR1-1::loose
10.10.10.5 10.10.10.1 1/1/1 n/a Up toR1-1::loose
10.10.10.8 10.10.10.1 1/1/3 n/a Up toR1-4::toR1strict
10.10.10.8 10.10.10.1 1/1/4 n/a Up toR1-4::loose
-------------------------------------------------------------------------------
LSPs : 4
-------------------------------------------------------------------------------
a. What new transiting LSPs do you observe? Where do they originate?
In addition to the LSPs observed in Phase I, the secondary path is now operational and can
be seen in the list of transiting LSPs. (Your output will difer if other pods have not yet
completed the LSP creation).
b. What new terminating LSPs do you observe? Where do they originate?

The secondary path of the LSP originating on the diagonal pod. (Your output will differ if
other pods have not yet completed the LSP creation)
4. Connect to your clockwise neighbor's CORE router (the one on your strict primary path). Use
the show router mpls lsp transit detail command to verify that this router is in
your LSP's path and to view the labels assigned.

A:MPLSv2_R2# show router mpls lsp transit detail
===============================================================================
===============================================================================
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
From : 10.10.10.5 To : 10.10.10.4
State : Up
Class Type : 0
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
From : 10.10.10.6 To : 10.10.10.3
State : Up
Class Type : 0
-------------------------------------------------------------------------------
LSP toR3-4::loose
-------------------------------------------------------------------------------
From : 10.10.10.6 To : 10.10.10.3
State : Up
Class Type : 0
a. Are there any changes from what you observed in Phase I?
No changes regarding your LSP can be observed because the secondary path uses a
different route to the tail-end router.
A:MPLSv2_R4# show router mpls lsp terminate detail
===============================================================================
===============================================================================
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
From : 10.10.10.5 To : 10.10.10.4
State : Up
Class Type : 0
-------------------------------------------------------------------------------
LSP toR4-4::loose
-------------------------------------------------------------------------------
From : 10.10.10.5 To : 10.10.10.4
State : Up
Class Type : 0
===============================================================================
a. Are there any changes from what you observed in Phase I?

On the tail-end, you can now see both the secondary path and the primary path because
both are operationally up.
Phase III
1. Ask the user on the clockwise pod to shut down the interface between their CORE router and
their clockwise neighbors CORE router (your tunnels tail-end). For example, if you are on pod
1, the user on pod 2 will shut down their R2-R4 interface. (Similarly, you will be asked to shut
down the interface to the clockwise CORE router). The secondary link should become the new
active link. Use the show router mpls lsp <lsp name> path detail command to
verify.

A:MPLSv2_R2# configure router interface "toR4" shutdown
The LSP path detail on router R5 is shown below.

===============================================================================
===============================================================================
Legend :
s - Soft Preemption
===============================================================================
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
From : 10.10.10.5 To : 10.10.10.4
Path Name : loose Path Type : Standby


None None
None None

Preference : 255
ExplicitHops:
No Hops Specified
Actual Hops :
10.1.5.5(10.10.10.5) Record Label : N/A
-> 10.1.5.1(10.10.10.1) Record Label : 131049
-> 10.1.4.4(10.10.10.4) Record Label : 131048
Srlg : Disabled
SrlgDisjoint: False
ResigEligib*: False
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
From : 10.10.10.5 To : 10.10.10.4

CSPF : Disabled Oper CSPF : N/A

Backup CT : None
MainCT Retry: n/a
Rem :
MainCT Retry: 0
Limit :
None N/A
None N/A

Preference : n/a
Failure Code: badNode Failure Node: 10.1.5.1
ExplicitHops:
10.10.10.1(S) -> 10.10.10.2(S) -> 10.10.10.4(S)
Actual Hops :
No Hops Specified
ResigEligib*: False
===============================================================================
The operational state of the primary path is now "down" since there is no longer a route to
the tail-end using the primary strict path.
b. What is the operational state of the secondary path?
The secondary path is Up.

*A:MPLSv2_R1# show router mpls lsp transit
===============================================================================
MPLS LSPs (Transit)
===============================================================================
===============================================================================
-------------------------------------------------------------------------------
10.10.10.5 10.10.10.8 1/1/1 1/1/4 Up toR8-3::loose
10.10.10.8 10.10.10.5 1/1/4 1/1/1 Up toR5-3::loose
10.10.10.5 10.10.10.4 1/1/1 1/1/4 Up toR4-4::loose
-------------------------------------------------------------------------------
LSPs : 3
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
LSPs : 9
-------------------------------------------------------------------------------
*A:MPLSv2_R1# show router mpls lsp terminate

===============================================================================
===============================================================================
===============================================================================
-------------------------------------------------------------------------------
10.10.10.5 10.10.10.1 1/1/1 n/a Up toR1-1::loose
10.10.10.8 10.10.10.1 1/1/4 n/a Up toR1-4::loose
-------------------------------------------------------------------------------
LSPs : 2
-------------------------------------------------------------------------------
a. What transiting LSPs do you observe? Where do they originate?

Only LSPs using the diagonal CORE links can now be observed. (Your output will differ if
other pods have not yet completed Phase III).
b. What terminating LSPs do you observe? Where do they originate?

Only LSPs using the diagonal CORE links can now be observed. (Your output will differ if
other pods have not yet completed Phase III).
3. Connect to your clockwise neighbor's CORE router (the one on your strict primary path). Is this
router still part of your LSP's path?

*A:MPLSv2_R2# show router mpls lsp transit detail
===============================================================================
===============================================================================
-------------------------------------------------------------------------------
LSP toR7-3::loose
-------------------------------------------------------------------------------
From : 10.10.10.6 To : 10.10.10.7
State : Up
Class Type : 0
-------------------------------------------------------------------------------
LSP toR6-3::loose
-------------------------------------------------------------------------------
From : 10.10.10.7 To : 10.10.10.6
State : Up
Class Type : 0
-------------------------------------------------------------------------------
LSP toR3-4::loose
-------------------------------------------------------------------------------
From : 10.10.10.6 To : 10.10.10.3
State : Up
Class Type : 0
===============================================================================
a. Are there any changes from what you observed in Phase II?
Your LSP no longer transits your neighbor's CORE router because a section of your strict
path was shut down.

*A:MPLSv2_R4# show router mpls lsp terminate detail
===============================================================================
===============================================================================
-------------------------------------------------------------------------------
LSP toR4-1::loose
-------------------------------------------------------------------------------
From : 10.10.10.8 To : 10.10.10.4
State : Up
Class Type : 0
-------------------------------------------------------------------------------
LSP toR4-4::loose
-------------------------------------------------------------------------------
From : 10.10.10.5 To : 10.10.10.4
State : Up
Class Type : 0
===============================================================================
a. Are there any changes from what you observed in Phase II?
On the tail-end, you can only see your LSP's secondary path since the primary path is now
down.
5. Once you have confirmed the path, ask your neighbor to bring up the interface and ensure that
the primary path is now the active path.
6.2. Using SRLG for Path Resiliency
Figure 6-2: Enabling SRLG Standby LSPs
Exercise
In this exercise, you will configure an LSP originating on your EDGE router and terminating on the
diagonally opposite EDGE router. You will configure two loose paths: one as a primary path, and the
second as a standby path. You will initially place all core links in SRLG orange and observe the path the
LSP chooses for both the primary and secondary paths. You will then modify the SRLG configuration and
observe the LSPs behavior as you disable and re-enable the cross link core interfaces.
1. Use the show router ospf status command on both your routers to verify that traffic
engineering is still enabled.
2. On both your EDGE and CORE routers, create an SRLG group orange, with a value of 1.
*A:MPLSv2_R1# configure router mpls srlg-group orange value 1
Note that even though the interfaces on the EDGE routers do not use the SRLG group, the
SRLG group still needs to be configured on them if the LSPs generating on the EDGE
routers are to use the SRLG path resiliency feature.
3. Place all your CORE router core MPLS interfaces in the orange SRLG group.
*A:MPLSv2_R1>config>router>mpls# interface "toR2" srlg-group "orange"
4. Create two loose paths: one will be the primary path, the other the standby path. You may use
your existing loose path for one of the two LSP path assignments.
The configuration is shown in step 6 below.
5. Create an LSP "toRx-5" with your EDGE router as head-end, and the diagonally opposite EDGE
router as tail-end. Be sure to enable CSPF, but do not set any LSP constraints.
The configuration is shown in step 6 below.
6. Make the secondary path a standby path, and enable SRLG on the standby path.
----------------------------------------------
srlg-group "orange" value 1
path "primary-toR8"
no shutdown
exit
path "secondary-toR8"
no shutdown
exit
lsp "toR8-5"
to 10.10.10.8
cspf
primary "primary-toR8"
exit
secondary "secondary-toR8"
standby
srlg
exit
no shutdown
exit
----------------------------------------------
7. Verify the LSPs status with the show router mpls lsp <lsp-name> path detail
command.
===============================================================================
===============================================================================
Legend :
s - Soft Preemption
===============================================================================
-------------------------------------------------------------------------------
LSP toR8-5 Path primary-toR8
-------------------------------------------------------------------------------
From : 10.10.10.5 To : 10.10.10.8
Path Name : primary-toR8 Path Type : Primary


Backup CT : None
MainCT Retry: n/a
Rem :
MainCT Retry: 0
Limit :
None None
None None

Preference : n/a
ExplicitHops:
No Hops Specified
Actual Hops :
10.1.5.5(10.10.10.5) Record Label : N/A
-> 10.1.5.1(10.10.10.1) Record Label : 131042
-> 10.1.4.4(10.10.10.4) Record Label : 131044
-> 10.4.8.8(10.10.10.8) Record Label : 131060
ComputedHops:
10.1.5.5(S) -> 10.1.5.1(S) -> 10.1.4.4(S)
-> 10.4.8.8(S)
ResigEligib*: False
-------------------------------------------------------------------------------
LSP toR8-5 Path secondary-toR8
-------------------------------------------------------------------------------
From : 10.10.10.5 To : 10.10.10.8
Path Name : secondary-toR8 Path Type : Standby
None N/A
None N/A

Preference : 255
ExplicitHops:
No Hops Specified
Actual Hops :
No Hops Specified
ComputedHops:
No Hops Specified
Srlg : Enabled
SrlgDisjoint: False
ResigEligib*: False
===============================================================================
a. Which path does the router choose for the primary path? Why?
The IGP best path is chosen because there are no constraints on the primary path.
b. Is secondary path operational? Why or why not?
All possible links between the CORE routers are in the same SRLG. The standby path
cannot become disjoined and is therefore operationally down.
c. Why did the router not use the same path for both?
Standby must use a link outside of the link group used by the primary path.
STOP: Wait for everyone to complete the preceding steps before continuing.
8. Once all pods have completed the steps 1 through 7, remove the CORE diagonal links from the
orange SRLG group and create a new blue SRLG group on all CORE and EDGE routers with a
value of 2. Place the CORE cross-connected interfaces in this new group.
*A:MPLSv2_R1# configure router mpls srlg-group blue value 2
*A:MPLSv2_R1# configure router mpls interface "toR4" no srlg-group "orange"
*A:MPLSv2_R1# configure router mpls interface "toR4" srlg-group "blue"
NOTE: If assigning one interface to an SRLG, assign them all. Though the secondary standby can come
up if only some links are SRLG members, this behavior is unpredictable, and in some cases the primary
and standby end up sharing links. Best practice is to define link SRLG memberships throughout the
MPLS domain.
9. Shut down, then turn up (no shutdown) your LSP. Again, verify the LSP status.
*A:MPLSv2_R5# configure router mpls lsp "toR8-5" no shutdown
===============================================================================
===============================================================================
Legend :
s - Soft Preemption
===============================================================================
-------------------------------------------------------------------------------
LSP toR8-5 Path primary-toR8
-------------------------------------------------------------------------------
From : 10.10.10.5 To : 10.10.10.8
Path Name : primary-toR8 Path Type : Primary


Backup CT : None
MainCT Retry: n/a
Rem :
MainCT Retry: 0
Limit :
None None
None None

Preference : n/a
ExplicitHops:
No Hops Specified
Actual Hops :
10.1.5.5(10.10.10.5) Record Label : N/A
-> 10.1.5.1(10.10.10.1) Record Label : 131042
-> 10.1.4.4(10.10.10.4) Record Label : 131044
-> 10.4.8.8(10.10.10.8) Record Label : 131060
ComputedHops:
10.1.5.5(S) -> 10.1.5.1(S) -> 10.1.4.4(S)
-> 10.4.8.8(S)
ResigEligib*: False
-------------------------------------------------------------------------------
LSP toR8-5 Path secondary-toR8
-------------------------------------------------------------------------------
From : 10.10.10.5 To : 10.10.10.8
Path Name : secondary-toR8 Path Type : Standby


None None
None None

Preference : 255
ExplicitHops:
No Hops Specified
Actual Hops :
10.1.5.5(10.10.10.5) Record Label : N/A
-> 10.1.5.1(10.10.10.1) Record Label : 131040
-> 10.1.3.3(10.10.10.3) Record Label : 131040
-> 10.3.4.4(10.10.10.4) Record Label : 131042
-> 10.4.8.8(10.10.10.8) Record Label : 131059
ComputedHops:
10.1.5.5(S) -> 10.1.5.1(S) -> 10.1.3.3(S)
-> 10.3.4.4(S) -> 10.4.8.8(S)
Srlg : Enabled
SrlgDisjoint: True
ResigEligib*: False
===============================================================================
a. Does the primary path change?
No; it still follows the IGP best path.
b. What happens to the standby path?
The head-end router resignals the standby over one of the outer ring paths, which are
disjoined (orange) from the diagonal link path (blue).
10. On your CORE router, view the SRLG membership information the router advertises in opaque
LSAs.
===============================================================================
===============================================================================
-------------------------------------------------------------------------------
Opaque LSA
-------------------------------------------------------------------------------
Sequence No : 0x80000092 Checksum : 0xee90
Options : E
Advertisement :
ROUTER-ID TLV (0001) Len 4 : 10.10.10.1
-------------------------------------------------------------------------------
Opaque LSA
-------------------------------------------------------------------------------
Sequence No : 0x8000000a Checksum : 0x77a4
Options : E
Advertisement :
Sub-TLV: 16 Len: 4 SRLG_LIST :
Num SRLGs: 1
1
-------------------------------------------------------------------------------
Opaque LSA
-------------------------------------------------------------------------------
Sequence No : 0x8000012d Checksum : 0xa250
Options : E
Advertisement :
Num SRLGs: 1
1
-------------------------------------------------------------------------------
Opaque LSA
-------------------------------------------------------------------------------
Sequence No : 0x8000013d Checksum : 0x13c5
Options : E
Advertisement :
Num SRLGs: 1
2
-------------------------------------------------------------------------------
Opaque LSA
-------------------------------------------------------------------------------
Sequence No : 0x80000137 Checksum : 0x6f96
Options : E
Advertisement :
===============================================================================
6.3. FRR Facility Backup Protection
Figure 6-3: Enabling FRR Facility Bypass Protection
Exercise
Figure 6-3 shows the primary LSPs from pod 3s perspective. Each pod will create two strict path LSPs,
one from their EDGE to the diagonally opposite EDGE, and another from their CORE to the diagonally
opposite CORE router, both transiting the clockwise CORE router. For example, if you are on pod 3s
EDGE router, then this LSP originates at router R7, travels clockwise through routers R3, R1, and R2,
and terminates on router R6.
1. On your CORE and EDGE routers, create the paths to the corresponding diagonally opposite
routers (CORE to CORE and EDGE to EDGE). Use strict hops including each downstream router
and go in the clockwise direction. An example is shown in Figure 6-3.
The configurations on routers R1 and R5 are shown in step 2.
2. Create the LSPs "toRx-6" using the paths you just created as primary paths. Enable facility FRR
on the LSP. Enable CSFP on the LSPs but do not configure any constraints on the LSPs (allocate
bandwidth, hop-limit, or admin-group inclusion/exclusion).
----------------------------------------------
exit
path "toR4-strict"
hop 10 10.10.10.2 strict
hop 20 10.10.10.4 strict
no shutdown
exit
lsp "toR4-6"
to 10.10.10.4
cspf
fast-reroute facility
exit
primary "toR4-strict"
exit
no shutdown
exit
no shutdown
----------------------------------------------

----------------------------------------------
exit
path "toR8-strict"
hop 10 10.10.10.1 strict
hop 20 10.10.10.2 strict
hop 30 10.10.10.4 strict
hop 40 10.10.10.8 strict
no shutdown
exit
lsp "toR8-6"
to 10.10.10.8
cspf
fast-reroute facility
exit
primary "toR8-strict"
exit
no shutdown
exit
----------------------------------------------
3. On your EDGE router, verify that your LSP is making use of the correct path and that the hops
are accurately represented.
===============================================================================
===============================================================================
Legend :
s - Soft Preemption
===============================================================================
-------------------------------------------------------------------------------
LSP toR8-6 Path toR8-strict
-------------------------------------------------------------------------------
From : 10.10.10.5 To : 10.10.10.8
Path Name : toR8-strict Path Type : Primary

FRR : Enabled Oper FRR : Enabled
FRR NodePro*: Enabled Oper FRR NP : Enabled
FR Hop Limit: 16 Oper FRHopL*: 16

Backup CT : None
MainCT Retry: n/a
Rem :
MainCT Retry: 0
Limit :
None None
None None

Preference : n/a
ExplicitHops:
10.10.10.1(S) -> 10.10.10.2(S) -> 10.10.10.4(S)
-> 10.10.10.8(S)
Actual Hops :
10.1.5.5(10.10.10.5) Record Label : N/A
-> 10.1.5.1(10.10.10.1) @ n Record Label : 131034
-> 10.1.2.2(10.10.10.2) @ Record Label : 131036
-> 10.2.4.4(10.10.10.4) Record Label : 131039
-> 10.4.8.8(10.10.10.8) Record Label : 131059
ComputedHops:
10.1.5.5(S) -> 10.1.5.1(S) -> 10.1.2.2(S)
-> 10.2.4.4(S) -> 10.4.8.8(S)
ResigEligib*: False
===============================================================================
a. Which routers use node backup?

Your CORE router uses node protection to protect the LSP against failure of the down
stream node (the clockwise CORE router).
b. Which routers use link backup?
Both your CORE router and the clockwise CORE router use link protection to protect the
LSP against failure of the next hop link (the link between your CORE router and the
clockwise CORE router, and between the clockwise CORE router and the tail-end).
4. On your CORE router, use the show router mpls bypass-tunnel protected-lsp
detail command to confirm that both protected LSPs are backed up by the one bypass tunnel.
*A:MPLSv2_R1# show router mpls bypass-tunnel protected-lsp detail
===============================================================================
MPLS Bypass Tunnels (Detail)
===============================================================================
-------------------------------------------------------------------------------
bypass-node10.10.10.2
-------------------------------------------------------------------------------
To : 10.1.4.4 State : Up
Out I/F : 1/1/4 Out Label : 131033
Up Time : 0d 00:22:11 Active Time : n/a
Reserved BW : 0 Kbps Protected LSP Count : 2
Type : Dynamic
Setup Priority : 7 Hold Priority : 0
Class Type : 0
Actual Hops :
10.1.4.1(S) -> 10.1.4.4(S)
Protected LSPs -
LSP Name : toR4-6::toR4-strict
From : 10.10.10.1 To : 10.10.10.4
Avoid Node/Hop : 10.10.10.2 Downstream Label : 131035
Bandwidth : 0 Kbps

From : 10.10.10.5 To : 10.10.10.8
Bandwidth : 0 Kbps
-------------------------------------------------------------------------------
bypass-link10.1.2.2
-------------------------------------------------------------------------------
To : 10.2.3.2 State : Up
Out I/F : 1/1/3 Out Label : 131035
Up Time : 0d 00:19:28 Active Time : n/a
Reserved BW : 0 Kbps Protected LSP Count : 2
Type : Dynamic
Setup Priority : 7 Hold Priority : 0
Class Type : 0
Actual Hops :
10.1.3.1(S) -> 10.1.3.3(S) -> 10.2.3.2(S)
Protected LSPs -
From : 10.10.10.3 To : 10.10.10.2
Bandwidth : 0 Kbps

From : 10.10.10.7 To : 10.10.10.6
Bandwidth : 0 Kbps
===============================================================================
a. Which LSPs do the bypass tunnels protect?
The bypass-node tunnel protects the two LSPs you configured on your EDGE and CORE
routers. The bypass-link tunnel protects the two LSPs configured on the CORE and EDGE
routers in the pod that is counter-clockwise from yours.
b. What path does each bypass tunnel take?
The bypass-node tunnel should follow the direct path to the diagonally connected CORE
router. The bypass-link tunnel follows the path via the diagonally connected CORE router.
5. On your CORE router, view the RSVP session for the bypass tunnel.
*A:MPLSv2_R1# show router rsvp session bypass-tunnel
===============================================================================
RSVP Sessions
===============================================================================
ID ID
-------------------------------------------------------------------------------
10.10.10.1 10.1.4.4 61441 4 bypass-node10.10.10.2 Up
10.10.10.1 10.2.3.2 61444 6 bypass-link10.1.2.2 Up
-------------------------------------------------------------------------------
Sessions : 2
===============================================================================
a. Which router is the PLR?
The PLR is the router in the From field (in this example 10.10.10.1 or router R1)
b. Which router is the MP?
The MP is the router shown in the "To" field (in this example 10.1.4.4, or router R4 for the
bypass-node tunnel, and 10.2.3.2, or R2 for the bypass-link tunnel).
6. On your CORE router, use the show router rsvp session bypass-tunnel detail
command to discover more specific information about your bypass tunnel.
*A:MPLSv2_R1# show router rsvp session bypass-tunnel detail
===============================================================================
RSVP Sessions (Detailed)
===============================================================================
-------------------------------------------------------------------------------
LSP : bypass-node10.10.10.2
-------------------------------------------------------------------------------
From : 10.10.10.1 To : 10.1.4.4
Tunnel ID : 61441 LSP ID : 4
Style : FF State : Up
Session Type : Bypass Tunnel
In Interface : n/a Out Interface : 1/1/4
In Label : n/a Out Label : 131033
Previous Hop : n/a Next Hop : 10.1.4.4
Class Type : 0
SubGrpOrig ID : 0 SubGrpOrig Addr:
P2MP ID : 0
FrrAvailType : N/A
FrrSrlgStrict : N/A
SrlgDisjoint : N/A
Path Recd : 0 Path Sent : 60

Resv Recd : 61 Resv Sent : 0
Summary msgs: :
SPath Recd : 0 SPath Sent : 0
SResv Recd : 0 SResv Sent : 0
-------------------------------------------------------------------------------
LSP : bypass-link10.1.2.2
-------------------------------------------------------------------------------
From : 10.10.10.1 To : 10.2.3.2
Style : FF State : Up
Session Type : Bypass Tunnel
Class Type : 0
P2MP ID : 0
FrrAvailType : N/A
FrrSrlgStrict : N/A
SrlgDisjoint : N/A

Summary msgs: :
===============================================================================
a. What is the style type of the Bypass tunnel?

The reservation style of the bypass tunnel is Fixed Filter
b. Why is there only one Out label displayed?
A bypass tunnel uses only one label to represent many primary tunnels because label
stacking is being used.
NOTE: In steps 7 to 9, one pod at a time should shut down its CORE interface to the
clockwise pod. Let the user of the clockwise neighbor pod know when you have completed
step 9. The interface should be turned back up before the next pod proceeds with the
exercise.
7. Ask the person working on the CORE router clockwise from you to shut down the interface
leading away from you towards your LSPs' tail-ends. For example, if you are on pod 1, the
person on pod 2 should shutdown the interface between routers R2 and R4.
8. Verify that the LSPs you configured on your EDGE and CORE routers are using the bypass tunnel
with the show router mpls lsp path detail command, and by performing an lsp-trace.
===============================================================================
===============================================================================
Legend :
s - Soft Preemption
===============================================================================
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
From : 10.10.10.5 To : 10.10.10.8


Backup CT : None
MainCT Retry: n/a
Rem :
MainCT Retry: 0
Limit :
None None
None None

Preference : n/a
Failure Code: tunnelLocallyRepaired Failure Node: 10.10.10.2
ExplicitHops:
10.10.10.1(S) -> 10.10.10.2(S) -> 10.10.10.4(S)
-> 10.10.10.8(S)
Actual Hops :
10.1.5.5(10.10.10.5) Record Label : N/A
-> 10.1.5.1(10.10.10.1) @ n Record Label : 131030
-> 10.1.2.2(10.10.10.2) @ # Record Label : 131037
-> 10.2.4.4(10.10.10.4) Record Label : 131042
-> 10.4.8.8(10.10.10.8) Record Label : 131059
ComputedHops:
10.1.5.5(S) -> 10.1.5.1(S) -> 10.1.2.2(S)
-> 10.2.4.4(S) -> 10.4.8.8(S)
ResigEligib*: False
In Prog MBB :
MBB Type : GlobalRevert NextRetryIn : 1 sec
FailureCode: noError Failure Node: n/a
Signaled BW: 0 Mbps
===============================================================================

NOTE: You might see your CORE router twice in the lsp-trace (as can be seen above). This happens
when the bypass-tunnel originating on the PLR transits your CORE router.
9. Ask the user of the clockwise pod to turn up the interface that was shut down in step 7. The
user on the next pod can now proceed with steps 7 to 9.
6.4. FRR One-to-One Protection
Figure 6-4: Enabling FRR One-to-One Protection
Exercise
This lab re-uses the two LSPs created in the previous lab (one LSP from your EDGE router to the EDGE
router of the diagonally connected Pod, and one LSP from your CORE router to the CORE router of the
diagonally connected pod.
1. Change both LSPs fast reroute configuration to one-to-one.
*A:MPLSv2_R1# configure router mpls lsp "toR4-6" fast-reroute one-to-one
2. Verify that your LSPs are using the correct paths and that the hops are as you defined them in
the strict paths.
===============================================================================
===============================================================================
Legend :
s - Soft Preemption
===============================================================================
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
From : 10.10.10.5 To : 10.10.10.8


Backup CT : None
MainCT Retry: n/a
Rem :
MainCT Retry: 0
Limit :
None None
None None

Preference : n/a
ExplicitHops:
10.10.10.1(S) -> 10.10.10.2(S) -> 10.10.10.4(S)
-> 10.10.10.8(S)
Actual Hops :
10.1.5.5(10.10.10.5) Record Label : N/A
-> 10.1.5.1(10.10.10.1) @ n Record Label : 131039
-> 10.1.2.2(10.10.10.2) @ Record Label : 131043
-> 10.2.4.4(10.10.10.4) Record Label : 131064
-> 10.4.8.8(10.10.10.8) Record Label : 131070
ComputedHops:
10.1.5.5(S) -> 10.1.5.1(S) -> 10.1.2.2(S)
-> 10.2.4.4(S) -> 10.4.8.8(S)
ResigEligib*: False
===============================================================================
a. Which routers show a Detour Available?
Your CORE router and the CORE router of the clockwise pod.
b. Which routers show Node Protect?
Only your CORE router should show Node Protect (the router with a n symbol).
3. On your CORE router, use the show router mpls lsp transit to see the full list of LSPs
transiting your CORE router.
*A:MPLSv2_R1# show router mpls lsp transit
===============================================================================
MPLS LSPs (Transit)
===============================================================================
===============================================================================
-------------------------------------------------------------------------------
10.10.10.7 10.10.10.5 1/1/2 1/1/1 Up toR5-3::loose
10.10.10.5 10.10.10.7 1/1/1 1/1/2 Up toR7-3::loose
10.10.10.5 10.10.10.6 1/1/1 1/1/2 Up toR6-1::loose
10.10.10.5 10.10.10.4 1/1/1 1/1/2 Up toR4-4::toR4strict
10.10.10.5 10.10.10.4 1/1/1 1/1/4 Up toR4-4::loose
10.10.10.8 10.10.10.5 1/1/4 1/1/1 Up toR5-3::loose
10.10.10.5 10.10.10.8 1/1/1 1/1/4 Up toR8-3::loose
10.10.10.8 10.10.10.5 1/1/4 1/1/1 Up toR5-5::primary-toR5
10.10.10.5 10.10.10.8 1/1/1 1/1/4 Up toR8-5::primary-toR8
10.10.10.5 10.10.10.8 1/1/1 1/1/2 Up toR8-5::secondary-toR8
10.10.10.8 10.10.10.5 1/1/2 1/1/1 Up toR5-5::secondary-toR5
10.10.10.7 10.10.10.2 1/1/3 1/1/2 Up toR2-4::toR2strict
10.10.10.7 10.10.10.5 1/1/3 1/1/1 Up toR5-1::loose
10.10.10.4 10.10.10.3 1/1/2 1/1/3 Up toR3-1::loose
10.10.10.5 10.10.10.8 1/1/1 1/1/2 Up toR8-6::toR8-strict
10.10.10.6 10.10.10.7 1/1/4 1/1/3 Up toR7-6::toR7-strict_de*
10.10.10.7 10.10.10.6 1/1/3 1/1/2 Up toR6-6::toR6-strict
10.10.10.8 10.10.10.5 1/1/3 1/1/1 Up toR5-6::toR5-strict
10.10.10.3 10.10.10.2 1/1/3 1/1/2 Up toR2-6::toR2-strict
-------------------------------------------------------------------------------
LSPs : 19
-------------------------------------------------------------------------------
4. On your CORE router, use the show router mpls lsp transit lsp-name <lsp name>
detail command to view more details regarding the LSP generating on your EDGE router. This
command provides more information regarding the LSPs transiting this router, and may be used
for LSP troubleshooting.
*A:MPLSv2_R1# show router mpls lsp transit lsp-name toR8-6::toR8-strict detail
===============================================================================
===============================================================================
-------------------------------------------------------------------------------
LSP toR8-6::toR8-strict
-------------------------------------------------------------------------------
From : 10.10.10.5 To : 10.10.10.8
State : Up
Class Type : 0
DetourStatus : Standby DetourType : Originate
DetourAvoidNode/Hop : 10.10.10.2 DetourOrigin : 10.10.10.1
Class Type : 0
DetourActiveTime : n/a DetourUpTime : 0d 10:20:12
InInterface : n/a InLabel : n/a
OutInterface : 1/1/4 OutLabel : 131054
NextHop : 10.1.4.4
ExplicitHops :
10.1.4.1(S) -> 10.1.4.4(S) -> 10.4.8.8(S)
DetourStatus : Up DetourType : Terminate

DetourAvoidNode/Hop : 10.2.4.4 DetourOrigin : 10.10.10.2
Class Type : 0
InInterface : 1/1/2 InLabel : 131049
PreviousHop : 10.1.2.2
===============================================================================
a. Which inbound interface does your LSP use? Which outbound interface does it use?
The inbound interface is the interface pointing towards your EDGE router, while the
outbound interface is the interface pointing towards the clockwise CORE router.
b. Which inbound interface does your detour use? Which outbound interface does it use?
The inbound interface does not change. The outbound interface is now pointing towards
the diagonal CORE router. Other pods will have different interfaces.Is your CORE router
part of a node or hop detour for the LSP that you configured? How do you know?
This router is being used by the detour as part of a node protection. The address being
used is the system address of the CORE router of the pod in the clockwise direction from
your pod (the router in transit). Also, the detour path defines the out interface as an
interface leading away from the CORE node (the node being protected).
c. For which LSPs are the other detours shown generated?
The router also contains detours from LSPs created by other pods. For example, router R1
has originating detours for the LSP from pod 3 to pod 2 (R3 to R2 and R7 to R6). There are
also terminating detours for LSPs from pod 3 to pod 1 (R4 to R1 and R8 to R5). There could
also be a transiting detour for the LSP from pod 1 to pod 4 (R1 to R4 and R5 to R8).
Detailed information on all detours is shown in the next step.
5. On your CORE router, use the show router rsvp session detail command to view all
the RSVP sessions established on the router for every LSP and detour LSP originating, transiting,
or terminating on it. This command gives similar information as the show router mpls lsp
[transit | terminate] command. You should be able to see all detours using your CORE
router.
An example is shown below (truncated for simplicity).
-------------------------------------------------------------------------------
LSP : toR8-6::toR8-strict
-------------------------------------------------------------------------------
From : 10.10.10.5 To : 10.10.10.8
Style : SE State : Up
Session Type : Transit
In Interface : 1/1/1 Out Interface : 1/1/2
In Label : 131039 Out Label : 131043
Class Type : 0
P2MP ID : 0
FrrAvailType : Detour
FrrSrlgStrict : N/A
SrlgDisjoint : N/A
Summary msgs: :
-------------------------------------------------------------------------------
LSP : toR8-6::toR8-strict_detour
-------------------------------------------------------------------------------
From : 10.10.10.5 To : 10.10.10.8
Session Type : Originate (Detour)
Class Type : 0
P2MP ID : 0
FrrAvailType : N/A
FrrSrlgStrict : N/A
SrlgDisjoint : N/A

Summary msgs: :
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
From : 10.10.10.5 To : 10.10.10.8
Session Type : Terminate (Detour)
Class Type : 0
P2MP ID : 0
FrrAvailType : N/A
FrrSrlgStrict : N/A
SrlgDisjoint : N/A

Summary msgs: :
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
From : 10.10.10.6 To : 10.10.10.7
Session Type : Transit (Detour)
Class Type : 0
P2MP ID : 0
FrrAvailType : N/A
FrrSrlgStrict : N/A
SrlgDisjoint : N/A
Summary msgs: :
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
From : 10.10.10.7 To : 10.10.10.6
Class Type : 0
P2MP ID : 0
FrrSrlgStrict : N/A
SrlgDisjoint : N/A

Summary msgs: :
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
From : 10.10.10.8 To : 10.10.10.5
Class Type : 0
P2MP ID : 0
FrrAvailType : N/A
FrrSrlgStrict : N/A
SrlgDisjoint : N/A

Summary msgs: :
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
From : 10.10.10.8 To : 10.10.10.5
Class Type : 0
P2MP ID : 0
FrrAvailType : N/A
FrrSrlgStrict : N/A
SrlgDisjoint : N/A

Summary msgs: :
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
From : 10.10.10.7 To : 10.10.10.6
Class Type : 0
P2MP ID : 0
FrrAvailType : N/A
FrrSrlgStrict : N/A
SrlgDisjoint : N/A

Summary msgs: :
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
From : 10.10.10.8 To : 10.10.10.5
Class Type : 0
P2MP ID : 0
FrrAvailType : N/A
FrrSrlgStrict : N/A
SrlgDisjoint : N/A

Summary msgs: :
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
From : 10.10.10.1 To : 10.10.10.4
Session Type : Originate
Hops :
10.10.10.2(S) -> 10.10.10.4(S)
Class Type : 0
P2MP ID : 0
FrrSrlgStrict : N/A
SrlgDisjoint : N/A

Summary msgs: :
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
From : 10.10.10.1 To : 10.10.10.4
Session Type : Transit (Detour)
Class Type : 0
P2MP ID : 0
FrrAvailType : N/A
FrrSrlgStrict : N/A
SrlgDisjoint : N/A

Summary msgs: :
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
From : 10.10.10.1 To : 10.10.10.4
Class Type : 0
P2MP ID : 0
FrrAvailType : N/A
FrrSrlgStrict : N/A
SrlgDisjoint : N/A

Summary msgs: :
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
From : 10.10.10.3 To : 10.10.10.2
Class Type : 0
P2MP ID : 0
FrrAvailType : N/A
FrrSrlgStrict : N/A
SrlgDisjoint : N/A

Summary msgs: :
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
From : 10.10.10.3 To : 10.10.10.2
Class Type : 0
P2MP ID : 0
FrrAvailType : N/A
FrrSrlgStrict : N/A
SrlgDisjoint : N/A

Summary msgs: :
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
From : 10.10.10.4 To : 10.10.10.1
Session Type : Terminate
In Interface : 1/1/3 Out Interface : n/a
In Label : 131030 Out Label : n/a
Previous Hop : 10.1.3.3 Next Hop : n/a
Class Type : 0
P2MP ID : 0
FrrAvailType : N/A
FrrSrlgStrict : N/A
SrlgDisjoint : N/A

Summary msgs: :
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
From : 10.10.10.4 To : 10.10.10.1
In Interface : 1/1/4 Out Interface : n/a
In Label : 131029 Out Label : n/a
Previous Hop : 10.1.4.4 Next Hop : n/a
Class Type : 0
P2MP ID : 0
FrrAvailType : N/A
FrrSrlgStrict : N/A
SrlgDisjoint : N/A

Summary msgs: :
===============================================================================
You can now identify the LSPs and detours on your CORE router and to which LSP each
detour belongs, and where these detours terminate.
NOTE: In steps 6 to 8, one pod at a time should shut down its CORE interface to the
clockwise pod. Let the user of the clockwise neighbor pod know when you have completed
step 8. The interface should be turned back up before the next pod proceeds with the
exercise.
6. Ask the person working on the CORE router clockwise from you to shut down the interface
leading away from you towards your LSPs' tail-ends. For example, if you are on pod 1, the
person on pod 2 should shut down the interface between routers R2 and R4.
7. Verify that the LSPs you configured on your EDGE and CORE routers are using the detour with
the show router mpls lsp path detail command and by performing an lsp-trace.
===============================================================================
===============================================================================
Legend :
s - Soft Preemption
===============================================================================
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
From : 10.10.10.5 To : 10.10.10.8


Backup CT : None
MainCT Retry: n/a
Rem :
MainCT Retry: 0
Limit :
None None
None None

Preference : n/a
Failure Code: tunnelLocallyRepaired Failure Node: 10.10.10.2
ExplicitHops:
10.10.10.1(S) -> 10.10.10.2(S) -> 10.10.10.4(S)
-> 10.10.10.8(S)
Actual Hops :
10.1.5.5(10.10.10.5) Record Label : N/A
-> 10.1.5.1(10.10.10.1) @ n Record Label : 131039
-> 10.1.2.2(10.10.10.2) @ # Record Label : 131043
-> 10.1.2.1(10.10.10.1) Record Label : 131049
-> 10.1.4.4(10.10.10.4) Record Label : 131054
-> 10.4.8.8(10.10.10.8) Record Label : 131070
ComputedHops:
10.1.5.5(S) -> 10.1.5.1(S) -> 10.1.2.2(S)
-> 10.2.4.4(S) -> 10.4.8.8(S)
ResigEligib*: False
In Prog MBB :
MBB Type : GlobalRevert NextRetryIn : 19 sec
FailureCode: noCspfRouteToDestination Failure Node: 10.10.10.5
Signaled BW: 0 Mbps
===============================================================================

NOTE: You might see your CORE router twice in the lsp-trace (as can be seen above). This happens
when the bypass-tunnel originating on the PLR transits your CORE router.
8. Ask the user of the clockwise pod to turn up the interface that was shut down in step 6. The
user on the next pod can now proceed with steps 6 to 8.

1. Can you configure a primary path with strict hops, and a secondary path with no hops
specified? What might be a consequence of performing this action?
Yes. The secondary path will be determined based on IGP shortest path and thus could
potentially use some of the same resources (links or nodes) as the primary path, in which
case it will not be completely physically diverse. However, if a network failure affects
both the primary and secondary paths, the head-end router will recompute another route
for the secondary path, if one exists. (Remember that the secondary path is loose).
2. Do the primary and secondary paths of an LSP use the same label at the destination router?
No. Each LSP path is signaled separately and therefore makes its own label requests.
3. What is the difference between a secondary path and a standby secondary path?
A secondary path configured as standby is signaled and established and ready for use as
soon as the primary path fails. A secondary path that is not in standby must first be
signaled and established after the primary path fails.
4. Does the label stack grow when a bypass tunnel is used?
Yes. When the labeled packet reaches the PLR and is forwarded into a bypass tunnel, the
PLR PUSHes a new label corresponding to the bypass tunnel onto the stack.
5. How does each router compute its detour for a given LSP?
The router determines the bypass tunnel by finding the least cost path to the next-hop
router (in the case of link protection) or the next-next-hop router (in the case of node
protection) while avoiding the next-hop node or link. If the path computed by the PLR
intersects a router that is on the protected LSPs original path, then the bypass tunnel
terminates on that router, and does not terminate on the next-hop or next-next-hop
router.
6. If an LSP is created from your EDGE router to the EDGE router in the pod that is clockwise from
yours, will it be protected by the bypass tunnel created by your CORE router for the two LSPs
created in this lab?
No, because the bypass tunnel created from the previous lab does node protection and
thus avoids the clockwise pods CORE router entirely. Your CORE router will create
another bypass tunnel to avoid the next-hop link, to protect this LSP.
7. Does the label stack grow when a detour LSP is used?
No.
8. What happens when node protection is requested but a given router cannot find a path that
avoids the next-hop node?
The router will still attempt to compute a detour, which avoids the next-hop link.
9. How does each router compute its detour for a given LSP?
The router determines the detour LSP by finding the least cost path to the destination
router (i.e. termination point of the protected LSP),while avoiding the next-hop node or
link.
10. When using SRLGs, what happens to a secondary path if the head-end router cannot find a path
that is disjoined from the primary path?
The secondary path stays operationally down.
http: / /www.alcatel-lucent.com/src

2015-09-04.MPLS LabGuide Ver2.2

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

2015-09-04.MPLS LabGuide Ver2.2

Hochgeladen von

Copyright:

Verfügbare Formate

May, 2015

LAB 3 MPLS INFRASTRUCTURE AND LDP CONFIGURATION .........................................................4

Figure 3-1: Lab Topology Overview

Lab 3 Command list

A:MPLS_R1# telnet <management ip address>

A:MPLS_R1# show router ldp discovery [detail]

Pod Number Management Address

Pod 1 CORE (R1)

2. Familiarize yourself with lab topology, shown in Figure 3-1.

Interface name toRy = where y is the opposite routers router

On your EDGE router, the LDP configuration should look like:

3. Verify that your routers LDP sessions show Established.

b. How many LDP sessions does your EDGE router have?

c. What types of adjacencies do your routers form? Why?

*A:MPLSv2_R1# show router ldp bindings

*A:MPLSv2_R1# show router ldp bindings active

6. Verify the LSPs that are present.

a. For which FECs has your router created LSPs?

*A:MPLSv2_R1# show router ldp bindings active

*A:MPLSv2_R5# show router ldp bindings active

4. View your CORE and EDGE router LIBs.

5. View the LFIBs.

*A:MPLSv2_R1# show router ldp bindings active

*A:MPLSv2_R1# show router tunnel-table

ldp-treetrace for Prefix 10.10.10.4/32:

10.3.4.4, ttl = 2 dst = 127.2.0.255 rc = EgressRtr status = Done

10.2.4.4, ttl = 2 dst = 127.1.0.255 rc = EgressRtr status = Done

ldp-treetrace discovery state: Done

*A:MPLSv2_R1# oam ldp-treetrace prefix 10.10.10.8/32

ldp-treetrace for Prefix 10.10.10.8/32:

10.4.8.8, ttl = 3 dst = 127.1.0.255 rc = EgressRtr status = Done

10.4.8.8, ttl = 3 dst = 127.2.0.255 rc = EgressRtr status = Done

ldp-treetrace discovery state: Done

*A:MPLSv2_R1# configure router policy-options

4. View the LIBs.

a. What additional FECs do your routers now generate labels for?

5. View the LFIBs.

*A:MPLSv2_R1# show router ldp bindings active

Lab 3 Review Questions

Figure 4-1: IGP based LSPs

A:MPLS_R1# configure router mpls no shutdown

3. Verify that RSVP is enabled on your interfaces.

---- LSP toR5-1 PING Statistics ----

*A:MPLSv2_R1# oam lsp-trace "toR5-1"

Lab 4 Review Questions

Lab 5 Command list

A:MPLS_R1# configure router interface shutdown

A:MPLS_R1# configure router ospf rsvp-shortcut

Phase I Enable and verify CSPF

A:MPLSv2_R1# show router ospf opaque-database

a. How many Type 10 LSAs do your routers report?

a. How many Type 10 LSAs do you see?

*A:MPLSv2_R1# show router ospf status

*A:MPLSv2_R1# show router ospf opaque-database

*A:MPLSv2_R1# show router mpls interface

Admin Group Sub TLV: 00000006 (6)

*A:MPLSv2_R1# show router mpls lsp "toR2-1" path detail

Adspec : Disabled Oper Adspec : Disabled

Neg MTU : 1564 Oper MTU : 1564

Adaptive : Enabled Oper Metric : 100

a. Does the LSP follow the IGP-chosen best path? Why?

*A:MPLSv2_R1# show router mpls lsp "toR2-1" path detail

Adspec : Disabled Oper Adspec : Disabled