MPLS - Oscar Nicasio - UTE day - 14 de julio de 2011

1. Diseños de red basados en MPLS
2011
Carlos Nicasio
carlos.nicasio@la.logicalis.com

2. Contents
- ¿Por qué MPLS?
- MPLS L3 VPNs
- Metro Ethernet: Diseños más comunes
- Metro Ethernet: Cisco EVC Framework
- Hardware
2 Diseños de Red Basados en MPLS

3. ¿Por qué MPLS?

4. Why MPLS?
• Needed a single infrastructure that supports multitude of applications in a
secure manner
• Provide a highly scalable mechanism
• Load balance traffic to utilize network bandwidth efficiently
• Allow core routers/networking devices to switch packets based on some
simplified header
• Leverage hardware so that simple forwarding paradigm can be used
Diseños de Red Basados en MPLS

5. Examine MPLS and Layer 3
Routing Limitations

6. L3 Routing Limitations
Traditional IP Forwarding
Diseños de Red Basados en MPLS

7. L3 Routing Limitations (Cont.)
Traffic Engineering Using Traditional IP Forwarding
Diseños de Red Basados en MPLS

8. MPLS Architecture
What Is MPLS?
Diseños de Red Basados en MPLS

9. Control Plane and Data Plane
MPLS Functionality
Diseños de Red Basados en MPLS

10. Frame-Mode
MPLS Modes of Operation
Diseños de Red Basados en MPLS

11. Label Headers
MPLS Label Format
Diseños de Red Basados en MPLS

12. Label Switched Router Types
Label Switched Routers
Diseños de Red Basados en MPLS

13. The Process of MPLS Forwarding
MPLS Forwarding
Diseños de Red Basados en MPLS

14. Identify Applications that Use
MPLS

15. Identify MPLS as an Application-driven
Technology
MPLS Applications
Diseños de Red Basados en MPLS

16. Identify MPLS as an Application-driven
Technology (Cont.)
Unicast IP Routing
Diseños de Red Basados en MPLS

17. Identify MPLS as an Application-driven
Technology (Cont.)
MPLS Traffic Engineering
Diseños de Red Basados en MPLS

18. Identify MPLS as an Application-driven
Technology (Cont.)
MPLS TE Example
• Some traffic from the upper (overutilized) path should
be moved to the lower path.
Diseños de Red Basados en MPLS

19. Identify MPLS as an Application-driven
Technology (Cont.)
Quality of Service
Diseños de Red Basados en MPLS

20. Identify MPLS as an Application-driven
Technology (Cont.)
Virtual Private Networks
Diseños de Red Basados en MPLS

21. Identify MPLS as an Application-driven
Technology (Cont.)
VPN Example
Diseños de Red Basados en MPLS

22. Identify MPLS as an Application-driven
Technology (Cont.)
Layer 2 MPLS VPN
Diseños de Red Basados en MPLS

23. Identify MPLS as an Application-driven
Technology (Cont.)
Layer 2 MPLS VPN Example
Diseños de Red Basados en MPLS

24. VPN Technologies
Overview

25. VPN Terminology
The Components of a Generic VPN
Diseños de Red Basados en MPLS

26. Overlay VPN
 Traditional VPN implementations were all based
on the overlay paradigm:
The service provider sells physical-layer connectivity, or
virtual circuits, or L2/L3 tunnels between customer sites
as a replacement for dedicated point-to-point links.
Diseños de Red Basados en MPLS

27. Overlay VPN (Cont.)
Example of Implementing an
Overlay VPN
Diseños de Red Basados en MPLS

28. Peer-to-Peer VPN
 The overlay VPN paradigm has a number of
drawbacks (need to establish point-to-point links
or VCs between customer sites).
 To overcome this drawback and provide optimum
data transport, the peer-to-peer concept was
introduced.
Diseños de Red Basados en MPLS

29. Peer-to-Peer VPN (Cont.)
 In a peer-to-peer VPN, the service provider
participates in the customer routing, accepting
customer routes, transporting them across the
service provider backbone, and finally propagating
them to other customer sites.
Diseños de Red Basados en MPLS

30. Peer-to-Peer VPN (Cont.)
The Move from Overlay to Peer-to-Peer
• Customers and service provider peer directly using the same OSI-layer
protocol - IP
Diseños de Red Basados en MPLS

31. The Major Categories of VPN
Benefits of the VPN Paradigms
Diseños de Red Basados en MPLS

32. The Major Categories of VPN (Cont.)
Drawbacks of the VPN Paradigms
Diseños de Red Basados en MPLS

33. MPLS Backbone
Benefits of deploy an MPLS
Backbone
• VPNs can utilize virtually any VPN technology (Layer 3
MPLS VPNs, Frame Relay, ATM, TDM, leased line) on the
edge of the backbone.
• All virtual VPN technologies use a single underlying MPLS
backbone to forward VPN packets, frames or cells.
Diseños de Red Basados en MPLS

