v4/v6 L3VPN over IP Core - Tutorial

Madhusudan Nanjanagud [email protected]

Presentation_ID

2006 Cisco Systems, Inc. All rights reserved.

Cisco Confidential

Agenda
Introduction Feature Overview 6VPE v6 L3VPN Service integration Configuration flow Summary
Presentation_ID 2006 Cisco Systems, Inc. All rights reserved. Cisco Confidential

Introduction
Providers have legacy infrastructure with IP core Provide Managed IP/ VPN services(L2 /L3),mVPN Converged common IP Core Backbone Simplify network Operations/Maintenance Simplified interface with other providers Secured infrastructure for service integrations

Presentation_ID

2006 Cisco Systems, Inc. All rights reserved.

Cisco Confidential

Feature Overview
RFC4364 based L3 VPN Services with IP Core L3VPN services could be for v4 or v6 over the same IP core Leverages most of the functionality from MPLS core based VPN Presence of IP Core is transparent to Customer Edge devices Two common approaches mGRE & L2TPv3 Tunnel

Presentation_ID

2006 Cisco Systems, Inc. All rights reserved.

Cisco Confidential

Feature Overview
Multipoint to Point Tunnels are established between the edge routers through BGP signaling. Instead of manually configuring tunnels, Tunnel Reachability Information is signaled via BGP. Packets encapsulated with L2TPv3 header Session ID/Cookie (optional) values exchanged part of BGP updates No native L2TP signaling, BGP is used as the signaling protocol to convey encap header from PE to PE One Multipoint-to-point tunnel (configured per PE)

Presentation_ID

2006 Cisco Systems, Inc. All rights reserved.

Cisco Confidential

Tunnel Overlay Model

Tunnel Overlay Multiaccess Network

Tunnel overlay network switches VPN traffic between PEs Transport network provides connectivity between PEs Transport network is independent of VPN Service

IP Transport Network

Presentation_ID

2006 Cisco Systems, Inc. All rights reserved.

Cisco Confidential

Encap PE Packet format

Tunnel IP >> To reach Egress PE with PID as 0x73 ( L2TPv3) Session ID/Cookie >> For L2TPv3 session control/Security BGP VRF Label >> For remote End point VPN IP >> Final customer destination prefix

Presentation_ID

2006 Cisco Systems, Inc. All rights reserved.

Cisco Confidential

Session ID/Cookie Values

Part of the L2TPv3 header Optional Cookie field is a random 64 bit value in each data packet associated with session id To protect against a malicious blind attack, or inadvertent insertion of data into the tunnel stream.
IP 20 Bytes L2TPv3 Header 4 - 12 Bytes

Payload

Session Identifier 4 Bytes

Cookie 0,4,8 Bytes

* [REF] - W. Mark Townsley NANOG presentations on L2TPv3

Presentation_ID 2006 Cisco Systems, Inc. All rights reserved. Cisco Confidential

Comparison MPLS Transport

CE A PE A
Blu LS P e

MPLS Core
Ora nge LSP

PE B PE-A Router imposes VPN label such that remote PE-B has enough information to determine that the payload should be delivered to CE-B in the Green VRF => UNTOUCHED PE-A injects VPN-labelled packet into orange LSP which will transport the payload transparently (almost!) to PE-B => LSP REPLACED BY IP TUNNEL

CE B

Presentation_ID

2006 Cisco Systems, Inc. All rights reserved.

Cisco Confidential

Comparison - MPLS Based Core L3VPN flow

As per RFC4364, MP-BGP would exchange customer prefixes between PE routers with Next Hop address. Ingress PE has LSP established with egress PE LDP/RSVP. Ingress PE resolves the customer prefix within VRF table. Ingress PE would impose IGP Label + VPN Label+ Customer Payload Traffic to be drained over the core uplink interface MPLS enabled links. Core P router does label Swap/Push/Pop Egress PE Label lookup ->IP Lookup and then packet forwarded to egress interface.
Presentation_ID 2006 Cisco Systems, Inc. All rights reserved. Cisco Confidential

10

