wolfgang riedel mpls overview [email protected]/mpls-overview.pdf · agenda...

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

MPLS MPLS overviewoverviewWolfgang Riedel

[email protected] Engineer

ECSO Enterprise ManufacturingCisco Systems GmbH

© 2001, Cisco Systems, Inc. All rights reserved. 212:24

Agenda MPLS Overview

1. Evolution of MPLS2. Technology Basics3. Label Distribution in MPLS Networks4. MPLS-Based Services (Business Opportunities)

4.1 BGP MPLS VPNs4.2 EoMPLS (Ethernet over MPLS)4.3 VPLS (virtual private lan services)4.4 ATOM (any transport over MPLS)4.5 Traffic Engineering4.7 Fast Reroute4.7 Carrier Supporting Carrier4.8 Multicast VPN´s4.9 QoS

5. Summary


Evolution of MPLS

• From tag switching• Proposed in IETF—Later combined with other

proposals from IBM (ARIS), Toshiba (CSR)

1996 1997 1998 1999 2000 2001TimeTime

Cisco Calls aBOF at IETF to

StandardizeTag Switching

Cisco Calls aBOF at IETF to

StandardizeTag Switching

Traffic Engineering Deployed

Traffic Engineering Deployed

MPLS VPNDeployed

MPLS VPNDeployed

Large Scale DeploymentLarge Scale Deployment

Cisco Ships MPLS (Tag Switching)

Cisco Ships MPLS (Tag Switching)

Cisco ShipsMPLS TE

Cisco ShipsMPLS TE

MPLS Croup Formally Chartered

by IETF

MPLS Croup Formally Chartered

by IETF


The Challenges

Campus Service Provider

“multiple customers”

Move into rapid deployment

Replacement of campus wide vlan´s

Cost saving

Lower cost of managing separate Data and Voice networks

Combine private data services with Internet services

Migration pathProtect existing Infrastructure—ATM/FR

Lower cost of WAN connectivity

Generate new services

EnterpriseService Providers


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) LDPLDPRSVPRSVP

PerPer--Label Forwarding, Queuing, Multicast, RestorationLabel Forwarding, Queuing, Multicast, RestorationMechanismsMechanisms CEFCEF

IPIPswitchingswitching

IPIPCoSCoS

((DiffServDiffServ))

DiffServDiffServawareaware

TETE

