Introduccion MPLS PDF

Introduction to MPLS
BRKMPL-1100
Jose Liste
Technical Marketing Engineer, Cisco
jliste@cisco.com
2
Session Goals
Objectives
• Understand history and business drivers for MPLS
• Learn about MPLS customer and market segments
• Understand the problems MPLS is addressing
• Understand the major MPLS technology components
• Understand typical MPLS applications
• Understand benefits of deploying MPLS
• Learn about MPLS futures; where MPLS is going
BRKMPL-1100 © 2014 Cisco and/or its affiliates. All rights reserved. Cisco Public 3
Agenda
• Introduction
• MPLS Technology Basics
• MPLS Layer-3 VPNs
• Advanced Topics
• Summary
Introduction
What Is MPLS?
Multi-Protocol: The ability to carry any
Multi payload
Have: IPv4, IPv6, Ethernet, ATM, FR

Protocol
Uses Labels to tell a node what to do

Label with a packet; separates forwarding
(hop by hop behavior) from routing
(control plane)
Routing == IPv4 or IPv6 lookup.
Switching Everything else is Switching.
What is MPLS?
Brief Summary
• It’s all about labels …
• Use the best of both worlds
– Layer-2 (ATM/FR): efficient forwarding and traffic engineering
– Layer-3 (IP): flexible and scalable
• MPLS forwarding plane
– Use of labels for forwarding Layer-2/3 data traffic
– Labeled packets are being switched instead of routed
• Leverage layer-2 forwarding efficiency
• MPLS control/signaling plane

– Use of existing IP control protocols extensions + new protocols
to exchange label information
• Leverage layer-3 control protocol flexibility and scalability
Technology Comparison
Key Characteristics of IP, Native Ethernet, and MPLS
IP Native Ethernet MPLS
Destination address based Destination address based Label based

Forwarding table learned Forwarding table learned Forwarding table learned from
Forwarding
from control plane from data plane control plane
TTL support No TTL support TTL support
Ethernet Loop avoidance Routing Protocols

Control Plane Routing Protocols
and signaling protocols MPLS protocols
Packet Encapsulation IP Header 802.3 Header MPLS shim header
QoS 8 bit TOS field in IP header 3-bit 802.1p field in VLAN tag 3 bit TC field in label
OAM IP ping, traceroute Ethernet OAM MPLS OAM
Evolution of MPLS
Technology Evolution and Main Growth Areas
 Evolved from tag switching in 1996 to full IETF Optimize MPLS
standard, covering over 130 RFCs for SDN and Cloud
 Key application initially were Layer-3 VPNs, Optimize MPLS for

followed by Traffic Engineering (TE), packet transport
(Planned)
and Layer-2 VPNs Optimize MPLS for video First
SDN/PCE
Deployments
Complete base MPLS portfolio
First G-MPLS
Bring MPLS to Market Deployment
(Planned)
First Large Scale
First L2VPN First Segment
L3VPNs L2VPN
Deployments Routing
Deployed Deployments
Deployments
Large Scale Large Scale (Planned) First

Cisco ships First MPLS TE First LSM First MPLS TP
L3VPN MPLS TE PBB-EVPN
MPLS Deployments Deployments Deployments
Deployments Deployments Deployments
1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015
MPLS Technology Basics
Topics
Basics of MPLS Signaling and Forwarding
• MPLS reference architecture
Service (Clients) Management
• MPLS Labels
Layer-3 VPNs Layer-2 VPNs
• MPLS signaling and forwarding
operations
MPLS OAM
Transport
• MPLS Traffic Engineering
IP/MPLS (LDP/RSVP-TE/BGP/OSPF/IS-IS)
• MPLS OAM
MPLS Forwarding
MPLS Reference Architecture
Different Type of Nodes in a MPLS Network
• P (Provider) router
– Label switching router (LSR) MPLS Domain
– Switches MPLS-labeled packets

P P
• PE (Provider Edge) router CE PE PE CE
– Label edge router (LER)

– Imposes and removes MPLS labels CE CE
• CE (Customer Edge) router PE P P PE

– Connects customer network to MPLS
network Label switched traffic
MPLS Labels
Label Definition and Encapsulation
MPLS Label Stack Entry
• Labels used for making
Label = 20 bits TC S TTL
forwarding decision
TC = Traffic Class: 3 Bits; S = Bottom of Stack; TTL = Time to Live
• Multiple labels can be used for
MPLS packet encapsulation
– No limit on the number of labels in a
stack LAN MAC Header Label, S=1 Layer 3
Packet
• Outer label always used for MPLS Label Stack (1 label)
switching MPLS packets in network
• Inner labels usually used for
services (e.g. L2/L3 VPN) LAN MAC Header Label, S=0 Label, S=1 Layer 3
Packet
MPLS Label Stack (2 labels)
MPLS QoS
QoS Marking in MPLS Labels
• MPLS label has 3 Traffic Class (TC) bits
• Used for packet classification and
prioritization
– Similar to Type of Service (ToS) field in IP MPLS DiffServ Marking
packet (DSCP values) in Traffic Class Bits IP DiffServ Marking
• DSCP values of IP packet mapped into

TC bits of MPLS label TC DSCP
– At ingress PE router Layer-2 Header MPLS Header Layer 3 Header
• Most providers have defined 3–5 service