IP Core - Ingress PE
As per RFC4364, MP-BGP would exchange customer prefixes between PE routers with Next Hop address. Along with this, VRF labels are exchanged as well vpnv4 AFI Ingress PEs routing table is populated with the prefix info and having Egress PE as Next Hop. Ingress can reach Egress PE as per IGP update IP Core Ingress PE resolves the customer prefix with a multipoint L2TPv3 tunnel data structures. Ingress PE would impose Tunnel IP/L2TPv3 header+ VPN Label+ Customer Payload Traffic to be drained over the tunnel
Presentation_ID 2006 Cisco Systems, Inc. All rights reserved. Cisco Confidential

11

IP Core - Core P router

P routers run standard IGP. Incoming traffic from Ingress PE would result in standard IP look over the Carrier IP. The Destination IP being Egress PE. Lookup resolves into packet getting forwarded as is to the NH. NH could be another P router or the Egress PE itself.

Core P router Not Aware of VPN prefix Standard IP Lookup

Presentation_ID

2006 Cisco Systems, Inc. All rights reserved.

Cisco Confidential

12

IP Core Implementation Egress PE

Egress PE would do IP Lookup on the Tunnel IP and then process the L2TPv3 header. L2TPv3 Session ID matched with Local Tunnel records and Cookie value compared with incoming packet. After admittance check, Session Type indicates L3 which results in BGP VPN Deagg thread. BGP Label lookup would result in VRF and its associated outgoing interface after VPN IP lookup. The Tunnel IP, L2TPv3 Header, BGP VRF label are all removed and the IP packet is forwarded.

Presentation_ID

2006 Cisco Systems, Inc. All rights reserved.

Cisco Confidential

13

Forwarding Into and Out Of Tunnel

Encapsulation Behaviour Forwards IP packet by looking up IP destination in customer VRF. Add VPN label and tunnel encap via standard adjacency rewrite Forward packet using outer header IP destination via global routing table Decapsulation Behaviour Forwarding matches a receive entry that matches the local tunnel address and finds L2TPv3 protocol type in IP header Lookup in VPN forwarding table based on the MPLS label in the packet Forward the inner IP packet using the interface derived from MPLS label lookup
14

Presentation_ID

2006 Cisco Systems, Inc. All rights reserved.

Cisco Confidential

Control Plane Events

BGP (4364) PE1 CE-g1 PE2 2. Get Remote tunnel end points via BGP PE3 CE-g2

CE-p2

CE-p1

3. Send VPN v4/v6 info through BGP

4. Receive VPN v4/v6 info via BGP

CE-g3

IP Network

1. Remote end point is routable through IGP

Presentation_ID

2006 Cisco Systems, Inc. All rights reserved.

Cisco Confidential

15

Control Plane Operation

VPN-v4 update: VPN-v4 update: RD:1:27:152.12.4.0/24 NH=PE-1 RD:1:27:152.12.4.0/24 NH=PE-1 RT=1:1, Label=(29) RT=1:1, Label=(29) IP Core -- IGP IP Core IGP
PE1 P1 P2

BGP Route imported BGP Route imported To the VRF To the VRF
PE2

MP-iBGP MP-iBGP VPNv4 & NH info VPNv4 & NH info Tunnel session Tunnel session

VPN-B VRF Import routes with route-target 1:1

BGP, OSPF, RIP, Static BGP, OSPF, RIP, Static 152.12.4.0/24,NH=CE1 152.12.4.0/24,NH=CE1
CE1 CE2

BGP, OSPF, RIP, Static BGP, OSPF, RIP, Static 152.12.4.0/24,NH=PE-2 152.12.4.0/24,NH=PE-2

VPN B
152.12.4.0/24

VPN B

Presentation_ID

2006 Cisco Systems, Inc. All rights reserved.

Cisco Confidential

16

Forwarding Plane Operation

IPv4 Address L2TPv3 Header

ip THdr 29 152.12.4.6 ip Hdr 29 152.12.4.6 ip Hdr 29 152.12.4.6

Decap Decap
PE1 152.12.4.6 29 P1 P2 PE2

Encap Encap
152.12.4.6 29