Multicast Multicast Routing Routing (PIM v2(PIM v2)

OSPFOSPFISIS--ISISPIMPIM

FastFastReroutingRerouting

TrafficTrafficEngineeringEngineering

Virtual Private NetworksBGPLDPBGPBGPLDPLDP

ATOMAny Transport over MPLS

IPv66PE

Carriersupporting

Carrier

MulticastoverVPN

L2VPN


MPLS Innovation & Standards





IPIPCoSCoS



TETE







IPv66PE

Carriersupporting

Carrier

MulticastoverVPN

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 Marker2698 A Two Rate Three Color Marker

3031 Multiprotocol Label Switching Architecture *

3032 MPLS Label Stack Encoding *3034 Label Switching on Frame

Relay Networks3035 MPLS using LDP and ATM VC

Switching *3036 LDP Specification *3037 LDP Applicability *

2702 Requirements for Traffic Engineering Over MPLS

2547 BGP/MPLS VPNs *


MPLS Innovation-in-Progress





IPIPCoSCoS



TETE







IPv66PE

Carriersupporting

Carrier

MulticastoverVPN

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 Architecture for L2VPNs *

draft-rosen-ppvpn-l2vpn-00.txt





5. Summary


MPLS Concept

In Core:Forward using labels (as opposed to IP addr)Label indicates service class and destination

Label Switch Router (LSR)

Label Distribution Protocol (LDP)

Edge Label Switch Router

At Edge:Classify packetsLabel them


MPLS Operation1a. Existing routing protocols (e.g. OSPF, IS-IS) establish reachability to destination networks

1b. Label Distribution Protocol (LDP) establishes label to destination network 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


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


Label Header for Packet Media

• Can be used over Ethernet, 802.3, or PPP links

• Uses two new Ethertypes/PPP PIDs• Contains everything needed at forwarding

time

Label = 20 bits COS/EXP = Class of Service, 3 bitsS = Bottom of Stack, 1 bit TTL = Time to Live, 8 bits

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





5. Summary


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 (Label Switched Paths)

• Advertise labels per FECReach destination a.b.c.d with label x

• Neighbor discoveryBasic and extended discovery


TDP and LDP

• Tag Distribution ProtocolPre-cursor to LDP

Used for Cisco tag switching

• TDP and LDP supported on the same boxPer neighbor/link basis

Per target basis


RSVP and Label Distribution

• Used in MPLS traffic engineering

• Additions to RSVP signaling protocol

• Leverage the admission control mechanism of RSVP

• Label requests are sent in PATH messages and binding is done with RESV messages

• EXPLICT-ROUTE object defines the path over which setup messages should be routed

• Using RSVP has several advantages


BGP-Based Label Distribution

• Used in the context of MPLS VPNs• Need multi-protocol extensions to BGP• Routers need to be BGP peers

Works in both RR and non-RR environment

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

© 2001, Cisco Systems, Inc. All rights reserved. 18

MPLS Example:Routing Information

128.89

171.69

1

010

You can reach 171.69through me

You can reach 128.89 and 171.69 through me

Routing Updates (OSPF, EIGRP, …)

You can reach 128.89 through me

In LblIn Lbl

Address Prefix

Address Prefix

128.89128.89171.69171.69

......

OutI’faceOut

I’face

0011......

Out Lbl

Out Lbl

In LblIn Lbl

Address Prefix

Address Prefix

128.89128.89171.69171.69

......

OutI’faceOut

I’face

1111......

Out Lbl

Out Lbl

In LblIn Lbl

Address Prefix

Address Prefix

128.89128.89

......

OutI’faceOut

I’face

00

......

Out Lbl

Out Lbl


MPLS Example:Assigning Labels

1

01

0

Use Lbl 7 for 171.69

Use Lbl 4 for 128.89 andUse Lbl 5 for 171.69

Label Distribution Protocol (LDP)(Downstream Allocation)

Use Lbl 9 for 128.89

128.89

171.69

In LblIn Lbl

Address Prefix

Address Prefix

128.89128.89171.69171.69

......

OutI’faceOut

I’face

0011......

Out Lbl

Out Lbl

In LblIn Lbl

Address Prefix

Address Prefix

128.89128.89171.69171.69

......

OutI’faceOut

I’face

1111......

Out Lbl

Out Lbl

In LblIn Lbl

Address Prefix

Address Prefix

128.89128.89

......

OutI’faceOut

I’face

00

......

Out Lbl

Out Lbl

----

4455

4455

9977

99 --


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 LblIn Lbl

Address Prefix

Address Prefix

128.89128.89171.69171.69

......

OutI’faceOut

I’face

0011......

Out Lbl

Out Lbl

In LblIn Lbl

Address Prefix

Address Prefix

171.69171.69......

OutI’faceOut

I’face

1111......

Out TLblOut TLbl

In LblIn Lbl

Address Prefix

Address Prefix

128.89128.89

......

OutI’faceOut

I’face

00

......

----

4455 55

9977

--44 99128.89128.89

Out Lbl

Out Lbl


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 in the network

• Allows building services such asMPLS VPNs

Traffic engineering and fast re-route

VPNs over traffic engineered core

Any transport over MPLSInner Label

Outer Label

IP Header

TE LabelTE Label

IGP LabelIGP Label

VPN LabelVPN Label





5. Summary


MPLS Features ...

That’s all nice but ...

How can you make money with it?


Metro Solutions –Architectural flexibility, service transparency

L3 VPNL2 VPN

TDM PL

GigE PL

Wavelength

Storage

Residential Data/Voice/Video

Enterprise VoIP

Internet Access

L2 VPN L3 VPNInternet Access


In what room do you want me to put it?

with enough fiber you could do anything?


MPLS IP-VPNThe L3 generation of core backbone

MPLSMPLSIPIP--VPNVPN

PSTNISDNBranch

Home

Travel

ADSL/Cable

Branch Home

INTERNET

Services

Regional Site

LL

Frame-RelayATM

Remote Sites

INTERNETBranch

Home

TravelIPSec Central

Site

TDMMUX





5. Summary


MPLS L2-VPNThe L3 generation of core backbone

Frame-RelayATM

Remote Sites

Frame-RelayATM

Remote Sites

Frame-RelayATM

MPLSMPLSIPIP--VPNVPNL2 VPNL2 VPN

Regional Site

Ethernet

Central Site

Ethernet

Ethernet

RegionalSite

Central Site

Ethernet

Regional Sites


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 policiesPolicies 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


MPLS-based IP-VPN Architecture

• Scalable VPNs

• IP QoS and traffic engineering

• Easy to manage and No VC provisioning required

• Provides a level of Security equivalent to Frame-relay and ATM

• Supports the deployment of 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 Bankcorp MPLS VPN Bankcorp

VPN ASite 2

VPN ASite 3

Corp ASite 1

Corp BSite 2

Corp BSite 1Corp B

Site 3

VPN Membership-Based on Logical Port

VPN Membership-Based on Logical Port


Using Labels to Build an IP VPN

• The network distributes labels to each VPNOnly labels for other VPN members are distributedEach VPN is provisioned automatically by IP routing

• Privacy and QoS of ATM without tunnels or encryptionEach network is as secure as a Frame Relay connection

• One mechanism (labels) for QoS and VPNs—no tradeoffs

Cust ACust ACust ACust A

Cust ACust A

Cust BCust B

Cust BCust B

MPLSNetwork

B-----------

B-----------

A-----------

A-----------


VPN A

VPN B

VPN C VPN A VPN BVPN C

VPN A

VPN B

VPN CVPN A

VPN C

VPN B

HostingMulticast

VoIP

Intranet

Extranet

Service Provider Benefitsof MPLS-Based VPNs

• Overlay VPNPushes content outside the networkCosts scale exponentiallyTransport dependentGroups endpoints, not groupsComplex overlay with QoS, tunnels, IP

• MPLS-based VPNsEnables content hosting inside the network“Flat” cost curveTransport independentEasy grouping of users and servicesEnables QoS inside the VPNs


MPLS Based IP-VPN Security

Cisco MPLS based VPNs: Equivalent to the Security of Frame Relay and ATM

Security

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

Miercom, March 30, 2001


Validating Cisco MPLS Based IP-VPN as a Secure Network

Security

Miercom independent testing confirmed Cisco MPLS VPN is secure:

Customers network topology is not revealed to the outside world

Customers can maintain own addressing plans and the freedom to use either public or private address space

Attackers cannot gain access into VPNs or Service Provider’s network

Impossible for attacker to insert “spoofed” label into a Cisco MPLS network and thus gain access to a VPN or the MPLS core

RED-Glascow2611

100.200.200.104

3.4.4.4

10.4.4.4

SER 5/0:0100.200.104.1

POS 1/0100.200.106.2

T1 FRdlci 102

eBGP AS72 T1 FRdlci 104RIP v2

Ser 3/0100.200.102.1

SiSi

SiSi

SER 1/0:0100.200.104.2

ATM2/0/0100.200.111.1

SER 1/0/1:0100.200.110.1

POS 2/1/0100.200.112.2

3.5.5.5

RED-Dover1750

100.200.200.10910.3.3.3

T1 FRdlci 109RIP v2T1 FR

dlci 110Static

10.3.3.3

DOVER7505

100.200.200.112

ATM1/0100.200.111.2

Ser 0100.200.109.2

BLUE-Dover2611

100.200.200.110 YELLOW-Dover3640

100.200.200.111

Ser 1/0100.200.110.2

Ser 5/0:0100.200.101.1

BLUE-Oxford1750

100.200.200.101

Ser 0100.200.101.2

T1 FRdlci 101

OSPF

10.4.4.4

pvc 0/11eBGP AS71

BLUE-Glascow3640

100.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

LONDONGSR12008

100.200.200.107

POS 1/0100.200.103.1POS 1/1

100.200.106.1

POS 1/0100.200.112.1

POS 2/0100.200.110.1

OC3 POSOC3 POS

YELLOW-Oxford3640

100.200.200.102

Ser 0/0100.200.102.2

SiSi

POS 2/0100.200.103.2

Test Network Topology


Key Features (Cont.)

• Connectivity to the Internet:VPN service providers may also provide connectivity to the Internet to its VPN customers

Common infrastructure is used for both VPN and the Internet connectivity services

• Simplifies operations and management for VPN service providers:

No need for VPN service providers to set up and manage a separate backbone or “virtual backbone” for each VPN


BGP/MPLS VPN—Summary

• Supports large scale VPN service

• Increases value add by the VPN service provider

• Decreases service provider cost of providing VPN services

• Mechanisms are general enough to enable VPN service provider to support a wide range of VPN customers





5. Summary


Ethernet Virtual Circuit – EoMPLS

EnterpriseCampus

A Ethernet Mapped Circuit

Access (L2)Ethernet

Access (L2)Ethernet

Access (L2)Ethernet

Access (L2)Ethernet

CoreMPLSCoreMPLS

Ethernet CircuitEoMPLS Tunnel in Core Enterprise

CampusB

MPLS

10/100/GigabitEthernet

10/100/GigabitEthernet

To the Enterprise this network isa pair of Pt to Pt 10/100/Gbit Bridged Ethernet Links

A B

MPLS PECisco 7600

MPLS PECisco 7600





5. Summary


VPLS ( Transparent LAN Services)

• Point to Multipoint Service

• Multipoint to Multipoint Service

• The network will simulate a L2 switch





5. Summary


L2 Transport: AToM|<|<-------------------- ES:FR/Ether/ATM/PPP/HDLC ES:FR/Ether/ATM/PPP/HDLC -------------------->|>|

|<|<------------ PW:Emulated VC PW:Emulated VC ------------>|>||<|<---- FR FR ---->| >| EthernetEthernet

ATM/PPP/HDLCATM/PPP/HDLC

|<|<----FR FR ---->| >| EthernetEthernet

ATM/PPP/HDLCATM/PPP/HDLC

ES ES 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

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

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

IP Network

MPLS Core

Attachment VC /Attachment VC /L2 circuitL2 circuit



Site1A

Site 2A

Attachment VC /Attachment VC /L2 circuit L2 circuit

PE1 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)