classes (TC values)
• Different DSCP <-> TC mapping
schemes possible
– Uniform mode, pipe mode, and short pipe
mode
Basic MPLS Forwarding Operations
How Labels Are Being Used to Establish End-to-end Connectivity
• Label imposition (Push) Label Imposition Label Swap Label Swap Label Disposition
– By ingress PE router; classify and (Push) (PoP)
label packets
– Based on Forwarding Equivalence
Class (FEC) PE
P P
PE
CE L1
L2 L3
CE
• Label swapping
– By P router; forward packets using
CE CE
labels; indicates service class &
destination PE P P PE
• Label disposition (Pop)

– By egress PE router; remove label and
forward original packet to destination
CE
MPLS Path (LSP) Setup and Traffic Forwarding
MPLS Traffic Forwarding and MPLS Path (LSP) Setup
• LSP signaling protocols IP MPLS
– Either LDP* or RSVP Destination address Label based
– Leverages IP routing based
Forwarding table learned
Forwarding table learned
from control plane
Forwarding
– Routing table (Routing Information from control plane TTL support
Base – RIB) TTL support
• Exchange of labels Control Plane OSPF, IS-IS, BGP

LDP, RSVP, BGP,
OSPF, IS-IS
– Label bindings Packet

– Downstream MPLS node advertises Encapsulation
IP Header One or more labels
what label to use to send traffic to 8 bit TOS field in IP

QoS 3 bit TC field in label
node header
• MPLS forwarding OAM IP ping, traceroute MPLS OAM
– MPLS Forwarding table (Forwarding

Information Base – FIB) (*) LDP signaling assumed for next the examples
MPLS Path (LSP) Setup
Signaling Options
• LDP signaling LDP RSVP
– Leverages existing routing LSP or TE Tunnel
Forwarding path LSP
• RSVP signaling
Primary and, optionally, backup
Based on TE topology
– Aka MPLS RSVP / TE Forwarding Based on IP routing database
database
Shortest-path and/or other
– Enables enhanced capabilities, such Calculation Shortest-Path based
constraints
(CSPF calculation)
as Fast ReRoute (FRR)
Packet
• Can use both protocols
Single label One or two labels
Encapsulation
simultaneously
Initiated by head-end node
– They work differently, they solve By each node independently
towards tail-end node
different problems Signaling Uses existing routing

Uses routing protocol
extensions/information
– Dual-protocol deployments are very

protocols/information
Supports bandwidth reservation
Supports link/node protection
common
MPLS Path (LSP) Setup with LDP
Step 1: IP Routing (IGP) Convergence
• Exchange of IP routes Forwarding Table Forwarding Table Forwarding Table
– OSPF, IS-IS, EIGRP, etc. In Address Out Out In Address Out Out In Address Out Out
Label Prefix I’face Label Label Prefix I’face Label Label Prefix I’face Label
• Establish IP reachability 128.89

171.69
1
1
128.89
171.69
0
1
128.89 0
… … … … … …
0 128.89
1
0
You Can Reach 128.89 Thru Me

You Can Reach 128.89 and 11
171.69 Thru Me
Routing Updates You Can Reach 171.69 Thru Me

171.69
(OSPF, EIGRP, …)
IP Packet Forwarding Example
Basic IP Packet Forwarding
• IP routing information exchanged Forwarding
Table
between nodes Forwarding
Table
Forwarding
Table Address I/F
– Via IGP (e.g., OSFP, IS-IS) Address I/F Address I/F
128.89 0
• Packets being forwarded based on 128.89 1 128.89 0 171.69 1
destination IP address 171.69 1 171.69 1 …

… …
– Lookup in routing table (RIB)
128.89
0
0 128.89.25.4 Data
1 128.89.25.4 Data
1
128.89.25.4 Data 128.89.25.4 Data
171.69
MPLS Path (LSP) Setup with LDP
Step 2: Assignment of Remote Labels
• Local label mapping are sent to Forwarding Table Forwarding Table Forwarding Table
connected nodes In Address Out Out
Label Prefix I’faceLabel
In Address Out Out In Address Out Out
Label Prefix I’faceLabel Label Prefix I’faceLabel
- 128.89 1 20 20 128.89 0 30 30 128.89 0 -
• Receiving nodes update forwarding - 171.69 1 21 21 171.69 1 36
table … … … … … … … … … … … …
– Out label
128.89
0
• LDP label advertisement happens in 1 0
parallel (downstream unsolicited) Use Label 20 for 128.89 and

Use Label 30 for 128.89
11
Use Label 21 for 171.69
Label Distribution Use Label 36 for 171.69

Protocol (LDP) 171.69
(Downstream
Allocation)
MPLS Traffic Forwarding with LDP
Hop-by-hop Traffic Forwarding Using Labels
• Ingress PE node adds label to Forwarding Table Forwarding Table Forwarding Table
In Address Out Out In Address Out Out In Address Out Out
packet (push) Label Prefix I’faceLabel Label Prefix I’faceLabel Label Prefix I’faceLabel
– Via forwarding table - 128.89 1 20 20 128.89 0 30 30 128.89 0 -

- 171.69 1 21 21 171.69 1 36
• Downstream node use label for … … … … … … … … … … … …
forwarding decision (swap) 0 128.89

