BRKMPL-1101 2012 San Diego

Introduction to MPLS
BRKMPL-1101
BRKMPL-1101
2012 Cisco and/or its affiliates. All rights reserved.
Cisco Public
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-1101
Cisco Public
Agenda
Topics
Introduction
MPLS Technology Basics
MPLS Layer-3 VPNs
MPLS Layer-2 VPNs
Advanced Topics
Summary
BRKMPL-1101
Cisco Public
Introduction
What is MPLS?
Brief Summary
Its 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
BRKMPL-1101
Cisco Public
Technology Comparison
Key Characteristics of IP, Native Ethernet, and MPLS
IP
Native Ethernet
MPLS
Destination address based

Forwarding table learned
from control plane
TTL support

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

and signaling protocols
Routing Protocols
MPLS protocols
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
E-OAM
MPLS OAM
Forwarding
Control Plane
Packet Encapsulation
BRKMPL-1101
Cisco Public
Evolution of MPLS
Technology Evolution and Main Growth Areas
Today
Evolved from tag switching in 1996 to full IETF

standard, covering over 130 RFCs
Key application initially were Layer-3 VPNs,
followed by Traffic Engineering (TE),
and Layer-2 VPNs
Optimize MPLS
for Cloud
Optimize MPLS for
packet transport
Optimize MPLS for video
Complete base MPLS portfolio

Bring MPLS to Market
First
L3VPNs
Deployed
Cisco ships
MPLS
First MPLS TE
Deployments
1997 1998 1999 2000
BRKMPL-1101
Large Scale
L2VPN
Deployments
First L2VPN
Deployments
Large Scale
L3VPN
Deployments
2001 2002 2003 2004
Large Scale
MPLS TE
Deployments
2005 2006 2007 2008
First LSM
Deployments
First MPLS TP
Deployments
2009 2010 2011 2012
Cisco Public
2013 2014
Market Segments
MPLS Business Drivers and Typical Deployment Characteristics
Service Provider
Enterprise
Data Center
BRKMPL-1101
Business Drivers
Business Goals
MPLS Capabilities
S Networking service reliability

S Cost effective service
bandwidth
S Flexible enablement of
existing and new services
S Leverage single network for scalable

delivery of multiple services
S Optimize network capacity to meet
current and future growth of service
bandwidth
S Deliver premium services with
guaranteed SLAs
Layer-3 VPN
Layer-2 VPN
MPLS TE
MPLS OAM, QoS
S Mergers and acquisitions

S Network consolidation
S Shared services
S Compliance
S Network Segmentation
S Network integration
S Multi-tenant hosting
S Data Center Interconnect
S Leverage single data center

infrastructure for multiple users and
services
S Deliver geographic independent
services from any data center
Layer-3 VPN
Cisco Public
Layer-2 VPN
Layer-3 VPN
Cisco Platform Coverage

MPLS Support by Cisco Platforms (Typical Deployments)
Access
Aggregation
Distribution
Enterprise
Core Backbone
WAN Edge
ISR/G2
6500
NEXUS 7K
ASR1K
Data Center
NEXUS 7K
6500
6500
6500
NEXUS 7K
ASR9000
7600
Service Provider
ASR901
ASR903
ASR9000
ME3800X
BRKMPL-1101
7600
CRS
GSR
ASR9000
ASR9000
GSR
ASR1K
7600
Cisco Public
10
MPLS Technology Basics

Technology Building Blocks of MPLS
Topics
Basics of MPLS Signaling and Forwarding

MPLS reference
architecture
Service (Clients)
MPLS Labels
Management
Layer-3 VPNs
MPLS Traffic Engineering

MPLS OAM and MIBs
Transport
IP/MPLS (LDP/RSVP-TE/BGP)
MPLS MIBs and OAM
MPLS signaling and

forwarding operations
Layer-2 VPNs
MPLS Forwarding
BRKMPL-1101
Cisco Public
12
MPLS Reference Architecture

Different Type of Nodes in a MPLS Network
P (Provider) router
Label switching router (LSR)
Switches MPLS-labeled
packets
PE (Provider Edge) router

Edge router (LER)
Imposes and removes
MPLS labels
MPLS Domain
CE
PE
PE
CE
CE
CE
PE
CE (Customer Edge) router

Connects customer network
to MPLS network
BRKMPL-1101
PE
Label switched trac
Cisco Public
13
MPLS Shim Labels
Label Definition and Encapsulation

Labels used for making
forwarding decision
Multiple labels can be used
for MPLS packet
encapsulation
Creation of a label stack
Outer label always used for

switching MPLS packets in
network
Remaining inner labels used
to specific services
(e.g., VPNs)
MPLS Label
0
1
2
3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
Label # 20bits
TC
TTL-8bits
TC = Trac Class: 3 Bits; S = Boom of Stack; TTL = Time to Live
MPLS Label Encapsulaon

LAN MAC Label Header
LAN MAC Label Header
MAC Header
Label
Layer 3 Packet
MPLS Label Stack

MAC Header
Label
Label S
Layer 3 Packet
Boom of Stack Bit Set
BRKMPL-1101
Cisco Public
14
MPLS QoS
QoS Marking in MPLS Labels

MPLS label contains 3 TC bits
Used for packet classification and
prioritization
Similar to Type of Service (ToS)
field in IP packet (DSCP values)
MPLS DiServ Marking

in Trac Class Bits
DSCP values of IP packet mapped

into TC bits of MPLS label
TC
At ingress PE router
Most providers have defined 35

service classes (TC values)
Layer-2 Header
MPLS Header
IP DiServ Marking
DSCP
Layer 3 Header
Different DSCP <-> TC mapping

schemes possible
Uniform mode, pipe mode, and
short pipe mode
BRKMPL-1101
Cisco Public
15
Basic MPLS Forwarding Operations
How Labels Are Being Used to Establish End-to-end Connectivity