VPN Label

IP L2TPv3
152.12.4.6

src addr dst addr Session Id Cookie VPN Label src addr

Tunnel Header
152.12.4.6

CE1

dst addr data

CE2

VPN B
152.12.4.0/24

VPN B

Presentation_ID

2006 Cisco Systems, Inc. All rights reserved.

Cisco Confidential

17

6VPE Analysis v6 L3VPN

Multiple approaches for IPv6 over v4 core IPv6 over EoMPLS/AToM IPv6 over L2TPv3 IPv6 CE-to-CE IPv6 over IPv4 tunnels IPv6 provider edge router (6PE) over MPLS/IP IPv6 VPN provider edge (6VPE) over MPLS/IP

Presentation_ID

2006 Cisco Systems, Inc. All rights reserved.

Cisco Confidential

18

6VPE Feature overview

6VPE is L3VPN services for v6 VPN customers RFC4659 L3VPN Extension for v6 VPN Could be MPLS based core or IP core No dual stacking in core! No v6 in Core Feature and functionality parity with v4 L3VPN v6 L3VPN services offered over the same v4 L3VPN infrastructure

Presentation_ID

2006 Cisco Systems, Inc. All rights reserved.

Cisco Confidential

19

6VPE : MP-BGP role

VPN BLUE v4 and v6 VPN

iBGP (MBGP) Sessions

v4 and v6 VPN VPN BLUE

v6 Only

P
v4 and v6 VPN

P
v6 Only

P
IP Core

v6 Only VPN YELLOW

6VPE ~ IPv6 customer payload + BGP VPN label + IP transport 6VPE is an implementation of RFC4659 VPNv6 address:
Address including the 64 bits route distinguisher and the 128 bits IPv6 address

MP-BGP VPNv6

AFI IPv6 (2), SAFI VPN (128)

VPN IPv6 MP_REACH_NLRI With VPNv6 next-hop (192bits) and NLRI in the form of <length, IPv6-prefix, label> Encoding of the BGP next-hop

Next Hop is carried as RD:v4-mapped-v6address

Presentation_ID 2006 Cisco Systems, Inc. All rights reserved. Cisco Confidential

20

6VPE : MP-iBGP role

MP-BGP is modular to facilitate distinct peering relationships Using the Address Family Identifier (AFI) VPNv4 & VPNv6 AFI Two provider edge routers to exchange labeled IPv6 VPN prefixes, they must use BGP capabilities negotiation for vpnv6 AFI. MP-iBGP peering would include typically vpnv4 AFI and vpnv6 AFI capability exchange along with other associated AFI/ SAFIs like Tunnel SAFI for L3VPN over IP Core 6VPE could have iBGP peering with RR which serve both vpnv4 and vpnv6 reflection.
Presentation_ID 2006 Cisco Systems, Inc. All rights reserved. Cisco Confidential

21

6VPE : Flow

Presentation_ID

2006 Cisco Systems, Inc. All rights reserved.

Cisco Confidential

22

6VPE Forwarding Operation

IPv4 Address L2TPv3 Header

ip THdr 29 2001::1 ip Hdr 29 2001::1 ip Hdr 29 2001::1

Decap Decap
PE1 2001::1 29 P1 P2 PE2

Encap Encap
2001::1 29

VPN Label

IP L2TPv3
2001::1

src addr dst addr Session Id Cookie VPN Label src addr

Tunnel Header
2001::1

CE1

dst addr data

CE2

VPN B
152.12.4.0/24

VPN B

Presentation_ID

2006 Cisco Systems, Inc. All rights reserved.

Cisco Confidential

23

6PE : Global v6 services

iBGP (MBGP) Sessions
2001:DB8:: 145.95.0.0 v6 v6 v6 2003:1:: 2001:CAFE::

v4

6PE

P P

P P

6PE

Dual Stack IPv4-IPv6 Routers 2001:F00D:: v6 CE

Dual Stack IPv4-IPv6 Routers

6PE
192.76.10.0 v4 CE

IP Core

6PE
v4 CE 192.254.10.0

