https www.ietf.org proceedings 49 slides ppvpn-7

12
8/11/2019 Https Www.ietf.Org Proceedings 49 Slides Ppvpn-7 http://slidepdf.com/reader/full/https-wwwietforg-proceedings-49-slides-ppvpn-7 1/12 1 49 th  IETF, San Diego, CA, December 2000 L. Fang Implementing MPLS VPN in Provider's IP Backbone Luyuan Fang [email protected] AT&T

Upload: elvin-dionicio

Post on 02-Jun-2018

215 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: Https Www.ietf.Org Proceedings 49 Slides Ppvpn-7

8/11/2019 Https Www.ietf.Org Proceedings 49 Slides Ppvpn-7

http://slidepdf.com/reader/full/https-wwwietforg-proceedings-49-slides-ppvpn-7 1/12

149th IETF, San Diego, CA, December 2000L. Fang

Implementing MPLS VPN in

Provider's IP Backbone

Luyuan Fang

[email protected]

AT&T

Page 2: Https Www.ietf.Org Proceedings 49 Slides Ppvpn-7

8/11/2019 Https Www.ietf.Org Proceedings 49 Slides Ppvpn-7

http://slidepdf.com/reader/full/https-wwwietforg-proceedings-49-slides-ppvpn-7 2/12

249th IETF, San Diego, CA, December 2000L. Fang

Outline

! BGP/MPLS VPN (RFC 2547bis)

! Setting up LSP for VPN - Design Alternative Studies! Interworking of LDP / RSVP / VPN protocols

! Interoperability in heterogeneous IP network 

! MPLS VPN Deployment Issues

! Scalability

!  VPN security

! Load sharing between PE-CE links

!

MPLS VPN network management! Provisioning

! Performance

! Fault Management

Page 3: Https Www.ietf.Org Proceedings 49 Slides Ppvpn-7

8/11/2019 Https Www.ietf.Org Proceedings 49 Slides Ppvpn-7

http://slidepdf.com/reader/full/https-wwwietforg-proceedings-49-slides-ppvpn-7 3/12

349th IETF, San Diego, CA, December 2000L. Fang

BGP/MPLS VPN (RFC 2547bis)

! MPLS VPN: Deliver network based VPN services over shared IPnetwork.

! Security: Controlled access. VRF - “VPN Routing and Forwarding” tables, contains customer VPN routes. VPNs are isolated.

! Scalability: Provider backbone (P) routers are not VPN aware;Provider Edge (PE) router only holds the routing information of 

 VPN directly connected.

! Customer addresses can overlap. Support non-unique, private(RFC1918) addressing in customer networks.

! Easy configuration for customers, no special changes requiredon customer side (for Enterprise VPN).

Page 4: Https Www.ietf.Org Proceedings 49 Slides Ppvpn-7

8/11/2019 Https Www.ietf.Org Proceedings 49 Slides Ppvpn-7

http://slidepdf.com/reader/full/https-wwwietforg-proceedings-49-slides-ppvpn-7 4/12

449th IETF, San Diego, CA, December 2000L. Fang

PE1

PE3

P1

P3

P2

P4

PE2

PE4

CE3X1

CE2

Y1

CE5

VPN Red

X2

VPN Green

VPN Green

CE4

VPN Red

Y1

CE6

Y2

VPN Green

CE1

VPN Red

X1

Lookup done once

the ingress PE3attaches two labels

on each packet

Penultimate Hop PoppingP4 removes the top label

Label swappingbased on IGP

(top) label

Pop VPN label (inner)

find the outgoing interface

aggregate to CE6

BGP/MPLS VPN

• IGP (e.g. OSPF, or ISIS) routing in the core

• MPLS (e.g. LDP) enabled for all P and PE• MP-iBGP fully meshed between PEs• PE-CE can be e-BGP, OSPF, RIP or Static

Configuration: Two level Labels:

• Top label : LDP label forwarding

through the core, PE-PE• Inner label : VPN label identify the

destination VPN, forwarding to CE

Page 5: Https Www.ietf.Org Proceedings 49 Slides Ppvpn-7

8/11/2019 Https Www.ietf.Org Proceedings 49 Slides Ppvpn-7

http://slidepdf.com/reader/full/https-wwwietforg-proceedings-49-slides-ppvpn-7 5/12

549th IETF, San Diego, CA, December 2000L. Fang

Setting up LSP for VPN- Design Alternatives Study

! Example 1: VPN / LDP

! MPLS (LDP) enabled in the entire backbone network, including all Pand PE routers for setting up the Label Switched Path (LSP)

!  VPN enabled on VPN PE routers

!  Advantage: simplicity

! Consider: availability of LDP

PE1

PE3P1

P3

P2

P4

PE2

PE4

CE1

VPN A

X

CE2

VPN A

Y

LSP = IGP path (e.g. OSPF shortest path), in this case

Page 6: Https Www.ietf.Org Proceedings 49 Slides Ppvpn-7

8/11/2019 Https Www.ietf.Org Proceedings 49 Slides Ppvpn-7

http://slidepdf.com/reader/full/https-wwwietforg-proceedings-49-slides-ppvpn-7 6/12

649th IETF, San Diego, CA, December 2000L. Fang

! Example 2: VPN / RSVP!

Using RSVP TE Tunnel through Multi OSPF areas (PE-PE) for setting up theLSP, with back-up tunnel for failure protection

! RSVP tunnels are unidirectional, alternative path can be taken for eachdirection

!  VPN enabled on VPN PE routers

!   Advantage: Better TE control, including fast reroute when available

!   Consider: Availability of RSVP across multi-OSPF area; many long tunnelsrequired throughout the network may or may not be desirable.

LSP: RSVP traffic engineering tunnel

PE1

PE3 P1

P3

P2

P4

PE2

PE4

CE1

VPN A

X

CE2

VPN A

Y

OSPF area 0OSPF area A OSPF area B

Setting up LSP for VPN- Design Alternatives Study

Page 7: Https Www.ietf.Org Proceedings 49 Slides Ppvpn-7

8/11/2019 Https Www.ietf.Org Proceedings 49 Slides Ppvpn-7

http://slidepdf.com/reader/full/https-wwwietforg-proceedings-49-slides-ppvpn-7 7/12

749th IETF, San Diego, CA, December 2000L. Fang

! Example 3: VPN / LDP / RSVP! Config LDP for PE1 and P1, P4 and PE2.

! Build short RSVP TE Tunnel in OSPF area 0 (P1-P3-P5-P4), note P1 and P4may be from one vendor, acting as the head-end, P3 and P5 may be fromanother vendor. P3 and P5 does not need to enable LDP.

! Interoperability on RSVP is required, not LDP in this example .

!  VPN enabled on VPN PE routers.

!   Advantage: LDP does not need to be available everywhere. Short tunnel.

!   Consider: There are no end-to-end TE control.

 RSVP traffic engineering tunnel LDP path

PE1

PE3 P1

P3

P2

P4

PE2

PE4

CE1

VPN A

X

CE2

VPN A

Y

P5

OSPF area BOSPF area A OSPF area 0

Setting up LSP for VPN- Design Alternatives Study

Page 8: Https Www.ietf.Org Proceedings 49 Slides Ppvpn-7

8/11/2019 Https Www.ietf.Org Proceedings 49 Slides Ppvpn-7

http://slidepdf.com/reader/full/https-wwwietforg-proceedings-49-slides-ppvpn-7 8/12

849th IETF, San Diego, CA, December 2000L. Fang

MPLS VPN Deployment Issues

!

MPLS Feature availability!  VPN, LDP, RSVP, CR-LDP: individually, and Interworking

! Design largely based on feature availability Vs. optimal