Any Transport over MPLSAToM

Service Provider

FR Cust

IPoFR cust

LSREdge-LSR

DLCI 202

DLCI 101

Example: Frame Relay over MPLS


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.txtdraft-martini-l2circuit-encap-mpls-01.txt





5. Summary


Why Traffic Engineering?

• Congestion in the network due to changing traffic patternsElection news, online trading, major sports events

• Better utilization of available bandwidthRoute on the non-shortest path

• Route around failed links/nodesFast rerouting around failures, transparently to usersLike SONET APS (Automatic Protection Switching)

• Build new services—Virtual leased line servicesVoIP toll-bypass applications, point-to-point bandwidth guarantees

• Capacity planningTE improves aggregate availability of the network


R8 R2

R6

R3R4

R7

R5

R1

IP (Mostly) Uses Destination-Based Least-Cost RoutingFlows from R8 and R1 Merge at R2 and Become IndistinguishableFrom R2, Traffic to R3, R4, R5 Use Upper Route

Alternate Path Under-Utilized

IP Routing and the Fish


Solution: Toll Bypass with Voice/Data Converged Network

PE

CE

PSTN –Traditional TDM

Network

Enterprise LAN

Enterprise LAN

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 with Circuit Emulation Interface

+ + + =⇒

Class 5legacy