– Outgoing interface 0
128.89.25.4 Data
– Out label 1 30 128.89.25.4 Data
128.89.25.4 Data 20 128.89.25.4 Data 11
• Egress PE removes label and
forwards original packet (pop)
Forwarding based on 171.69
Label
MPLS Traffic Forwarding with LDP
Quick recap
• Routing protocol distributes routes
• LDP distributes labels that map to routes
• Packets are forwarded using labels
• …
• So what?
• …
• MPLS’s benefit shows up later, in two places:
– Divergence from IP routed shortest path
– Payload-independent tunneling
MPLS Path (RSVP) Setup
• MPLS-TE lets you deviate from the IGP shortest-cost path
• This gives you lots of flexibility around how you send traffic across your network
• Three steps:
– Information distribution
– Path calculation
– LSP signaling
• Flood link characteristics in the IGP
– Reservable bandwidth, link colors,
IP/MPLS
other properties
TE
Topology
database
• IGP: Find shortest (lowest cost) path n Link with insufficient bandwidth
to all nodes Find
shortest n Link with sufficient bandwidth
path to R8
• TE: Per node, find the shortest with 8Mbps

IP/MPLS
(lowest cost) path which meets R1

constraints 15 3
5
R8
10
10 8
10
10
TE
Topology
database
• Set up the calculated path using
RSVP (Resource ReSerVation
Protocol) IP/MPLS
Head end
• Once labels are learned, they’re
programmed just like LDP labels
– At the forwarding level, you can’t tell
whether your label came from RSVP L=16
or LDP RESV Tail end
– All the hard work is in the control plane
– No per-packet forwarding hit for any of PATH
this
TE LSP
Topic covered in detail in
MPLS TE Fast ReRoute (FRR) BRKMPL-2100 (MON / TUE)
Implementing Network Failure Protection Using MPLS RSVP/TE

• Steady state
Router A Router B Router D Router E
– Primary tunnel:
• A→B→D→E
– Backup tunnel:
• B → C → D (pre-provisioned)
• Failure of link between router B and

D
• Traffic rerouted over backup tunnel Router X Router Y
Router C
• Recovery time 50 ms Primary Tunnel
– Actual Time Varies—Well Below 50 Backup Tunnel
ms in Lab Tests
MPLS OAM
Tools for Reactive and Proactive Trouble Shooting of MPLS Connectivity
• MPLS LSP Ping
– Used for testing end-to-end MPLS connectivity similar to IP ping
– Can we used to validate reachability of LDP-signaled LSPs, TE tunnels, and PWs
• MPLS LSP Trace
– Used for testing hop-by-hop tracing of MPLS path similar to traceroute
– Can we used for path tracing LDP-signaled LSPs and TE tunnels
• MPLS LSP Multipath (ECMP) Tree Trace
– Used to discover of all available equal cost LSP paths between PEs
– Unique capability for MPLS OAM; no IP equivalent!
• Auto IP SLA
– Automated discovery of all available equal cost LSP paths between PEs
– LSP pings are being sent over each discovered LSP path
Summary
Key Takeaways
• MPLS networks consist of PE routers at in/egress and P routers in core
• Traffic is encapsulated with label(s) at ingress (PE router)
• Labels are removed at egress (PE router)
• MPLS forwarding operations include label imposition (PUSH), swapping, and
disposition (POP)
• LDP and RSVP can be used for signaling label mapping information to set up an
end-to-end Label Switched Path (LSP)
• RSVP label signaling enables setup of TE tunnels, supporting enhanced traffic
engineering capabilities; traffic protection and path management
MPLS Virtual Private Networks
MPLS Virtual Private Networks
Topics
• Definition of MPLS VPN service
• Basic MPLS VPN deployment
scenario Layer-3 VPNs Layer-2 VPNs 
• Technology options
MPLS OAM
Transport
IP/MPLS (LDP/RSVP-TE/BGP/OSPF/IS-IS)
 MPLS Forwarding
What Is a Virtual Private Network?
Definition
• Set of sites which communicate with each other in a secure way
– Typically over a shared public or private network infrastructure
• Defined by a set of administrative policies
– Policies established by VPN customers themselves (DIY)
– Policies implemented by VPN service provider (managed/unmanaged)
• Different inter-site connectivity schemes possible
– Full mesh, partial mesh, hub-and-spoke, etc.
• VPN sites may be either within the same or in different organizations
– VPN can be either intranet (same org) or extranet (multiple orgs)
• VPNs may overlap; site may be in more than one VPN
MPLS VPN: Build vs Buy?
• To some people, “deploying MPLS VPN” means building your own MPLS
network
• To some, it means “buying MPLS-based VPN services from a provider”
• Most of the heavy lifting is in building your own
• Buying may or may not have any impact on your network
MPLS VPN Example
Basic Building Blocks
• VPN policies
PE-CE BGP Route Reflector PE-CE
– Configured on PE routers (manual Link Link
operation)
PE VPN PE
CE CE
• VPN signaling Signaling
VPN VPN
– Between PEs Policy Policy
– Exchange of VPN policies VPN

CE Policy
VPN
Policy CE
• VPN traffic forwarding PE PE