Label imposition (PUSH)
By ingress PE router;
classify and label packets
Based on Forwarding
Equivalence Class (FEC)
Label swapping or switching

By P router; forward packets
using labels; indicates
service class & destination
Label disposition (POP)

By egress PE router;
remove label and forward
original packet to
destination CE
BRKMPL-1101
Label Imposion (Push)

Label Swap
L1
L1
L2
Label Swap
L2
L3
Label Disposion
(PoP)
L3
L2/L3 Packet
CE
PE
PE
CE
CE
CE
PE
Cisco Public
PE
16
MPLS Path (LSP) Setup and Traffic Forwarding

MPLS Traffic Forwarding and MPLS Path (LSP) Setup
LSP signaling
Either LDP* or RSVP
Leverages IP routing
Routing table (RIB)
Forwarding
Exchange of labels
IP
MPLS

from control plane
TTL support
Label based
from control plane
TTL support
Label bindings
Control Plane
OSPF, IS-IS, BGP
OSPF, IS-IS, BGP

LDP, RSVP
Downstream MPLS node

advertises what label to use
to send traffic to node
Packet
Encapsulation
IP Header
One or more labels
QoS
8 bit TOS field in IP header
3 bit TC field in label
OAM
IP ping, traceroute
MPLS OAM
MPLS forwarding
MPLS Forwarding table
(FIB)
* LDP signaling assumed for next the examples
BRKMPL-1101
Cisco Public
17
MPLS Path (LSP) Setup

Signaling Options
LDP signaling
Leverages existing routing
RSVP signaling
Aka MPLS RSVP/TE
Enables enhanced
capabilities, such as
Fast ReRoute (FRR)
Forwarding path
Forwarding
Calculation
Packet
Encapsulation
Signaling
BRKMPL-1101
LDP
RSVP
LSP
LSP or TE Tunnel
Primary and, optionally, backup
Based on IP routing database

Shortest-Path based
Based on TE topology
database
Shortest-path and/or other
constraints
(CSPF calculation)
Single label
One or two labels
By each node independently

Uses existing routing
protocols/information
Initiated by head-end node

towards tail-end node
Uses routing protocol
extensions/information
Supports bandwidth reservation
Supports link/node protection
Cisco Public
18
IP Packet Forwarding Example

Basic IP Packet Forwarding
IP routing information
exchanged between
nodes
Via IGP (e.g., OSFP,
IS-IS)
Forwarding Table
Forwarding Table
Address
Prex
128.89

171.69
BRKMPL-1101
Address
Prex
I/F
Address
Prex
I/F
128.89

171.69
I/F
128.89

171.69
Packets being
forwarded based on
destination IP address
Lookup in routing table
(RIB)
Forwarding Table
128.89
0
0
128.89.25.4
128.89.25.4
Data
Data
1
128.89.25.4
Data
128.89.25.4
Data
171.69
Cisco Public
19

Step 1: IP Routing (IGP) Convergence
Exchange of IP routes
OSPF, IS-IS, EIGRP,
etc.
Establish IP
reachability
Forwarding Table
In
Label
Address Out Out

Prex
Iface Label
Forwarding Table
In
Label
Address Out Out

Prex
Iface Label
128.89
128.89
171.69
171.69
Forwarding Table
In
Label
Address Out Out

Prex
Iface Label
128.89
0 128.89
0
1
1
You Can Reach 128.89 and

171.69 Thru Me
Roung Updates (OSPF,

EIGRP, )
BRKMPL-1101
0
1
1
You Can Reach 128.89 Thru Me
You Can Reach 171.69 Thru Me
Cisco Public
171.69
20

Step 2A: Assignment of Local Labels
Each MPLS node

assigns a local label to
each route in local
routing table
In label
Forwarding Table
In
Label
Forwarding Table
Address Out Out

Prex
Iface Label
In
Label
128.89
20
128.89
171.69
21
171.69
Forwarding Table
Address Out Out

Prex
Iface Label
In
Label
Address Out Out

Prex
Iface Label
30
128.89
0 128.89
0
1
1
1
171.69
BRKMPL-1101
Cisco Public
21

Step 2B: Assignment of Remote Labels
Local label mapping

are sent to connected
nodes
Receiving nodes
update forwarding
table
Out label
Forwarding Table
In
Label
Forwarding Table
Address Out Out

Prex
Iface Label
In
Label
128.89
20
20
128.89
30
171.69
21
21
171.69
36
In
Label
Address Out Out

Prex
Iface Label
30
128.89
0 128.89
0
Label Distribuon
Protocol (LDP)
Use Label 30 for 128.89

1
1
(Downstream Allocaon)
Use Label 20 for 128.89 and

BRKMPL-1101
Forwarding Table
Address Out Out

Prex
Iface Label
Cisco Public
171.69
22
MPLS Traffic Forwarding
Hop-by-hop Traffic Forwarding Using Labels

Ingress PE node adds
label to packet (push)
Via forwarding table
Downstream node use

label for forwarding
decision (swap)
Forwarding Table
In
Label
Address Out Out

Prex
Iface Label
Address Out Out

Prex
Iface Label
128.89
20
20
128.89
30
171.69
21
21
171.69
36
In
Label
Address Out Out

Prex
Iface Label
30
128.89
0 128.89
0
128.89.25.4
Data
20
0
128.89.25.4
Egress PE removes label

and forwards original
packet (pop)
BRKMPL-1101
In
Label
Forwarding Table
Outgoing interface
Out label
Forwarding Table
30
128.89.25.4
Data
128.89.25.4
Data
Data
1
1
Forwarding based on Label
Cisco Public
171.69
23
MPLS TE Fast ReRoute (FRR)
Implementing Network Failure Protection Using MPLS RSVP/TE

Steady state
Router A
Primary tunnel:
Router B
Router D
Router E
ABDE
Backup tunnel:
B C D (pre-provisioned)
Failure of link between

