MPLS-overview.pdf

7/29/2019 MPLS-overview.pdf

1/80

1 2001, Cisco Systems, Inc. All rights reserved. 2001, Cisco Systems, Inc. All rights reserved. 2001, Cisco Systems, Inc. All rights reserved.

MPLSMPLS overviewoverviewWolfgang Riedel

[email protected]

Systems EngineerECSO Enterprise Manufacturing

Cisco Systems GmbH


2/80

2001, Cisco Sys tems, Inc. All ri ghts reserved. 212:24

Agenda MPLS Overview

1. Evolution of MPLS

2. Technology Basics

3. Label Distribution in MPLS Networks

4. MPLS-Based Services (Business Opportunities)

4.1 BGP MPLS VPNs

4.2 EoMPLS (Ethernet over MPLS)

4.3 VPLS (virtual private lan services)

4.4 ATOM (any t ransport over MPLS)

4.5 Traffic Engineering

4.7 Fast Reroute

4.7 Carrier Suppor ting Carrier

4.8 Multicast VPNs

4.9 QoS

5. Summary


3/80


Evolution of MPLS

From tag switching

Proposed in IETFLater combined with otherproposals from IBM (ARIS), Toshiba (CSR)

1996 1997 1998 1999 2000 2001

TimeTime

Cisco Calls aBOF at IETF to

StandardizeTag Switching

Cisco Calls aBOF at IETF to

StandardizeTag Switching

Traffic EngineeringDeployed

Traffic EngineeringDeployed

MPLS VPNDeployed

MPLS VPNDeployed

Large ScaleDeploymentLarge ScaleDeployment

Cisco ShipsMPLS (TagSwitching)

Cisco ShipsMPLS (TagSwitching)

Cisco ShipsMPLS TE

Cisco ShipsMPLS TE

MPLS CroupFormally Chartered

by IETF

MPLS CroupFormally Chartered

by IETF


4/80


The Challenges

Campus Service Provider

multiple customers

Move into rapid deployment

Replacement of campuswide vlans

Cost saving

Lower cost of managingseparate Data and Voicenetworks

Combine private dataservices with Internetservices

Migration pathProtect existing

InfrastructureATM/FR

Lower cost of WANconnectivity

Generate new services

EnterpriseService Providers


5/80


MPLS

advanced services

L2 protocols (PPP, POS, ATM, FR,L2 protocols (PPP, POS, ATM, FR, EnetEnet, GRE, ...), GRE, ...)

LabelLabel Forwarding Information Base (LFIB)Forwarding Information Base (LFIB)LDPLDP

RSVPRSVP

PerPer--Label Forwarding, Queuing, Mult icast, RestorationLabel Forwarding, Queuing, Mult icast, Restoration

MechanismsMechanismsCEFCEF

IPIP

switchingswitching

IPIP

CoSCoS

((DiffServDiffServ))

DiffServDiffServ

awareaware

TETE

MulticastMulticast

RoutingRouting