– Additional VPN-related MPLS label
encapsulation
• PE-CE link
– Connects customer network to MPLS
network; either layer-2 or layer-3
MPLS VPN Models
Technology Options
MPLS VPN Models
– Peering relationship between CE and
PE MPLS Layer-2 VPNs MPLS Layer-3 VPNs
• MPLS Layer-2 VPNs • CE connected to PE via IP-
– Interconnect of layer-2 Attachment Point-to-Point Multi-Point based connection (over any
Layer-2 VPNs Layer-2 VPNs layer-2 type)
Circuits (ACs) – Static routing
• CE • CE
connected connected to – PE-CE routing protocol;
to PE via L2 PE Ethernet eBGP, OSPF, IS-IS
(Eth, FR, connection • CE routing has peering
ATM, etc) • CE-CE L2 relationship with PE router; PE
connection (Eth) mp routers are part of customer
• CE-CE L2 connectivity routing
p2p • CE-CE • PE routers maintain customer-
connectivity routing; no specific routing tables and
• CE-CE SP exchange customer=specific
routing; no involvement routing information
SP
BRKMPL-1100 © 2014 Cisco and/or its affiliates. All rights reserved. Cisco Public
involvement
35
BRKMPL-2102 (TUE)
MPLS Layer-3 Virtual Private Networks

Topics
• Technology components
• VPN control plane mechanisms
Layer-3 VPNs Layer-2 VPNs 
• VPN forwarding plane
MPLS OAM
• Deployment use cases Transport
– Business VPN services
– Network segmentation IP/MPLS (LDP/RSVP-TE/BGP/OSPF/IS-IS)
– Data Center access
 MPLS Forwarding
MPLS Layer-3 VPN Overview
Technology Components
• VPN policies
– Separation of customer routing via virtual VPN routing table (VRF)
– In PE router, customer interfaces are connected to VRFs
• VPN signaling
– Between PE routers: customer routes exchanged via BGP (MP-BGP)
• VPN traffic forwarding
– Separation of customer VPN traffic via additional VPN label
– VPN label used by receiving PE to identify VPN routing table
• PE-CE link
– Can be any type of layer-2 connection (e.g., FR, Ethernet)
– CE configured to route IP traffic to/from adjacent PE router
– Variety of routing options; static routes, eBGP, OSPF, IS-IS
Virtual Routing and Forwarding Instance
Virtual Routing Table and Forwarding to Separate Customer Traffic
• Virtual routing and forwarding table
– On PE router
CE
– Separate instance of routing (RIB) and VPN 1 VRF
forwarding table Green
PE
• Typically, VRF created for each CE MPLS Backbone
customer VPN
– Separates customer traffic VPN 2 VRF
Blue
• VRF associated with one or more
customer interfaces
• VRF has its own routing instance for
PE-CE configured routing protocols
– E.g., eBGP
VPN Route Distribution
Exchange of VPN Policies Among PE Routers
• Full mesh of BGP sessions among
BGP Route Reflector
all PE routers PE-CE PE-CE
Link Link
– Or BGP Route Reflector (common)
PE PE
• Multi-Protocol BGP extensions (MP- CE CE
iBGP) to carry VPN policies Blue VRF Blue VRF
Red VRF Red VRF

• PE-CE routing options CE CE
– Static routes PE PE
– eBGP
– OSPF
– IS-IS
– EIGRP
VPN Control Plane Processing
• Make customer routes unique:
– Route Distinguisher (RD):
– 8-byte field, VRF parameters; unique value to make VPN IP routes unique
– VPNv4 address: RD + VPN IP prefix
• Selective distribute VPN routes:
– Route Target (RT):
– 8-byte field, VRF parameter, unique value to define the import/export rules for VPNv4
routes
– MP-iBGP: advertises VPNv4 prefixes + labels
VPN Control Plane Processing
Interactions Between VRF and BGP VPN Signaling
• CE1 redistribute IPv4 route to PE1
BGP advertisement:
VPN-IPv4 Addr = RD:16.1/16
via eBGP BGP Next-Hop = PE1
Route Target = 100:1
eBGP: Label=42
• PE1 allocates VPN label for prefix 16.1/16
eBGP:
16.1/16
learnt from CE1 to create unique
VPNv4 route CE1
PE1 Blue VPN PE2
CE2
• PE1 redistributes VPNv4 route into

MP-iBGP, it sets itself as a next hop
and relays VPN site routes to PE2 ip vrf blue-vpn
RD 1:100
VRF parameters:
• PE2 receives VPNv4 route and, via route-target export
Name = blue-vpn
1:100
RD = 1:100
processing in local VRF (green), it route-target import
Import Route-Target = 100:1
1:100
redistributes original IPv4 route to Export Route-Target = 100:1
CE2
VPN Forwarding Plane Processing
Forwarding of Layer-3 MPLS VPN Packets
• CE2 forwards IPv4 packet to PE2
• PE2 imposes pre-allocated VPN label to
IPv4 packet received from CE2 IPv4 IGP
Label C
VPNv4
Label
IPv4 IGP
Label B
VPNv4
Label
IPv4 IGP
Label A
VPNv4
Label
IPv4 IPv4
– Learned via MP-IBGP IPv4

IPv4
Packet Packet
• PE2 imposes outer IGP label A (learned PE1 P1 P2 PE2
via LDP) and forwards labeled packet to CE1 CE2
next-hop P-router P2
• P-routers P1 and P2 swap outer IGP
label and forward label packet to PE1
– A->B (P2) and B->C (P1)
• Router PE1 strips VPN label and IGP