router B and D
Traffic rerouted over
backup tunnel
Router Y
Router X
Router C
Primary Tunnel
Recovery time* ~ 50 ms
Backup Tunnel
*Actual Time VariesWell Below 50 ms in Lab Tests, Can Also Be Higher

BRKMPL-1101
Cisco Public
24
MPLS SNMP MIBs

SNMP Management Access to MPLS Resources
MPLS-LSR-STD-MIB
Provides LSP end-point and LSP cross-connect information
Frequently used: none L
MPLS-LDP-STD-MIB
Provides LDP session configuration and status information
Frequently used: LDP session status Trap notifications
MPLS-L3VPN-STD-MIB
Provides VRF configuration and status information and associated interface mappings
Frequently used: VRF max-route Trap notifications
MPLS-TE-STD-MIB
Provides TE tunnel configuration and status information
Frequently used: TE Tunnel status Trap notifications
BRKMPL-1101
Cisco Public
25
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 reach ability 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
BRKMPL-1101
Cisco Public
26
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 OAM and MIBs can be used for MPLS connectivity validation and
troubleshooting
BRKMPL-1101
Cisco Public
27
MPLS Virtual Private Networks

Technology Overview
MPLS Virtual Private Networks

Topics
Definition of MPLS VPN

service
Service (Clients)
Technology options
BRKMPL-1101
Layer-3 VPNs
Layer-2 VPNs
Transport
MPLS Forwarding
Cisco Public

MPLS MIBs and OAM
Basic MPLS VPN

deployment scenario
Management
29
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
BRKMPL-1101
Cisco Public
30
MPLS VPN Example

Basic Building Blocks
VPN policies
Configured on PE routers
(manual operation)
VPN signaling
PE
CE
Between PEs
VPN
Policy
Exchange of VPN policies
VPN traffic forwarding
VPN Signaling
PE-CE
Link
CE
VPN
Policy
Additional VPN-related
MPLS label encapsulation
PE
VPN
PE-CE
Link
PE
CE
VPN
Policy
VPN
Policy
CE
PE
PE-CE link
Connects customer network
to MPLS network; either
layer-2 or layer-3
BRKMPL-1101
Label Switched Trac
Cisco Public
31
MPLS VPN Models

Technology Options
MPLS Layer-3 VPNs

Peering relationship
between CE and PE
MPLS Layer-2 VPNs

Interconnect of layer-2
Attachment Circuits (ACs)
MPLS VPN Models

MPLS Layer-2 VPNs
Point-to-Point
Layer-2 VPNs
CE connected to
PE via p2p L2
connecon (FR,
ATM)
CEs peer with
each other (IP
roung) via p2p
layer-2 VPN
connecon
CE-CE roung; no
SP involvement
BRKMPL-1101
Mul-Point
Layer-2 VPNs
CE connected to PE
via Ethernet
connecon (VLAN)
CEs peer with each
other via fully/
paral mesh
Layer-2 VPN
connecon
MPLS Layer-3 VPNs

CE connected to PE via IP-based
connecon (over any layer-2 type)
Stac roung
PE-CE roung protocol; eBGP, OSPF,
IS-IS
CE roung has peering relaonship with
PE router; PE routers are part of
customer roung
PE routers maintain customer-specic
roung tables and exchange
customer=specic roung informaon
CE-CE roung; no
SP involvement
Cisco Public
32
MPLS Layer-3 Virtual Private Networks

End-to-end Layer-3 Services Over MPLS Networks

Topics
Technology components
Service (Clients)
VPN control plane

mechanisms
Management
Layer-3 VPNs
Layer-2 VPNs
Deployment use cases

Business VPN services
Network segmentation
Data Center access
BRKMPL-1101
Transport
MPLS Forwarding
Cisco Public
MPLS MIBs and OAM
VPN forwarding plane
34
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-iBGP)

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
BRKMPL-1101
Cisco Public
35
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 forwarding table
Typically, VRF created for each

customer VPN
Separates customer traffic
VPN 1
VRF Green
PE
CE
VPN 2
MPLS Backbone
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
BRKMPL-1101
Cisco Public
36
VPN Route Distribution
Exchange of VPN Policies Among PE Routers