IPv6 global connectivity over and IPv4 core PE to support dual stack/6PE IPv6 reachability exchanged among 6PEs via iBGP IPv6 packets transported from 6PE to 6PE
Presentation_ID 2006 Cisco Systems, Inc. All rights reserved. Cisco Confidential

24

Sample Configuration Flow

iBGP (vpnv4, v4 tunnel, vpnv6)

eBGP

eBGP
Lo0 5.5.5.5

ISIS
pos 53.2.2.1

Lo0 3.3.3.3
pos 53.2.2.2

Router Tester

Pos0/1/0/0 PE1

PE2

Router Pos0/8/0/0Tester
Advertise 120.1.1.0

Presentation_ID

2006 Cisco Systems, Inc. All rights reserved.

Cisco Confidential

25

BGP Config vpnv4 & vpnv6 AFI

(Cisco config guide reference)

PE1 Config BGP Related

router bgp 1803 bgp router-id 5.5.5.5 address-family ipv4 unicast ! address-family ipv4 tunnel ! address-family vpnv4 unicast ! address-family ipv6 unicast ! address-family vpnv6 unicast ! neighbor 3.3.3.3 remote-as 1803 update-source Loopback0 address-family ipv4 unicast ! address-family ipv4 tunnel ! address-family vpnv4 unicast ! address-family vpnv6 unicast !
Presentation_ID 2006 Cisco Systems, Inc. All rights reserved. Cisco Confidential

PE2 Config BGP Related

router bgp 1803 bgp router-id 3.3.3.3 address-family ipv4 unicast ! address-family ipv4 tunnel ! address-family vpnv4 unicast ! address-family ipv6 unicast ! address-family vpnv6 unicast ! neighbor 5.5.5.5 remote-as 1803 update-source Loopback0 address-family ipv4 unicast ! address-family ipv4 tunnel ! address-family vpnv4 unicast ! address-family ipv6 unicast ! address-family vpnv6 unicast !

26

Local VRF (PE-CE) config

(Cisco config guide reference) RP/0/8/CPU0:PE1#sh run int poS 0/1/0/0 interface POS0/1/0/0 vrf vpn55 RP/0/8/CPU0:PE1#sh run router bgp vrf vpn55 ipv4 address 15.1.1.1 255.255.255.0 vrf vpn55 ipv6 address 1511::1/64 rd 1803:55 ipv6 enable address-family ipv4 unicast encapsulation hdlc ! keepalive disable address-family ipv6 unicast ! ! RP/0/8/CPU0:PE1#sh run vrf vpn55 neighbor 15.1.1.2 vrf vpn55 remote-as 7000 address-family ipv4 unicast import route-target address-family ipv4 unicast 1803:55 route-policy allpass in ! route-policy allpass out export route-target ! 1803:55 ! ! neighbor 1511::2 ! remote-as 7001 address-family ipv6 unicast import route-target address-family ipv6 unicast 1803:55 route-policy allpass in ! route-policy allpass out export route-target ! 1803:55
2006 Cisco Systems, Inc. All rights reserved. Cisco Confidential

Presentation_ID

27

Service Integration
With this L3VPN v4/v6 over IP infrastructure, new services can be offered Layer 2 VPN L2TP Signaling Native Multicast or Multicast VPN BGP MDT SAFI Quality of Service Edge & Core Service Provider Edge feature set can be integrated over the same infrastructure Transparent to customers CsC and Inter-AS Parity with MPLS based core! Transit carriers can be IP Core based while Baby Carriers could be MPLS core based.

Presentation_ID

2006 Cisco Systems, Inc. All rights reserved.

Cisco Confidential

28

Summary
Investment Protection for Providers IP Core Enabling L3VPN v4 & v6 services over the legacy infrastructure Newer services can be easily integrated L2VPN multicast VPN / Native Network Troubleshooting / Maintenance simplified Parity with MPLS based services Implementation on networking gear is simplified

Presentation_ID

2006 Cisco Systems, Inc. All rights reserved.

Cisco Confidential

29

Thank You!

Presentation_ID

2006 Cisco Systems, Inc. All rights reserved.

Cisco Confidential

30