MPLS
IP has a limited ability to alleviate hyper aggregation which leads to
network and link congestion
All network traffic will flow via the primary path
No traffic will use the Alternate Link Inefficient use of resources
Alternate
Link
IGP
7750 Service Router
All Rights Reserved Alcatel-Lucent 2007
Alcatel-Lucent Services Implementation Course
Benefits of MPLS
MPLS Overview 613
Congestion
IGP PATH
Exclude this
link
MPLS PATH
Explicitly define the path or use any IGP
LSR
LSR
LSR
LER LSR
LER
Push Swap Swap Pop
Frame header Single Label
Label Stack
4 Octets
Label Stack TTL
Label Exp. S
Entry Format
Label: Label Value, 20 bits
Exp.: Experimental, 3 bits (Class of Service)
S: Bottom of Stack, 1 bit (1 = last entry in label stack)
TTL: Time to Live, 8 bits
A:SR2# show router mpls label-range
==============================================================================
Label Ranges
==============================================================================
Label Type Start Label End Label Aging Total Available
------------------------------------------------------------------------------
Static-lsp 32 1023 - 992
Static-svc 2048 18431 - 16384
Dynamic 32768 131071 0 98291
==============================================================================
Type = IP Type = IP
DA SA Payload FCS DA SA Payload
0800 0800 FCS
IS-IS
RIP
Distance Vector OSPF
Link State
Static Dynamic
LDP RSVP-TE
IGP Based IGP or CSPF based
Static LSPs are manually configured on each LER/LSR
Disadvantages:
Labour intensive operation
Changes need a reconfiguration on every node
No back-up or fast re-route
No support of label stacking
1.1.1.1/32 2.2.2.2/32
iLER LSR2
10.23.1.3
Static LSP
Static LSP
eLER
3.3.3.3/32
LSR3
4.4.4.4/32
LSPs are established dynamically using a label distribution protocol: LDP
LSR 1 Prefix Ingress Egress Egress next-
LFIB Label Label Interface hop Dynamic Label
10.2.1.0/24 131067 131071 1/1/4 LER 2 Exchange
LSR 2 1/1/1
1/1/4 10.2.1.0/24
LER 1
1/1/2 1/1/2
1/1/1
1/1/1 1/1/3
LSR 2 Prefix Ingress Egress Egress next-
LFIB Label Label Interface hop
10.2.1.0/24 131069 131071 1/1/2 LER 2
Control Plane
LABEL
(System Address)
Data packets flow in the downstream direction
Control driven model
Label bindings are formed before the arrival of user generated data packets
Alcatel-Lucent products use the control driven model
Label bindings are distributed from the downstream to the upstream direction
Table Meaning Contents Populated By
Name
RIB Routing Information Base Routing updates received Routing Protocol Exchange - Each routing
protocol has a separate RIB
FIB Forwarding Information Active routes RTM selects the active routes from all
Base protocol "Best" routes
LIB Label Information Base Locally generated and MPLS Label Exchange
received MPLS labels
LFIB Label Forwarding Labels used by the LSR The labels assigned to the active routes (for
Information Base each next-hop)
RIB OSPF
FIB
RIB IS-IS
LFIB
LIB LDP
Unsolicited:
1.1.1.1/32 FEC: 10.2.1.0/24
Label mappings are provided to all peers Label: 131065
2.2.2.2/32
iLER LSR2
for which the local LSR might be a next-
hop for a given FEC, even when not
explicitly requested.
FEC: 10.2.1.0/24
FEC: 10.2.1.0/24
Label: 131067
Label: 131066
10.2.1.0/24
LSR3
eLER
4.4.4.4/32 FEC: 10.2.1.0/24
3.3.3.3/32
Label: 131067
Liberal Retention:
Ordered Control:
The label received from the router An LSR only propagates a label for a FEC
providing the active IGP route for once it has a label mapping from the
the FEC is used and the other labels FEC next-hop.
are kept Label
2.2.2.2/32
131065
1.1.1.1/32 LSR2
iLER Prefix Next-hop Label iLER Step 2
LIB
Step 2
Label
Step 1
131066 131067
iLER Prefix Next-hop
FIB
10.2.1.0/24 LSR 3
10.2.1.0/24
iLER Prefix Next-hop Label
LFIB
Step 1
10.2.1.0/24 LSR 3 131066 LSR3 eLER
Label
4.4.4.4/32 3.3.3.3/32
131067
Each LSR will originate a label for its system address by default
Each LSR may originate a label for a FEC for which it has a next-hop
that is external to the MPLS domain: an export policy is needed !
LSR 1 Prefix Ing. Egr. Egr. Next-hop LSR 4 Prefix Ing. Egr. Egr. Next-hop
LFIB Label Label Intf LFIB Label Label Intf
Control Plane
1.1.1.1/32 2.2.2.2/32
iLER LSR2
LSR 1 Prefix Next-hop Label
LIB
1/1/2
10.2.1.0/24 LSR 2 131065
10.2.1.0/24 LSR 3 131066
1/1/3
LER 1 Prefix Next-hop Interface
FIB
10.2.1.0/24 LSR 2 1/1/2
10.2.1.0/24 LSR 3 1/1/3
10.2.1.0/24
LER 1 Prefix Ing. Egr. Egr. Next-hop
LFIB Label Label Intf
LSR3 eLER
10.2.1.0/24 - 131065 1/1/2 LSR2
4.4.4.4/32 3.3.3.3/32
10.2.1.0/24 - 131066 1/1/3 LSR3
PE1 P1 P2
PE2
Provider
Network
PE-3
P3
P1# configure router
P1>config>router# ldp
P1>config>router>ldp# interface-parameters
P1>config>router>ldp>if-params$ interface "P1-PE1"
P1>config>router>ldp>if-params>if$ exit
P1>config>router>ldp>if-params$ interface "P1-P2"
P1>config>router>ldp>if-params>if$ exit
P1>config>router>ldp>if-params$ interface "P1-P3"
P1>config>router>ldp>if-params>if$ exit all
LSP before the failure
LSP after the failure
1/1/2 LSR2
LSR4 10.2.1.0/24
1000
1/1/3
LER1 LER2
LSR1
RSVP-TE is used for establishing LSPs in MPLS networks
RSVP-TE operates in downstream-on-demand (DOD) label
advertisement mode with ordered LSP control.
A request to bind labels to a specific LSP tunnel is initiated by an
ingress node through the RSVP Path message
Labels are requested downstream and distributed (propagated)
upstream by means of the RSVP Resv message
Advantage of using RSVP to establish LSP tunnels is that it enables the
allocation of resources along the path.
For example, bandwidth can be allocated to an LSP tunnel using
standard RSVP reservations and Integrated Services service classes
Downstream on Demand (DoD)
PATH message sent
towards tunnel 1.1.1.1/32 2.2.2.2/32
destination iLER LSR1
Path: 3.3.3.3
Receiver sends RESV
message back towards
sender
eLER sends label Resv: label 131068
Path: 3.3.3.3
binding info in RESV
message
Path Refresh and RESV
Refresh messages are
sent periodically
LSR2 eLER
4.4.4.4/32 3.3.3.3/32
ilER makes use of
the shortest IGP
path from tunnel iLabel eLabel Action iLabel eLabel Action
head to tunnel
--- 131068 Push 131068 131071 Swap
Example of strict and loose path
Blue path => ERO (Explicit Route Object) defines strict hops
ERO explicitly defines the path PE2 => PE3 => PE4
Red Path => ERO defines only loose hops
ERO defines only 4.4.4.4 as loose
1.1.1.1/32 2.2.2.2/32
PE1 PE2
Blue Path
10.12.1.2
Red Path
10.23.1.3
10.34.1.4
PE4 PE3
4.4.4.4/32 3.3.3.3/32
RSVP Path
LSP Tunnel (IPv4)
ERO provides specific Label_Request
ERO: 10.12.1.2
path information for the 10.23.1.3
RSVP Path message to 10.34.1.4
4.4.4.4
follow Session_Attributes
1.1.1.1/32 RRO: 1.1.1.1 2.2.2.2/32
If ERO is not present PE1 PE2
then IGP is used to .1 .2
10.12.1.0/29
follow the path RSVP Path
LSP Tunnel (IPv4)
ERO can be manually Label_Request
ERO: 10.12.1.2
provided or computed .1 .2
10.23.1.0/29
10.23.1.3
based on RSVP 10.14.1.29/29
.4 .3
10.34.1.4
4.4.4.4
requirements such as Session_Attributes
Record Route Object RSVP Resv
LSP Tunnel (IPv4)
(RRO) of RSVP-TE is Label: 65
used for route Session_Attributes
recording purpose RRO: 10.12.1.1
10.12.1.2
RRO records the 1.1.1.1/32 10.34.1.3 2.2.2.2/32
actual route a PE1 PE2
.1 .2
packet traversed 10.12.1.0/29
Recording the path
RSVP Resv
allows the iLER to .1 .2
LSP Tunnel (IPv4)
know, on a hop-by- 10.14.1.29/29 10.23.1.0/29
Label_Request
Session_Attributes
hop basis, which .4 .3 RRO: 10.12.1.2
LSRs the path 10.23.1.2
traverses. 10.34.1.0/29 10.34.1.3
.4 RSVP Resv .3
LSP Tunnel
PE4 PE3
(IPv4)
4.4.4.4/32 Label_Request 3.3.3.3/32
Session_Attribut
es
RRO: 10.12.1.1
10.23.1.2
10.34.1.3
7750 Service Router
All Rights Reserved Alcatel-Lucent 2007
Alcatel-Lucent Services Implementation Course
RSVP-TE: The Alcatel-Lucent CSPF Implementation
MPLS Overview 6 1 31
The CSPF functionality provided by OSPF and IS-IS provides the capability to
traffic engineer LSPs based on the following constraints:
config>router>ospf# traffic-engineering
config>router>isis# traffic-engineering
TE Capable IGP
OSPF-TE
IS-IS-TE
Traffic Constrained
User
Routing Table Engineering Shortest Path First
Requirements
Database (TED) (CSPF)
Explicit Route
Object
(ERO)
Signaling
10.10.43.3 10.10.44.3
10.10.10.101
10.10.42.3 10.10.10.102
10.10.10.99 10.10.10.103
10.10.10.100
===================================================
RSVP Sessions
===================================================
From To Tunnel LSP Name State
ID ID
-------------------------------------------------------------------------------------------------------------------
10.10.10.99 10.10.10.103 1 1 LSP_99_103::Primary_Path Up
10.10.10.99 10.10.10.103 1 2 LSP_99_103::Secondary_Path Up
-------------------------------------------------------------------------------------------------------------------
Sessions : 2
===================================================
Display MPLS paths with binding information.
===================================================
MPLS Path:
===================================================
Path Name Opr LSP Name Binding
---------------------------------------------------------------------------------------------------------------
Primary_Path Up LSP_99_103 Primary
Secondary_Path Down LSP_99_103 Secondary
---------------------------------------------------------------------------------------------------------------
Paths : 2
===================================================
A:#
Alcatel-Lucent supports two reservation styles for LSP BW reservation
Shared Explicit
Total amount of BW
reserved on shared link
equals BW of largest
reservation request
Shared Link Shared Link
(FF) (SE)
90Mb/s 80Mb/s
Path Protection
Primary LSP with Secondary LSP
Primary LSP with Secondary Standby LSP
Fast Reroute
One-to-One Backup
Facilities Backup
R3
R2
R1
R6 R9
R7 R4
Primary LSP:
R1->R2->R3->R4 R8
Secondary LSP:
Primary LSP: One primary path R1->R6->R7->R8->R9->R4
Secondary LSP
Alternative path that is used if the primary path is not available.
Non-Standby needs to be signaled first (after primary path failure detection
Hot-Standby will be signaled upon creation
Continuously tries to revert back to the primary path.
Up to 8 secondary paths can be specified.
Allthe secondary paths are considered equal and the first available path is
used.
The software will not switch back among secondary paths.
7750 Service Router
All Rights Reserved Alcatel-Lucent 2007
Alcatel-Lucent Services Implementation Course
RSVP-TE: LSP Protection with a Secondary Path
MPLS Overview 6 1 40
Pros
Deterministic data flow during any point in primary path
Multiple failures along the primary path can be handled by the same
secondary path
When statically configured, no nodes or links should be shared by the
Primary and Secondary paths (otherwise if that link or node goes down,
both are lost)
Entire path is protected
Cons
Notification of a link or node failure might take a while to reach head of
tunnel
Full path resources are reserved over both Primary and Secondary paths,
therefore double booking
Selective protection of link or node is not possible, only end-to-end
MPLS Fast Reroute (FRR) defines ways of pre-configuring and
signaling backup paths before a failure
Allows traffic to flow almost continuously (in the 10s of ms
timeframe)
Uses LSPs established using RSVP-TE
Allows protection to be applied as close to point of failure as
possible
R10
R3
PLR
R2
R1 MP
PLR PLR
R5 MP
R4
MP
(2)
(1)
R9
R6
R7 R8
(1)
PLR
R3
R2 PLR
R1 MP
R5 (3)
PLR R4
(1) (2)
R9
R6
R7 R8
Detour Tunnel
(1) (3)
R1s backup:
R1->R6->R7->R8->R9->R4 R3s backup:
Protected LSP: R3->R9->R4
(2)
R1->R2->R3->R4
R2s backup:
R2->R7->R8->R9->R4
Failure occurred along the protected LSP, the PLR redirects traffic into the local detour.
PLR R3
R2
R1 X MP
R5
R4
R9
R6
R7 R8
If the link [R2->R3] fails:
R2 switches traffic received from R1 LSP along link [R2->R7] using the label received
when R2 created the detour.
The detour is calculated based on the shortest IGP path using CSPF from the PLR (R2)
to the router that is the termination of the protected LSP (R4), while avoiding the
failed link (R2-R3).
At no point does the depth of the label stack increase as a result of taking the detour.
While R2 is using its detour, traffic will take the path [R1->R2->R7->R8->R9->R4]
PLR
R3 54
R2 32
21 MP
R1
R4
159
172
198
187
R9
R8
R7
Protected LSP:
R1->R2->R3->R4
Inner
label
21
R3 54
R2 PLR
21 MP
R1
X R4
159
172
Inner 198
172 187 Inner
159
label label
R9
R7
R8
Inner Inner
187 label
198
label
Protected LSP:
R1->R2->R3->R4
R2s backup:
R2->R7->R8->R9->R4 Control Plane
(label propagation)
R10
R3
R2
R1
MP
PLR
R4
R9
R6
R7 R8
Protected LSP 1:
R1->R2->R3->R4
Bypass tunnel
R2->R7->R8->R3
Protected LSP 2:
R10->R2->R3->R4
Works the same as One-to-One Backup under normal operating conditions
MP
PLR R3 54
32
21 R2
R1
R4
172
138
R8
R7 187
Protected LSP:
R1->R2->R3->R4
MP receives same label from backup link as it would from Primary LSP
Inner
label 32 Inner
Inner
21 label 54
label MP
PLR 32
R3 54
R2
21
R1
X R4
172 Inner
label 32 138
Inner
label 32 172 138
R8
Protected LSP: R7 187
R1->R2->R3->R4 Inner
label 32 187
R2s backup:
R2->R7->R8->R3 Control Plane
(label propagation)
End of Module