Full mesh of BGP sessions
among all PE routers
BGP Route Reflector
Multi-Protocol BGP
extensions (MP-iBGP) to
carry VPN policies
PE-CE routing options
Static routes
eBGP
BGP Route Reector
PE-CE
Link
PE
CE
PE
Blue VPN
Policy
CE
CE
BlueVPN
Policy`
Red VPN
Policy CE
Red VPN
Policy
PE
OSPF
IS-IS
BRKMPL-1101
PE-CE
Link
PE
Label Switched Trac
Cisco Public
37
VPN Control Plane Processing

VRF Parameters
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
BRKMPL-1101
Cisco Public
38
VPN Control Plane Processing

Interactions Between VRF and BGP VPN Signaling
1. CE1 redistribute IPv4 route
to PE1 via eBGP
2. PE1 allocates VPN label for
prefix learnt from CE1 to
create unique VPNv4 route
3. PE1 redistributes VPNv4
route into MP-iBGP, it sets
itself as a next hop and
relays VPN site routes to
PE2
4. PE2 receives VPNv4 route
and, via processing in local
VRF (green), it redistributes
original IPv4 route to CE2
BRKMPL-1101
eBGP:
16.1/16
IP Subnet
CE1
PE1
BGP adversement:
VPN-IPv4 Addr = RD:16.1/16
BGP Next-Hop = PE1
Route Target = 100:1
Label=42
Blue VPN
eBGP:
16.1/16
IP Subnet
PE2
CE2
VRF
ip
vrfparameters:
blue-vpn
Name
= blue-vpn
RD 1:100
RD
= 1:100 export 1:100
route-target
Import
Route-Target
= 100:1
route-target
import 1:100
Export Route-Target = 100:1
Cisco Public
39
VPN Forwarding Plane Processing

Forwarding of Layer-3 MPLS VPN Packets
1. CE2 forwards IPv4 packet to PE2
2. PE2 imposes pre-allocated VPN
label to IPv4 packet received from
CE2
3. PE2 imposes outer IGP label A
(learned via LDP) and forwards
labeled packet to next-hop
P-router P2
4. P-routers P1 and P2 swap outer
IGP label and forward label
packet to PE1
IGP VPNv4 IPv4

Label C Label
IPv4
Learned via MP-IBGP
IGP VPNv4 IPv4

Label A Label
IPv4
IPv4
Packet
IPv4
Packet
CE1
PE1
A->B (P2) and B->C (P1)
5. Router PE1 strips VPN label and

IGP labels and forwards IPv4
packet to CE1
BRKMPL-1101
IGP VPNv4 IPv4

Label B Label
P1
Blue VPN P2

PE2
CE2
VRF
ip vrfparameters:
blue-vpn
Name
= blue-vpn
RD 1:100
RD
= 1:100 export 1:100
route-target
Import
Route-Target
= 1:100
route-target
import 1:100
Export Route-Target = 1:100
Cisco Public
40
Service Provider Deployment Scenario

MPLS Layer-3 VPNs for Offering Layer-3 Business VPN Services
Deployment Use Case
Managed VPN Service
Delivery of IP VPN services

to business customers
Benefits
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
BRKMPL-1101
Unmanaged VPN Service
Edge
Network Segment
MPLS Node
Typical Platforms
Core
VPN
Core
Edge
CPE
CPE
Edge
Core
CE
PE
ASR1K
ASR9K
CRS-1
ISR/G2
7600
GSR
ASR1K
ASR9K
ASR903
ME3800X
Cisco Public
41
Enterprise Deployment Scenario
MPLS Layer-3 VPNs for Implementing Network Segmentation

Deployment Use Case
Segmentation of enterprise
network to provide selective
connectivity for specific user
groups and organizations
Benefits
Network segmentation only
requires edge node
configuration
MPLS VPNs for L3 Network Segmentaon
Access
Edge
Network Segment
MPLS Node
Typical Platforms
Flexible routing; different IP

connectivity can be easily
configured; e.g., full/partial
mesh
BRKMPL-1101
Core
VPN
Core
Edge
Access
Access
Edge
Core
CE
PE
ASR1K
7600
CRS-1
ISR/G2
ASR1K
GSR
ASR9K
7600
6500
Cisco Public
42
Data Center Deployment Scenario
MPLS Layer-3 VPNs for Segmented L3 Data Center Access and Interconnect
Deployment Use Case
MPLS VPNs terminang on DC aggregaon
Segmented WAN Layer-3

at Data Center edge
Layer-3 segmentation in
Data Center
MPLS VPNs
at DC edge
Access
Top Of Rack Distribuon
Benefits
Only single Data Center
edge node needed for
segmented layer-3 access
Enables VLAN/Layer-2
scale (> 4K)
BRKMPL-1101
Core
Core
Edge
Data Center
Network Segment
MPLS Node
Typical Platforms
Distribution
Core
Edge
CE or PE
P or CE
PE
N7K
N7K
ASR9K
6500
6500
7600
Cisco Public
43
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-1101
Cisco Public
44

End-to-end Layer-2 Services Over MPLS Networks

Topics
L2VPN technology options

P2P VPWS services (PWs)
Overview & Technology Basics
VPN control plane
MP2MP VPLS services

Overview & Technology Basics
VPN control plane
Deployment use cases
Management
Layer-3 VPNs
Layer-2 VPNs
Transport
MPLS Forwarding

MPLS MIBs and OAM
Service (Clients)
L2 Business VPN services

Data Center Interconnect
BRKMPL-1101
Cisco Public
46

Technology Options
VPWS services
MPLS Layer-2 VPNs
Point-to-point
Referred to as
Pseudowires (PWs)*
VPLS services
Multipoint-to-Multipoint
Point-to-Point
Layer-2 VPNs (PWs)
CE connected to PE via
p2p L2 connecon
(e.g., FR, ATM)
CEs peer with each other
(IP roung) via p2p layer-2
VPN connecon
CE-CE roung; no MPLS
network involvement
Mulpoint-to-Mulpoint
Layer-2 VPNs (VPLS)
CE connected to PE via
Ethernet connecon (VLAN)
CEs peer with each other via
fully/paral mesh Layer-2
VPN connecon
CE-CE roung; no MPLS
network involvement
* Used to be referred to as Any Transport over MPLS or AToM as well.

BRKMPL-1101
Cisco Public
47
Virtual Private Wire Services (VPWS)

Overview of Pseudowire (PW) Architecture
Based on IETFs PseudoWire (PW) Reference Model
Enables transport of any
Layer-2 traffic over MPLS
Includes additional VC label
encapsulation and
translation of L2 packets
ATM, ATM, FR, or PPP
Aachment
Circuit (AC)

PE
CE
Pseudo-Wire 1
PE
Layer-2
CE
Layer-2
Pseudo-Wire 2
CE
CE
Layer-2
PE-CE link is referred to as

Attachment Circuit (AC)
Support for L2 interworking
PWs are bi-directional
BRKMPL-1101
Aachment
Circuit (AC)
PE
PE
Layer-2
Emulated Layer-2 Service

Label Switched Trac
Cisco Public
48
Virtual Private Wire Services (VPWS)

VPN policies
Virtual cross-connect (Xconnect)
Maps customer interface (AC) to PW (1:1 mapping)
VPN signaling
Targeted LDP* or BGP session between ingress and egress PE router
Virtual Connection (VC)-label negotiation, withdrawal, error notification
1 or 2 labels used for encapsulation + 1 (IGP) label for forwarding: VC label + optional control word
Inner de-multiplexer (VC) label: identifies L2 circuit (packet)
Control word: replaces layer-2 header at ingress; used to rebuild layer-2 header at egress
Outer tunnel (IGP) label: to get from ingress to egress PE using MPLS LSP
PE-CE link
Referred to as Attachment Circuit (AC)
Can be any type of layer-2 connection (e.g., FR, ATM)
* LDP is assumed as signaling protocol for next examples
BRKMPL-1101
Cisco Public
49
VPWS Control Plane Processing

Signaling of a New Pseudo-Wire
1. New Virtual Circuit (VC) crossconnect connects customer L2
interface (AC) to new PW via
VC ID and remote PE ID
2. New targeted LDP session
between PE1 and PE2 is
established, in case one
does not already exist
3. PE binds VC label with
customer layer-2 interface and
sends label-mapping to
remote PE
4. Remote PE receives LDP label
binding message and matches
VC ID with local configured VC
cross-connect
BRKMPL-1101
3
4
PE
CE
Layer-2
2
P
Label Mapping Messages
LDP session
4
PE
1
CE
Layer-2
Emulated Layer-2 Service
Cisco Public
50
VPWS Forwarding Plane Processing

Forwarding of Layer-2 Traffic Over PWs
1. CE2 forwards L2 packet to PE2.
2. PE2 pushes VC (inner) label to L2
packet received from CE2
Optionally, a control word is added
as well (not shown)
3. PE2 pushed outer (Tunnel) label

and forwards packet to P2
L2
Layer-2
Tunnel VC
Label C Label L2
CE1 Packet PE1
Tunnel VC
Label B Label L2
P1
Tunnel VC
Label A Label L2
P2
L2
Layer-2
PE2 Packet CE2
4. P2 and P1 forward packet using

outer (tunnel) label (swap)
5. 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
BRKMPL-1101
Cisco Public
51
Virtual Private LAN Services

Overview of VPLS Architecture
Architecture for Ethernet
Multipoint Services over
MPLS
VPLS network acts like a
virtual switch that emulates
conventional L2 bridge
Fully meshed or HubSpoke topologies
supported
PE-CE link is referred to
as Attachment Circuit (AC)
Aachment
Circuit (AC)

PE
CE
PE
Layer-2
CE
Layer-2
CE
CE
Layer-2
Always Ethernet
BRKMPL-1101
Aachment
Circuit (AC)
PE
PE
Layer-2
Emulated Virtual Switch

Label Switched Trac
Pseudo-Wire
Cisco Public
52
Virtual Private LAN Services (VPLS)

VPN policies
Virtual Switching Instance or VSI
One or more customer interfaces are connected to VSI
One or more PWs for interconnection with related VSI instances on remote PE
VPN signaling
Full mesh of targeted LDP* (VC exchange) and/or BGP sessions (discovery and VC exchange)
Virtual Connection (VC)-label negotiation, withdrawal, error notification

1 VC label used for encapsulation + 1 (IGP) label for forwarding
Inner de-multiplexer (VC) label: identifies VSI
Outer tunnel (IGP) label: to get from ingress to egress PE using MPLS LSP
PE-CE link
Referred to as Attachment Circuit (AC)
Ethernet VCs are either port mode or VLAN ID
* LDP is assumed as signaling protocol for next examples
BRKMPL-1101
Cisco Public
53
VPLS Forwarding Plane Processing

Forwarding of Layer-2 Traffic Over VPLS Network
MAC learning:
For new L2 packets
VSI forwarding table updated
Packets flooded to all PEs
over PWs
Layer-2 Packet Forwarding:
For L2 packets with known
destination MAC addresses
Lookup in VSI forwarding
table
L2 packet forwarded onto
PWs to remote PE/VSI
L2
Tunnel VSI
Label C Label L2
PE
CE
Tunnel VSI
Label B Label L2
Tunnel VSI
Label A Label L2
L2
PE
Layer-2
CE
Layer-2
CE
CE
Layer-2
PE
PE
Layer-2
Emulated Virtual Switch

Label Switched Trac
Full Mesh of Pseudo-Wires
BRKMPL-1101
Cisco Public
54

PWs for Offering Layer-2 Business VPN Services
Deployment Use Case
Delivery of E-LINE
services to business
customers
Benefits
Leverage same network

for multiple services and
customers (CAPEX)
Highly scalable
Layer-2 VPN Service
NID
Edge
Ethernet
xconnect
Network Segment
MPLS Node
Service enablement only

requires edge node
configuration (OPEX)
Core
Typical Platforms
MPLS Core
Network
Edge
NID
Ethernet
xconnect
NID *
Edge
Core
CE
U-PE
M3400
ME3800X
CRS-1
ASR901
ASR903
GSR
ASR9K
ASR9K
* NID : Network Interface Device
BRKMPL-1101
Cisco Public
55
Data Center Deployment Scenario
VPLS for Layer-2 Data Center Interconnect (DCI) Services
Data Center
DC
Edge
Deployment Use Case

E-LAN services for Data
Center interconnect
Benefits
Single WAN uplink to
connect to multiple
Data Centers
Easy implementation of
segmented layer-2 traffic
between Data Centers
Data Center
DC
Edge
Core
Edge
Data Center
Edge
DC
Edge
Ethernet
Core
Network Segment
MPLS Node
Typical Platforms
BRKMPL-1101
Core
Edge
Core
Ethernet
DC Edge
Core
Edge
CE
PE
ASR9K
CRS-1
ASR9K
7600
GSR
7600
6500
ASR9K
Cisco Public
56
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 L2VPN 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)
Typical applications of L2VPNs are layer-2 business VPN services and
Data Center interconnect
BRKMPL-1101
Cisco Public
57
Advanced Topics
Latest MPLS Technology Developments, Trends, and Futures
MPLS And IPv6
IPv6 Support for Native MPLS Deployments and MPLS Layer-3 Services
IPv6 traffic carried over IPv4
MPLS network
Encapsulation of IPv6 into
IPv4 LSP (6PE)
IPv6
6PE
CE
IPv6
IPv4 MPLS
6PE
CE
Encapsulation of IPv6 into

MPLS layer-3 VPN (6VPE)
Translation of IPv6 to IPv4
at PE edge
IPv6
CE
6VPE
IPv6
IPv4 MPLS
v6VPN

6VPE
CE
BRKMPL-1101
Cisco Public
59
Label Switched Multicast (LSM)

Point-to-Multi-Point MPLS Signaling and Connectivity
What is Label Switched Multicast?
MPLS extensions to provide
P2MP connectivity
RSVP extensions and multicast
LDP
Uni-Direconal
LSP
MPLS / IP
IP/MPLS
Why Label-Switched Multicast?

Enables MPLS capabilities, which
can not be applied to IP multicast
traffic (e.g., FRR)
Benefits of Label-Switched
Multicast
Efficient IP multicast traffic
forwarding
P2MP or MP2MP
LSP Tree
Label Switched
Mulcast (LSM)
Enables MPLS traffic protection and

BW control of IP multicast traffic
BRKMPL-1101
IP/MPLS
Cisco Public
MPLS Transport Profile (TP)
Bi-Directional MPLS Tunnel Extensions For Transport Oriented Connectivity

What is MPLS TP?
Point-to-point static LSPs which
are co-routed
Bi-directional TP tunnel
Why MPLS TP?
Migration of TDM legacy
networks often assume
continuation of connectionoriented operations model
MPLS TP enables packet-based
transport with connectionoriented connectivity
Benefits of MPLS TP
Meets transport-oriented
operations requirements
Enables seamless migration to
dynamic MPLS
BRKMPL-1101
Bi-Direconal
MPLS TP Tunnel
PE
CE
PE
CE
Transport
IP/MPLS
(LDP/RSVP-TE/BGP)
MPLS-TP
(Stac/RSVP-TE)
MPLS Forwarding
Cisco Public
61
Futures
New MPLS Developments on the Horizon
MPLS and Cloud

Integraon
VPN Data Center
Integraon
MPLS Transport
Evoluon
MPLS TP and GMPLS

Integraon
BRKMPL-1101
Cisco Public
62
Summary
Final Notes and Wrap Up
Summary
Key Takeaways
Its 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

Defacto for most SPs, large enterprises, and increasingly in Data Centers
Ongoing technology evolution

IPv6, optimized video transport, TP transport evolution, and cloud integration
BRKMPL-1101
Cisco Public
64
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
BRKMPL-1101
Cisco Public
65
References
Further Readings on MPLS Technology
Cisco Live 2012

MPLS Sessions
BRKMPL-1101 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 Global MPLS WAN Redesign Case Study
BRKMPL-2109 MPLS Solutions for Cloud Networking
BRKMPL-3101 Advanced Topics and Future Directions in MPLS
LTRMPL-2104 Implementing MPLS in Service Provider Networks: Introduction
LTRMPL-2105 Implementing MPLS in Service Provider Networks: Advanced
LTRMPL-2106 Enterprise Network Virtualization using IP and MPLS Technologies
TECMPL-3002 MPLS Transport Profile (MPLS-TP) - Enabling evolution of transport
networks
BRKMPL-1101
Cisco Public
67
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
BRKMPL-1101
Cisco Public
68
Terminology Reference
Acronyms Used in MPLS Reference Architecture
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
BRKMPL-1101
Cisco Public
69
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
BRKMPL-1101
Cisco Public
70
Complete Your Online

Session Evaluation
Give us your feedback and
you could win fabulous
prizes.
Winners announced daily.
Receive 20 Passport points
for each session evaluation
you complete.
Complete your session
evaluation online now (open
a browser through our
wireless network to access
our portal) or visit one of the
Internet stations throughout
the Convention Center.
BRKMPL-1101
Dont forget to activate your

Cisco Live Virtual account for access to
all session material, communities, and
on-demand and live activities throughout
the year. Activate your account at the
Cisco booth in the World of Solutions or visit
www.ciscolive.com.
Cisco Public
71
Presentation_ID
Cisco Public
Label Distribution Protocol
For your
reference only
Overview
MPLS nodes need to exchange label information with each other
Ingress PE node (Push operation)
Needs to know what label to use for a given FEC to send packet to neighbor
Core P node (Swap operation)

Needs to know what label to use for swap operation for incoming labeled packets
Egress PE node (Pop operation)

Needs to tell upstream neighbor what label to use for specific FEC type LDP used for exchange of label
(mapping) information
Label Distribution Protocol (LDP)

Defined in RFC 3035 and RFC3036; updated by RFC5036
LDP is a superset of the Cisco-specific Tag Distribution Protocol
Note that, in addition LDP, also other protocols are being used for label information
exchange
Will be discussed later
BRKMPL-1101
Cisco Public
73
For your
reference only
Some More Details

Assigns, distributes, and installs (in forwarding) labels for prefixes advertised by unicast routing
protocols
OSPF, IS-IS, EIGRP, etc.
Also used for Pseudowire/PW (VC) signaling

Used for L2VPN control plane signaling
Uses UDP (port 646) for session discovery and TCP (port 646) for exchange of LDP messages
LDP operations
LDP Peer Discovery
LDP Session Establishment
MPLS Label Allocation, Distribution, and Updating MPLS forwarding
Information repositories used by LDP

LIB: Label Information Database (read/write)
RIB: Routing Information Database/routing table (read-only)
BRKMPL-1101
Cisco Public
74
For your
reference only
Operations Details
LDP startup
Local labels assigned to RIB
prefixes and stored in LIB
Peer discovery and session
setup
Exchange of MPLS label
bindings
Programming of MPLS
forwarding
Based on LIB info
CEF/MFI updates
BRKMPL-1101
MPLS Node A
LDP Control Plane
MPLS Node B
Session Setup
RIB
LIB
RIB
LIB
Label Binding
Exchange
LDP Interacons
with
MPLS Forwarding
MPLS
Forwarding
CEF/MFI
MPLS
Forwarding
CEF/MFI
Cisco Public
75
Why MPLS QoS
For your
reference only
The Need for Differentiated Services
Typically different traffic types (packets) sent over MPLS networks

E.g., Web HTTP, VoIP, FTP, etc.
Not all traffic types/flows have the same performance requirements

Some require low latency to work correctly; e.g., video
MPLS QoS used for traffic prioritization to guarantee minimal traffic loss
and delay for high priority traffic
Involves packet classification and queuing
MPLS leverages mostly existing IP QoS architecture

Based on Differentiated Services (DiffServ) model; defines per-hop behavior
based on IP Type of Service (ToS) field
BRKMPL-1101
Cisco Public
76
MPLS Uniform Mode
For your
reference only
QoS Field Assignments in MPLS Network

End-to-end behavior:
Original IP DSCP value not
preserved
At ingress PE:
CE
PE
IP DSCP value copied in

EXP value of MPLS label
EXP value changed in the

MPLS core
Based on traffic load and
congestion
CE
IP DSCP
3
MPLS
EXP 3
MPLS
EXP 2
MPLS
EXP 3
MPLS
EXP 3
MPLS
EXP 2
IP
DSCP 3
IP
DSCP 3
IP
DSCP 3
PE
IP
DSCP 2
IP
DSCP
2
At egress PE:
EXP value copied back into
IP DSCP value
BRKMPL-1101
Cisco Public
77
MPLS Pipe Mode
For your
reference only

Original IP DSCP is
preserved
CE
At ingress PE:
PE
EXP value set based on

ingress classification
EXP changed in the MPLS

core
congestion
CE
IP DSCP
3
PE
MPLS
EXP 3
MPLS
EXP 2
MPLS
EXP 2
MPLS
EXP 3
MPLS
EXP 3
MPLS
EXP 3
MPLS
EXP 2
IP DSCP
3
IP DSCP
3
IP DSCP
3
IP DSCP
3
IP DSCP
3
At egress PE:
EXP value not copied back
into IP DSCP value
BRKMPL-1101
Cisco Public
78
MPLS Short Pipe Mode
For your
reference only

Original IP DSCP is
preserved
CE
At ingress PE:
PE
EXP value set based on

ingress classification
EXP changed in the MPLS

core
congestion
CE
IP DSCP
3
MPLS
EXP 3
MPLS
EXP 2
MPLS
EXP 3
MPLS
EXP 3
MPLS
EXP 2
IP DSCP
3
IP DSCP
3
IP DSCP
3
PE
IP DSCP
3
IP DSCP
3
At egress PE:
Original IP DSCP value
used for QoS processing
BRKMPL-1101
Cisco Public
79
Why MPLS Traffic Engineering?
For your
reference only
Drivers for MPLS Traffic Management
Need for better utilization of available network bandwidth

Optimize traffic distribution throughout network
Network capacity management
Protection against link and node failures

Fast rerouting around failures to minimize (service) traffic loss
Optimize aggregate availability of network
Delivery of premium services and enhanced SLAs

Ability to support guaranteed high availability and bandwidth for services
Congestion in network due to changing traffic patterns

Optimize high bandwidth traffic flows; streaming video, database backup, etc.
BRKMPL-1101
Cisco Public
80
The Problem with Shortest-Path Forwarding

Alternate Path Under Utilization As a Result of Least-Cost Routing
Some links are DS3, some
are OC-3
Router A has 40M of traffic
for router F, 40M of traffic
for router G
Massive (44%) packet loss
at router Brouter E!
Changing to traffic
forwarding to A->C->D->E
wont help
Node
Next-Hop
Cost
10
10
20
20
30
30
Router B
Router A
b Dr
OC-3
ops
OC-3
Router E
Router G
DS3
OC-3
Router C
BRKMPL-1101
DS3
Tra
b
80 M
Router F
35 M
DS3
OC-3
Router D
Cisco Public
81
How MPLS TE Solves the Problem
For your
reference only
Optimized Path Computation Via Additional Costs Metrics

Router A sees all links
Router A computes paths
on properties other than
just shortest cost
Creation of 2 tunnels
Node
Next-Hop
Cost
10
10
20
20
Tunnel 0
30
Tunnel 1
30
No link oversubscribed!
Router B
Router A
OC-3
OC-3
DS3
40 M
40 Mb
OC-3
Router C
BRKMPL-1101
Router F
DS3
Router E
Router G
DS3
OC-3
Router D
Cisco Public
82
TE Tunnel Signaling
For your
reference only
RSVP Signaling of MPLS Connectivity

Tunnel signaled with TE extensions
to RSVP
Soft state maintained with
downstream PATH messages
Soft state maintained with upstream
RESV messages
New RSVP objects
LABEL_REQUEST (PATH)
LABEL (RESV)
EXPLICIT_ROUTE
RECORD_ROUTE (PATH/RESV)
SESSION_ATTRIBUTE (PATH)
IP/MPLS
Head end
L=16
Tail end
RESV
PATH
Input
Label
Out Label,
Interface
17
16, 0
TE LSP
LFIB populated using RSVP labels

allocated by RESV messages
BRKMPL-1101
Cisco Public
83
MPLS Traffic Engineering
For your
reference only
Technology Building Blocks

Link information Distribution*
ISIS-TE
OSPF-TE
Path Calculation (CSPF)*
At head-end node
Path Setup (RSVP-TE)
Unidirectional forwarding traffic
down Tunnel
Auto-route
Static
PBR
CBTS / PBTS
Forwarding Adjacency
Tunnel select
Head end
IP/MPLS
Mid-point
Tail end
TE LSP
* Oponal
BRKMPL-1101
Cisco Public
84
Distribution of Link Information
For your
reference only
Additional Metrics for Path Computation

Additional link characteristics
Interface address
IP/MPLS
Neighbor address
Physical bandwidth
Maximum reservable bandwidth
Unreserved bandwidth
(at eight priorities)
TE metric
Administrative group (attribute flags)
IS-IS or OSPF flood link information
TE Topology
database
TE nodes build a topology database

Not required if using off-line path
computation
BRKMPL-1101
Cisco Public
85
Path Calculation
For your
reference only
Calculation of Optimal Network Path, Based on Multiple Metrics

TE nodes can perform
constraint-based routing
Constraints and topology
database as input to path
computation
Shortest-path-first
algorithm ignores links not
meeting constraints
Tunnel can be signaled
once a path is found
Not required if using offline
path computation
Find shortest path

to R8 with 8Mbps
IP/MPLS
R1
15
10
10
R8
10
10
TE Topology
database
n
n
BRKMPL-1101
Link with insucient bandwidth

Link with sucient bandwidth
Cisco Public
86
TE Tunnel Signaling
For your
reference only
End-to-end Signaling of TE Tunnel in MPLS Network

Tunnel signaled with TE extensions
to RSVP
Soft state maintained with
downstream PATH messages
Soft state maintained with upstream
RESV messages
New RSVP objects
LABEL_REQUEST (PATH)
LABEL (RESV)
EXPLICIT_ROUTE
RECORD_ROUTE (PATH/RESV)
SESSION_ATTRIBUTE (PATH)
IP/MPLS
Head end
L=16
Tail end
RESV
PATH
Input
Label
Out Label,
Interface
17
16, 0
TE LSP
LFIB populated using RSVP labels

allocated by RESV messages
BRKMPL-1101
Cisco Public
87
For your
reference only
Implementing Sub-Second Failure Protection Using MPLS TE FRR

Deployment Use Case
Implementing sub-second
failure protection in MPLS
core network
P
CE
PE
P
Benefits
Sub-second failover
protection against link
failures in core network
Can be less than 50 ms
Predictable traffic flows

after core link failures
Network Segment
MPLS Node
Typical Platforms

MPLS

CPE
P
PE
CE
Edge
Core
CE
PE
ASR1K
ASR9K
CRS-1
ISR/G2
7600
GSR
ASR1K
ASR9K
ASR903
ME3800X
BRKMPL-1101
Cisco Public
88
MPLS Management
For your
reference only
Overview
Basic CLI (Craft interface):

CLI used for basic configuration and trouble shooting (show commands)
Traditional management tools:
SNMP MIBs to provide management information for SNMP (NMS)
management applications
MIB counters, Trap notifications, etc.
New management tools:
MPLS OAM; used for reactive trouble shooting
LSP Ping and LSP Trace for trouble shooting MPLS label switched paths
Automated MPLS OAM; used for proactive trouble shooting

Automated LSP ping/trace via Auto IP SLA
BRKMPL-1101
Cisco Public
89
Presentation_ID
Cisco Public

BRKMPL-1101 2012 San Diego

Uploaded by

Document Information

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

BRKMPL-1101 2012 San Diego

Uploaded by

Copyright:

Available Formats

Introduction to MPLS

2012 Cisco and/or its affiliates. All rights reserved.

Understand history and business drivers for MPLS

2012 Cisco and/or its affiliates. All rights reserved.

2012 Cisco and/or its affiliates. All rights reserved.

Its all about labels

MPLS forwarding plane

MPLS control/signaling plane

2012 Cisco and/or its affiliates. All rights reserved.

Destination address based

Destination address based

Ethernet Loop avoidance

MPLS shim header

8 bit TOS field in IP header

3-bit 802.1p field in VLAN tag

3 bit TC field in label

2012 Cisco and/or its affiliates. All rights reserved.

Evolved from tag switching in 1996 to full IETF

Complete base MPLS portfolio

1997 1998 1999 2000

2001 2002 2003 2004

2005 2006 2007 2008

2012 Cisco and/or its affiliates. All rights reserved.

2009 2010 2011 2012

S Networking service reliability

S Leverage single network for scalable

S Mergers and acquisitions

S Leverage single data center

2012 Cisco and/or its affiliates. All rights reserved.

Cisco Platform Coverage

2012 Cisco and/or its affiliates. All rights reserved.

MPLS Technology Basics

Basics of MPLS Signaling and Forwarding

MPLS Traffic Engineering

MPLS MIBs and OAM

MPLS signaling and

2012 Cisco and/or its affiliates. All rights reserved.

MPLS Reference Architecture

PE (Provider Edge) router

CE (Customer Edge) router

2012 Cisco and/or its affiliates. All rights reserved.

Label switched trac

MPLS Shim Labels

Label Definition and Encapsulation

Outer label always used for

TC = Trac Class: 3 Bits; S = Boom of Stack; TTL = Time to Live

MPLS Label Encapsulaon

LAN MAC Label Header

MPLS Label Stack

Boom of Stack Bit Set

2012 Cisco and/or its affiliates. All rights reserved.

QoS Marking in MPLS Labels

MPLS DiServ Marking

DSCP values of IP packet mapped

Most providers have defined 35

Different DSCP <-> TC mapping

2012 Cisco and/or its affiliates. All rights reserved.

Basic MPLS Forwarding Operations

How Labels Are Being Used to Establish End-to-end Connectivity

Label swapping or switching

Label disposition (POP)

Label Imposion (Push)

2012 Cisco and/or its affiliates. All rights reserved.

MPLS Path (LSP) Setup and Traffic Forwarding