(PIM v2(PIM v2)

OSPFOSPF

ISIS--ISIS

PIMPIM

FastFast

ReroutingReroutingTrafficTraffic

EngineeringEngineering

Virtual Private NetworksBGP

LDP

BGPBGP

LDPLDPATOM

Any Transport over MPLS

IPv6

6PE

Carriersupporting

Carrier

Multicastover

VPN

L2VPN


6/80


MPLS

Innovation & Standards



RSVPRSVP



IPIP

switchingswitching

IPIP

CoSCoS


DiffServDiffServ

awareaware

TETE

MulticastMulticast

RoutingRouting

(PIM v2(PIM v2)

OSPFOSPF

ISIS--ISIS

PIMPIM

FastFast




LDP

BGPBGP

LDPLDPATOM


IPv6

6PE

Carriersupporting

Carrier

Multicastover

VPN

L2VPN

2474 Definition of the Differentiated Services

Field in IP Headers *

2475 An Architecture for Differentiated

Services

2597 Assured Forwarding PHB Group *

2598 An Expedited Forwarding PHB *2697 A Single Rate Three Color Marker

2698 A Two Rate Three Color Marker

3031 Multiprotocol Label SwitchingArchitecture *

3032 MPLS Label Stack Encoding *

3034 Label Switching on Frame

Relay Networks

3035 MPLS using LDP and ATM VC

Switching *

3036 LDP Specification *

3037 LDP Applicability *

2702 Requirements for

Traffic Engineering Over MPLS

2547 BGP/MPLS VPNs *


7/80


MPLS

Innovation-in-Progress



RSVPRSVP



IPIP

switchingswitching

IPIP

CoSCoS


DiffServDiffServ

awareaware

TETE

MulticastMulticast

RoutingRouting

(PIM v2(PIM v2)

OSPFOSPF

ISIS--ISIS

PIMPIM

FastFast




LDP

BGPBGP

LDPLDPATOM


IPv6

6PE

Carriersupporting

Carrier

Multicastover

VPN

L2VPN

[Martini Drafts]

Transport of Layer 2 Frames

Over MPLS *draft-martini-l2circuit-trans-

mpls-06.txt

Encapsulation Methods for

Transport of Layer 2 Frames

Over MPLS *draft-martini-l2circuit-encap-

mpls-02.txt

MPLS Support of

Differentiated Services *

draft-ietf-mpls-diff-ext-09.txt

[Draft Rosen]

An Archi tecture for L2VPNs *draft-rosen-ppvpn-l2vpn-00.txt


8/80







4.1 BGP MPLS VPNs





4.7 Fast Reroute


4.8 Multicast VPNs

4.9 QoS

5. Summary


9/80


MPLS Concept

In Core:Forward using labels(as opposed to IP addr)

Label indicates serviceclass and destination

Label SwitchRouter (LSR)

Label Distribution

Protocol (LDP)

Edge LabelSwitch Router

At Edge:Classify packets

Label them


10/80


MPLS Operation1a. Existing routing protocols (e.g. OSPF, IS-IS)

establish reachability to destination networks

1b. Label Distribution Protocol (LDP)

establishes label to destinationnetwork mappings

2. Ingress Edge LSR receives packet,

performs Layer 3 value-added

services, and labels packets

3. LSR switches packets using

label swapping

4. Edge LSR at egress

removes label and

delivers packet


11/80


Encapsulations

Label HeaderLabel HeaderPPP HeaderPPP Header Layer 3 HeaderLayer 3 HeaderPPP Header

(Packet over SONET/SDH)

ATM Cell Header HECHEC

LabelLabel

DATADATACLPCLPPTIPTIVCIVCIGFCGFC VPIVPI

Label HeaderLabel HeaderMAC HeaderMAC Header Layer 3 HeaderLayer 3 HeaderLAN MAC Label Header


12/80


Label Header for Packet Media

Can be used over Ethernet, 802.3, or PPPlinks

Uses two new Ethertypes/PPP PIDs

Contains everything needed at forwardingtime

Label = 20 bits COS/EXP = Class of Service, 3 bits

S = Bottom of Stack, 1 bit TTL = Time to Live, 8 bits

0 1 2 30 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 10 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

Tag COS S TTL


13/80







4.1 BGP MPLS VPNs

4.2 EoMPLS (Ethernet over MPLS)4.3 VPLS (virtual private lan services)



4.7 Fast Reroute


4.8 Multicast VPNs

4.9 QoS

5. Summary


14/80


Label Distribution Protocol

Defined in RFC 3036 and 3037

Used to distribute labels in a MPLS network

Forwarding equivalence class

How packets are mapped to LSPs (LabelSwitched Paths)

Advertise labels per FEC

Reach destination a.b.c.d with label x Neighbor discovery

Basic and extended discovery


15/80


TDP and LDP

Tag Distribution ProtocolPre-cursor to LDP

Used for Cisco tag switching

TDP and LDP supported on the same box

Per neighbor/link basis

Per target basis


16/80


RSVP and Label Distribution

Used in MPLS traffic engineering

Additions to RSVP signaling protocol

Leverage the admission control mechanismof RSVP

Label requests are sent in PATH messages andbinding is done with RESV messages

EXPLICT-ROUTE object defines the path over which

setup messages should be routed

Using RSVP has several advantages


17/80


BGP-Based Label Distribution

Used in the context of MPLS VPNs

Need multi-protocol extensions to BGP

Routers need to be BGP peersWorks in both RR and non-RR environment

Label mapping info carried as part of NLRI(Network Layer Reachability Information)


18/80

2001, Cisco Sys tems, Inc. All ri ghts reserved. 18

MPLS Example:

Routing Information

128.89

171.691

010

You can reach 171.69

through me

You can reach 128.89 and

171.69 through me

Routing Updates

(OSPF, EIGRP, )

You can reach 128.89

through me

In

Lbl

In

LblAddress

Prefix

Address

Prefix

128.89128.89171.69171.69

......

Out

Iface

Out

Iface

0011

......

Out

Lbl

Out

LblIn

Lbl

In

LblAddress

Prefix

Address

Prefix

128.89128.89171.69171.69

......

Out

Iface

Out

Iface

1111

......

Out

Lbl

Out

LblIn

Lbl

In

LblAddress

Prefix

Address

Prefix

128.89128.89

......

Out

Iface

Out

Iface

00

......

Out

Lbl

Out

Lbl


19/80


MPLS Example:

Assigning Labels

1

010

Use Lbl 7 for 171.69

Use Lbl 4 for 128.89 and


Label Distribution

Protocol (LDP)(Downstream Allocation)


128.89

171.69

In

Lbl

In

LblAddress

Prefix

Address

Prefix

128.89128.89171.69171.69

......

Out

Iface

Out

Iface

0011

......

Out

Lbl

Out

LblIn

Lbl

In

LblAddress

Prefix

Address

Prefix

128.89128.89171.69171.69

......

Out

Iface

Out

Iface

1111

......

Out

Lbl

Out

LblIn

Lbl

In

LblAddress

Prefix

Address

Prefix

128.89128.89

......

Out

Iface

Out

Iface

00

......

Out

Lbl

Out

Lbl

----

4455

4455

9977

99 --


20/80


MPLS Example:

Forwarding Packets

128.89

171.69

1

01

128.89.25.4 Data44128.89.25.4128.89.25.4 Data

128.89.25.4 Data

128.89.25.4Data99

0

Label Switch Forwards

Based on Label

In

Lbl

In

LblAddress

Prefix

Address

Prefix

128.89128.89171.69171.69

......

Out

Iface

Out

Iface

0011

......

Out

Lbl

Out

LblIn

Lbl

In

LblAddress

Prefix

Address

Prefix

171.69171.69

......

Out

Iface

Out

Iface

1111

......

Out

TLbl

Out

TLblIn

Lbl

In

LblAddress

Prefix

Address

Prefix

128.89128.89

......

Out

Iface

Out

Iface

00

......

----

4455 55

9977

--44 99128.89128.89

Out

Lbl

Out

Lbl


21/80


Label Stacking

Arrange labels in a stack

Inner labels can be used to designate services/FECs, etc.E.g. VPNs, fast re-route

Outer label used to route/switch the MPLS packets inthe network

Allows building services such as

MPLS VPNs

Traffic engineering and fast re-route

VPNs over traffic engineered core

Any transport over MPLS

Inner Label

Outer Label

IP Header

TE LabelTE Label

IGP LabelIGP Label

VPN LabelVPN Label


22/80







4.1 BGP MPLS VPNs




4.7 Fast Reroute

4.7 Carrier Suppor ting Carrier4.8 Multicast VPNs

4.9 QoS

5. Summary


23/80


MPLS Features ...

Thats all nice but ...

How can you make moneywith it?


24/80


Metro Solutions Architectural flexibility, service transparency

L3 VPN

L2 VPN

TDM PL

GigE PL

Wavelength

Storage

ResidentialData/Voice/Video

Enterprise VoIP

Internet Access

L2 VPN L3 VPNInternet Access


25/80


In what roomdo you want

me to put i t?

with enough fiber you could do anything?


26/80


MPLS IP-VPNThe L3 generation of core backbone

MPLSMPLS

IPIP--VPNVPN

PSTNISDNBranch

Home

Travel

ADSL/Cable

BranchHome

INTERNET

Services

Regional Site

LL

Frame-Relay

ATM

Remote Sites

INTERNET

Branch

Home

Travel

IPSec Central

Site

TDM

MUX


27/80







4.1 BGP MPLS VPNs




4.7 Fast Reroute


4.9 QoS

5. Summary


28/80


MPLS L2-VPNThe L3 generation of core backbone

Frame-Relay

ATM

Remote Sites

Frame-RelayATM

Remote Sites

Frame-Relay

ATM

MPLSMPLS

IPIP--VPNVPNL2 VPNL2 VPN

Regional Site

Ethernet

Central

Site

Ethernet

Ethernet

RegionalSite

Central

Site

Ethernet

Regional Sites


29/80


What Is a VPN?

VPN is a set of sites which are allowed to

communicate with each other

VPN is defined by a set of administrative policies

Policies determine both connectivity and QoS

among sites

Policies established by VPN customers

Policies could be implemented completely by VPN

service providers

Using BGP/MPLS VPN mechanisms


30/80


MPLS-based IP-VPN Architecture

Scalable VPNs

IP QoS and trafficengineering

Easy to manage and NoVC provisioning required

Provides a level ofSecurity equivalent toFrame-relay and ATM

Supports the deploymentof new value-added

applications Customer IP address

freedom

MPLSNetwork

Traffic Separation at Layer 3Each VPN Has Unique RD

Traffic Separation at Layer 3Each VPN Has Unique RD

MPLS VPN RenaultMPLS VPN Renault

MPLS VPN BankcorpMPLS VPN Bankcorp

VPN ASite 2

VPN ASite 3

Corp ASite 1

Corp BSite 2

Corp BSite 1Corp BSite 3

VPN Membership-

Based on Logical Port

VPN Membership-

Based on Logical Port


31/80


Using Labels to Build an IP VPN

The network distributes labels to each VPN

Only labels for other VPN members are distr ibuted

Each VPN is provisioned automatically by IP routing

Privacy and QoS of ATM without tunnels or encryption

Each network is as secure as a Frame Relay connection

One mechanism (labels) for QoS and VPNsno tradeoffs

Cust ACust A

Cust ACust A

Cust ACust A

Cust BCust B

Cust BCust B

MPLS

Network

B----

---

----

B----

---

----

A----

---

----

A----

---

----


32/80


VPN A

VPN B

VPN CVPN A VPN B

VPN C

VPN A

VPN B

VPN CVPN A

VPN C

VPN B

Hosting

Multicast

VoIP

Intranet

Extranet

Service Provider Benefitsof MPLS-Based VPNs

Overlay VPNPushes content outside the network

Costs scale exponentially

Transport dependent

Groups endpoints, not groups

Complex overlay with QoS, tunnels, IP

MPLS-based VPNsEnables content hosting inside the

network Flat cost curve

Transport independent

Easy grouping of users and services

Enables QoS inside the VPNs


33/80


MPLS Based IP-VPN Security

Cisco MPLS based VPNs:

Equivalent to the Securityof Frame Relay and ATM

Security

http://www.mier.com/reports/cisco/MPLS-VPNs.pdf

Miercom, March 30, 2001


34/80


Validating Cisco MPLS Based IP-VPN

as a Secure Network

Security

Miercom independent testingconfirmed Cisco MPLS VPN is

secure:9 Customers network topology is not

revealed to the outside world

9 Customers can maintain own

addressing plans and the freedomto use either public or privateaddress space

9Attackers cannot gain access into

VPNs or Service Providers network

9 Impossible for attacker to insert spoofed label into a Cisco MPLSnetwork and thus gain access to a

VPN or the MPLS core

RED-Glascow

2611100.200.200.104

3.4.4.4

10.4.4.4

SER 5/0:0

100.200.104.1

POS 1/0100.200.106.2

T1 FRdlci 102

eBGP AS72T1 FR

dlci 104RIP v2

Ser 3/0

100.200.102.1SiSi

SiSi

SER 1/0:0

100.200.104.2

ATM2/0/0100.200.111.1

SER 1/0/1:0100.200.110.1

POS 2/1/0

100.200.112.2

3.5.5.5

RED-Dover

1750

100.200.200.10910.3.3.3

T1 FRdlci 109RIP v2

T1 FR

dlci 110Static

10.3.3.3

DOVER

7505

100.200.200.112

ATM1/0100.200.111.2

Ser 0

100.200.109.2

BLUE-Dover

2611100.200.200.110

YELLOW-Dover

3640

100.200.200.111

Ser 1/0100.200.110.2

Ser 5/0:0100.200.101.1

BLUE-Oxford

1750

100.200.200.101

Ser 0

100.200.101.2

T1 FR

dlci 101OSPF

10.4.4.4

pvc 0/11

eBGP AS71

BLUE-Glascow

3640100.200.200.105

SER 1/0/0:0100.200.109.1

ATM1/0100.200.105.2

10.5.5.5

ATM 1/0100.200.105.1

pvc 1/1OS PF

OC3 POS

GLASCOW7206

100.200.200.106

OXFORD7206

100.200.200.103

LONDON

GSR12008

100.200.200.107

POS 1/0100.200.103.1

POS 1/1100.200.106.1

POS 1/0

100.200.112.1

POS 2/0100.200.110.1

OC3 POSOC3 POS

YELLOW-Oxford

3640

100.200.200.102

Ser 0/0100.200.102.2

SiSi

POS 2/0

100.200.103.2

Test Network Topology


35/80


Key Features (Cont.)

Connectivity to the Internet:

VPN service providers may also provide connectivityto the Internet to its VPN customers

Common infrastructure is used for both VPN and theInternet connectivity services

Simplifies operations and management for VPNservice providers:

No need for VPN service providers to set up andmanage a separate backbone or virtual backbonefor each VPN


36/80


BGP/MPLS VPNSummary

Supports large scale VPN service

Increases value add by the VPN serviceprovider

Decreases service provider cost ofproviding VPN services

Mechanisms are general enough to enable

VPN service provider to support a widerange of VPN customers


37/80




2. Technology Basics3. Label Distribution in MPLS Networks


4.1 BGP MPLS VPNs




4.7 Fast Reroute


4.9 QoS

5. Summary


38/80


Ethernet Virtual Circuit EoMPLS

Enterprise

Campus

A Ethernet Mapped Circuit

Access (L2)Ethernet

Access (L2)Ethernet

Access (L2)Ethernet

Access (L2)Ethernet

CoreMPLSCoreMPLS

Ethernet Circuit

EoMPLS Tunnel in Core EnterpriseCampus

B

MPLS

10/100/Gigabit

Ethernet

10/100/Gigabit

Ethernet

To the Enterprise this network is

a pair of Pt to Pt 10/100/Gbit Bridged Ethernet Links

A B

MPLS PECisco 7600

MPLS PECisco 7600


39/80






4.1 BGP MPLS VPNs




4.7 Fast Reroute


4.9 QoS

5. Summary


40/80


VPLS ( Transparent LAN Services)

Point to Multipoint Service

Multipoint to Multipoint Service

The network will simulate a L2 switch


41/80






4.1 BGP MPLS VPNs




4.7 Fast Reroute


4.9 QoS

5. Summary


42/80


L2 Transport: AToM| |

| || |Et her netEt her net

ATM/ PPP/ HDLCATM/ PPP/ HDLC

| |Et hernetEt hernet

ATM/ PPP/ HDLCATM/ PPP/ HDLC

ESES Emulated Services:Emulated Services: FR/Ether/ATM/PPP/HDLCFR/Ether/ATM/PPP/HDLC

Attachment VCAttachment VC (AVC)(AVC):: FR DLCI/Ethernet VLAN/ATM PVC/PPP/HDLCFR DLCI/Ethernet VLAN/ATM PVC/PPP/HDLC

PWPW PseudoPseudo--Wire: Emulated VCWire: Emulated VC (EVC)(EVC):: MPLS LSPMPLS LSP

PSNPSN Packet Switched NetworkPacket Switched Network (Tunnel)(Tunnel):: MPLS LSP or RSVPMPLS LSP or RSVP--TETE

IPNetwork

MPLS

Core

At tachment VC /At tachment VC /

L2 circuitL2 circuit





Site1A

Site 2A


L2 circuitL2 circuitPE1 Site1B

Site 2B

PE2

AToM Reference ModelAToM Reference Model

CE 1A

CE 2A

CE 1B

CE 2B

PSN Tunnel : MPLS TunnelPSN Tunnel : MPLS Tunnel

MPLS ( LSP or RSVPMPLS ( LSP or RSVP--TE)TE)



43/80


Any Transport over MPLSAToM

Service Provider

FR Cust

IPoFR cust

LSREdge-LSR

DLCI

202

DLCI

101

Example: Frame Relay over MPLS

Transports over MPLS


44/80


Transports over MPLSAToM

Ethernet

802.1Q (Ethernet VLAN)

Frame Relay PDU

ATM AAL5 PDU

ATM cells (non AAL5 mode)

Cisco HDLC

PPP

draft-martini-l2circuit-trans-mpls-05.txt

draft-martini-l2circuit-encap-mpls-01.txt


45/80






4.1 BGP MPLS VPNs





4.7 Fast Reroute


4.9 QoS

5. Summary


46/80


Why Traffic Engineering?

Congestion in the network due to changing traffic patterns

Election news, online trading, major sports events

Better utilization of available bandwidth

Route on the non-shortest path

Route around failed l inks/nodes

Fast rerouting around failures, transparently to users

Like SONET APS (Automatic Protection Switching)

Build new servicesVirtual leased line services

VoIP toll-bypass applications, point-to-point bandwidth guarantees

Capacity planning

TE improves aggregate availabil ity of the network


47/80


R8R2

R6

R3

R4

R7

R5

R1

IP (Mostly) Uses Destination-Based Least-Cost Routing

Flows f rom R8 and R1 Merge at R2 and Become Indistinguishable

From R2, Traffic to R3, R4, R5 Use Upper Route

Al ternate Path Under-Utilized

IP Routing and the Fish

Solution: Toll Bypass with Voice/Data


48/80


Solution: Toll Bypass with Voice/Data

Converged Network

PE

CE

PSTN Traditional TDMNetwork

EnterpriseLAN

EnterpriseLAN

Toll Bypass

QoS on PE

Router

Solution

Requirements

Mapping

Traffic to

Tunnels

DiffServ-Aware

Traffic Engineering

QoS on

Core

Routers

CE

QoS on CE

Router

PEGB Tunnel

PBX withCircuitEmulationInterface

+ + +=

Class 5

legacyswitches

Fast Reroutein the core


49/80


DiffServ Aware TE Virtual Leased Line

PE

CentralOffice

TraditionalTelephony

Toll Bypass

PE

VoIPGateway

VoIPGateway

MPLSNetwork

PE PERegular TE

TunnelCE

EnterpriseLAN

PE PE

Voice TrunkingVoice Trunking

VPN ServiceVPN Service

Internet ServiceInternet Service EnterpriseLAN

InternetAccess Router

InternetAccess Router

EnterpriseLAN

Class 5LegacyswitchesPSTN

Traditional TDMNetwork Central

OfficeTraditionalTelephony

GB

Tunnel

CEEnterprise

LAN

GB-TE TunnelRegular TE Tunnel

Physical Link


50/80






4.1 BGP MPLS VPNs





4.7 Fast Reroute


4.8 Multicast VPNs

4.9 QoS

5. Summary


51/80


What Is Fast Reroute?

Definition

Fast ReRoute (FRR) is a link or node

protection feature, allowing fortemporary bypassing of the failed link or

node over a preestablished tunnel, while

the head-end is rerouting the failed LSP


52/80


What is Fast Re-route? (cont.)

Head-end Router

Link Resilience (Next-hop Backup


53/80


Tunnel)

Node Resilience (Next-next Hop


54/80


Backup Tunnel)


55/80






4.1 BGP MPLS VPNs





4.7 Fast Reroute


4.8 Multicast VPNs

4.9 QoS

5. Summary

Carrier Supporting Carrier& I t P id A


56/80


& Inter-Provider Access

Carrier Supporting Carrier

Hierarchical relationship

Opportunity: Offer

backbone services to peer

or smaller carriers

Inter-Provider Access

Peer relationship

Opportunity: Provide

carrier services on behalf

of other carriers

Backbone

Carrier

Customer

Carriers

Carrier A

Carrier B

Inter-AS VPN Using VRF-to-VRFD i (C t )


57/80


Design (Cont.)

ASBRs collect the client VPN routes through configured VRFs.

Adjacent ASBR is seen as a CE through separate logical interface.

Dedicated IPv4 routing session per VRF usually eBGP.

VRF-to-VRF Connections Between AS Border Routers



58/80


Design (Cont.)

VPN routing information distributed across inter-AS network

VPN Routing Distribution Between MPLS VPN Backbones



59/80


Design (Cont.)

Data flow: Label switching within AS and IP forwarding on Inter-AS link

Data Flow Label Switching and IP Forwarding

MPLS VPN Enabled ISP ConnectedAcross Standard Carrier (Cont )


60/80


Across Standard Carrier (Cont.)

Customer Carrier is Not Running MPLS (Cont.)

MPLS VPN Enabled ISP ConnectedAcross Standard Carrier (Cont )


61/80


Across Standard Carrier (Cont.)

Customer Carrier is Running MPLS (Cont.)

IBGP



62/80






4.1 BGP MPLS VPNs





4.7 Fast Reroute


4.8 Multicast VPNs

4.9 QoS

5. Summary

Multicast VPN (MVPN)


63/80


Receiver 4Receiver 4

B1

D

FF

CECE

A

CECE

CECE

High bandwidth

multicast source



C

CECE

CECE

MPLS VPNMPLS VPN

CoreCore

CECE


EE

PEPE

BPEPE

PEPE

EE

PEPEA

PEPED

C

Multicast VPN (MVPN)

Join high

bandwidth source

Join high

bandwidth source

A Default MDT is createdconnecting all the PEswithin a VPN for signalingand low bandwidth flows

Customer CE devices joinsthe MPLS Core throughproviders PE devices

Data-MDT is formed forthis High-Bandwidthsource

A High-bandwidth source

for that customer startssending traffic

Interested receivers 1 & 2join that High Bandwidthsource

CECE

DataDataMDTMDT

For HighBandwidthtraffic only.

DefaultDefaultMDTMDT

For lowBandwidth &

controltraffic only.

B2

San

Francisco

San

Francisco

Los

Angeles

Los

Angeles

DallasDallas

New YorkNew York



64/80






4.1 BGP MPLS VPNs





4.7 Fast Reroute


4.8 Multicast VPNs

4.9 QoS

5. Summary

Backbone and Edge QoS Design


65/80


Backbone and Edge QoS Design

Availability Loss rate

Latency

Jitter

Throughput

Loss rate

Latency

Jitter

Subsecond Interior Gateway

Protocol (IGP) convergence

Sub-100 ms Fast Reroute (FRR)

High availabili ty

Scope

Backbone and Edge QoS Design(Cont )


66/80


(Cont.)

An MPLS packet carries two (or more)DiffServ markings.

Three modes of interaction are defined

between markings: Uniform, Pipe, and ShortPipe.

Modes are only relevant when a label is

popped/pushed.

QoS Transparency

Backbone and Edge QoS Design (Cont.)


67/80


Backbone and Edge QoS Design (Cont.)

QoS Transparency: Uniform Mode



68/80


(Cont.)

QoS Transparency: Pipe Mode



69/80


(Cont.)

QoS Transparency: Short Pipe Mode



70/80






4.1 BGP MPLS VPNs





4.7 Fast Reroute


4.8 Multicast VPNs

4.9 QoS

5. Summary

MPLS: The Key Technology for IPService Delivery


71/80


Se ce e e y

Network-based VPNs with MPLS:a foundation for value-added service delivery

Flexible user and service grouping (biz-to-biz)

Flexibil ity of IP and the QoS and privacy of ATM

Enables application and content hosting inside each VPN

Transport independent

Low provisioning costs enable affordable managed services

IPServices

IPServices

ATMServices

ATMServices

IP+ATM SwitchIP+ATM Switch

PNNIPNNI MPLSMPLS

IPIP IP+ATM: MPLS brings IP and ATM togetherEliminates IP over ATM overhead and complexity

One network for Internet, Business IP VPNs, and transport



72/80


y

Guaranteed bandwidth services

Combine MPLS traffic engineering and QoS

Deliver point-to-point bandwidth guaranteed pipes

Leverage the capability of traffic engineering

Build solut ion like virtual leased line and toll trunking

MPLS traffic engineering

Provides routing on diverse paths to avoid congestion

Better uti lization of the network

Better availability using protection solution (FRR)



73/80


y

IP+Optical: MPLS brings IP and Optical together

Eliminates IP over optical complexityUses MPLS as a control plane for setting up l ightpaths(wavelengths)

One control plane for Internet (GMPLS), business IP VPNs,and Optical transport

Any transport over MPLS

Transport ATM, FR, Ethernet, PPP over MPLS

Provide services to exist ing installed base

Protect Investment in the installed gear

Leverage capabili ties of the packet core

Combine with other packet-based services such asMPLS VPNs

FrameRelay

ATM

FrameRelay

IPServices

IPServices

OpticalServicesOptical

Services

IP+Optical SwitchIP+Optical Switch

O-UNIO-UNI MPLSMPLS

IPIP

Literature


74/80


MPLS and VPN ArchitecturesIvan Pepelnjak

Jim Guichard

ISBN 1-58705-002-1


75/80


MPLS Features ...


76/80


Thats all nice but ...

How does this help me formy datacenter ?

Customer StrategiesMapping Customer Problems to Cisco Solutions


77/80


Inter-Data CenterConnectivity

Distributed Data Centers

Data Center

Solution Set

Data Center

DataSecurity

HighlyAvailabilityInfrastructure

StorageNetwork

Application/Server

Optimization

Strategies Server, Application and DCServer, Application and DC

consolidationconsolidation

Migration to Web AppsMigration to Web Apps Comprehensive SecurityComprehensive Security

Services ModelServices Model

Storage ConsolidationStorage Consolidation

Business Continuance &Business Continuance &

Disaster RecoveryDisaster Recovery

Data CenterCenter

Networking

Data Center Networking


78/80


Data CenterInfrastructure

Server &

Application

Optimization

Storage

NetworkingData Center

Security

DistributedData Centers

Campus Core

Internet

ISP A

Primary Data

Center

Distributed Data

CenterInternet

SP B

Intranet

SP AIP Network

External

protection

Server farm

protection

Internal

protection

IP NetworkPrimary

Data CenterDistributed

Data Center

ISP B


79/80



80/80


Documents

MPLS-overview.pdf