34. MPLS Layer 2 and Layer 3 VPN
 MPLS-based VPNs can provide VPN functionality using OSI Layers 2 and 3:
Layer 3 MPLS VPN is a peer-to-peer model where
the MPLS VPN backbone and the VPN are
exchanging Layer 3 routing information, and Layer 3
packets are transmitted across an MPLS-enabled IP
backbone.
Layer 2 MPLS VPN is an Overlay model where
Layer 2 frames or cells are transmitted across and
MPLS-enabled IP backbone.
Diseños de Red Basados en MPLS

35. MPLS Layer 2 and Layer 3 VPN (Cont.)
Layer 3 MPLS VPN
 Layer 3 MPLS VPNs provide support for IPv4 protocol to be used inside a VPN:
The customer routers use a routing protocol (or static route) to exchange routing information with the provider
edge routers.
The MPLS VPN backbone uses MP-BGP to propagate VPN routing information across the backbone.
Diseños de Red Basados en MPLS

36. MPLS Layer 2 and Layer 3 VPN (Cont.)
Layer 2 MPLS VPN
 Layer 2 MPLS VPNs provide support for OSI Layer 2 Protocols to be used inside a VPN:
Point-to-point Layer 2 connections can be established over MPLS LSPs to provide support for Layer 2 protocols
such as Frame Relay, ATM, PPP.
Multipoint Layer 2 connections can be established to create virtual LANs across an MPLS backbone.
Diseños de Red Basados en MPLS

37. MPLS Layer 2 and Layer 3 VPN (Cont.)
 A single IP backbone can do the job of:
Internet service provisioning
Layer 3 MPLS VPN provisioning
Frame Relay trunk or PVC provisioning
ATM trunk or PVC provisioning
Leased line provisioning
TDM provisioning
Interworking between different Layer 2 technologies
(e.g. Frame Relay  ATM, Ethernet  Frame
Relay)
Diseños de Red Basados en MPLS

38. MPLS and Enterprise Networks
Diseños de Red Basados en MPLS

39. Metro Ethernet Designs

40. Centralized MPLS VPN Design
Diseños de Red Basados en MPLS

41. QinQ VLAN Encapsulation
Diseños de Red Basados en MPLS

42. Distributed MPLS VPN Design
Diseños de Red Basados en MPLS

43. Metro Ethernet
Arquitectura EVCs

44. Flexible QinQ Introduction
 Typical Metro Ethernet challenges
L2 and L3 services on the same port
Flexible service mapping
Flexible VLAN matching and manipulation
Local VLAN significance
VLAN scale
H-QoS per VLAN
…
EVC based Flexible QinQ will meet all the above requirements
Diseños de Red Basados en MPLS

45. ServiceFlex
No global VLAN resource needed for xconnect 
VLAN Scalability
VLAN 6
W
S
L
P
M
o
E
VLAN 7
o
t
a
n
i
m
r
e
T
F
R
V
/
3
L L3/VRF termination
VLAN 8
Split-horizon option provide “isolation”
between sub-interfaces
I
V
S
+
0
1
N
A
L
a
b
o
l
G
S
L
P
M
o
E
/
V Bridge-domain is global
Bridge-domain 100 [dot1q- F
R
V
/
3
L VLAN which has L2/L3
VLAN 6
service associated
tunnel] g
n
i
d
r
B
2
L
VLAN 7 [bpdu transparent | drop]
VLAN 9
Have option to add second vlan tag or replace the encap vlan tag
Have option to drop or transparently forward CE BPDU
L2 and L3 co-exist on the same port
Flexible L2/L3 service mapping
VLAN local port significance and VLAN Scalability
VLAN local port significance H-QoS support on main-interface/sub-interface
Diseños de Red Basados en MPLS

46. Flexible QinQ Overview
Service instance
One service instance (EFP) can
(Ethernet Flow Point)
match one or multiple or range Per service features
of VLANs at a time EVC
L3
VPLS
Flexible Flexible EoMPLS
VLAN VLAN H-QoS
Security
tag Tag per VLAN
matching rewrite
Local connect (P2P)
Local Bridging (MP)
Flexible VLAN tag manipulation,
pop/push/translate Flexible L2/L3 service mapping,
one or groups of EFPs can map
• VLAN local port significance to same EVC
• Two VLAN tag aware
• Flexible VLAN tag matching
(combination of up to two tag)
Diseños de Red Basados en MPLS