labels and forwards IPv4 packet to CE1
Service Provider Deployment Scenario
MPLS Layer-3 VPNs for Offering Layer-3 Business VPN Services
• Deployment Use Case
– Delivery of IP VPN services to Managed VPN Service
business customers Unmanaged VPN Service
• Benefits CPE
Edge Core
VPN Core Edge
CPE
– Leverage same network for multiple
services and customers (CAPEX)
• Highly scalable
– Service enablement only requires
edge node configuration (OPEX)
– Different IP connectivity can be easily
configured; e.g., full/partial mesh
Enterprise Deployment Scenario
MPLS Layer-3 VPNs for Implementing Network Segmentation
– Segmentation of enterprise network to
MPLS VPNs for L3 Network
provide selective connectivity for Segmentation
specific user groups and organizations Core
Access
Edge VPN Core Edge
Access
• Benefits
– Network segmentation only requires
edge node configuration
– Flexible routing; different IP
connectivity can be easily configured;
e.g., full/partial mesh
Data Center Deployment Scenario
MPLS Layer-3 VPNs for Segmented L3 Data Center Access and Interconnect
• Deployment Use Case MPLS VPNs terminating on DC
aggregation
– Segmented WAN Layer-3 at Data MPLS VPNs
Center edge at DC edge
– Layer-3 segmentation in Data Center Access

Core Core Edge
Top Of Rack Distribution
• Benefits
– Only single Data Center edge node Data Center
needed for segmented layer-3 access
– Enables VLAN/Layer-2 scale (> 4K)
MPLS L3 VPN: Build vs buy?
• Key consideration: bringing SP into the customer’s routing domain
• Easy to solve with BGP, the world’s only political routing protocol!
• Also works with static routes: no dynamic handoff, no potential for dynamic
mess
• BGP and static are very popular
• EIGRP, OSPF, RIP are also options
Summary
Key Takeaways
• MPLS Layer-3 VPNs provide IP connectivity among CE sites
– MPLS VPNs enable full-mesh, hub-and-spoke, and hybrid IP connectivity
• CE sites connect to the MPLS network via IP peering across PE-CE links
• MPLS Layer-3 VPNs are implemented via VRFs on PE edge nodes
– VRFs providing customer routing and forwarding segmentation
• BGP used for signaling customer VPN (VPNv4) routes between PE nodes
• To ensure traffic separation, customer traffic is encapsulated in an additional
VPN label when forwarded in MPLS network
• Key applications are layer-3 business VPN services, enterprise network
segmentation, and segmented layer-3 Data Center access
BRKMPL-2101 (TUE / WED)

Topics
• L2VPN technology options
• P2P services (VPWS)
– Overview & Technology Basics  Layer-3 VPNs Layer-2 VPNs 
– VPN control plane
MPLS OAM
– VPN forwarding plane Transport
• MP2MP services (VPLS / xEVPN) IP/MPLS (LDP/RSVP-TE/BGP/OSPF/IS-IS)

– Overview & Technology Basics
– VPN control / forwarding plane  MPLS Forwarding
• Deployment use cases

– L2 Business VPN services
– Data Center Interconnect
Technology Options
• VPWS services MPLS Layer-2 VPNs
– Point-to-point
– Referred to as Pseudowires (PWs)
Point-to-Point Multipoint-to-Multipoint
• VPLS services Layer-2 VPNs (VPWS) Layer-2 VPNs
– Multipoint
• EVPN
– Multipoint with BGP-based MAC VPLS
EVPN
learning
• PBB-EVPN
PBB-EVPN
– Combines scale tools from PBB (aka
MAC-in-MAC) with BGP-based MAC
learning from EVPN
Virtual Private Wire Services (VPWS)
Overview of Pseudowire (PW) Architecture
• Based on IETF’s Pseudo-Wire (PW) Attachment Attachment
Reference Model Circuit (AC)
Pseudo-Wire 1
Circuit (AC)
• Enables transport of any Layer-2 CE

PE1 PE2
CE
traffic over MPLS Layer-2 Layer-2
• PE-CE link is referred to as

CE CE
Attachment Circuit (AC) Layer-2 Layer-2
Pseudo-Wire 2
• Provides a p2p service PE3 PE4
• Discovery: manual (config) Emulated Layer-2 Service
• Signaling: LDP
• Learning: none
VPWS Control Plane Processing
Signaling of a New Pseudo-Wire
(1) New Virtual Circuit (VC) cross-connect
connects customer L2 interface (AC) to
new PW via VC ID and remote PE ID
3 Label Mapping Messages
(2) New targeted LDP session between 4 4
PE1 and PE2 is established, in case one 2 LDP session
does not already exist CE1 PE1 PE2

CE2
(3) PE binds VC label with customer layer- 1 1

2 interface and sends label-mapping to
remote PE Emulated Layer-2 Service
(4) Remote PE receives LDP label binding

message and matches VC ID with local
configured VC cross-connect
VPWS Forwarding Plane Processing
Forwarding of Layer-2 Traffic Over PWs
• CE2 forwards L2 packet to PE2.
• PE2 pushes VC (inner) label to L2 packet
received from CE2
Eth IGP PW Eth IGP PW Eth IGP PW Eth Eth
– Optionally, a control word is added as well (not Label C Label Label B Label Label A Label
shown) Ethernet Ethernet

Frame Frame
• PE2 pushed outer (Tunnel) label and forwards PE1 P1 P2 PE2

packet to P2 CE1 CE2
• P2 and P1 forward packet using outer (tunnel)

label (swap)
• Router PE2 pops Tunnel label and, based on
VC label, L2 packet is forwarded to customer
interface to CE1, after VC label is removed
– In case control word is used, new layer-2 header is
generated first
Virtual Private LAN Services
Overview of VPLS Architecture
• VPLS network acts like a virtual Attachment
Circuit (AC)
Attachment
Circuit (AC)
switch that emulates conventional
L2 bridge
PE1 PE2
CE CE
• Fully meshed or Hub-Spoke Eth Eth
topologies supported
• Provides a multipoint ethernet CE CE
Eth Eth
service PE3 PE4
• Discovery: manual or auto (BGP)