switches

Fast Reroute in the core


DiffServ Aware TE Virtual Leased Line

PE

Central Office

Traditional Telephony

Toll Bypass

PE

VoIPGateway

VoIP Gateway

MPLS Network

PE PERegular TE

TunnelCEEnterprise

LANPE PE

Voice TrunkingVoice Trunking

VPN ServiceVPN Service

Internet ServiceInternet Service Enterprise LAN

Internet Access Router

Internet Access Router

Enterprise LAN

Class 5 LegacyswitchesPSTN—

Traditional TDM Network Central

OfficeTraditional Telephony

GB Tunnel

CEEnterprise

LAN

GB-TE TunnelRegular TE TunnelPhysical Link





5. Summary


What Is Fast Reroute?

Definition

Fast ReRoute (FRR) is a link or node protection feature, allowing for temporary bypassing of the failed link or node over a preestablished tunnel, while the head-end is rerouting the failed LSP


What is Fast Re-route? (cont.)

Head-end Router


Link Resilience (Next-hop Backup Tunnel)


Node Resilience (Next-next Hop Backup Tunnel)





5. Summary


Carrier Supporting Carrier& 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

CustomerCarriers

Carrier A

Carrier B


Inter-AS VPN Using VRF-to-VRF 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



•VPN routing information distributed across inter-AS network