47. Parent VLAN
priority
Flexible QinQ - EVC Control Point CLI shape
average
bandwidth
shape
Child
average
interface <type><slot/port>
service instance <id> ethernet <evc-name> ID is per interface scope. evc-name
is global unique in the network. All service instances should have the same
evc-name if they are mapped to same EVC
<match criteria commands> VLAN tags, MAC, CoS, Ethertype
<rewrite commands>  VLAN tags pop/push/translation
<forwarding commands> L2 P2P or MP
<feature commands> QoS, ACL, etc
Interface
service instance X service instance Y sub-interface
Per Sub-interface
Per Port Per EVC Per Port Per EVC
Features (L3)
Features Features
Layer 2 Services
Bridging (VPLS via SVI)
xconnect (EoMPLS) L3 VRF
Local Connect
Diseños de Red Basados en MPLS

48. Flexible QinQ Configuration –
flexible frame matching
 Single tagged frame
encapsulation dot1q {any | “<vlan-id>[,<vlan-id>[-<vlain-id>]]”}
Vlan tag can be single, multiple or range or any (1-4096).
 Double tagged frame (only look up to 2 tags if receive more than 2 tagged frames)
encapsulation dot1q <vlan-id> second-dot1q {any | “<vlan-id>[,<vlan-id>[-<vlain-id>]]”}
First vlan tag must be unique, second vlan tag can be any, unique, range or multiple
 Default tag
encapsulation dot1q default
Match all frames tagged or untagged that are not matched by other more specific service
instances
 untagged
encapsulation untagged
Match no tagged frames
One service instance can match one, multiple or range of VLANs 
simplify configuration and operation, improve performance, more scale
Diseños de Red Basados en MPLS

49. Flexible QinQ Configuration –
flexible encapsulation rewrite
Router(config-if-srv)#[no] rewrite ingress tag … symmetric
 push {dot1q <vlan-id> | dot1q <vlan-id> second-dot1q <vlan-id>}  add 1 or 2 tag
 pop {1 | 2}  remove outer 1 or 2 tag
 translate  translate vlan tag
1-to-1 dot1q <vlan-id>
2-to-1 dot1q <vlan-id>
1-to-2 dot1q <vlan-id> second-dot1q <vlan-id>
2-to-2 dot1q <vlan-id> second-dot1q <vlan-id>
“symmetric” – any rewrite on ingress, do the reverse rewrite on egress. For example,
“rewrite ingress tag push dot1q 100 symmetric” =
“rewrite ingress tag push dot1q 100” +
“rewrite egress tag pop 1”
Note, we only support “rewrite ingress” with “symmetric” keyword. Not support “rewrite
egress” configuration. “symmetric” is MUST configuration, not optional
Diseños de Red Basados en MPLS

50. Flexible QinQ Configuration –
flexible service mapping/forwarding
Service instance
(Ethernet Flow Point)
connect test gig1/0/0 10 gig1/0/1
20 EVC
Local Connect, including hair pinning
xconnect …
EoMPLS
xconnect vfi …
VPLS
EoMPLS
BD
Local Bridging
bridge-domain 100 [split-horizon]
 put multiple EFPs into one global VLAN for L2 bridging
 split-horizon option to enable/disable bridging between
EFPs
interface vlan 100
xconnect … or ip address …
 L2/L3 service associated to bridge-domain (global VLAN)
Diseños de Red Basados en MPLS

51. EVC Infrastructure Overview
EFP – Ethernet Flow Point
EVC – Ethernet Virtual
Circuit
L3 subI/F
Multipoint EVC
Routing
EoMPLS PW
VPLS
Bridging EoMPLS PW
P2P EVC
VLAN
xlate EoMPLS PW
1:1, 2:2
1:2
X Bridging Multipoint EVC
P2P EVC
EFPs:
VLAN
(802.1q/802.1ad) EFPs: VLAN
(802.1q/QinQ)
Diseños de Red Basados en MPLS

52. Hardware

53. Cisco ASR9000 Aggregation Service Router
6 and 10 slot chassis
1+1 RSP, SSO, NSR
180 Gbps per slot, Tbps fabrics.
IOS XR Operating System, microkernel
EVC Framework (up to 32K EFPs per slot)
HQoS (up to 256K queues per slot)
High 10GE density (up to 24x10GE per
Diseños de Red Basados en MPLS

54. Cisco Metro 3600X Access Switches
Advanced Access
24xGE+2x10GE
Redundant Power Supplies (AC/DC)
65Mpps
EVC Framework (4000 EFPs)
MPLS, MPLS TE, EoMPLS, MPLS VPNs
HQoS on all ports
4K Egress Queues
Diseños de Red Basados en MPLS

55. Cisco Metro 3800X Switch Router
 Advanced Access
 24xGE+2x10GE
 Redundant Power Supplies (AC/DC)
 65Mpps
 EVC Framework (16000 EFPs)
 MPLS, MPLS TE, EoMPLS, VPLS, MPLS VPNs
 HQoS on all ports
 32K Egress Queues
Diseños de Red Basados en MPLS

56. Thank you
Carlos Nicasio
carlos.nicasio@la.logicalis.com