Emulated Virtual Switch
• Signaling: LDP or BGP (PW label)
Pseudo-Wire
• Learning: data plane
BRKMPL-2333 (THU)
EVPN
BGP advertisement:
L2VPN/EVPN Addr = CE1.MAC
• Ethernet VPN BGP Next-Hop = PE1
Route Target = 100:1
• Provides a multipoint ethernet Label=42
service
• Discovery: BGP, using MPLS VPN BGP RR
PE 1 PE 3
mechanisms (RT) CE1 CE3
• Signaling: BGP (MAC prefixes)

• Learning: Control plane (BGP) CE2 CE4
• Allows for multihomed CEs PE 2 PE 4
Emulated Virtual Switch
BRKMPL-2333 (THU)
PBB-EVPN
BGP advertisement:
L2VPN/EVPN Addr = PE1.B-MAC
• Combines Provider Backbone BGP Next-Hop = PE1
Bridging (MAC-in-MAC) with EVPN Route Target = 100:1
Label=42
– Scales better than EVPN
– Removes the need to advertise CE-CE MAC addresses learned in the data plane)
Customer MAC addresses in BGP BGP RR
B-MAC PE 1 PE 3 B-MAC
CE3
• Provides multipoint ethernet service CE1
• Discovery: BGP, using MPLS VPN

B-MAC
mechanisms (RT) CE2 CE4
B-MAC
• Signaling: BGP (B-MAC prefixes) PE 2 PE 4
• Learning: Control plane (BGP) and Emulated Virtual Switch

forwarding plane
• Allows for multihomed CEs C-MAC = Customer MAC address
B-MAC = Backbone MAC address
Service Provider Deployment Scenario
PWs for Offering Layer-2 Business VPN Services
– Delivery of E-LINE services to
business customers
Layer-2 VPN Service
• Benefits
– Leverage same network for multiple PE P P PE
CE CE
services and customers (CAPEX)
• Highly scalable
– Service enablement only requires
edge node configuration (OPEX)
Data Center Deployment Scenario
VPLS for Layer-2 Data Center Interconnect (DCI) Services
• Deployment Use Case Data Center
– E-LAN services for Data Center DC
interconnect Edge
• Benefits Data Center Core Core Edge

– Single WAN uplink to connect to DC Data Center
Edge Edge
multiple
DC
Data Centers Edge
– Easy implementation of segmented
layer-2 traffic between Data Centers Core Core Edge
Summary
Key Takeaways
• L2VPNs enable transport of any Layer-2 traffic over MPLS network
• L2 packets encapsulated into additional VC label
• Both LDP and BGP can be used Pseudowire (PW) signaling
• PWs suited for implementing transparent point-to-point connectivity between
Layer-2 circuits (E-LINE services)
• VPLS suited for implementing transparent point-to-multipoint connectivity
between Ethernet links/sites (E-LAN services)
• EVPN / PBB-EVPN are next-generation L2VPN solutions based on BGP control-
plane for MAC distribution/learning over the core
• Typical applications of L2VPNs are layer-2 business VPN services and Data
Center interconnect
Topics covered in detail in
BRKMPL-3101 ( WED/THU)
Advanced Topics
MPLS And IPv6
IPv6 Support for Native MPLS Deployments and MPLS Layer-3 Services
• MPLS allows IPv6 to be deployed
as an edge-only service, no need to IPv6 IPv4 MPLS IPv6
run v6 in the core
P P
– Easier to deploy CE
6PE 6PE
CE
– Security mechanism
• 6PE: All IPv6 can see each other
(single VPN) IPv6 IPv4 MPLS IPv6
– IPv6+label (no RD, no RT) 6VPE P P 6VPE

CE CE
• 6VPE: Separate IPv6 VPNs
– VPNv6, includes RD and RT
Label Switched Multicast (LSM)
Point-to-Multi-Point MPLS Signaling and Connectivity
• What is Label Switched Multicast? Uni-Directional
LSP
– MPLS extensions to provide
P2MP connectivity MPLS /
– RSVP extensions and multicast LDP IP
IP/MPLS
• Why Label-Switched Multicast?
– Enables MPLS capabilities, which can
not be applied to IP multicast traffic
P2MP or MP2MP
(e.g., FRR) LSP Tree
• Benefits of Label-Switched Multicast Label Switched

– Efficient IP multicast traffic forwarding Multicast (LSM)
IP/MPLS
– Enables MPLS traffic protection and
BW control of IP multicast traffic
Segment Routing
Control Plane
• Segment routing provides A B
– Rich forwarding behaviors 101 102
– Minimal forwarding state (encapsulated in packet) 203
• Simple IS-IS / OSPF extensions program 202

MPLS forwarding plane
201 201 E
• IGP advertises 103
– Node segment id (label) per node (globally
significant) 203
– Adjacency segment id (label) per link (locally
significant) 202
• Packet with node segment id forwarded along C D