VPN Routing Distribution Between MPLS VPN Backbones



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

Data Flow – Label Switching and IP Forwarding


MPLS VPN Enabled ISP Connected Across Standard Carrier (Cont.)

Customer Carrier is Not Running MPLS (Cont.)


MPLS VPN Enabled ISP Connected Across Standard Carrier (Cont.)

Customer Carrier is Running MPLS (Cont.)

IBGP





5. Summary


Receiver 4Receiver 4

B1

D

FF

CECE

A

CECE

CECE

High bandwidth multicast source



C

CECE

CECE

MPLS VPNMPLS VPNCore Core

CECE


EE

PEPEBPEPE

PEPE

EE

PEPEA

PEPED

C

Multicast VPN (MVPN)

Join highbandwidth source

Join highbandwidth source

• A Default MDT is created connecting all the PE’s within a VPN for signaling and low bandwidth flows

• Customer CE devices joins the MPLS Core through provider’s PE devices

• Data-MDT is formed for this High-Bandwidth source

• A High-bandwidth source for that customer starts sending traffic

• Interested receivers 1 & 2 join that High Bandwidth source

CECE

DataDataMDTMDT

For High Bandwidth traffic only.

DefaultDefaultMDTMDTFor low

Bandwidth & control

traffic only.

B2

San Francisco

San Francisco

Los Angeles

Los Angeles

DallasDallas

New YorkNew York





5. Summary


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 availability

Scope


Backbone and Edge QoS Design (Cont.)

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

• Three modes of interaction are defined between markings: Uniform, Pipe, and Short Pipe.

• Modes are only relevant when a label is popped/pushed.

QoS Transparency


Backbone and Edge QoS Design (Cont.)QoS Transparency: Uniform Mode



QoS Transparency: Pipe Mode



QoS Transparency: Short Pipe Mode





5. Summary


MPLS: The Key Technology for IP Service Delivery

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

Flexible user and service grouping (biz-to-biz)Flexibility of IP and the QoS and privacy of ATMEnables application and content hosting inside each VPNTransport independentLow 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 together

Eliminates IP “over” ATM overhead and complexityOne network for Internet, Business IP VPNs, and transport



• Guaranteed bandwidth servicesCombine MPLS traffic engineering and QoSDeliver point-to-point bandwidth guaranteed pipesLeverage the capability of traffic engineeringBuild solution like virtual leased line and toll trunking

• MPLS traffic engineeringProvides routing on diverse paths to avoid congestionBetter utilization of the networkBetter availability using protection solution (FRR)



• IP+Optical: MPLS brings IP and Optical togetherEliminates IP “over” optical complexityUses MPLS as a control plane for setting up lightpaths (wavelengths)One control plane for Internet (GMPLS), business IP VPNs, and Optical transport

• Any transport over MPLSTransport ATM, FR, Ethernet, PPP over MPLSProvide services to existing installed baseProtect Investment in the installed gearLeverage capabilities of the packet coreCombine with other packet-based services such as MPLS VPNs

FrameRelay

ATM

FrameRelay

IPServices

IPServices

OpticalServicesOptical

Services

IP+Optical SwitchIP+Optical Switch

O-UNIO-UNI MPLSMPLS

IPIP


Literature

MPLS and VPN ArchitecturesIvan PepelnjakJim Guichard

ISBN 1-58705-002-1


MPLS Features ...

That’s all nice but ...

How does this help me for my datacenter ?


Inter-Data Center Connectivity

Distributed Data Centers

Customer StrategiesMapping Customer Problems to Cisco Solutions

Data Center Solution Set

Data Center

DataSecurity

Highly Availability

Infrastructure

Storage Network

Application/Server Optimization

Strategies

•• Server, Application and DC Server, 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 CenterCenterNetworking


Data Center Networking

Data Center Infrastructure Server &

ApplicationOptimization

StorageNetworkingData Center

Security

DistributedData Centers

Campus Core

InternetISP A

Primary Data Center

Distributed Data Center

InternetSP B

Intranet

SP AIP Network

Externalprotection

Server farm protection

Internalprotection

IP NetworkPrimary

Data CenterDistributedData Center

ISP B

wolfgang riedel mpls overview [email protected]/mpls-overview.pdf · agenda...

Documents