Professional Documents
Culture Documents
MPLS
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 Alcatel-Lucent Services Implementation Course
All Rights Reserved Alcatel-Lucent 2007
Benefits of MPLS
MPLS Overview 613
Congestion
IGP PATH
Exclude this link Use CSPF to avoid low bandwidth links
MPLS PATH
Explicitly define the path or use any IGP
MPLS: Terminology
MPLS Overview 614
Multi Protocol Label Switching, MPLS: Allows the network operator to create end-to-end LSPs for data forwarding instead of using hop-by-hop IP routing. Alleviates the limitations of traditional IP routing
LSP 1 LSP 2
LSR
LSR
LER
615
Pop
LER
LSR
LSR
LER
data
IP Forwarding
label
data
label
data
label
data
data
IP Forwarding
LABEL SWITCHING
MPLS Label
MPLS Overview 616
Frame header
DA SA Type = 88 47
Single Label
MPLS Header IP Header IP Packet FCS
Label Stack
Data Link Header MPLS Header 1 MPLS Header 2 IP Header IP Data FCS
4 Octets
Label
Label: Exp.: S: TTL:
Exp.
TTL
Label Value, 20 bits Experimental, 3 bits (Class of Service) Bottom of Stack, 1 bit (1 = last entry in label stack) Time to Live, 8 bits
MPLS Label-range
MPLS Overview 617
==============================================================================
Label Type Static-lsp Static-svc Start Label 32 2048 End Label 1023 18431 Aging Total Available 992 16384 ------------------------------------------------------------------------------
Dynamic
32768
131071
98291
==============================================================================
FCS
LER DA
LER SA
Type = 88 47
MPLS Header
DA
SA
Type = 0800
IP Payload
FCS
LER DA
LER SA
Type = 88 47
MPLS Header
DA
SA
Type = 0800
IP Payload
FCS
LER DA
LER SA
Type = 88 47
MPLS Header
DA
SA
Type = 0800
IP Payload
FCS
A group
of IP packets forwarded in the same manner, over the same path, with the same forwarding treatment
Static
RIP
Distance Vector
IS-IS OSPF
Link State
LDP
IGP Based
RSVP-TE
IGP or CSPF based
Static LSPs are manually configured on each LER/LSR Labels are assigned on each router individually Allows the creator to have full control on the path Disadvantages:
Labour intensive operation
Changes need a reconfiguration on every node No back-up or fast re-route No support of label stacking
PE1# configure router mpls static-lsp "PE-1 to PE-3" to 3.3.3.3 push 999 nexthop 10.12.1.2 10.12.1.2 1.1.1.1/32 iLER
PE2>config>router# mpls interface "tope1" label-map 999 swap 998 nexthop 10.23.1.3 2.2.2.2/32 LSR2
10.23.1.3
4.4.4.4/32
PE3>config>router# mpls interface "tope2" label-map 998 pop
SWAP
LSR 1
POP
LER 2
1/1/5 1/1/1 1/1/4 1/1/2
LSR 2 LER 1
1/1/2 1/1/1 1/1/1 1/1/3
LSR 2 LFIB Prefix 10.2.1.0/24 LER 1 LFIB Prefix 10.2.1.0/24 10.2.1.0/24 Ingress Label Egress Label 131069 131067 Egress Interface 1/1/3 1/1/2 nexthop LSR 2 LSR 1 Ingress Label
10.2.1.0/24
nexthop LER 2
131069
SWAP PUSH
DATA
Data flow
LABEL
Data Plane
DATA
DATA
Data flow
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
7750 Service Router Alcatel-Lucent Services Implementation Course
All Rights Reserved Alcatel-Lucent 2007
Table Name
RIB FIB LIB LFIB
Meaning
Routing Information Base Forwarding Information Base Label Information Base Label Forwarding Information Base
Contents
Routing updates received Active routes Locally generated and received MPLS labels Labels used by the LSR
Populated By
Routing Protocol Exchange - Each routing protocol has a separate RIB RTM selects the active routes from all protocol "Best" routes MPLS Label Exchange The labels assigned to the active routes (for each next-hop)
PE1# show router ldp bindings =============================================================================== LDP LSR ID: 1.1.1.1 =============================================================================== Legend: U - Label In Use, N - Label Not In Use E - Epipe Service, V - VPLS Service, M - Mirror Service A - Apipe Service, F - Fpipe Service =============================================================================== LDP Prefix Bindings =============================================================================== Prefix Peer IngLbl EgrLbl EgrIntf EgrNextHop ------------------------------------------------------------------------------1.1.1.1/32 2.2.2.2 131071U ---1.1.1.1/32 3.3.3.3 131071U ---1.1.1.1/32 4.4.4.4 131071U ---2.2.2.2/32 2.2.2.2 -131071 1/1/2 10.12.1.2 2.2.2.2/32 3.3.3.3 131069U 131069 --2.2.2.2/32 4.4.4.4 131069U 131064 --3.3.3.3/32 2.2.2.2 131070U 131069 --3.3.3.3/32 3.3.3.3 -131071 1/1/4 10.13.1.3 3.3.3.3/32 4.4.4.4 131070U 131065 --4.4.4.4/32 2.2.2.2 131067U 131067 --4.4.4.4/32 3.3.3.3 131067U 131067 --4.4.4.4/32 4.4.4.4 -131067 1/1/3 10.14.1.4
7750 Service Router Alcatel-Lucent Services Implementation Course
All Rights Reserved Alcatel-Lucent 2007
PE1# show router ldp bindings active =============================================================================== Legend: (S) - Static =============================================================================== LDP Prefix Bindings (Active) =============================================================================== Prefix Op IngLbl EgrLbl EgrIntf EgrNextHop ------------------------------------------------------------------------------1.1.1.1/32 Pop 131071 ---2.2.2.2/32 Push -131071 1/1/2 10.12.1.2 2.2.2.2/32 Swap 131069 131071 1/1/2 10.12.1.2 3.3.3.3/32 Push -131071 1/1/4 10.13.1.3 3.3.3.3/32 Swap 131070 131071 1/1/4 10.13.1.3 4.4.4.4/32 Push -131067 1/1/3 10.14.1.4 4.4.4.4/32 Swap 131067 131067 1/1/3 10.14.1.4 -output omitted=============================================================================== PE1#
PE1# show router ldp parameters ===================================================================== LDP Parameters (LSR ID 1.1.1.1) ===================================================================== ---------------------------------------------------------------------
Interface Parameters
--------------------------------------------------------------------Keepalive Timeout Hold Time Propagate Policy Deaggregate FECs Control Mode : 30 sec : 15 sec : system : False : ordered Keepalive Factor : 3 HELLO Factor : 3 Transport Address: system Route Preference : 9 Label Retention Loop Detection : liberal : none
--------------------------------------------------------------------PE1#
7750 Service Router Alcatel-Lucent Services Implementation Course
Prefix
10.2.1.0/24 10.2.1.0/24
Next-hop
LSR 2 LSR 3
Label
131065 131066
1.1.1.1/32
iLER
2.2.2.2/32 LSR2
10.2.1.0/24
LSR3 4.4.4.4/32
FEC: 10.2.1.0/24
Label: 131067
eLER 3.3.3.3/32
Liberal Retention:
The label received from the router providing the active IGP route for the FEC is used and the other labels are kept
iLER LIB
Ordered Control: An LSR only propagates a label for a FEC once it has a label mapping from the FEC next-hop.
Label 131065
2.2.2.2/32 LSR2
Prefix
10.2.1.0/24 10.2.1.0/24
Next-hop
LSR 2 LSR 3
Label
131065 131066
Label
Step 2
Label 131067
Step 1
iLER FIB
Prefix
10.2.1.0/24
Next-hop
LSR 3
131066
iLER LFIB
Prefix
10.2.1.0/24
Next-hop
LSR 3
Label
131066 Step 1 LSR3 4.4.4.4/32
Label 131067
10.2.1.0/24
eLER 3.3.3.3/32
LDP: Signaling
MPLS Overview 6 1 21
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
LSR 4
1/1/1 10.2.1.0/24
1.1.1.1/32
2.2.2.2/32
3.3.3.3/32
4.4.4.4/32
LSR 1 LFIB
Ing. Label -
LSR 4 LFIB
Ing. Label -
Control Plane
7750 Service Router Alcatel-Lucent Services Implementation Course
Multiple next hops for a given FEC Maximum number of ECMP LDP paths
1.1.1.1/32
LSR 1 LIB
2.2.2.2/32 LSR2
Prefix
10.2.1.0/24 10.2.1.0/24
Next-hop
LSR 2 LSR 3
Next-hop
Label
131065 131066 1/1/3
Interface
iLER
1/1/2
LER 1 FIB
Prefix
10.2.1.0/24 10.2.1.0/24
1/1/2 1/1/3 Egr. Intf 1/1/2 1/1/3 Next-hop LSR2 LSR3 LSR3 4.4.4.4/32 eLER 3.3.3.3/32 10.2.1.0/24
LER 1 LFIB
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
7750 Service Router Alcatel-Lucent Services Implementation Course
All Rights Reserved Alcatel-Lucent 2007
LDP: Convergence
MPLS Overview 6 1 24
1/1/2 1000
LSR2
10.2.1.0/24
LER1
1/1/3
LER 1 LFIB
Prefix
Ingress Label -
nexthop LSR 2
MPLS Convergence =
Failure Detection Time + IGP Convergence + LDP Convergence
10.2.1.0/24
LER 1 LFIB
Prefix 10.2.1.0/24
Ingress Label -
nexthop LSR 1
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
2.2.2.2/32
LSR1
Path: 3.3.3.3
LSR2 4.4.4.4/32
eLER 3.3.3.3/32
iLabel --eLabel Action 131068 Push iLabel eLabel Action 131068 131071 Swap
1/1/2
the shortest IGP path from tunnel head to tunnel destination (no ERO). After the Resv message is propagated upstream to the sender node, a label-switched path is effectively established.
2.2.2.2/32 LSR2
1.1.1.1/32 iLER
1/1/1
1/1/3
1/1/2
eLER 3.3.3.3/32
LSr3 4.4.4.4/32
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 PE2 10.12.1.2 PE1
10.23.1.3
10.34.1.4
PE4 4.4.4.4/32
7750 Service Router Alcatel-Lucent Services Implementation Course
PE3 3.3.3.3/32
RSVP Path
path information for the RSVP Path message to follow If ERO is not present then IGP is used to follow the path ERO can be manually provided or computed 10.14.1.29/29 based on RSVP requirements such as bandwidth, hop limit, link coloring
1.1.1.1/32 PE1 .1
LSP Tunnel (IPv4) Label_Request ERO: 10.12.1.2 10.23.1.3 10.34.1.4 4.4.4.4 Session_Attributes RRO: 1.1.1.1
2.2.2.2/32 PE2 .2
10.12.1.0/29
RSVP Path
.2 10.23.1.0/29 .3
LSP Tunnel (IPv4) Label_Request ERO: 10.12.1.2 10.23.1.3 10.34.1.4 4.4.4.4 Session_Attributes RRO: 1.1.1.1 10.12.1.2
.1 .4
1/1/2
10.34.1.0/29
.4
RSVP Path
LSP Tunnel (IPv4) Label_Request ERO: 10.12.1.2 10.23.1.3 10.34.1.4 4.4.4.4 Session_Attribut es RRO: 1.1.1.1 10.12.1.2 10.34.1.3
.3
PE4 4.4.4.4/32
PE3 3.3.3.3/32
RSVP Resv
LSP Tunnel (IPv4) Label: 65 Session_Attributes RRO: 10.12.1.1 10.12.1.2 10.34.1.3 2.2.2.2/32 PE2 .2 10.12.1.0/29
(RRO) of RSVP-TE is used for route recording purpose RRO records the actual route a packet traversed Recording the path allows the iLER to know, on a hop-byhop basis, which LSRs the path traverses.
1.1.1.1/32 PE1 .1
RSVP Resv
.1 10.14.1.29/29 .4 .2 10.23.1.0/29 .3
RSVP Resv
.3 PE3 3.3.3.3/32
The CSPF functionality provided by OSPF and IS-IS provides the capability to
Routing Table
User Requirements
Signaling
10.10.10.99
10.10.10.100
10.10.10.103
interface to-100
Example: config>router# mpls config>router>mpls# path Primary_Path config>router>mpls>path$ hop 1 10.10.42.3 strict config>router>mpls>path$ hop 2 10.10.43.3 strict config>router>mpls>path# hop 3 10.10.44.3 strict config>router>mpls>path# hop 4 10.10.10.103 loose config>router>mpls>path# no shutdown config>router>mpls>path# exit
config>router# mpls config>router>mpls#lsp LSP_99_103 config>router>mpls>lsp# to 10.10.10.103 config>router>mpls>lsp# cspf config>router>mpls>lsp# primary Primary_Path" config>router>mpls>lsp>primary# hop-limit 4 config>router>mpls>lsp>primary# bandwidth 256,000 config>router>mpls>lsp>primary# no shutdown
A:# show router mpls path lsp-binding =================================================== 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:#
6 1 36
->10.10.45.3
-> 10.10.45.3
(80 Mb/s)
Path Protection
Primary LSP with Secondary LSP Primary LSP with Secondary Standby LSP
Fast Reroute
One-to-One Backup
Facilities Backup
R2 R1 R6 R7
Primary LSP: R1->R2->R3->R4
R3
R9
R4
R8
Secondary LSP: R1->R6->R7->R8->R9->R4
Alternative path that is used if the primary path is not available. Non-Standby needs to be signaled first (after primary path failure Hot-Standby will be signaled upon creation Continuously tries to revert back to the primary path.
detection
Up All
to 8 secondary paths can be specified. the secondary paths are considered equal and the first available path is used. The software will not switch back among secondary paths.
7750 Service Router Alcatel-Lucent Services Implementation Course
All Rights Reserved Alcatel-Lucent 2007
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
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
PLR
R3 R2
MP PLR
R1
PLR
R5 (2) R6
MP
R4
MP
(1) R9 R7 R8
(1)
Protected LSP 1: R1->R2->R3->R4 R2s backup for Protected LSP 1 R2->R7->R8->R9->R4
(2)
Protected LSP 2: R10->R2->R3->R4 R2s backup for Protected LSP 2 R2->R7->R8->R9->R4
PLR
R3 R2
PLR MP
R1 R5
PLR
(3) R4
(1) R6 R7
(2) R9 R8
Detour Tunnel
R1s backup: R1->R6->R7->R8->R9->R4 Protected LSP: R1->R2->R3->R4
(1)
(3)
R3s backup: R3->R9->R4
(2)
R2s backup: R2->R7->R8->R9->R4
Failure occurred along the protected LSP, the PLR redirects traffic into the local detour.
PLR
R3
R1
R2
X
R5
MP
R4
R6 R7 R8
R9
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]
7750 Service Router Alcatel-Lucent Services Implementation Course
All Rights Reserved Alcatel-Lucent 2007
21
32 R3
54
PLR
R1
21
R2 32
54
MP
R7
R8
Inner label
21 21 R2 PLR R3 54
MP
R1
X
172
Inner label
172 R7
159
187
Inner label
198
R10 R3 R2 R1
PLR MP
R4
R6
R9 R7 R8
21 32
32 R3
54
PLR
MP
21 R1
R2
54 R4
172 138
R7
187
R8
MP receives same label from backup link as it would from Primary LSP
Inner label
21
Inner label
32
MP
Inner label
54
PLR 32
21 R1
R2
R3
54 R4
X
172
Inner label
32 138
Inner label
32 172
138 R8 32 187
R7
187
Inner label
A:# oam lsp-trace LSP_99_103 lsp-trace to LSP_99_103: 0 hops min, 0 hops max, 116 byte packets 1 10.10.10.100 rtt<10ms, rc=6 (DSRtrMatchLabel) 2 10.10.10.100 rtt<10ms, rc=6 (DSRtrMatchLabel) 3 10.10.10.101 rtt<10ms, rc=6 (DSRtrMatchLabel) 4 10.10.10.102 rtt<10ms, rc=3 (EgressRtr) A:#
MPLS Overview
6 1 51
End of Module