shortest path to destination 105 104 Node Segment
Identifier (label)
• Packet with adjacency segment id forwarded Adjacency Segment
over adjacency Identifier (label)
Segment Routing
Forwarding Plane
Node Path Adjacency Path Combined Path
A B A B A B
102
202 202
E 201 E E
103
202
C D C D C D
202
201 201 102
103 202 202 202 202 202
Payload Payload Payload Payload Payload Payload Payload Payload Payload
C D E C D B E C D B E
(php) (php)
Enhanced Path Computation for MPLS TE LSPs
with Path Computation Element (PCE)
Inter-Area MPLS TE SDN WAN Orchestration
Application
Stateless PCE Path Request
LSP DB
Stateful PCE
TED TED
Area 0
Stateless PCE PCEP Stateless PCE
(ABR) (ABR)
PCEP BGP-LS / PCEP BGP-LS /
PCEP SNMP / CLI SNMP / CLI
Area 0
Stateless PCC Area 1 Area 2
Stateful
PCC-initiated PCC
LSP
PCE-initiated
Stateless LSP
Area 1 Area 2
PCC
PCC-initiated
LSP
• ABRs act as stateless PCEs • Out-of-network, stateless PCE server • Out-of-network, stateful PCE server
• ABRs implement backward recursive • PCC initiates LSPs • PCE always initiates LSPs
PCE-Based Computation • Introduced in IOS XR 3.5.2 • Introduced in IOS XR 5.1.1
• Introduced in IOS XR 3.5.2
Futures
New MPLS Developments on the Horizon
WAN Orchestration
PCE/SDN
MPLS Multilayer Control Plane

Optimization Simplification
PCE/GMPLS
Segment Routing
Summary
Summary
Key Takeaways
• It’s all about labels …
– Label-based forwarding and protocol for label exchange
– Best of both worlds … L2 deterministic forwarding and scale/flexible L3 signaling
• Key MPLS applications are end-to-end VPN services
– Secure and scalable layer 2 and 3 VPN connectivity
• MPLS supports advanced traffic engineering capabilities
– QoS, bandwidth control, and failure protection
• MPLS is a mature technology with widespread deployments
– De facto for most SPs, large enterprises, and increasingly in Data Centers
• Ongoing technology evolution
– Control-plane simplification (Segment Routing) and WAN orchestration (PCE/SDN)
Consider MPLS When …
Decision Criteria
• Is there a need for network segmentation?
– Segmented connectivity for specific locations, users, applications, etc.
• Is there a need for flexible connectivity?
– E.g., Flexible configuration of full-mesh or hub-and-spoke connectivity
• Is there a need for implementing/supporting multiple (integrated) services?
– Leverage same network for multiple services
• Are there specific scale requirements?
– Large number of users, customer routes, etc.
• Is there a need for optimized network availability and performance?
– Node/link protection, pro-active connectivity validation
– Bandwidth traffic engineering and QoS traffic prioritization
MPLS Sessions at Cisco Live
• BRKMPL-1100 Introduction to MPLS
• BRKMPL-2100 Deploying MPLS Traffic Engineering
• BRKMPL-2101 Deploying MPLS-based Layer 2 Virtual Private Networks
• BRKMPL-2102 Deploying MPLS-based IP VPNs
• BRKMPL-2108 Designing MPLS in Next Generation Data Center: A Case Study
• BRKMPL-2333 E-VPN & PBB-EVPN: the Next Generation of MPLS-based L2VPN
• BRKMPL-3101 Advanced Topics and Future Directions in MPLS
• LTRMPL-2102 Enterprise Network Virtualization using IP and MPLS Technologies: Introduction
• LTRMPL-3102 Enterprise Network Virtualization using IP and MPLS Technologies: Advanced
• TECMPL-3100 Unified MPLS - An architecture for Advanced IP NGN Scale
• TECMPL-3200 SDN WAN Orchestration in MPLS and Segment Routing Networks
Terminology Reference
Acronyms Used in MPLS Reference Architecture
Terminology Description
AC Attachment Circuit. An AC Is a Point-to-Point, Layer 2 Circuit Between a CE and a PE.
AS Autonomous System (a Domain)
CoS Class of Service
ECMP Equal Cost Multipath
IGP Interior Gateway Protocol
LAN Local Area Network
LDP Label Distribution Protocol, RFC 3036.
LER Label Edge Router. An Edge LSR Interconnects MPLS and non-MPLS Domains.
LFIB Labeled Forwarding Information Base
LSP Label Switched Path
LSR Label Switching Router
NLRI Network Layer Reachability Information
P Router An Interior LSR in the Service Provider's Autonomous System
PE Router An LER in the Service Provider Administrative Domain that Interconnects the Customer Network and the Backbone Network.
PSN Tunnel Packet Switching Tunnel
Terminology Reference
Acronyms Used in MPLS Reference Architecture (cont.)
Terminology Description
Pseudo-Wire A Pseudo-Wire Is a Bidirectional “Tunnel" Between Two Features on a Switching Path.
PWE3 Pseudo-Wire End-to-End Emulation
QoS Quality of Service
RD Route Distinguisher
RIB Routing Information Base
RR Route Reflector
RT Route Target
RSVP-TE Resource Reservation Protocol based Traffic Engineering
VPN Virtual Private Network
VFI Virtual Forwarding Instance
VLAN Virtual Local Area Network
VPLS Virtual Private LAN Service
VPWS Virtual Private WAN Service
VRF Virtual Route Forwarding Instance
VSI Virtual Switching Instance
Further Reading
MPLS References at Cisco Press and cisco.com
• http://www.cisco.com/go/mpls
• http://www.ciscopress.com
• MPLS and VPN Architectures — Cisco Press®
– Jim Guichard, Ivan Papelnjak
• Traffic Engineering with MPLS — Cisco Press®
– Eric Osborne, Ajay Simha
• Layer 2 VPN Architectures — Cisco Press®
– Wei Luo, Carlos Pignataro, Dmitry Bokotey, and Anthony Chan
• MPLS QoS — Cisco Press ®
– Santiago Alvarez
Participate in the “My Favorite Speaker” Contest
Promote Your Favorite Speaker and You Could be a Winner
• Promote your favorite speaker through Twitter and you could win $200 of Cisco
Press products (@CiscoPress)
• Send a tweet and include
– Your favorite speaker’s Twitter handle @jliste2002
– Two hashtags: #CLUS #MyFavoriteSpeaker
• You can submit an entry for more than one of your “favorite” speakers
• Don’t forget to follow @CiscoLive and @CiscoPress
• View the official rules at http://bit.ly/CLUSwin
Complete Your Online Session Evaluation
• Give us your feedback and you
could win fabulous prizes. Winners
announced daily.
• Complete your session evaluation
through the Cisco Live mobile app
or visit one of the interactive kiosks
located throughout the convention
center.
Don’t forget: Cisco Live sessions will be available