! Multi-vendor inter-operability

! Required in an heterogeneous IP network ! Incremental deployment plans

! Fully enable MPLS in the entire IP backbone Vs. partiallyenable MPLS.

! TE tunnels, use only as needed Vs. fully meshed! Incrementally deploy BGP/MPLS VPN on PE routers

Page 9: Https Www.ietf.Org Proceedings 49 Slides Ppvpn-7

8/11/2019 Https Www.ietf.Org Proceedings 49 Slides Ppvpn-7

http://slidepdf.com/reader/full/https-wwwietforg-proceedings-49-slides-ppvpn-7 9/12

949th IETF, San Diego, CA, December 2000L. Fang

! Scalability

! The use of Route Reflector! Performance impact on PEs needs to be measured

! Load sharing between PE-CE links

!  Assign different RDs to different sites Vs. single RD for each

 VPN.! Security

! One VPN’s route does not exist in other non-connected VPN’s VRF or the global routing table

!

FR/ATM equivalent security - more study needed! Multi-AS inter-working

! Feature needed today for building VPN to traverse multi-AS / multi-provider’s network 

MPLS VPN Deployment Issues

Page 10: Https Www.ietf.Org Proceedings 49 Slides Ppvpn-7

8/11/2019 Https Www.ietf.Org Proceedings 49 Slides Ppvpn-7

http://slidepdf.com/reader/full/https-wwwietforg-proceedings-49-slides-ppvpn-7 10/12

1049th IETF, San Diego, CA, December 2000L. Fang

MPLS VPN network management

!  Available MIBs today

! LSR MIB, VPN MIB, MBGP MIB, RSVP TE MIB,TDP MIB, FTNMIB,…

! Configuration and Provisioning

!  Auto-provisioning tools needed for large scale VPN deployment

! Performance!  All MPLS features impact on performance, including basic VPN

on PE routers, need to be studied

! More study needed for VPN supporting QoS

! Network performance: delay, jitter, loss, throughput,availability

! Element performance: utilization

! Security

Page 11: Https Www.ietf.Org Proceedings 49 Slides Ppvpn-7

8/11/2019 Https Www.ietf.Org Proceedings 49 Slides Ppvpn-7

http://slidepdf.com/reader/full/https-wwwietforg-proceedings-49-slides-ppvpn-7 11/12

1149th IETF, San Diego, CA, December 2000L. Fang

! Traffic Management / Engineering!

Characterize traffic for VPNs! Profiling, correlation, and optimization

! Fault management! Monitoring and troubleshooting

!  VPN failure detection and recovery

MPLS VPN network management

PE1

PE3P1

P3

P2

P4

PE2

PE4

CE1

VPN A

X

CE2

VPN A

Y

Config: LDP in the core for all P and PE router; IGP: OSPF; iBGP full mesh between PEs

  LSP: OSPF shortest path: PE1-P1-P3-P4-PE2; no TE tunnels.

Problem: All links and nodes are up, but P3 label switching fails. LSP failure results in VPN failure.Solution required: PE1 and PE2 to to be notified of the LSP failure

  LSP needs to be re-established through recovery mechanism, force LSP <> OSPF path

Example:

Page 12: Https Www.ietf.Org Proceedings 49 Slides Ppvpn-7

8/11/2019 Https Www.ietf.Org Proceedings 49 Slides Ppvpn-7

http://slidepdf.com/reader/full/https-wwwietforg-proceedings-49-slides-ppvpn-7 12/12

1249th IETF, San Diego, CA, December 2000L. Fang

Summary

! Implementing BGP/MPLS VPN in large IP backbonecan be feasible

! Illustrations of alternatives and examples presented here havebeen experimented through lab testing and inter-lab trial

!

Deployment Challenges! Feature availability

! Interoperability

! Manageability

! Requirements on BGP/MPLS VPN implementation,service deployment and management