for viewing on-demand after the event at
CiscoLive.com/Online
Continue Your Education
• Demos in the Cisco Campus
• Walk-in Self-Paced Labs
• Table Topics
• Meet the Engineer 1:1 meetings
MPLS Transport Profile (TP)
Bi-Directional MPLS Tunnel Extensions For Transport Oriented Connectivity
• What is MPLS TP? Bi-Directional
– Point-to-point static LSPs which are co- MPLS TP Tunnel
routed
– Bi-directional TP tunnel CE PE P P PE CE
• Why MPLS TP?

– Migration of TDM legacy networks often
assume continuation of connection-oriented
operations model Transport
– MPLS TP enables packet-based transport IP/MPLS MPLS-TP
with connection-oriented connectivity (LDP/RSVP-TE/BGP) (Static/RSVP-TE)
• Benefits of MPLS TP
MPLS Forwarding
– Meets transport-oriented operations
requirements
– Enables seamless migration to dynamic
MPLS

Introduccion MPLS PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Introduccion MPLS PDF

Uploaded by

Copyright:

Available Formats

Introduction to MPLS

Have: IPv4, IPv6, Ethernet, ATM, FR

Uses Labels to tell a node what to do

• MPLS control/signaling plane

IP Native Ethernet MPLS

Destination address based Destination address based Label based

Ethernet Loop avoidance Routing Protocols

Packet Encapsulation IP Header 802.3 Header MPLS shim header

OAM IP ping, traceroute Ethernet OAM MPLS OAM

 Key application initially were Layer-3 VPNs, Optimize MPLS for

Large Scale Large Scale (Planned) First

– Switches MPLS-labeled packets

– Label edge router (LER)

• CE (Customer Edge) router PE P P PE

• DSCP values of IP packet mapped into

– At ingress PE router Layer-2 Header MPLS Header Layer 3 Header

• Most providers have defined 3–5 service

– By ingress PE router; classify and (Push) (PoP)

• Label disposition (Pop)

• Exchange of labels Control Plane OSPF, IS-IS, BGP

– Label bindings Packet

what label to use to send traffic to 8 bit TOS field in IP

• MPLS forwarding OAM IP ping, traceroute MPLS OAM

– MPLS Forwarding table (Forwarding

different problems Signaling Uses existing routing

– Dual-protocol deployments are very

• Establish IP reachability 128.89

You Can Reach 128.89 Thru Me

Routing Updates You Can Reach 171.69 Thru Me

• Packets being forwarded based on 128.89 1 128.89 0 171.69 1

destination IP address 171.69 1 171.69 1 …

parallel (downstream unsolicited) Use Label 20 for 128.89 and

Label Distribution Use Label 36 for 171.69

– Via forwarding table - 128.89 1 20 20 128.89 0 30 30 128.89 0 -

• Downstream node use label for … … … … … … … … … … … …

forwarding decision (swap) 0 128.89

• TE: Per node, find the shortest with 8Mbps

(lowest cost) path which meets R1

Implementing Network Failure Protection Using MPLS RSVP/TE

• Failure of link between router B and

– Exchange of VPN policies VPN

• VPN traffic forwarding PE PE

MPLS Layer-3 Virtual Private Networks

iBGP) to carry VPN policies Blue VRF Blue VRF

Red VRF Red VRF

• PE1 redistributes VPNv4 route into

– Learned via MP-IBGP IPv4

• Router PE1 strips VPN label and IGP

business customers Unmanaged VPN Service

– Layer-3 segmentation in Data Center Access

MPLS Layer-2 Virtual Private Networks

• MP2MP services (VPLS / xEVPN) IP/MPLS (LDP/RSVP-TE/BGP/OSPF/IS-IS)

• Deployment use cases

• Enables transport of any Layer-2 CE

• PE-CE link is referred to as

• Discovery: manual (config) Emulated Layer-2 Service

does not already exist CE1 PE1 PE2

(3) PE binds VC label with customer layer- 1 1

(4) Remote PE receives LDP label binding

shown) Ethernet Ethernet

• PE2 pushed outer (Tunnel) label and forwards PE1 P1 P2 PE2

• P2 and P1 forward packet using outer (tunnel)

• Discovery: manual or auto (BGP)